CKNY

I render my movies and put in the jitter but I found the timing is not right. I read many of the articles here but I still want to know is there a "right answer" of qmetro settings of different fps.

If I render my movies as 30 fps, 640x480, what should I set with the qmetro?

If I render my movies as 29.97 non-drop 640x480, what is the best setting of qmetro?

If I render my movies as 29.97 drop 640x480, is the setting still the same with 29.97 non-drop?

I haven't tried it yet because some people said here that it is not recommend. Should I change qmetro settings if I put HD formate or very high resolution movies?

I render my movies and put in the jitter but I found the timing is not right. I read many of the articles here but I still want to know is there  a "right answer" of qmetro settings of different fps.

so-whats-the-best-settings-for-qmetro-of-different-fps

by rendering movies you mean to record them to harddisk via jit.record?

as long as you set 'realtime 0' the qmetro settings are less relevant to the

duration of your rendered movie as the timescale setting.

in realtime 0 mode every incoming frame is supposed to be the next frame in the

for pal content timescale should be set to 800. not realy shure about ntsc

> I render my movies and put in the jitter but I found the timing is not right.

> I read many of the articles here but I still want to know is there a "right

> answer" of qmetro settings of different fps.

> If I render my movies as 30 fps, 640x480, what should I set with the qmetro?

> If I render my movies as 29.97 non-drop 640x480, what is the best setting of

> If I render my movies as 29.97 drop 640x480, is the setting still the same

> I haven't tried it yet because some people said here that it is not

> recommend. Should I change qmetro settings if I put HD formate or very high

----------------------------------------------------------------

This message was sent using IMP, the Internet Messaging Program.

by rendering movies you mean to record them to harddisk via jit.record?
as long as you set 'realtime 0' the qmetro settings are less relevant to the
duration of your rendered movie as the timescale setting.
in realtime 0 mode every incoming frame is supposed to be the next frame in the
rendered video,
for pal content timescale should be set to 800. not realy shure about ntsc
though.

>
> Hi,
>
> I render my movies and put in the jitter but I found the timing is not right.
> I read many of the articles here but I still want to know is there  a "right
> answer" of qmetro settings of different fps.
>
> If I render my movies as 30 fps, 640x480, what should I set with the qmetro?
>
> If I render my movies as 29.97 non-drop 640x480, what is the best setting of
> qmetro?
>
> If I render my movies as 29.97 drop 640x480, is the setting still the same
> with 29.97 non-drop?
>
> I haven't tried it yet because some people said here that it is not
> recommend. Should I change qmetro settings if I put HD formate or very high
> resolution movies?
>
> thank you so much
>
>

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


I believe it is 600, but im not positive :X

On Aug 10, 2007, at 3:35 PM, sm@xdv.org wrote:

> by rendering movies you mean to record them to harddisk via 

> as long as you set 'realtime 0' the qmetro settings are less 

> duration of your rendered movie as the timescale setting.

> in realtime 0 mode every incoming frame is supposed to be the next 

> for pal content timescale should be set to 800. not realy shure 

>> I render my movies and put in the jitter but I found the timing is 

>> I read many of the articles here but I still want to know is 

>> answer" of qmetro settings of different fps.

>> If I render my movies as 30 fps, 640x480, what should I set with 

>> If I render my movies as 29.97 non-drop 640x480, what is the best 

>> If I render my movies as 29.97 drop 640x480, is the setting still 

>> I haven't tried it yet because some people said here that it is not

>> recommend. Should I change qmetro settings if I put HD formate or 

> ----------------------------------------------------------------

> This message was sent using IMP, the Internet Messaging Program.

