Re: FCP and generators: forcing an entire clip to re-render?
Re: FCP and generators: forcing an entire clip to re-render?
- Subject: Re: FCP and generators: forcing an entire clip to re-render?
- From: Peter Litwinowicz <email@hidden>
- Date: Fri, 29 May 2009 16:04:53 -0700
- Thread-topic: FCP and generators: forcing an entire clip to re-render?
We'd like this to0. For instance, in our retiming plugin, it would be nice
to "retime to fit"... Which would also necessitate the same feature.
Pete
> Hi Steve,
>
> There's no way for you to signal that changing your generator's
> duration invalidates all previously rendered frames. I think we'd need
> a separate flag for this, since this isn't true for many effects, even
> the ones that vary over time.
>
> I believe we've had requests for this before, but please feel free to
> add your voice.
>
> - Paul
>
>
> On May 29, 2009, at 1:49 PM, Steve Christensen wrote:
>
>> I have a generator effect that varies over the length of a clip in a
>> way that depends upon the clip length. For example, think of the
>> case where you have a bouncing ball that goes from the left- to the
>> right side of the frame over the course of the clip duration.
>>
>> If I drag my generator effect to the timeline and configure it, then
>> tell FCP to render the clip, the render happens and the render
>> status line above the clip changes from orange (unlimited) to blue
>> (rendered). When I play back the clip, I see the equivalent of the
>> bouncing ball happily bouncing from the left- to the right side of
>> the frame.
>>
>> If I then increase the length of the clip, I see the blue line above
>> the previously-rendered section, the orange line above the section
>> just extended. If I "render all," the newly-added section is
>> rendered. If I play back the clip, I see the bouncing ball going
>> from left to right, then in the newly-added section, the ball hops
>> back a bit and then bounces to the right edge.
>>
>> I'm trying to figure out if I have something set up incorrectly in
>> the plugin or if this is just the way that FCP works. There are only
>> two things I think I have control over, thus those methods are set
>> up as:
>>
>> - (BOOL) variesOverTime
>> {
>> return YES;
>> }
>>
>> - (NSDictionary*) properties
>> {
>> return [NSDictionary dictionaryWithObjectsAndKeys:
>> [NSNumber numberWithBool:YES],
>> kFxPropertyKey_SupportsRowBytes,
>> [NSNumber numberWithBool:NO],
>> kFxPropertyKey_SupportsR408,
>> [NSNumber numberWithBool:NO],
>> kFxPropertyKey_SupportsR4fl,
>> [NSNumber numberWithBool:NO],
>> kFxPropertyKey_MayRemapTime,
>> [NSNumber numberWithBool:NO],
>> kFxPropertyKey_PreservesAlpha,
>> [NSNumber numberWithBool:NO],
>> kFxPropertyKey_PixelIndependent,
>> [NSNumber numberWithInt:0],
>> kFxPropertyKey_EquivalentSMPTEWipeCode,
>> nil];
>> }
>>
>>
>> Anything else I can fix or am I stuck with this behavior?
>>
>> steve
>>
>> _______________________________________________
>> 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