Forums > Jitter

why this movie stops ?

June 15, 2007 | 2:34 am

Hi all

I asked this question last week but no answer. So I’m sending a little
patch to show the problem.
I don’t know why direct rendering of a quicktime movie stops after
jit.window receives a message.
Maybe I’m missing something ?

Thanks for any help.

Mirko

max v2;
#N vpatcher 246 221 846 621;
#P window setfont "Sans Serif" 12.;
#P window linecount 1;
#P comment 253 168 162 196620 3. change the position –>;
#P comment 194 134 145 196620 2. direct render;
#P window setfont "Sans Serif" 9.;
#P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 421 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 371 216 110 196617 pak pos 0 0;
#P button 93 230 23 0;
#P newex 371 267 149 196617 jit.window ventana @noaccel 1;
#P message 111 136 82 196617 window ventana;
#P message 79 104 30 196617 read;
#P newex 79 271 63 196617 jit.qt.movie;
#P window setfont "Sans Serif" 12.;
#P comment 113 102 115 196620 1. read a movie;
#P fasten 5 0 1 0 98 263 84 263;
#P fasten 3 0 1 0 116 210 84 210;
#P connect 2 0 1 0;
#P connect 6 0 4 0;
#P connect 7 0 6 1;
#P connect 8 0 6 2;
#P pop;


June 15, 2007 | 6:14 am

you need to continously bang jit.qt.movie in order for it to send out
its matrix. I’m not quite sure why the movie plays at all. Perhaps
it has something to do with the fact that you’re direct rendering, but
in my experience, the picture won’t show without being sent with a
bang. Connect a [metro] to jit.qt.movie, and you should be fine.

Here’s an example.

max v2;
#N vpatcher 518 44 1118 444;
#P toggle 17 122 15 0;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 17 143 46 196617 metro 5;
#P window setfont "Sans Serif" 12.;
#P comment 253 168 162 196620 3. change the position –>;
#P comment 194 134 145 196620 2. direct render;
#P window setfont "Sans Serif" 9.;
#P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 421 160 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 371 216 110 196617 pak pos 0 0;
#P button 93 230 23 0;
#P newex 371 267 149 196617 jit.window ventana @noaccel 1;
#P message 111 136 82 196617 window ventana;
#P message 79 104 30 196617 read;
#P newex 79 271 63 196617 jit.qt.movie;
#P window setfont "Sans Serif" 12.;
#P comment 113 102 115 196620 1. read a movie;
#P connect 12 0 11 0;
#P connect 11 0 1 0;
#P connect 2 0 1 0;
#P fasten 3 0 1 0 116 210 84 210;
#P fasten 5 0 1 0 98 263 84 263;
#P connect 6 0 4 0;
#P connect 7 0 6 1;
#P connect 8 0 6 2;
#P pop;

Bryan

http://www.bryanteoh.com

http://www.ksod.net


June 15, 2007 | 7:07 am

…mmm, I think when you’re doing direct rendering you don’t send a
matrix.
I’m doing direct rendering because I need to play a 1600×600 movie
(progressive) of a medium speed travelling at the exact framerate. If
I use metro I get a kind of "judder" in the motion.
Correct me if I’m wrong but I think hardware decompression is more
accurate in terms of framerate.
If someone can explain me what’s happening here I’ll be very grateful.
Muchas gracias.

Mirko

On Jun 15, 2007, at 2:14 AM, Bryan Teoh wrote:

