"Assuming no clipping" is the biggest problem there, because the loudness wars resulted in a ton of very lossy clipping and similar artifacts. Arguably that sort of distortion became part of the expected sound, though, so just because it isn't reversible doesn't necessarily mean it is a problem.

In the open metadata world there is ReplayGain which analyzes music peaks and tries to create a negative gain to equalize the dynamic range to a standard volume at both the individual track and full album level.

Apple Music, Spotify, and others have proprietary but similar systems.

(As someone who deeply loves to shuffle an entire library, having a music player that supports ReplayGain has long been a personal requirement.)

▲

Melatonic 15 hours ago | parent [-]

ReplayGain sounds pretty cool. Does it pre analyse your library ?

	▲	nighthawk454 11 hours ago \| parent \| next [-]
		ReplayGain is nice - but note it doesn’t ’fix the compression’. Compression and dynamic range is about loud/quiet _within_ the track. ReplayGain just turns the volume up and down for the entire track, the point being so all your tracks play back at about the same level. It saves a preset on the volume knob for you essentially. If you remember making a playlist where one song is suddenly much louder than the last, and you’re riding the volume knob on every other song, you’ll see why this is nice!
	▲	WorldMaker 13 hours ago \| parent \| prev [-]
		Yeah, you run an analyzer on your library and it creates MP3 or Ogg Tags that the player. Often you can leave the rest of the file as it was originally, just the new metadata tags. On Windows I've always liked Foobar 2000 for its strong ReplayGain support, both automating the analyzing pass and respecting the metadata in the tags once saved. On Unix I was using Banshee for playback and automating analyzing with a pair of CLI tools I've forgotten the names of, one was MP3 specific and the other Ogg/FLAC-specific, as I recall.