using Sonar as slave rewire device for running VST's with Reason

I use Sonar. My wife uses Reason (in a Windows platform). She would like to use the Korg Legacy M1 and Wavestation VST's. Is it possible to use Sonar as the (slave) VST host, with Reason as the Master and Midi/audio recorder?
In other words, could Rewire be used to send MIDI from Reason to Sonar/Korg Legacy, and use Rewire to send audio from Sonar/Korg Legacy back into Reason?
 
thanks
 
Keith

Additionally, Reason can only be the ReWire Slave.  It cannot be the host.
 
There are a fair number of posts on the Propellerhead forum about accomplishing almost the same thing using the new MIDI out device in Reason.  
 
Basically, the MIDI path is:
Reason -> MIDI Out to some loopback device -> your synth
and then the Audio path is:
your synth -> Reason.
 
ReWire (and thus Sonar) don't enter the picture at all.  It's pretty easy to do the audio stuff on a Mac, some folks had used a program called "Jack" to do a similar thing on the windows side.  I have played with Jack and found it a bit fiddly for my taste, but YMMV.
 
Hope that helps.

Yes, I do that.  And that's why I walked away from that one.  Spend so much time fiddling that you forget to make music.

I have a Focusrite 8i6 which is supposed to have this capability, but I cannot get it to function in any practical sense.
 
Since the ASIO driver can't be opened by multiple programs simultaneously, there's no way to send output to the the loopback channel. They have a video on setting this up, but it's done on a Mac where I suspect the CoreAudio drivers handle this a bit better.
 
I only mention this because the spec sheet of the Scarlett interfaces would lead you to believe that it will meet your requirements, but I just don't think that it will on a Windows machine.
See below, the interface can be configured to work this way.

AndyDavis
I have a Focusrite 8i6 which is supposed to have this capability, but I cannot get it to function in any practical sense.
 
Since the ASIO driver can't be opened by multiple programs simultaneously, there's no way to send output to the the loopback channel. They have a video on setting this up, but it's done on a Mac where I suspect the CoreAudio drivers handle this a bit better.
 
I only mention this because the spec sheet of the Scarlett interfaces would lead you to believe that it will meet your requirements, but I just don't think that it will on a Windows machine.

The ASIO limitation is that only one driver can access a device.
Multiple audio hosts can address the ASIO driver this is what happens when Sonar is set to share driver with other programs. When you select this only the audio program that has Windows focus can be heard. So make sure it's deselected. I only mentioned it as it seems counter intuitive.

Have any of you heard of this program, if I understand correctly permits multiple hosts to share an ASIO driver?
 
http://odeus-audio.com.au/Odeus/AsioLinkPro
 
 

mcdonalk
Have any of you heard of this program, if I understand correctly permits multiple hosts to share an ASIO driver?
 
http://odeus-audio.com.au/Odeus/AsioLinkPro
 
 

Yes I use it, (or rather the earlier version) to permit running more than one ASIO enabled app and for some routing flexibility.
 
I've done all the workarounds to loopback audio into Reason.  Most of those solutions are about as useful and surprisingly similar to learning to chew your own toenails.
 
The most useful way of integrating Reason's workflow into Sonar is done by using Rewire in the way it was intended with Reason as the slave and Sonar as the host.  If you spend as much time working out how that works as you would using any of the workarounds you'll find it's a great match.
 
Using ASIOLink or an Audio Hardware Loopback I can get the latency nicely low but why would I want to jump through those hoops when there's a perfectly accepted way of working with the two programs.
 
It is perfectly possible to send midi from Reason to Sonar however whilst Rewired using the EMI in Reason and virtual (or real) MIDI cables to trigger as many VSTi's in Sonar as you like.  There is no penalty for doing that other than Sonar will be rendering the audio which is certainly no hardship. amd of you want to keep the Reason project self contained just bounce all the VST synths you ultimately want in the Reason project to printed stems and import them back into Reason if you so wished.

subtlearts
It was and is fiddly, but possible. I had it working under X3 last year - full bi-directional control with both programs running (Sonar as host, Reason as slave), sending MIDI and audio in either direction, however I wanted to. Round-trip latency was even manageable, not brilliant but not crippling. But it took a bunch of brain-befuddling workarounds to get it happening, and I never ended up using it for anything in a production sense. Just one of those technical mountains one climbs "because it's there"... wait, does anyone else do that?

Guilty as charged