use of dB unit without suffix in Normalization preferences is confusing

Bug #1561131 reported by Be
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
New
Undecided
Unassigned

Bug Description

Under the "Target loudness" slider in the normalization preferences, the position of the slider is noted in terms of LUFS, with "(adjust by X dB)" after the LUFS. It seems that the dB measurement is in reference to -18 LUFS, but for a long time I have been confused in thinking that it was in reference to digital full scale and that ReplayGain would adjust my tracks by that many dB relative to how they are recorded. I did not understand that ReplayGain was making my tracks substantially quieter until I played with toggling ReplayGain on and off and realized I had to put the Target loudness slider to +6 dB (-12 LUFS) for tracks to reach the same levels on the level meters without ReplayGain applied. The use of "dB" in this unusual way is confusing. I'm not certain what the best way to make this less confusing would be. Perhaps simply removing the "(adjust by X dB)" text would help to make it clear that the Target loudness slider is only dealing with LUFS, not dBFS.

Revision history for this message
Be (be.ing) wrote :

The pending ReplayGain 2.0 PR solves the issue with having to turn the slider up to -12 LUFS, but the confusing use of "dB" remains.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

> It seems that the dB measurement is in reference to -18 LUFS

That is correct. -18 LUFS is the ReplayGain reference loudness.

We have added the dB value witch is basically an additional gain to the normalized -18 LUFS track.

In the 1.11 version, we had only the dB value. And it helps to compare the LUFS slider with the Initial Boost slider below and the
Replay Gain value in the library column.

A dB scale is the most common scale for gain and volume slider, and it should catch the user who are not familiar with LUFS. It has nothing to do with dBFS, which is a unit for peak sample measurement.

Revision history for this message
Be (be.ing) wrote :

I don't know of anything else that uses dB in reference to -18 LUFS, so I doubt I'm the only one who got confused and thought that the dB value is in reference to a more common reference for dB, such as 0 dBFS. I think removing the "(adjust by X dB)" and only show LUFS would be clearer.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

OK, I can live without ;-)

Revision history for this message
JosepMa (josepma) wrote :

@be: As noted, dB is a relative unit, which expresses the amount of change respect another value. As such 0dBFS expresses the amount of change, versus a predefined level named "Full Scale" (Max digital level, or unity level). This unit only has sense in a meter, not in a fader.

In this case, the slider for the replaygain is indicating a change of gain versus the default target loudness, and usually people require increasing the gain ( i.e. push it nearer to 0 ). Just remember that the usual precautions about mixing gains should be respected.

There is no standarized unit to describe this. It could have been named 0dBRgT ( Replaygain target).
As Daniel says, what has been done to 1.12/2.0 is to express this gain in a more reasonably unit (at least in recent years) which is using the LUFS unit. The expression in dBs helps to know where the 0 point is and should imply the meaning that it is a gain change.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

No one has confirmed that bug, close as won't fix?

Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8499

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.