Re: [Alsa-user] Audiotrak Maya 44 USB Soundcard
Brought to you by:
perex
From: Hiram A. <dom...@on...> - 2006-03-13 18:19:50
|
Quoting Frank Barknecht <fb...@fo...>: > Hallo, > Hiram Abiff hat gesagt: // Hiram Abiff wrote: > >> Thnx for the tip, will try this. But, no matter which index the >> Maya gets I always have this same issue that I described earlier, >> cannot get it to play anything. > > Yes, and I still have no idea, why it doesn't let you play anything, > not even with the plug-device, which AFAIK is supposed to do all > format, channel count and rate conversions necessary to basically play > anything on any soundcard. I read alsa docs concerning the plug device in the meantime, I don't get it either. **scratch scratch** > I especially don't understand why aplay > complains about not being able to set the hw_params to something like > a samplerate of 22050Hz, when playing a 22050Hz soundfile as in your > first mail. ALSA should know, that the MAYA USB cannot do 22050Hz in > hardware, this card can only do 44.1kHz and 48kHz and aplay should not > even try to use anything else, the plughw-device should instead do > proper conversions as it does on, e.g., the similar Terratec Aureon, > which I have. > Some similar things maybe go wrong in other areas as well, like > channel count or sample format. I don't know the ALSA internals in > this area, so lets hope one of the ALSA experts finds the time to look > at this. > lets, indeed. I did some further testing. Since aplay complains that "Channels count non available" I used sox to convert the test wave file from mono to stereo first, which produced the same error. I then converted to quad after which I get a different error message about the sample rate not being accurate: > I especially don't understand why aplay > complains about not being able to set the hw_params to something like > a samplerate of 22050Hz, when playing a 22050Hz soundfile as in your > first mail. ALSA should know, that the MAYA USB cannot do 22050Hz in > hardware, this card can only do 44.1kHz and 48kHz and aplay should not > even try to use anything else, the plughw-device should instead do > proper conversions as it does on, e.g., the similar Terratec Aureon, > which I have. > Some similar things maybe go wrong in other areas as well, like > channel count or sample format. I don't know the ALSA internals in > this area, so lets hope one of the ALSA experts finds the time to look > at this. > lets, indeed. I did some further testing. Since aplay complains that "Channels count non available" I used sox to convert the test wave file from mono to stereo first, which produced the same error. I then converted to quad after which I get a different error message about the sample rate not being accurate: Playing WAVE 'arrive.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Channels 4 Warning: rate is not accurate (requested = 22050Hz, got = 44100Hz) please, try the plug plugin (-Dplug:hw:2) aplay: set_params:935: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 64 CHANNELS: 4 RATE: 44100 PERIOD_TIME: (125011 125012) PERIOD_SIZE: 5513 PERIOD_BYTES: 44104 PERIODS: (3 4) BUFFER_TIME: 500000 BUFFER_SIZE: 22050 BUFFER_BYTES: 176400 TICK_TIME: 1000 After which I converted the wave file to 44100Hz sample rate and got the same error message that I get when I use the plug device. Playing WAVE 'arrive.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Channels 4 aplay: set_params:935: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 64 CHANNELS: 4 RATE: 44100 PERIOD_TIME: (125011 125012) PERIOD_SIZE: 5513 PERIOD_BYTES: 44104 PERIODS: (3 4) BUFFER_TIME: 500000 BUFFER_SIZE: 22050 BUFFER_BYTES: 176400 TICK_TIME: 1000 I checkveed dmesg, this message appears after each aplay's unsuccesful attempt: cannot submit datapipe for urb 0, err = -38 What is this "urb 0"? -- http://www.egoboobits.net/HiramAbiff |