VST instrument MIDI Thru to Melda Envelope (REAPER and Bitwig)
- KVRist
- 69 posts since 2 Sep, 2014
Some VST instruments don't readily pass on the track MIDI. I've found this with Native Instruments' Massive and FM8 as well as Cakewalk Z3TA+. If you want to put a Melda plug-in after one of these and have the track's MIDI trigger a Modulator Envelope you might have problems.
In REAPER you can do it:
- bring up the FX window and click the Plug In Pin Connector button (top right between Param and UI)
- select I/O / MIDI output / Merges with MIDI bus
- add a Melda plug in after the synth
- as before then select I/O / MIDI input / Map REAPER MIDI buses to VST3 buses
You should now be getting MIDI Thru for mod fun.
Does anyone know how to do this in Bitwig 2?
In REAPER you can do it:
- bring up the FX window and click the Plug In Pin Connector button (top right between Param and UI)
- select I/O / MIDI output / Merges with MIDI bus
- add a Melda plug in after the synth
- as before then select I/O / MIDI input / Map REAPER MIDI buses to VST3 buses
You should now be getting MIDI Thru for mod fun.
Does anyone know how to do this in Bitwig 2?
No Such Error | nosucherror.com
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I'd suggest asking on Bitwig's forum, they could probably help you more.
-
- KVRist
- 43 posts since 24 Feb, 2021
I've noticed that Melda plugs also don't pass midi through themselves, does anyone know if this ever got fixed/a legit workaround? Is this entirely a Bitwig-dev-side issue?
only workaround I've found so far is to run something like Element VST host and use it's internal MIDI routing
only workaround I've found so far is to run something like Element VST host and use it's internal MIDI routing
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
^^^
Works OK in Bitwig 3 here.
I created a MIDI clip then added a MeldaProduction plug-in (I tried several), followed by a MIDI monitor, to the track. On playback the MIDI was seen in the monitor.
Works OK in Bitwig 3 here.
I created a MIDI clip then added a MeldaProduction plug-in (I tried several), followed by a MIDI monitor, to the track. On playback the MIDI was seen in the monitor.
-
- KVRist
- 138 posts since 10 May, 2015
Do you have MIDI Thru activated in the settings?GXG wrote: Mon Mar 22, 2021 10:18 pm I've noticed that Melda plugs also don't pass midi through themselves, does anyone know if this ever got fixed/a legit workaround? Is this entirely a Bitwig-dev-side issue?
only workaround I've found so far is to run something like Element VST host and use it's internal MIDI routing
I'm on Bitwig. Once that option is turned on, everything works as you'd expect.
EDIT: This works in MSoundFactory and MPowerSynth. This option doesn't seem to exist in standalone MXXX. This might be something worth adding in.
EDIT 2: Of the quick testing that I've done, MXXX seems to be the only Melda plugin where MIDI isn't passed through where there's no option to stop it. Can we call this a bug?
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
There will be a MIDI thru option in the next version for all plugins, but note that this is quite a bit nonstandard.
-
- KVRer
- 11 posts since 22 May, 2020
Cool, just found this thread after trying to get the MIDI out of Mdrummer (inside of MXXX) routed into another drum VST inside of Cubase. The MIDI output from MXXX to Cubase shows up as an option, but i don't think Mdrummer itself is passing the MIDI itself..
So this will be sorted next update (or thereabouts!)? If so, this will be very much appreciated, thank you...
So this will be sorted next update (or thereabouts!)? If so, this will be very much appreciated, thank you...
