February 2009 - Pro-apps-dev

Re: Motion - Antialiasing off
by Darrin Cardani 04 Feb '09

04 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Feb 4, 2009, at 4:57 AM, Kamil Ornarowicz wrote: 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… Is there any option to turn off anti-aliasing in Motion? Every "single line" is imported and draw as group of pixels with some blur. I can't find option to turn off this feature. It is easy to examine by changing view to 800% and draw a sample line. Can you describe in more detail what you are doing? I don't understand what you mean by "Every 'single line' is imported and drawn..." How are you importing these lines? What type of files contain them? Also, what are your project and view settings? Is this a progressive project or interlaced? This email sent to site_archiver(a)lists.apple.com

1 0

Re: fxplugins generated by XCode standard templates not showing up in FCP
by Steve Christensen 04 Feb '09

04 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com steve On Feb 3, 2009, at 3:52 PM, Philipp Haindl wrote: _______________________________________________ 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… The most likely problem is that you haven't generated new UUIDs for the plugin and for the plugin's group. The project templates use reserved UUIDs that FCP, FCE and Motion know about. When you launch one of them you should see the following Console message if you haven't yet changed the UUIDs: The UUID of the plug-in "Test" is reserved, and will not be registered. To correct this, edit the "uuid" entry in the plug-in's Info.plist file. If you look inside the plugin's info.plist file, you'll see some comments that show you how and where to make the changes. A strange problem - hope you can help.. I'm new to fxplugin and try to experiment with this SDK. When I compile the sample FXPlugins provided through the plugin installation, the show up in Final Cut Pro. Unfortunately, when I pick any FXPlugin from the "Standard Apple Plugins" menu in XCode to write my own one, I'm able to compile the generated project without any errors, but they don't show up in FCP... Does anyone have a hint on this? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Motion - Antialiasing off
by Patrick Sheffield 04 Feb '09

04 Feb '09

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=pSiajCYrIjTvYULDoBBXv5KLFO4AM7IgvxC1hg/6g1xX2gO3AqvhAFOT67eJuGxz; h=Received:Cc:Message-Id:From:To:In-Reply-To:Content-Type:Mime-Version:Subject:Date:References:X-Mailer:X-ELNK-Trace:X-Originating-IP; Patrick On Feb 4, 2009, at 4:57 AM, Kamil Ornarowicz wrote: Hi All, Kamil _______________________________________________ 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/psheffield%40earthlink.… _______________________________________________ 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 Oh happy day if that were the case, but no - AFAIK, there is no way to disable the anti-aliasing in Motion. I suspect it has to do with using the GFx card to do the rendering... Is there any option to turn off anti-aliasing in Motion? Every "single line" is imported and draw as group of pixels with some blur. I can't find option to turn off this feature. It is easy to examine by changing view to 800% and draw a sample line. This email sent to psheffield(a)earthlink.net smime.p7s

1 0

Motion - Antialiasing off
by Kamil Ornarowicz 04 Feb '09

04 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi All, Kamil _______________________________________________ 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… Is there any option to turn off anti-aliasing in Motion? Every "single line" is imported and draw as group of pixels with some blur. I can't find option to turn off this feature. It is easy to examine by changing view to 800% and draw a sample line. This email sent to site_archiver(a)lists.apple.com

1 0

Problems opening Final Cut Pro (6.0.2) files on XSan
by Matt Christy 04 Feb '09

