Page 1 of 3

Loudness management

Posted: Sat Aug 24, 2019 12:13 pm
by Lunkhead
What would folks think about Song Fight joining the ranks of e.g. Apple Music and Spotify and publishing a guideline about loudness in submitted songs?

https://www.masteringthemix.com/blogs/l ... nd-youtube

More radically, maybe we could even explore doing some kind of loudness adjustment to the submitted songs to make for a smoother listening experience within a fight? I'm sure that would be extremely controversial though.

Re: Loudness management

Posted: Sat Aug 24, 2019 3:34 pm
by fluffy
Isn't it already hard enough getting people to submit things with the right filename and format, and which are actually songs with the current title? Fortunately ReplayGain exists and there's plenty of tools out there to tell you what the LUFS is (heck, LAME does it by default, and a lot of mp3 encoders are based on LAME) so publishing a guideline is at least worth doing.

Regarding automatic normalization: Once upon a time I wrote a thing to stabilize volume and when word got out that I listened to all my music through it — especially Song Fight! — there was much wailing and gnashing of teeth because I was "destroying the musicians' intent." And when blue was looking into using it as a filter for the ongoing Song Fight! icecast stream, oh boy did people have a lot to say about that.

Hopefully the community has calmed down about that since then, because I think it's a good idea.

Maybe before the fight goes live the files could all be run through a (non-destructive) ReplayGain normalizer to target, say, -12dB.

Re: Loudness management

Posted: Sat Aug 24, 2019 10:25 pm
by grumpymike
You can do this non-destructively and automatically by providing a player that abides loudness metadata (Nur Ein site now does this - LUFS calculations are server-side and the client scales the volume slider) or by adding the ReplayGain and/or Apple tags to the MP3 files - which requires users to have capable players. They both have pros/cons but there is nothing to object to in either because they aren’t destructive. And they’re not mutually exclusive.

Re: Loudness management

Posted: Sun Aug 25, 2019 8:53 am
by owl
I don't think enforcing a loudness setting would be good unless there's something on the back end making it happen automagically, because it's a barrier to entry that I think would eliminate a lot of cool songs by non-tech-savvy musicians.

BUT I personally would like at least having a guideline to work to and help figuring out how to export my files at the right levels, because despite putting ozone and another LUFS meter in my chain on the master track (ps thanks to Chumpy and everyone else who chimed in on that Nur Ein Round Zero thread about measuring/fixing levels), I never seem to be able to export things at the right levels the "correct" way, for whatever reason--I have to futz around with a couple of different exports usually and the LUFS meter ends up saying it's too loud, but my ears end up saying it's fine next to reference tracks.

Re: Loudness management

Posted: Mon Aug 26, 2019 6:57 am
by Pigfarmer Jr
So I'm fairly inconsistent, but I try to render at -14 LUFS (because I read that's spotify etc., playback level.) Having a guideline that we should aim for is a great idea. Having a playback mechanism that levels out all the songs is a great idea (especially since we can all just download the songs and listen however we want, anyway.) Enforcing a level would be impossible (unless you disqualify entries) and I personally think isn't a good idea. That being said, I've not been bothered by volume differences enough to go to the trouble of listening through any system that "normalizes" playback. I just use the volume knob if/when needed.

Re: Loudness management

Posted: Mon Aug 26, 2019 8:43 am
by ujnhunter
Yeah, I wouldn't be a fan of Song Fight! altering the submitted songs that people download... If you wanted to make a Song Fight! "player" that did it the way that @grumpymike says that the Nur Ein player does, I wouldn't object to that... but altering a file that someone submitted wouldn't be cool in my book, and I, just like Stuntman Mike (no relation to @grumpymike), actually have a book.

P.S. How many commas is too many commas? Maybe I should just stick with my horrible... habit.

Re: Loudness management

Posted: Mon Aug 26, 2019 9:16 am
by fluffy
I think the only alteration of the actual files that anyone's suggesting is adding a ReplayGain tag, which doesn't alter the audio data at all. It just tells the player where to set the volume knob for the song.

When I was using the volume stabilizer it was only as an audio filter that happened after my player (and it only turns up the volume on things that are too quiet and is careful to never cause clipping), and people got the misconception I was, like, changing the files or something. There's plenty of ways of dealing with automatic volume management that don't involve modifying the actual sound data, and remember that these things are all being designed and implemented by other musicians who understand the importance of protecting the recordings themselves.

Re: Loudness management

Posted: Tue Aug 27, 2019 8:55 am
by Rabid Garfunkel
Could this be an addition to the jukebox's playback function, leaving the front page fight links as submitted?

Oh, and hey all. Been a while, yo.

Re: Loudness management

