Optimizing midi chop channel cooking

Beginners
1

i have select chops patched to a midi in chop, splitting relevant CC channels and note channels into separate networks.

i’m noticing that when i adjust any midi parameter on my controller the all of the networks cook. i assumed the select chops would prevent this from happening. am i missing something?

thanks!

2

Hi @shellfritsch,

we currently do not have per channel cooking in a CHOP. You could use the Null CHOP’s “Cook Type” parameter and set it to Selective which with the default setting of “Check Values” would stop the cooking except for when the value actually changes.

Otherwise making use of the Midi In DAT and it’s callbacks can give you more control in this regard.

cheers
Markus

3

thank you for your reply @snaut

perhaps you can help me with a bit more info about best practices for performant midi control?

i am using sceneChanger with 12 different scenes.

on project level i’ve built a “controllers” base, which contains my midi in chop, feeding to a select chop to identifiy specific midi cc messages and rename them to generic names. after that is a math chop to scale values 0 to 1. finally i have a filter chop to provide some smoothing.

within the scenes i am using select chops to bring in specific controls, which are often the scaled to useful values using another math chop.

some questions:

is the midi mapper more cpu efficient?

rather than bring select chops into the scenes, should i instead be adding useful parameters to the parent container and then assigning my controller to those parameters?

if you have any other tips i welcome them.

thank you!