can somebody explain to me how the jump instance is supposed to work?
and or if there is a funktion where you can jump to the end of the movie since i am trying to make the loop also work in reverse (speed = -1).

Without using a profiler I can't really tell you. The movie as such should not eat all that memory, because the whole movie is never loaded, just frames. Do you maybe store frames or process lots of frames somewhere? What is the resolution of the movie. Otherwise we might have amemory leak, maybe someone with a profiler and some spare time can check this?

Anyhow, in general playing very big movies is problematic, as the implementation, due to having to deal with processing, is still suboptimal, and I myself fell back to a pure java solution with lots of glue and magick back on the project I devloped fm for.

void setup ()
{
 myMouseWheel = new MyMouseWheel();
 frame.addMouseWheelListener(myMouseWheel);
 
 
   //size(1152,768);
   size (800,300);
   
   fma = new FasterMovie(this, "round_web.mov", false);
   fma.loop();
   
   //fmb = new FasterMovie(this, "muede_small.mov",false);
   //fmb.loop();
   
   fill (0);
   noStroke ();
   background( 0 );
   

 
}

void draw ()
{
 
 if (myMouseWheel.wasMoved==false){
   wheelspeed = 0 ;
   count++;
    }
  else
 {
   //fmb.speed(0);
   fma.speed(wheelspeed);
   image( fma, 400, 0, 400, height );
   //if ( mImage != null ) image( mImage, 400,0, 400, height );
   count = 0;
 }

if (count>=12){
   rect (400,0, 400, height);
   //fmb.speed(1);
   //image( fmb, 0,0, 400, height );
   fma.speed(0);
 
  }
 


mcount++;


   myMouseWheel.loop();
 
   
   println (wheelspeed);
}

void movieImageAvailable ( PImage _movieImage )
{
   mImage = _movieImage;
}

ok, so to probelm is "only" the big files? mh, have you tried to split your big movie into some smaller parts and loading them separately when needed?

gruss

I think big files aren't a problem, it's rather big framesizes, but I am not sure. btw, tray going to even more ram and see what happens, especially, when do you get the error, always at the same point or, f.e., the later the more ram you add? In the latter case a memory leak is rather likely.

As for reverse/jump/speed: check out the source code and corresponding qtjava reference docs .

Hmm, I suppose in the java world these belong to the myth section, but I have had them there too, so let's clear the myth:

Memory leaks commonly happen in non-garbage collected environments (i.e. plain old c et.al.) when you allocate memory but never free it, leaving amounts of orphaned memory around, that the system can't use, because you haven't told it you don't use it anymore. These usually kreep in in some repetitive tasks and slowly "leak" the available memory to zero.

In java these are rarer, but possible, if somehow you keep referencing old objects, but never use them. It does happen in complicated code, or when using lots of libraries.

Best

Daniel

hmm, well, it could be _inside_ the faster movie class. noone said me (or extrapixel) are perfect programmers