Imagine that you have a pedalboard with the following pedals:
Octaver
Distorsion
Fuzz
Amplifier + Cabinet Simulator
Chorus
Delay
Reverb
You decide that you will use it in mainly four scenarios, that can be interchangeable at in any moment of your musics:
Clean: Just Amplifier + Cabinet Simulator on
Modulation: Amplifier + Cabinet Simulator, Chorus, Delay, Reverb on
Distortion: Distorsion, Amplifier + Cabinet Simulator on
Solo: Octaver, Fuzz, Amplifier + Cabinet Simulator, Delay, Reverb on
A way for you do it is creating four snapshots. But it could be an inconvenient if you want to change the values of pedals after create them.
An alternative is using tetr4 switch pedal. You can imagine it as a less powerful alternative to snapshots, that avoid this previous situation .
With it, you have four CVs that you can assign with any of pedal parameters. So the idea is that you assign CVs with the pedalboards bypasses. For instance, I decided to assign as the following way:
CV 1: Distortion bypass
CV 2: Octaver, Fuzz bypasses
CV 3: Chorus bypass
CV 4: Delay, Reverb bypasses
I rename it to make more clear with each one means:
Tetr4 Switch has four presets. At each preset you have four toggles/switches. If I want to make a clean sound when Preset 1 enable, they I will make all switches as off. If I want to make Preset 2 just a distortion, then I will make only the CV that is assigned to Distortion on.
Yes, CV restricts the management of the octaver plugin by Web UI. Is it the problem that you thought?
I’m sorry, but it’s possible to assign notes generated by a plugin to another plugin parameter? I didn’t know that it is possible.
Anyway, I think that isn’t possible to assign more than one parameter for the same MIDI command, I remember that I tried last week, I think. So the assignment for multiple footswitches for the same tetr4 switch parameter probably requires a more complex strategy that send more than one midi message for each for four tetr4 switch possible parameters.
My current update, maybe the last one. I think that I finished the physical part, but I have not tested. I’m having troubles for connecting my device with a computer, apparently the dwarf USB B doesn’t work anymore.
The source code is on my Github if someone would to explore it.
Yep, since you program the 1st switch with Fuzz+Oct you can’t have the Octaver only. Another solution would have to “sacrifice” another switch from your plugin to make it engage the Octaver only… so having 4 switches would become rapidly not enough and it would make sense to have a switch for each plugin + the actual 4 switches for combinaisons.
Yep, you can send the midi to the “virtual loopback” so the ModDevice is listening to the message you generate inside the ModDevice !
I use this a lot so I can engage plugins with my midi controller, or with the dwarf (when I don’t need the MC8 midi-controller), or with the computer of a friend (with midi-bluetouth)
Nope, but you can send multiple midi message with one single footswitch !
And it could be really nice to set some parameters precisely :
switch 1 : delay ON + delay feedback 58 + octaver ON + octaver wet 127
switch 2 : crunch ON + Gain 102 + delay OFF + reverb wet 50
Ok, I think that I understood the problem. For switches per preset just allows fine control of four plugins without aggregate them in a unique switch.
At a similar way, maybe the number of presets could not be sufficient for some musicians.
–
I think that a version that can assign any plugin individually with midi messages is a good idea, but at the moment MIDI is something that I don’t have programming skills. I could offer a extended version of tetra switch with more switches (8 switch with 8 presets?), but my Dwarf pre diagnosis is not good.
I added a select list parameter for this plugin. It is useful if you want assign a device footswitch (B, C or B+C).
You can also use the four paratemeters `Preset [1…4] if you want to assign a specific preset for a footswitch. Actually, you couldn’t yet… the device leds values aren’t showing the current state I’m trying to fix a wrong behavior.
But you can use they as well for assign an external device, like M-VAVE Chocolate. Talking about this controller, as it doesn’t shows any information because it doesn’t has leds related for each parameter, I added a “dummie parameter” just for enable showing notification on device
You can see an example here:
Note: Maybe you have seen this following parameters. Actually they didn’t work. I’m trying to understand how can I use it for customize the message showed on notification.
Now it works. So, if you assign the Preset 1-4 parameters for some of the device footswitches, the led is turned on if the respective patch is in use. The led colour is based on the preset number.
Maybe you prefer to assign the “current preset” parameter. I tried to change the led colour based on the preset, but I noticed that it doesn’t work appropriately when a parameter is a list like that. I opened a issue for mod team (Lv2-hmi.h issues on lv2:portProperty lv2:integer, lv2:enumeration).
I noticed something that makes me sad. Unfortunately the notifications will only appears If the assigned parameter is showing on device led. It is something that I wasn’t expecting.
I also refactored the source code to be easier to make the Hep7a Switch. And yes, the extended version will to be 7 instead of 8 because of the number of colours assignable for the Dwarf LEDs.
it does, we should get back to more developments very soon.
but going forward we only want to have stuff in beta that is 100% confirmed to be pushed into stable eventually, for the final stages of testing.
while a plugin is in development we should find some other way. I have some ideas on how to do it, should happen later in the month.
Having just tried it out, I think this is a wonderful piece of work - particularly the way you get the UI to represent the exclusivity of the presets and to show the 10/0 states of the 4 toggles.
Am wondering though, would it be possible to add a single midi output port - which could (at the simplest level) just also send out 4 midi cc messages, whenever a preset is triggered? e.g for 10v,0v,10v,10v
CC1 127
CC2 0
CC3 127
CC4 127
This way they could be routed through the MIDI-loopback port and control the states various other plugins on the pedal board
My own particular use case is using the alo-looper where I will sometimes have 4 loops playing at particular times. For purposes of song dynamics I’d love to be able to just be able to turn off everything , then bring back percussion, then bass, then pads etc. (a version of The Human League’s “Love Action” is particularly the song I want to try this with)
Unfortunately, due time and knowledge, the MIDI integration with my plugin isn’t in my plans. But if there is someone who would like to push a pull request, I’ll appreciate.
By the way, I am quite sure that it is possible integrate Tetr4 switch with other plugins to do what you want. Maybe using MIDI Note Toggle - MOD Audio or maybe MIDI File - MOD Audio you can use the CV from Tetr4 switch for on some of these plugins and they send your required message…
Pretty incredible you have merged these two UIs into such a useful plugin.
Anyway, sometime, maybe next week, I will see if I can add the extra midi functionality. I know how to generate midi events in c/lv2, but one thing I have never got my head round is makefiles and build scripts. Anyway, I will give it a go.
In the image attached - Tetr4 switch now has a midi output port - that is being fed to the midi loopback - and the ALO looper, previously configured using midi channel 10 (or 9 if zero indexed) with CC 50/51/52/53 - follows the state of the preset.
For this to work I had to add the extra params CC1, CC2, CC3, CC4, Channel, and ChangesOnly (to choose whether you want all 4 midi cc commands to be sent, or just the ones which have changed)
Unfortunately, I have not yet progressed to the ModUI aspect, so those things have to be set via the default UI.
The midi display tool can only display the last cc command in the sequence - so in each preset, it is showing the toggle value of the 4th config button
.
.
