Gideon Kiers

hello, i have a problem. i'm running the latest versions of maxmsp 

jitter and osx on a quad g5 with a very clean second internal raptor 

a very simple patch, containing one metro, two quicktime players 720 

576, connected to two jit.pwindows and a 'read a.mov' and a 'read 

b.mov' message box, connected to each of the two qt players. when i 

load a different clip on one player, the output on the other player 

shows a hickup, the output stops for some miliseconds (it's very 

visible). is there a way to solve this ? of course there is the 

possibility of references movies, of one movieobject for each clip in 

a folder, etc. but i'm looking for a more elegant solution. i'm 

actually hoping i'm overlooking some incredibly efficient preload 

hello, i have a problem. i'm running the latest versions of maxmsp  
jitter and osx on a quad g5 with a very clean second internal raptor  
10000 rpm disk.
a very simple patch, containing one metro, two quicktime players 720  
576, connected to two jit.pwindows and a 'read a.mov' and a 'read  
b.mov' message box, connected to each of the two qt players. when i  
load a different clip on one player, the output on the other player  
shows a hickup, the output stops for some miliseconds (it's very  
visible). is there a way to solve this ? of course there is the  
possibility of references movies, of one movieobject for each clip in  
a folder, etc. but i'm looking for a more elegant solution. i'm  
actually hoping i'm overlooking some incredibly efficient preload  
quicktime function, but i guess not ..

quicktime-load-hickup

2. use absolute paths (as the time to search the search path based on 

3. preload all the movies in advance using poly~ or the JS or Java 

2. use absolute paths (as the time to search the search path based on  
filename alone is not insignificant)

3. preload all the movies in advance using poly~ or the JS or Java  
based examples

This helps me -- If you can anticipate all the files you're going to use, load them each once before starting your session. I find the load time the first time is noticeable, but subsequent loads are much less noticeable. I still typically get a little hiccup, just not as bad.

This helps me -- If you can anticipate all the files you're going to use, load them each once before starting your session.  I find the load time the first time is noticeable, but subsequent loads are much less noticeable.  I still typically get a little hiccup, just not as bad.

quicktime load hickup