> by rendering movies you mean to record them to harddisk via  
> jit.record?
> as long as you set 'realtime 0' the qmetro settings are less  
> relevant to the
> duration of your rendered movie as the timescale setting.
> in realtime 0 mode every incoming frame is supposed to be the next  
> frame in the
> rendered video,
> for pal content timescale should be set to 800. not realy shure  
> about ntsc
> though.
>
> Quoting UCDMSRA :
>
>>
>> Hi,
>>
>> I render my movies and put in the jitter but I found the timing is  
>> not right.
>> I read many of the articles here but I still want to know is  
>> there  a "right
>> answer" of qmetro settings of different fps.
>>
>> If I render my movies as 30 fps, 640x480, what should I set with  
>> the qmetro?
>>
>> If I render my movies as 29.97 non-drop 640x480, what is the best  
>> setting of
>> qmetro?
>>
>> If I render my movies as 29.97 drop 640x480, is the setting still  
>> the same
>> with 29.97 non-drop?
>>
>> I haven't tried it yet because some people said here that it is not
>> recommend. Should I change qmetro settings if I put HD formate or  
>> very high
>> resolution movies?
>>
>> thank you so much
>>
>>
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.

Quote: sm wrote on Fri, 10 August 2007 13:35

----------------------------------------------------

> by rendering movies you mean to record them to harddisk via jit.record?

> as long as you set 'realtime 0' the qmetro settings are less relevant to the

> in realtime 0 mode every incoming frame is supposed to be the next frame in the

> for pal content timescale should be set to 800. not realy shure about ntsc

> > I render my movies and put in the jitter but I found the timing is not right.

> > I read many of the articles here but I still want to know is there a "right

> > answer" of qmetro settings of different fps.

> > If I render my movies as 30 fps, 640x480, what should I set with the qmetro?

> > If I render my movies as 29.97 non-drop 640x480, what is the best setting of

> > If I render my movies as 29.97 drop 640x480, is the setting still the same

> > I haven't tried it yet because some people said here that it is not

> > recommend. Should I change qmetro settings if I put HD formate or very high

Hmm.....well, the information you told me I didn't know so that's very good. However, I think what I want to say is if I render my movie in After Effects or editing my movie at Final Cut Pro. Why my movie end of play different speed when pull into jitter? All the movies I rendered out was 20:00 seconds. I render the movies as 29.97 fps non-drop. However, I found that it will playback less than 20 seconds in jitter (I think maybe 0.5 to 1 second different). Why is that? What did I do wrong, is the problem with "qmetro" settings?

Quote: sm wrote on Fri, 10 August 2007 13:35
----------------------------------------------------
> by rendering movies you mean to record them to harddisk via jit.record?
> as long as you set 'realtime 0' the qmetro settings are less relevant to the
> duration of your rendered movie as the timescale setting.
> in realtime 0 mode every incoming frame is supposed to be the next frame in the
> rendered video,
> for pal content timescale should be set to 800. not realy shure about ntsc
> though.
>
> Quoting UCDMSRA :
>
> >
> > Hi,
> >
> > I render my movies and put in the jitter but I found the timing is not right.
> > I read many of the articles here but I still want to know is there  a "right
> > answer" of qmetro settings of different fps.
> >
> > If I render my movies as 30 fps, 640x480, what should I set with the qmetro?
> >
> > If I render my movies as 29.97 non-drop 640x480, what is the best setting of
> > qmetro?
> >
> > If I render my movies as 29.97 drop 640x480, is the setting still the same
> > with 29.97 non-drop?
> >
> > I haven't tried it yet because some people said here that it is not
> > recommend. Should I change qmetro settings if I put HD formate or very high
> > resolution movies?
> >
> > thank you so much
> >
> >
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
----------------------------------------------------

Hmm.....well, the information you told me I didn't know so that's  very good. However, I think what I want to say is if I render my movie in After Effects or editing my movie at Final Cut Pro. Why my movie end of play different speed when pull into jitter? All the movies I rendered out was 20:00 seconds. I render the movies as 29.97 fps non-drop. However, I found that it will playback less than 20 seconds in jitter (I think maybe 0.5 to 1 second different). Why is that? What did I do wrong, is the problem with "qmetro" settings?

Try [qmetro 2] --> [qlim 33.333] --> [jit.qt.movie]. 

the qmetro setting has most definitely nothing to with the playback speed of you

movie.did you change the 'rate' parameter in jitter?

the qmetro just forces jit.movie do put out a frame each bang while the runs on

anyhow, to help you fix the problem you should provide your patch - a striped

