#Bitwig Levels

1 messages · Page 1 of 1 (latest)

oblique temple
#

Bitwig doesn't clip automatically at 0 dB, that's basically a warning that the output may get clipped by your interface.

oblique temple
#

Maybe the mastering is a bit too hot?

oblique temple
#

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?

reef temple
#

ist with all files like .mp3 .wav etc.

#

happens since I started with Bitwig 3

oblique temple
#

I am using the default track level of -10dB, no problem with that

reef temple
#

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.

oblique temple
#

using the default track level, Beyonce comes to -9.4, which is pretty safe

reef temple
#

it shouldn`t clip at 0

fathom igloo
#

seems like a bug to me. 0db should be 0db

sage sedge
#

Is the audio event in raw mode? Any of the stretch modes could be changing the peak

reef temple
#

Can you make a ticket?

fathom igloo
#

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
reef temple
#

I just wrote the support on the homepage a mail.

reef temple
#

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.

rough pewter
#

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?)

reef temple
#

every version. I tested mp3 and wav

#

project/soundcard at 48.000 samplerate.

rough pewter
#

I have a feeling this is SRC related, I'm going to run a test later

reef temple
#

happens on 48khz.

rough pewter
#

Weird. Wav over here is 0 if the wav is 0

reef temple
rough pewter
reef temple
#

please import a wav. at 44.1khz

#

and mp3

reef temple
#

ok, the problem is that bitwig doesnt convert 44.1khz files to your system samplerate (in my case 48khz).

reef temple
#

Just got a mail about it. "Just use 44.1 khz".. this is so unacceptable! I will stay away from Bitwig for now. Sad

livid plover
reef temple
#

But the Sample are not clipping in other DAWs. And in Bitwig its not only up to one db difference its up to 4db sometimes.

#

I think its not inter-sample peaks related.

#

If I convert the file in Cubase and load it into Bitwig its not clipping anymore.

rough pewter
#

Bitwig uses different SRC than Cubase

#

It's a shorter filter

#

Converting in RX will also avoid this issue

#

but I agree I think it would be awesome if Bitwig could add some SRC options

#

Ableton used to have terrible SRC that has cleared up in the past few versions