I'm the one who posted the 'Can Jitter do this?' post from before.. Now that I've gotten into this a bit, I have some deeper memory questions and some other things.
I spent 6 hours today going through the tutorials, and Jitter is pretty powerful, wow. Well documented too. I've had some fun playing, but I still have no idea what these 'giant pulsating donut' things are that you all joke about. well, someday maybe. :>
Ok, so here is my text-drawing of how I am planning to set up my 'speed up a party in real-time' video. Mind taking a look, and giving a critique? I'd really appreciate it.
jit.qt.grab - grabs the video footage
|__jit.qt.record - records all the footage for safe keeping
jit.matrix - stores the video data as a buffer ( this will work, right?)
Then this matrix receives a bang, causing it to dump all the data down stream to..
jit.qt.record - this saves the footage to disk
jit.qt.movie - this will be set to play back the saved movie at 10X
|when the movie is done playing, some how it sends a bang to the jit.matrix above, causing it to dump all the data again.
And then I'd be done!!
Ok, so here is what is worrying me:
1. Can a matrix store video like this? The matrix seems like a memory'buffer', but I haven't gotten it to work that way, so maybe I'm misunderstanding
2. If it does store the video, however, is it storing it on RAM? Because though I have a 1GHZ 1GB RAM powerbook running 10.4.6, I think my computer will die after the footage gets long. How might I deal with this?
3. Is there a way to get the matrix to 'dump data' with a bang like I've shown? am I thinking idealistically?
Finally, does anyone know how to make a movie send a 'bang' when it is done playing? I tried to see if it does it naturally, using the 'LED' but it didn't seem to do it. This is key to the process repeating itself.