VST plugins on macOS will be matched with VST plugins on Windows. 64 Bit only - FL Studio for macOS is only compatible with 64 Bit AU and VST plugins. There is no automatic bridging as there is with VST on Windows. See here why we did not support 32 Bit on macOS. AU vs VST - We recommend using the VST version of plugins, when available, on.

Hey there, I have recently been developing a VST plugin with JUCE and have come across an issue that I haven’t been able to find a solution to. Before the weekend I had Ardour and the plugin working fine, since then I have attempted to stabilise my audio subsystem and in the process uninstalled and reinstalled Ardour (not sure what the previous version was, sorry). Since the update Ardour. When you first launch Reason, it will scan for any installed VST plugins from its default plug-in path. If you installed a new plug-in or virtual instrument to a custom folder, however, you first need to add that new path within the Advanced Preferences. Follow these steps to add a new plug-in for use with Reason. Propellerhead Reason 10 is the tenth version of the software, with improvements, optimizations, and more than 3 GB of additional audio content. These are samples and loops in the Reason Loop Supply section and in the Reason Drum Supply section. Several new tools have appeared. Hello I am having an issue with a particular VST plugin (TBH it is mine.) not loading in Reason. Getting the very non useful message: 'There were errors when inspecting some plugins'. Note that VST3 plugins are not supported, and neither are 32-bit VST plugins. Also, VSTs that output MIDI are not supported in Reason. Multitimbral VSTs (that can receive on separate MIDI channels) are not supported either. You will then have to use one instance of the VST for each sound/channel. Over 400 free VST plugins and VST instruments to use with FL Studio, Ableton Live, and Pro Tools. Includes Bass, Synths, Pianos, Strings. These are the best FREE VST plugins & Free VST Effect Plugins that you can download online. Reason, Ableton Live, and other VST supported software.

Published: 2017-01-17

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.

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

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.

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)

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. 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

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. 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

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. /vst-plugin-helix.html. 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)

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

Free Reason Plugins

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

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

Hello,

Reason Vst Download

I've tried searching on this topic without much luck, so figured I'd start a new post in hopes that someone might be able to help..
I have historically created all of my Live projects on my iMac, however, I recently got a newer Macbook, so I've been creating solely on that.. I put every plugin / software application onto the laptop that was originally on my iMac desktop - so I figured there would be no issues.
Unfortunately, I went to open a project created a few months ago - on my desktop - and upon loading the project, it says 'The VST Plugin Could Not Be Found' next to a list of a few plugins that ARE on my laptop. Some Waves plugins, Serato Sample, etc etc..

Free Reason Vst Plugins

I tried to Re-Scan plugins from within Ableton Live before even opening a project, to see if that would update things, but no luck..
I think that the issue is the plugins have a different file directory path than they did on my desktop, so Live is not finding them.. which leads me to my question -- is there ANY way to relocated the plugins without losing my settings??? The pop-up box reporting the missing plugins does NOT give the option to locate these 'missing' plugins.. although, again, they are on my laptop.

Reason 10 Vst Plugins Folder

I know that I could just re-load the plugins in question, but patch selections / presets are lost if I do this. Further, on Serato Sample, I have to re-load the samples I had chosen (not to mention their key, the same slice settings, etc..) which is impossible.

Best Vst Plugins For Reason

You would think that this would be a common issue and/or easily rectified, but I can't seem to find any solutions.. Any help would be greatly appreciated. Thank you!!