I’ve tried for a while to fix this and I’m still having trouble.
I’ve got a patch which loads a jit.qt.movie (loadram 1) say 10 seconds. I want to slow it down so the movie plays to the end in 20 secs and then record it with jit.qt.record. If I change the rate, that’s fine, but running a framedump ignores the rate.
Running at realtime is not satisfactory as any disk activity I’m finding causes a frame drop (which is the reason I was using framedump in the first place obviously) which shows up in the movie jit.qt.record records. Is there any way round this, to change the rate and dump the modified frames?
you could try triggering two frames for each frame you receive from the frame dump eg. using [trigger l l]. this should effectively double the length of the movie.
Thanks for the post. I’m going to use Final Cut to do the donkey work. Seems a bit like cheating though…
Isn’t there a "duration $1" message to jit.qt.movie which scales the whole length of the movie? You could find the duration with "getduration", then double that, re-save the movie, maybe.
Yeah man, don’t cheat! :)
(actually using other software to fill in the gaps is totally fine and can save time in certain cases…)
I’ll check out the duration message, although I wouldn’t have thought this works with a framedump.
C74 RSS Feed | © Copyright Cycling '74