November 2008 - Pro-apps-dev

Re: Quartz vs Motion float pixels
by Darrin Cardani 18 Nov '08

18 Nov '08

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

formatsFloatRGBABitmapsAsARGB?
by Stonewall Ballard 18 Nov '08

18 Nov '08

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=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer:sender; bh=PuBcNCgYMXnaQaaSb4vMnEmwgY3IV2a2GuWWs9TzuLQ=; b=bQO4mz7TuAUH2/ilGrkOlpD7T7O231wIyzArFquBx4hIPVaM1phZ0DWr4Es3q4ELPd RWQ1q0QyIX5JI9zw97pejCmSns/kseHkfyhMGyX42RwT4EvjUwmtQy0yeHAcH4lR3cRs 4XT7hNqYVCZEw7cC/7U9YZNU0tN/UPnuHs10Y= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer:sender; b=VEAXYICxyRECfFPaZfPOp/0OOxkGAp22htJQgF+IubPWWOjBs5M8IqCL51XwLW8vhi LDZb1RKWwwqfl4Hhk+9hPSLHYAnyoZ5BlLaO/Wsutv5TZoJNU/T7EG1ZvX2ZFfr9bPWw gCunFe+REprWW0T+vnqPVp6S1tfHguv+bbeMw= Any explanations would be greatly appreciated. - Stoney -- Stonewall Ballard stoney(a)sb.org http://stoney.sb.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… What does it mean for Motion 3 to return YES for [_hostCapabilities formatsFloatRGBABitmapsAsARGB]? That makes no sense to me. I thought this was supposed to return NO for hosts that labeled their float bitmaps correctly, which Motion 3 apparently does. This section from the SDK overview is ambiguous, since it doesn't say how Motion corrected this problem: Float Images pixelFormat Correction Motion 2.1 ordered pixel components RGBA in floating-point images, but the -pixelFormat method returned ARGB. Motion 3 corrects this problem. You can determine whether floating-point images are mislabeled by querying [FxHostCapabilities formatsFloatRGBABitmapsAsARGB]. I assume that Motion 3 corrected this problem by changing the component order to ARGB, since that's what I'm seeing in the FxBitmaps, but I don't see any mislabeling. As in my previous message, it seems very odd to me that Motion would switch from RGBA to ARGB float pixels, especially since Quartz doesn't support float ARGB. This email sent to site_archiver(a)lists.apple.com

1 0

Quartz vs Motion float pixels
by Stonewall Ballard 18 Nov '08

18 Nov '08

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=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer:sender; bh=Qd4vSgL1xk2OxdAYOq4XMI+jrqe6LwnbyLWnaA9I5wA=; b=Mh3hdJjVc0KJen+G3+MjPQKsYDVXEWqd2Dms9KFhNF5JJAeLLwcXMMTbHsUx5Ubo7y 6oYIIOnQAldCBP9xLyXcUjg+hZC1mwyy9fMsS+E3uHtve2xkpnta7wAPvIOp1zg7SONb Q2IHRNP2qMiFNK6XKo40YCTkdbX98+Pv8C0e0= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer:sender; b=i0yT/FSh09PZxa4wpggGwnEkqdEqNx3knsvSNO7wafKN16Y+kva3tYKjnskt6v39rm 0oRSEZlhB4EoVGmPh1VRxgXHJo9wpQN32mwpfUS1CwQujep8dvae1Kury3eUFtgri03Z PrUY26XLbaRg8ouQVv6EEB3GZnu67ZbU5Z+jY= Or am I missing something? - Stoney -- Stonewall Ballard stoney(a)sb.org http://stoney.sb.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… How did it happen that Motion's ARGB 32-bit float pixels are a format that Quartz won't process? I'm more surprised that Quartz requires 32- bit float pixels to be in RGBA format, but this precludes using Quartz to process and draw on Motion's float FxBitmaps. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Plugin not receiving -dealloc call at the expected time
by Darrin Cardani 17 Nov '08

