b00kwheat

This blog post is dated from 2007. CPUs and graphics cards have significantly increased since then.

I'm wondering if it's still relevant to Max6 and Max7 with today's processors?

Can anyone comment on what revisions should be made on this?

This blog post is dated from 2007.  CPUs and graphics cards have significantly increased since then.
I'm wondering if it's still relevant to Max6 and Max7 with today's processors?

vades-jitter-movie-playback-optimizations

So when , set in @output_texture 1, jit.movie no longer need to receive a bang to output a clip.

Anyways , here's what Rob Ramirez has to say about it:

 https://cycling74.com/forums/jit-movie-output_texture-1-texture_name-n-vs-jit-gl-hap-out_name-n/

jit.movie @output_texture 1 @engine qt is more or less equal to jit.gl.hap playing back non-hap encoded files. they use the same basic software library when not playing hap-files.

jit.movie @output_texture 1 @engine qt is not equal to jit.gl.hap when playing back hap encoded files.

jit.movie @output_texture 1 @engine avf (the default) is not equal to jit.gl.hap. different technology entirely.

the two most efficient options a jit.gl.hap playing hap encoded files, and jit.movie @engine avf @output_texture 1 @colormode uyvy (if not using alpha) playing prores files.

jit.qt.movie is now jit.movie.
jit.movie now has:
-built-in avf engine
-@output_texture 1
-@colormode uyvy 

So when , set in @output_texture 1, jit.movie no longer need to receive a bang to output a clip.
going directly to GPU.

Anyways , here's what Rob Ramirez has to say about it:
From the thread: https://cycling74.com/forums/jit-movie-output_texture-1-texture_name-n-vs-jit-gl-hap-out_name-n/ 

Vade's Jitter movie playback optimizations