July 2010 - Pro-apps-dev - lists.apple.com

Out of range premultiplied images in FxPlug/FCP
by Eberhard Ammelt 29 Jul '10

29 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hello, we have a problem with some of our OpenGL based fxplug filters. In some cases the rendered image doesn't look as expected where alpha is > 0 and < 1. This problem does only occur with FCP but not with Motion at any bit depth. It seems that the color values of the filter output get out of range when unpremultiplied by FCP internally (?) As Motion seems to handle this, is there a way we could change this behavior in FCP - maybe by changing an OpenGL attribute? Thanks, Eberhard Ammelt - Pixlock _______________________________________________ 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: Setting keyframes in FxPlug
by Garrick Meeker 22 Jul '10

22 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Filed radar #8223125. On Jul 22, 2010, at 10:59 AM, Darrin Cardani wrote: > Please file a request. We have other requests for it already, but more requests usually equals more weight in management's mind. > > Darrin > > On Jul 22, 2010, at 10:54 AM, Garrick Meeker wrote: > >> Then should I file a feature request for an API to modify keyframes, or is this already under consideration? >> >> On Jul 22, 2010, at 10:42 AM, Darrin Cardani wrote: >> >>> In my opinion, Motion's doing the correct thing, and FCP is not. The parameter setting API is not intended to set keyframes. >>> >>> Darrin >>> >>> On Jul 22, 2010, at 10:36 AM, Garrick Meeker wrote: >>> >>>> Another note about keyframes. In FCP, we can have the user set keyframes on some parameters and then calling the set parameter value methods will create new keyframes (current only the current frame due to the bug below). In Motion, these methods don't create new keyframes. We'd have to require the user to manually create keyframes for every frames. Is this a bug? Should Motion behave like FCP? Or do we just need a new interface in the FxPlug API? A new interface would let us skip the step of the user creating the initial keyframes but that's secondary to our issue with Motion. >>>> >>>> On Dec 6, 2009, at 2:43 PM, Paul Schneider wrote: >>>> >>>>> >>>>> Hi Garrick, >>>>> >>>>> This looks like a bug in FCP. Unfortunately, it's still there in version 7. I've filed radar #7447967 to track fixing it. Sorry about that... >>>>> >>>>> - Paul >>>>> >>>>> >>>>> On Dec 5, 2009, at 11:41 PM, Garrick Meeker wrote: >>>>> >>>>>> I know that FxPlug doesn't have an interface for manipulating keyframes, and that the set parameter value methods won't set a keyframe until the user has keyframed that parameter. I can't even get these methods to have any effect for times other than the current one (atTime != currentTime). I'm calling this from the action on a custom parameter, and yes, I'm calling startAction first. >>>>>> >>>>>> I've only tried this in FCP6 as I don't have access to FCP7 yet. Has anyone else tried this? >>>>>> >>>>>> _______________________________________________ >>>>>> 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/dcardani%40apple.com >>>> >>>> This email sent to dcardani(a)apple.com >>> >>> -- >>> 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: Setting keyframes in FxPlug
by Pierre Jasmin 22 Jul '10

22 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Organization: RE:Vision Effects User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6 Then should I file a feature request for an API to modify keyframes, or is this already under consideration? On Jul 22, 2010, at 10:42 AM, Darrin Cardani wrote: In my opinion, Motion's doing the correct thing, and FCP is not. The parameter setting API is not intended to set keyframes. Darrin On Jul 22, 2010, at 10:36 AM, Garrick Meeker wrote: Another note about keyframes. In FCP, we can have the user set keyframes on some parameters and then calling the set parameter value methods will create new keyframes (current only the current frame due to the bug below). In Motion, these methods don't create new keyframes. We'd have to require the user to manually create keyframes for every frames. Is this a bug? Should Motion behave like FCP? Or do we just need a new interface in the FxPlug API? A new interface would let us skip the step of the user creating the initial keyframes but that's secondary to our issue with Motion. On Dec 6, 2009, at 2:43 PM, Paul Schneider wrote: Hi Garrick, This looks like a bug in FCP. Unfortunately, it's still there in version 7. I've filed radar #7447967 to track fixing it. Sorry about that... - Paul On Dec 5, 2009, at 11:41 PM, Garrick Meeker wrote: I know that FxPlug doesn't have an interface for manipulating keyframes, and that the set parameter value methods won't set a keyframe until the user has keyframed that parameter. I can't even get these methods to have any effect for times other than the current one (atTime != currentTime). I'm calling this from the action on a custom parameter, and yes, I'm calling startAction first. I've only tried this in FCP6 as I don't have access to FCP7 yet. Has anyone else tried this? _______________________________________________ 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/dcardani%40apple.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/jasmin%40revisionfx.com This email sent to jasmin(a)revisionfx.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 7/22/2010 10:54 AM, Garrick Meeker wrote: Had my name for it if not already there :) This email sent to pschneider(a)apple.com This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Setting keyframes in FxPlug
by Darrin Cardani 22 Jul '10

