There is no standard on LV2 on how the pitchbend range is defined/used.
VST kinda has something for this, but not LV2. It is a good conversation to have, likely we need to ask something on the LV2 development mailing list.
MPE vs MIDI2 is a great question.
Will MPE be phased out now that MIDI2 is starting to be a thing? from what I understood, they are not compatible.
I have seen a few opensource synths that handle MPE (surge and helm, anything else?).
The other issue is MIDI guitars send out MPE/Multi-Channel MIDI. “Faking” MPE/Multi is definitely possible, though CPU expensive with SIX copies of whatever synth receiving a single channel.
And this should be a nice workaround for your multiple channel issue:
Just set the 6 channels your guitar is sending to the one the synth plug will receive.
I am also a guitar MIDI user so I absolutely feel your pain with the pitchbend situation. That filter that @falkTX posted above will surely help, but it still sucks that so many of the synth plugins have different bend ranges without any way of knowing what they are or a way to change them.
Not sure how I missed the event filter.
/smacks forehead with palm.
falkTX Will MPE be phased out now that MIDI2 is starting to be a thing? from what I understood, they are not compatible.
I’m not entirely certain. I don’t see how MPE could possibly be incompatible with MIDI2 since the new standard will allow you to define things any way you want to. I may only be a fledgling programmer but I’ve been a using MIDI since 1988 with my Commodore64 SO I’ve been following the MIDI2.0 thing pretty religiously for the past two years or so. As far I know just about every single thing is addressable and definable, even on the fly if need be. I’m not sure they’ve released an official “standard parameter names” list yet but the entire construct is designed to be backwards compatible.
edit: MIDI-Capability-Inquiry (MIDICL) is the concept they’ve rolled with.
You can join the MIDI Association for free and download the spec files here: https://www.midi.org/specifications-old/category/midi-2-0-specifications-v1-1
Words words words, basically you can make a controller that says “I am a controller with a knob labeled cutoff frequency” and a source that will say “I have a parameter named cutoff frequency” and they will auto connect at high resolution, instead of having to assign specific CC numbers to each thing.
OR, to address the specificity of MPE, you would tell a sound source that it was receiving MultiChannel/MPE from a port and it would just work.
bleo
Yeah I got that part. I was referring to “faking MPE” as in having six instances of Dexed all being fed separate channels.
As far as I can tell, all of the synth plugins receive MIDI as OMNI so channel mapping isn’t neccesary, they just play whatever channels you feed them.
Stripping the pitch wheel should do just fine, for piano/pads/strings anyway. Not so great for the expressive leads though.
I also have a wish for a CV plug-in. In principle, it is a modification of the LFO plug-in. It is intended to be used to turn the controls of plug-ins (e.g. reverb, delay, etc.) up to a defined point at any speed.
In CV_Tutorial it is shown how to turn a knob of an effect with the AMS LFO2 plugin. The controller is turned back and forth in the form of a sine curve with the help of the LFO plug-in.
My wish for the plug-in would be to limit the running time of the curve. That means, for example, that you only run through the first quarter of the sine curve, then the process stops. If we take the example from the tutorial, this would mean that the controller is only turned up, where it then remains. Only when the LFO plug-in receives a new command does it continue.
Maybe this possibility already exists, but I haven’t found anything about it.
Yes, danmh, I tried it once. It did not work. But may be I did it wrong, I tested it only for some minutes. I will try this again. Many thanks for the tip.
The problem has been the stopping. In my eyes you can rise and fall the speed of CV. But to stop it is not included. But let me test once again.
Hi Danmh,
Your tip with the “Slew Rate Limiter” was excellent! I was actually able to solve my “problem” with it. It didn’t work right away, because I had to realise that the “Control to CV” has a value range from 0 to 10, whereas the “Slew R. L.” has a value range from -5 to 5, but I stuck a “CV attenuator” in between, which adjusts the value ranges. Now I press the footswitch of the midi controller and the mix control of my reverb effect slowly turns up. It works! I am thrilled!
It’s a pity that one has so little time because of too much work, so my improvements to the pedalboard took a few days. I have now put in some fine-tuning. You can find my new enhanced pedalboard with the feature here: Endless Decay Pedalboard. An audio sample is available as well.
Cool Thanks for sharing!
I love the effect with the reverb, can really find a lot situations where that could be useful changing the “mood” from something more “in your face” to something more “spacy”
SO I’ve been following the MIDI2.0 thing pretty religiously for the past two years or so. As far I know just about every single thing is addressable and definable, even on the fly if need be. I’m not sure they’ve released an official “standard parameter names” list yet but the entire construct is designed to be backwards compatible.
Yeah! This is right! But LFO can be stopped, right?
