#REASON 9.5 TO 10 UPGRADE UPGRADE#

You could have a MIDI splitter, similar to the audio or cv splitters if you wanted to send a MIDI out to several VI's MIDI INs at one time. Combinator set ups using that could become quite complex and textured. Imagine if you had 2 MIDI out ports on, say, the Dual Arp Player, and could route Arp 1 to one VI and Arp 2 to a different one. The other thing I want to see if MIDI cable routing similar to how we can route cables now on the back of the rack. Reaper can host VSTs when in slave can't be that hard to pull off programming wise. Frankly I don't see why that's an issue now.

#REASON 9.5 TO 10 UPGRADE UPGRADE#

But, the REAL solution is for the P-heads to simply upgrade Reason to allow VST hosting while Reason is in slave mode. Now, if Blue Cat made a Reason version of Patchwork.then that would make it so you can host VSTs in Reason while in Slave mode. If I'm just going to use a single instance of a particular VST VI, then I can just host it directly in PT using Reaper or Patchwork. Mainly its in the Combinator in Reason that I do that. I just open Reason then Pro Tools to do things this way if I want to use patches created using VSTs in Reason. So, I don't see how adding VEPro makes that any different.

I can do that now using virtual midi and the loop back audio feature on my Focusrite interface. So, even if you somehow hosted Reason i VEPro without it being in slave mode, you'd still have to route the MIDI from Pro Tools to Reason to play a part, and then route the audio back from Reason to Pro Tools to lay down the track. But I doubt it would solve the issue as you can't host VSTs with Reason in slave mode anyways. Do you by any chance have VEPro on your system? I wonder if that could be used as a workaround to get R9 and higher to host vsts while working for the main part in PT? I have VEPro 6 but just R8 like I said.

Reason 9.5 to 10 upgrade