One could send the message "frame my_first_frame_number" and then "jump
1" until you've gotten to the frame you want (my_last_frame_number -
Or one could calculate the frame number based on the movie's timescale
(gettimescale / getfps = number of time units per frame) and then use
looppoints to set the first and last frame (@loop 3 will do a
single-cycle read from the beginning to the end).
Or you get set @editmode to 2 (frame) or 3 (frame_true) and set
looppoints directly in frames.
The jit.qt.movie object uses QuickTime time units rather that
what you're referring to as "frames" when specifying things
like loops. I'm not sure whether this is potentially a language
problem or not - that is, your use of the phrase "from this
frame to this other frame" refers to a time point in a QuickTime
move rather than an explicit frame [The QuickTime confidential
appendix in the tutorial goes over some of this]. If so, you should
have a look at the loop and looppoints messages to the
jit.qt.movie object, either in the help file or the online Reference
Manual page (which is accessible from the help file).
If you *really* mean a frame, you have access to the frame
message which will display an explicit frame of a QuickTime
movie [the getframecount message can be used to find out
how many of them there are in a movie]. Again, have a look at
the Reference manual pages.
The Jitter tutorial covers the use of the "get" messages (e.g.,
getframecount, getduration), which you'll find useful.
i'm not sure about the convenience of this message in this list...
however, the matter is jitter related and perhaps some of you have
already run over this situation.
i've installed windows xp system pack 2 in a power book pro 2.0 GHz.
macosx partition is about 70 Gbytes and windows partition is 20 Gbytes.
maxmsp seems work properly : it was installed without any problems,
objects instantiate and msp produces sound.
jitter doesn't behave normally:
when trying to install it, the installer claims for .NET framework
and suggests a visit to the download page.
after downloading and installing .NET framework from the suggested
page and trying to install jitter again , the installer displays a
box claiming for version 1.14...
actually, the installed version from this page was 2.0...
once version 2.0 has been uninstalled and version 1.1 downloaded and
installed, the jitter installation appers to be normal. the problem
arises when launching maxmsp-jitter : the launching process never
ends, even crashes... sometimes, in the scrollbars of the max window,
some rests of the regular splashscreen image of maxmsp remain. when
trying to click somwhere, maxmsp doesn't respond anymore and must be
killed to regain control.
after uninstalling jitter, maxmsp works again
reinstalling maxmsp and jitter again yields the described behaviour.
am i missing something? must i delete some archive somewhere? should
i reinstall windows?
You will need to make sure your Windows partition has Quicktime and Java
installed for Jitter to function properly.
The .NET nag is just an installer quirk, and won't be present in the
next version of Jitter.