> you need to continously bang jit.qt.movie in order for it to send out
> its matrix. I’m not quite sure why the movie plays at all. Perhaps
> it has something to do with the fact that you’re direct rendering, but
> in my experience, the picture won’t show without being sent with a
> bang. Connect a [metro] to jit.qt.movie, and you should be fine.
>
> Here’s an example.
>
> max v2;
> #N vpatcher 518 44 1118 444;
> #P toggle 17 122 15 0;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P newex 17 143 46 196617 metro 5;
> #P window setfont "Sans Serif" 12.;
> #P comment 253 168 162 196620 3. change the position –>;
> #P comment 194 134 145 196620 2. direct render;
> #P window setfont "Sans Serif" 9.;
> #P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P number 421 160 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 371 216 110 196617 pak pos 0 0;
> #P button 93 230 23 0;
> #P newex 371 267 149 196617 jit.window ventana @noaccel 1;
> #P message 111 136 82 196617 window ventana;
> #P message 79 104 30 196617 read;
> #P newex 79 271 63 196617 jit.qt.movie;
> #P window setfont "Sans Serif" 12.;
> #P comment 113 102 115 196620 1. read a movie;
> #P connect 12 0 11 0;
> #P connect 11 0 1 0;
> #P connect 2 0 1 0;
> #P fasten 3 0 1 0 116 210 84 210;
> #P fasten 5 0 1 0 98 263 84 263;
> #P connect 6 0 4 0;
> #P connect 7 0 6 1;
> #P connect 8 0 6 2;
> #P pop;
>
>
> Bryan
> —
> http://www.bryanteoh.com
> http://www.ksod.net
>


June 15, 2007 | 7:16 am

You still need to bang jit.qt.movie, whether you’re in direct-to-
window mode or not.

jb

Am 15.06.2007 um 09:07 schrieb Mirko Petrovich:

> …mmm, I think when you’re doing direct rendering you don’t send a
> matrix.
> I’m doing direct rendering because I need to play a 1600×600 movie
> (progressive) of a medium speed travelling at the exact framerate.
> If I use metro I get a kind of "judder" in the motion.
> Correct me if I’m wrong but I think hardware decompression is more
> accurate in terms of framerate.
> If someone can explain me what’s happening here I’ll be very grateful.
> Muchas gracias.
>
> Mirko


June 15, 2007 | 8:08 am

the fact that on mac movies are displayed without bangs in direct to
window mode is an unsupported feature. your observation that movies
"judder" when banged is right. i use this unsupported behaviour
extensively for proper playback. try the patch below if that works for
you to keep your movie displayed.

if not you might want to use ntsc encoding to achieve a better look than
pal does.

Jeremy an Joshua, please look into this! I will buy you two beers, every
one of you, if there is any chance that pal playback could be enhanced
or even better pal and ntsc playback could be as posh as direct to
window on mac without banging. if this works on windows as well you get
three beers. each.

word.

john.

max v2;
#N vpatcher 433 222 1033 622;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 203 223 50 196617 deferlow;
#P window setfont "Sans Serif" 12.;
#P comment 253 168 162 196620 3. change the position –>;
#P comment 194 134 145 196620 2. direct render;
#P window setfont "Sans Serif" 9.;
#P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 421 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 371 216 110 196617 pak pos 0 0;
#P button 93 230 23 0;
#P newex 371 267 149 196617 jit.window ventana @noaccel 1;
#P message 111 136 82 196617 window ventana;
#P message 79 104 30 196617 read;
#P newex 79 271 63 196617 jit.qt.movie;
#P window setfont "Sans Serif" 12.;
#P comment 113 102 115 196620 1. read a movie;
#P connect 2 0 1 0;
#P fasten 3 0 1 0 116 210 84 210;
#P fasten 5 0 1 0 98 263 84 263;
#P connect 11 0 5 0;
#P connect 8 0 11 0;
#P connect 7 0 11 0;
#P connect 6 0 4 0;
#P connect 7 0 6 1;
#P connect 8 0 6 2;
#P pop;

Mirko Petrovich schrieb:
> …mmm, I think when you’re doing direct rendering you don’t send a matrix.
> I’m doing direct rendering because I need to play a 1600×600 movie
> (progressive) of a medium speed travelling at the exact framerate. If I
> use metro I get a kind of "judder" in the motion.
> Correct me if I’m wrong but I think hardware decompression is more
> accurate in terms of framerate.
> If someone can explain me what’s happening here I’ll be very grateful.
> Muchas gracias.
>
> Mirko
>
>
> On Jun 15, 2007, at 2:14 AM, Bryan Teoh wrote:
>
>> you need to continously bang jit.qt.movie in order for it to send out
>> its matrix. I’m not quite sure why the movie plays at all. Perhaps
>> it has something to do with the fact that you’re direct rendering, but
>> in my experience, the picture won’t show without being sent with a
>> bang. Connect a [metro] to jit.qt.movie, and you should be fine.
>>
>> Here’s an example.
>>
>> max v2;
>> #N vpatcher 518 44 1118 444;
>> #P toggle 17 122 15 0;
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P newex 17 143 46 196617 metro 5;
>> #P window setfont "Sans Serif" 12.;
>> #P comment 253 168 162 196620 3. change the position –>;
>> #P comment 194 134 145 196620 2. direct render;
>> #P window setfont "Sans Serif" 9.;
>> #P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P number 421 160 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 371 216 110 196617 pak pos 0 0;
>> #P button 93 230 23 0;
>> #P newex 371 267 149 196617 jit.window ventana @noaccel 1;
>> #P message 111 136 82 196617 window ventana;
>> #P message 79 104 30 196617 read;
>> #P newex 79 271 63 196617 jit.qt.movie;
>> #P window setfont "Sans Serif" 12.;
>> #P comment 113 102 115 196620 1. read a movie;
>> #P connect 12 0 11 0;
>> #P connect 11 0 1 0;
>> #P connect 2 0 1 0;
>> #P fasten 3 0 1 0 116 210 84 210;
>> #P fasten 5 0 1 0 98 263 84 263;
>> #P connect 6 0 4 0;
>> #P connect 7 0 6 1;
>> #P connect 8 0 6 2;
>> #P pop;
>>
>>
>> Bryan
>> —
>> http://www.bryanteoh.com
>> http://www.ksod.net
>>
>
>


June 15, 2007 | 8:12 am

Here’s a potentially worthless suggestion: what happens if you enable
@unique 1? Does playback improve?

jb

Am 15.06.2007 um 10:08 schrieb John Dekron:

> the fact that on mac movies are displayed without bangs in direct
> to window mode is an unsupported feature. your observation that
> movies "judder" when banged is right. i use this unsupported
> behaviour extensively for proper playback. try the patch below if
> that works for you to keep your movie displayed.
>
> if not you might want to use ntsc encoding to achieve a better look
> than pal does.
>
> Jeremy an Joshua, please look into this! I will buy you two beers,
> every one of you, if there is any chance that pal playback could be
> enhanced or even better pal and ntsc playback could be as posh as
> direct to window on mac without banging. if this works on windows
> as well you get three beers. each.
>
> word.
>
> john.
>
> max v2;
> #N vpatcher 433 222 1033 622;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P newex 203 223 50 196617 deferlow;
> #P window setfont "Sans Serif" 12.;
> #P comment 253 168 162 196620 3. change the position –>;
> #P comment 194 134 145 196620 2. direct render;
> #P window setfont "Sans Serif" 9.;
> #P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P number 421 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 371 216 110 196617 pak pos 0 0;
> #P button 93 230 23 0;
> #P newex 371 267 149 196617 jit.window ventana @noaccel 1;
> #P message 111 136 82 196617 window ventana;
> #P message 79 104 30 196617 read;
> #P newex 79 271 63 196617 jit.qt.movie;
> #P window setfont "Sans Serif" 12.;
> #P comment 113 102 115 196620 1. read a movie;
> #P connect 2 0 1 0;
> #P fasten 3 0 1 0 116 210 84 210;
> #P fasten 5 0 1 0 98 263 84 263;
> #P connect 11 0 5 0;
> #P connect 8 0 11 0;
> #P connect 7 0 11 0;
> #P connect 6 0 4 0;
> #P connect 7 0 6 1;
> #P connect 8 0 6 2;
> #P pop;
>
>
> Mirko Petrovich schrieb:
>> …mmm, I think when you’re doing direct rendering you don’t send
>> a matrix.
>> I’m doing direct rendering because I need to play a 1600×600
>> movie (progressive) of a medium speed travelling at the exact
>> framerate. If I use metro I get a kind of "judder" in the motion.
>> Correct me if I’m wrong but I think hardware decompression is more
>> accurate in terms of framerate.
>> If someone can explain me what’s happening here I’ll be very
>> grateful.
>> Muchas gracias.
>> Mirko
>> On Jun 15, 2007, at 2:14 AM, Bryan Teoh wrote:
>>> you need to continously bang jit.qt.movie in order for it to send
>>> out
>>> its matrix. I’m not quite sure why the movie plays at all. Perhaps
>>> it has something to do with the fact that you’re direct
>>> rendering, but
>>> in my experience, the picture won’t show without being sent with a
>>> bang. Connect a [metro] to jit.qt.movie, and you should be fine.
>>>
>>> Here’s an example.
>>>
>>> max v2;
>>> #N vpatcher 518 44 1118 444;
>>> #P toggle 17 122 15 0;
>>> #P window setfont "Sans Serif" 9.;
>>> #P window linecount 1;
>>> #P newex 17 143 46 196617 metro 5;
>>> #P window setfont "Sans Serif" 12.;
>>> #P comment 253 168 162 196620 3. change the position –>;
>>> #P comment 194 134 145 196620 2. direct render;
>>> #P window setfont "Sans Serif" 9.;
>>> #P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>>> #P number 421 160 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>>> #P newex 371 216 110 196617 pak pos 0 0;
>>> #P button 93 230 23 0;
>>> #P newex 371 267 149 196617 jit.window ventana @noaccel 1;
>>> #P message 111 136 82 196617 window ventana;
>>> #P message 79 104 30 196617 read;
>>> #P newex 79 271 63 196617 jit.qt.movie;
>>> #P window setfont "Sans Serif" 12.;
>>> #P comment 113 102 115 196620 1. read a movie;
>>> #P connect 12 0 11 0;
>>> #P connect 11 0 1 0;
>>> #P connect 2 0 1 0;
>>> #P fasten 3 0 1 0 116 210 84 210;
>>> #P fasten 5 0 1 0 98 263 84 263;
>>> #P connect 6 0 4 0;
>>> #P connect 7 0 6 1;
>>> #P connect 8 0 6 2;
>>> #P pop;
>>>
>>>
>>> Bryan
>>> —
>>> http://www.bryanteoh.com
>>> http://www.ksod.net
>>>
>