22 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Darrin On Jul 22, 2010, at 10:54 AM, Garrick Meeker wrote: On Jul 22, 2010, at 10:42 AM, Darrin Cardani wrote: Darrin On Jul 22, 2010, at 10:36 AM, Garrick Meeker wrote: On Dec 6, 2009, at 2:43 PM, Paul Schneider wrote: Hi Garrick, - Paul On Dec 5, 2009, at 11:41 PM, Garrick Meeker 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/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/dcardani%40apple.com -- 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… Please file a request. We have other requests for it already, but more requests usually equals more weight in management's mind. Then should I file a feature request for an API to modify keyframes, or is this already under consideration? In my opinion, Motion's doing the correct thing, and FCP is not. The parameter setting API is not intended to set keyframes. Another note about keyframes. In FCP, we can have the user set keyframes on some parameters and then calling the set parameter value methods will create new keyframes (current only the current frame due to the bug below). In Motion, these methods don't create new keyframes. We'd have to require the user to manually create keyframes for every frames. Is this a bug? Should Motion behave like FCP? Or do we just need a new interface in the FxPlug API? A new interface would let us skip the step of the user creating the initial keyframes but that's secondary to our issue with Motion. This looks like a bug in FCP. Unfortunately, it's still there in version 7. I've filed radar #7447967 to track fixing it. Sorry about that... I know that FxPlug doesn't have an interface for manipulating keyframes, and that the set parameter value methods won't set a keyframe until the user has keyframed that parameter. I can't even get these methods to have any effect for times other than the current one (atTime != currentTime). I'm calling this from the action on a custom parameter, and yes, I'm calling startAction first. I've only tried this in FCP6 as I don't have access to FCP7 yet. Has anyone else tried this? This email sent to pschneider(a)apple.com This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Setting keyframes in FxPlug
by Garrick Meeker 22 Jul '10

22 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Then should I file a feature request for an API to modify keyframes, or is this already under consideration? On Jul 22, 2010, at 10:42 AM, Darrin Cardani wrote: > In my opinion, Motion's doing the correct thing, and FCP is not. The parameter setting API is not intended to set keyframes. > > Darrin > > On Jul 22, 2010, at 10:36 AM, Garrick Meeker wrote: > >> Another note about keyframes. In FCP, we can have the user set keyframes on some parameters and then calling the set parameter value methods will create new keyframes (current only the current frame due to the bug below). In Motion, these methods don't create new keyframes. We'd have to require the user to manually create keyframes for every frames. Is this a bug? Should Motion behave like FCP? Or do we just need a new interface in the FxPlug API? A new interface would let us skip the step of the user creating the initial keyframes but that's secondary to our issue with Motion. >> >> On Dec 6, 2009, at 2:43 PM, Paul Schneider wrote: >> >>> >>> Hi Garrick, >>> >>> This looks like a bug in FCP. Unfortunately, it's still there in version 7. I've filed radar #7447967 to track fixing it. Sorry about that... >>> >>> - Paul >>> >>> >>> On Dec 5, 2009, at 11:41 PM, Garrick Meeker wrote: >>> >>>> I know that FxPlug doesn't have an interface for manipulating keyframes, and that the set parameter value methods won't set a keyframe until the user has keyframed that parameter. I can't even get these methods to have any effect for times other than the current one (atTime != currentTime). I'm calling this from the action on a custom parameter, and yes, I'm calling startAction first. >>>> >>>> I've only tried this in FCP6 as I don't have access to FCP7 yet. Has anyone else tried this? >>>> >>>> _______________________________________________ >>>> 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/dcardani%40apple.com >> >> This email sent to 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: Setting keyframes in FxPlug
by Darrin Cardani 22 Jul '10