04 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-index: AcmGOwXR19VbwKtfSO2gp6klWqDhjgAhZvGw Thread-topic: Problems opening Final Cut Pro (6.0.2) files on XSan Hello All, We're running into very frustrating issues as we are trying to save and open Final Cut Pro project files. We are currently using an XSan with ACLs set up to store FCP documents and related files. The six workstations aren't directly attached to the SAN, they connect via GigE to AFP shares (not an ideal solution, but it's what we can afford right now). It should be noted that our setup is currently using the "Golden Triangle" of directory services (AD user accounts and groups). In December we upgraded our XSan to version 2 (which was a nightmare in itself), and all of our clients were upgraded to 10.5 with FCS2. After the upgrades, a few issues have arisen: 1. When a user attempts to save a FCP project, sometimes they receive the error message that the file is locked. From what I read on apples support site, this is due to permissions-- a file cannot be saved by one person, and then opened and saved by another. If the ACLs set on the folder reflect the groups that have full access to the files in which the project resides (recursively), why is this an issue? Or is this just another case of bad execution on apples part? 2. After concluding a "Save As", most of the time the alternate project file is able to be opened. We've run into several instances, however, when the project file is a very small size (16k or so), and gives the error message "Unable to open project file".. and it's pretty much trash. In these cases, the autosaves are behaving in a similar manner, being a very low size and not opening. So my question is, does this all sound like permissions issues.. or is there something inherently wrong with the XSan at this point (e.g. corruption)? How are other people using XSan volumes in conjunction with FCP 6.0.2/FCS2 to edit and store files? Perhaps we're going about the whole setup the wrong way.. Thanks for your time and any advice you can provide.. Matthew Lawrence Christy Systems Administrator Independence Media | MiND TV 215.483.3900 ext.208 | mchristy(a)mindtv.org 8200 Ridge Avenue, Philadelphia, PA 19128 www.independencemedia.org | www.mindtv.org _______________________________________________ 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: fxplugins generated by XCode standard templates not showing up in FCP
by Paul Schneider 03 Feb '09

03 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Philipp, Good luck! - Paul On Feb 3, 2009, at 5:52 PM, Philipp Haindl wrote: Hello all! Does anyone have a hint on this? Best regards, Philipp _______________________________________________ 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/pschneider%40apple.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… Make sure that your plugin is installed in either ~/Library/Plug-Ins/ FxPlug or /Library/Plug-Ins/FxPlug. And also, make sure that you have replaced the UUID's in your Info.plist with new versions. Check out the FxPlug SDK documentation for more hints. A strange problem - hope you can help.. I'm new to fxplugin and try to experiment with this SDK. When I compile the sample FXPlugins provided through the plugin installation, the show up in Final Cut Pro. Unfortunately, when I pick any FXPlugin from the "Standard Apple Plugins" menu in XCode to write my own one, I'm able to compile the generated project without any errors, but they don't show up in FCP... This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

fxplugins generated by XCode standard templates not showing up in FCP
by Philipp Haindl 03 Feb '09

03 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hello all! Does anyone have a hint on this? Best regards, Philipp _______________________________________________ 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… A strange problem - hope you can help.. I'm new to fxplugin and try to experiment with this SDK. When I compile the sample FXPlugins provided through the plugin installation, the show up in Final Cut Pro. Unfortunately, when I pick any FXPlugin from the "Standard Apple Plugins" menu in XCode to write my own one, I'm able to compile the generated project without any errors, but they don't show up in FCP... This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP parameter count limits?
by Paul Schneider 03 Feb '09

03 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Glad you figured it out! On Feb 2, 2009, at 7:08 PM, Garrick Meeker wrote: On Feb 2, 2009, at 4:43 PM, Paul Schneider wrote: Hi Garrick - Paul On Feb 2, 2009, at 6:37 PM, Garrick Meeker wrote: On Feb 2, 2009, at 4:13 PM, Paul Schneider wrote: Hi Garrick, - Paul On Feb 2, 2009, at 5:58 PM, Garrick Meeker wrote: This is FCP 6.0.5. _______________________________________________ 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/pschneider%40apple.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/pschneider%40apple.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/pschneider%40apple.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… It probably would have saved you a couple of hours if FCP printed a more helpful message when you registered the duplicate parameter. We have some bugs filed about this, but if you'd like to file a new one, that might help things get bumped up in priority. Okay, ignore all of this. I forgot that our serial number code was creating a parameter too. Sorry about that, Paul... I made a test plugin with param ID 100 (actually, params 1-249) and it worked. I'll send the plugin to you off-list. I believe that Motion requires that param ID's be in the range 1-9998 inclusive. FCP shouldn't have any restrictions. It looks like ID 100 is bad, maybe used by the input image or something. The SimplePaint example starts at ID 1. Is there a range that's reserved? We don't have a hard limit on number of parameters, although you will probably hit performance problems in our UI with a large number. I just wrote a quick plugin that adds 250 sliders in a loop and it seemed to work. Is it possible that you are using 100 as the ID for two different parameters? Is your 100th parameter a point control? Is there a limit to the number of FxPlug parameters allowed in FCP? I don't recall this being discussed. On the 100th parameter I get this exception: 2009-02-02 15:54:52.706 Final Cut Pro[1189:813] Exception thrown while loading plugin "FxPlugWrapper: 1BF495F8_AC0F_422D_B400_0E91831993A7": -[FxPlugWrapper createInputPortWithArguments:forKey:]: Key "input_100" is already in use by node <FxPlugWrapper "1BF495F8_AC0F_422D_B400_0E91831993A7" = 0x21633FC0 "(null)"> This email sent to pschneider(a)apple.com This email sent to pschneider(a)apple.com This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP parameter count limits?
by Emile Tobenfeld 03 Feb '09

03 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Feb 2, 2009, at 4:43 PM, Paul Schneider wrote: Hi Garrick - Paul On Feb 2, 2009, at 6:37 PM, Garrick Meeker wrote: On Feb 2, 2009, at 4:13 PM, Paul Schneider wrote: Hi Garrick, - Paul On Feb 2, 2009, at 5:58 PM, Garrick Meeker wrote: This is FCP 6.0.5. _______________________________________________ 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/pschneider%40apple.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/pschneider%40apple.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/emilet%40borisfx.com -- Emile Tobenfeld, Ph. D. Video Producer Image Processing Specialist Video for your HEAD! Boris FX http://www.foryourhead.com http://www.borisfx.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… Burned by you rown copy protection -- I think we've all been there before more often than we'd care to admit-:) At 5:08 PM -0800 2/2/09, Garrick Meeker wrote: Okay, ignore all of this. I forgot that our serial number code was creating a parameter too. Sorry about that, Paul... I made a test plugin with param ID 100 (actually, params 1-249) and it worked. I'll send the plugin to you off-list. I believe that Motion requires that param ID's be in the range 1-9998 inclusive. FCP shouldn't have any restrictions. It looks like ID 100 is bad, maybe used by the input image or something. The SimplePaint example starts at ID 1. Is there a range that's reserved? We don't have a hard limit on number of parameters, although you will probably hit performance problems in our UI with a large number. I just wrote a quick plugin that adds 250 sliders in a loop and it seemed to work. Is it possible that you are using 100 as the ID for two different parameters? Is your 100th parameter a point control? Is there a limit to the number of FxPlug parameters allowed in FCP? I don't recall this being discussed. On the 100th parameter I get this exception: 2009-02-02 15:54:52.706 Final Cut Pro[1189:813] Exception thrown while loading plugin "FxPlugWrapper:1BF495F8_AC0F_422D_B400_0E91831993A7": -[FxPlugWrapper createInputPortWithArguments:forKey:]: Key "input_100" is already in use by node <FxPlugWrapper "1BF495F8_AC0F_422D_B400_0E91831993A7" = 0x21633FC0 "(null)"> This email sent to pschneider(a)apple.com This email sent to pschneider(a)apple.com This email sent to emilet(a)borisfx.com "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" -- The Red Queen This email sent to site_archiver(a)lists.apple.com

1 0

Re: FCP parameter count limits?
by Garrick Meeker 03 Feb '09

03 Feb '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Feb 2, 2009, at 4:43 PM, Paul Schneider wrote: Hi Garrick - Paul On Feb 2, 2009, at 6:37 PM, Garrick Meeker wrote: On Feb 2, 2009, at 4:13 PM, Paul Schneider wrote: Hi Garrick, - Paul On Feb 2, 2009, at 5:58 PM, Garrick Meeker wrote: This is FCP 6.0.5. _______________________________________________ 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/pschneider%40apple.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/pschneider%40apple.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… Okay, ignore all of this. I forgot that our serial number code was creating a parameter too. Sorry about that, Paul... I made a test plugin with param ID 100 (actually, params 1-249) and it worked. I'll send the plugin to you off-list. I believe that Motion requires that param ID's be in the range 1-9998 inclusive. FCP shouldn't have any restrictions. It looks like ID 100 is bad, maybe used by the input image or something. The SimplePaint example starts at ID 1. Is there a range that's reserved? We don't have a hard limit on number of parameters, although you will probably hit performance problems in our UI with a large number. I just wrote a quick plugin that adds 250 sliders in a loop and it seemed to work. Is it possible that you are using 100 as the ID for two different parameters? Is your 100th parameter a point control? Is there a limit to the number of FxPlug parameters allowed in FCP? I don't recall this being discussed. On the 100th parameter I get this exception: 2009-02-02 15:54:52.706 Final Cut Pro[1189:813] Exception thrown while loading plugin "FxPlugWrapper: 1BF495F8_AC0F_422D_B400_0E91831993A7": -[FxPlugWrapper createInputPortWithArguments:forKey:]: Key "input_100" is already in use by node <FxPlugWrapper "1BF495F8_AC0F_422D_B400_0E91831993A7" = 0x21633FC0 "(null)"> This email sent to pschneider(a)apple.com This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0