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

Re: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
by Eberhard Ammelt 01 Aug '11

01 Aug '11

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com I'm passing an empty NSDictionary as default value. The problem appears only with FCP 7 under Lion, not with Motion 4. Did you see this problem under 10.6 as well? Eberhard > On 8/1/2011 12:56 PM, Eberhard Ammelt wrote: >> Thanks Paul, but both options don't help. It looks that the FxPlugWrapper object is the same for V1 and V2 parameter APIs. > > Hmm I don't know what to tell you. I know that some of the API interfaces look the same between v1 and v2. I just know that I also had the problem as you, and fiddling around with these 2 things helped. > > Make sure you are using FxParameterSettingAPI_v2 and FxParameterCreationAPI_v2, as well as FxParameterRetrievalAPI_v2. > > One more thing - when you create your Custom parameter, you *MUST* give it a default value. It can't be NULL. Even if it's just an empty NSData object, you have to pass something into the default value argument. > > Those are the only gotchas I can remember. > _______________________________________________ > 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/eammelt%40pixlock.com > > This email sent to eammelt(a)pixlock.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: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
by Micah Sharp 01 Aug '11

01 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: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
by Paul Miller 01 Aug '11

01 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 Those are the only gotchas I can remember. _______________________________________________ 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/1/2011 12:56 PM, Eberhard Ammelt wrote: Thanks Paul, but both options don't help. It looks that the FxPlugWrapper object is the same for V1 and V2 parameter APIs. Hmm I don't know what to tell you. I know that some of the API interfaces look the same between v1 and v2. I just know that I also had the problem as you, and fiddling around with these 2 things helped. Make sure you are using FxParameterSettingAPI_v2 and FxParameterCreationAPI_v2, as well as FxParameterRetrievalAPI_v2. One more thing - when you create your Custom parameter, you *MUST* give it a default value. It can't be NULL. Even if it's just an empty NSData object, you have to pass something into the default value argument. This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
by Eberhard Ammelt 01 Aug '11

01 Aug '11

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Thanks Paul, but both options don't help. It looks that the FxPlugWrapper object is the same for V1 and V2 parameter APIs. Eberhard > On 8/1/2011 8:49 AM, Eberhard Ammelt wrote: >> Hello, >> >> I noticed that custom parameter data is not saved with the project in FCP 7.0.3 in OS X 10.7 and changing a custom parameter value does not trigger a re-render. >> Is this a known issue, and is there a workaround for this? > > There are two things that could affect this: > > 1. make sure you are using the V2 parameter create/query APIs. Your plugin will still appear to work fine if you are using the V1 APIs, but your custom data won't save. > > 2. If you *ARE* using the V2 APIs, you may need to add a dummy NSView in the custom UI creation callback. Just an empty very small view and mark it hidden. > > _______________________________________________ > 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/eammelt%40pixlock.com > > This email sent to eammelt(a)pixlock.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 01 Aug '11

01 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

Re: setWidth deprecated warning
by Darrin Cardani 01 Aug '11

01 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Martin, It's because FxImages are mostly immutable. There's no safe way to change the image data in an FxImage, so we deprecated the setters and updated the initializers to make it more clear. In the past, when a plug-in called -setWidth:, the image's width member variable would be changed, but the data behind it wouldn't. (Because how can we know if you want to scale or crop it when changing the width.) So the object was then in an inconsistent state and any operations on it were inherently unsafe (at least with bitmaps where reading or writing off the edge could clobber other parts of memory). Also, it allowed the plug-in to do some unsafe things like changing an output image's bitmap pointer behind the app's back. If that happens, the app no longer knows if the bitmap owns the data pointer or not, so it can't safely free it. So if you want to change the width or height of an image you now have to create a new image. This shouldn't be a performance hit because you have to regenerate the data, anyway. Creating a new FxImage is a pretty fast operation with the new initializers. Note that I said they're "mostly" immutable. It is fairly safe to change the field value, for example, since it doesn't require changing the image data. It's rare that you'd want to change that value. But you could, theoretically, create a new image that you're using as an intermediate buffer, and set the field value to match something the app passed you, or something like that. Not a common case, but much less problematic than changing the width or height. Darrin On Jul 30, 2011, at 1:48 AM, Martin Baker wrote: > Everytime I call FxImage.width, Xcode throws up a warning that "setWidth is deprecated". Why? > > Martin Baker > www.digital-heaven.co.uk > www.twitter.com/digitalheaven > www.videospaceonline.com > www.finalcutters.com > ------------------------------------------------------ > Digital Heaven Ltd is registered in England and Wales > Company registration number: 3628396 > Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE > VAT registration number: GB 736 0989 03 > > _______________________________________________ > 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: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
by Paul Miller 01 Aug '11

