Astro A50 isn't functioning with the new motherboard.
Astro A50 isn't functioning with the new motherboard.
I've been using a pair of Astro A50 Gen 4s for about five years, primarily on my old Xbox and PC, without any major issues. Last week, I upgraded my motherboard and CPU to a Ryzen 7 9700X with an MSI B650M Mortar. The board has four USB 3.2 (5Gbps) ports (blue) and two USB 3.2 (10Gbps) ports (red). One of the main reasons I like the A50s is their ability to separate voice/communications from game/other sounds and mix them independently. However, when plugged into the blue USB ports, the headset will only recognize one source at a time, or everything gets muted. When I connect the base to a red port, everything works fine. I know this is a first-world problem, but I have a couple of questions: Why does the increased bandwidth matter now? The headset ran for years on a USB 2.0 port (black) and even on my launch-edition Xbox One from 2013 without any issues. While it works, I don’t like having to use a high-bandwidth port for a headset that (in my opinion) shouldn’t require it. This makes me think something might be wrong with my PC’s BIOS or settings. Any insights would be appreciated!
It seems the USB controller might be having trouble with Astro USB. With an Astro A30, the issue appears only when connected to a Lenovo Legion 5 laptop via its USB-A ports. Using a USB-C adapter to another device resolves the problem. On my desktop, it works fine unless I connect it to a USB port on a Wacom drawing tablet. This behavior has been observed for a long time and appears to be specific to Astro.
Another approach could be finding alternative strategies without relying on a specific adapter or the powerful port.
It doesn't seem to be the case. Many people use USB extenders or hubs to get devices working. Likely, the issue involves a USB protocol handshake problem, which works fine on hubs or extenders but not always with direct connections. Extension cables rated for 2.0 usually function properly, while 3.0 may have compatibility issues.