My first though after overviewing the midi implementation chart is that the E1 preset would need to dynamically update names and ranges of the parameters depending on which Lexicon 300 preset is loaded.
I am very new to the E1, my programming skills are essentially limited to Max/MSP, still I am willing to learn, but before digging further I wondered if that particular behaviour is even achievable/recommended.
It can be done. I was a little sad to see that they didn’t implement it in the 480L.
You might be able to do it using the new graphical UI that Martin has been crafting, but to handle all the params for all the different algorithms, you probably either want to use a separate control for every possible param (using the JSON/GUI approach) or keep a main set of controls on one screen and use a lot of LUA to dynamically reassign names/lists/ranges to the visible controls.
The benefit is that as a user you don’t have to keep switching pages. The downside is way more of a headache for the developer.
In general, Lexicon sysex has made my head hurt in the past, although this looks a little cleaner than their extreme bit packing/bit shifting sysex from older units.
So 2 ways yes, the LUA approach seems to be a huge plus from the user perspective.
I just read the post where @NewIgnis (thank you) pointed a E1 preset that seems to do exactly this, switching parameters depending on the selected effects. I’m going to start testing using it as a start point.
