Published: 2017-01-17
Written by hydlide
Published: 2017-01-17
VST plugin support: add any instrument or effect plugin to Reason’s rack; Delay compensation makes all signal paths play in perfect, phase-locked sync; Opens songs and synth patches made in Reason Compact - the free pocket music studio for iOS. The best free VST's to download. Browse our ever growing library of free VST plugins to use in your productions.
VST in Reason is something people have been requested a lot of times. It has been stated back in the days that Propellerhead will not integrate the VST format. Nor are there any plans regarding integrating VSTs in the Digital Audio Workstation called Reason (yes, we can call it a DAW). At some point in time when Reason 6.5 got released the program got its own unique platform for external plugins. Which is a great step forward. Most of the external plugins as Rack Extensions work seamless in the workflow of the program itself. While this has been there for quite some time there is still an outcry for VST support in Reason. For those who really want to use VST support in Reason, this topic might be for you. Since we'll be diving right in to it. We'll also discuss the different downsides with this setups and different 'work flow issues' you may need to be aware of.
VST since Reason 9.5
While this is quite fresh, vst will be supported since Propellerhead Reason 9.5. 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.
Learn More: Delivering on our #1 feature request, VST plugins have come to Reason. It's the creative flow you know an.
VST the old Method
Before diving in to it, there is always the option of 'Rewire'. Rewire is a protocol which allows other DAWs (that do support VST) to run reason in the background. In this case the other DAW is the host and Reason just hangs in there in the back ground. For a complete list of daws that support the Rewire protocol you can check the wikipedia list.
There is a lot to say about this type of set up. Since in theory you will need 2 different programs to make use of it. Where Reason is used as a Synth (since in rewire mode you connect directly to the Rack while sending midi data to different devices). At the same time you using the other DAW to make music with. This may sound fine as it is. But there are some major drawbacks to this workflow.
- the user needs to have full understanding working with 2 DAWs
- the reason file needs to be saved as well as the song file. If you want to reload the session you need 2 files. One for the DAW, the other for Reason. I am not 100% sure if this is still the case, but it used to work that way.
- memory load (since your running 2 programs next to each other)
- cpu load might become an issue
- latency might become an issue
- the user needs to have full understanding working with 2 DAWs
- the reason file needs to be saved as well as the song file. If you want to reload the session you need 2 files. One for the DAW, the other for Reason. I am not 100% sure if this is still the case, but it used to work that way.
- memory load (since your running 2 programs next to each other)
- cpu load might become an issue
- latency might become an issue
At some extend, if there is no real other alternative to get VST working with Reason. Then this might eventually be the only real solid solution there is. Sure, there are issues. But I never said this would be easy.
VST with Midi Out
Since Reason 7 there is a new way to control a VST (where VST stands for Virtual Studio Technology). In this version you have a Midi Out in Reason to control an external VST program. While original Midi Out was implemented to control external hardware, yet it works perfect to control VST instruments that allow it. And this the catch: Not every VST allows this. And not every 'setup' (eg: hardware) allows this to happen. There are a few requirements for this to work. And I know there is Mac OS. I don't own a Mac, there for I cannot make any conclusion on how this works on a Mac.
See Full List On Waves.com
Minimum requirements for this VST method:
- A Program to Loop the Midi (in this case I am using loopMidi)
- A VST that runs as stand alone
- Minimum Reason version: Reason 7
- multiple Audio Cards that support VST (not required, I will get back to this)
- A Program to Loop the Midi (in this case I am using loopMidi)
- A VST that runs as stand alone
- Minimum Reason version: Reason 7
- multiple Audio Cards that support VST (not required, I will get back to this)
LoopMidi
Best VST Host? - ReasonTalk.com
The idea behind loop midi is to use this as a 'midi bridge' between Reason and the VST. In this case it allows you to control multiple VST instruments at the same time (while using multiple midi loop interfaces). After installing to program loop midi, you will need to set up a Midi interface. Just to keep things simple, give it a solid name that would define what you are using it for.
Midi Out in Reason 7
For the next step, you will need an instrument called Midi Out. This can be added inside the Rack. The only important thing is to select the proper Midi Out channel. In my case it is a setting called 'Reason Midi Out'. Because this is the midi port I created inside loopMidi.
Midi Input VST
Here is the 'tricky' part. Since not every VST instrument will work the same. The most important parts are:
- The VST instrument needs a stand alone version of the plugin (not every VST has this, but most instruments from Native Instruments work as a stand alone version. #1)
- The VST needs to accept a Custom Midi Port.
- Per VST the workflow may be different
- The VST instrument needs a stand alone version of the plugin (not every VST has this, but most instruments from Native Instruments work as a stand alone version. #1)
- The VST needs to accept a Custom Midi Port.
- Per VST the workflow may be different
As an example, I will show a screenshot from Native Instruments Massive on how the Midi Port configuration may look like:
As far as most native instrument I have tested, these will have a similar set up. Under the menu 'file' there is a setting called 'Audio and Midi' settings. This will display the above picture after selecting the Midi Tab. When done so, make sure the Midi Port you are using in loopMidi is turned 'on' (by default, it is turned off!). When done so, you can go back to reason. Select the Midi Out, and play notes. This even works with the on screen piano.
Multiple Audio Cards
In case you want to play the VST as is, you can stop here. Since it should already be working as it is. However, sometimes you may need to 'sample' the input from the VST to another track. Jasper from therSitez has presented an awesome video which displays this method. It comes down to have the Audio Output from the VST going through a specific audio port. Next you create an audio track. There you will select the same audio channel as input. Hit record.. and you are all set to go. At this point in time I can't display any images regarding this technique because the laptop I am writing on does not have multiple audio card, my desktop does. Since I have already tested this workflow, I therefor can confirm that it works. Only disadvantage with the audio cards: they need to work with Asio4All. Other wise.. it is going to be a no-go.
VST Samples in Reason
Some VST instrument have data libraries where the sound sources are RAW wave files. I know that for instance Battery has this, same goes for AbSynth 4. At some point you are able to use the sound source from different VST and load these up directly inside an NN-XT. Or Kong. I depends if they sound proper enough, and if the VST instrument is using raw sample data by default. In most cases, this is not the case. But I thought I would just add this option to the list of ways to get VST sounds inside the Reason Rack.
There is also the method to record every single note from a VST inside a DAW that supports it, export the sound as a Wav File and import those back inside the NN-XT. While this workflow is really time consuming, I can say I have done this method once using Legacy Cell in the past. There for I know.. it is a real time consuming job to export it, load it up, layer it and so. This method also has some limitations to it (since your only using raw souns). But I am just saying, it can be done.
For now, this kind of sums up my chain of thoughts when it comes to using VST instruments in Reason. Have a good evening!
1. This is based on experimenting with VSTs from Native Instruments like Monark, Reaktor 6, AbSynth 4 and Massive
VST in Reason is something people have been requested a lot of times. It has been stated back in the days that Propellerhead will not integrate the VST format. Nor are there any plans regarding integrating VSTs in the Digital Audio Workstation called Reason (yes, we can call it a DAW). At some point in time when Reason 6.5 got released the program got its own unique platform for external plugins. Which is a great step forward. Most of the external plugins as Rack Extensions work seamless in the workflow of the program itself. While this has been there for quite some time there is still an outcry for VST support in Reason. For those who really want to use VST support in Reason, this topic might be for you. Since we'll be diving right in to it. We'll also discuss the different downsides with this setups and different 'work flow issues' you may need to be aware of.
VST and using Reason Rewire
Reason Rewire is a protocol which allows other DAWs (that do support VST) to run reason in the background. In this case the other DAW is the host and Reason just hangs in there in the back ground. Free vst plugin bass enhancer. For a complete list of daws that support the Rewire protocol you can check the wikipedia list.
There is a lot to say about this type of set up. Since in theory you will need 2 different programs to make use of it. Where Reason is used as a Synth (since in rewire mode you connect directly to the Rack while sending midi data to different devices). At the same time you using the other DAW to make music with. This may sound fine as it is. But there are some major drawbacks to this workflow.
- the user needs to have full understanding working with 2 DAWs
- the reason file needs to be saved as well as the song file. If you want to reload the session you need 2 files. One for the DAW, the other for Reason. I am not 100% sure if this is still the case, but it used to work that way.
- memory load (since your running 2 programs next to each other)
- cpu load might become an issue
- latency might become an issue
- the user needs to have full understanding working with 2 DAWs
- the reason file needs to be saved as well as the song file. If you want to reload the session you need 2 files. One for the DAW, the other for Reason. I am not 100% sure if this is still the case, but it used to work that way.
- memory load (since your running 2 programs next to each other)
- cpu load might become an issue
- latency might become an issue
At some extend, if there is no real other alternative to get VST instruments working with Reason. Then this might eventually be the only real solid solution there is. Sure, there are issues. But I never said this would be easy.
VST instruments and Midi Out in Reason
VST (Virtual Studio Technology) instruments can be controlled since Reason 7. Since this version you have a Midi Out in Reason to control an external VST program. While original Midi Out was implemented to control external hardware, yet it works perfect to control VST instruments that allow it. And this the catch: Not every instrument allows this. And not every 'setup' (eg: hardware) allows this to happen. There are a few requirements for this to work. And I know there is Mac OS. I don't own a Mac, there for I cannot make any conclusion on how this works on a Mac.
Minimum requirements for this VST method:
- A Program to Loop the Midi (in this case I am using loopMidi)
- A VST that runs as stand alone
- Minimum Reason version: Reason 7
- multiple Audio Cards that support VST (not required, I will get back to this)
- A Program to Loop the Midi (in this case I am using loopMidi)
- A VST that runs as stand alone
- Minimum Reason version: Reason 7
- multiple Audio Cards that support VST (not required, I will get back to this)
LoopMidi
The idea behind loop midi is to use this as a 'midi bridge' between Reason and the VST. In this case it allows you to control multiple VST instruments at the same time (while using multiple midi loop interfaces). After installing to program loop midi, you will need to set up a Midi interface. Just to keep things simple, give it a solid name that would define what you are using it for.
Midi Out in Reason 7
For the next step, you will need an instrument called Midi Out. This can be added inside the Rack. The only important thing is to select the proper Midi Out channel. In my case it is a setting called 'Reason Midi Out'. Because this is the midi port I created inside loopMidi.
Midi Input VST
Here is the 'tricky' part. Not every VST instrument will work the same. The most important parts are:
- The VST instrument needs a stand alone version of the plugin (not every VST has this, but most instruments from Native Instruments work as a stand alone version. #1)
- The VST needs to accept a Custom Midi Port.
- Per VST the workflow may be different
- The VST instrument needs a stand alone version of the plugin (not every VST has this, but most instruments from Native Instruments work as a stand alone version. #1)
- The VST needs to accept a Custom Midi Port.
- Per VST the workflow may be different
As an example, I will show a screenshot from Native Instruments Massive on how the Midi Port configuration may look like:
As far as most native instrument I have tested, these will have a similar set up. Under the menu 'file' there is a setting called 'Audio and Midi' settings. This will display the above picture after selecting the Midi Tab. When done so, make sure the Midi Port you are using in loopMidi is turned 'on' (by default, it is turned off!). When done so, you can go back to reason. Select the Midi Out, and play notes. This even works with the on screen piano.
Multiple Audio Cards
In case you want to play the VST as is, you can stop here. Since it should already be working as it is. However, sometimes you may need to 'sample' the input from the VST to another track. Jasper from therSitez has presented an awesome video which displays this method. It comes down to have the Audio Output from the VST going through a specific audio port. Next you create an audio track. There you will select the same audio channel as input. Hit record.. and you are all set to go. At this point in time I can't display any images regarding this technique because the laptop I am writing on does not have multiple audio card, my desktop does. Since I have already tested this workflow, I therefor can confirm that it works. Only disadvantage with the audio cards: they need to work with Asio4All. Other wise.. it is going to be a no-go.
VST Samples in Reason
Some VST instrument have data libraries where the sound sources are RAW wave files. I know that for instance Battery has this, same goes for AbSynth 4. At some point you are able to use the sound source from different VST and load these up directly inside an NN-XT. Or Kong. I depends if they sound proper enough, and if the VST instrument is using raw sample data by default. In most cases, this is not the case. But I thought I would just add this option to the list of ways to get VST sounds inside the Reason Rack.
There is also the method to record every single note from a VST inside a DAW that supports it, export the sound as a Wav File and import those back inside the NN-XT. While this workflow is really time consuming, I can say I have done this method once using Legacy Cell in the past. There for I know.. it is a real time consuming job to export it, load it up, layer it and so. This method also has some limitations to it (since your only using raw souns). But I am just saying, it can be done.
For now, this kind of sums up my chain of thoughts when it comes to using VST instruments in Reason. Have a good evening!
1. This is based on experimenting with VSTs from Native Instruments like Monark, Reaktor 6, AbSynth 4 and Massive
Written by hydlide
Published: 2017-01-17
Get producing music straight away with free VST plug-ins and samples in KOMPLETE START, taken from our leading production suite, KOMPLETE. Get REAKTOR PLAYER, KONTAKT PLAYER, KOMPLETE KONTROL, free effects VST plug-ins, free synth plug-ins, and sampled instruments to use in your own productions, as much as you want.
Download over 2,000 sounds and more than 6 GB of content – drums and percussion, basses, acoustic instruments, synths, pads and atmospheres, and more – plus VST plug-in instruments, effects, and other free resources for music production.
FREE DOWNLOAD
Download over 2,000 sounds and more than 6 GB of content – drums and percussion, basses, acoustic instruments, synths, pads and atmospheres, and more – plus VST plug-in instruments, effects, and other free resources for music production.
FREE DOWNLOAD
SYNTHS
A selection of VST synths, complete with 500+ professionally-designed presets for any genre.
SAMPLED INSTRUMENTS
Nine pro-grade sample-based VST instruments – vintage synths, acoustic instruments, drums, and more.
EFFECTS
A tube compressor and 13 versatile effects, great for guitars, drums, vocals, synths, or anything you like.
KOMPLETE KONTROL
Find, play, and tweak all your sounds, instruments and effects from one powerful plug-in.
SAMPLES
Almost 1,500 loops and samples from our popular Expansions range, suitable for use in any DAW.
KONTAKT PLAYER
A sample player that runs all NI KONTAKT instruments, and hundreds of instruments from other companies.
REAKTOR PLAYER
A powerful platform that runs all REAKTOR-based synths and effects from NI and other creators.
HOW TO USE VST PLUGINS
VST plugins are virtual instruments and effects that you can use in productions. They can recreate classic synth designs, or represent completely new ways of making sound. VST plugins are easy to use; download them, install, and your DAW will pick them up and let you use them in the workstation. From classic instruments to experimental indie gems, there’s a huge world of both paid and free VST plugins to choose from. Native has spent decades creating and developing some of the world’s leading VST plugins with REAKTOR, KONTAKT, KOMPLETE KONTROL, and loads more.
HOW TO USE VST PLUGINS FOR SYNTH SOUNDS
VST plugins can be used in a wide variety of ways to create synth sounds for songwriting and production. Almost any instrument can be turned into a VST plugin, and more often than not, when you need a certain kind of sound there’s a VST plugin for it. There are several varieties of VST plugins for synth sounds that are worth noting. Polyphonic VST plugins create more than one note at a time, so are great for building complex melodies, chords, and harmonies, while monophonic VST plugins play one note at a time and are commonly used for basslines. Some VST plugins strictly model themselves on reproducing sounds you would expect from analogue instruments, but others go way beyond that. Wavetable VST plugins like MASSIVE and MASSIVE X tend to focus on helping producers create something unusual and completely different to traditional instruments, and can be more useful for experimental productions than other VST plugins.
HOW TO USE MULTIPLE VST PLUGINS
Trying things out and exploring new territory is hugely important when trying to craft something unique, and using multiple VST plugins will give you a wide range of instruments and sounds to work with. Chaining multiple VST plugins together sis a typical way to start crafting a sound you can call your own. Feeding one VST plugin instrument into a VST plugin effect will alter them even further. This is also common with digital production as lots of recording tools come in VST plugin form – there’s no issue with running multiple VSTs at once – simply load them in and start playing. Native offers over 2,000 free sounds and more than 6 GB of free VST plugin content with KOMPLETE START, so if you’re looking for some inspiration it’s a great way to get started.
DON’T HAVE AN ACCOUNT YET?
Download Native Access, create an account, and find all KOMPLETE START contents under the NOT INSTALLED tab.
DOWNLOAD NATIVE ACCESS (MAC) DOWNLOAD NATIVE ACCESS (WINDOWS)
Learn how to install KOMPLETE START..
Please see the Native Access system requirements.
DOWNLOAD NATIVE ACCESS (MAC) DOWNLOAD NATIVE ACCESS (WINDOWS)
Learn how to install KOMPLETE START..
Please see the Native Access system requirements.
ALREADY HAVE AN ACCOUNT?
Login and request KOMPLETE START:
GET KOMPLETE START
GET KOMPLETE START
INSTALLATION GUIDE FOR NEW CUSTOMERS
1: Create a Native Instruments account using Native Access
2: Your KOMPLETE START products might take a moment to appear – press the refresh button if necessary. Install all included products by clicking ‘Install All’ in the ‘Not Installed’ tab in Native Access.
3: Launch KOMPLETE KONTROL. Important: Run it in standalone mode before using it in your DAW. This allows it to scan and organize all your sounds.