brunomathez

Even though I don't use Max on a regular basis, I thought I'd find a quick solution for that, but that didn't happen.

I'm creating an interactive installation, where the user is sending single bangs in order to trigger a series of videos.

Very simple: one bang = triggers 1 video out of 12 randomly.

The videos are 3 seconds and on a black background.

The user can send a bang any time. If he sends a bang while one video is playing, I wanted to avoid to cut straight to the new video without seeing the end of the previous one, so I've set-up a series of jit.op filters between each of the 12 videos (so they can be superimposed and have several layers seen at the same time).

The problem is that I am using the clocker to give me a time duration (300ms) for another set of very simple actions.

So sometimes I get a bang to activate the clocker (clocker 1), then with the select option I get it to send me another bang 300ms later. (select 300)

This works perfectly when I don't have the 12 videos running, but it stops working altogether when the 12 videos are running.

when the metro is activated (even if no video is playing), the counter is erratic as it seems that the CPUI is too busy to pass on every single number correctly

, so it skips 300 most of the time without sending any bang....

I understand this needs to be CPU issue and that my 12 videos should be loaded into the RAM. I tried the jit.matrix (with indexing frmaes, storing them then output matrix) but it's too convoluted to get it to play exactly what I need.

I'm sure there's a very, very simple solution to this. I'm sure that I can play 12 videos in a loadram system while having a very quick CPU...but I've been trying for the last two days and nothing has really been working so far....so if someone could send me a very simple patch, or correct my patch (attached) that would be very appreciated. I wrote down

Very simple: one bang  = triggers 1 video out of 12 randomly.
The videos are 3 seconds and on a black background.
The user can send a bang any time. If he sends a bang while one video is playing, I wanted to avoid to cut straight to the new video without seeing the end of the previous one, so I've set-up a series of jit.op filters between each of the 12 videos (so they can be superimposed and have several layers seen at the same time).

The problem is that I am using the clocker to give me a time duration (300ms) for another set of very simple actions.
So sometimes I get a bang to activate the clocker (clocker 1), then with the select option I get it to send me another bang 300ms later. (select 300)This works perfectly when I don't have the 12 videos running, but it stops working altogether when the 12 videos are running.

They all run from the same metro, and when the metro is activated (even if no video is playing), the counter is erratic as it seems that the CPUI is too busy to pass on every single number correctly, so it skips 300 most of the time without sending any bang....

how-to-smoothly-play-a-dozen-of-very-short-videos-without-compromising-the-cpu

you are doing all your rendering on the CPU. This will very easily create a huge load. Try to move things to the GPU with the jit.gl... objects.

here is a short example on how to render clips on the GPU with [jit.gl.videoplane], layer and blend them. you also might want to take a look into [jit.gl.slab] for other transitions and the HAP codec based external [jit.gl.hap] (32 bit only) from rob: 

it is by far more efficient than [jit.qt.movie]

here is a short example on how to render clips on the GPU with [jit.gl.videoplane], layer and blend them. you also might want to take a look into [jit.gl.slab] for other transitions and the HAP codec based external [jit.gl.hap] (32 bit only) from rob: https://cycling74.com/tools/jit-gl-hap/
it is by far more efficient than [jit.qt.movie]


this is the very first video patch using open gl that makes sense to me!

Each of my videos are showing 2 snowflakes (white dots on black background) and they need to be played together so I can get a few snowflakes in the same time, all at 100% opacity on a black background. That's why I used the jit.op* + (works also with the MAX blending mode).

I'll try and see how this can be done with open gl.

Also, instead of "select 300", you could use "> 300" followed by a "select 1". You would need to avoid the successive repetitions ("change" maybe? or reset the counter at the first 1 (> 300).

Difference between CPU and GPU rendering:

http://www.youtube.com/watch?v=XcolCeWIcss

Here is an example of multiplying 2 textures with [jit.gl.slab]. Again if [jit.gl.hap] works for you, you can skip the step of transforming the matrix into a texture with [jit.gl.texture]. You also might consider to change the color mode of your rendering chain from rgba to uyvy which is more effient than rgba:Ps: Inside the folder Cycling '74/jitter-shaders you find all shaders that ship with Max.

How to smoothly play a dozen of very short videos without compromising the CPU?