down version - and a short part of you misbehaving movies.

> Quote: sm wrote on Fri, 10 August 2007 13:35

> ----------------------------------------------------

> > by rendering movies you mean to record them to harddisk via jit.record?

> > as long as you set 'realtime 0' the qmetro settings are less relevant to

> > duration of your rendered movie as the timescale setting.

> > in realtime 0 mode every incoming frame is supposed to be the next frame in

> > for pal content timescale should be set to 800. not realy shure about ntsc

> > > I render my movies and put in the jitter but I found the timing is not

> > > I read many of the articles here but I still want to know is there a

> > > answer" of qmetro settings of different fps.

> > > If I render my movies as 30 fps, 640x480, what should I set with the

> > > If I render my movies as 29.97 non-drop 640x480, what is the best setting

> > > If I render my movies as 29.97 drop 640x480, is the setting still the

> > > I haven't tried it yet because some people said here that it is not

> > > recommend. Should I change qmetro settings if I put HD formate or very

> > ----------------------------------------------------------------

> > This message was sent using IMP, the Internet Messaging Program.

the qmetro setting has most definitely nothing to with the playback speed of you
 movie.did you change the 'rate' parameter in jitter?
the qmetro just forces jit.movie do put out a frame each bang while the runs on
its own speed - determined by rate.

anyhow, to help you fix the problem you should provide your patch - a striped
down version - and a short part of you misbehaving movies.
cheers

>
> Quote: sm wrote on Fri, 10 August 2007 13:35
> ----------------------------------------------------
> > by rendering movies you mean to record them to harddisk via jit.record?
> > as long as you set 'realtime 0' the qmetro settings are less relevant to
> the
> > duration of your rendered movie as the timescale setting.
> > in realtime 0 mode every incoming frame is supposed to be the next frame in
> the
> > rendered video,
> > for pal content timescale should be set to 800. not realy shure about ntsc
> > though.
> >
> > Quoting UCDMSRA :
> >
> > >
> > > Hi,
> > >
> > > I render my movies and put in the jitter but I found the timing is not
> right.
> > > I read many of the articles here but I still want to know is there  a
> "right
> > > answer" of qmetro settings of different fps.
> > >
> > > If I render my movies as 30 fps, 640x480, what should I set with the
> qmetro?
> > >
> > > If I render my movies as 29.97 non-drop 640x480, what is the best setting
> of
> > > qmetro?
> > >
> > > If I render my movies as 29.97 drop 640x480, is the setting still the
> same
> > > with 29.97 non-drop?
> > >
> > > I haven't tried it yet because some people said here that it is not
> > > recommend. Should I change qmetro settings if I put HD formate or very
> high
> > > resolution movies?
> > >
> > > thank you so much
> > >
> > >
> >
> >
> >
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> ----------------------------------------------------
>
> Hmm.....well, the information you told me I didn't know so that's  very good.
> However, I think what I want to say is if I render my movie in After Effects
> or editing my movie at Final Cut Pro. Why my movie end of play different
> speed when pull into jitter? All the movies I rendered out was 20:00 seconds.
> I render the movies as 29.97 fps non-drop. However, I found that it will
> playback less than 20 seconds in jitter (I think maybe 0.5 to 1 second
> different). Why is that? What did I do wrong, is the problem with "qmetro"
> settings?
>
> thanks
>
>

Quote: sm wrote on Sat, 11 August 2007 11:31

> the qmetro setting has most definitely nothing to with the playback speed of you

> movie.did you change the 'rate' parameter in jitter?

> the qmetro just forces jit.movie do put out a frame each bang while the runs on

> anyhow, to help you fix the problem you should provide your patch - a striped

> down version - and a short part of you misbehaving movies.

> > Quote: sm wrote on Fri, 10 August 2007 13:35

> > ----------------------------------------------------

> > > by rendering movies you mean to record them to harddisk via jit.record?

> > > as long as you set 'realtime 0' the qmetro settings are less relevant to

> > > duration of your rendered movie as the timescale setting.

> > > in realtime 0 mode every incoming frame is supposed to be the next frame in

