Zensō
Major Contributor
The THX is UAC2, I can’t find the spec on the Apple dongle.Are they both UAC2? if so and others find the same it will confirm the problem is not mac hardware, And that it is fixable.
The THX is UAC2, I can’t find the spec on the Apple dongle.Are they both UAC2? if so and others find the same it will confirm the problem is not mac hardware, And that it is fixable.
There is not. You'd need some kind of USB Host device between the HDMI extractor and your DAC. Something like a Raspberry Pi.After reading about the HDMI option, I had a quick google and searched the forum, but I'm guessing there's no easy way to extract audio from HDMI to a USB DAC?
One significant difference is also the amount of power they draw from the usb. The play!4 only draws 0.16w at normal volume, the same perceived volume and headphones on the x1 draws 0.6watts, way more.
And, e.g., the RME ADI-2 DAC that many reported having issues with has an external power supply and can run standalone. Inferring from that, it doesn’t seem to me that the power draw is a good predictor for stuttering.
You're welcome. It's not ideal, but I can live with this solution. I'm certainly happy to move on from trying to solve this headache. As for the bitrate, I'm just having the WiiM output 16/44.1 over S/PDIF which is more than good enough for my ears.Thanks for sharing. AirPlay always worked for me, too. But it is limited to 16 bit and 48 kHz and there is the issue with latency, requiring additional devices, etc. But for some it might provide a good temporary fit.
Maybe that's also an solution for some of you. Afaik there are also bluetooth receivers you could hook into whatever inputs your DAC has.

Thank you the helpful advice.To be honest - from what you have said, it seems likely your mac has become infected with some sort of malware. Particularly the pop up ads you are experiencing, and difficulty installing ad blockers suggest this.
It may be that the malware has allowed someone to compromise your apple ID password. (Apple do not arbitrarily invalidate your password). You need to get that fixed immediately. Contact apple support if you are unable to get your password changed yourself.
And I'd suggest not entering any critical passwords on your mac until you've ensured there is no suspicious software on it.
Sounds like expected behavior. The common denominator that we see here for the stuttering to occur is high memory usage/pressure. If you‘re not running any memory hungry application you‘ll probably only rarely or not at all run into your audio stuttering.I did not notice any audio dropouts after watching Netflix in Safari for a few hours.
Connected my RME ADI-2 DAC FS to a Mac Studio M2 Max with 32 GB RAM running MacOS 13.4. I used one of the USB-A ports in the back for connection to the RME.
Since you seem to be one of the few M2 havers in this thread, do you think you can do a bit of testing for us?I did not notice any audio dropouts after watching Netflix in Safari for a few hours.
Connected my RME ADI-2 DAC FS to a Mac Studio M2 Max with 32 GB RAM running MacOS 13.4. I used one of the USB-A ports in the back for connection to the RME.
The Mac Studio M2 max 32 GB is a gift to my daughter so it’s in use for the moment. I’ll see what I can do in a week or so.Since you seem to be one of the few M2 havers in this thread, do you think you can do a bit of testing for us?
Discussions a few pages ago suggests that this problem is isolated to the M1 devices and that M2 devices are not affected by this issue at all. Could you try artificially increasing the RAM load to your system to induce medium/high memory pressure (yellow graph in the activity monitor, which should show up at or around 29-30GB RAM usage) and see if any audio skipping shows up?
You can try either opening many professional apps at the same time or, if that's usually not your workflow, use this link https://www.trackthis.link/ and open as many Chrome tabs as you can through the system (I think 6-7 instance of 100 tabs will get you to 29-30GB RAM usage easily).
We're trying to track if this might have also been a hardware-related issue that Apple is keeping quiet about to prevent a recall.