17 Nov '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Nov 16, 2008, at 8:50 AM, David Yamnitsky wrote: 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… Hi everyone, I'm building a plugin which opens a separate window. It all works fine, except I'm having the problem that when the effect is deleted, the window remains open. Any attempt to manipulate something in the window which makes an FxPlug API call crashes the app. I consulted the FloatingWindow example code, which just releases the window when -dealloc is sent to the plugin object, which is the same thing I'm doing. I did some digging, and found that the FloatingWindow example receives the -dealloc call right when the effect is deleted, but my plugin receives that call rather spontaneously, either when the app is quit or when another effect is applied. Why is this? Could it be because my plugin is dynamically registered? (that seems to be the only obvious difference between the FloatingWindow example and my code). David, One thing to look out for is make sure none of your objects are retaining your plugin instance. If you've retained it, then when the host app releases it, it will still have at least 1 reference and won't be deallocated. This email sent to site_archiver(a)lists.apple.com

1 0

Re: logic-pro plugins
by Paul Schneider 17 Nov '08

17 Nov '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Daniel, - Paul On Nov 16, 2008, at 4:02 PM, Dan Birns wrote: --Daniel _______________________________________________ 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… this list is for all pro apps; it's just that some of them get more traffic than others. I've forwarded your question to the Logic team. It might help if you could be more specific, though. What exactly do you want to do, and why won't the AudioUnit API meet your needs? Is there such a thing as logic-pro plugins, aside from AudioUnits? Any information about it. Is this thread only for video? This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Plugin not receiving -dealloc call at the expected time
by Paul Schneider 17 Nov '08

