November 2007 - Pro-apps-dev

Forcing redraw on custom param pushbutton in FCP FxPlug plug-in whenever the frame is changed
by Benjamin Kent 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.0 (Macintosh/20070326) Hi, Thanks Ben _______________________________________________ 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… I have a custom param which is masquerading as an animatable bool toggle - i.e. the param is a toggle push button and it's value is changed when my plug-in is rendered such that it reflects the value of an internal data structure cached in the plug-in. This works fine, except that if the frame is cached, the push button doesn't get updated. For example, the default value of the push button is checked - the user unchecks it and it sets a keyframe of value 0 in the internal data structure. The user goes to the next frame and the push button returns to checked (as the internal data structure value at this frame is still 1). Then, if you go back to the previous frame, the push button stays checked, as the plug-in never renders and sets the value of the push button. Now I realise I don't want to stop the caching, as a user would never be able to render and play a sequence - so is it possible to force the push button to have its drawRect function called whenever the frame is changed - that way I could query the plug-in at this point as to the value of the internal data structure? This email sent to site_archiver(a)lists.apple.com

1 0

Re: KickRender and access to retrieval/setting api
by Paul Schneider 06 Nov '07

06 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Gary, are you seeing this in Final Cut, or in Motion? Which version? - Paul On Nov 6, 2007, at 6:57 PM, Gary Fielke wrote: Hi all, The KickRender sample FxPlug posted here doesn't work for me. Is anyone else seeing this? Thanks Gary (10.4.10, Powerbook G4 1.67, Motion 3.0.1, FCP 6.0.1) _______________________________________________ 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 turns out that in the -(void)kickRender:(id)sender method, both the getApi object (retrieved using [_apiManager apiForProtocol:@protocol(FxParameterRetrievalAPI)]) and the setApi object (from FxParameterSettingAPI) are NULL. Consequently, the rendering isn't being kicked. The current plugin I'm working on also needs access (which it doesn't get) to the retrieval and setting API in the action method of a button used in a custom view. _______________________________________________ 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 This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

KickRender and access to retrieval/setting api
by Gary Fielke 06 Nov '07

06 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi all, The KickRender sample FxPlug posted here doesn't work for me. Is anyone else seeing this? Thanks Gary (10.4.10, Powerbook G4 1.67, Motion 3.0.1, FCP 6.0.1) _______________________________________________ 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 turns out that in the -(void)kickRender:(id)sender method, both the getApi object (retrieved using [_apiManager apiForProtocol:@protocol(FxParameterRetrievalAPI)]) and the setApi object (from FxParameterSettingAPI) are NULL. Consequently, the rendering isn't being kicked. The current plugin I'm working on also needs access (which it doesn't get) to the retrieval and setting API in the action method of a button used in a custom view. This email sent to site_archiver(a)lists.apple.com

1 0

Re: pixelAspect for fielded images in FxPlug plug-ins on FCP
by Paul Schneider 06 Nov '07

06 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Ben, Thanks, - Paul On Nov 6, 2007, at 9:36 AM, Benjamin Kent wrote: Hi Thanks _______________________________________________ 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… yes, this is expected. It should be explicitly mentioned in the "FCP FxPlug Rendering Paths" document; let me know if it isn't and I'll fix that up. It appears that when calling [outputImage pixelAspect] in renderOutput, if the image is fielded and therefore half height, the pixelAspect is half what I'd expect. Now obviously there's an easy way round this - I just want to check if this is expected behaviour? Ben _______________________________________________ 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 This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

pixelAspect for fielded images in FxPlug plug-ins on FCP
by Benjamin Kent 06 Nov '07

06 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.0 (Macintosh/20070326) Hi Thanks Ben _______________________________________________ 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 appears that when calling [outputImage pixelAspect] in renderOutput, if the image is fielded and therefore half height, the pixelAspect is half what I'd expect. Now obviously there's an easy way round this - I just want to check if this is expected behaviour? This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug plugins not loading on FCP
by Paul Schneider 05 Nov '07