01 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 Hello, I noticed that custom parameter data is not saved with the project in FCP 7.0.3 in OS X 10.7 and changing a custom parameter value does not trigger a re-render. Is this a known issue, and is there a workaround for this? There are two things that could affect 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/site_archiver%40lists.a… On 8/1/2011 8:49 AM, Eberhard Ammelt wrote: 1. make sure you are using the V2 parameter create/query APIs. Your plugin will still appear to work fine if you are using the V1 APIs, but your custom data won't save. 2. If you *ARE* using the V2 APIs, you may need to add a dummy NSView in the custom UI creation callback. Just an empty very small view and mark it hidden. This email sent to site_archiver(a)lists.apple.com

1 0

FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
by Eberhard Ammelt 01 Aug '11

01 Aug '11

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Hello, I noticed that custom parameter data is not saved with the project in FCP 7.0.3 in OS X 10.7 and changing a custom parameter value does not trigger a re-render. Is this a known issue, and is there a workaround for this? Regards, Eberhard _______________________________________________ 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

Encoding of data parameters in .moef (Final Cut Effect template) files
by Patrick Renner 01 Aug '11

01 Aug '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com We are programmatically creating .moef files from our own application - which works pretty good for numerical parameters. For data parameters (data blobs) we couldn't completely encode our payload data into data parameters in the moef XML file. An example snipped from the .moef file: --- snip --- <parameter name="My Fancy Datablob" id="23" flags="77326188545"> <numberOfKeypoints>0</numberOfKeypoints> <defaultVal>*********6IeMb-gOLBoA11I*E61-*I40*ZM75NZQbBdPqtM74xWOaJXR5BN743mMqVdRaJmJ0FoPr*G**44c825JGFiRKlgLl*DHZB9NLZZN23mMqVdRaJmoEc9IWEkU**62FcX9H6rCHxFJ3Q********-*E*********A********************KE**</defaultVal> <dataValue>********67UeMb-gOLBoA11I*E61-*I40EdM75NZQbBdPqtM74xWOaJXR5BN743mMqVdRaJmJ0FoPr*G**44c86503IYPbJgP2wF6*1a*CQ*u*1c*CY*uE1e*Cg*uk1g*Co*vE1i*Cs*vk1k*D**wE1l*D6*wk1n*DE*x*1p*DM*xU1r*DU*y*1t*DY*yU1v*Dg*z*1x*Do*zU1y*Dw***2**E2-*U20*EA-*k22*EI--E24*EQ--k26*EY-0E28*Ec-0k2A*Ek-1E2C*Es-1k2E*F*-2E2G*F6-2k2I*FE-3E2K*FM-3k2L*FU-4E2N*Fc-4k2P*Fk-5E2R*Fs-5k2T*G*-6E2V*G6-6k2X*GE-7E2Z*GM-7k2c*GU-8E2e*Gc-8k2g*Gk-9E2i*Gs-9k2k*H*-AE2m*H6-Ak2o*HI-BE2q*HQ-Bk2s*HY-CE2u*Hg-D*2w*Ho-DU2y*Hw-E*3**I2-EU31*IA-F*33*II-FU35*IU-G*37*Ic-GU39*Ik-HE3B*Is-Hk3E*J*-IE3G*J6-Ik3I*JI-JE3K*JQ-K*3M*JY-KU3P*Jg-L*3R*Js-LU3T*K*-ME3V*K6-Mk3Y*KE-NE3a*KQ-Nk3c*KY-OU3e*Kg-P*3h*Ko-PU3j*L*-Q*3l*L6-Qk3o*LE-RE3q*LQ- .... --- snip --- We found out, that the blob is the plist from a NSKeyedArchiver encoded with something similar to xxencode (with a slightly different character set). This is similar to the blob encoding used for Final Cut Studio, but still different (no CDATA element, other encoding character set, different archiver nesting). Unfortunately there are some padding bytes at the beginning of the plist and some missing bytes at the end for which we couldn't find out an apparent algorithm. Maybe someone knows more or can give some hints how to properly create these blobs for .moef XML files. Thanks, Patrick -- Patrick Renner -- ptr(a)pomfort.com -- Pomfort GmbH -- http://pomfort.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 smime.p7s

1 0