Those devices would have worked as a very basic first approach to the problem. But, in general, they only automate one or two parameters. What I have in mind involves 16 tracks (at present) with co-ordination between them that would be very hard to organise using multiple copies of the devices.

Given that it seems to make more sense to create the device I want, assuming it’s not too hard.

A umenu, using checkitem, does look like it would work for toggling of enabled/disabled per track, thanks for the suggestion.

But what about if I wanted to be more ambitious with routings affecting multiple tracks. Then I guess I’d be looking at something like a matrixctl but dynamically generated and labelled.

I’ll start with something basic but I’m interested in what others have done in this area.

Thanks again.

Matt