Jutla

Does Anyone Know How To Split Screen A Jitter Window?

It Would Be Really Nice If You Can Suggest Some Objects To Check Out That Allow Me Achieve This.

split-screen-in-jit

depending on what you actually mean, I would suggest you to look at jit.glue and jit.scissors.

I'm trying to split a screen into three segments to display three different images/videos, which will be triggered by MIDI messages from an music instrumentalist.

So, on the same window/screen, potion one will remain blank until my drummer hits the kick drum. Portion two will remain blank until he hits the snare, and so on. Using triggers on the drums I will send MIDI data into jitter which will trigger pre-loaded images for each potion/split.

I'm trying to split a screen into three segments to display three different images/videos, which will be triggered by MIDI messages from an music instrumentalist.  

So, on the same window/screen, potion one will remain blank until my drummer hits the kick drum. Portion two will remain blank until he hits the snare, and so on.  Using triggers on the drums I will send MIDI data into jitter which will trigger pre-loaded images for each potion/split.

I'm not used to jitter and I'd like to be able to split the screen in up to 4 parts, and recall different cue points in the 4 split screens from the same movie. 

Here's my first rough test, and I notice it's quite sluggy (is this a word?), and has some latency when calling back cues. The final patch would have different cues for each part of the screen.

Hi there, 
I'm not used to jitter and I'd like to be able to split the screen in up to 4 parts, and recall different cue points in the 4 split screens from the same movie. 
Here's my first rough test, and I notice it's quite sluggy (is this a word?), and has some latency when calling back cues. The final patch would have different cues for each part of the screen.

Here's an approach which should give you optimal performance. Just copy the jit.movie and jit.gl.cornerpin that you want and position them on the screen.

Are the jit.gl objects supposed to be faster to respond, in general ?

Thanks a lot. 
Are the jit.gl objects  supposed to be faster to respond, in general ? 

Yes, jit.gl.* objects use mostly GPU for processing data.

"Regular" jit.* objects use mostly the CPU, which should be much slower. Additionaly, if you use the GPU for image/video tasks, you free the CPU for audio and other tasks.

Yes, jit.gl.* objects use mostly GPU for processing data.
"Regular" jit.* objects use mostly the CPU, which should be much slower. Additionaly, if you use the GPU for image/video tasks, you free the CPU for audio and other tasks.

So, what's the basic jit.gl replacement for jit.window ?

jit.window shows content both for matrices (CPU) and textures (GPU).

jit.world and jit.pworld include internally a jit.window/jit.pwindow

jit.window shows content both for matrices (CPU) and textures (GPU).
jit.world and jit.pworld include internally a jit.window/jit.pwindow


sorry for asking trivial questions, but what would then be the jit.gl replacement for this stripped-down patch ? 

I tried jit.videoplane, but had trouble getting the output size right. 

My goal is just to have a basic movie player, with access to a list of cues, looppoints and rates, with the smallest latency, as cues etc. will be triggered in live. 

Thanks, 
sorry for asking trivial questions, but what would then be the jit.gl replacement for this stripped-down patch ? 
I tried jit.videoplane, but had trouble getting the output size right. 
My goal is just to have a basic movie player, with access to a list of cues, looppoints and rates, with the smallest latency, as cues etc. will be triggered in live. 


Wow, ok. That simple. I guess I miss some elementary knowledge about video to properly understand what's behind jit.world. 

Meanwhile, I just discovered the "viddll" engine. Again, I don't really understand a thing but it seems to but a lot faster.

Wow, ok. That simple. I guess I miss some elementary knowledge about video to properly understand what's behind jit.world. 
I'll do some reading. 
Meanwhile, I just discovered the "viddll" engine. Again, I don't really understand a thing but it seems to but a lot faster.

Split Screen In Jit.