#Bitwig Levels
1 messages · Page 1 of 1 (latest)
Maybe the mastering is a bit too hot?
I just looked at an official FLAC from Beyoncé's Renaissance - "Thique", to find some nice mastering. If I set the track level to 0dB, the playback is also +0.6 dB over. That's a bug, I guess.
Do you get the same issue with the default track level of -10dB?
I am using the default track level of -10dB, no problem with that
Sometimes even when you bounce files limited at 0 it will be clipping right after that.
I imported many mastered Dance Tracks and they all clip over 0db.
I have no idea why.
using the default track level, Beyonce comes to -9.4, which is pretty safe
it shouldn`t clip at 0
seems like a bug to me. 0db should be 0db
Is the audio event in raw mode? Any of the stretch modes could be changing the peak
Can you make a ticket?
Now that i focused on the topic of Bitwigs peak levels:
- you cant see the peak levels in the normal mixer. So when mixing an arrangement with one monitor, you are forced to switch the whole view to the MIX view with big meters in order to see an overview of the peak hold values.
- the colorization in general is unconventional/misleading, or am i wrong? I mean i don’t know many other editors, where the VU meter gets deep red where there’s still so much headspace
I just wrote the support on the homepage a mail.
they are investigating. I send them several videos about the problem.
funfact: a bounce/render of the mastered track is even more clipping on import.
What version? I don't have this issue at all
I'm on 5.0.9
Correction, appears with an MP3 but the flac file I tested was fine
Definitely odd, they aren't displaying true peak because a TP +.7 flac file shows under 0 dBFS but an mp3 that's definitely PCM limited to 0 shows +.7 (which is roughly the TP level, but then why did the FLAC file meter under 0?)
Does this still happen if the track being loaded is also 48khz or only when 44.1?
I have a feeling this is SRC related, I'm going to run a test later
happens on 48khz.
Weird. Wav over here is 0 if the wav is 0
with 48khz?
Yeah, running at 48khz project sample rate and importing a wav at 48
ok, the problem is that bitwig doesnt convert 44.1khz files to your system samplerate (in my case 48khz).
Just got a mail about it. "Just use 44.1 khz".. this is so unacceptable! I will stay away from Bitwig for now. Sad
If this is due to sample rate conversion then this is definitely also related to inter-sample peaks - songs mastered to 0db sometimes have inter-sample peaks up to nearly 1db. Meaning this issue 1) affects probably any daw, and 2) your speakers are being pushed past 0db anyway even without the SRC.