Patches

[dionnaki]

Any chance of having the patch function for the expanders bumped up the priority list please?

[XORadmin]

It's up on the list but not on top.
Why is it not in there yet? Because the patch screen itself need to be redesigned in order to allow 4 digit editing and a better graphical representation of the functions/values. Same for the Tables.
Why do you want it especially?

[dionnaki]

Fair does. All in good time. The reason for urgency is that I use the patches for sound design. Instead of using  info on the main edit window. I will just feed it from a patch. This way I just  use a patch block instead of lots of different info n ain window. So patch 01 is kick sound, patch 02 is a snare etc. the CVS that make the sound usually span over a few channels. I then use FX column for automation within the track. Basically, patches are what I use most and are most valuable function for me. Can do more with one page this way and is easier to read. But whenever you plan to is fine. Sound like more work than I expected.

Thanks

[dionnaki]

Hope you don't mind me asking. Are we eventually going to be able to access the cv16 outputs from the patches in the trigger 16 window?

[XORadmin]

That will most probably be not possible. There is not enough information per patch field to make that possible. You would need the additional NSA-Number, the function code, eg if it is a note or a pitch value etc. and then the value itself. That is too much information for the patches.