Filling this list is straightforward, but how should updating or deleting presets be handled? What if I select an inexistent preset? What if I want to rearrange the array/list because there are too few or much entries? Shall we consider n amount of empty preset spaces between song indexes m beforehand? What if a preset n is used by song m1,m3,m15,m17?
I guess the mechanism would be analogous to the list of the pedalboards in a bank.
I haven’t actually tried it yet, but I guess the “bank” is actually an one dimensional array of pedalboards, so if you send PC 1 you get the first and so on.
So if you rearrange the pedalboards in the bank you also must change the configuration of your MIDI controller to match.
It’s not something guitarists are not used to, any way. With old school rack effects unit, it was part of the daily workflow.
You may use some or all MIDI channels for sending preset changes, but I think it’s hard to implement.
Even if you use a dedicated MIDI controller like the Korg nanokontrol switching dedicated plugin presets with the 3 (Solo,Mute,Record) buttons (for previous plugin preset, next plugin preset and engage plugin) and the slider for changing a dedicated parameter.
I’m afraid I’m still not getting the point straight. In the kind of user experience I’m trying to explain, there’s no place for parameter editing or plugin presets.
What matters is ONLY whole “patch” changes. You have the clean chorus sound for the verse and you go to the distorted delayed sound for the solo. And back.And you need to do it with a single pedal press, possibly with as little interruption of signal as possible (that’s why pedalboard changes with the duo are not ideal).
Since you want to use just the two Mod Duo switches and MIDI messages,our programmers have to implement a good way showing banks and presets and switching within them or handling MIDI messages in an easier, faster way.
To be honest, the 2 switches on the duo are nearly useless in my scenario. Once you can pilot the Duo fully with a MIDI pedalboard, there isn’t a good reason to use them.
Well now that I think, if I had fully random access to presets in a pedalboard with a MIDI footswitch, I could revert to switching pedalboards in a bank with the Duo switches, since in this scenario pedalboard switching should be limited to the time between songs, and pedalboard number would be reduced by much, but this is a secondary consideration that just came to me.
A better way of showing bank and pedalboard info on the Duo display is another matter entirely, but now that you mention it, is another thing that bothers me and, frankly, another evidence that use of the Duo outside a studio has been severely overlooked.
Unless I’m mistaken, there’s no place you can see the current pedalboard name (let alone bank and pedalboard preset) anywhere on the display if you have plugin parameters mapped to the Duo footswitches.
You can ONLY see them in the web pedalboard builder.
This is complete nonsense!!! I won’t have a laptop connected to the Duo onstage!!!
I can happily live without bank info, but I really think that pedalboard name and pedalboard preset should be always visible on the displays