05 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thanks, Patrick and Gabe. Thanks! - Paul On Nov 5, 2007, at 1:12 PM, Patrick Sheffield wrote: Patrick On Nov 5, 2007, at 10:01 AM, Paul Schneider wrote: Hi, Steve, - Paul On Nov 5, 2007, at 12:19 PM, Steve Christensen wrote: Anything else you can think of for me to try? steve On Nov 5, 2007, at 7:54 AM, Paul Schneider wrote: Hi, Steve, Hope that helps, - Paul On Nov 2, 2007, at 10:17 PM, Steve Christensen wrote: Plugins are in ~/Library/Plug-Ins/FxPlug/ on both computers. Bad system: Intel iMac running 10.4.10. Good system Intel MacBook Pro running either 10.4.10 or 10.5. Any thoughts from the FCP team or other knowledgeable folks? _______________________________________________ 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 sounds like we have a more serious problem than I'd thought. I was under the impression that this only affected systems that had once been running our beta software. I'm escalating this now. If any of you are able to get system profiles from affected machines, send them my way. I should point out that while I participated in the beta, AFTER FCS2's release I bought a new machine and did a clean install of FCS2 and I had this problem (despite the fact that beta libraries were never installed on this machine, nor did I migrate my user account to it) - which was resolved by following instructions like yours... CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. the problem is that you have an early beta of some shared libraries, but the updater thinks that you have the latest shipping versions, because it is looking at PluginManager's version number. *Lowering* the version number from 1.7.1 to 1.7 will convince the ProAppsUpdater installer to update you to the shipping version of these libraries, which Final Cut needs for FxPlug hosting. These libraries live in /Library/Frameworks, so you probably didn't clean them out when you trashed the apps and reinstalled. This was caused by a bug in our installer process; we've fixed things so that it shouldn't happen again. But those who participated in the 6.0.1 beta may need to do this extra step. Please try the steps in my earlier message and let me know if they work. Thanks! CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. Software Update is showing that I have all updates to date, including FCP Update 6.0.1 and Motion Update 3.0.1. (Are they part of the PAU2007-01 update?) When I did the ProApps reinstall from the DVD, I trashed the applications as well as the various receipt files to make sure updates would be reapplied. we've seen problems like this when upgrading an earlier beta of Final Cut 6.0.1 to a later beta, or to the released version of 6.0.1. If your "bad system" ever had one of our betas on it, this could be the culprit. If you are in this situation, we have a pretty ugly workaround to get you out of it: 1. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/Info.plist and change the value of CFBundleShortVersionString to be 1.7. 2. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/version.plist and change the value of CFBundleShortVersionString to be 1.7. 3. Run Software Update and install PAU2007-01. I have a weird situation here. On one computer, several plugins I've written plus some other third party plugins aren't showing up in FCP, but they are showing up in Motion. No console messages, either. I've even trashed all the ProApp applications and reinstalled from the DVD with no difference. They -are- showing up in both Motion and FCP running on a different computer. steve _______________________________________________ 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.net This email sent to psheffield(a)earthlink.net This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug plugins not loading on FCP
by Steve Christensen 05 Nov '07

05 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com That seems to have done it. Thanks, Paul. On Nov 5, 2007, at 10:01 AM, Paul Schneider wrote: - Paul On Nov 5, 2007, at 12:19 PM, Steve Christensen wrote: Anything else you can think of for me to try? steve On Nov 5, 2007, at 7:54 AM, Paul Schneider wrote: Hi, Steve, Hope that helps, - Paul On Nov 2, 2007, at 10:17 PM, Steve Christensen wrote: Plugins are in ~/Library/Plug-Ins/FxPlug/ on both computers. Bad system: Intel iMac running 10.4.10. Good system Intel MacBook Pro running either 10.4.10 or 10.5. Any thoughts from the FCP team or other knowledgeable folks? _______________________________________________ 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… CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. the problem is that you have an early beta of some shared libraries, but the updater thinks that you have the latest shipping versions, because it is looking at PluginManager's version number. *Lowering* the version number from 1.7.1 to 1.7 will convince the ProAppsUpdater installer to update you to the shipping version of these libraries, which Final Cut needs for FxPlug hosting. These libraries live in /Library/Frameworks, so you probably didn't clean them out when you trashed the apps and reinstalled. This was caused by a bug in our installer process; we've fixed things so that it shouldn't happen again. But those who participated in the 6.0.1 beta may need to do this extra step. Please try the steps in my earlier message and let me know if they work. Thanks! CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. Software Update is showing that I have all updates to date, including FCP Update 6.0.1 and Motion Update 3.0.1. (Are they part of the PAU2007-01 update?) When I did the ProApps reinstall from the DVD, I trashed the applications as well as the various receipt files to make sure updates would be reapplied. we've seen problems like this when upgrading an earlier beta of Final Cut 6.0.1 to a later beta, or to the released version of 6.0.1. If your "bad system" ever had one of our betas on it, this could be the culprit. If you are in this situation, we have a pretty ugly workaround to get you out of it: 1. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/Info.plist and change the value of CFBundleShortVersionString to be 1.7. 2. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/version.plist and change the value of CFBundleShortVersionString to be 1.7. 3. Run Software Update and install PAU2007-01. I have a weird situation here. On one computer, several plugins I've written plus some other third party plugins aren't showing up in FCP, but they are showing up in Motion. No console messages, either. I've even trashed all the ProApp applications and reinstalled from the DVD with no difference. They -are- showing up in both Motion and FCP running on a different computer. steve This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug plugins not loading on FCP
by Patrick Sheffield 05 Nov '07

