Aaron Poor

I discovered jitter not too long ago and am loving it. I want to eventually do live visuals for shows and dj sets with it but I have a few questions about the setup for a patch to do this. 

Is it all about abstracts and bpatchers and then you just have one patch open and que bpatchers to switch between visuals sources/effects? 

For a full set you would have to have a lot of different subpatches to switch to. Does this not overload the computing power having all jitter objects running in the background while you switch between them? Or do you pop a new bpatcher into the chain every time you want to switch up the visuals displayed? Or am I even on the right path with this bpatcher logic? 

I discovered jitter not too long ago and am loving it. I want to eventually do live visuals for shows and dj sets with it but I have a few questions about the setup for a patch to do this.  


Is it all about abstracts and bpatchers and then you just have one patch open and que bpatchers to switch between visuals sources/effects? 
 For a full set you would have to have a lot of different subpatches to switch to. Does this not overload the computing power having all jitter objects running in the background while you switch between them? Or do you pop a new bpatcher into the chain every time you want to switch up the visuals displayed? Or am I even on the right path with this bpatcher logic? 


Any tips would be much appreciated.
 Thanks!

Hello all!  

I discovered jitter not too long ago and am loving it. I want to eventually do live visuals for shows and dj sets with it but 

performing-visuals-basic-setup

you are probably wrong if you think that every little change needs another patcher.

for example if you plan to play 100 video files,

you use 1 player and tell it which video file to play

you are probably wrong if you think that every little change needs another patcher.
for example if you plan to play 100 video files,
you use 1 player and tell it which video file to play
you don't use 100 players


sure you can organise your code in bpatcher or sub patchers. 

The main thing to keep in mind is that you want to disable portions of patch which are not currently used. 

To do that you simply want to avoid matrices from receiving bangs and you want to disable jit.gl. objects with the @enable attribute. 

That's all it takes, then your patch can even be 10 square meters big.

Hey Aaron, 

sure you can organise your code in bpatcher or sub patchers. 
The main thing to keep in mind is that you want to disable portions of patch which are not currently used. 
To do that you simply want to avoid matrices from receiving bangs and you want to disable jit.gl. objects with the @enable attribute. 

That's all it takes, then your patch can even be 10 square meters big.  

or have the video effects all open in parallel and then use [gate] to decide which path the video signal should go.

Performing visuals basic setup