I am wondering. What is actually happening inside the jit.qt.movie object when sending him a 'start'-message. To me the performance seems to increase when sending 'time $1' messages instead.
If I use the standart way in my patch (by using the a 'start' message) 30-50% of my CPU is taken already, without even sending any bangs to the jit.qt.movie object for output (I am working with two 1024 x 768 foto-jpeg footages).
But if I use a metro and 'time' values that I send to the movie object, I have almost all the CPU-power left. To me it looks as if there is no decompression done just by sending 'time' messages.
Is that correct?
When banging the jit.qt.movie object, the difference in performance speed is not that huge anymore but an advantage of a few fps remains.
I'd really like to know a bit more about what's actually going on in there, because it seems to be an important point if you want to do some tuning while working on the edge of your CPU-Power.
Does it make any sense to work around the usual way of playing a footage by 'starting' the movie object or do some problems occur that I haven't noticed yet?
thanks a lot