site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Thanks Piero Fiorani Il giorno 02/apr/09, alle ore 11:20, Kristian Harms ha scritto: Den 2. april. 2009 kl. 02.57 skrev Brian Gardner: When I put my generator on the timeline and cut it in half, the second half now restarts the generator at frame 1. I'd like to have the generated frames on either side of the cut look identical to how they looked before the cut. Can I do that? -- Kristian Harms _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/piero.fiorani%40fastwebn... _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... I wrote couple of fxscript generators myself and I was about to say: hey I have a solution... but while coding I bumped into a fxscript limit. There is no way that I know to get the IN point position in a generator. If it were possible the IN position could be saved into a global variable savedOffset (which is left untouched during clip copies or IN point repositioning) and used in the new generator instance to evaluate myFrame = frame + glOffset - savedOffset. If it were possible... Unfortunately the GetLimits(clip, glDuration, glOffset) function does not work applied to generators because there is no way to set clip = the generator itself. Is there any hidden fxscript function or predeclared variable that allows to get the glOffset for a generator ? (Note: I already used this technique to save a filter state into global variables and it works - see my Auto Pan Zoom filter. But while glDuration and glOffset values are meaningful for both filters and generators, the GetLimits function cannot be used in generators to get those values...) -- Brian I'd very much like to second what Brian is saying here, this is something our users would also benefit from. Maybe an auxiliary step to "freeze" a generator, take a rendered generator and turn it into something that behaves more like video item could be employed, after which the cut-in-half operation would behave like Brian describes. A somewhat related request that I would like to put forward (related because it also involves getting two generator instances from one, without making a new instance from scratch) is to have some sort of notification when the user uses copy and paste on a generator. While there would be many who wouldn't have any use for this, in our particular case it would be most helpful. The value of our custom parameter contains a persistent ID which we map to objects in an internal data structure (shared by our generator instances), and the current situation will sometimes lead to multiple generators with the same ID. While we have managed to maintain correct operation, it does create a performance hit. This email sent to piero.fiorani@fastwebnet.it This email sent to site_archiver@lists.apple.com