> > > for pal content timescale should be set to 800. not realy shure about ntsc

> > > > I render my movies and put in the jitter but I found the timing is not

> > > > I read many of the articles here but I still want to know is there a

> > > > answer" of qmetro settings of different fps.

> > > > If I render my movies as 30 fps, 640x480, what should I set with the

> > > > If I render my movies as 29.97 non-drop 640x480, what is the best setting

> > > > If I render my movies as 29.97 drop 640x480, is the setting still the

> > > > I haven't tried it yet because some people said here that it is not

> > > > recommend. Should I change qmetro settings if I put HD formate or very

I spent few days tried to figure out what is this patch and hope I can do some adjustment but......I just messed everything up.

Actually this is just a example patch from Max help file about how to load bunch of movies from one folder and playback randomly. There are two things I think I will never figure it out unless someone help me.

1. I hope I can read the movies in uyvy mode, I am not sure in this patch the movies are readed in uyvy mode because when I tried to mix the movies in uyvy mode, the colors became very weird.

2. I set the random metro to 20000 because all my movies are 20 seconds and I rendered my movies as 29.97fps non-drop. I hope every time my movies play is gonna be from beginning to the end. However, "sometimes" the movie suddenly jump out in the middle and that's why it makes me think maybe the metro setting is wrong.

