Just a quick sum up here and also some expositions on our future features and possible developments:
This topic of changing scenes needs some clarification prior to any discussion. Normally when we refer to MIDI or even existing multi-effects it has a small difference in the meaning.
In the MOD we have two important words: Pedalboards and Presets.
Pedalboard is probably what most people understand as a scene or patch. We consider it to be the selection and arrangement of the plugins + the connections between them + the addressings to the hardware. Note that addressing, in this context, refers only to plugins parameters. Pedalboard change is out of the internal pedalboard scope and needs to be viewed from a different angle.
Preset is a saved combination of plugins parameters values. We can refer to presets both for plugins as for entire pedalboards. The preset can also be referred as a state.
Then we have the necessities of the musicians. The bottom line is “changing the sound with a click” and we provide different ways of doing that. Each of them has advantages/disadvantages. Some change the states of a pedalboard and others change the pedalboard itself.
Things that are implemented and working:
1 - Utility plugins for routing
We have the A/B Switch box, the 4 channel Trigger Switch and the 4 channel Toggle Switch. These are plugins that split the signal in multiple paths that can be selected by a single click. Depending on where you position them you can literally change the entire effect chain when clicking
These are all “intra pedalboard” controls, meaning the same pedalboard is loaded all the time. In this case there is no lag between sound changes. Ideally, only the path where the audio flows should consume CPU but that is not the current case. This can generate some CPU overloading and there are optimizations in the software development roadmap.
2 - Bank system and MOD Duo Controller
Banks are simple Pedalboard containers. You can access and navigate the bank list and select a pedalboard using the right-side knob.
Each bank has an internal property of using the two footswitches for navigation. When this is enabled, both footswitches are “stolen” from the plugins and used for previous/next navigation
Different than the tool plugins, this option requires the loading of a new set of plugins and this generates the audio lag - I’d say about 0,25 seconds - and that will be optimzed soon by plugin pre-loading.
Things to be developed:
Preset Widget - both for plugins as for pedalboards
The widget will enable the creation of presets for plugins or even entire pedalboards.
the presets will be addressed in two different ways:
a - as a enumeration list to a knob. In this case you address the entire list and using the knob you can navigate the list to select one particular preset (similar to the navigation that we have with the Cabinets and other lists)
Although possible, this solution is not very friendly with MIDI due too the lack of monitoring.
b - as a pre-defined state to a footswitch. In this case you load the preset by pressing the switch. Simple and effective. I believe that this would sort out a great amount of requirements from musicians in general.
By reading this tread it gets quite clear that more MIDI integration would be highly valuable. Two ideas that pop-up right away are:
1 - navigate a bank in the same way as we do with the foot-switches. This could even be hardcoded to some pre-defined MIDI message so that it would not be dependable on the configuration of the Bank itself, enabling the bank navigation whilst still foreign the footswitches to the plugins.
2 - bind a pedalboard to a particular switch, similar to what we want to do with the preset states. This could totally bypass the Bank system and maybe could even be a pedalboard property.
@falkTX could help us on the feasibility of that