Posted: Tue Aug 27, 2019 10:08 am
by jast
I don't mind an official recommendation, though I doubt they'll make much of a difference.
I don't mind an optional filter in e.g. the jukebox, either.

I wouldn't be happy with any automatic mangling of audio - for one thing it can destroy the intent of the mix, for another it makes it hard to review the mix if you don't know what's due to the original submission and what's due to filtering. I prefer listening to the originals.

Finally, I don't really think ReplayGain tags are really worth the effort here. As I understand it, ReplayGain calculates the recommended adjustment based on RMS normalization and an extra 14 dB of headroom. However, this fails if a track's dynamics exceed 14 dB above the RMS mean - the adjustment will either have to include more headroom for this track, or cause clipping. So, we either get different loudness in different tracks, or artifacts.

This might work if all of the tracks actually are mastered to similar specifications, but in practice they won't be - and it's unrealistic to ask this of participants who aren't really that much into the engineering side of things.

Re: Loudness management

Posted: Tue Aug 27, 2019 11:09 am
by grumpymike
jast wrote:
Tue Aug 27, 2019 10:08 am
As I understand it, ReplayGain calculates ...
While it might not be in the spirit of the ReplayGain standard, you can calculate the value in REPLAYGAIN_TRACK_GAIN however you like. The same is true for iTunNORM. So, you could calculate and adjust the loudness using LUFS in order to be more accurate in terms of perceived loudness. Regardless, you would still need a target, which likely entails clipping. Not to re-litigate the entire concept of standardizing loudness, but the reality is people expect songs to be playable adjacent to other songs.

The larger problem is that few audio players support these tags.

Re: Loudness management

Posted: Tue Aug 27, 2019 11:13 am
by fluffy
Or if they do support the tags it's a very all-or-nothing thing, and is often shoddily-done (like iTunes).

I wonder how many entries in the archive already have ReplayGain tags without anyone even realizing it.

Re: Loudness management

Posted: Tue Aug 27, 2019 11:34 am
by Lunkhead
I personally was not proposing any modification of the audio in the files, just adding metadata. So could we maybe please stop wasting time arguing about something that wasn't mooted in the first place? :P

Re: Loudness management

Posted: Tue Aug 27, 2019 11:45 am
by jb
jast wrote:
Tue Aug 27, 2019 10:08 am
I wouldn't be happy with any automatic mangling of audio - for one thing it can destroy the intent of the mix,
It's not compression or EQ, it's gain. It doesn't seem like normalizing to a particular LUFS number would destroy the intent of the mix on Song Fight any more than it does on Spotify.

I can see your point for any production that is intentionally trying to screw with the listener, experimenting with extreme quietness or extreme loudness, or farcical submissions like a Lightning Ear Fart. But for %99.999 of submissions this seems like it would at worst do no harm and at best help them be heard in the best context possible.
for another it makes it hard to review the mix if you don't know what's due to the original submission and what's due to filtering. I prefer listening to the originals.
If someone suggested automatically compressing or EQ'ing the entries, I think I would probably agree with you. But this is just about gain, so given an option to listen to a LUFS-normalized playlist or the original submissions, I'd choose the normalized playlist to make it easier for me to listen to the songs confidently without having to adjust my volume controls for each song.

We make fun of this idea, but this really is Song Fight, not Production Fight. So in my opinion, someone's lack of engineering expertise should not disqualify them from winning a fight. It's a fact that humans confuse loudness for fidelity, so for submissions that are too quiet increasing the LUFS level via a normalization process would be leveling the playing field to some extent. And for submissions that are too loud, it can prevent the listener from skipping the song entirely just because it came on too loudly after the previous song.

I do think this probably wouldn't work well unless the processing happened on the server-- I think player metadata and implementation might be too much of a crapshoot given the various methods people use to listen to Song Fight (the variety of which always surprises me).

Just my $.02

JB

Re: Loudness management

Posted: Tue Aug 27, 2019 12:41 pm
by grumpymike
Lunkhead wrote:
Tue Aug 27, 2019 11:34 am
I personally was not proposing any modification of the audio in the files, just adding metadata. So could we maybe please stop wasting time arguing about something that wasn't mooted in the first place? :P
If you just want to post guidelines, do it. I don't think anyone will object.

Re: Loudness management