05 Nov '07

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=DNNwE0ljLYG7Xe0LaG3a49LfEjUpY3Bh5f8ASPq5LDBWeHFHSRPLEx93dhbibpR/; h=Received:In-Reply-To:References:Mime-Version:Content-Type:Message-Id:Cc:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer:X-ELNK-Trace:X-Originating-IP; Patrick On Nov 5, 2007, at 10:01 AM, Paul Schneider wrote: Hi, Steve, - Paul On Nov 5, 2007, at 12:19 PM, Steve Christensen wrote: Anything else you can think of for me to try? steve On Nov 5, 2007, at 7:54 AM, Paul Schneider wrote: Hi, Steve, Hope that helps, - Paul On Nov 2, 2007, at 10:17 PM, Steve Christensen wrote: Plugins are in ~/Library/Plug-Ins/FxPlug/ on both computers. Bad system: Intel iMac running 10.4.10. Good system Intel MacBook Pro running either 10.4.10 or 10.5. Any thoughts from the FCP team or other knowledgeable folks? _______________________________________________ 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… I should point out that while I participated in the beta, AFTER FCS2's release I bought a new machine and did a clean install of FCS2 and I had this problem (despite the fact that beta libraries were never installed on this machine, nor did I migrate my user account to it) - which was resolved by following instructions like yours... CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. the problem is that you have an early beta of some shared libraries, but the updater thinks that you have the latest shipping versions, because it is looking at PluginManager's version number. *Lowering* the version number from 1.7.1 to 1.7 will convince the ProAppsUpdater installer to update you to the shipping version of these libraries, which Final Cut needs for FxPlug hosting. These libraries live in /Library/Frameworks, so you probably didn't clean them out when you trashed the apps and reinstalled. This was caused by a bug in our installer process; we've fixed things so that it shouldn't happen again. But those who participated in the 6.0.1 beta may need to do this extra step. Please try the steps in my earlier message and let me know if they work. Thanks! CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. Software Update is showing that I have all updates to date, including FCP Update 6.0.1 and Motion Update 3.0.1. (Are they part of the PAU2007-01 update?) When I did the ProApps reinstall from the DVD, I trashed the applications as well as the various receipt files to make sure updates would be reapplied. we've seen problems like this when upgrading an earlier beta of Final Cut 6.0.1 to a later beta, or to the released version of 6.0.1. If your "bad system" ever had one of our betas on it, this could be the culprit. If you are in this situation, we have a pretty ugly workaround to get you out of it: 1. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/Info.plist and change the value of CFBundleShortVersionString to be 1.7. 2. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/version.plist and change the value of CFBundleShortVersionString to be 1.7. 3. Run Software Update and install PAU2007-01. I have a weird situation here. On one computer, several plugins I've written plus some other third party plugins aren't showing up in FCP, but they are showing up in Motion. No console messages, either. I've even trashed all the ProApp applications and reinstalled from the DVD with no difference. They -are- showing up in both Motion and FCP running on a different computer. steve _______________________________________________ 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.net This email sent to psheffield(a)earthlink.net This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug plugins not loading on FCP
by Paul Schneider 05 Nov '07

