which daw is best for showing plugin errors ?

[Paul_Pulsonix]

I've always just tested in Reaper, to find out later that my plugin distorted and crashed in Logic.
All is fixed now, and next time i'm going to test in Logic too obviously before release.

Which DAW's are notriously hard on plugins so this doesn't happen again ? Should I test others ? Auval and Pluginval test are perfect now. are there any other validations I should run ?

[Marvinh]

I have heard fl studio is the one to test because of their weird block sizes .my plugins always run weird on windows so definitely test different os as well .

[gambero]

In my experience each DAW has its own quirks when it comes to plugin hosting, so really the more you test the better.
Test on as many the major ones as you can. You can also consider setting up a small testing team

[mystran]

I have heard fl studio is the one to test because of their weird block sizes .my plugins always run weird on windows so definitely test different os as well .

FL studio has never been the only DAW that split blocks, it's just that some other DAWs mostly do it in some special cases, where as FL does it fairly regularly. If you have a problem with "weird" blocks, then FL is the best DAW to use for debugging though, precisely because it splits so regularly.

[Marvinh]

Yes specially when doing internal block sizes of functions .

But for instance juce horizontalverticaldrag is a horizontal drag in some daws and a vertical drag in others. threw me for a loop . Stick to vertical or horizontal only .

[JustinJ]

Unfortunately they've all got issues that you may run in to. Reaper is great to develop with as it loads so fast, but I'd also test on Ableton, Logic, FL Studio and Bitwig at least. Mac and PC. And Protools if that's relevant.

[kerfuffle]

Different DAWs also handle playhead position (PPQ) in different ways. For example, I *think* Reaper always puts the playhead exactly on a sample, so if a measure starts in between two samples (as the measure length is not always a whole number of samples), the playhead can actually end up before or after the measure's start position.

Looping is another difference. Some DAWs chop the block in half at the end of the loop region, others don't and expect you to detect where inside the block the jump back to the start of the loop happens. And so on...

[Benedict]

Plenty of 'loose' VST do not open or behave well in Reason.
Those that do behave tend to be rock solid.

[knob_monster]

Compile your debug builds with AddressSanitizer (ASan) enabled and run them inside JUCE's AudioPluginHost (or Reaper) attached to your IDE.