Definitely something to look into, but I checked on eBay and they seem to have captive screw connectors I'd have to assemble a cable from. Not impossible but another thing for me to look for.
There are photos at https://www.aliexpress.us/item/3256806185045998.html (I didn't insert one into the article), and a cross-section near the end. I could take a photo of the dongle with heatsink, but not unmodified dongle.
I didn't realize the filter leaked this much AC until I had been using the "working" board for weeks, without audible distortion (but it's still theoretically there). And I'd have to run another power cable to the filter board, since 3.5mm doesn't supply power. It's possible the cable would result in distortion/radiation in the MHz range if the filter isn't located near the chip, but I don't know if this is a problem in practice. It might be something to work on in the future?
> I'm not sure where to source straddle-mount VGA connectors. Alibaba has a product listing that describes the same part found in my DAC, but has no pictures of the actual product.
> I also found straddle-mount VGA to break off the board easily
> All of this is possible... but it's a lot of work for an incremental upgrade that doesn't resolve the jitter and audio dropout problems. Compare this to the HDMI2SCART which required more manufacturing effort, but fulfilled a previously unmet use case; even then the author stopped selling them himself because he couldn't find a better source for chips.
3.5mm, I now know why conventional consumer audio devices don't use mixers, they're a ground loop party
It's also that I don't know how to build a differential input not limited to power supply range, I do think they are sold and I have a mixer at home but it's somewhat bulky for my computer desks.
The CS5213 appears pinout-compatible with the MX929x, interesting. The AG620x is a chip I've had the misfortune of encountering; it was common in Amazon DACs, dropped signal output every 15 minutes or so unless you disconnected the EDID pins from the (monitor?), and interprets input signal in a cursed fashion where 16 or below produces black but only 255 produces full white. If your computer outputs limited range HDMI the analog signal can't reach white, but if your computer outputs full range HDMI the shadows are clipped. This is one of the chips that gave HDMI DACs a reputation for black crush and caused CRT communities to recommend DP.
Interestingly the MiSTer game system community actually patched their FPGAs to output digital signals from 16-255, and have some other way of avoiding the signal dropouts (never talk to EDID?), so this chipset is almost seeked out over incompatible models.
It doesn't smell like a state actor to me, just gross negligence. Brushing up on the Reddit comment we wrote, the MITM isn't exploitable by default, since the client will error out at the 301 redirect and leave an obvious black window on the user's desktop. Exploiting a user would require replacing the 301 redirect with a direct download, which requires the same amount of effort whether the default disclosure was broken or not.
Now if they could've started shipping a modified AMD auto update that followed redirects, that would allow them to pwn users of the updated program. But it would do nothing to people who had installed older versions, up to the version the author installed (which left a black window open indicating the downloads never completed)...
I think that trans people, being the ones with firsthand experience of dysphoria and misgendering, and being a disadvantaged minority (https://www.mckinsey.com/featured-insights/sustainable-inclu...) threatened by right-wing rhetoric, should be the ones to speak for what is right for them ("nothing about us without us"), individually and as a group.
I'm pretty sure they're still allowing puberty blockers for premature puberty, inducing puberty in cis teens, and surgically and medically forcing intersex people into a binary sex without consent.
It's chilling watching the latest political powers openly declare that trans people are not who they are inside and must never be allowed to become what they are inside, while eliminating legal recognition and protection and criminalizing life-saving transition healthcare. I find myself retreating into dissociation because to feel the horrors is more than I can bear.
Yiikes, on my B550M DS3H, previously when I woke my PC from sleep immediately after it slept (eg. by pressing the keyboard or case power button), it would "wake" after 0.5 seconds asleep and turn on the power light but not respond to user input, and not even shut down if I held the power button for 4 seconds! I had to pull power at the wall. This behavior occurred on both Windows and Linux, and was fixed at some point in a BIOS update.
As I understand, KWin does call glGetGraphicsResetStatusARB(), and on Nvidia GPUs, sleep-wake (or opening apps if it crashed the GPU) would cause KDE to detect a graphics reset and print "Desktop effects were restarted due to a graphics reset" (https://github.com/KDE/kwin/blob/10c04995c1f9f82ddbd6610e5e0...). I haven't used Nvidia GPUs in years and don't know if this is still an issue. I think many apps don't check for graphics resets?
I'm not sure if residency is relevant here; the Microsoft link indicates that eviction makes memory inaccessible from the GPU to make room for other memory, which explains why Linux uses the same name for "backing up" VRAM before sleep (through the same underlying mechanism).
I didn't mention in the article but the Nvidia drivers at one point would drop VRAM rather than preserving it, leading to corrupted RGB noise textures in window managers and browsers (and potential crashes though I don't think I encountered them). I suggested doing this on the AMD bug tracker (https://gitlab.freedesktop.org/drm/amd/-/issues/2362#note_20...), but the amdgpu developers weren't interested.
denying self-determination is the root of hierarchy and fascism