Comments by sblakely

@itsBREX - sorry I never saw your comment. I haven't been back here for some time and notifications were disabled.

So the use case is flexible set flow.

I have a group of tracks containing four or five control tracks.
With ClyphX, the clip name contains instructions - play this, adjust that etc.
By setting an option in ClyphX, only the unmuted track commands get actioned.

So for each Scene, I can have different outcomes based on which track is not muted - play next scene, loop this scene, jump to chorus, jump to bridge, hold on the solo until I am ready, jump to the end. Using an FCB-1010 footpedal mapped to the track mute buttons, I can rearrange the set elements as I perform.

From a programming perspective, it's a finite state machine with tracks in the exclusive group acting as the "state" variable.

I have another set of Python extensions to ClyphX that allow me to record on the fly into layered clips - like looping, but with the ability to undo and change tempo. That bit isn't working so well yet, but I'll revisit it soon.