<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>USBD Audio only supports 2 Channels and 48000 Frequency and FAIL on other values</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62821/usbd-audio-only-supports-2-channels-and-48000-frequency-and-fail-on-other-values</link><description>Hi, 
 I am working on the nrf52840 DK using &amp;quot;nRF5_SDK_16.0.0&amp;quot;. 
 I tested out the example code for USBD Audio in &amp;quot;examples\peripheral\usbd_audio&amp;quot;. 
 If I use the default values (as is), this works fine in Windows 10 using Audacity 2.3.2 to record and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Jun 2020 03:16:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62821/usbd-audio-only-supports-2-channels-and-48000-frequency-and-fail-on-other-values" /><item><title>RE: USBD Audio only supports 2 Channels and 48000 Frequency and FAIL on other values</title><link>https://devzone.nordicsemi.com/thread/256556?ContentTypeID=1</link><pubDate>Wed, 24 Jun 2020 03:16:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:14b26372-0038-4555-b777-eb889f3a4cb6</guid><dc:creator>engleok</dc:creator><description>&lt;p&gt;Hung Bui,&lt;/p&gt;
&lt;p&gt;Confirmed. Thanks for the solution.&lt;/p&gt;
&lt;p&gt;engleok&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: USBD Audio only supports 2 Channels and 48000 Frequency and FAIL on other values</title><link>https://devzone.nordicsemi.com/thread/256516?ContentTypeID=1</link><pubDate>Tue, 23 Jun 2020 14:43:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e0af8d3-5c53-4145-818e-e0e7a25f2844</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Engleok,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We found that it was because Windows cached the descriptor of the device. So if you go to Device Manager and click Uninstall device. Then unplug and plug the device USB port again, Windows will reinstall the device and will update the descriptor. Another option is to change to another PID so that it will show up as a new device to Google.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>