Samplitude: Best sounding Daw?

[IncarnateX]

"Factor analysis of differents tests from the past twenty years of research shows a significant support for our conclusions. Unfortunately some random guy at an unrelated internet forum says it isn' t so, therefore we must reject them.
Sorry Gentlemen, I expect your resignations on my desk in half an hour."

[trimph1]

"Factor analysis of differents tests from the past twenty years of research shows a significant support for our conclusions. Unfortunately some random guy at an unrelated internet forum says it isn' t so, therefore we must reject them.
Sorry Gentlemen, I expect your resignations on my desk in half an hour."

It does not matter how many decades of research went into this..someone will always come along and say the opposite.

Don't you just love it?

[bobbybland]

sounds great,but the workflow sucks in it compared to Studio One, but damn't all of the daws I've tried suck compared to the workflow in Studio One. yep..

bring on this bitwig, to test please, ahem..

[Trakstar]

sounds great,but the workflow sucks in it compared to Studio One, but damn't all of the daws I've tried suck compared to the workflow in Studio One. yep..

bring on this bitwig, to test please, ahem..

+1 for studio 1 workflow, working with REX slices is so easy as pulling out a slice and sticking it on a track. The Gui is well thought out, I want to buy it, but wont because I already have too many and if I keep on eventually some will just sit there gathering virtual dust. Shame though, I really do like it and all.
The free demo is excellent, just a bit limited with no vsts. Shame

[Hink]

this thread is still going

"wow that sounded so good last night* but today it sounds terrible today...what was I thinking?"


if you can relate to that statement and have experienced it then it's not your DAW, it's not colors, it's not the GUI, it's not your monitors, it's not your headphones, it's not the cables, it's not your pluggins, it's not your room acoustics...it's you.

If you want to blame everything else that's your problem, but it's still you. If you have not experienced that statement or cannot relate to it you have to find out why because something is amiss...the above statement is normal and a good thing, not a bad thing. But you really should take the time you are spending trying to be right in these threads and work on your skills.


FWIW I firmly believe the more you grow the more the above statement is true, at least that has been my experience going back to before I had a studio and I just played in bands. WE are the weakest link.

*or yesterday, last week or even last month for that matter

[IncarnateX]

It does not matter how many decades of research went into this..someone will always come along and say the opposite.

Don't you just love it?

Not really. But it keeps the business going, I'll give you that .

[IncarnateX]

"wow that sounded so good last night* but today it sounds terrible today...what was I thinking?"

if you can relate to that statement and have experienced it then it's not your DAW, it's not colors, it's not the GUI, it's not your monitors, it's not your headphones, it's not the cables, it's not your pluggins, it's not your room acoustics...it's you.

Nope, it's the drugs. Today I am sober.

[Hink]

"wow that sounded so good last night* but today it sounds terrible today...what was I thinking?"

if you can relate to that statement and have experienced it then it's not your DAW, it's not colors, it's not the GUI, it's not your monitors, it's not your headphones, it's not the cables, it's not your pluggins, it's not your room acoustics...it's you.

Nope, it's the drugs. Today I am sober.

[rifftrax]

Look, I don't resent it that you're philosophically unsophisticated. Perhaps you can design high end audio circuits from the ground up? I know, I can't.

But if you get a chance, check out Aristotle's four types of causation. It will help you get a grip on how to think through problems like whether or why DAWs might sound different to different people.

Your sarcasm does reflect some promising command of language, if not of reasoning.

Como

First off, you don't anything about me. Also, you are obviously all kinds of conceited. Good luck with your ego-trippin bro. Maybe there's an actual payout for that kind of pomp at the end of the day.

Eminently pragmatic conclusion.

WOW. Dude, you're not writing a scientific white paper - you're posting on a godforsaken forum. If you are some sort of rhode-scholar or esteemed professor then I feel really sorry for your pupils.

Using graduate-level language to express opinions on a high-school level topic is pure self-masturbation.

[Nighthawk77]

The best sounding DAW = the one you make the BEST music on the most intuitively.

This will always vary for every user.
So really there is no "best", just what is best for you.

[Pupok]

Maybe all sequencers sound null - when there no VST. But all works very different. You can consider me crazy)).

Here is images of one fragment of a track, which was made in 3 sequencers by the same pluggins with the same settings, the same pan law, the same panning, the same volume on tracks. Difference is obvious.

