this post was submitted on 17 Dec 2023
557 points (90.2% liked)

Technology

59038 readers
4002 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] First@programming.dev 16 points 10 months ago* (last edited 10 months ago) (2 children)

Do you realize AirPods Max/iPhone is capped at AAC/256 kbps over BT, and needs DAC -> ADC -> DAC to use a wired connection?

[–] HexagonSun@sh.itjust.works 10 points 10 months ago* (last edited 10 months ago) (1 children)

Yep, absolutely this.

You cannot listen to music 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 1 points 10 months ago

If someone thinks AirPods Max sound amazing, they’re agreeing how good compressed audio can sound, whether they realize it or not.

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 1 points 10 months ago (1 children)

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 1 points 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:

https://abx.digitalfeed.net/ (select the first link - "The statistically valid Tidal test to make")