People already did this. Here, for example: https://www.youtube.com/watch?v=FGrFIb9nxhg
FL Studio, Pro Tools, Ableton Live, Logic. All sound the same, since the null test proves it.

 

Like they say all daws sound the same but ONLY if your files are recorded at the same sample rate and bit depth that you're going to export to, if they aren't the daw is going to use their own algorithm for conversion causing aliasing in some cases, Cubase and Ableton have the best ones right now, in that regard Cubase 13 is better than 5 since it doesn't introduce aliasing, you can check that here

https://src.infinitewave.ca

 

Let's see the spectrograms

 

I don't remember whether I answered.
Cubase 5 was 32 bit float as I remember correctly, but since circa 2019 or so it became 64 bit float.

What the difference may be among/between DAWs:
- 32 or 64 bit float
- pan laws
- PDC compensation (plugins may work different in diferrent DAWs, different compensation algos, ms)
- sample accuracy
- fade-in, fade-out modes
- dithering mode while bit reduction (POW-R, UV-22HR, TPDF modification by voxengo)
- there were tests of automation etc, some are clicky, some noisier, some cleaner (but is toooo looooow)..
- Different SRC quality (aliasing, imaging, thd, imd, noise, filter sharpness, phase lin vs min), so there are not so much where used SoX algo, r8brain by voxengo etc. Some are worse or too bad. Standalone apps are better or some editors and DAWs, built-in ones
- other few details..
Summary, it is all about very small nuances mostly.

Summing is same in digital DAWs vs analog mixers or summing gear, except saturation, noise (Dan Worrall's video about this, nulling etc)

 

The digital data sent from DAWs is identical, but what we ultimately hear may differ. It is crucial to consider coupling DAW data flow with the later stages of audio processing, specifically with Audio APIs such as DirectSound, WASAPI, ASIO, and taking into consideration Exclusive Mode.
Exclusive mode offers Push/Pull options: Push mode continuously delivers data from the DAW, whereas pull mode requests data from the interface when needed. Pull mode generally provides slightly lower latency, while push mode might be more reliable for certain setups.
Then there's the DAC, with its specific requirements - DAC Driver Interface with Operating System: The driver serves as a bridge between the DAC hardware and the operating system, and compatibility issues may arise, affecting audio performance or stability.
These factors influence how the DAW interacts with the audio hardware, impacting the signal's journey from output to analog stage. As a result, each DAW, without being at fault, can produce a slightly different sound. I have never compared DAWS, but I never did encounter two digital audio players that sound the same.

 

Several things come into play before the main question can be answered:

• What O/S are you using? 32bit or 64bit? If the latter, v13 will be better. If Win 7 and it's not 64bit forget it..it is noticeable... you have a 4Gb RAM limitation with 32bit. These days that's bordering on a waste of time.
• Sample rates function faster and better with latency in later versions and in 64bit - You won't get v5 to run anything above 96Khz in fact, you may not get that depending on your hardware or O/S version.
• RAM limitations come into play
• CPU speed comes into play
• The speed of whether SSD or HDD also matters...
• You get much better stock plugins in v13 which again leads to RAM size again if you use a lot of plugins and Vsti's
• Multiple track simultaneous MIDI editing in a single window and more... in v13..go to Steinberg's new features on the web.

There's more to take into consideration, the above are possibly the main ones..

 

Last edited by a moderator: Jan 26, 2024

Choose the same driver and they will sound the same.

 

Best if you upload your projects and renders so the differences you say you hear can be retraced objectively.

 

My daw sound better than yours

 

- Ableton sounds edgy
- Studio One sound cold as ice
- Reaper sounds phat
- Cubase sounds perfect

Bye.

 

I believe there might be a misunderstanding. What I meant is that the way Digital Audio Workstations (DAWs) output is programmed to interact with drivers and APIs can vary, such as in CPU load, number of exceptions, etc. This slight difference in the way of coupling might result in variations in the content of the final digital package that reaches the DAC.

 

Engine and binary are not dependent.
x64 ozone is 32 bit float audio
x64 fabfilter pro-q is 32 bit float audio
x86 (32 bit) and x64 DMG Equilibrium are both 64 bit float audio
x64 kirchhoff eq is either 64 bit float or 117 bit float audio, depending in what phase mode is used
x86 (32 bit) or x64 psp masterQ2 is 80 bit extended float internally audio

 

ASIO eliminates this, does it not? It was designed to interact directly with the interface.

 

Cool Edit Pro sound like hot spicy chicken wings
Ableton sounds like a briefcase full of money (only if you use AT LEAST 10 third-party M4L devices)
FL Studio sounds like John Travolta's wife's armpit hair making tiny scruffle noises when she walks

prove me wrong

 

BS. Either is a plugin delay compensation or not. There is no "better" or worse. Everything over 32bit float gives you dynamic range beyond the silence between our galaxy and Andromeda (0, nada, nothing, zilch) and an explosion of hydrogen-bomb in 1 meter, in numbers: more than 1.500 dB. There is no cleaner or not so clean. There is absolute perfection beyond any discussion.

 

I used C5 in the day and it was a 32bit system that had very little in the way of headroom for much of anything unless you were working in 32float. At the time though it was more limitations of the average available hardware that could thwart large productions done on generic PC (or apple) platforms. These days it seems everyone is sporting 8+ core processors, 64+ GB ram, super fast Nvme and SSD's, etc... Working in 32 float on C5 at anything higher than 44khz was a hardware ass kicker. Now, 96khz+ 32/64bit float is commonplace. When pressed hard C5 would come apart at the seams quicker requiring higher and higher buffer values to keep it in line. This would be expected of a 32bit system, but when mixing large amounts of tracks you just had to get used to it...The audio hardware didn't really matter much as long as it was ASIO compatible and was designed well. I was running a RME hammerfall 9652 which made things about as easy hardware/driver wise as they could get. This was at a time when Soundblaster type cards were the generic goto audio "interfaces". You had others like the turtle beach, MOTU's (considered high end at the time), midi-man, and a few other boutique offerings that by today's standards were completely subpar with regards to analog noise figures and their ability to deal with internal computer switching noise. The hammerfall 9652's were in with the best of the best as far as noise abatement and sound quality. They were as quiet as church-mice comparatively.

 

Last edited: Jan 27, 2024

The export differs from the playback because of coupling? Which DAW?

 

Cakewalk is the sound you want and can't figure out how that guy is getting it...

 

I used to think people discussing this topic and pointing to null tests were talking about various complexities in each DAW. Personally, I know a project I do in Logic will not turn out exactly the same as one I would end up with had I used a different DAW. When it dawned on me that the real point of the discussion for these people, was that a single wav file playback in each DAW is the same and therefore confirms that "my free DAW sounds the same as your $1000 DAW" imagine my surprise. Oh hell no.

 

No, it's about the same processing with the same plug-ins and of course summing.