I am not 100% sure if this is still the case, but it used to work that way. If you want to reload the session you need 2 files. the reason file needs to be saved as well as the song file. the user needs to have full understanding working with 2 DAWs But there are some major drawbacks to this workflow. At the same time you using the other DAW to make music with.
Where Reason is used as a Synth (since in rewire mode you connect directly to the Rack while sending midi data to different devices). Since in theory you will need 2 different programs to make use of it. There is a lot to say about this type of set up. For a complete list of daws that support the Rewire protocol you can check the wikipedia list. In this case the other DAW is the host and Reason just hangs in there in the back ground. Rewire is a protocol which allows other DAWs (that do support VST) to run reason in the background. VST the old Methodīefore diving in to it, there is always the option of "Rewire". The whole rack interface contains a VST Host, and you can seamless drag and drop VST intstruments and plugins in to the reason rack as of the latest version. While this is quite fresh, vst will be supported since Propellerhead Reason 9.5. We'll also discuss the different downsides with this setups and different 'work flow issues' you may need to be aware of. For those who really want to use VST support in Reason, this topic might be for you. While this has been there for quite some time there is still an outcry for VST support in Reason. Most of the external plugins as Rack Extensions work seamless in the workflow of the program itself. At some point in time when Reason 6.5 got released the program got its own unique platform for external plugins.
Nor are there any plans regarding integrating VSTs in the Digital Audio Workstation called Reason (yes, we can call it a DAW). It has been stated back in the days that Propellerhead will not integrate the VST format. VST in Reason is something people have been requested a lot of times.
0 kommentar(er)
