coda

I'm trying to create a patch which at final output renders a quicktime movie, these movies will for the most part be rendered at their native fps without any variation in their playback "rate" whilst in the patch, it's important that the final frame count and rate remain accurate and at an exact match to the source movie, without either dropping or repeating frames. ie is frame accurate.

So, I've started putting together the basic elements in to a patch and am having the following problems, the fps of the playback and record windows does fluctuate slightly as indicated by the fps objects, though minor it's obvious that this frame rate is not "locked" and when I hit the write message the frame rate drops to approx 10 fps slower, completely dislocating it from it's original frame rate and order, which creates choppy looking renders with frames both duplicating and dropping out.

I can't find any way to fix this problem, I'm new to maxmsp and jitter and I'm not sure a lot of the time if I'm working around genuine bugs or my own errors, it would be a great help to me to talk this though with someone.

jit-qt-movie-fps-problem

you need something that doesn't do real-time frame capture. so jit.qt.record (with the default of "realtime" attribute turned off). But don't use jit.vcr, since that is for real time.

use the message "framedump" to your jit.qt.movie to send out frames as quickly as your patch can handle them. they should then be recorded at whatever constant frame rate you define in the "write" message to the jit.qt.record.

Assuming you don't need to process the audio, ignore sending it out a socket. In quicktime pro, you can just copy the audio from the original and paste it into the new movie

you need something that doesn't do real-time frame capture. so jit.qt.record (with the default of "realtime" attribute turned off). But don't use jit.vcr, since that is for real time. 

use the message "framedump" to your jit.qt.movie to send out frames as quickly as your patch can handle them. they should then be recorded at whatever constant frame rate you define in the "write" message to the jit.qt.record. 

Jit.qt.movie fps problem