thanks for your reply – I only partially agree. Think of an USB device with a
such a single format support which perhaps is shipped with 44.1/16/2 and the
customer connects it to his machine and switches it to 48/24/2 as this is the
samplerate in his complete audio network. Now should I tell him it’s normal
that the device doesn’t show up anymore in his audio device list and that he
just has to wait (and for how long) until things are going to work again? It’s
true that probably those actions will not happen too often, probably only once
after the first startup – but unfortunately this is the first contact to a new
device ending with an unpleasant an unexpected experience.
Would you also have any idea on testing the functionality of the USB feedback
endpoint or do you think my approach should work and I should see a slightly
increased or decreased samplerate in my player application?
Thanks and best regards,
Von: wdmaudiodev-bounce@xxxxxxxxxxxxx Im Auftrag von Tim Roberts
Gesendet: Dienstag, 28. September 2021 19:50
Betreff: [wdmaudiodev] Re: AW: UAC2 driver loaded but no audio endpoints visible
Johannes Freyberger wrote:
so it seems to be no Linux USB audio gadget thing. Without changing anything on
the Linux side 48kHz/24Bit/Stereo suddenly worked after I disconnected my
device from windows, stopped the windows audio endpoint builder, removed all
registry entries in
which pointed to my device, restarted the windows audio endpoint builder and
reconnected my device.
I, also, have had problems when changing the advertised formats after Windows
has already cached my current formats. The Audio Engine seems to have a long
memory. Since this is a development issue that is not likely to be encountered
in a customer-facing situation, I never took the time to analyze this.
Tim Roberts, timr@xxxxxxxxx <mailto:timr@xxxxxxxxx>
Providenza & Boekelheide, Inc.