I’m not sure if I’m the only one, but when working in the MOD environment, I’m often using CV modules to work around a missing feature that I feel should be a simple plug-in. I’m excited about new delays and other functional plug-ins, but I feel like the basic “ease of use” side is being ignored somewhat - probably because it’s less exciting.
For example, the various switchbox plug-ins - if I’m switching between an A/B signal path, I should be able to assign this to a single knob, but you can’t, and also, you can’t use CV with those. So I end up using other work arounds.
I would love a panner that syncs to BPM. In fact a basic LFO that syncs to BPM (with a start/stop trigger) and can be assigned anywhere would be a great help.
Anyway, I love my Mod Duo X, and just wanted to give my 2 cents about wanting more plug-ins for channel switching, and signal routing, and other less exciting stuff.
It’s pretty unfortunate that the switchbox plugins can’t be controlled with CV. I noticed something similar recently. Lists with more than 2 items can’t be controlled with MIDI. It would be nice if these assignments could become possible on the MOD image. If the switchbox had a toggle control instead of an enumerated list for the channel switching it would be CV controllable by the way. In my opinion both should be CV controllable though.
AMS LFO2 and dm-LFO and possibly others can be synced to BPM with the “Translate value to musical tempo” toggle. Maybe that helps?
I have been learning how to make lv2 plugins for a while now, and hopefully over the xmas break I will have enough time to release them.
However, in advance of that, I attach here code for two plugins I am working on. AudioRouter and MidiRouter. Each of them allow the signals (audio or midi respectively) to be sent to 7 possible outputs (Out1,Out2,Out4,Out8,Out16,Out32,Out64). Which ones it goes to is determined by a value 0-127 set by an external midi CC command value which is then converted to binary. Therefore if you put in 1 (0000001 in binary) - then the signal just goes to the port Out1 - if its 16 it is 0010000 therefore only port Out16 passes on the signal. Though if it is 15, the signal flows through Out1, Out2, Out4 and Out8 (15 being 0001111 in binary).
I dont have access to the machine with the compiled version, and I only compile for the dwarf. But if anyone wants to try it out, please do!
AudioRouter:
MidiRouter:
If anyone wants to compile them and post the results here, feel free.
Its released under gnu 3.0 so all the usual no warranty of fitness for purpose caveats apply!
Oh and there is no html interface - its just the built in one, so you’ll have to do the binary calculations yourselves
Just wondering about the pros and cons of editing that file. I assume switchbox type plug-ins won’t get updates that could undo that change. Would it affect my existing pedalboards which use this plug-in?
I did it more than 2 years ago, so far no problem. As you said, probably because these plugin were not updated. If you want another way for audio routing you can use Toggle_2IN and Xfade1to2st, both in the Beta store and CV assignable.
Not sure how you have built this. But you could try MOD Cloud Builder and upload a make file for a more user-friendly way to install. http://builder.mod.audio/ if it’s written in Faust, Max gen~ or Pure Data (hvcc). This way you’ll get a build for all devices
And in the code below, I just have to make sure the folder name follows the repo name:
# Copy additional files from package directory to the installed LV2 bundle
cp -rL $($(PKG)_PKGDIR)/bolliedelay.lv2/* $(TARGET_DIR)/usr/lib/lv2/bolliedelay.lv2/
The cloud builder in order to run seems to require a mod box connected to the computer. Mine is a dwarf. But will the cloud builder still compile for duo also?
The source path of the copy command should correspond to the .lv2 folder location in your git repository. The target path should correspond to the mod devices plugin folder. So that should be $(TARGET_DIR)/usr/lib/lv2/<your_plug_name>.lv2/
Correct. But it will compile for all other devices too.
There could be differences between your project and this example. So no guarantees this mk file can be copied line for line.
I managed to test today your midirouter and audiorouter plugins.
I must say that they are pretty handy/useful plugins for a lot of pedalboards, despite being quite simple. I suppose many users agree with me on this.
If you could manage to get a somewhat easier-to-understand method to open the gates, I guess that we would find some other community member eager to design an interface for it.
With that, plus adding it to the MOD Cloud Builder (just like @DaveM does with his insanely cool plugins), you would be a huge step closer to getting them on the beta shop and from there, then into the normal shop.
Perhaps we should also fork this thread so your plugins get their own thread.
Hi @jon , thanks for the kind words! Unfortunately I am insanely busy at work at the moment right now, but should have free time over Christmas.
I realise that binary isnt for everyone but using it for the gate openings means you only need 1 midi-learn to get that working.
An html interface using javascript which could translate 7 checkboxes into a decimal number would be ideal
I believe that by January 8 at the latest I should be able to get these plugins on the MOD Cloud Builder (as well as a few others including a rewrite of the ALO looper as you advised)
These routers are super cool! I just tried the MIDI router out on my Dwarf and I love the binary concept and also the numerous outputs. The big issue, however, is that this plugin doesn’t pass pitchbend data. I haven’t tested what other messages are getting filtered out but, when you get the time, if you could make the router simple pass ALL MIDI, that would be great!
You’re welcome Just trying to get these plugins (that as I wrote can be quite useful) not into “waste”
I agree with you. There are pros and contras and a single assignment it’s definitely a huge pro.
I guess that we should open the discussion to the community. If there’s something that this community excels is on finding great solutions for this type of stuff.
Yes. Adding my 5cents on it, what about if you use something like the interval control from Shiroverb (for sxample):
Just trying to get these plugins (that as I wrote can be quite useful) not into “waste”