I can not understand - why track in reaper sounds lauder and more dirty at low end? Look at images.

http://postimage.org/gallery/1756db9k/a66d2b54/

[Trakstar]

Maybe all sequencers sound null - when there no VST. But all works very different. You can consider me crazy)).

Here is images of one fragment of a track, which was made in 3 sequencers by the same pluggins with the same settings, the same pan law, the same panning, the same volume on tracks. Difference is obvious.

I can not understand - why track in reaper sounds lauder and more dirty at low end? Look at images.

http://postimage.org/gallery/1756db9k/a66d2b54/

Yes, I can see your point. The audio shape and texture with the apparent peaks and troughs are all very clearly indicated, apart from in the reaper diagram where there appears to be a subtle difference in gain by a few decibels. Also examining the reaper picture I can clearly see the muddy and dirty low end from the spectral analysis of the audio you provided.

[Burillo]

Maybe all sequencers sound null - when there no VST. But all works very different. You can consider me crazy)).

Here is images of one fragment of a track, which was made in 3 sequencers by the same pluggins with the same settings, the same pan law, the same panning, the same volume on tracks. Difference is obvious.

I can not understand - why track in reaper sounds lauder and more dirty at low end? Look at images.

http://postimage.org/gallery/1756db9k/a66d2b54/

I won't call you crazy but i will say that it's probably user error or incompetence. Can you post the projects and the source files?

Also, not all VST's are equal. Some VST's won't even null when they are placed side by side in the same host - because part of their processing is either random (synths, saturators etc.) or otherwise different (round-robin/humanize in samplers for example).

To do a proper null test, you would have to use either wave files and not involve VST plugins at all (this is to test host's summing), or use wave files and VST's that linearly and predictably process sound e.g. simple EQ's (this is to test how host handles VST plugins). If host handles one plugin correctly, it correctly handles them all. There's no magic involved, host doesn't care if it's compressor or sampler, it's just numbers in - numbers out.

[Pupok]

Maybe all sequencers sound null - when there no VST. But all works very different. You can consider me crazy)).

Here is images of one fragment of a track, which was made in 3 sequencers by the same pluggins with the same settings, the same pan law, the same panning, the same volume on tracks. Difference is obvious.

I can not understand - why track in reaper sounds lauder and more dirty at low end? Look at images.

http://postimage.org/gallery/1756db9k/a66d2b54/

I won't call you crazy but i will say that it's probably user error or incompetence. Can you post the projects and the source files?

I can not. The project is in work and not allowed been showed out there. I can make a new project with a simple setup of elements - loop+bass+chords and so on if you want)). Result be the same. But for more than 14 years of practise I always see and hear one thing - sequencers work with VST on it's own way, differently. What is all that null tests? Just a simple WAV-tracks without any VST on slots rendered to one stereo WAV. Off course - there will be no difference. But i do not sure that they are correct tests.

Bla bla bla.... So, my opinion - all VST and VSTi sounds different in sequencers.))

[Burillo]

I can not. The project is in work and not allowed been showed out there. I can make a new project with a simple setup of elements - loop+bass+chords and so on if you want)). Result be the same. But for more than 14 years of practise I always see and hear one thing - sequencers work with VST on it's own way, differently. What is all that null tests? Just a simple WAV-tracks without any VST on slots rendered to one stereo WAV. Off course - there will be no difference. But i do not sure that they are correct tests.

Bla bla bla.... So, my opinion - all VST and VSTi sounds different in sequencers.))

i'm sorry to inform you, but your opinion is wrong. it is true that hosts may treat plugins differently, but it never alters their sound in any way.

null tests do not only consist of summing WAV files, but you have to understand that not all VST plugins are valid for null testing. For example, if you use a Kontakt instrument, chances are it's got round-robin or otherwise randomized samples for each note, so you might not be able to null it. therefore, to do a proper null test you absolutely must exclude every bit of uncertainty and randomization out of the equation so that the test is reliable, reproducible and with predictable outcome.

it's OK to be wrong, even if you're experienced. John Vestman is an experienced mastering engineer, yet he holds a firm belief that different hard drives sound different, and it's better to use internal hard drives than to use firewire ones. it happens, we're not perfect. therefore i invite you to create a simple project with samples and VST's and whatnot. we will find out the truth ourselves.