Re: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
Re: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
- Subject: Re: FxPlug custom parameter data not saved in FCP 7 / OS X 10.7
- From: Eberhard Ammelt <email@hidden>
- Date: Mon, 01 Aug 2011 21:01:02 +0200
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 (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden