Matthew Grouse

Hey! :-) I'm sure I'm just doing something really stupid and it's a simple fix but I'm having significant problems when movie files reach their end point.

I'm using jit.movie with the following arguments (@drawto patch @output_texture 1 @automatic 1 @autostart 0 @loop 0) - feeding jit.world.

qmetro is requesting frames from jit.movie at the frame rate of the video. If looping is turned on, there's no problem (but I don't want the video to loop) so when I give the argument @loop 0, then play the video (banging jit.movie with a 'start msg) and movie eventually reaches its end point, activity monitor (mac) shows my CPU skyrocketting and Max becomes unresponsive. I don't really understand what's happening here.

I'm getting round it currently in a clumsy way (sending a delayed bang to a 'dispose' msg sending to jit.movie a few milliseconds before the end of the file). I just basically want to understand what is happening when a movie files end when looping is turned off so I can avoid running into further problems.

I'm using jit.movie with the following arguments (@drawto patch @output_texture 1 @automatic 1 @autostart 0 @loop 0) - feeding jit.world. 

qmetro is requesting frames from jit.movie at the frame rate of the video. If looping is turned on, there's no problem (but I don't want the video to loop) so when I give the argument @loop 0, then play the video (banging jit.movie with a 'start msg) and movie eventually reaches its end point,  activity monitor (mac) shows my CPU skyrocketting and Max becomes unresponsive. I don't really understand what's happening here. 

Hey! :-) I'm sure I'm just doing something really stupid and it's a simple fix but I'm having significant problems when movie files reach th

CPU problem with jit.movie when it receives @loop 0