(02-04-2020, 07:36 PM)XORadmin Wrote: I assume you didn’t see the Midi CC function in the input settings yet. They are there for exactly that purpose. It is not implemented yet as i got to release from time to time and this was not ready and completely thought of yet.
So when request features you can help me really out by thinking of how these could be integrated best and practically while keeping the workflow.
The CC one is not too easy because they are not enough CC numbers in Midi per channel to fit for all functions of all tracks. Of course Midi CC in general are easy.
So a fixed cc mapping got to be smart. And i want to have it directly all and not just one value. And it got to be future proof. So all stuff which kept me for now to implement it. It’ll be there for sure!
Btw i will start with the easy way through the automators.
I might have came across it but never knew it was for this purpouse. Good to know! The way I envisioned it is something like this: cc10 maps to patch column, cc11 to table, cc12 to trigger, cc13 to mod value, cc20 to fx1 type, cc21 to fx1 value, cc22 to fx2 type, cc23 to fx2 value etc.
You could use the step input midi channel which would input these values in the active pattern at the cursor