album gain normalization

Bug #1752654 reported by Be
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Wishlist
Unassigned

Bug Description

Currently Mixxx only calculates gain normalization on a per track basis to normalize the perceived loudness to a specified target loudness. This can reduce intentional differences between dynamics among tracks in an album. It would be nice if Mixxx could also normalize the perceived loudness between albums while preserving the dynamic range within albums. A setting to toggle between track and album normalization may be added to the AutoDJ preferences or perhaps a button in the AutoDJ controls in the main window.

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

Please explain your use case.

This means that a track recorded with low volume will still played at low volume.
If there is a loud track in the album the low track will be played even lower.

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

The use case is playing whole albums with AutoDJ and preserving the relative levels of tracks within each album.

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

Thinking of it again, the album replay gain is probably the one that is the "intended" loudness of a track.
For example, it does not make sense to play a noise floor intro at track replay gain. That would be much to loud.

How to you like to obtain the album gain?
I bet, there are only a minority of tracks, with this set?

I think an option: "Use Album gain if available" makes most sense.

An option to calculate album gain could be also usefull.

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Be (be.ing) wrote :

I would like if Mixxx could calculate this along with the track gain. The analyzer could be toggled by a preference option so users who would not use album gain would not need to spend the CPU time analyzing it. I am not sure how to implement this because Mixxx analyzes one track at a time.

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

For album gain, the we hole album needs to be analyzed together, somehow as a single track.
For this to work, we need to fetch all tracks from an album in one analysis.
It will get a bad result of a single track is missing or the album tracks are ripped from different recordings.

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

Perhaps we could cache a running average per album in the database? I'm not sure how album gain normalization is typically calculated, so that might not be feasible.

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

Mixxx has already global accessible control objects for it: [Recording], "status" with RECORD_OFF (0.0) RECORD_READY (1.0) RECORD_ON (2.0) and RECORD_SPLIT_CONTINUE (3.0) and [Recording], "toggle_recording".
These controls might be used from a PlugIn, to enforce the streaming user conditions. If [Recording], "status" is different from 0.0 the Plug-In may stop either the stream or the recording via [Recording], "toggle_recording"

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

Ups, #7 went to the wrong bug.

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/9162

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.