Here is the patch, I post the original one, not the one after I fixed (it doesn't work anyway).....because I don't want you get more confused.

Quote: sm wrote on Sat, 11 August 2007 11:31
----------------------------------------------------
> the qmetro setting has most definitely nothing to with the playback speed of you
>  movie.did you change the 'rate' parameter in jitter?
> the qmetro just forces jit.movie do put out a frame each bang while the runs on
> its own speed - determined by rate.
>
> anyhow, to help you fix the problem you should provide your patch - a striped
> down version - and a short part of you misbehaving movies.
> cheers
>
> Quoting UCDMSRA :
>
> >
> > Quote: sm wrote on Fri, 10 August 2007 13:35
> > ----------------------------------------------------
> > > by rendering movies you mean to record them to harddisk via jit.record?
> > > as long as you set 'realtime 0' the qmetro settings are less relevant to
> > the
> > > duration of your rendered movie as the timescale setting.
> > > in realtime 0 mode every incoming frame is supposed to be the next frame in
> > the
> > > rendered video,
> > > for pal content timescale should be set to 800. not realy shure about ntsc
> > > though.
> > >
> > > Quoting UCDMSRA :
> > >
> > > >
> > > > Hi,
> > > >
> > > > I render my movies and put in the jitter but I found the timing is not
> > right.
> > > > I read many of the articles here but I still want to know is there  a
> > "right
> > > > answer" of qmetro settings of different fps.
> > > >
> > > > If I render my movies as 30 fps, 640x480, what should I set with the
> > qmetro?
> > > >
> > > > If I render my movies as 29.97 non-drop 640x480, what is the best setting
> > of
> > > > qmetro?
> > > >
> > > > If I render my movies as 29.97 drop 640x480, is the setting still the
> > same
> > > > with 29.97 non-drop?
> > > >
> > > > I haven't tried it yet because some people said here that it is not
> > > > recommend. Should I change qmetro settings if I put HD formate or very
> > high
> > > > resolution movies?
> > > >
> > > > thank you so much
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > ----------------------------------------------------------------
> > > This message was sent using IMP, the Internet Messaging Program.
> > >
> > ----------------------------------------------------
> >
> > Hmm.....well, the information you told me I didn't know so that's  very good.
> > However, I think what I want to say is if I render my movie in After Effects
> > or editing my movie at Final Cut Pro. Why my movie end of play different
> > speed when pull into jitter? All the movies I rendered out was 20:00 seconds.
> > I render the movies as 29.97 fps non-drop. However, I found that it will
> > playback less than 20 seconds in jitter (I think maybe 0.5 to 1 second
> > different). Why is that? What did I do wrong, is the problem with "qmetro"
> > settings?
> >
> > thanks
> >
> >
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
----------------------------------------------------

Actually this is just a example patch from Max help file about how to load bunch of movies from one folder and playback randomly. There are two things I think I will never figure it out unless someone help me. 

2. I set the random metro to 20000 because all my movies are 20 seconds and I rendered my movies as 29.97fps non-drop. I hope every time my movies play is gonna be from beginning to the end. However, "sometimes" the movie suddenly jump out in the middle and that's why it makes me think maybe the metro setting is wrong. 

#1 - Drop frame only refers to time code - and only really useful if 

outputting to a tape or a VTR device. You should not need it in 

#2 What is important is the FPS. and number of frames, and the QTUNIT 

As was said before, if your movie is rate 1.0, and you realize that 

unless you have autoplay disabled, a movie will start playing 

So to time a movie, autostart = 0, rate = 1, start timer and play at 

this patch loads any movie, and times it in seconds. compare to your 

I loaded a movie that was 18.38 seconds according to QT player, and 

#1 - Drop frame only refers to time code - and only really useful if  
outputting to a tape or a VTR device. You should not need it in  
jitter at all.

#2 What is important is the FPS. and number of frames, and the QTUNIT  
- this determines the duration.

As was said before, if your movie is rate 1.0, and you realize that  
unless you have autoplay disabled, a movie will start playing  
immediately.

So to time a movie, autostart = 0, rate = 1, start timer and play at  
the same time, report when movie loops.

this patch loads any movie, and times it in seconds. compare to your  
movies.

I loaded a movie that was 18.38 seconds according to QT player, and  
the timer returned 18.4

Quote: vade wrote on Sun, 19 August 2007 23:35

> #1 - Drop frame only refers to time code - and only really useful if 

> outputting to a tape or a VTR device. You should not need it in 

> #2 What is important is the FPS. and number of frames, and the QTUNIT 

> As was said before, if your movie is rate 1.0, and you realize that 

> unless you have autoplay disabled, a movie will start playing 

> So to time a movie, autostart = 0, rate = 1, start timer and play at 

> the same time, report when movie loops.

> this patch loads any movie, and times it in seconds. compare to your 

> I loaded a movie that was 18.38 seconds according to QT player, and 

> #P flonum 462 259 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 456 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P user jit.pwindow 169 254 82 62 0 1 0 0 1 0;

> #P message 187 61 104 196617 time 0 , start , rate 1;

> #P newex 368 212 82 196617 route loopnotify;

> #P newex 145 163 274 196617 jit.qt.movie @loopreport 1 @autostart 0 

I got it....but how to apply it in the patch I posted above? The patch I posted above is actually the example patch of jsmoviebank.js, I don't know how to do the adjustment according to what you told me. jx code is just still complicate to me....... I don't even sure all the movies are read as uyvy modes or RGB modes. (I hope my movies can be read as uyvy modes)

I need to load a bunch of movies once at a time and play them back randomly. In the jitter this patch is the only example about how to load many movies and playback. Can you check out the js code for me or tell me how to read those codes? I tried but I really don't understand most of them.

Quote: vade wrote on Sun, 19 August 2007 23:35
----------------------------------------------------
> Ok.
>
> #1 - Drop frame only refers to time code - and only really useful if  
> outputting to a tape or a VTR device. You should not need it in  
> jitter at all.
>
> #2 What is important is the FPS. and number of frames, and the QTUNIT  
> - this determines the duration.
>
> As was said before, if your movie is rate 1.0, and you realize that  
> unless you have autoplay disabled, a movie will start playing  
> immediately.
>
> So to time a movie, autostart = 0, rate = 1, start timer and play at  
> the same time, report when movie loops.
>
> this patch loads any movie, and times it in seconds. compare to your  
> movies.
>
> I loaded a movie that was 18.38 seconds according to QT player, and  
> the timer returned 18.4
>
> :)
>
> #P window setfont "Sans Serif" 9.;
> #P flonum 462 259 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P window linecount 1;
> #P newex 469 218 46 196617 / 1000.;
> #P flonum 456 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P button 394 248 15 0;
> #P user jit.pwindow 169 254 82 62 0 1 0 0 1 0;
> #P button 93 96 15 0;
> #P button 248 96 15 0;
> #P message 216 134 30 196617 read;
> #P newex 401 187 32 196617 print;
> #P newex 411 116 35 196617 timer;
> #P message 187 61 104 196617 time 0 , start , rate 1;
> #P newex 368 212 82 196617 route loopnotify;
> #P newex 145 163 274 196617 jit.qt.movie @loopreport 1 @autostart 0  
> @adapt 1 @loop 1;
> #P connect 11 0 12 0;
> #P connect 10 0 11 0;
> #P connect 3 0 10 0;
> #P connect 9 0 3 1;
> #P connect 1 0 9 0;
> #P connect 2 0 0 0;
> #P connect 2 0 6 0;
> #P connect 0 0 8 0;
> #P connect 7 0 0 0;
> #P connect 0 1 1 0;
> #P connect 0 1 4 0;
> #P connect 5 0 0 0;
> #P connect 6 0 3 0;
> #P window clipboard copycount 13;
>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>
----------------------------------------------------

