I’m not trained in anything useful but I had a similar experience. It was like upgrading from a 720 screen to a 4k screen.
I wholeheartedly disagree. I have more trained ears then most (worked in video production), but not by much, and when i got my AirPods Max, I thought they sounded awful at first. They were crunchy and dithered sounding in this weird way. I was gonna return them, but I did some testing, and discovered that I was hearing Spotify compression. I turned up the quality as high as it would go in the settings, and that made it a little bit better, but I could still hear it, and can to this day. I did some further testing by signing up for a tidal free trial, in addition to Apple Music. Listening in lossless was an entirely different experience, I could definitely tell the two apart blindly, without even specifically looking for sound quality. There were like 2 to 3 instruments in a given song that I wouldn’t be able to pick out in the lower quality audio, that I could easily pick out in the lossless audio. You have to have a pretty decent pair of headphones to be able to hear it, but some of the higher and consumer stuff can definitely hit that level, and when you do, it’s not something you have to go looking for, it sounds very obvious.
astray@lemm.ee 11 months ago
First@programming.dev 11 months ago
Do you realize AirPods Max/iPhone is capped at AAC/356 kbps over BT, and needs DAC -> ADC -> DAC to use a wired connection?
HexagonSun@sh.itjust.works 11 months ago
Yep, absolutely this.
You cannot listen to musically losslessly with AirPods Max, cabled or not.
From Apple’s own site: “The Lightning to 3.5 mm Audio Cable was designed to allow AirPods Max to connect to analog sources for listening to movies and music. AirPods Max can be connected to devices playing Lossless and Hi-Res Lossless recordings with exceptional audio quality. However, given the analog-to-digital conversion in the cable, the playback will not be completely lossless.”
If someone thinks AirPods Max sound amazing, they’re agreeing how good compressed audio can sound, whether they realise it or not.
pup_atlas@pawb.social 11 months ago
Yes! (Kinda) I’m not saying lossless music is the end all be all, and honestly in normal life I prefer non-lossless, because its SOO much less data, and you can hardly tell the difference in normal listening anyway. What I was trying to express was how bad badly done compression can sound. Good compression exists, and it can sound nearly identical anecdotally, but there is a limit to how low you can go before you start hearing it, and I’m trying to say that I think Spotify has chosen a rate below that level by default. I switched to a higher profile and the problem is mostly gone.
pup_atlas@pawb.social 11 months ago
There may be other factors at play, Apple quite likes to compress stream data between their own devices, even on “standard” protocols (just look at their monitor collaboration with LG where they did the same thing to exceed the max resolution of an existing display signal). Regardless, there is a difference, and it is not a small one. It was immediately obvious to me after listening to a single song. Something about the pipeline is crunching audio to the level where it’s obviously degraded. This isn’t audiophile grade splitting hairs and “I think it sounds ever so slightly better with these gold cables” it was like the difference between 480p and 1080p video to me, enough to be actually annoying during normal listening, even if I was actively trying to forget about it.
First@programming.dev 10 months ago
Ok it sounds like what you experienced was caused by something completely different than detecting an audible difference between Spotify’s 320 kbps AAC encoding and lossless encoding, encoded over a 256 kbps AAC BT codec, but if you actually want to do a true A/B blind test of 320 kbps vs. lossless on your setup, here’s the place to do it:
abx.digitalfeed.net (select the first link - “The statistically valid Tidal test to make”)