The source of my DIYinHK multichannel XMOS interface refusing to play unless set to 16bit output in the CP was the USB port, specfically the 3.1 ports on a Ryzen mobo.
These 3.1 ports are a part of the Ryzen CPU's SoC (System on chip), typically (e.g Intel mobos) all the USB controllers are part of the chipset and both AMD and Intel have their own USB3 controller hardware I think (they use different drivers at least).
The interface works fine with USB3 ports on an Intel PC, it also works fine with the chipset based USB2 ports on the same AMD mobo.
I'm curious to figure out where this strange and specific issue comes from, if it's unique to this diyinhk interface and/or this mobo/cpu model or a greater issue with XMOS drivers and the Ryzen CPU's USB controller.
These 3.1 ports are a part of the Ryzen CPU's SoC (System on chip), typically (e.g Intel mobos) all the USB controllers are part of the chipset and both AMD and Intel have their own USB3 controller hardware I think (they use different drivers at least).
The interface works fine with USB3 ports on an Intel PC, it also works fine with the chipset based USB2 ports on the same AMD mobo.
I'm curious to figure out where this strange and specific issue comes from, if it's unique to this diyinhk interface and/or this mobo/cpu model or a greater issue with XMOS drivers and the Ryzen CPU's USB controller.
Last edited: