Forums > Jitter

restarting a movie

December 12, 2006 | 8:51 pm

i have a problem that bewilders me.
to restart a qt.movie i expect [time 0] or [frame 0] will jump the playhead
to frame/time 0 .
but if i stop the metro and pass those messages to the qt.movie, when i re
enable the metro it plays from a different position.

max v2;
#N vpatcher 15 55 516 455;
#P user jit.pwindow 92 224 82 62 0 1 0 0 1 0;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P message 223 163 60 9109513 read;
#P message 154 162 60 9109513 time 0 , bang;
#P flonum 131 141 35 9 0.5 0 1 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P toggle 97 141 15 0;
#P newex 97 161 44 9109513 metro 2;
#P newex 97 198 103 9109513 jit.qt.movie 320 240;
#B color 5;
#P connect 0 0 6 0;
#P connect 2 0 1 0;
#P connect 5 0 0 0;
#P fasten 1 0 0 0 102 191 102 191;
#P fasten 4 0 0 0 159 188 102 188;
#P connect 3 0 1 1;
#P pop;


December 12, 2006 | 9:07 pm

This reflects a misunderstanding of how jit.qt.movie is working.
jit.qt.movie is playing the movie,
_regardless_of_whether_the_metro_is_on_or_not_. if you want to stop
the movie, send the "stop" message to the movie, and then the "start"
message to get it going again. If you need to switch the metro off
and on, for whatever reason, you can do it as I’ve repatched below:

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 198 133 40 196617 t 1 s b;
#P message 198 114 33 196617 start;
#P newex 157 132 31 196617 t 0 s;
#P message 157 113 29 196617 stop;
#P user jit.pwindow 152 284 82 62 0 1 0 0 1 0;
#P message 302 158 60 196617 read;
#P message 228 157 39 196617 time 0;
#P flonum 111 178 35 9 0.5 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P toggle 77 178 15 0;
#P newex 77 198 44 196617 metro 2;
#P newex 157 258 103 196617 jit.qt.movie 320 240;
#B color 5;
#P connect 9 0 10 0;
#P connect 10 2 4 0;
#P connect 10 1 0 0;
#P connect 10 0 2 0;
#P connect 8 0 2 0;
#P connect 7 0 8 0;
#P connect 8 1 0 0;
#P connect 3 0 1 1;
#P fasten 4 0 0 0 233 248 162 248;
#P fasten 1 0 0 0 82 251 162 251;
#P connect 5 0 0 0;
#P connect 2 0 1 0;
#P connect 0 0 6 0;
#P window clipboard copycount 11;

Am 12.12.2006 um 21:51 schrieb yair reshef:

> i have a problem that bewilders me.
> to restart a qt.movie i expect [time 0] or [frame 0] will jump the
> playhead
> to frame/time 0 .
> but if i stop the metro and pass those messages to the qt.movie,
> when i re
> enable the metro it plays from a different position.


December 12, 2006 | 9:16 pm

>This reflects a misunderstanding of how jit.qt.movie is working.
>jit.qt.movie is playing the movie,

Apparently. But happily, this can be remedied by looking at Jitter
Tutorials 1 and 4.

on the floor there’s a long wooden table/on the table there’s an open book/
on the page there’s a detailed drawing/and on the drawing is the name I took
Gregory Taylor http://www.rtqe.net


December 12, 2006 | 9:23 pm

stopping the metro does not stop the playhead from moving. if you
want to stop the playhead from moving send the stop message.

if you want to stop outputting frames, and stop the playhead moving,
send stop and no longer bang.

just because you arent feeding metros doesnt mean the playhead isnt
moving. :)

On Dec 12, 2006, at 3:51 PM, yair reshef wrote:

> i have a problem that bewilders me.
> to restart a qt.movie i expect [time 0] or [frame 0] will jump the
> playhead to frame/time 0 .
> but if i stop the metro and pass those messages to the qt.movie,
> when i re enable the metro it plays from a different position.
>
> max v2;
> #N vpatcher 15 55 516 455;
> #P user jit.pwindow 92 224 82 62 0 1 0 0 1 0;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P message 223 163 60 9109513 read;
> #P message 154 162 60 9109513 time 0 , bang;
> #P flonum 131 141 35 9 0.5 0 1 139 0 0 0 221 221 221 222 222 222 0
> 0 0;
> #P toggle 97 141 15 0;
> #P newex 97 161 44 9109513 metro 2;
> #P newex 97 198 103 9109513 jit.qt.movie 320 240;
> #B color 5;
> #P connect 0 0 6 0;
> #P connect 2 0 1 0;
> #P connect 5 0 0 0;
> #P fasten 1 0 0 0 102 191 102 191;
> #P fasten 4 0 0 0 159 188 102 188;
> #P connect 3 0 1 1;
> #P pop;
>

v a d e //

http://www.vade.info
abstrakt.vade.info


December 12, 2006 | 10:05 pm

>
> just because you arent feeding metros doesnt mean the playhead isnt
> moving. :)
>

back to basics for me, this is completly unintuative . way would a playhead
move if theres no bang.
thank you all for the corrections.