now autostart and rate seems right but uyvy is still a problem. Would you please tell me how should I fix this?

Quote: vade wrote on Sun, 19 August 2007 23:35
----------------------------------------------------
> Ok.
>
> #1 - Drop frame only refers to time code - and only really useful if  
> outputting to a tape or a VTR device. You should not need it in  
> jitter at all.
>
> #2 What is important is the FPS. and number of frames, and the QTUNIT  
> - this determines the duration.
>
> As was said before, if your movie is rate 1.0, and you realize that  
> unless you have autoplay disabled, a movie will start playing  
> immediately.
>
> So to time a movie, autostart = 0, rate = 1, start timer and play at  
> the same time, report when movie loops.
>
> this patch loads any movie, and times it in seconds. compare to your  
> movies.
>
> I loaded a movie that was 18.38 seconds according to QT player, and  
> the timer returned 18.4
>
> :)
>
> 

Why do you need uyvy ? is your window also set to @colormode uyvy ?

With uyvy - its really most useful with GPU based effects, as 99% of 

the matrix based processing effects are written with the assumption 

of ARGB colors, not UYVY, so things like contrast, saturation etc 

On Aug 20, 2007, at 11:57 AM, UCDMSRA wrote:

> Quote: vade wrote on Sun, 19 August 2007 23:35

>> #1 - Drop frame only refers to time code - and only really useful if

>> outputting to a tape or a VTR device. You should not need it in

>> #2 What is important is the FPS. and number of frames, and the QTUNIT

>> As was said before, if your movie is rate 1.0, and you realize that

>> unless you have autoplay disabled, a movie will start playing

>> So to time a movie, autostart = 0, rate = 1, start timer and play at

>> the same time, report when movie loops.

>> this patch loads any movie, and times it in seconds. compare to your

>> I loaded a movie that was 18.38 seconds according to QT player, and

>> #P flonum 462 259 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P flonum 456 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P user jit.pwindow 169 254 82 62 0 1 0 0 1 0;

>> #P message 187 61 104 196617 time 0 , start , rate 1;

>> #P newex 368 212 82 196617 route loopnotify;

>> #P newex 145 163 274 196617 jit.qt.movie @loopreport 1 @autostart 0

With uyvy - its really most useful with GPU based effects, as 99% of  
the matrix based processing effects are written with the assumption  
of ARGB colors, not UYVY, so things like contrast, saturation etc  
dont 'work' as expected with UYVY data.

>
> Quote: vade wrote on Sun, 19 August 2007 23:35
> ----------------------------------------------------
>> Ok.
>>
>> #1 - Drop frame only refers to time code - and only really useful if
>> outputting to a tape or a VTR device. You should not need it in
>> jitter at all.
>>
>> #2 What is important is the FPS. and number of frames, and the QTUNIT
>> - this determines the duration.
>>
>> As was said before, if your movie is rate 1.0, and you realize that
>> unless you have autoplay disabled, a movie will start playing
>> immediately.
>>
>> So to time a movie, autostart = 0, rate = 1, start timer and play at
>> the same time, report when movie loops.
>>
>> this patch loads any movie, and times it in seconds. compare to your
>> movies.
>>
>> I loaded a movie that was 18.38 seconds according to QT player, and
>> the timer returned 18.4
>>
>> :)
>>
>> #P window setfont "Sans Serif" 9.;
>> #P flonum 462 259 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P window linecount 1;
>> #P newex 469 218 46 196617 / 1000.;
>> #P flonum 456 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P button 394 248 15 0;
>> #P user jit.pwindow 169 254 82 62 0 1 0 0 1 0;
>> #P button 93 96 15 0;
>> #P button 248 96 15 0;
>> #P message 216 134 30 196617 read;
>> #P newex 401 187 32 196617 print;
>> #P newex 411 116 35 196617 timer;
>> #P message 187 61 104 196617 time 0 , start , rate 1;
>> #P newex 368 212 82 196617 route loopnotify;
>> #P newex 145 163 274 196617 jit.qt.movie @loopreport 1 @autostart 0
>> @adapt 1 @loop 1;
>> #P connect 11 0 12 0;
>> #P connect 10 0 11 0;
>> #P connect 3 0 10 0;
>> #P connect 9 0 3 1;
>> #P connect 1 0 9 0;
>> #P connect 2 0 0 0;
>> #P connect 2 0 6 0;
>> #P connect 0 0 8 0;
>> #P connect 7 0 0 0;
>> #P connect 0 1 1 0;
>> #P connect 0 1 4 0;
>> #P connect 5 0 0 0;
>> #P connect 6 0 3 0;
>> #P window clipboard copycount 13;
>>
>>
>> v a d e //
>>
>> www.vade.info
>> abstrakt.vade.info
>>
>>
>>
>>
>>
>>
> ----------------------------------------------------
>
> Hi Vade,
>
> I guess I need to put the following js code in the js file:
>
> movearray[vcount].autostart = 0;
> movearray[vcount].rate = 1;
> movearray[vcount].readmode = uyvy;
>
> now autostart and rate seems right but uyvy is still a problem.  
> Would you please tell me how should I fix this?
>
> thank you so much
>
> CK

Quote: vade wrote on Mon, 20 August 2007 10:45

> Why do you need uyvy ? is your window also set to @colormode uyvy ?

> With uyvy - its really most useful with GPU based effects, as 99% of 

> the matrix based processing effects are written with the assumption 

> of ARGB colors, not UYVY, so things like contrast, saturation etc 

> dont 'work' as expected with UYVY data.

> On Aug 20, 2007, at 11:57 AM, UCDMSRA wrote:

> > Quote: vade wrote on Sun, 19 August 2007 23:35

> >> #1 - Drop frame only refers to time code - and only really useful if

> >> outputting to a tape or a VTR device. You should not need it in

> >> #2 What is important is the FPS. and number of frames, and the QTUNIT

> >> As was said before, if your movie is rate 1.0, and you realize that

> >> unless you have autoplay disabled, a movie will start playing

> >> So to time a movie, autostart = 0, rate = 1, start timer and play at

> >> the same time, report when movie loops.

> >> this patch loads any movie, and times it in seconds. compare to your

> >> I loaded a movie that was 18.38 seconds according to QT player, and

> >> #P flonum 462 259 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> >> #P flonum 456 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> >> #P user jit.pwindow 169 254 82 62 0 1 0 0 1 0;

Yes, I run all my movies in jit.gl.texture, jit.gl.videoplane and jit.gl.slab in 3D space. I also use your Shader Beta 1 (again, that is awesome) for some color change and fade in/ fade out. The problem is I ran over 10 different movies in jit.gl.videoplane and I got over 5 different shaders run in the same window at the same time. Sometimes I still got slow response and weird movie timing. That's why I think maybe I should use uyvy mode to save my poor ATI Radeon 9600 as possible as I can.

However, according to what you said, uyvy may bring me more problem right? What should I do?

Quote: vade wrote on Mon, 20 August 2007 10:45
----------------------------------------------------
> Why do you need uyvy ? is your window also set to @colormode uyvy ?
>
> With uyvy - its really most useful with GPU based effects, as 99% of  
> the matrix based processing effects are written with the assumption  
> of ARGB colors, not UYVY, so things like contrast, saturation etc  
> dont 'work' as expected with UYVY data.
>
>
>
> On Aug 20, 2007, at 11:57 AM, UCDMSRA wrote:
>
> >
> > Quote: vade wrote on Sun, 19 August 2007 23:35
> > ----------------------------------------------------
> >> Ok.
> >>
> >> #1 - Drop frame only refers to time code - and only really useful if
> >> outputting to a tape or a VTR device. You should not need it in
> >> jitter at all.
> >>
> >> #2 What is important is the FPS. and number of frames, and the QTUNIT
> >> - this determines the duration.
> >>
> >> As was said before, if your movie is rate 1.0, and you realize that
> >> unless you have autoplay disabled, a movie will start playing
> >> immediately.
> >>
> >> So to time a movie, autostart = 0, rate = 1, start timer and play at
> >> the same time, report when movie loops.
> >>
> >> this patch loads any movie, and times it in seconds. compare to your
> >> movies.
> >>
> >> I loaded a movie that was 18.38 seconds according to QT player, and
> >> the timer returned 18.4
> >>
> >> :)
> >>
> >> #P window setfont "Sans Serif" 9.;
> >> #P flonum 462 259 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> >> #P window linecount 1;
> >> #P newex 469 218 46 196617 / 1000.;
> >> #P flonum 456 170 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> >> #P button 394 248 15 0;
> >> #P user jit.pwindow 169 254 82 62 0 1 0 0 1 0;
> >> #P button 93 96 15 0;
> >> #P button 248 96 15 0;
> >> #P message 216 134 30 196617 read;
> >> #P newex 401 187 32 196617 print;
> >> #P newex 411 116 35 196617 timer;
> >> #P message 187 61 104 196617 time 0 , start , rate 1;
> >> #P newex 368 212 82 196617 route loopnotify;
> >> #P newex 145 163 274 196617 jit.qt.movie @loopreport 1 @autostart 0
> >> @adapt 1 @loop 1;
> >> #P connect 11 0 12 0;
> >> #P connect 10 0 11 0;
> >> #P connect 3 0 10 0;
> >> #P connect 9 0 3 1;
> >> #P connect 1 0 9 0;
> >> #P connect 2 0 0 0;
> >> #P connect 2 0 6 0;
> >> #P connect 0 0 8 0;
> >> #P connect 7 0 0 0;
> >> #P connect 0 1 1 0;
> >> #P connect 0 1 4 0;
> >> #P connect 5 0 0 0;
> >> #P connect 6 0 3 0;
> >> #P window clipboard copycount 13;
> >>
> >>
> >> v a d e //
> >>
> >> www.vade.info
> >> abstrakt.vade.info
> >>
> >>
> >>
> >>
> >>
> >>
> > ----------------------------------------------------
> >
> > Hi Vade,
> >
> > I guess I need to put the following js code in the js file:
> >
> > movearray[vcount].autostart = 0;
> > movearray[vcount].rate = 1;
> > movearray[vcount].readmode = uyvy;
> >
> > now autostart and rate seems right but uyvy is still a problem.  
> > Would you please tell me how should I fix this?
> >
> > thank you so much
> >
> > CK
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>
----------------------------------------------------

Yes, I run all my movies in jit.gl.texture, jit.gl.videoplane and jit.gl.slab in 3D space. I also use your Shader Beta 1 (again, that is awesome) for some color change and fade in/ fade out. The problem is I ran over 10 different movies in jit.gl.videoplane and I got over 5 different shaders run in the same window at the same time. Sometimes I still got slow response  and weird movie timing. That's why I think maybe I should use uyvy mode to save my poor ATI Radeon 9600 as possible as I can.

No, uyvy is not *more* of a problem, but be aware:

if you are on windows XP you should use the uyvy2rgba conversion 

So, what's the best settings for qmetro of different fps?