This has been already commented here. There is no platform culprit, neither NVIDIA, Android or TIDAL.
The reason for this is the Dolby implementation of the parameter “DialNorm” in Dolby Atmos that was supposed to be to automatic adjustment of the Master Volume Level reproduction for content dealing with “Dialogs”, i.e., TV, films and commercials.
This parameter is ‘used’ or ‘misussed’ by the audio engineer mixing or mastering the final Dolby Atmos track. This parameter can be found in the Dolby Atmos Tidal tracks with some random and not coherent values, among different tracks.
Many claim that this parameter should not be used for MUSIC.
Once the final Master Dolby Atmos track goes to the Platform (TIDAL in this case) nothing can be done.
The players just ‘obey’ that Dolby Atmos parameter ‘DialNorm’ as they should.
Some say that it can be overridden by some settings in the AVR (Denon disabling dynamic volume) but it does not work for me.
The Conclusion and Recommendation IS....…. Be prepared when the Atmos track reaches the end, to have the remote in hand with the finger over the ‘reduce volume’ button.
For more information about the ‘DialNorm’ disaster, read through this article:
https://connectedmag.com.au/dialling-down-dialnorm/
) sat in the vaults.. though i'll bet the proverbial nobody at the label knows or even cares about its existence 
back to our regular programming 
just revisiting some ol' pals 
