Apple

Paul Schneider wrote:

Hi, Micah,

yes, unfortunately, FCP doesn't support separate slider ranges and numeric-entry ranges. We limit input to the smaller of the two ranges. This should be documented in the FxPlug SDK: it's a bug if it's not.

- Paul

On Jul 16, 2007, at 3:57 PM, Micah Sharp wrote:

Hey guys, I am seeing that this code

[parmsAPI addFloatSliderWithName :@"Offset"

parmId :FXid_Cycle

defaultValue :0

parameterMin :-100

parameterMax :10000

sliderMin :0

sliderMax :100

delta :1

parmFlags :kFxParameterFlag_DEFAULT | kFxParameterFlag_COLLAPSED];

FCP 6.0 either ignores input less than the slider min (no render call), or clamps the value to the slider max, regardless of what is typed into the fields. Is this a known issue? Motion seems to have no problem using the parameter min/max values rather than only slider min/max.

Note it's been FR'd here for what 8 years? I guess we're being patient :)
Also is something like state animation (i.e. animated menu) on the top of the FR list for next version - also an 8 years old FR
(Or a workaround like possibility to greyout an integer slider so a popup menu can become an action that always reset itself to the same menu value eg "select mode" so we can select a popup mode, set a key on greyed out int slider, unset the popup mode and then in rendering lookup where int slider keyframes (prev and next) are in time).
Pierre

Thanks,

Micah

_______________________________________________

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:
	>parameter min/max in FCP (From: Micah Sharp <email@hidden>)
	>Re: parameter min/max in FCP (From: Paul Schneider <email@hidden>)