Bernhard

it seems that the framedump message is broken when recording the 

output to disc with jit.qt.record. It gets confused with the length 

http://www.archive.org/download/LuckyStr1948_2/

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

---
Bernhard Loibner
sound & media artist
http://loibner.cc

framedump-broken-when-recording

It appears that the built-in "stop" function isn't working, for some 

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 

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 

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.

> 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.


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

> It appears that the built-in "stop" function isn't working, for 

> 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 

> 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.

> 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.
>

framedump broken when recording?