Apologies for the catchy subject title.
I am seeing behaviors in Studio One 2 that contradicts the idea that all native DAWs sound the same.
This was confirmed using Bitter and a 44.1/16 audio file.
**Testing in SONAR
1. Create new 44.1 project
2. Load above audio file
3. Insert Bitter in master bus and playback
-> Bitter indicates 16 bits
4. Reduce gain of file
-> Bitter indicates 32 bits
... so far, this is working as I would expect.
**Testing in Studio One 2
(Options for dithering and 64f processing are both disabled)
1. Create new song at 44.1/16
2. Load above audio file
3. Insert Bitter in master bus and playback
-> Bitter indicates 32 bits
4. Reduce gain of file
-> Bitter indicates 32 bits "wide" cluster of bits, but shifts down to 64 bits.
----------------
Can anyone explain what is going on inside SO2?
Studio One 2 sounding different from other DAWs?
-
- KVRAF
- 6419 posts since 22 Jan, 2005 from Sweden
Among things that may affect how daws sound are pan laws - whether each channel is compensated etc.
So panning center may reduce overall level so that when panning energy is constant, just distributed differently in stereo field.
So having all tracks to 0dB fader level will make them sound different in one daw compared to another - if any tracks are panned.
Pan laws are usually selectable as a preference setting,
0dB=no compensation when panned, -3dB=center is attentuated 3db.
And there might be curves selectable as well, how compensation is done.
So panning center may reduce overall level so that when panning energy is constant, just distributed differently in stereo field.
So having all tracks to 0dB fader level will make them sound different in one daw compared to another - if any tracks are panned.
Pan laws are usually selectable as a preference setting,
0dB=no compensation when panned, -3dB=center is attentuated 3db.
And there might be curves selectable as well, how compensation is done.
-
- KVRer
- Topic Starter
- 17 posts since 15 Jan, 2008
lfm,
I know about the different pan laws.
I have already pointed out in my original post, some kind of 64bit funkiness going on in the mix bus even with "64bit processing" option turned off. This is not conventional, and can possibly alter any signal passing through it even with faders set to null.
Would you please explain this?
I know about the different pan laws.
I have already pointed out in my original post, some kind of 64bit funkiness going on in the mix bus even with "64bit processing" option turned off. This is not conventional, and can possibly alter any signal passing through it even with faders set to null.
Would you please explain this?
-
- KVRAF
- 2063 posts since 14 Sep, 2004 from $HOME
I don't have S1 but I can confirm that my Cubase 6 works like Sonar.
But what do you exactly mean by
"Bitter indicates 32 bits "wide" cluster of bits, but shifts down to 64 bits."?
Do you have a screenshot maybe?
But what do you exactly mean by
"Bitter indicates 32 bits "wide" cluster of bits, but shifts down to 64 bits."?
Do you have a screenshot maybe?
-
- KVRer
- Topic Starter
- 17 posts since 15 Jan, 2008
Ok, just found the cause.. and apologies in advance for the hassle.
lfm had a point.
When loading a mono 44.1/16 file, SO2 reduces the level by roughly 3dB which broke the quantization even when panned center.
SONAR on the other hand copies the mono content to both channels, retaining the quantization.
lfm had a point.
When loading a mono 44.1/16 file, SO2 reduces the level by roughly 3dB which broke the quantization even when panned center.
SONAR on the other hand copies the mono content to both channels, retaining the quantization.
-
- KVRist
- 200 posts since 12 Aug, 2013 from LA
I haven't read what the others have posted, though some of their info may also be true.
I'm just posting now to say that the plugin Bitter has been known to show some funny stuff at times. Don't know why, but I've seen it not report the lowest 16 bits when slapped on various tracks and so on. I stopped using it and switched straight away to SSL's X-ISM when that one was being given away.
I'm just posting now to say that the plugin Bitter has been known to show some funny stuff at times. Don't know why, but I've seen it not report the lowest 16 bits when slapped on various tracks and so on. I stopped using it and switched straight away to SSL's X-ISM when that one was being given away.