On Dec 12, 2006, at 3:51 PM, yair reshef wrote:
>
> i have a problem that bewilders me.
> to restart a qt.movie i expect [time 0] or [frame 0] will jump the
> playhead to frame/time 0 .
> but if i stop the metro and pass those messages to the qt.movie, when i re
> enable the metro it plays from a different position.
>
> max v2;
> #N vpatcher 15 55 516 455;
> #P user jit.pwindow 92 224 82 62 0 1 0 0 1 0;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P message 223 163 60 9109513 read;
> #P message 154 162 60 9109513 time 0 , bang;
> #P flonum 131 141 35 9 0.5 0 1 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P toggle 97 141 15 0;
> #P newex 97 161 44 9109513 metro 2;
> #P newex 97 198 103 9109513 jit.qt.movie 320 240;
> #B color 5;
> #P connect 0 0 6 0;
> #P connect 2 0 1 0;
> #P connect 5 0 0 0;
> #P fasten 1 0 0 0 102 191 102 191;
> #P fasten 4 0 0 0 159 188 102 188;
> #P connect 3 0 1 1;
> #P pop;
>
>
>
> *v a d e //*
>
> *www.vade.info*
> *abstrakt.vade.info*
>
>
>
>
>
>
>


December 12, 2006 | 10:17 pm

I still forget about this all the time – . its a bit unintuitive,
but makes sense. The bang only tells jit.qt.movie to output a matrix,
Realize too that the frames are still being decompressed when no
matrix is being output, so unless you hit stop, you still may have a
significant performance loss due to having a movie being playedin the
background, esp if it is something like h.264 or a large DV movie,
etc etc.

On Dec 12, 2006, at 5:05 PM, yair reshef wrote:

>
>
> just because you arent feeding metros doesnt mean the playhead isnt
> moving. :)
>
> back to basics for me, this is completly unintuative . way would a
> playhead move if theres no bang.
> thank you all for the corrections.
>
> On Dec 12, 2006, at 3:51 PM, yair reshef wrote:
>
>> i have a problem that bewilders me.
>> to restart a qt.movie i expect [time 0] or [frame 0] will jump the
>> playhead to frame/time 0 .
>> but if i stop the metro and pass those messages to the qt.movie,
>> when i re enable the metro it plays from a different position.
>>
>> max v2;
>> #N vpatcher 15 55 516 455;
>> #P user jit.pwindow 92 224 82 62 0 1 0 0 1 0;
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P message 223 163 60 9109513 read;
>> #P message 154 162 60 9109513 time 0 , bang;
>> #P flonum 131 141 35 9 0.5 0 1 139 0 0 0 221 221 221 222 222 222 0
>> 0 0;
>> #P toggle 97 141 15 0;
>> #P newex 97 161 44 9109513 metro 2;
>> #P newex 97 198 103 9109513 jit.qt.movie 320 240;
>> #B color 5;
>> #P connect 0 0 6 0;
>> #P connect 2 0 1 0;
>> #P connect 5 0 0 0;
>> #P fasten 1 0 0 0 102 191 102 191;
>> #P fasten 4 0 0 0 159 188 102 188;
>> #P connect 3 0 1 1;
>> #P pop;
>>
>
> v a d e //
>
> http://www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>
>

v a d e //

http://www.vade.info
abstrakt.vade.info


December 12, 2006 | 10:22 pm

>I still forget about this all the time – . its a bit unintuitive,
>but makes sense. The bang only tells jit.qt.movie to output a matrix,

So, if you send the bang message at a faster rate than the "film" is playing
inside the jit.qt.movie object, it repeats frames. If you send the bang message
more slowly than the movie’s rate, it drops frames. This seems intuitively
optimal… to me, anyway. Or at least that Tutorial explained it pretty well.

on the floor there’s a long wooden table/on the table there’s an open book/
on the page there’s a detailed drawing/and on the drawing is the name I took
Gregory Taylor http://www.rtqe.net


December 12, 2006 | 10:36 pm

That part I got, the part that took me a while to digest was that not
banging did not stop the movies frames from being decompressed
‘behind’ the scenes.

On Dec 12, 2006, at 5:22 PM, Gregory Taylor wrote:

>> I still forget about this all the time – . its a bit unintuitive,
>> but makes sense. The bang only tells jit.qt.movie to output a matrix,
>
> So, if you send the bang message at a faster rate than the "film"
> is playing
> inside the jit.qt.movie object, it repeats frames. If you send the
> bang message
> more slowly than the movie’s rate, it drops frames. This seems
> intuitively
> optimal… to me, anyway. Or at least that Tutorial explained it
> pretty well.
> —
> on the floor there’s a long wooden table/on the table there’s an
> open book/
> on the page there’s a detailed drawing/and on the drawing is the
> name I took
> Gregory Taylor http://www.rtqe.net

v a d e //

http://www.vade.info
abstrakt.vade.info


December 12, 2006 | 10:49 pm

They aren’t being decompressed per se, but QuickTime is preparing
them for decompression and continuing to read data from disk.

jb

Am 12.12.2006 um 23:36 schrieb vade:

> That part I got, the part that took me a while to digest was that
> not banging did not stop the movies frames from being decompressed
> ‘behind’ the scenes.


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