If you have a shit-ton of waves plugins like I do, and your rack effects view is now unmanageable, this is how I've been working with Waves plugins inside Reason.
First, download Studiorack here: https://www.waves.com/downloads/free
Now, disable every single one of your waves plugins, EXCEPT for Studiorack:
You should now have Studiorack as the only Waves plugin in the list:
Studiorack is like an all in one plugin chainer, where all your Waves plugins will show up nicely organized:
Here's How To Better Manage Waves Plugins In Reason
You can chain as many as 8 plugins, plus you can save them like Combis. You can also move them around: Plus each plugin slot has a handy bypass button.
In addition, you can assign functions to the knobs, like a combinator.
THE END.
In addition, you can assign functions to the knobs, like a combinator.
THE END.
Very cool, I will try this.
Producer, songwriter, multi-instrumentalist. I make indie pop as Port Streets, 90s/shoegaze as Swooner, and Electro as Yours Mine.
Does this mean no access to the CV mod matrix (as in the default Reason plugin setup)?
Sorry, I could care less about CV as I never use it so I don't know if CV works like a normal single VST plugin. CV mod matrix is still there though.
So another thing I use this for, and something that is actually very handy, is that if you have GTR installed, all the stomp boxes show up as individual plugins, which again can be moved around and re-ordered, in a visual manner:
But you can still load the normal GTR plugin, which by itself loads 6 stomps, so you could in theory load as many as 48 stomp boxes, customize them like crazy, and save your setup as one tiny preset, which can then be loaded in any DAW, so you can take your setup with you.
This worked out well for my guitarist friend who doesn't have Reason, but who created a pretty amazing sounding gtr chain which he saved and emailed to himself for him to use in Pro Tools at home.
Too bad this only works with Waves plugins, but there are rumors they will open it up to 3rd parties.
More tips:
You don't have to disable every single waves plugin, you can keep enabled those you use most frequently for added convenience:
Due to the nature of Reason's alphabetical plugin sort, Studio rack will be near the bottom of the list, which is what I don't want. Luckily, you can now create custom Effects folders, where the sort depends on the order you drag and drop them in: So mine looks like:
You could also just right-click in the rack and use the text menu to select a plugin, but because I have way too many plugins, getting to Waves is kind of a hassle since it's way at the bottom of the list.
The studio rack + custom Waves effects folder setup is what works best for me inside Reason. I like it.
You don't have to disable every single waves plugin, you can keep enabled those you use most frequently for added convenience:
Due to the nature of Reason's alphabetical plugin sort, Studio rack will be near the bottom of the list, which is what I don't want. Luckily, you can now create custom Effects folders, where the sort depends on the order you drag and drop them in: So mine looks like:
You could also just right-click in the rack and use the text menu to select a plugin, but because I have way too many plugins, getting to Waves is kind of a hassle since it's way at the bottom of the list.
The studio rack + custom Waves effects folder setup is what works best for me inside Reason. I like it.
I like new ideas, so thanks for this one.hurricane wrote: ↑16 Jan 2018If you have a shit-ton of waves plugins like I do, and your rack effects view is now unmanageable, this is how I've been working with Waves plugins inside Reason.
First, download Studiorack here: https://www.waves.com/downloads/free
Now, disable every single one of your waves plugins, EXCEPT for Studiorack:
disable.png
You should now have Studiorack as the only Waves plugin in the list:
studiorack.png
Studiorack is like an all in one plugin chainer, where all your Waves plugins will show up nicely organized:
chainer.png
I don't know if you can help with a question though - like many others on this forum I've experienced problems with several of the waves plugins not operating correctly (or at all) in a Windows 10 OS. My way around this is to push the problem devices through JBridge and then job done. Since that leaves me with a bunch of devices showing up in Reason under their own names plus a bunch of devices showing up as JBridge devices, I'm guessing that this means that the Waves JBridge devices would not show up in Studiorack??
Thanks
Sorry, I haven't used a Windows machine in years, but if Jbridge is anything like Bluecat's Patchwork, then you can disable every single Waves plugin and still load them and Studiorack through the wrapper. So in my case, using Patchwork, I can load Studiorack:
And then still load all the Waves plugins even though I "disabled" them all. It reads them off the Waveshell.
Also note that I used the VST3 version, which then enables sidechain, so yes you CAN use Waves plugins for sidechaining duties inside Reason:
And then still load all the Waves plugins even though I "disabled" them all. It reads them off the Waveshell.
Also note that I used the VST3 version, which then enables sidechain, so yes you CAN use Waves plugins for sidechaining duties inside Reason:
Thanks Hurricane. I haven't tried it yet (the 99 euro put me off for now), but I did notice another post from a Windows user saying that attempting to get the VST3 functionality through BC Patchwork results in a crash.....hurricane wrote: ↑19 Jan 2018Sorry, I haven't used a Windows machine in years, but if Jbridge is anything like Bluecat's Patchwork, then you can disable every single Waves plugin and still load them and Studiorack through the wrapper. So in my case, using Patchwork, I can load Studiorack:
Screen Shot 2018-01-19 at 2.31.04 PM.png
And then still load all the Waves plugins even though I "disabled" them all. It reads them off the Waveshell.
Also note that I used the VST3 version, which then enables sidechain, so yes you CAN use Waves plugins for sidechaining duties inside Reason:
Screen Shot 2018-01-19 at 2.32.20 PM.png
viewtopic.php?t=7502336
Yeah, Patchwork crashes for me - but of course only in Reason.
So sick of things working fine elsewhere but crapping out in Reason - oh and it's not Reason's fault! Always the developer. Lol, f*ck this, man...
I guess you'll just have to wait for them to add VST3 support - in 5-10 years.
So sick of things working fine elsewhere but crapping out in Reason - oh and it's not Reason's fault! Always the developer. Lol, f*ck this, man...
I guess you'll just have to wait for them to add VST3 support - in 5-10 years.
-
- Information
-
Who is online
Users browsing this forum: Trendiction [Bot] and 11 guests