On 22 June 2010 13:58, Sid Boyce <sboyce@xxxxxxxxxxxxxxxx> wrote: > I have an application using the on-board sound card mic which should send > it's data to the USB card for relay to a Sofweare Defined Radio as 2 > quadrature signals digital (I/Q) for transmission. > On the receiving side it can take data from the Radio at up to 192K sample > rate --> program --> Speaker on the on-board sound card - that works fine. > Transmit fails, dmesg output with 48K sample rate set is:- > [509686.177169] ALSA sound/usb/clock.c:214: 6:2:3: endpoint lacks sample > rate attribute bit, cannot set. > [509686.187920] ALSA sound/usb/clock.c:214: 6:2:1: endpoint lacks sample > rate attribute bit, cannot set. > [509686.266905] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509686.330901] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509686.353775] ALSA sound/usb/clock.c:214: 6:2:7: endpoint lacks sample > rate attribute bit, cannot set. > [509686.394898] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509686.458886] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509686.522874] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509823.078594] ALSA sound/usb/clock.c:214: 6:2:3: endpoint lacks sample > rate attribute bit, cannot set. > [509823.091571] ALSA sound/usb/clock.c:214: 6:2:1: endpoint lacks sample > rate attribute bit, cannot set. > [509823.146811] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509823.202679] ALSA sound/usb/clock.c:214: 6:2:7: endpoint lacks sample > rate attribute bit, cannot set. > [509823.210807] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509823.274792] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509823.338782] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > [509823.402783] ALSA sound/usb/mixer.c:2051: status interrupt: c0 0e > Regards > Sid. > -- This device uses a global clock rate according to the data sheets. So, record rate must equal playback rate. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
