• Lumidaub@feddit.org
    link
    fedilink
    English
    arrow-up
    39
    arrow-down
    3
    ·
    6 days ago

    Admittedly, I could be smarter and/or less sleep deprived, then maybe I wouldn’t be having trouble taking in all the technical information. So I’m not saying this is a bad article. But is there a thesis hidden somewhere (even a tl;dr, as the cool kids say)? I made it about half-way through without knowing what the actual problem is before I gave up (see above lack of smarts and sleep). I THINK it’s suboptimal audio quality? (Which, admittedly again, probability says it is, given this is about headphones)

    tl;dr: me no brain good but me interested, eli5?

    • fleck@lemmy.world
      link
      fedilink
      English
      arrow-up
      50
      ·
      5 days ago

      The observation is that most USB-C to 3.5mm (“aux jack”) audio dongles are supporting high quality audio but only support the USB Full Speed (FS) data rate which is not enough for the high quality audio. This causes problems.

    • Krudler@lemmy.world
      link
      fedilink
      English
      arrow-up
      12
      ·
      edit-2
      5 days ago

      Agreed, and this article is written backwards.

      Problem: Audio is a low power (relatively low data) signal that goes over wire. Audio data (not audio) sent via USB needs decoding into audio before it gets sent down the headphone wire. Implementation fails due to insufficient bandwidth. Graphs and textual details go into details about the bottlenecks.

    • Chronographs@lemmy.zip
      link
      fedilink
      English
      arrow-up
      16
      arrow-down
      1
      ·
      6 days ago

      Buzzing, buttons not working, other devices not working in the same bus. I’d just read it when you’ve had some sleep