Last night I discovered a serious limitation/bug with jit.qt.record (I need realtime = off). As described also by several persons in this forum the resulting movie's play framerate does often not correspond to the settings. I discovered that it depends solely on the x/y resolution settings in the jit.qt.record object! Nothing to do with codec or recording from jit.matrix or jit.gl.asyncread or correspondence of source x/y resolution with record resolution. With higher record resolutions the movie plays at a higher speed! In my case I'm recording in a 25Hz environment (metro 40, jit.matrix + jit.gl.render) duration 20 seconds. Here a list of measurements:
jit.qt.record settings -> resulting movie file duration
1280 x 720 , 25.0 Hz -> ca. 10 sec. - too fast - double speed
800 x 448 , 25.0 Hz -> ca. 12 sec. - too fast
640 x 480 , 25.0 Hz -> ca. 13 sec. - too fast
320 x 240 , 25.0 Hz -> ca. 20 sec. - correct speed!
1280 x 720 , 12.5 Hz -> ca. 20 sec. - correct speed!
320 x 240 , 12.5 Hz -> ca. 40 sec. - too slow - half speed!
Got it?! As stated above the environment conditions have NO meaning. Everyone can try the effect by simply running and editing the jit.qt.record MAX 6.0 built in help patch. Just edit the 'jit.qt.record 320 240' object changing the x/y resolution. Use 'countdown.mov' for ease of verification.
MAX 6.0.1 (50928) on Windows 7 and Intel i7 processor 2.8 GHz, 8 GB RAM
So is this a Quicktime bug or something wrong in the MAX object?
Does it happen only under Windows?