D
Deleted member 17960
Guest
I started a Tidal trial on mobile a few weeks ago and was impressed with the (ostencibly) more enjoyable sound than that of Spotify. After numerous listens between the services and on different devices, I set out to understand why Spotify and Tidal sound different.
The following comparisons are from "Killa" by Cherish, matched horizontally sample-for-sample. Volume is matched by RMS to -16.86 dB with the Normalize effect in Audacity in 32-bit space. The tracks all end at the 2:04 mark of the song. The actual captures were done by the following methods.
Ouch. That picture looks like Tidal and YouTube are range-compressed. I've been taught that range compression is a bad thing if it comes out looking like that. Although pictures can be deceiving, the whole tracks match those snippets closely. The audio segment can be downloaded at https://files.catbox.moe/ie76x4.wav
Here are the "plot spectrums" generated by Audacity for each track from 0:00 to 2:04. From left to right: Spotify web, Spotify desktop, Spotify mobile, Tidal web, Tidal desktop, Tidal mobile, YouTube web, YouTube mobile.
If you open the pictures in separate tabs and tab back and forth, it becomes evident that Tidal desktop nearly matches YouTube web, while Tidal web nearly matches Tidal mobile and YouTube mobile. None of the Spotify sources appear to match anything. The frequency axis at the bottom of the plot does not change, despite its labels moving around.
For a second audio comparison, I put together a sixty second segment from 0:30 to 1:30 that seamlessly rotates between sources on each 0:10 mark. The order is Spotify desktop, Spotify mobile, Tidal desktop, Tidal mobile, YouTube web, YouTube mobile. The segment can be downloaded at https://files.catbox.moe/s7wf8p.wav. To me, the differences between sources are almost unnoticeable in this one.
Ultimately, I hope this data is interesting, and that some of this forum's members understand the differences better.
The following comparisons are from "Killa" by Cherish, matched horizontally sample-for-sample. Volume is matched by RMS to -16.86 dB with the Normalize effect in Audacity in 32-bit space. The tracks all end at the 2:04 mark of the song. The actual captures were done by the following methods.
- Web players: PulseAudio capture by ffmpeg at 44100 and pcm_s16le (wav).
- Desktop apps: PulseAudio capture by ffmpeg at 44100 and pcm_s16le (wav). The Tidal app is inside a VirtualBox Windows guest; I'm not sure if that affects anything.
- Mobile apps: iPhone iOS 14 with the built-in screen video capture (implying recompression to AAC 128 kbits/s) and copied by ffmpeg into an M4A container.
- Spotify: 320 kbits Vorbis ("Very high").
- Tidal: 320 kbits AAC ("High").
- YouTube: 720p. It's not clear if this gives 128 kbits AAC like it used to, or some kind of recompressed audio.
Ouch. That picture looks like Tidal and YouTube are range-compressed. I've been taught that range compression is a bad thing if it comes out looking like that. Although pictures can be deceiving, the whole tracks match those snippets closely. The audio segment can be downloaded at https://files.catbox.moe/ie76x4.wav
Here are the "plot spectrums" generated by Audacity for each track from 0:00 to 2:04. From left to right: Spotify web, Spotify desktop, Spotify mobile, Tidal web, Tidal desktop, Tidal mobile, YouTube web, YouTube mobile.
If you open the pictures in separate tabs and tab back and forth, it becomes evident that Tidal desktop nearly matches YouTube web, while Tidal web nearly matches Tidal mobile and YouTube mobile. None of the Spotify sources appear to match anything. The frequency axis at the bottom of the plot does not change, despite its labels moving around.
For a second audio comparison, I put together a sixty second segment from 0:30 to 1:30 that seamlessly rotates between sources on each 0:10 mark. The order is Spotify desktop, Spotify mobile, Tidal desktop, Tidal mobile, YouTube web, YouTube mobile. The segment can be downloaded at https://files.catbox.moe/s7wf8p.wav. To me, the differences between sources are almost unnoticeable in this one.
Ultimately, I hope this data is interesting, and that some of this forum's members understand the differences better.
Last edited by a moderator: