New alpha reason plugin midi out
Posted: 13 Dec 2019
Just see this
You can already do that cant you ? For example you can load up an arpeggiator vst on a track and a reason rack on another track now change the midi input of the reason rack tack to that of the midi arpeggiator track.
I think that’s what they meant—about getting MIDI output from VSTs into the Reason DAW.visheshl wrote: ↑13 Dec 2019You can already do that cant you ? For example you can load up an arpeggiator vst on a track and a reason rack on another track now change the midi input of the reason rack tack to that of the midi arpeggiator track.
I think I've done this before
I think it depends on whether the vst is sending midi or audio
Also on DAW implementation ?
I like that guy's Re...Kraft!
So things like Xfer Records Cthulu will work in Reason?guitfnky wrote: ↑13 Dec 2019I think they mean we want to be able to get MIDI output from VSTs into the Reason DAW. no idea if there’s a workaround in Reason VST, but you definitely can’t do it in the DAW.visheshl wrote: ↑13 Dec 2019
You can already do that cant you ? For example you can load up an arpeggiator vst on a track and a reason rack on another track now change the midi input of the reason rack tack to that of the midi arpeggiator track.
I think I've done this before
I think it depends on whether the vst is sending midi or audio
Also on DAW implementation ?
I think it should work let me try it with blue arp, if that works, why shouldn't cthulhu work ? Gimme ten minutes, will let you know
YES you can use vsts like bluearp to trigger reason plugin sounds. Cthulhu should work too.
Theoretically if we have a rack extension which takes a cv input and outputs midi cc data(lets u select which midi cc to change via cv), and then you send this to the midi out device, we could alter another VST's parameter via lfos or REs in reason. We just need a rack extension which converts cv data to midi cc datadanc wrote: ↑13 Dec 2019Now... if I could run Reason's CV devices out into my other DAW (say as MIDI CC events) this would be super powerful.
All those Rack Extension LFO devices that I have would have a serious lease of life running my instruments and effects in Studio ONE.
Or am I hoping for too much... and should just accept MIDI NOTES.
Not in standalone Reason, though. Wondering if this new MIDI-out device will allow it.
You can use virtual midi ports, like loop midi.EnochLight wrote: ↑13 Dec 2019Not in standalone Reason, though. Wondering if this new MIDI-out device will allow it.
do you have a step by step for how to do this? I’m very skeptical. I tried using a loopback to do this last week, but there was no way for me to get the VST MIDI out of the VST rack device. I’m familiar with looping back in from an external standalone app, but I still don’t think you can do what you describe in Reason.visheshl wrote: ↑13 Dec 2019You can use virtual midi ports, like loop midi.EnochLight wrote: ↑13 Dec 2019
Not in standalone Reason, though. Wondering if this new MIDI-out device will allow it.
Send midi out from cthulhu to a virtual midi port.
Create a midi keyboard in controllers using the virtual midi port. Now you have out from cthulhu into reason.
I use a mac so i have a program called midi pipe running between my midi keyboard and reason using a virtual midi cable, i use it to alter my midi data i send to reason. For example i can transpose the notes i play on my keyboard.
Let me check if i can get midi out of a vst into a virtual port from ableton...guitfnky wrote: ↑13 Dec 2019do you have a step by step for how to do this? I’m very skeptical. I tried using a loopback to do this last week, but there was no way for me to get the VST MIDI out of the VST rack device. I’m familiar with looping back in from an external standalone app, but I still don’t think you can do what you describe in Reason.visheshl wrote: ↑13 Dec 2019
You can use virtual midi ports, like loop midi.
Send midi out from cthulhu to a virtual midi port.
Create a midi keyboard in controllers using the virtual midi port. Now you have out from cthulhu into reason.
I use a mac so i have a program called midi pipe running between my midi keyboard and reason using a virtual midi cable, i use it to alter my midi data i send to reason. For example i can transpose the notes i play on my keyboard.
I’d love to be proven wrong though.
Sure, but that’s a clunky workaround that is a pain in the ass and not nearly as functional as proper support. We’ve been able to use VST’s in Reason since the Record days using MIDI and audio loopback. It was never an enjoyable approach, though.visheshl wrote: ↑13 Dec 2019You can use virtual midi ports, like loop midi.EnochLight wrote: ↑13 Dec 2019
Not in standalone Reason, though. Wondering if this new MIDI-out device will allow it.
Send midi out from cthulhu to a virtual midi port.
Create a midi keyboard in controllers using the virtual midi port. Now you have out from cthulhu into reason.
I use a mac so i have a program called midi pipe running between my midi keyboard and reason using a virtual midi cable, i use it to alter my midi data i send to reason. For example i can transpose the notes i play on my keyboard.
Fyi, midi pipe lets you create as many virtual ports, and its free
(This has nothing to do with reason midi out device, this is about routing midi from the plugin into reason)
Well thats a different thing, they should add support for midi vsts in reason standalone. In plug-in, you can already send midi from another vst to reason plugin.EnochLight wrote: ↑13 Dec 2019Sure, but that’s a clunky workaround that is a pain in the ass and not nearly as functional as proper support. We’ve been able to use VST’s in Reason since the Record days using MIDI and audio loopback. It was never an enjoyable approach, though.visheshl wrote: ↑13 Dec 2019
You can use virtual midi ports, like loop midi.
Send midi out from cthulhu to a virtual midi port.
Create a midi keyboard in controllers using the virtual midi port. Now you have out from cthulhu into reason.
I use a mac so i have a program called midi pipe running between my midi keyboard and reason using a virtual midi cable, i use it to alter my midi data i send to reason. For example i can transpose the notes i play on my keyboard.
Fyi, midi pipe lets you create as many virtual ports, and its free
(This has nothing to do with reason midi out device, this is about routing midi from the plugin into reason)
wait, you’re using a second DAW simultaneously just to get MIDI out of that VST, into the loopback, and then back into Reason? that’s a useless workaround. you’re using two separate sets of unsynchronized transport controls?visheshl wrote: ↑13 Dec 2019Let me check if i can get midi out of a vst into a virtual port from ableton...guitfnky wrote: ↑13 Dec 2019
do you have a step by step for how to do this? I’m very skeptical. I tried using a loopback to do this last week, but there was no way for me to get the VST MIDI out of the VST rack device. I’m familiar with looping back in from an external standalone app, but I still don’t think you can do what you describe in Reason.
I’d love to be proven wrong though.
Result
Ok so this would depend on the DAW.
In Ableton create a midi track.
Load midi arp(blue arp, cthulhu whatever) in the track.
Create one more midi track.
In the second midi track, select track 1 bluearppl in the midi from. Below that select blue arp.
Now since this is a midi track, it will have midi to instead of audio to.
In the midi to, select the virtual midi port.
Put the second track monitor to IN
Now open up reason
Create a midi keyboard with your virtual midi port.
Create whatever device like europa to test.
Now go back to ableton. Select the arpeggiator track and play the midi vst plugin.
I just tested it, its working.
My bad man, i totally misunderstood what you guys were talkiing about. I thought since this thread is about the midiout in reason plugin, i thought the original poster wanted to trigger reason plugin from another vst in the DAW(not standalone reason), then it became more confusing....i thought you wanted to trigger reason standalone from another vst in another daw....oops...by the way my approach couldve still worked if they hadnt taken out rewire.guitfnky wrote: ↑13 Dec 2019wait, you’re using a second DAW simultaneously just to get MIDI out of that VST, into the loopback, and then back into Reason? that’s a useless workaround. you’re using two separate sets of unsynchronized transport controls?visheshl wrote: ↑13 Dec 2019
Let me check if i can get midi out of a vst into a virtual port from ableton...
Result
Ok so this would depend on the DAW.
In Ableton create a midi track.
Load midi arp(blue arp, cthulhu whatever) in the track.
Create one more midi track.
In the second midi track, select track 1 bluearppl in the midi from. Below that select blue arp.
Now since this is a midi track, it will have midi to instead of audio to.
In the midi to, select the virtual midi port.
Put the second track monitor to IN
Now open up reason
Create a midi keyboard with your virtual midi port.
Create whatever device like europa to test.
Now go back to ableton. Select the arpeggiator track and play the midi vst plugin.
I just tested it, its working.
interesting from a technical standpoint, but from a practical standpoint, pointless.