# Different Flavors of VST/AU DAWs **URL:** \ **Category:** General JUCE discussion\ **Created:** [September 6, 2018, 8:48pm UTC](https://forum.juce.com/t/different-flavors-of-vst-au-daws/29307 "2018-09-06T20:48:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![midiculous](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/midiculous/32/582_2.png) [@midiculous](https://forum.juce.com/u/midiculous)\ **Post date:** [September 6, 2018, 8:48pm UTC](https://forum.juce.com/t/different-flavors-of-vst-au-daws/29307/1 "2018-09-06T20:48:21Z")
Hey guys…Just wondering what are your approaches to the different Flavor of DAWS…Namely Machine and Reason. They seem not to adhere to the standard framework and so far we have not been able to get our plugins working for Reason (Windows) and Machine. Can anyone share or gleam any specific things they had to update to get these two working? ---
**Author:** ![pizzafilms](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/pizzafilms/32/562_2.png) [@pizzafilms](https://forum.juce.com/u/pizzafilms)\ **Post date:** [September 6, 2018, 9:43pm UTC](https://forum.juce.com/t/different-flavors-of-vst-au-daws/29307/2 "2018-09-06T21:43:07Z")
I can tell you from my experience that my plugin works in pretty much all DAWs without changing anything in my code for a particular DAW. Well, except for Cubase and this issue: > [@Cubase calling setCurrentProgram after setStateInformation](https://forum.juce.com/t/cubase-calling-setcurrentprogram-after-setstateinformation/21637/14): > > It turns out that this has been discussed here since 2010…and on KVR since 2005… The threads basically say that this is a somewhat known issue with some VST hosts including Cubase, Bitwig Studio and Ableton Live and likely not a JUCE issue at all. It looks like the solution is possibly two fold: not changing the program if setCurrentProgram() is called with the same index, and also setting a timer in setStateInformation() and not changing the program if setCurrentProgram() is called within… Of course, Pro Tools has it’s own hoops to jump through just to get it to build, but not to actually run. When you say “not been able to get our plugins working…”, what exactly happens? Have you tried running them in the debugger? ---
**Author:** ![midiculous](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/midiculous/32/582_2.png) [@midiculous](https://forum.juce.com/u/midiculous)\ **Post date:** [September 6, 2018, 10:29pm UTC](https://forum.juce.com/t/different-flavors-of-vst-au-daws/29307/3 "2018-09-06T22:29:47Z")
I get crashes from Machine and from Reason. All other major ones work. Also it doesn’t work in Akai. So I guess I should preface my statement with saying…Our products work in major DAWs, but struggle with the minor ones and I can confirm that Machine, Akai, and Reason all crash. ---
**Author:** ![pizzafilms](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/pizzafilms/32/562_2.png) [@pizzafilms](https://forum.juce.com/u/pizzafilms)\ **Post date:** [September 7, 2018, 12:26am UTC](https://forum.juce.com/t/different-flavors-of-vst-au-daws/29307/4 "2018-09-07T00:26:56Z")
But _where_ are they crashing? ---
**Author:** ![otristan](https://avatars.discourse-cdn.com/v4/letter/o/f0a364/32.png) [@otristan](https://forum.juce.com/u/otristan)\ **Post date:** [September 7, 2018, 7:13am UTC](https://forum.juce.com/t/different-flavors-of-vst-au-daws/29307/5 "2018-09-07T07:13:55Z")
Juce plugin wrapper should be robust enough so the problem lies in your own code. So it’s a matter of init/deletion order in different thread, stuff like that. ---
**Author:** ![dave96](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/dave96/32/8487_2.png) [@dave96](https://forum.juce.com/u/dave96)\ **Post date:** [September 8, 2018, 10:33am UTC](https://forum.juce.com/t/different-flavors-of-vst-au-daws/29307/6 "2018-09-08T10:33:27Z")
Sounds like you could do with some more validation/testing? This is the reason I made pluginval: [Anouncing "pluginval" an open-source cross-platform plugin validation tool](https://forum.juce.com/t/anouncing-pluginval-an-open-source-cross-platform-plugin-validation-tool/27710), to replicate esoteric host behaviour and be able to test/fuzz in an automated way. If you find any host specific weirdness let me know and I’ll try to add a test for it. The more tests we have, the more bulletproof plugins will become 😃