"Reason sound" test :)

[chk071]

I don't know better shootout video on youtube in this topic,
Minimoog Softsynth Shootout: Diva MiniV3 Monark Legend Minimonsta vs Model D

IMO Legend is the winner here but the real thing is the real thing especially in movement ((dunno it's matter or not I'm listening it with Sennheiser HD-800 headphone)) round 7-8

That test isn't the best IMO. He messed up the filter tuning of Monark on one test, and, he also in no way covered that smacking resonant behavior, with short filter decay, which IMO is so characteristic for the Minimoog filter sound. Monark is much better in that regard, when you compare it to Legend, for example. But, don't take it from me... try it out yourself.

[EnochLight]

It wasn't supposed to be a null test, just how I named the files.
I'd otherwise post some screens from the analysis, right?

Right, I saw what you posted now.

There's no way real null test would work using VSTs, because there's so much more variables that might make it fail.

Are you sure? A null test using a VST should be accomplished pretty easy by bouncing a track to wav, exporting, and doing the test in all DAW being compared. This is of course assuming you turn off all effects and anything else that would otherwise "color" the sound. What other variables would make it fail?

Also, a DAW having its - theoretical - "own sound" would be hard to prove with null test, because it's not about there being differences, but them being in specific places and intensity, like e.g. the mix would be more noisy, more bass heavy, with some skewed EQ, etc. That's a completely different analysis.

So chill, it was just a name I chose

I'm quite chill, thanks, but you are correct in that a DAW does not have its "own sound" (as this has been pointed out countless times before doing null tests). A DAW's "own sound" is generated by any effects or processing used (whether they are stock or 3rd party). There's where the differences will always lie.

Don't get me wrong - I think your comparison in this thread was useful for what you were trying to accomplish.

[zzz00m]

#4 clearly has the most professional sound.

[chk071]

Well... it's called Studio One 4 Pro for a reason.

[zzz00m]

Well... it's called Studio One 4 Pro for a reason.

+1

[antic604]

There's no way real null test would work using VSTs, because there's so much more variables that might make it fail.

Are you sure? A null test using a VST should be accomplished pretty easy by bouncing a track to wav, exporting, and doing the test in all DAW being compared. This is of course assuming you turn off all effects and anything else that would otherwise "color" the sound. What other variables would make it fail?

I meant for example plugin delay compensation - if there's even one sample difference between how the DAWs compensate the proper null-test would fail. Or some small differences in how notes in MIDI clip trigger processing in the VST. Or how the velocity or note-length info is translated for the VST. Or how VSTs might have a free running phase or LFOs (I tried to pick patches that don't, but can't be 100% sure). Or even some small differences in BPM between DAWs, which would be irrelevant when comparing bounce of un-warped audio files...

I just meant it's more reliable to do test with audio files than with VSTs, but I attempted the latter any way, because I thought it's a fun exercise. The downside would be avoiding of the proper null-test, instead relying on our ears to tell if there's a noticeable difference, because - after all - that's what important, right?

Well... it's called Studio One 4 Pro for a reason.

+1