Julien Bayle

finishing my system for my live performance (named ALPHA), I'm looking for to optimize things a bit.

If I can disable/enable jitter OB3D instances, I'd like to know more about jit.catch~ and other objects like that.

Of course, I already optimized things by doing this:

- disable for instance the jit.gl.graph fed by the jit.catch~

Check on the patch picture. I'm doing that in one check with the toggle (actually, this is a program change controlling a [preset] that does it automatically)

But would it be a better way to do that ?

In my patch, I have a big routing system able to route this audio channel to that visual module for that song, etc for each song. In my creation process, I need to be able to remove and add new module and my current system fits well my process. I'd just need to be careful to switch off unused (but consuming) modules when I don't need them at a particular moment..

Hi there,
finishing my system for my live performance (named ALPHA), I'm looking for to optimize things a bit.

Of course, I already optimized things by doing this:
- cut the flow of bang to jit.catch~
- cut the signal incoming to jit.catch~
- disable for instance the jit.gl.graph fed by the jit.catch~
Check on the patch picture. I'm doing that in one check with the toggle (actually, this is a program change controlling a [preset] that does it automatically)

optimizations-and-cpu-consumption-with-jitter-objects

From your description I would remove the jit.catch~ instances from within your modules and simply have a single instance at a high level of your patch. You can then distribute the resulting jit.matrix to whichever module is active at the desired time.

From your description I would remove the jit.catch~ instances from within your modules and simply have a single instance at a high level of your patch.  You can then distribute the resulting jit.matrix to whichever module is active at the desired time.


Optimizations and CPU consumption with jitter objects