<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, Conrad. My regular E-MU 0404 has been configured as Analog Stereo Output for ages. When I received white edition, I plugged it in, and didn't bother to configure anything (I don't even remember why do I have Analog Stereo Output in the first place, I'd say it's a happy coincidence). So the only difference between white and regular on my system was the profile they were configured with. I explicitly tested regular E-MU 0404 just now, and autoswitching does not work if device is configured as Analog Stereo Duplex. Now, another riddle: * archlinux-arm on rPi3 | Analog Stereo Output: works * archlinux-arm on rPi3 | Analog Stereo Duplex: **doesn't work** * archlinux on amd64: works in both cases So this limits the problem to my Raspberry Pi, which I use as a shared sound server. I played with modules loaded on my rPi. Namely, I tried disabling native-tcp and zeroconf-publish modules (I thought maybe some device on the network captures the card inputs and thus locks the sampling frequency), but results are the same: autoswitching works only with Analog Stereo Output profile. Let me know if you are curious to try anything else on my setup, I'd be happy to share results. <div class="moz-cite-prefix">On 4/23/19 12:01 AM, Conrad Jones wrote: </div> <blockquote type="cite" cite="mid:CAG0Z69ORkH1fNLpfHw++KEA6t28-cCfr7ezcC2hKmtK2tBguPw@mail.gmail.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr">This is interesting, are you requiring to switch the profile only on the white edition ? <div> </div> <div>I ask because I have a box full of these in storage, it would be interesting if there is a difference if there is different firmware at play on the device</div> </div> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Mon, Apr 22, 2019 at 11:46 PM edio <<a href="mailto:edio@archlinux.us" moz-do-not-send="true">edio@archlinux.us</a>> wrote: </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I was looking for clues here and there, until I stumbled on this gist: <a href="https://github.com/taravasya/taravasya_snips/commit/a99bc93365aafbdc8a735fe24a9f4107f857144e#diff-e2c3b1bfad69cc1fb921d18bdb7c2bd5" rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/taravasya/taravasya_snips/commit/a99bc93365aafbdc8a735fe24a9f4107f857144e#diff-e2c3b1bfad69cc1fb921d18bdb7c2bd5</a> That gave me an idea, that perhaps switching profile from Duplex to Output would solve my issue. Indeed it did! I switched profile to Analog Stereo Output (instead of Duplex) and frequency autoswitching started working. Would you consider this a bug either in PulseAudio or Linux kernel? Thanks On 4/22/19 12:07 PM, edio wrote: > Hello, > I'm having trouble with sampling frequency autoswitching when using > E-MU 0404 USB soundcard. > > This case is rather strange. > > I have 2 E-MU 0404 USB soundcards: regular one (model EM8761) and > white edition (model EM8762). > > Autoswitching in PulseAudio works with the regular one but not with > the white edition. However in ALSA both sound cards work as expected. > > Here's dmesg output when I connect both: > > ---- > [ 842.304339] usb 1-1.2: new high-speed USB device number 6 using dwc2 > [ 842.446437] usb 1-1.2: New USB device found, idVendor=041e, > idProduct=3f04, bcdDevice= 1.00 > [ 842.466211] usb 1-1.2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 842.479357] usb 1-1.2: Product: E-MU 0404 | USB > [ 842.489520] usb 1-1.2: Manufacturer: E-MU Systems, Inc. > [ 842.500246] usb 1-1.2: SerialNumber: > E-MU-09-3F04-07D90916-0914D-8761T2A > ... > [ 901.444396] usb 1-1.2: new high-speed USB device number 7 using dwc2 > [ 901.586367] usb 1-1.2: New USB device found, idVendor=041e, > idProduct=3f04, bcdDevice= 1.00 > [ 901.603744] usb 1-1.2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 901.616060] usb 1-1.2: Product: E-MU 0404 | USB > [ 901.625459] usb 1-1.2: Manufacturer: E-MU Systems, Inc. > [ 901.635506] usb 1-1.2: SerialNumber: > E-MU-43-3F04-07D70109-0964D-STATION 01 > ---- > > From this both seem to be the same: vendor and product IDs are the > same. Yet somehow, PulseAudio works differently for them. Is there > maybe some sound card specific code in PulseAudio? > > Would appreciate any hints and suggestions on how to debug the issue. > > Thanks > _______________________________________________ pulseaudio-discuss mailing list <a href="mailto:pulseaudio-discuss@lists.freedesktop.org" target="_blank" moz-do-not-send="true">pulseaudio-discuss@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss" rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss</a></blockquote> </div> <fieldset class="mimeAttachmentHeader"></fieldset> <pre class="moz-quote-pre" wrap="">_______________________________________________ pulseaudio-discuss mailing list <a class="moz-txt-link-abbreviated" href="mailto:pulseaudio-discuss@lists.freedesktop.org">pulseaudio-discuss@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss">https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss</a></pre> </blockquote> </body> </html>