Jit.qt.movie and getting timecode from a movie

Jul 5, 2011 at 3:31pm

Jit.qt.movie and getting timecode from a movie

Hi everyone!
I have a movie which contains timecode information, but I can’t seem to figure out how the reference manual tells me to retrieve the timecode info, within max/msp.

I need the timecode (preferebly in ticks) to drive a midisequencer (seq object).

But this doesn’t seem to work – i don’t get where the list, the reference manual writes about, is supposed to come from.

– Pasted Max Patch, click to expand. –

Hope you guys can help me out!

Jul 5, 2011 at 5:07pm

I don’t have any Movies with timecode tracks, but when trying your patch, the Max Window reports: Jit.qt.movie: doesn’t understand “timecodeinfo” . Maybe try using “gettimecodeinfo nondrop counter fps2″ from a messagebox connected to the qtmovie object instead.

Jul 5, 2011 at 5:09pm

nope it doesn’t work.. i’m reading the Tutorial 4: Controlling Movie Playback. but it doesn’t seem to be excatly what i need.

Jul 5, 2011 at 5:13pm

EDited prevoius post FWIW . Also, you might need to set gettimecode 1. Otherwise I’m not sure… Just in case – are you looking in the max window for messages from the jit.qt.object?

Jul 5, 2011 at 5:15pm

as an attribute so @gettimecode 1 ?

Jul 5, 2011 at 5:17pm

not if it is a message then its just: “gettimecode 1″

Jul 5, 2011 at 5:50pm

‘timecode’ and ‘timecodeinfo’ are gettable attributes (but are not settable). You send the message ‘gettimecodeinfo’ and ‘gettimecode’ to query the state of those attributes, and the response comes out of the right outlet as ‘timecodeinfo’ and ‘timecode’ messages.

– Pasted Max Patch, click to expand. –
Jul 5, 2011 at 6:17pm

now i see.. thank you so much. Se if I want that to drive my [seq] object, which wants 48 ticks pr. second, could I just use a [uzi 2] (since my framerate is 24 in the video), or do you have some other cool nifty little trick?

Jul 5, 2011 at 8:21pm

Christopher, When is the “timescale” created? When you render your movie?


You must be logged in to reply to this topic.