Re: Reading temporal textures in FCP
Re: Reading temporal textures in FCP
- Subject: Re: Reading temporal textures in FCP
- From: Eberhard Ammelt <email@hidden>
- Date: Wed, 1 Dec 2010 12:40:42 +0100
Hello Darrin,
the problem seems to be related to caching of textures. The plugin uses a contiguous range of texture frames and keeps the recently used ones retained so mostly only one frame needs to be read from the timeline per "renderOutput:" call.
Is it wrong to retain textures beyond the scope of "renderOutput:"?
Eberhard
> Eberhard,
> That's something that should work correctly. My only guess would be either to make sure you're actually sending different time values (within the valid range for the clip) for each frame. If that's happening correctly, it could be a bug in FCP (though I'd think someone would have run into this sooner if it were).
>
> Darrin
>
> On Nov 19, 2010, at 6:08 AM, Eberhard Ammelt wrote:
>
>> Hello,
>>
>> I'm trying to read a contiguous range of textures from the timeline in FCP (7.0.2) using "getInputTexture:".
>> All the returned textures seem to contain just the current image though the texture ids are different.
>> Am I missing anything?
>>
>> Thanks, Eberhard _______________________________________________
>> 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
>
> --
> Darrin Cardani
> 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