For context, LDAC is one of the few wireless audio codecs stamped Hi-Res by the Japan Audio Society and its encoder is open source since Android 8, so you can see just how long Windows is sleeping on this. I’m excited about the incoming next gen called LC3plus, my next pair is definitely gonna have that.

  • RunAwayFrog@sh.itjust.works
    link
    fedilink
    arrow-up
    13
    ·
    1 year ago

    LDAC claims are completely bullshit.

    LC3plus is worse than AAC quality wise (to be expected). Lower latency is the only thing going for it. And that’s just because AAC is a very high-latency codec. Opus (as a format) would win on both fronts, although there could be issues with creating a high-quality encoder for it that is not too complex, and power-efficient.

    • drwankingstein@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      After testing LC3Plus, Opus, and AAC personally for bluetooth, LDAC claims are BS, but for the usecase for bluetooth, LC3Plus is more then sufficient, I don’t know why people keep quoting this post, under normal usecase, you get 3-6x the bitrate being tested, under which case all three codecs sound transparent with LC3Plus maybe dipping a little low. however latency is significantly better then AAC (tested against libfdk) and marginally better then opus

      • RunAwayFrog@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        After testing LC3Plus, Opus, and AAC personally for bluetooth, LDAC claims are BS

        How did you test Opus for bluetooth?

        latency is significantly better then AAC (tested against libfdk) and marginally better then opus

        In case you didn’t know, you can use 10ms (or even 5ms) frames with Opus instead of the default (20ms). 10ms should roughly match LC3plus’s default latency while still retaining high quality.