Jump to content

Samuel T Cogley

Members
  • Content Count

    1842
  • Joined

  • Last visited

1 Follower

About Samuel T Cogley

  • Rank
    Galactic Level Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We have conversed in the past and it seems your USB issues are always..... interesting. Have you tried: A complete power cycle, cold start of the Mac? Different USB cables? Also some things to consider: The speaker icon in Audio MIDI shows which interface will output system audio. For example, your browser playing a web video. IME, software like A+ or Roon will "grab" the interface for something like exclusive access (the degree of "exclusivity" depends on which version of MacOS you're running) When that happens, you'll see the speaker icon move to another interface There's no doubt that I personally have experienced odd USB audio behavior on Macs. And what seems to exacerbate that odd behavior is having multiple DACs attached to the Mac. What surprised me is that a warm reboot (as opposed to power down/up) often does not clear the issues. Also, a USB hub will often cause additional issues. If there's a powered USB hub in the mix, you should also power down/up the hub while the Mac is powered down. I hope this is helpful.
  2. Just post the screenshot to this thread so everyone can see. Google how to do a screenshot in MacOS. It's straight forward.
  3. Hi @bobbmd Any chance you could post a screen shot of what you're seeing? As someone who primarily streams audio from Mac, I'm curious to understand this issue better. Ideally, the screenshot would have both the Audio MIDI settings and your player (with the file playing including the sample rate).
  4. I see that you're apparently immune to irony. 🙂
  5. No doubt the reason you post here, no? 🙂
  6. I was surprised at first when I discovered that USB Audio Class 2 (or for that matter, Class 1) has no error correction features. I actually read the spec (pretty much the whole thing) because I just didn't believe there wasn't error correction in there. There is none.
  7. Can we really characterize high-end HiFi as a growth sector? I'm thinking that luxury manufacturers like dCS need to check the "we decode everything" box just to maintain sales. I've listened to a Vivaldi DAC (playing PCM) and liked it. No way it was worth the outlay, but it was pleasant to listen to. The Old Guard audiophile publications must at least appear to cater to the luxury sector. So their interest in MQA is logical. Is it pro-consumer? No way!
  8. I was talking just about that the authentication does not detect certain kinds of of tampering. I don't think there's any dispute about that.
  9. Those vulnerabilities are a few years old and have been addressed. There's no doubt that SSL has its problems (not the least of which is the unknowns around possible backdoors in AES), but you can't compare it with the utterly broken "authentication" of MQA. They're completely unrelated.
  10. Assuming you're not revealing an SSL vulnerability with your site(s), change just one bit of the data in the encrypted stream, and the alteration detection mechanisms will do their job and you'll know something's amiss. And by the way, editing binary data in a file does not require a "laboratory" or even a white coat. 🙂 And I'm not "attacking" MQA. I'm simply stating that the "authentication" has been effectively circumvented. This is a fact.
  11. Don't recall Dolby heralding their "authentication" scheme. Detecting encoded material (even if it's intentionally adulterated) is a far different thing than advertising your "secure authentication" as a guarantee of "what the artist intended", only to demonstrate that the "authentication" light will still illuminate when the file has been altered. Apples and oranges.
  12. Doesn't matter. The authentication has been broken. EDIT: If you alter the file, and the blue light still comes on, the "authentication" is bogus.
  13. Non sequitur. Netflix isn't advertising "authentication" of the stream.
  14. It can be objectively stated that the "authentication" can be easily circumvented. The practicality of this is not relevant to the fact that the "authentication" is weak.
  15. I thought it was @FredericV who showed that changing certain bits of the payload would alter the sound, but the blue light would remain on (MQA's "authentication" effectively circumvented). Apologies if I'm mistaken.
×
×
  • Create New...