22 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Darrin On Jul 22, 2010, at 10:36 AM, Garrick Meeker wrote: On Dec 6, 2009, at 2:43 PM, Paul Schneider wrote: Hi Garrick, - Paul On Dec 5, 2009, at 11:41 PM, Garrick Meeker 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/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/dcardani%40apple.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… In my opinion, Motion's doing the correct thing, and FCP is not. The parameter setting API is not intended to set keyframes. Another note about keyframes. In FCP, we can have the user set keyframes on some parameters and then calling the set parameter value methods will create new keyframes (current only the current frame due to the bug below). In Motion, these methods don't create new keyframes. We'd have to require the user to manually create keyframes for every frames. Is this a bug? Should Motion behave like FCP? Or do we just need a new interface in the FxPlug API? A new interface would let us skip the step of the user creating the initial keyframes but that's secondary to our issue with Motion. This looks like a bug in FCP. Unfortunately, it's still there in version 7. I've filed radar #7447967 to track fixing it. Sorry about that... I know that FxPlug doesn't have an interface for manipulating keyframes, and that the set parameter value methods won't set a keyframe until the user has keyframed that parameter. I can't even get these methods to have any effect for times other than the current one (atTime != currentTime). I'm calling this from the action on a custom parameter, and yes, I'm calling startAction first. I've only tried this in FCP6 as I don't have access to FCP7 yet. Has anyone else tried this? This email sent to pschneider(a)apple.com This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Setting keyframes in FxPlug
by Garrick Meeker 22 Jul '10

22 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Another note about keyframes. In FCP, we can have the user set keyframes on some parameters and then calling the set parameter value methods will create new keyframes (current only the current frame due to the bug below). In Motion, these methods don't create new keyframes. We'd have to require the user to manually create keyframes for every frames. Is this a bug? Should Motion behave like FCP? Or do we just need a new interface in the FxPlug API? A new interface would let us skip the step of the user creating the initial keyframes but that's secondary to our issue with Motion. On Dec 6, 2009, at 2:43 PM, Paul Schneider wrote: > > Hi Garrick, > > This looks like a bug in FCP. Unfortunately, it's still there in version 7. I've filed radar #7447967 to track fixing it. Sorry about that... > > - Paul > > > On Dec 5, 2009, at 11:41 PM, Garrick Meeker wrote: > >> I know that FxPlug doesn't have an interface for manipulating keyframes, and that the set parameter value methods won't set a keyframe until the user has keyframed that parameter. I can't even get these methods to have any effect for times other than the current one (atTime != currentTime). I'm calling this from the action on a custom parameter, and yes, I'm calling startAction first. >> >> I've only tried this in FCP6 as I don't have access to FCP7 yet. Has anyone else tried this? >> >> _______________________________________________ >> 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/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Final Cut 6 and the Nvidia 9400
by Paul Schneider 19 Jul '10

19 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Brad, > The blacks in the being processed wrong which is causing my Keying plug in to clip the black region. Do you mean that the superblacks are lost? What format (codec) is the footage? What format is your plugin rendering in? (RGB, R408, r4fl)? - Paul On Jul 16, 2010, at 4:58 PM, Brad Wright wrote: > Does anyone know if there's a known problem with the Nvidia 9400M graphics card and Final Cut 6? I've got a customer who is seeing what appears to be a color conversion problem. The blacks in the being processed wrong which is causing my Keying plug in to clip the black region. If the customer brings up the level of the blacks through color correction right before the keyer, the problem goes away. I've tried same exact settings and footage on my ATI 4870 Graphics card and it doesn't happen. I've had no other reports of this problem by any other customers, so it appear to be just this particular system. All the keying is being done on the GPU. > > Brad Wright > _______________________________________________ > 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/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Final Cut 6 and the Nvidia 9400
by Brad Wright 16 Jul '10

16 Jul '10

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Brad Wright _______________________________________________ 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… Does anyone know if there's a known problem with the Nvidia 9400M graphics card and Final Cut 6? I've got a customer who is seeing what appears to be a color conversion problem. The blacks in the being processed wrong which is causing my Keying plug in to clip the black region. If the customer brings up the level of the blacks through color correction right before the keyer, the problem goes away. I've tried same exact settings and footage on my ATI 4870 Graphics card and it doesn't happen. I've had no other reports of this problem by any other customers, so it appear to be just this particular system. All the keying is being done on the GPU. This email sent to site_archiver(a)lists.apple.com

1 0

Re: 3rd party download pages
by Jon Chappell 14 Jul '10

14 Jul '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=default; d=digitalrebellion.com; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject:To:Cc:Content-Type:X-Identified-User; b=xlK8AG5qv4PXs4W3MYx+CalHYtmtic6zI5W4Q2Lh5paFJfPAmHUpLFMjTwpO7kwCUJGtYp+mtPAIxYzM2LkVoIDlzuwb7JP97P3uMNrozvJqjfl0EQESdhq6WC5VZAk2; _______________________________________________ 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