June 15, 2007 | 8:47 am

I think I tried all possible commutations, including @unique 1. also
banging with metro 33, metro 40, metro 2, accessing single frames with
frame 1, 2, 3 etc, uyvy, open gl, videoplanes, textures and what not.
no chance.

john.

Jeremy Bernstein schrieb:
> Here’s a potentially worthless suggestion: what happens if you enable
> @unique 1? Does playback improve?
>
> jb
>
> Am 15.06.2007 um 10:08 schrieb John Dekron:
>
>> the fact that on mac movies are displayed without bangs in direct to
>> window mode is an unsupported feature. your observation that movies
>> "judder" when banged is right. i use this unsupported behaviour
>> extensively for proper playback. try the patch below if that works for
>> you to keep your movie displayed.
>>
>> if not you might want to use ntsc encoding to achieve a better look
>> than pal does.
>>
>> Jeremy an Joshua, please look into this! I will buy you two beers,
>> every one of you, if there is any chance that pal playback could be
>> enhanced or even better pal and ntsc playback could be as posh as
>> direct to window on mac without banging. if this works on windows as
>> well you get three beers. each.
>>
>> word.
>>
>> john.
>>
>> max v2;
>> #N vpatcher 433 222 1033 622;
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P newex 203 223 50 196617 deferlow;
>> #P window setfont "Sans Serif" 12.;
>> #P comment 253 168 162 196620 3. change the position –>;
>> #P comment 194 134 145 196620 2. direct render;
>> #P window setfont "Sans Serif" 9.;
>> #P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P number 421 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 371 216 110 196617 pak pos 0 0;
>> #P button 93 230 23 0;
>> #P newex 371 267 149 196617 jit.window ventana @noaccel 1;
>> #P message 111 136 82 196617 window ventana;
>> #P message 79 104 30 196617 read;
>> #P newex 79 271 63 196617 jit.qt.movie;
>> #P window setfont "Sans Serif" 12.;
>> #P comment 113 102 115 196620 1. read a movie;
>> #P connect 2 0 1 0;
>> #P fasten 3 0 1 0 116 210 84 210;
>> #P fasten 5 0 1 0 98 263 84 263;
>> #P connect 11 0 5 0;
>> #P connect 8 0 11 0;
>> #P connect 7 0 11 0;
>> #P connect 6 0 4 0;
>> #P connect 7 0 6 1;
>> #P connect 8 0 6 2;
>> #P pop;
>>
>>
>> Mirko Petrovich schrieb:
>>> …mmm, I think when you’re doing direct rendering you don’t send a
>>> matrix.
>>> I’m doing direct rendering because I need to play a 1600×600 movie
>>> (progressive) of a medium speed travelling at the exact framerate.
>>> If I use metro I get a kind of "judder" in the motion.
>>> Correct me if I’m wrong but I think hardware decompression is more
>>> accurate in terms of framerate.
>>> If someone can explain me what’s happening here I’ll be very grateful.
>>> Muchas gracias.
>>> Mirko
>>> On Jun 15, 2007, at 2:14 AM, Bryan Teoh wrote:
>>>> you need to continously bang jit.qt.movie in order for it to send out
>>>> its matrix. I’m not quite sure why the movie plays at all. Perhaps
>>>> it has something to do with the fact that you’re direct rendering, but
>>>> in my experience, the picture won’t show without being sent with a
>>>> bang. Connect a [metro] to jit.qt.movie, and you should be fine.
>>>>
>>>> Here’s an example.
>>>>
>>>> max v2;
>>>> #N vpatcher 518 44 1118 444;
>>>> #P toggle 17 122 15 0;
>>>> #P window setfont "Sans Serif" 9.;
>>>> #P window linecount 1;
>>>> #P newex 17 143 46 196617 metro 5;
>>>> #P window setfont "Sans Serif" 12.;
>>>> #P comment 253 168 162 196620 3. change the position –>;
>>>> #P comment 194 134 145 196620 2. direct render;
>>>> #P window setfont "Sans Serif" 9.;
>>>> #P number 471 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>>>> #P number 421 160 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>>>> #P newex 371 216 110 196617 pak pos 0 0;
>>>> #P button 93 230 23 0;
>>>> #P newex 371 267 149 196617 jit.window ventana @noaccel 1;
>>>> #P message 111 136 82 196617 window ventana;
>>>> #P message 79 104 30 196617 read;
>>>> #P newex 79 271 63 196617 jit.qt.movie;
>>>> #P window setfont "Sans Serif" 12.;
>>>> #P comment 113 102 115 196620 1. read a movie;
>>>> #P connect 12 0 11 0;
>>>> #P connect 11 0 1 0;
>>>> #P connect 2 0 1 0;
>>>> #P fasten 3 0 1 0 116 210 84 210;
>>>> #P fasten 5 0 1 0 98 263 84 263;
>>>> #P connect 6 0 4 0;
>>>> #P connect 7 0 6 1;
>>>> #P connect 8 0 6 2;
>>>> #P pop;
>>>>
>>>>
>>>> Bryan
>>>> —
>>>> http://www.bryanteoh.com
>>>> http://www.ksod.net
>>>>
>>
>
>


June 15, 2007 | 10:19 am

You can add a couple of six packs from me as well.

This is the fundamental issue stopping me from using Max more professionally.

Being in the UK, most of what I film is in PAL. Converting everything to NTSC is a colossal headache, particularly with live events where things need to changed at the last minute.


June 15, 2007 | 10:37 am

Since I live in the same city as John, I think have a shot at
actually getting his promised reward, although I’ll attempt to hold
you to yours, if we can figure it out! ;)

I promise that we’ll look at this, but the honest truth is: we can’t
spend a lot of time on Jitter dev right now, until Max 5 is out the
door. Which is still a while away.

Thanks for your patience — there’s lots of things we’re planning to
address and to add to Jitter, so no worries about that. But as a
small company, we tend to have to focus resources on one major
project at a time.

Best,
jb

Am 15.06.2007 um 12:19 schrieb marcus lyall:

>
> You can add a couple of six packs from me as well.
>
>
> This is the fundamental issue stopping me from using Max more
> professionally.
>
> Being in the UK, most of what I film is in PAL. Converting
> everything to NTSC is a colossal headache, particularly with live
> events where things need to changed at the last minute.


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