Page 5 of 5

Re: USB Audio 2.0 support coming to Windows 10 from Microsoft

Posted: Wed Jun 27, 2018 4:16 pm
by akp
They monitor the forums, don't worry, they know.

Re: USB Audio 2.0 support coming to Windows 10 from Microsoft

Posted: Fri Jun 29, 2018 12:36 pm
by MaximLiadov
Ok. We are looking forward to any official XMOS comment on this topic. Do they have any plan to make official firmware to be 100% compatible with W10 out-of-the-box driver or not. I don't think we are capable to do this by our own knowledge.

Re: USB Audio 2.0 support coming to Windows 10 from Microsoft

Posted: Tue Jul 03, 2018 8:17 am
by bearcat
(Edited since no reply yet with new data. I had microphone privacy turned on, silly me. And appears a poor USB cable.)

I worked a little bit here... Ill keep the politics out for now.

The Windows UAC2 native driver only supports explicit feedback per the website.
1 - Setting no inputs selects explicit feedback
2 - Enable inputs and add this to customdefines.h: #define UAC_FORCE_FEEDBACK_EP

Inputs can be enabled and still operate as output device.

The UAC2 driver does not support setting a clock selector. The website says they will ignore it. So if you have SPDIF, ADAT, or ? you will need another means to select clocks.

I got the older L1 reference board and latest software to connect and play with explicit feedback and inputs enabled. It operated fine on both inputs and outputs. A loopback showed correct audio.

There if a post online of a Teac dac operating with the UAC2.

I am testing/retesting with my custom board.

So, it appears item 2 above should get things working with the Windows native UAC2 driver with inputs and outputs working. I will offer an update later after more testing.

Re: USB Audio 2.0 support coming to Windows 10 from Microsoft

Posted: Thu Jul 05, 2018 7:00 am
by bearcat
I started a new thread for my summary. See:

http://www.xcore.com/viewtopic.php?f=8&t=6806

Re: USB Audio 2.0 support coming to Windows 10 from Microsoft

Posted: Fri Nov 02, 2018 3:47 pm
by tiasuccess
akp wrote:Just checking if you referred to https://docs.microsoft.com/en-us/window ... io-drivers
If not, you may need to slog through that and make sure everything works out. It seems like Windows is picky, as usual. e.g. you will need to use explicit feedback apparently.


Thanks for the link.