could somebody explain to me what is the time unity of [imovie] (movie) ?

here's a patch to show if i use one movie, the time unity is 24 for 1 second, and for another movie it's 600 for 1 second.

i don't understand why, except maybe it depends of the fps of the movie.

in that case how to do to have always the same unity to control [imovie] ?

here's a patch to show if i use one movie, the time unity is 24 for 1 second, and for another movie it's 600 for 1 second.
i don't understand why, except maybe it depends of the fps of the movie.
in that case how to do to have always the same unity to control [imovie] ?

imove-time-unity

Even if you're not using Jitter, you might want to read the Jitter 

tutorials for a reasonably clear explanation of this.

Tutorial 4 and the QuickTime Confidential appendix should be helpful.

http://developer.apple.com/documentation/QuickTime/RM/MovieInternals/

MTTimeSpace/MTTimeSpace.pdf is the official description. Check the 

> could somebody explain to me what is the time unity of [imovie] 

> here's a patch to show if i use one movie, the time unity is 24 for 

> 1 second, and for another movie it's 600 for 1 second.

> i don't understand why, except maybe it depends of the fps of the 

> in that case how to do to have always the same unity to control 

Even if you're not using Jitter, you might want to read the Jitter  
tutorials for a reasonably clear explanation of this.

http://developer.apple.com/documentation/QuickTime/RM/MovieInternals/ 
MTTimeSpace/MTTimeSpace.pdf is the official description. Check the  
chapter on "Movie Time and Space".

> could somebody explain to me what is the time unity of [imovie]  
> (movie) ?
>
> here's a patch to show if i use one movie, the time unity is 24 for  
> 1 second, and for another movie it's 600 for 1 second.
> i don't understand why, except maybe it depends of the fps of the  
> movie.
> in that case how to do to have always the same unity to control  
> [imovie] ?


> Even if you're not using Jitter, you might want to read the Jitter 

> tutorials for a reasonably clear explanation of this.

It does explain the technical context, it does not explain why for 

example jit.gt.movie doesn't allow navigation by time. To do that simple 

calculation internally wouldn't hurt. And I can't imagine that the 

majority of users prefers to think in awkward units versus time, and 

even if, I can navigate in units, or in frames why not in time...

I came around by creating my own abhaXion for it, but still it doesn't 

explain it for me... The same is true for imovie I guess...

Maybe explanation is not enough... (another hint for Max 5... ;-)

Jeremy Bernstein schrieb:
> Even if you're not using Jitter, you might want to read the Jitter 
> tutorials for a reasonably clear explanation of this.

It does explain the technical context, it does not explain why for 
example jit.gt.movie doesn't allow navigation by time. To do that simple 
calculation internally wouldn't hurt. And I can't imagine that the 
majority of users prefers to think in awkward units versus time, and 
even if, I can navigate in units, or in frames why not in time...

I came around by creating my own abhaXion for it, but still it doesn't 
explain it for me... The same is true for imovie I guess...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


You might be interested in the "editmode" and "edittime" attributes.

One might also argue that media is best handled in their native time 

coordinates - in this case, QuickTime Time Units. For instance, many 

Pretending that QuickTime movies necessarily have regular frames or 

some sort of other timing resolution which they don't is misleading. 

Nevertheless, "editmode" and "edittime" do precisely this.

Am 24.04.2007 um 15:53 schrieb Stefan Tiedje:

>> Even if you're not using Jitter, you might want to read the Jitter 

>> tutorials for a reasonably clear explanation of this.

> It does explain the technical context, it does not explain why for 

> example jit.gt.movie doesn't allow navigation by time. To do that 

> simple calculation internally wouldn't hurt. And I can't imagine 

> that the majority of users prefers to think in awkward units versus 

> time, and even if, I can navigate in units, or in frames why not in 

> I came around by creating my own abhaXion for it, but still it 

> doesn't explain it for me... The same is true for imovie I guess...

> Maybe explanation is not enough... (another hint for Max 5... ;-)

One might also argue that media is best handled in their native time  
coordinates - in this case, QuickTime Time Units. For instance, many  
MSP objects handle time in samples.

Pretending that QuickTime movies necessarily have regular frames or  
some sort of other timing resolution which they don't is misleading.  
Nevertheless, "editmode" and "edittime" do precisely this.

> Jeremy Bernstein schrieb:
>> Even if you're not using Jitter, you might want to read the Jitter  
>> tutorials for a reasonably clear explanation of this.
>
> It does explain the technical context, it does not explain why for  
> example jit.gt.movie doesn't allow navigation by time. To do that  
> simple calculation internally wouldn't hurt. And I can't imagine  
> that the majority of users prefers to think in awkward units versus  
> time, and even if, I can navigate in units, or in frames why not in  
> time...
>
> I came around by creating my own abhaXion for it, but still it  
> doesn't explain it for me... The same is true for imovie I guess...
>
> Maybe explanation is not enough... (another hint for Max 5... ;-)
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>


it's a little bit clearer but not really useful.

ok, thx.
it's a little bit clearer but not really useful.

> You might be interested in the "editmode" and "edittime" attributes.

Thanks for the pointer, I think they should go into the main page of the 

> One might also argue that media is best handled in their native time 

> coordinates - in this case, QuickTime Time Units. For instance, many MSP 

I won't and didn't argue against that. But even for me as a sort of DSP 

expert, which deals a lot in samples, I mostly use milliseconds as the 

main unit. The artistic way of thinking which would deal with results 

rather than technical terms would always START thinking in real world 

units. And the most common one is time. Especially for beginners, the 

only units they know are the real world units. (consider me as a Jitter 

beginner...) That's why I think its essential that these real world 

units are the first and the default for most objects.

The help file should at least point to it directly... Though the docs 

list all commands, the important ones should be explained in the help 

file, especially with complex objects like jit.qt.movie. I consider all 

> Pretending that QuickTime movies necessarily have regular frames or some 

> sort of other timing resolution which they don't is misleading. 

> Nevertheless, "editmode" and "edittime" do precisely this.

Yes, that will simplify life, until the defaults in Max 5 are user 

Jeremy Bernstein schrieb:
> You might be interested in the "editmode" and "edittime" attributes.

Thanks for the pointer, I think they should go into the main page of the 
help file.

> One might also argue that media is best handled in their native time 
> coordinates - in this case, QuickTime Time Units. For instance, many MSP 
> objects handle time in samples.

I won't and didn't argue against that. But even for me as a sort of DSP 
expert, which deals a lot in samples, I mostly use milliseconds as the 
main unit. The artistic way of thinking which would deal with results 
rather than technical terms would always START thinking in real world 
units. And the most common one is time. Especially for beginners, the 
only units they know are the real world units. (consider me as a Jitter 
beginner...) That's why I think its essential that these real world 
units are the first and the default for most objects.
The help file should at least point to it directly... Though the docs 
list all commands, the important ones should be explained in the help 
file, especially with complex objects like jit.qt.movie. I consider all 
real world units to be important....

> Pretending that QuickTime movies necessarily have regular frames or some 
> sort of other timing resolution which they don't is misleading. 
> Nevertheless, "editmode" and "edittime" do precisely this.

Yes, that will simplify life, until the defaults in Max 5 are user 
definable I'll make a prototype...

>> You might be interested in the "editmode" and "edittime" attributes.

what is it ?
wher to find infos about that ?
thx.

>>> You might be interested in the "editmode" and "edittime" attributes.

>>> You might be interested in the "editmode" and "edittime" attributes.
>
> what is it ?
> wher to find infos about that ?
> thx.
>
>


imove time unity ?