Ways to control the Duo on stage

#25

Hi, my live use case has been pretty basic up until now.
A few different sounds all on a single board for each gig (I play bass).
I’ve taken to using an audio to midi converter and feeding the sounds into the mod. I can toggle the sounds I need on a per board basis ok, a mix of pre-sets and using the actuators directly.

What I’ve not been able to do is figure out an easy/quick way to switch between boards in a bank. I saw the navigate via footswitches option but can’t work out how to get in or out of that mode. Nothing I could find in the user guide, manual or wiki.

What am I missing?

#26

The navigate by footswitches option only works when the web interface is not connected. To activate it, load a pedalboard from within the bank from directly on your Duo. Then you should be able to navigate boards within that bank via footswitches. Oh, and IIRC you can’t have anything mapped to the footswitches because that would override the navigation.

Also - any my memory is hazy here - I think you can change pedalboards via Program Change messages, so PC 0 would select the first board, PC 1 the second, etc.

#27

Hi ssj71, I haven’t find out the solution for using OSC2MIDI on the duo: when I try to open in the Duo the binary I compiled in Doccker’s Mod Plugin Builder environment it gives me an error. Could you maybe help me to compile it in the proper way?

#28

I will be happy to, but it will take me a little while. I haven’t had as much time for development and I installed a new version of linux last year and so I need to set up the MOD development environment again. Once I have that I think I could get a binary to you. Sorry it will probably be a few weeks at least.

#29

I’ll really appreciate it, thank you!

#30

https://drive.google.com/file/d/15ZIE7yWGZbD2vfhCWq9XcB3b4EtzGPeI/view?usp=sharing

give that a whirl and let me know how it goes. :slight_smile:
Thanks for the patience.

#31

Thanks lots for your job sjj71, I really appreciate :grinning::grinning:.
Unfortunately trying opening your file on the duo gives me this error:

Error opening map file! /usr/local/share/osc2midi/default.omm

I didn’t find what this means, any tip to help me?

#32

For lists (either plugin parameter list, plugin presets or the new pedalboard presets in v1.3) you can map them to the Duo foot and knobs too.
Not possible to assign them to MIDI CC yet.

Has been anything done in this regard? Is now possible to assign a pedalboard preset list to MIDI CC or PC?

That would be of great interest for me.

#33

@Tarrasque73 and community,

if you follow the instructions in the MOD_Web_GUI_User_Guide#Organizing_Banks part of the wiki, you can choose to use PC messages in a Bank list instead of using the two switches on the Mod Duo…
So you can directly change your pedalboards via Program Change message.

Greetings and God bless, Marius

#34

I know that, but it’s still some sort of workaround in my opinion.

From what I remember, changing a pedalboard will cause a short muting of the output (inevitable, I know).

This is the way I always worked with rackmount multieffect processors. One sound, one patch, and try to switch while you aren’t playing.

I was hoping the Duo could offer something more sophisticated. If it allowed to assign a pedalboard preset to a footswitch (or, better, a CC message) I could move to a “one song, one pedalboard” approach and switch to all the different clean, distorted, solo, whatever sounds I need with no interruption.

And as an added bonus, it would help drastically reduce the number of pedalboards in my Duo. :wink:

#35

Hello @Tarrasque73,

I would suggest you to make a pedalboard with all used plugins and use pedalboard presets according to the wiki here
In the section about saving and loading pedalboard presets
you can assign such presets to a switch on the Mod Duo.
I am changing reverb presets and wah on/off state at once within one pedalboard using different presets.
With this I mean the presets button in the GUI that I assign to a switch or the knob.

I know, this costs time upfront to prepare for a number of songs looking for the right plugin presets to be chosen for a particular song, but it should be no problem improving it.

Maybe you can simplify your pedalboards first, meaning following:

  1. Giving abbreviated names for song presets like
    SongA_Intro, SongA_V1, SongA_Ch1, SongA_Solo…
    for Intro, Verse, Chorus, Solo
    2.Reducing your plugins of the same type ( gates, distortions, compressors, amps, time based effects and reverbs) to a list of preferred plugins and presets.
  2. Creating pedalboards for one or more songs and creating pedalboard presets like under 1 where you decide which plugin ( and plugin preset) is turned on.
  3. Choosing a knob or switch on your Mod Duo for your pedalboard presets to choose from.

Hint: If I just switch between verse and chorus I I like to name both presets as follows:
SongA->Chorus (for the verse)
SongA->Verse (for the chorus)
to show what’s next.

Greetings and God bless, Marius

#36

The real problem is that a list assigned to a footswich will, if I am not mistaken, cycle with each click, while I need “random” access.

I often have 3 or more sounds per song, and they are not used in sequence.I have to be able to jump back and forth to one sound to the other.

#37

Hi @Tarrasque73,

I know your concern, and if the overall form of the song will be the same like
Intro, V1, C1;Interlude,V2, C2, Solo, Pre-Chorus, V3, V1,
there is only the next pedalboard preset available and unfortunately you have to make an entry in the list for each part…

How can we fix this is the question because sometimes this exact order may be too unflexible.
You want to make music, not fiddling with presets if it’s just one song or a numberof songs with one pedalboard.

I hope someone will chime in here with a proposal for better management…

Greetings and God bless, Marius

#38

I think the only viable solution to be able to select entries from a list by using PC or CC messages as “item index” exactly as is now possible for pedalboards in a bank.

This way you could use any of the available commercial MIDI pedalboards to either switch pedalboards in a bank or presets in a pedalboards, to fit your liking.

If you could also choose the MIDI channel for each of these control methods you could even use both at the same time!

But maybe this would be a little overkill. I figure that if someone used my approach to use one pedalboard per song, then he could be content with changing pedalboard with the MOD buttons.

#39

Ah sorry I should have forseen that. You need some mapping files for osc2midi to run, you can create your own and pass it in as a parameter with the -m flag. If one is not specified it looks for it in the path reported in the error. You can copy this folder https://github.com/ssj71/OSC2MIDI/tree/master/maps to that directory and it should start with the default map.

#40

Ok, sorry, now my problem is that i can’t create the folder /usr/local/share/osc2midi/ because I don’t have permissions (filesystem is read-only and i can’t change permissions with chmod). Is there a solution you can suggest?

#41

~/.config/osc2midi/
Will also work. Copy them there.

#42

Thank you for patience. Now it seems to works, I mean, it says:

starting osc server on port 57120
sending osc messages to address osc.udp://localhost:8000

Fantastic. But now… how can I communicate with?
My phone is connected to the Duo through bluethoot. Wich is the host adress to set in my OSC app?
And through wich virtual midi port can I communicate with plugins?
:thinking:

#43

now we get to the fun part. :grimacing: I haven’t done this myself.
You should see a new midi port appear in the pedalboard builder. Does that show up?

The next step would be to use an app like control osc+midi to send some osc messages to 192.168.51.1:57120

if you run osc2midi with the -v flag it will print a message when it receives an OSC message.

Lets try to get to that point, then we’ll figure out midi learn etc. If I have some time tonight/soon I’ll see if I can do this at home, then I can make a better tutorial.

#44

Unfortunatly it doesn’t seems to work.

  • Scanning for midi ports in MOD Web GUI doesn’t find any new port.
  • osc2midi (-v) doesn’t receive any message while my OSC app is connected to 192.168.51.1:57120 (or even 192.168.50.1:57120)
    Let me know if you find a solution.