site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=q+mi4sgeivDT7Gi1GjlUtI4fw8QCgctp1XDgDIR+/GpQ2nPsAH4i92/gBP87mkM+; h=Received:From:To:In-Reply-To:X-Mailer:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-ELNK-Trace:X-Originating-IP; Hi, Darrin. Certainly, Image Parameters have been troublesome. Especially, getting frames synced from timeline to matching frames in Image parameters. Trying to keep them in sync through user edits on the Timeline was very troublesome. I wrote a bunch of stereoscopic FxPlugs a while back. I eventually got them working as well as the API would allow. Some of the Dev problems were documentation that could be misinterpreted, which could have been disambiguated better if there were examples to clarify. Of course, eventually, after figuring it all out, I realized that some necessary functionally was just not in the API at all. These were not just stereoscopic related, but missing functionality for image parameters in general. So, I've had to do stereo-3D in two passes. A "conform" pass, to merge the two streams (Left and Right cameras) into one 3-D stream. Then, the regular editing, using the merged footage. I only use Image Parameters in the Conform stage. This allows me to avoid Image Parameters completely during the regular 3-D editing of the movie. (I never edit 3-D movies in 2-D.) I have never released any of these commercially. Mostly because I've never figured out how to implement licensing code for FxPlugs. So far, I've just been using them in-house for various movies roughly over the past 5 years. Which might be another thing that could be addressed into documentation. Like an example license gen/checker. -- Brian Sent from my iPad On Oct 19, 2010, at 7:16 AM, Darrin Cardani <dcardani@apple.com> wrote:
I'm working on some documentation (gasp!), and am trying to think of problems that developers commonly run into when writing plug-ins. The things I've thought of so far are not properly handling non-square pixels, fields, and proxy resolution. So I'm thinking of writing some documentation on how to properly handle those and how to test your plug-ins to ensure that you're properly handling them.
What other problems have vexed you in the past when writing your plug-ins? Anything you wish you had better documentation on?
Thanks, Darrin -- Darrin Cardani dcardani@apple.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/brianrg%40earthlink.net
This email sent to brianrg@earthlink.net
Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com