TIDAL upgrade their loudness normalization – and enable it by default

Hi @brian

Just read this:

How is Roon’s TIDAL integration setup, with regards to this loudness normalisation?


1 Like

TIDAL publishes one volume normalization number via their API. This article is announcing that they changed the meaning/computation of that number from being a “track” value to an “album” value. Since they have rolled it out, Roon is now using the new number.

In general: Roon has three modes–album,track,auto. For TIDAL these always did the same thing since we didn’t have separate album/track values to work with. That’s still true after TIDAL’s change, but now the behavior is like “album” not like “track” because they changed the values.

Otherwise, our volume normalization implementation/approach is exactly like what is described in that article. I had a conversation with Eelco Grimm a little over a year ago, and we used the same techniques he recommends in the MLA resources. This has been in place since 1.3 was released in February.


Thanks Brian.

But if I have all volume levelling turned OFF in Roon, is there still this TIDAL ‘loudness normalization’ happening in the background?

This article says it’s now enabled by default. Does that only apply to TIDAL’s own desktop and mobile applications, or also API’s like Roon uses?

Their defaults changes only relate to their apps. They are not pre-processing the audio that is being sent to us–we receive the original file and the normalization numbers and it’s up to us to decide what to do with them. They have no power to change our defaults. As always, signal path will tell you if a gain adjustment is being applied.


Brilliant stuff. As always, many thanks.