Re: Problems with US Robotics usb phone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 23 Jan 2007, Sergei Steshenko wrote:

> On Tue, 23 Jan 2007 10:14:37 -0800 (PST)
> Bill Unruh <unruh@xxxxxxxxxxxxxx> wrote:
>
>> On Tue, 23 Jan 2007, Michele Bonera wrote:
>>
>>> Hi All.
>>>
>>> I recently bought an US Robotics usb phone. The name of the phone is "USB
>>> Internet Mini Phone" and the model is 9602.
>>>
>>> When I plug the phone to my notebook, the usb audio module is loaded correctly
>>> and everything lets you think it works because you can find it in the "audio
>>> cards" list in skype (for example).
>>>
>>> But it doesn't work!
>>>
>>> If you try to play a sound using asound, the result is:
>>>
>>> [root@bellatrix:~]# aplay -D hw:1,0 /usr/share/sounds/pop.wav
>>>
>>> Playing WAVE '/usr/share/sounds/pop.wav' : Signed 16 bit Little Endian, Rate
>>> 44100 Hz, Mono
>>> aplay: set_params:901: Channels count not available
>>
>> Could be that you are trying to play a stereo (2 channel) .wav file over a
>> mono device. I would strongly suspect a phone to be a mono device.
>>
>>
>>>
>>> I really like to use that phone: can someone help me?
>>>
>>> Thank in advance for all your answers.
>>>
>>
>
> If the assumption (mono <-> stereo) is correct, the message
>
> aplay: set_params:901: Channels count not available
>
> manifests a bug.
>
> For the case of mono <-> stereo the message should be something
> like this:
>
> Error - too many (2) channels in input stream, the card supports only 1 channel.

While arguing about the exact phrasing of the error message might be useful
somewhere, I doubt it would be of benefit to the OP, especially since we
have no idea if this is actually the problem. I would suggest that the OP
send the phone a mono source .wav file. Also why is he using the hw: ? That
ensures that if there is any discrepancy nothing can happen. That tells
alsa to not try to make the signal conform to the card in any way, but to
send it straight out if it can, and to fail if it cannot. Why not let alsa
at least try to make the signal conform to the card by removing that hw:
requirement?


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user

[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux