August 2011 - Pro-apps-dev - lists.apple.com

Re: so confused about image wells/drop zones for Final Cut Effect templates.
by Darrin Cardani 04 Aug '11

04 Aug '11

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: so confused about image wells/drop zones for Final Cut Effect templates.
by Alex Gollner 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: AcxS9nvWmwp2rAFDIEe03FQEWc+cgQ== Thread-topic: so confused about image wells/drop zones for Final Cut Effect templates. User-agent: Microsoft-Entourage/12.24.0.100205 On 04/08/2011 8:24 pm, you wrote a message that included: > When I create another Drop Zone that I drop into one of my image wells so > that I may use the image well in FCP When I create drop zones in .moefs, they automatically are created at the same size as the project. That allows for the same project to be used at different sizes and aspect ratios. These are also automatically published with the effect for use in Final Cut. I think the placeholder image itself isn't 1920 by 1080, but it's only for illustrative purposes. Alex ............................................................................ Screenwriter, Zone 2-North West, London alex4d on twitter, facebook, .wordpress.com & .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: so confused about image wells/drop zones for Final Cut Effect templates.
by Peter Litwinowicz 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-topic: so confused about image wells/drop zones for Final Cut Effect templates. User-agent: Microsoft-MacOutlook/14.12.0.110505 _______________________________________________ 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: Moefs not storing all FxPlug parameters?
by Nathan Weston 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 On Aug 4, 2011, at 8:55 AM, Nathan Weston wrote: Yes this is intentional. It's an optimization to make reading Motion Effects faster. This is a really bad idea. Consider the following case: 1. User creates a Motion Effect with version 1 of my plugin. They leave parameter X at the default value. 2. I release version 2 of my plugin, in which I've changed the default value of X to something nicer. 3. User installs version 2, and their Motion Effect now renders differently. You should be checking the -versionAtCreation method and setting the default appropriately. If the plug-in's versionAtCreation is 1, set the default to the version 1 default. If it's 2, set the default to the version 2 default. Note that if your plug-in didn't have a version when the document was created, -versionAtCreation will return 0. So when you update it and add a version, just set it to 1, and you'll be able to tell the current version from older versions. -- . . . . . . . . . . . . . . . . . . . . . . . . . Nathan Weston nathan(a)genarts.com GenArts, Inc. Tel: 617-492-2888 955 Mass. Ave Fax: 617-492-2852 Cambridge, MA 02139 USA www.genarts.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… On 8/4/2011 12:46 PM, Darrin Cardani wrote: When I make a Motion Effect containing an FxPlug, it appears that it only stores parameters which have been changed from the default value. Is that expected behavior? In effect, it means we can never change parameter default values if we want to keep backward compatibility. If you store all the parameters in the Motion Effect it's guaranteed to render consistently even if the FxPlug changes default values underneath it. I still think it's a bad idea, and I strongly urge you guys to reconsider. Compatibility tricks with versionAtCreation are a big burden on the plug-in developer, and provide many opportunities to screw things up. By storing the default values you can protect your users from this potential problem in one easy step, even if plug-in developers are lazy or careless. It's hard to believe that the overhead of reading a few params (or even a few dozen) can make a significant speed difference, unless your storage format is really screwed up. :) This email sent to site_archiver(a)lists.apple.com

1 0

Re: Moefs not storing all FxPlug parameters?
by Darrin Cardani 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 4, 2011, at 8:55 AM, Nathan Weston wrote: > When I make a Motion Effect containing an FxPlug, it appears that it only stores parameters which have been changed from the default value. Is that expected behavior? Yes this is intentional. It's an optimization to make reading Motion Effects faster. > This is a really bad idea. Consider the following case: > 1. User creates a Motion Effect with version 1 of my plugin. They leave parameter X at the default value. > 2. I release version 2 of my plugin, in which I've changed the default value of X to something nicer. > 3. User installs version 2, and their Motion Effect now renders differently. > > In effect, it means we can never change parameter default values if we want to keep backward compatibility. If you store all the parameters in the Motion Effect it's guaranteed to render consistently even if the FxPlug changes default values underneath it. You should be checking the -versionAtCreation method and setting the default appropriately. If the plug-in's versionAtCreation is 1, set the default to the version 1 default. If it's 2, set the default to the version 2 default. Note that if your plug-in didn't have a version when the document was created, -versionAtCreation will return 0. So when you update it and add a version, just set it to 1, and you'll be able to tell the current version from older versions. 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: Point controls, parameter groups, and templates (oh my!)
by Darrin Cardani 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 3, 2011, at 5:02 PM, Pierre Jasmin wrote: > A simple test procedure Apple could use in internal QA is something like make an uncompress movie (with 0.91 PAR) that is just alternate 1,0,1,0 for pixel values (ON/OFF) repeated at all frames... (you could maybe if this could be more then 8 bit do something that looks like a bit like a bayer mosaic ant set the alternatively R then G then B ON value to something not 1.0 to allow you to catch 8 bit in pixel path, and gamma or pixel order out of wack). > make a plugin that reads a frame at another time (A), reads a frame from that movie copy using the clip well (B) , and reads the main input (C), > plugin loops through pixels and does a diff of A to B (if pixel is different r=1,else 0), and B to C (if pixel is different g=1,else 0), and C to A (if pixel is different b=1,else 0). > For more complete case replace last diff by a procedural one that redraws the mosaic and where ON level is equal to the float value level that is equivalent to the rounded value on either 0-1023 or 0-4095 levels scale used to make reference test pattern movie source. > Make a template at 1080p square pixel with that fabulous effect > load SD res movie and apply template in FCP-X... > repeat software and hardware. > If you don't get a constant black image, bug! That's a really great idea. I'm actually working on improving our automated testing, so this will help a lot. 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: Point controls, parameter groups, and templates (oh my!)
by Darrin Cardani 04 Aug '11

04 Aug '11

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: Poor performance on software rendering generator
by Darrin Cardani 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com We're seeing that software rendering for a generator is extremely slow. All these are on a Motion 5 project at 1920x1080, 29.97fps, progressive at full res. ... So even before we add any custom code we're hampered by using software rendering, and this is just a simple generator with an output only not a filter with input/output. _______________________________________________ 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

Moefs not storing all FxPlug parameters?
by Nathan Weston 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 - Nathan _______________________________________________ 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… When I make a Motion Effect containing an FxPlug, it appears that it only stores parameters which have been changed from the default value. Is that expected behavior? This is a really bad idea. Consider the following case: 1. User creates a Motion Effect with version 1 of my plugin. They leave parameter X at the default value. 2. I release version 2 of my plugin, in which I've changed the default value of X to something nicer. 3. User installs version 2, and their Motion Effect now renders differently. In effect, it means we can never change parameter default values if we want to keep backward compatibility. If you store all the parameters in the Motion Effect it's guaranteed to render consistently even if the FxPlug changes default values underneath it. This email sent to site_archiver(a)lists.apple.com

1 0

Opening an NSPanel in FCP 7 blocks in a runModalSession session loop
by Peter T 04 Aug '11

04 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=yTzEsPVwswQjCOZywZBq7QBpaSm0PJj+LWGnBEqtanU=; b=eG6hQ62wDXCjjpHteFyOf9+/amExbjml+2dOGHgjjklA1hNWafTSF+lSYfHDs2tfoo 5sh0SU01/ULBIzveLjYLBRoQ79vpDdyizIRiyWE1O3OnN4IMe2Dtrx0pkL2hLSrupZ0G c1CkhgqTNBvGc/pv1Al56QQPghuudcv71K3oU= _______________________________________________ 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