framedump broken when recording?

Nov 6, 2006 at 12:37pm

framedump broken when recording?

Hello

it seems that the framedump message is broken when recording the
output to disc with jit.qt.record. It gets confused with the length
of the movie and the order of frames.

Didn’t work with this: http://www.archive.org/download/LuckyStr1948_2/
LuckyStr1948_2_256kb.mp4

thanks
Bernhard

G5, X.4.8, max/msp 4.6.2, Jitter 1.6.2

max v2;
#N vpatcher 21 52 472 677;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P message 90 67 60 196617 framedump;
#P newex 181 149 58 196617 print dump;
#P user jit.pwindow 118 180 162 122 0 1 0 0 1 0;
#P message 152 67 88 196617 cancelframedump;
#P user jit.fpsgui 119 378 60 196617 0;
#P message 56 68 30 196617 read;
#P newex 56 100 105 196617 jit.qt.movie 320 240;
#P message 311 428 35 196617 write;
#P newex 254 488 66 196617 jit.qt.record;
#P message 268 426 27 196617 stop;
#P connect 6 0 3 0;
#P connect 4 0 3 0;
#P connect 9 0 3 0;
#P connect 3 0 7 0;
#P connect 7 0 5 0;
#P fasten 3 1 8 0 156 122 186 122;
#P fasten 3 0 1 0 61 350 259 350;
#P connect 0 0 1 0;
#P connect 2 0 1 0;
#P pop;


Bernhard Loibner
sound & media artist

http://loibner.cc

#28544
Nov 6, 2006 at 1:33pm

It appears that the built-in “stop” function isn’t working, for some
reason. Will investigate.

In the meantime, just send “stop” to the movie or use “@autostart 0″
before loading it. Then framedump seems to work properly.

This is, btw, a Jitter issue, and should properly go in the Jitter
forum.

jb

Am 06.11.2006 um 13:37 schrieb Bernhard Loibner:

> it seems that the framedump message is broken when recording the
> output to disc with jit.qt.record. It gets confused with the length
> of the movie and the order of frames.

#87787
Nov 6, 2006 at 4:56pm

Thanks Jeremy, this did the trick.

best
B.

On Nov/06/2006/, at 14/33, Jeremy Bernstein wrote:

> It appears that the built-in “stop” function isn’t working, for
> some reason. Will investigate.
>
> In the meantime, just send “stop” to the movie or use “@autostart
> 0″ before loading it. Then framedump seems to work properly.
>
> This is, btw, a Jitter issue, and should properly go in the Jitter
> forum.
>
> jb
>
> Am 06.11.2006 um 13:37 schrieb Bernhard Loibner:
>
>> it seems that the framedump message is broken when recording the
>> output to disc with jit.qt.record. It gets confused with the
>> length of the movie and the order of frames.
>


Bernhard Loibner
sound & media artist

http://loibner.cc

#87788

You must be logged in to reply to this topic.