Resetting up my systems

[musicman691]

Originally Posted by JFreak

Bear in mind that these bridge plugins that are capable of hosting VST instruments might not be as stable as native AAX, so your mileage may very well vary.

I haven't heard that and if you do know of some please pass that info along. Not trying to be snarky but if there's troubles out there the community would be appreciative of such knowledge.

[lvly5t]

Can you rewire cubase as slave to PT? I know you can with Ableton and Reaper and then you can use the plugins that way?

[musicman691]

Originally Posted by lvly5t

Can you rewire cubase as slave to PT? I know you can with Ableton and Reaper and then you can use the plugins that way?

You probably could but there are easier ways like using Blue Cat Patchworks or MB7 and you don't have to muck about with Rewire protocol.

[lvly5t]

ahh I see.
out of curiosity what do you mean by muck about with rewire protocol?
I've pretty much been able to "plug and play" when rewire is concerned.
Like I rewire Reason and Ableton as slave to Pro Tools and its easy peazy?
All I do is create a stereo instrument track and choose Reason or Ableton as a plug-in and it launches that way.

I do know if you want to individually route virtual instruments from Reason or Ableton in it is a little time consuming (like if you want stems from those VI's) with all those VI's routing to seperate tracks.
But I just make one bus and bus it to all the tracks I want to make stems for and solo the VI that I want to put on that track.

example: Reason has 3 VI's going (synth 1, synth 2, synth 3) so on the stereo instrument track that the Reason plugin is on I create a bus labeled "Reason Bus"
Then I make 3 stereo audio tracks (labeled synth 1, synth 2, and synth 3) with the input on all 3 set to "Reason Bus" and arm synth 1 to record.
Then I go inside Reason and solo synth 1 and record it on to Pro Tools for my print track or stem.
There are other more "proper" ways of doing that but I find that to be the quickest work flow wise.
Other wise I would have to create 3 stereo instrument tracks all having the reason plugin and click the plugin which brings up the ReWire window and set up the signal flow of each of those synths to the Rewire's channels (idk if they are busses or channels) and then do it that way.

So aside from things like that what other issues or headaches does Rewire have?

[musicman691]

Originally Posted by lvly5t

ahh I see.
out of curiosity what do you mean by muck about with rewire protocol?
I've pretty much been able to "plug and play" when rewire is concerned.
Like I rewire Reason and Ableton as slave to Pro Tools and its easy peazy?
All I do is create a stereo instrument track and choose Reason or Ableton as a plug-in and it launches that way.

I do know if you want to individually route virtual instruments from Reason or Ableton in it is a little time consuming (like if you want stems from those VI's) with all those VI's routing to seperate tracks.
But I just make one bus and bus it to all the tracks I want to make stems for and solo the VI that I want to put on that track.

example: Reason has 3 VI's going (synth 1, synth 2, synth 3) so on the stereo instrument track that the Reason plugin is on I create a bus labeled "Reason Bus"
Then I make 3 stereo audio tracks (labeled synth 1, synth 2, and synth 3) with the input on all 3 set to "Reason Bus" and arm synth 1 to record.
Then I go inside Reason and solo synth 1 and record it on to Pro Tools for my print track or stem.
There are other more "proper" ways of doing that but I find that to be the quickest work flow wise.
Other wise I would have to create 3 stereo instrument tracks all having the reason plugin and click the plugin which brings up the ReWire window and set up the signal flow of each of those synths to the Rewire's channels (idk if they are busses or channels) and then do it that way.

So aside from things like that what other issues or headaches does Rewire have?

For me Rewire protocol when it comes to Reason isn't all that easy to work with, especially if you're working with Combinators in Reason. To get control over both notes and volume you need to send to two separate parts of Reason and the Combinator. If you don't use Combinators then the routing is easy. Sad thing is there's no documentation that's at least available to us end users from Reason or anyone else on how the MIDI implementation is handled in Rewire. If you send to a single path you can either get to trigger MIDI notes or control volume when using Combinators. To control both drives me to drink

[lvly5t]

Originally Posted by musicman691

For me Rewire protocol when it comes to Reason isn't all that easy to work with, especially if you're working with Combinators in Reason. To get control over both notes and volume you need to send to two separate parts of Reason and the Combinator. If you don't use Combinators then the routing is easy. Sad thing is there's no documentation that's at least available to us end users from Reason or anyone else on how the MIDI implementation is handled in Rewire. If you send to a single path you can either get to trigger MIDI notes or control volume when using Combinators. To control both drives me to drink

I know exactly what you mean. I just do all creation via MIDI with it in rewire then I bus a print track and work only in pro tools. I dont use any eq's, comps, or FX in Reason. It makes it easier for me that way. But yeah its a pain and should be more straight forward. I think ultimately though Reason is on its way out tbh