Multiple jit.window objects /// multiple video instances
I am working on a project that entails having multiple video files playing at once. I had the project set up very simply with multiple jit.window objects but, alas, twas too good to be true. It seems that I can only have 2 instances of jit.window open and running before all the others close their feed.
I have been looking around and maybe the solution I am seeking can be found in open GL or using a matrix? I am a novice with max, I don't use the software often.
The ultimate goal is simple- to have control over multiple video playbacks in a single instance, which all originate from different files.
Any and all help appreciated- thanks a bunch!
use multiple jit.gl.videoplanes and render them into the same context?
Thanks for the response Fedde. The patch you provided does not accomplish what I am looking to do, although- very cool and glad that I know how to do that now! Thanks!
I am trying to figure out how I can playback multiple video files at the same time, each one in its own window that can me moved /// controlled independently.
Using jit.window and I was only able to do this with two separate files.
Well then a logical question would be: why do you need multiple jit.windows?
Using more than 1 jit.window will use far more resources than needed.
As Fedde said its not clear what your trying to achieve.
Why use multiple jit.windows ?
Do's it need to go to two or three beamers/Monitors ?
If so then you need one big render context (1 jit.window) and something like the matrox triplehead to split it into two or three outputs.
As an example.
If i need to use 3 beamers and I have 3 video files that are 1024 X 768 then I create one jit.window which has a resolution of
3072 x 768
I send each separate film to a jit.gl.videoplane.
Those 3 videoplanes are positioned with the position attribute so they're in one long row next to each other.
You then pull the jit.window over to your "2nd screen" and activate fullscreen mode.
I then set the matrox unit to 3 monitors output 1024 x 768 per monitor.
The hardware then splits this signal into 3 outputs.
This is by far the most efficient way to have separate render contexts.
Oh wow- my illiteracy within this software led to confusion in comprehending the patch you provided Fedde! I gave up too easily before. This helps so much!
Andro- thank you for further explaining, I looked back on what I was doing and it makes much more sense now, in the context of the patch Fedde provided.
Huge help, many thanks to the both of you!