[alsa-devel] Solved Hercules RMX2

[Daniel Schürmann]

Hallo Alsa Developers,

I have fixed Support for Hercules RMX2.

You can find the Bug and the patch here:
https://bugs.launchpad.net/mixxx/+bug/1096687

The issue was caused by the first time setting the rate.
I have changed the usb_msg_timeout to 1500 ms to make it work.
The measures time is a ~1240 ms.
All following rate settings are finished in not time < 4 ms

Sound is now working fine but there are still IO errors just after
connecting the device

errno 5 - input/output error

Here the extended Log:
Apr 14 23:50:37 KellerPc kernel: [19213.746929] snd_usb_autoresume() -19
ID:6f8b113 chip->shutdown 0 chip->probing 1.
Apr 14 23:50:37 KellerPc kernel: [19213.746934] -5 1 cannot get ctl value:
req = 0x83, wValue = 0x201, wIndex = 0x0, type = 4
Apr 14 23:50:37 KellerPc kernel: [19213.747053] snd_usb_autoresume() -19
ID:6f8b113 chip->shutdown 0 chip->probing 1.
Apr 14 23:50:37 KellerPc kernel: [19213.747058] -5 1 cannot get ctl value:
req = 0x83, wValue = 0x200, wIndex = 0x0, type = 4
Apr 14 23:50:37 KellerPc kernel: [19213.747430] snd_usb_autoresume() -19
ID:6f8b113 chip->shutdown 0 chip->probing 1.
Apr 14 23:50:37 KellerPc kernel: [19213.747435] -5 1 cannot get ctl value:
req = 0x83, wValue = 0x201, wIndex = 0x0, type = 4
Apr 14 23:50:37 KellerPc kernel: [19213.747554] snd_usb_autoresume() -19
ID:6f8b113 chip->shutdown 0 chip->probing 1.
Apr 14 23:50:37 KellerPc kernel: [19213.747559] -5 1 cannot get ctl value:
req = 0x83, wValue = 0x200, wIndex = 0x0, type = 4
Apr 14 23:50:37 KellerPc kernel: [19213.752599] usbcore: registered new
interface driver snd-usb-audio
Apr 14 23:50:37 KellerPc kernel: [19213.775204] snd_usb_ctl_msg()
dev:ed5eb000 pipe:80000d80 request:02, requesttype:a1, value:0201,
index:0a00, data_size:8.
Apr 14 23:50:37 KellerPc kernel: [19213.776264] snd_usb_ctl_msg()
dev:ed5eb000 pipe:80000d80 request:02, requesttype:a1, value:0201,
index:0a00, data_size:8.
Apr 14 23:50:37 KellerPc kernel: [19213.776436] snd_usb_ctl_msg()
dev:ed5eb000 pipe:80000d80 request:02, requesttype:a1, value:0201,
index:0a00, data_size:8.

The current solution is fine for me, but maybe there is an other place for
tweaking the startup timing. Any ideas?

Is it possible to include the fix in trunk?

Thank you.

Kind regards,

Daniel Schürmann