Forums > Jitter

[Sharing is timely] video retiming tool

March 15, 2011 | 1:11 am

Here’s a video retiming tool I’ve been developing forever: http://zachgold.tv/?p=147. It’s basically the reason I originally learned Max. Use it to generate all kind of crazy automated time ramps for your video…with no rendering whatsoever!

I would absolutely love it if anyone cares enough to extend this in any way. If you slog through my overly verbose description, you’ll see that I’m actually releasing two separate patches. One is more streamlined and fine tuned, while the other includes pretty much every feature I could imagine at the time (I have now imagined far more). The latter has a crude facility for adding modules to generate your timing algorithms. I’m not sure there’s enough interest in such a prosaic use of Jitter, but I think it’d be rockin if someone other than me patched together some modules.

Please let me know what you think!

Zach


March 15, 2011 | 3:01 pm

Hi Zach,

Thanks for the sharing :)
Unfortunately every time i load a video and start to play whit the settings max crash :( I’m on Macbook Pro 1.87GHz (5 years old now), 10.6.6, Max 5.1.7

Thanks

Luis Marques


March 15, 2011 | 6:39 pm

Hmm, I would check that it’s not loading the video into RAM. I generally use this for smaller videos, plus I currently am on a Mac Pro with a ton of RAM, so you may not ever want to do that for your own purposes.

Which version of the patch are you using?


March 15, 2011 | 6:48 pm

I didn’t "loadram" videos, i just hit "read" probably the crash came from there. I’m using Scruber1 and Scruber2, the crash happens to both.

Luis Marques


March 15, 2011 | 8:04 pm

I did some testing and the crash seems to occur when the patch starts sending frame values before a video is loaded. I never had this problem in the past, so it must be due to a recent Jitter update. As noted, I’ve also been using the second version for a while, where this issue is not so noticeable because of its "single shot" (as opposed to continuous looping) scrubbing style. I’ll log a bug report and get back to you.


March 16, 2011 | 9:55 pm

I’m told this is a bug that will be fixed in 5.1.8. In the meantime, using a patch cord instead of @window fixes the problem.


Viewing 6 posts - 1 through 6 (of 6 total)