October 2010 - Pro-apps-dev

Re: What problems do you run into when writing plug-ins?
by Darrin Cardani 25 Oct '10

25 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I will look into it. I think that you need to make your own info parameter, and use the current context as the "shared context" parameter. I think you might be right that it's irrelevant, because I think we only set that to give information to the plug-in, and we use the appropriate thing internally. But I'll verify that and then try to clarify it in the docs. Darrin On Oct 25, 2010, at 11:24 AM, Garrick Meeker wrote: > In a somewhat recent post you mentioned that Motion 4 added support to checkout images at non-render times. Unless I'm missing something, the documentation doesn't mention that this is supported and it doesn't describe what to pass to the withInfo parameter. I'm guessing you just initialize it yourself and the sharedContext field isn't required. I haven't tried this myself. Are there still limitations on when this should be called? Would you call it while drawing a custom parameter? > > On Oct 18, 2010, at 4:16 PM, Darrin Cardani 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(a)apple.com >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarch… >> >> This email sent to garrick(a)digitalanarchy.com > -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Garrick Meeker 25 Oct '10

25 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com In a somewhat recent post you mentioned that Motion 4 added support to checkout images at non-render times. Unless I'm missing something, the documentation doesn't mention that this is supported and it doesn't describe what to pass to the withInfo parameter. I'm guessing you just initialize it yourself and the sharedContext field isn't required. I haven't tried this myself. Are there still limitations on when this should be called? Would you call it while drawing a custom parameter? On Oct 18, 2010, at 4:16 PM, Darrin Cardani 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(a)apple.com > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarch… > > This email sent to garrick(a)digitalanarchy.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Brian Gardner 24 Oct '10

24 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=FE02WOyRgiQ3OwKzhPpEskA4ypxPeq5DtttlVL/wU9gXGADSp+sPymhKtWZKhDiV; 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; _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Andrew Mees 23 Oct '10

23 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Darrin Cardani 22 Oct '10

22 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com That's a really good suggestion. Some quick advice: Don't open a dialog during a render in Motion. Rendering happens on threads other than the UI thread, so it's not safe to display and run a dialog. I believe that currently Final Cut Pro renders on the UI thread, but there's no guarantee that won't change in the future. I'll see if I can flesh out more details for the docs on this. Thanks! Darrin On Oct 22, 2010, at 3:28 PM, Garrick Meeker wrote: > Many people porting AE plugins could run into the issue of displaying a message to the user, i.e. figuring out what to do with the code that sets return_msg in the AE plugin. In places like parameter changed callbacks, it makes sense to just display a dialog. I'm still not sure what to do if something goes wrong in the render. Retuning NO just shows the generic "render failed" message, but opening a dialog seems like bad citizen behavior: stopping a potentially long render for user interaction, and possibly annoying the user if the dialog appears more than once. Or is that not an issue because an error will stop all rendering? What do other people do? I didn't think about this until our plugins got complex enough that "out of memory" was no longer the only possible error. > > While this sounds like a feature request, it'd be helpful to have some guidance in the docs for the current versions of the apps, even just "don't open a dialog during the render call." > > On Oct 18, 2010, at 4:16 PM, Darrin Cardani 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(a)apple.com > -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Garrick Meeker 22 Oct '10

22 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Many people porting AE plugins could run into the issue of displaying a message to the user, i.e. figuring out what to do with the code that sets return_msg in the AE plugin. In places like parameter changed callbacks, it makes sense to just display a dialog. I'm still not sure what to do if something goes wrong in the render. Retuning NO just shows the generic "render failed" message, but opening a dialog seems like bad citizen behavior: stopping a potentially long render for user interaction, and possibly annoying the user if the dialog appears more than once. Or is that not an issue because an error will stop all rendering? What do other people do? I didn't think about this until our plugins got complex enough that "out of memory" was no longer the only possible error. While this sounds like a feature request, it'd be helpful to have some guidance in the docs for the current versions of the apps, even just "don't open a dialog during the render call." On Oct 18, 2010, at 4:16 PM, Darrin Cardani 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(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Darrin Cardani 21 Oct '10

21 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Oct 20, 2010, at 1:26 PM, Mattias Sandstrom wrote: > On 20/10 2010 00:12 , Mattias Sandstrom wrote: >> currently experimenting with reading chroma values from a desaturated >> buffer but that's some workaround for sure, and it's not quite working >> either. > > it's not working because colorof returns the 8-bit value regardless of render mode. i guess i could find the positive edges with a zero offset, add them to a gray buffer, then find the negative edges and subtract from the same. more work for no extra functionality but whatever, i'm used to it. either way this is something you need to document. or is your request only about the fxplug architechture? I was mainly asking about FxPlug documentation. I don't work on FxScript at all, but I'll pass your suggestion on to the people who do. Thanks, Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Mattias Sandstrom 20 Oct '10

20 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5 currently experimenting with reading chroma values from a desaturated buffer but that's some workaround for sure, and it's not quite working either. /mattias _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… On 20/10 2010 00:12 , Mattias Sandstrom wrote: it's not working because colorof returns the 8-bit value regardless of render mode. i guess i could find the positive edges with a zero offset, add them to a gray buffer, then find the negative edges and subtract from the same. more work for no extra functionality but whatever, i'm used to it. either way this is something you need to document. or is your request only about the fxplug architechture? This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Robert Monaghan 20 Oct '10

20 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: What problems do you run into when writing plug-ins?
by Darrin Cardani 20 Oct '10

20 Oct '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0