Posted: Tue Aug 27, 2019 5:50 pm
by fluffy
jb wrote:
Tue Aug 27, 2019 11:45 am
I can see your point for any production that is intentionally trying to screw with the listener, experimenting with extreme quietness or extreme loudness, or farcical submissions like a Lightning Ear Fart. But for %99.999 of submissions this seems like it would at worst do no harm and at best help them be heard in the best context possible.
Also keep in mind that at least for ReplayGain it's only choosing one relative gain offset for the entire track, meaning that if someone's made a purposefully very quiet VERY LOUD!!!! mix (for example, Octothorpe's "Crinkle Binkle") this wouldn't do anything to affect that.

(Also tracks like that tend to be very listener-hostile and not really all that funny)

Re: Loudness management

Posted: Tue Aug 27, 2019 10:52 pm
by Lunkhead
Spotify's FAQs on the subject for reference:

https://artists.spotify.com/faq/mastering-and-loudness

Turns out at playback time in mobile apps they apply a limiter when boosting softer tracks:
Positive gain is applied to softer masters so that the loudness level is at ca - 14 dB LUFS. A limiter is also applied, set to engage at -1 dB (sample values), with a 5 ms attack time and a 100 ms decay time. This will prevent any distortion or clipping from soft but dynamic tracks.

Re: Loudness management

Posted: Tue Aug 27, 2019 11:02 pm
by fluffy
Previously I was determining my LUFS by just looking at what the ReplayGain output said from my mp3 encoding, which seems to not be a great way of doing it. So just now I found a free VST/AU that looks like it'll give you a better overview of what's happening dynamics-wise.

Re: Loudness management

Posted: Wed Aug 28, 2019 2:04 am
by jast
Yeah, I was using Youlean's for quite some time, too. I've switched to a DAW that has built-in visualization of integrated loudness, though, so that makes it unnecessary.

Re: Loudness management

Posted: Wed Aug 28, 2019 2:39 am
by fluffy
I’m surprised Apple hasn’t added that to logic, frankly.

Re: Loudness management

Posted: Wed Aug 28, 2019 4:45 am
by jast
Yeah, same for REAPER... anyway, back to the topic. :)

I think that normalizing loudness is a particularly tricky topic for submissions that have a really rough mix - e.g. the drums kick in late and are way overbearing, stuff like that. Inexperience can easily make for fluctuations of 6 dB, which would mean a departure of maybe 3 dB in the mean - so, part of the song is 3 dB louder than the rest, and the rest is 3 dB quieter. The same can happen for a song with two distinct parts - in a more dynamic mix, 6 dB of difference are not at all out of the question (and not as extreme as the examples brought up earlier). There's really no way to stop this without going into audio-level compression (which we seem to agree is not a good idea).

So, we're likely going to have 3-4 dB variation in fights even with normalization tags provided - and in general I think most songs don't stray that much further - this is pretty much mainly about songs that are mastered way too hot (at least in my opinion). At that point I have to wonder: is this enough of a pain point to justify setting up extra processing infrastructure, or add more manual steps to publishing each fight?

(For me personally it's not...)

Re: Loudness management

Posted: Wed Aug 28, 2019 5:13 am
by Pigfarmer Jr
To further the quote from Lunkhead:
Negative gain is applied to louder masters so the loudness level is at ca - 14 dB LUFS. This process only decreases the volume in comparison to the master; no additional distortion occurs.
Positive gain is applied to softer masters so that the loudness level is at ca - 14 dB LUFS. A limiter is also applied, set to engage at -1 dB (sample values), with a 5 ms attack time and a 100 ms decay time. This will prevent any distortion or clipping from soft but dynamic tracks.
I've always erred on the side of softer, ie - 14.2 etc., but according to this, it'd be better to be at -13.8 so that no limiting is put on the track. Although, I doubt I could hear the difference. It'd be interesting to do a listening test, but not worth the trouble.

Also, we have the option of setting up something we could do individually to help with the listening experience. If someone has a player/normalization process that each of us could individually set up/use, then it's an option I'd probably choose to use. For instance, if the jukebox was set up in such a way that it had the option or was standard with normalization then I'd use that even more than I already do. (I'd really like it to be optional to hear the differences, but I'm not sure that's necessary.)

Re: Loudness management

Posted: Wed Aug 28, 2019 8:03 am
by jb
Pigfarmer Jr wrote:
Wed Aug 28, 2019 5:13 am
Also, we have the option of setting up something we could do individually to help with the listening experience. If someone has a player/normalization process that each of us could individually set up/use, then it's an option I'd probably choose to use. For instance, if the jukebox was set up in such a way that it had the option or was standard with normalization then I'd use that even more than I already do. (I'd really like it to be optional to hear the differences, but I'm not sure that's necessary.)
Kind of an "advanced mode" sort of thing.

Personally I lean towards the "how can we make all submitted productions as good as possible considering the variety of engineering expertise"-- so for example "Hey LANDR want to partner up and give any songfight who wants it the option to pass their submission through your maxifier gizmo?" An opt-in auto-master for those who are either lazy or inexperienced.

Because 15-16 Puzzle. Because 2002 JBB.

But that's just me.

J