I just posted over on the Reasontalk forum in a thread announcing R11 and asked about aax support.
IOW I'd like to be able to handle Reason like I do BFD3 where I don't use BFD's mixer but bring things out to individual tracks like I would when working with a physical drum kit.
REASON 6 UPGRADE FROM REASON 4 MANUAL
I can't seem to find a way to set routing to the aux outputs of Patchwork into PT - how do I set things up in Patchwork to it's aux outputs? The Patchwork manual is zero help and I don't know if I want to do all my mixing of synths inside Reason. What I've had a problem with in Patchwork is getting individual audio outputs from it into PT. The MIDI might not be a problem if one remembers to use the synth version of Patchwork. This is heaven as I've never been a huge fan of Rewire with all the problems I've had with the input routing from PT to Reason. In any event, this is huge step in the right direction of Reason, IMHO! With an AAX version that allowed VST hosting, Reason would be the most powerful VI on the planet.because it could essentially be virtually ANY VI or combination of VI's all in one rack! One of the reasons I often use Reason is because of the rack and how easy it is to build unique and multi-layered patches all in one rack or Combinator. Having to use the rack instead of individual plugins isn't that much of big deal to me. And, if they did, then making it so it can also host VSTs within it, like Patchwork does, shouldn't be all that difficult either. It shouldn't be all that hard for them to make Reason AAX. We definitely need an AAX version as I’m not sure how well the Reason rack will work in something like Patchwork due to the MIDI and audio capabilities. This also includes the players and third part RE devices.ĪU is coming at the end of the year and AAX is on the radar but not confirmed. The entire rack is one plugin with the modules hosted within the rack. In fact, ReWire is discontinued as if v11.Īlso, the modules won’t be individual plugins.
0 kommentar(er)
