AudioTrak Optoplay...
Note: This is a repost of an email I sent a week ago which is still awaiting
moderator approval. I'm now a subscriber, so hopefully this post will go
right through....
There was a thread on the alsa-user list back in March discussing Audiotrack products, and specifically the Optoplay USB device. The relevant bits are:
Quoted 9 lines
Quoted 5 lines
The Optoplay, listed as '?' on the matrix, seemed to work OK, the drivers loaded but - no sound output. This is the same as the problem someone reported a coulpe of months ago - it only works at 24 bits, and while the driver loads, apps only try to open the device @ 16 bits, which doesn't work.
This is only for OSS apps. ALSA programs (e.g. aplay) probably would have worked.
Having just tried it out on version 0.9.3c, I can confirm that the optoplay
DOESN'T work, even at 24 bits, using aplay. However, it can be made to work
with a quick hack to the driver code. I'll get to that below. First, here's the errors I get from aplay:
snoopy:/usr/local/alsa/bin # ./aplay ~/24bit.wav
Playing WAVE '/root/24bit.wav' : Signed 24 bit Little Endian in 3bytes, Rate 44100 Hz, Mono
ALSA lib pcm_hw.c:436:(snd_pcm_hw_prepare) SNDRV_PCM_IOCTL_PREPARE failed:
Connection timed out
aplay: set_params:840: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S24_3LE SUBFORMAT: STD SAMPLE_BITS: 24 FRAME_BITS: 24 CHANNELS: 1 RATE: 44100 PERIOD_TIME: (61927 61928) PERIOD_SIZE: 2731 PERIOD_BYTES: 8193 PERIODS: (3 4) BUFFER_TIME: (247664 247665) BUFFER_SIZE: 10922 BUFFER_BYTES: 32766 TICK_TIME: 10000
Also, the following lines are printed in the syslog:
May 24 23:28:17 snoopy kernel: usb-uhci.c: interrupt, status 2, frame# 985 May 24 23:28:18 snoopy kernel: usb_control/bulk_msg: timeout May 24 23:28:18 snoopy kernel: ALSA ../alsa-kernel/usb/usbaudio.c:1026: 5:1:2:
cannot get freq at ep 0x1
I looked at the source code, and line 1026 is in the init_usb_sample_rate function. According to the comment, the calls are made
only if the devices has "sampling rate control" . I hacked that part out (so that the function no longer tries to set the rate) and then the device played just fine, at 24, 16 and 8 bits. The only problem was that it spat out a continuous stream of messages to the syslog. Here's a sample:
May 24 23:44:32 snoopy last message repeated 3 times May 24 23:44:32 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED: was 456, would be 913, bustime = 457 us May 24 23:44:32 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED: was 799, would be 913, bustime = 114 us May 24 23:44:32 snoopy last message repeated 3 times May 24 23:44:33 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED:
was 456, would be 913, bustime = 457 us
These messages continue for as long as the sound is playing.
It looks to me like the audioformat structure is being set wrong for this device. Specifically, the EP_CS_ATTR_SAMPLE_RATE attribute is set when it
probably shouldn't be. Interestingly, a grep for that attribute only
returns 2 hits: the #define for it and the code that I commented out that tests it. I didn't see any place where a value was set or unset.
Can anyone comment on this? And can we find a way to set the audioformat structure properly? Also, what do all the usb-check-bandwidth messages mean? They appear to be coming from the USB system, but since they appear when sound is playing, I assume it has something to do with the snd-usb-audio driver.
I'd be happy to try out any patches or code samples anyone could provide.
Thanks very much,
-Ross
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
Quoted 22 lines · Ross Miller
There was a thread on the alsa-user list back in March discussing Audiotrack products, and specifically the Optoplay USB device. The relevant bits are:
Quoted 8 lines
Quoted 5 lines
The Optoplay, listed as '?' on the matrix, seemed to work OK, the drivers loaded but - no sound output. This is the same as the problem someone reported a coulpe of months ago - it only works at 24 bits, and while the driver loads, apps only try to open the device @ 16 bits, which doesn't work.
This is only for OSS apps. ALSA programs (e.g. aplay) probably would have worked.
Having just tried it out on version 0.9.3c, I can confirm that the optoplay
DOESN'T work, even at 24 bits, using aplay. However, it can be made to work
with a quick hack to the driver code. I'll get to that below. First, here's the errors I get from aplay:snoopy:/usr/local/alsa/bin # ./aplay ~/24bit.wav
Playing WAVE '/root/24bit.wav' : Signed 24 bit Little Endian in 3bytes, Rate 44100 Hz, Mono
ALSA lib pcm_hw.c:436:(snd_pcm_hw_prepare)SNDRV_PCM_IOCTL_PREPAREfailed:
Connection timed out
Quoted 6 lines
aplay: set_params:840: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S24_3LE SAMPLE_BITS: 24 CHANNELS: 1...
Are you sure that the Optoplay supports _one_-channel output?
Quoted 13 lines
Also, the following lines are printed in the syslog:
May 24 23:28:17 snoopy kernel: usb-uhci.c: interrupt, status 2, frame# 985 May 24 23:28:18 snoopy kernel: usb_control/bulk_msg: timeout May 24 23:28:18 snoopy kernel: ALSA ../alsa-kernel/usb/usbaudio.c:1026: 5:1:2:cannot get freq at ep
0x1I looked at the source code, and line 1026 is in the
init_usb_sample_ratefunction. According to the comment, the calls are made
only if the devices has "sampling rate control" . I hacked that part out (so that the function no longer tries to set the rate) and then the device played just fine, at 24, 16 and 8 bits. The only problem was that it spat out a continuous stream of messages to the syslog. Here's a sample:
Quoted 8 lines
May 24 23:44:32 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED:was 456, would be 913, bustime = 457 us
...
These messages continue for as long as the sound is playing.It looks to me like the audioformat structure is being set wrong for this device. Specifically, the
EP_CS_ATTR_SAMPLE_RATEattribute is set when it probably shouldn't be.
Hmm, this flag is to be set by the device in its USB descriptors if it supports sampling rate control.
Please post the contents of /proc/asound/cardX/stream0 and the output of "lsusb -v".
Quoted 1 line
And can we find a way to set the audioformat structure properly?
Yes; the Optoplay isn't the only device with (apparently) broken descriptors.
Quoted 1 line
Also, what do all the usb-check-bandwidth messages mean?
The device sends or receives more data than it should. Probably because the sampling rate isn't set correctly ...
HTH
Clemens
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
This OUGHT to be easy, but I'm a bit lost...
I'm just attempting to write a simple playback routine. Yes, I know that 'aplay' exists, but I need some more goodies, and 'aplay' is too complex in other areas.
I've got a multi-channel interleaved sound file (1-6 channels for the sake of argument) and I'd like it to reproduce. In AC-97 sound hardware (the motherboard has a VIA 82XX chip set) I need to setup the rear outputs to come out the "line-in" jack, and the 5th and 6th channels come out the Mic jack. I'd like to have 2 channel sound OPTIONALLY "double up" and at option come out the "rear" outputs. I wrote programs to do this under OSS (granted it WAS an CMI chip set, but the same jacks existed, and the same controls had to be set). I would like to set these controls with the amixer command line program (the final program will have NO GUI's at ALL).
In addition, I have a Turtle Beach Santa Cruz card (CS42xx chip set). It has nice things like front and rear outputs (even leveled on the card!!). I have my CD player wired into this, and need the mixer controls to make this work as well. The difficult part is finding out exactly the command line to make it work. It is a bit confusing.
Writing the program is the "easy" part. Figuring out the commands and the like is a bit difficult. Any assistance would be quite helpful.
Clues??
Thanks!!
=====
Signature · 13 lines
Tom Watson [email protected] __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
Re: This OUGHT to be easy, but I'm a bit lost...
At Tue, 3 Jun 2003 01:46:06 -0700 (PDT),
Quoted 10 lines · Tom Watson
I'm just attempting to write a simple playback routine. Yes, I know that 'aplay' exists, but I need some more goodies, and 'aplay' is too complex in other areas.
I've got a multi-channel interleaved sound file (1-6 channels for the sake of argument) and I'd like it to reproduce. In AC-97 sound hardware (the motherboard has a VIA 82XX chip set) I need to setup the rear outputs to come out the "line-in" jack, and the 5th and 6th channels come out the Mic jack.
this is rather the problem of mixer configuration. in general, however, you can play via "surround51" pcm:
% aplay -Dsurround51 six-chs.wav
don't forget to raise and unmute "surround" and "center/lfe" volumes.
Quoted 6 lines
I'd like to have 2 channel sound
OPTIONALLY "double up" and at option come out the "rear" outputs. I wrote programs to do this under OSS (granted it WAS an CMI chip set, but the same jacks existed, and the same controls had to be set). I would like to set these controls with the amixer command line program (the final program will have NO GUI's at ALL).
some codecs have already a mixer switch to do that on hardware (e.g. ALC650). or, some driver (e.g. ymfpci) supports it. in theory, it's not difficult on emu10k1, too.
if you do that on software, you can do it by adding a new pcm to ~/.asoundrc with copy plugin.
Quoted 5 lines
In addition, I have a Turtle Beach Santa Cruz card (CS42xx chip set). It has nice things like front and rear outputs (even leveled on the card!!). I have my CD player wired into this, and need the mixer controls to make this work as well. The difficult part is finding out exactly the command line to make it work. It is a bit confusing.
routing the analog CD input to the arbitrary analog/digital out is difficult in general. only some chip does support it. i forgot whether cs46xx can do that.
instead of hardware wiring, you can do it all in digital, i.e. reading via CDDA and sending the PCM data, so that you can handle everything as you like.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
Quoted 5 lines · Clemmens Ladisch
Quoted 2 lines
CHANNELS: 1
...Are you sure that the Optoplay supports _one_-channel output?
That's a good question - I'll try a stereo WAV later this evening after I get off work.
Quoted 3 lines
Please post the contents of
/proc/asound/cardX/stream0and the output of "lsusb -v".
/proc/asound/OptoPlay/stream0:
Ego Systems Inc. AUDIOTRAK OptoPlay at usb-00:07.2-1 : USB Audio
Playback:
Status: Stop
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 32000, 44100, 48000, 64000, 88200, 96000
Interface 1
Altset 2
Format: S24_3LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 32000, 44100, 48000, 64000, 88200, 96000lsusb -v:
Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 0.00
iManufacturer 0
iProduct 2 USB UHCI Root Hub
iSerial 1 1400
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 8
bInterval 255
Language IDs: (length=4)
0000 (null)((null))Bus 001 Device 002: ID 0a92:0053 EGO SYStems, Inc. Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0a92 EGO SYStems, Inc. idProduct 0x0053 bcdDevice 1.00 iManufacturer 1 Ego Systems Inc. iProduct 2 AUDIOTRAK OptoPlay iSerial 0 bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 201
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 1 Control Device
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 40
bInCollection 1
baInterfaceNr( 0) 1
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bNrChannels 2
wChannelConfig 0x0003
Left Front (L)
Right Front (R)
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 10
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 2
bSourceID 1
bControlSize 1
bmaControls( 0) 0x00
bmaControls( 0) 0x03
Mute
Volume
bmaControls( 0) 0x03
Mute
Volume
iFeature 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 3
wTerminalType 0x0301 Speaker
bAssocTerminal 0
bSourceID 2
iTerminal 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 1
bDelay 1 frames
wFormatTag 1 PCM
AudioControl Interface Descriptor:
bLength 26
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType 6 Discrete
tSamFreq[ 0] 32000
tSamFreq[ 1] 44100
tSamFreq[ 2] 48000
tSamFreq[ 3] 64000
tSamFreq[ 4] 88200
tSamFreq[ 5] 96000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 9
Transfer Type Isochronous
Synch Type Adaptive
wMaxPacketSize 384
bInterval 1
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x01
Sampling Frequency
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 1
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 1
bDelay 1 frames
wFormatTag 1 PCM
AudioControl Interface Descriptor:
bLength 26
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 3
bBitResolution 24
bSamFreqType 6 Discrete
tSamFreq[ 0] 32000
tSamFreq[ 1] 44100
tSamFreq[ 2] 48000
tSamFreq[ 3] 64000
tSamFreq[ 4] 88200
tSamFreq[ 5] 96000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 9
Transfer Type Isochronous
Synch Type Adaptive
wMaxPacketSize 576
bInterval 1
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x01
Sampling Frequency
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 42
Report Descriptor: (length is 42)
Item(Global): Usage Page, data= [ 0xa0 0xff ] 65440
(null)
Item(Local ): Usage, data= [ 0x01 ] 1
(null)
Item(Main ): Collection, data= [ 0x01 ] 1
Application
Item(Local ): Usage, data= [ 0x01 ] 1
(null)
Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255 Item(Global): Report Size, data= [ 0x08 ] 8 Item(Global): Report Count, data= [ 0x08 ] 8 Item(Main ): Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile
Bitfield
Item(Local ): Usage, data= [ 0x02 ] 2
(null)
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x08 ] 8
Item(Main ): Output, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile
Bitfield
Item(Local ): Usage, data= [ 0x03 ] 3
(null)
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x08 ] 8
Item(Main ): Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile
Bitfield
Item(Main ): End Collection, data=none
Language IDs: (length=4)
0409 English(US)BTW: Is there any documentation available that explains what all these fields mean?
-Ross
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
Quoted 5 lines · Ross Miller
Quoted 2 lines · Clemmens Ladisch
Are you sure that the Optoplay supports _one_-channel output?
That's a good question - I'll try a stereo WAV later this evening after I get off work.
It doesn't, but your aplay command used the "default" device which automatically converts unsupported sample formats. Anyway, the problem is with the sample rate.
Quoted 4 lines
lsusb -v:
[... many lines ...]
BTW: Is there any documentation available that explains what all these fields mean?
The official documentation for this are the USB 2.0 Specification, the USB Audio Specifications, and the USB Human Interface Device Specification from www.usb.org, but those are not quite easy to parse.
HTH
Clemens
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com.
At Mon, 2 Jun 2003 14:18:26 -0600,
Quoted 5 lines · Ross Miller
Also, the following lines are printed in the syslog:
May 24 23:28:17 snoopy kernel: usb-uhci.c: interrupt, status 2, frame# 985 May 24 23:28:18 snoopy kernel: usb_control/bulk_msg: timeout May 24 23:28:18 snoopy kernel: ALSA ../alsa-kernel/usb/usbaudio.c:1026: 5:1:2:
Quoted 7 lines
cannot get freq at ep
0x1I looked at the source code, and line 1026 is in the
init_usb_sample_ratefunction. According to the comment, the calls are made
only if the devices has "sampling rate control" . I hacked that part out (so that the function no longer tries to set the rate) and then the device played just fine, at 24, 16 and 8 bits.
ok, i added a workaround code in usbaudio.c.
Quoted 10 lines
The only problem was that it spat out a
continuous stream of messages to the syslog. Here's a sample:May 24 23:44:32 snoopy last message repeated 3 times May 24 23:44:32 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED: was 456, would be 913, bustime = 457 us May 24 23:44:32 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED: was 799, would be 913, bustime = 114 us May 24 23:44:32 snoopy last message repeated 3 times May 24 23:44:33 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED:
Quoted 3 lines
was 456, would be 913, bustime = 457 us
These messages continue for as long as the sound is playing.
a possible reason is that either we set up the interface correctly, or we pass too many packets for the requested status.
i added nrpacks module option in usbaudio driver. please set nrpacks=2 to reduce the max number of URB packets.
the changes were committed to cvs now, so please give a try.
ciao,
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com.
Quoted 7 lines · Takashi Iwai
a possible reason is that either we set up the interface correctly, or we pass too many packets for the requested status.
i added nrpacks module option in usbaudio driver. please set nrpacks=2 to reduce the max number of URB packets.the changes were committed to cvs now, so please give a try.
The changes you made allowed me to play sound through the device, but I still get those usb-check-bandwidth messages, regardless of whether or not I used the "nrpacks=2" option for the snd-usb-audio module. Is there anything else we can try? The driver is usable as-is, but all those messages fill up the syslog pretty quick.
Also, although a volume control shows up in alsamixer (and that's all that shows up in alsamixer) it doesn't seem to affect the sound coming out of the optical port; it only controls sound coming out of the analog headphone jack. I don't know if this is a limitation of the hardware, or if something in the software isn't getting set correctly. It'd be nice to have a software volume control for the optical out, though.
Thanks,
-Ross
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com.
At Fri, 6 Jun 2003 00:34:53 -0600,
Quoted 8 lines · Ross Miller
Quoted 5 lines · Takashi Iwai
a possible reason is that either we set up the interface correctly, or we pass too many packets for the requested status.
i added nrpacks module option in usbaudio driver. please set nrpacks=2 to reduce the max number of URB packets.
Quoted 7 lines
Quoted 2 lines
the changes were committed to cvs now, so please give a try.
The changes you made allowed me to play sound through the device, but I still get those usb-check-bandwidth messages, regardless of whether or not I used the "nrpacks=2" option for the snd-usb-audio module. Is there anything else we can try? The driver is usable as-is, but all those messages fill up the syslog pretty quick.
to be sure, please check /proc/asound/card0/stream0 while playback and how much URB packets are being used.
the message can be disabled if you build the kernel without CONFIG_USB_DEBUG, btw.
Quoted 4 lines
Also, although a volume control shows up in alsamixer (and that's all that shows up in alsamixer) it doesn't seem to affect the sound coming out of the optical port; it only controls sound coming out of the analog headphone jack.
if you change a DAC volume, it should not affect the "digital" outs :)
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com.
Quoted 11 lines · Takashi Iwai
Quoted 7 lines
Quoted 1 line
the changes were committed to cvs now, so please give a try.
The changes you made allowed me to play sound through the device, but I still get those usb-check-bandwidth messages, regardless of whether or not I used the "nrpacks=2" option for the snd-usb-audio module. Is there anything else we can try? The driver is usable as-is, but all those messages fill up the syslog pretty quick.
to be sure, please check
/proc/asound/card0/stream0while playback and how much URB packets are being used.
Sorry for the delay in getting back to you; work very rudely intruded on my
life last week..;) Regarding your request, the relevant line from
stream0 looks like:
URBs = 5 [ 2 2 2 2 2 ]
Without the nrpacks=2 option, the URB line looks like:
URBs = 5 [ 4 4 4 4 4 ]
I should point out that things have apparently changed some in the last week. Using the code I checked out of CVS just a few hours ago, I no longer get continuous messages in the syslog. Instead I seem to get a few lines of those usb-check-bandwidth messages each time a new song is loaded by xmms. Then, while the song is playing, I will get occasional breaks in the sound accompanied by a few messages in the syslog similar to the following:
Jun 12 23:36:58 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED: was 912, would be 1140, bustime = 228 us Jun 12 23:36:59 snoopy last message repeated 715 times Jun 12 23:36:59 snoopy kernel: usb-uhci.c: iso_find_start: gap in seamless isochronous scheduling Jun 12 23:36:59 snoopy kernel: usb.c: usb-check-bandwidth would have FAILED: was 912, would be 1140, bustime = 228 us Jun 12 23:37:19 snoopy last message repeated 10003 times Jun 12 23:37:19 snoopy kernel: usb-uhci.c: iso_find_start: gap in seamless isochronous scheduling Jun 12 23:37:19 snoopy kernel: usb.c: usb-check-bandwidth would have
FAILED: was 912, would be 1140, bustime = 228 us
Also, a dialog box will sometimes pop up saying "snd_pcm_wait: Input/output error"
-Ross
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5