-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
usb audio class device not cross platform #20
Comments
The workaround is to fix the issue that Windows OS (like Windows 10) does not comply with the USB Audio 2.0 spec. Although we still not get the official confirm about this finding from MSFT, but we provide a solution related to the macro USB_DEVICE_WORKAROUND_AUDIO_20_WINDOWS. This macro is disabled by default. User need to enable this macro manually if the environment meet the 3 conditions: We can make sure that our case can work on the OS that totally comply with USB audio spec no matter audio 1.0 or audio 2.0, but we can not meet not meet the requirement for cross-platform working based on the wrong behavior of Windows OS itself, sorry about this. |
thanks for reply, we're aware of audio-class is broken on windows resulting in most sound-card vendors choose to provide their own drivers as a workaround... wish we could have Microsoft jump in an resolve this once and for all including driverless multi-channel support. so it is possible to run stereo in & out on both macOS and Windows10/11 driverless as long as we make use of the high-speed phy, correct!? I will have to try again on the LPC55 ev-kit as I'm not sure if I tested using the FS or HS phy
|
Yes, if you use USB HS then you can ignore this issue on Windows 10/11.
|
In the examples, I noted this define: USB_DEVICE_WORKAROUND_AUDIO_20_WINDOWS, confirmed that you can either get it to run on windows, or mac, but not both...
Since an audio class device is expected to run on both macOS, Linux and Windows, any plans to fix this "compile time workaround"? Would be great if the official NXP UAC2 device driver could get a little update to work cross-platform.
The text was updated successfully, but these errors were encountered: