[pulseaudio-discuss] Frequency autoswitching with E-MU 0404 USB

[edio]

I was looking for clues here and there, until I stumbled on this gist:
https://github.com/taravasya/taravasya_snips/commit/a99bc93365aafbdc8a735fe24a9f4107f857144e#diff-e2c3b1bfad69cc1fb921d18bdb7c2bd5

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
>