• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: updating custom parameter value does not force render (FCP)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: updating custom parameter value does not force render (FCP)


  • Subject: Re: updating custom parameter value does not force render (FCP)
  • From: Paul Schneider <email@hidden>
  • Date: Tue, 28 Jun 2011 12:03:47 -0500

One possibility is that you're testing with a project that was created with an older version of your plugin. FCP 7 will use the default value that was specified when the effect was added to the project; we won't notice if you change it on a subsequent launch.

On Jun 28, 2011, at 11:58 AM, Paul Schneider wrote:

>
>> Another CUSTOM anomaly. When I press RESET, my custom parameter is not getting it's value set back to the empty NSData that I used for the default value.
>>
>> Do CUSTOM parameters reset properly normally?
>
> I just checked this with the SimpleMatte example in FCP 7, and it appears to work. You might not receive a -parameterChanged message during a reset, though.
>
>
> On Jun 28, 2011, at 10:37 AM, Paul Miller wrote:
>
>> On 6/27/2011 2:03 PM, Paul Miller wrote:
>>> On 6/27/2011 1:48 PM, Paul Schneider wrote:
>>>>
>>>> Final Cut 7 won't re-render in response to changes in hidden
>>>> parameters. One way to work around this is to change a visible
>>>> parameter, even if the parameter data doesn't really have anything to
>>>> do with the UI. For example, you could attach some data to your
>>>> "Options" button parameter, and change that when you need to re-render.
>>>
>>> Okay I'll try that thanks!
>>
>> Okay this works.
>>
>> Another CUSTOM anomaly. When I press RESET, my custom parameter is not getting it's value set back to the empty NSData that I used for the default value.
>>
>> Do CUSTOM parameters reset properly normally?
>> _______________________________________________
>> 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

 _______________________________________________
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

References: 
 >updating custom parameter value does not force render (FCP) (From: Paul Miller <email@hidden>)
 >Re: updating custom parameter value does not force render (FCP) (From: Garrick Meeker <email@hidden>)
 >Re: updating custom parameter value does not force render (FCP) (From: Paul Miller <email@hidden>)
 >Re: updating custom parameter value does not force render (FCP) (From: Paul Schneider <email@hidden>)
 >Re: updating custom parameter value does not force render (FCP) (From: Paul Miller <email@hidden>)
 >Re: updating custom parameter value does not force render (FCP) (From: Paul Miller <email@hidden>)
 >Re: updating custom parameter value does not force render (FCP) (From: Paul Schneider <email@hidden>)

  • Prev by Date: Re: updating custom parameter value does not force render (FCP)
  • Next by Date: Re: Making FxPlugs Work in Final Cut Pro X
  • Previous by thread: Re: updating custom parameter value does not force render (FCP)
  • Next by thread: Building a Universal FxPlug
  • Index(es):
    • Date
    • Thread