Please feel free to contribute to this thread any VST's which cause reason to Crash/Freeze/Crap Out/Cause any bother. Please include if it is a free plug-in or paid for with the name of the author/company if it is not a well known VST!
The 1st one here which I know now has major issues:
flux :: StereoToolV3 - Free. Caused reason to crash many times for me lost a good few projects because of it***
K-meter - Martin Zurther - Free. It is showing signs of performance issues buffer pop and crackles when moved not known if it causes carshes.
Ozone 5 - Completely froze Reason upon opening a project. DSP meter was in the red two different projects of the same opened. Plug-in windows pinned with the meter bridge opened. This one is a performance hog anyway so use carefully.
There must be more out there that cause problems please show them in this thread so we know what to avoid! or at least use with caution anyway.
***It crashes Blue Cats PatchWork in stand alone mode also when you change soundcards no other plug ins do that.
List of VST's not worth using because of their stability
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
Last edited by AttenuationHz on 15 Jun 2017, edited 1 time in total.
It is not too much of an ask for people or things to be the best version of itself!
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
short answer no. Reason forum not Studio one.Jmax wrote:Could the Ozone 5 be slower due to a slower computer? I have Ozone 5 and works fine in Studio One. I'm using Ozone 7 with Reason now and no problems at all. Although it is a hog for sure.
It is not too much of an ask for people or things to be the best version of itself!
I feel inclined to add Waldorf's Nave onto this list as there is no way to actually save any patch you would like to create without the entire instrument and Reason crashing. I reached out to Waldorf and they said the issue had been reported with other DAWs, and that they might look into fixing it sometime soon, but refused to tell me if it was an actual priority or not. No notification will be sent to customers if and when they fix a highly critical bug.
The instrument works fine as long as you do not want to save your patch.
I love the instrument, but am not at all impressed by the developers. This is a pretty expensive instrument, and such a horrible bug, and the communications from the developer did not leave me to believe they felt the issue was that important.
The instrument works fine as long as you do not want to save your patch.
I love the instrument, but am not at all impressed by the developers. This is a pretty expensive instrument, and such a horrible bug, and the communications from the developer did not leave me to believe they felt the issue was that important.
Fotizimo @ Instagram
on Surface Pro 4
Nektar Impact 25
Novation Launchkey Mini
Arturia SparkLE Spark Codec for Reason
on Surface Pro 4
Nektar Impact 25
Novation Launchkey Mini
Arturia SparkLE Spark Codec for Reason
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
Can you use reasons save feature?fotizimo wrote:I feel inclined to add Waldorf's Nave onto this list as there is no way to actually save any patch you would like to create without the entire instrument and Reason crashing. I reached out to Waldorf and they said the issue had been reported with other DAWs, and that they might look into fixing it sometime soon, but refused to tell me if it was an actual priority or not. No notification will be sent to customers if and when they fix a highly critical bug.
The instrument works fine as long as you do not want to save your patch.
I love the instrument, but am not at all impressed by the developers. This is a pretty expensive instrument, and such a horrible bug, and the communications from the developer did not leave me to believe they felt the issue was that important.
It is not too much of an ask for people or things to be the best version of itself!
I hadn't tried that, but suspect that will save the snap shot of the instrument, and not just the settings. This would require saving presets outside of Nave, and would not be an optimized experience.
Fotizimo @ Instagram
on Surface Pro 4
Nektar Impact 25
Novation Launchkey Mini
Arturia SparkLE Spark Codec for Reason
on Surface Pro 4
Nektar Impact 25
Novation Launchkey Mini
Arturia SparkLE Spark Codec for Reason
I just tested Ozone 5 with Reason on my other computer. Works perfect! I have no idea what you're talking about.AttenuationHz wrote:short answer no. Reason forum not Studio one.Jmax wrote:Could the Ozone 5 be slower due to a slower computer? I have Ozone 5 and works fine in Studio One. I'm using Ozone 7 with Reason now and no problems at all. Although it is a hog for sure.
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
Jmax wrote:I just tested Ozone 5 with Reason on my other computer. Works perfect! I have no idea what you're talking about.AttenuationHz wrote:short answer no. Reason forum not Studio one.Jmax wrote:Could the Ozone 5 be slower due to a slower computer? I have Ozone 5 and works fine in Studio One. I'm using Ozone 7 with Reason now and no problems at all. Although it is a hog for sure.
Completely froze Reason upon opening a project. DSP meter was in the red two different projects of the same opened. Plug-in windows pinned with the meter bridge opened. This one is a performance hog anyway so use carefully.
It is not too much of an ask for people or things to be the best version of itself!
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
It saves the setting too. Work around no? There is a setting in options also to give the VST keyboard focus I was unable to save presets in Kick 2 and enabling that fixed the issue worth a try.fotizimo wrote:I hadn't tried that, but suspect that will save the snap shot of the instrument, and not just the settings. This would require saving presets outside of Nave, and would not be an optimized experience.
It is not too much of an ask for people or things to be the best version of itself!
Maybe the VST isn't your problem. Could it be your project is to large and causing problems when using a more DSP intensive plugin. To say Ozone 5 is faulty and doesn't work properly inside Reason, is misleading. There are other factors that go into play. What are you using in that project that causes high DSP? If I have one instance of RE Spire it causes CPU spikes. I can have one Spire and 10 Omnisphere.. so it's all relative. Also many people are complaining about performance problems with Mac, you haven't stated any hardware or software.AttenuationHz wrote:Jmax wrote:I just tested Ozone 5 with Reason on my other computer. Works perfect! I have no idea what you're talking about.AttenuationHz wrote:short answer no. Reason forum not Studio one.Jmax wrote:Could the Ozone 5 be slower due to a slower computer? I have Ozone 5 and works fine in Studio One. I'm using Ozone 7 with Reason now and no problems at all. Although it is a hog for sure.Completely froze Reason upon opening a project. DSP meter was in the red two different projects of the same opened. Plug-in windows pinned with the meter bridge opened. This one is a performance hog anyway so use carefully.
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
This thread is not meant for discussions! Its simply to list plug-ins that you know have issues. If you want to Report RE spire for issues feel free to do so in a similar thread in Rack Extensions. I'm on windows and it is relative what my and others specs are. I never said it was faulty inside reason I simple said that it caused a crash because the VST window was pinned and the meter bridge was opened when the project saved and closed reopening it caused the crash and high DSP. Poke holes some where else buddy.Jmax wrote:Maybe the VST isn't your problem. Could it be your project is to large and causing problems when using a more DSP intensive plugin. To say Ozone 5 is faulty and doesn't work properly inside Reason, is misleading. There are other factors that go into play. What are you using in that project that causes high DSP? If I have one instance of RE Spire it causes CPU spikes. I can have one Spire and 10 Omnisphere.. so it's all relative. Also many people are complaining about performance problems with Mac, you haven't stated any hardware or software.AttenuationHz wrote:Jmax wrote:I just tested Ozone 5 with Reason on my other computer. Works perfect! I have no idea what you're talking about.AttenuationHz wrote:short answer no. Reason forum not Studio one.Jmax wrote:Could the Ozone 5 be slower due to a slower computer? I have Ozone 5 and works fine in Studio One. I'm using Ozone 7 with Reason now and no problems at all. Although it is a hog for sure.Completely froze Reason upon opening a project. DSP meter was in the red two different projects of the same opened. Plug-in windows pinned with the meter bridge opened. This one is a performance hog anyway so use carefully.
It is not too much of an ask for people or things to be the best version of itself!
"lost a good few projects because of it"
I tried to warn people VST comes along, this is exactly what people will be able to expect. And here it is.
Sent from my XT1575 using Tapatalk
I tried to warn people VST comes along, this is exactly what people will be able to expect. And here it is.
Sent from my XT1575 using Tapatalk
Last edited by etyrnal on 15 Jun 2017, edited 1 time in total.
"they might look into fixing it sometime soon"fotizimo wrote:I feel inclined to add Waldorf's Nave onto this list as there is no way to actually save any patch you would like to create without the entire instrument and Reason crashing. I reached out to Waldorf and they said the issue had been reported with other DAWs, and that they might look into fixing it sometime soon, but refused to tell me if it was an actual priority or not. No notification will be sent to customers if and when they fix a highly critical bug.
The instrument works fine as long as you do not want to save your patch.
I love the instrument, but am not at all impressed by the developers. This is a pretty expensive instrument, and such a horrible bug, and the communications from the developer did not leave me to believe they felt the issue was that important.
The instant I hear this attitude from a developer, I immediately stop using all of their products indefinitely.
Sent from my XT1575 using Tapatalk
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
If you just want to chat start a thread this thread is for listing plug-ins. Got any to contribute?etyrnal wrote:"they might look into fixing it sometime soon"fotizimo wrote:I feel inclined to add Waldorf's Nave onto this list as there is no way to actually save any patch you would like to create without the entire instrument and Reason crashing. I reached out to Waldorf and they said the issue had been reported with other DAWs, and that they might look into fixing it sometime soon, but refused to tell me if it was an actual priority or not. No notification will be sent to customers if and when they fix a highly critical bug.
The instrument works fine as long as you do not want to save your patch.
I love the instrument, but am not at all impressed by the developers. This is a pretty expensive instrument, and such a horrible bug, and the communications from the developer did not leave me to believe they felt the issue was that important.
The instant I hear this attitude from a developer, I immediately stop using all of their products indefinitely.
Sent from my XT1575 using Tapatalk
It is not too much of an ask for people or things to be the best version of itself!
for me the Waldorf plugins only work as expected if i start reason (or any other daw) with administrator rights (pc, win7, 64 bit). have you tried that?fotizimo wrote:I feel inclined to add Waldorf's Nave onto this list as there is no way to actually save any patch you would like to create without the entire instrument and Reason crashing. I reached out to Waldorf and they said the issue had been reported with other DAWs, and that they might look into fixing it sometime soon, but refused to tell me if it was an actual priority or not. No notification will be sent to customers if and when they fix a highly critical bug.
The instrument works fine as long as you do not want to save your patch.
I love the instrument, but am not at all impressed by the developers. This is a pretty expensive instrument, and such a horrible bug, and the communications from the developer did not leave me to believe they felt the issue was that important.
-
- Information
-
Who is online
Users browsing this forum: PhillipOrdonez and 9 guests