I have submitted a support request.fde101 wrote: Fri Jul 17, 2020 3:29 pm Go to tracktion.com and click the "Support" tab along the right edge of the window.
Reason 11 Rack Plugin and MIDI Out in Waveform 11
-
- KVRist
- Topic Starter
- 414 posts since 25 Aug, 2018
-
- KVRist
- 391 posts since 21 Feb, 2009
I had this working in one of my videos but it seems to only work with the AU version of the Reason Rack plugin on macOS. I didn't realize this at the time. I haven't tested on Windows but it might that it doesn't work with VST or VST3.courtjestr wrote: Wed Jul 01, 2020 10:35 pm I am trying to use Reason 11 Rack plugin with Waveform 11, specifically the Scales and Chords player. The Scales and Chords player is supposed to take MIDI input and remap the input to a specific scale or chord on the output. It does do that in Waveform 11 but unfortunately it also passes through whatever MIDI notes appear on the input. I cannot figure out how to prevent the MIDI input from passing through. It does work correctly in Cakewalk. Any ideas?
-
- KVRist
- Topic Starter
- 414 posts since 25 Aug, 2018
There is no VST2 version of Reason 11 Rack, only VST3. The problem is with the VST3 version.gigazaga wrote: Sun Aug 02, 2020 2:08 pmI had this working in one of my videos but it seems to only work with the AU version of the Reason Rack plugin on macOS. I didn't realize this at the time. I haven't tested on Windows but it might that it doesn't work with VST or VST3.courtjestr wrote: Wed Jul 01, 2020 10:35 pm I am trying to use Reason 11 Rack plugin with Waveform 11, specifically the Scales and Chords player. The Scales and Chords player is supposed to take MIDI input and remap the input to a specific scale or chord on the output. It does do that in Waveform 11 but unfortunately it also passes through whatever MIDI notes appear on the input. I cannot figure out how to prevent the MIDI input from passing through. It does work correctly in Cakewalk. Any ideas?
-
- KVRist
- Topic Starter
- 414 posts since 25 Aug, 2018
This is almost certainly a bug in JUCE 5. I compiled Kushview Element with the latest version of JUCE (6.0.1) and it no longer has this bug. Just to confirm that it was not a fix in Element, I compiled the same code with JUCE 5.4.5 and it exhibited the bug.