Simon when I ran a 30 day trial when Qobuz came to the US against TIDAL, I was using the Qobuz Hi-Res files and they sounded much better than the CD quality files available on TIDAL. The reason to moving to Qobuz was the music did sound much better.
Perhaps some that use MQA there may be a difference. All I know is that the $14.99 monthly charge for Qobuz with HiRes vs the $19.99 monthly charge for TIDAL, CD quality, was a no brainer. My System, My Room, My Ears…
Your right, I interpreted the ‘all things being equal’ as not being possible because of the different pricing and MQA vs HiRes files. If just using CD quality they should be the same. I should not read and respond after midnight.
Having both services gave me the time to think and listen things over. It’s going to be Qobuz only. Often Qobuz has a better catalogue than Tidal. More albums and better resolutions.
When it comes to comparing Tidal standard CD SQ vs Qobuz standard CD SQ there is imho often a difference, I prefer the sound of Qobuz. On Tidal the music is often louder. Perhaps the extra head room gives space to the more pleasant sound? Or is it Hifi placebo again ?
Both services probably have a normalize / replaygain setting, this adjusts the playback volume to a standard level. It’s possible that on one service this setting is enabled but not on the other, this is something you could check to be sure.
I very much doubt that… to do that would involve creating a new master effectively… and that would run into copyright issues… also gapless replay would jump and interfere with album playback… finally bit wise normalisation can introduce reconstruction errors…
I have no evidence of that, in fact I have clear evidence of the contrary as masters from Tidal and Qobuz have quite difference loudness settings dependent on source master… in fact so much so when I compile playlists I sometimes introduce a degree of level optimisation. (Note not normalisation)
Different distribution masters, especially on older tracks or compilations can have quite different loudness settings.
I think you’ll find that that cloud streamers use CDN providers delivering http media deliveries… these are global cloud media asset service providers like providing images, videos, bit maps etc… I very much doubt that they could get involved with on the fly media asset manipulation…
I am pretty confident the cloud stream providers stream what ever assets the music distributors provide them.
Yes, you can provide a degree of loudness optimisation in Roon as an option, when creating playlists etc… it’s not normalisation however… Roon can use the average loudness value of a media asset if provided… or default to a set value. Ron’s loudness optimisation algorithm is based on EBU R128 specification… but is only applied once the media is upsampled to 64 bit floating point to minimise quantisation processing errors.
But I only use occasionally for playlists because bit wise manipulation here (ie changing sample values) can lower the audio quality for critical listening on some media… but for me playlists are not usually for immersive listening.
Hi, replay gain normalisation (loudness normalisation) is not the same as sample normalisation… they are quite distinct approaches… the former is based on LUFS, the latter on absolutes… and based on sample absolute values.
Well your post prompted me to look into it further… EBU 128 S2 (supplement 2) is specifically targeted at streaming media provides and players, and the recommendation for broadcasters and cloud stream providers following EBU R128 (and Tidal is mentioned as an example) that use their own interfaces is that loudness is applied on their clients either by default or on demand rather than at source and be controlled by using meta data.
So in this example using Roon to optionally apply loudness normalisation if the user requires for content fits this model. This is also the approach used by Tidal’s own player. With Naim natively there is no option to use this normalisation meta data.
Or if no loudness normalisation is required, or the player (device) can’t process the loudness normalisation meta data, the source is not manipulated and the meta data ignored