17 Nov '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi David, I'll assume that you see this problem in FCP and not Motion? - Paul On Nov 16, 2008, at 10:50 AM, David Yamnitsky wrote: Thanks in advance, David _______________________________________________ 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… I believe that when an effect is "deleted" in FCP, it is actually transferred to the undo stack, where it hangs out until either a) the user hits undo to bring it back, or b) the "delete effect" action falls off the stack. The second one can happen if the stack gets full (I think by default, we cap it at 20 actions, but you can adjust this in the preferences), or if the user does something to take undo down a different branch (like adding a different effect). This would explain why you don't get a -dealloc message when you delete the effect, and why you receive -dealloc at a seemingly random time later. I don't know why your plugin behaves differently from the example in this respect; I'd actually expect the example to have the same problem. I can investigate that. Without a crash report, I can't speculate on why you are crashing, but it sounds like you're manipulating the parameters of an effect which only lives on the undo stack (isn't applied to any clip or sequence), and I wouldn't be surprised if that confused Final Cut. We won't send you a separate "the effect has been deleted, as far as the user's concerned" message, so there's not much you can do to trap this case. We should probably dealloc FxPlugs when they're removed from the clip, and re-alloc them if that removal is undone. Please file an enhancement request at bugreport.apple.com if you'd like that behavior. In the meantime, I think you will have some problems trying to manage a floating window from an FxPlug in Final Cut. I know that there's a problem where FCP won't refresh the canvas if you change a parameter which isn't loaded in the viewer's control tab, and it sounds like you've found a second issue. I'd recommend sticking to a modal UI for now. Hi everyone, I'm building a plugin which opens a separate window. It all works fine, except I'm having the problem that when the effect is deleted, the window remains open. Any attempt to manipulate something in the window which makes an FxPlug API call crashes the app. I consulted the FloatingWindow example code, which just releases the window when -dealloc is sent to the plugin object, which is the same thing I'm doing. I did some digging, and found that the FloatingWindow example receives the -dealloc call right when the effect is deleted, but my plugin receives that call rather spontaneously, either when the app is quit or when another effect is applied. Why is this? Could it be because my plugin is dynamically registered? (that seems to be the only obvious difference between the FloatingWindow example and my code). This email sent to pschneider(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Plugin not receiving -dealloc call at the expected time
by Steve Christensen 17 Nov '08

17 Nov '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Nov 16, 2008, at 6:46 PM, David Yamnitsky wrote: On Nov 16, 2008, at 9:32 PM, Steve Christensen wrote: On Nov 16, 2008, at 8:50 AM, David Yamnitsky wrote: Yeah, that's exactly what I did. FxPlug isn't deallocating 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/site_archiver%40lists.a… I'm building a plugin which opens a separate window. It all works fine, except I'm having the problem that when the effect is deleted, the window remains open. Any attempt to manipulate something in the window which makes an FxPlug API call crashes the app. I consulted the FloatingWindow example code, which just releases the window when -dealloc is sent to the plugin object, which is the same thing I'm doing. I did some digging, and found that the FloatingWindow example receives the -dealloc call right when the effect is deleted, but my plugin receives that call rather spontaneously, either when the app is quit or when another effect is applied. Why is this? Could it be because my plugin is dynamically registered? (that seems to be the only obvious difference between the FloatingWindow example and my code). If you are releasing the window in your dealloc method then I don't know why it should make any difference when that happens. If the window is still open then perhaps you're plugin's effect class instance hasn't actually been dealloc'd. Did you check for that (either in GDB or by adding some NSLog() calls to your code)? I suppose there could be some differences in the way statically and dynamically created classes are handled that might keep a class instance around in the dynamic case. Perhaps FCP has an optimization for doing so, figuring that it's more expensive (time- wise) to create dynamic class instances. Just a guess. I don't know of anyplace that says it's guaranteed that your class instance will be dealloc'd in a particular fashion so it's probably not wise to make any assumptions on your own. Yeah, I agree. If that is the case, do you know of any workaround that would result in being notified when the effect is deleted? Otherwise the window I create lingers afterwards. Nope, the effect is only called when the host app wants it to do something. To my knowledge there isn't any other notification of when the effect is deleted vs dealloc'd. As for the crash in your window handling code, do you have more details about what's crashing? The crash may not have anything to do with the above issue. The crash isn't really important to this issue. It's caused by an attempt by changes in the window to manipulate FxPlug parameters that don't exist because the effect has been deleted. If the window is released, this won't happen. Well, one of the hazards of having a modeless window associated with a plugin is that the host app creates and deletes instances of your plugin class as they're needed. For example, if you drag your transition class to two points on the timeline, there will be two instances of your class. Otherwise you wouldn't be able to use different parameter settings in each case. This also brings up a usability issue WRT the window: how do you specify which class instance the parameters in the window are referring to? Typically you would use a mix of standard and custom controls as part of the standard plugin UI. If you want to do something more involved, a modal window works better since (a) the parameter changes can only apply to a specific effect instance; and (b) the effect instance can't be dealloc'd before the window is released. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Plugin not receiving -dealloc call at the expected time
by David Yamnitsky 17 Nov '08

17 Nov '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Nov 16, 2008, at 9:32 PM, Steve Christensen wrote: Yeah, that's exactly what I did. FxPlug isn't deallocating steve On Nov 16, 2008, at 8:50 AM, David Yamnitsky 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… If you are releasing the window in your dealloc method then I don't know why it should make any difference when that happens. If the window is still open then perhaps you're plugin's effect class instance hasn't actually been dealloc'd. Did you check for that (either in GDB or by adding some NSLog() calls to your code)? I suppose there could be some differences in the way statically and dynamically created classes are handled that might keep a class instance around in the dynamic case. Perhaps FCP has an optimization for doing so, figuring that it's more expensive (time-wise) to create dynamic class instances. Just a guess. I don't know of anyplace that says it's guaranteed that your class instance will be dealloc'd in a particular fashion so it's probably not wise to make any assumptions on your own. Yeah, I agree. If that is the case, do you know of any workaround that would result in being notified when the effect is deleted? Otherwise the window I create lingers afterwards. As for the crash in your window handling code, do you have more details about what's crashing? The crash may not have anything to do with the above issue. The crash isn't really important to this issue. It's caused by an attempt by changes in the window to manipulate FxPlug parameters that don't exist because the effect has been deleted. If the window is released, this won't happen. I'm building a plugin which opens a separate window. It all works fine, except I'm having the problem that when the effect is deleted, the window remains open. Any attempt to manipulate something in the window which makes an FxPlug API call crashes the app. I consulted the FloatingWindow example code, which just releases the window when -dealloc is sent to the plugin object, which is the same thing I'm doing. I did some digging, and found that the FloatingWindow example receives the -dealloc call right when the effect is deleted, but my plugin receives that call rather spontaneously, either when the app is quit or when another effect is applied. Why is this? Could it be because my plugin is dynamically registered? (that seems to be the only obvious difference between the FloatingWindow example and my code). This email sent to site_archiver(a)lists.apple.com

1 0

Re: Plugin not receiving -dealloc call at the expected time
by Steve Christensen 17 Nov '08

17 Nov '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com steve On Nov 16, 2008, at 8:50 AM, David Yamnitsky 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… If you are releasing the window in your dealloc method then I don't know why it should make any difference when that happens. If the window is still open then perhaps you're plugin's effect class instance hasn't actually been dealloc'd. Did you check for that (either in GDB or by adding some NSLog() calls to your code)? I suppose there could be some differences in the way statically and dynamically created classes are handled that might keep a class instance around in the dynamic case. Perhaps FCP has an optimization for doing so, figuring that it's more expensive (time-wise) to create dynamic class instances. Just a guess. I don't know of anyplace that says it's guaranteed that your class instance will be dealloc'd in a particular fashion so it's probably not wise to make any assumptions on your own. As for the crash in your window handling code, do you have more details about what's crashing? The crash may not have anything to do with the above issue. I'm building a plugin which opens a separate window. It all works fine, except I'm having the problem that when the effect is deleted, the window remains open. Any attempt to manipulate something in the window which makes an FxPlug API call crashes the app. I consulted the FloatingWindow example code, which just releases the window when -dealloc is sent to the plugin object, which is the same thing I'm doing. I did some digging, and found that the FloatingWindow example receives the -dealloc call right when the effect is deleted, but my plugin receives that call rather spontaneously, either when the app is quit or when another effect is applied. Why is this? Could it be because my plugin is dynamically registered? (that seems to be the only obvious difference between the FloatingWindow example and my code). This email sent to site_archiver(a)lists.apple.com

1 0

logic-pro plugins
by Dan Birns 16 Nov '08

16 Nov '08

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=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer; bh=TS9Sh5GrfhaUpjMRUBvEkWFDwSeFU9VNejWUW1kzSrU=; b=qeIY8QIK3WWFfaUUDzjQBiINylQ+nKTIkefFqO1pUd5eD6rmu8yvq8V1TXiGyrxkdH TOJdQ8MG/fLGJMcLZuixissy5GwdDliTBAVbNIi53qrjoy4smgLKY/3zTQdDyly7CbFW jvuPetXP27pgCrTG/L8tjgupPvZoWVgxFYqvY= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=tyTMf0E9sblLJA+Zd1XJJx6DTnx6yFgBE7QAawKqOYrxzoKAvcVEonrLEz/z6Nwb+y pgq6JiAl2nLsUeEwxJn+jtcFD1jOLrt4JYeu2YbzS/5tCLjtx7rEVR9cH4wS8oS4WXvn q6mVCaMUweOMrRcXMlnLSdWSD/GH7hI5gnTkw= --Daniel _______________________________________________ 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 such a thing as logic-pro plugins, aside from AudioUnits? Any information about it. Is this thread only for video? This email sent to site_archiver(a)lists.apple.com

1 0