05 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, Steve, - Paul On Nov 5, 2007, at 12:19 PM, Steve Christensen wrote: Anything else you can think of for me to try? steve On Nov 5, 2007, at 7:54 AM, Paul Schneider wrote: Hi, Steve, Hope that helps, - Paul On Nov 2, 2007, at 10:17 PM, Steve Christensen wrote: Plugins are in ~/Library/Plug-Ins/FxPlug/ on both computers. Bad system: Intel iMac running 10.4.10. Good system Intel MacBook Pro running either 10.4.10 or 10.5. Any thoughts from the FCP team or other knowledgeable folks? _______________________________________________ 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… CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. the problem is that you have an early beta of some shared libraries, but the updater thinks that you have the latest shipping versions, because it is looking at PluginManager's version number. *Lowering* the version number from 1.7.1 to 1.7 will convince the ProAppsUpdater installer to update you to the shipping version of these libraries, which Final Cut needs for FxPlug hosting. These libraries live in /Library/Frameworks, so you probably didn't clean them out when you trashed the apps and reinstalled. This was caused by a bug in our installer process; we've fixed things so that it shouldn't happen again. But those who participated in the 6.0.1 beta may need to do this extra step. Please try the steps in my earlier message and let me know if they work. Thanks! CFBundleShortVersionString is set to 1.7.1 in both the framework's Info.plist and version.plist files. And isn't the PluginManager framework responsible for actually loading the plugins? If so I would expect that Motion would be seeing the same problems. Software Update is showing that I have all updates to date, including FCP Update 6.0.1 and Motion Update 3.0.1. (Are they part of the PAU2007-01 update?) When I did the ProApps reinstall from the DVD, I trashed the applications as well as the various receipt files to make sure updates would be reapplied. we've seen problems like this when upgrading an earlier beta of Final Cut 6.0.1 to a later beta, or to the released version of 6.0.1. If your "bad system" ever had one of our betas on it, this could be the culprit. If you are in this situation, we have a pretty ugly workaround to get you out of it: 1. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/Info.plist and change the value of CFBundleShortVersionString to be 1.7. 2. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/version.plist and change the value of CFBundleShortVersionString to be 1.7. 3. Run Software Update and install PAU2007-01. I have a weird situation here. On one computer, several plugins I've written plus some other third party plugins aren't showing up in FCP, but they are showing up in Motion. No console messages, either. I've even trashed all the ProApp applications and reinstalled from the DVD with no difference. They -are- showing up in both Motion and FCP running on a different computer. steve This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug plugins not loading on FCP
by Gabriele de Simone 05 Nov '07

05 Nov '07

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi everyone, Gabe On Nov 5, 2007, at 12:27 PM, Kristian Harms wrote: Hi Paul, Steve and list, But your sollution worked brilliantly for me, Paul. Thanks so much! Regards, Kristian Harms Plugins are in ~/Library/Plug-Ins/FxPlug/ on both computers. Bad system: Intel iMac running 10.4.10. Good system Intel MacBook Pro running either 10.4.10 or 10.5. Any thoughts from the FCP team or other knowledgeable folks? steve _______________________________________________ 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/kha%40vizrt.com This email sent to kha(a)vizrt.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… We have a fairly large number of users who have never touched or seen an FCP beta who report the exact same problem (plug-ins go missing in FCP, they are still there in Motion). Something, somewhere must be broken (who needs more detail than that? :-)) in the way the SU process works, because it started happening only with the latest round of FCS2 updates. So this is definitely affecting more than just developers. Let me briefly add that I have been having identical issues as those that Steve describes, on two of our development machines, and I was about to ask the list what to do when Steve beat me to it :-) The plugin we're developing stopped showing up, whereupon I tried some other plugins: The sample plugins as well as some that were freely downloadable from the net. None showed up. Steve, I changed the two fields from 1.7.1 to 1.7, ran the update, which then changed the fields back to 1.7.1, and FCP now works with the various plugins. Paul Schneider skrev: Hi, Steve, we've seen problems like this when upgrading an earlier beta of Final Cut 6.0.1 to a later beta, or to the released version of 6.0.1. If your "bad system" ever had one of our betas on it, this could be the culprit. If you are in this situation, we have a pretty ugly workaround to get you out of it: 1. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/Info.plist and change the value of CFBundleShortVersionString to be 1.7. 2. Edit the file /Library/Frameworks/PluginManager.framework/ Resources/version.plist and change the value of CFBundleShortVersionString to be 1.7. 3. Run Software Update and install PAU2007-01. Hope that helps, - Paul On Nov 2, 2007, at 10:17 PM, Steve Christensen wrote: I have a weird situation here. On one computer, several plugins I've written plus some other third party plugins aren't showing up in FCP, but they are showing up in Motion. No console messages, either. I've even trashed all the ProApp applications and reinstalled from the DVD with no difference. They -are- showing up in both Motion and FCP running on a different computer. _______________________________________________ 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 This email sent to pschneider(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/gds% 40noiseindustries.com This email sent to gds(a)noiseindustries.com This email sent to site_archiver(a)lists.apple.com

1 0