I would like to start with a template for the Ensoniq DP4.
The fx have a max of 31 parameters, so there are 4 fx slots / instances.
I would need 1 list per FX and these would be used by any of the 4 fx slots / instances.
Any examples available or a template that does it?
Both FX have like 48 types, each of which had a set of up to 7 parameters for which the Names, the minimum value, the maximum value could be different. I solved it using sets of tables, combined with a set of fx management functions:
setFx to hide non used controls. You will notice that some name setting and all the color setting was resolved in code instead of in table, because I ran out of memory in FW2
sendFx to send out SysEx messages (Korg split its values over more than one byte)
Be aware, it’s not really list switching here, rather name, color and value boundary switching. But it might give you some inspiration.
Thanks again @NewIgnis, Ok it doesn’t mean much but I am also dutch
Yeah the memory worries me, I would need about 45 different lists for the different FX types. Ranging from 8 to 32 parameters.
I think I need to switch only one byte for selecting the right fx.
The rest is just overlay, parameter names and hiding. …
Did not even think about value bounderies…
The sysex spec looks spicey with signed and unsigned etc…
@eusti I would really like a template for the e.one for the dp4. @martin owns one too
I am just not sure if the e.one can handle that many lists and parameter combination.
Besides the list there are also many controls. .
I will anyhow start a POC and see how far i can get.
Just ordered that firmware last night myself… Had put it off for months, but now that you brought my attention back to the DP/4 I followed through… Thanks for that!
You’ve got a lot of MIDI enabled effects and synths. Hopefully you have a MIDI patchbay (or 3) that has sufficient ins and outs to have all them plugged in at the same time.
It would be interesting to hear how others have their systems patched for MIDI control.
I’m currently using two MRCCs along with some dedicated connections to multiple Electra Ones.
I have a MOTU Midi Express XT and some midi merge/thru boxes for when I need them. My midi routing setup is able to remain pretty consistent.
I currently have the dp/4 hooked up to the ipad editor, but the computer one defective records released recently is far superior. I just don’t have the dp/4 in the motu patch bay for the time being so I mostly stick to the ipad.
I use 3 Iconnectivity MIO’s. 2 XL and 1 XM. They are interconnected via ethernet as well as to the PC. So each MIO can see the MIDI traffic from the other MIO’s if desired.
The PC has a route as well where it can monitor any traffic generated on each of the thee MIO’s, which I then send to MIDI-Ox for debugging purposes.
All MIO’s have presets for routing and filtering. So I have presets I use for testing purposes, for making music which is DAW centric or for making music which is DAW less.
It all works fine, unless I need to upgrade firmware. In that case I have to make a direct connection between the synth USB and the PC. Other than that, no real complaints.
For the rest this is quite flexible: the routings are easy to read, as its routings can be made visible and maintained on the PC.
For emergency purpose there is a manual MIDI patchbay (ESI M4U Ex) but I haven’t had to use it anymore since those 3 MIO’s are in service, which indicates they work well.
Side note: My PC has a direct USB connection to my Zoom Livetrak Audio Interface. All other USB connections that are hooked to the PC use a powered hub for Elektron (Overhub), because it is one of the few MTT hubs that aligns on the highest USB protocol, and not on the lowest (as most USB hub do), which might be relevant to keep good clock timing.
Most synths however have their USB connected to a MIO, as it offers most flexibility (for those time I do not want to fire up my PC).