The plugin contain four states. You can select choose between each effects pressing the footswitches. Note that only one is currently active.
For each state you can toggle on or off the config sliders. Each one represents an CV output. The idea here is that when the an footswitch is activated, the four CV states will be change their value based on Config related.
For example, in the following gif example, we will have this states
Footswitch 1 - Config 1:
10v: 1, 3, 4
Footswitch 2 - Config 2:
10v: 3, 4
0v: 1, 2
Footswitch 1 - Config 1:
10v: 2, 4
0v: 1, 3
Footswitch 1 - Config 1:
10v: 1, 2, 3
If you need that the active means 0v instead of 10v, you can change the upper sliders
And finally, you can assign a better label to explain what the state means for you
you are the best @SrMouraSilva. This is the thing I tried to build so many times with onboard plugins but couldn’t get to work. Please consider to add four more switches - or have another version with 8 config sliders each.
If you’d like I could help out with the mod-ui part.
I’m having difficulties for connecting the pedal state with the ui state. I would like to emit an event for the plugin when I press on a knob or a switch (and also, vice-versa). Do you know any source code of a plugin that I can check it use as an example?
If you have some curiosity, there is the current state
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.
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.