>>> Hey Grant!
>>> Yes there is a difference. plughw automatically does some conversions for
>>> you and some looking after you. I'm not sure what exactly this comprised.
>>> But I _THINK_! it was samplerate conversion?, channel-counting and opening
>>> the device, so it won't conflict. If there was more, I don't know.
>>> Kindest regards
>>> Julien
>>
>> Hi Julien,
>>
>> I'm having a lot of trouble getting more info on this. mpd doesn't
>> work when I specify hw:0,0 but does work when I specify plughw:0,0 so
>> I'm trying to figure out the difference. plughw does seem to bypass
>> dmix's samplerate conversion, so it seems to work just like hw. There
>> must be a difference though. Could it be documented somewhere?
>>
>> - Grant
>
> On April this year there was a thread with subject
> query alsa for supported sample rates and formats?
> where Clemens Ladisch posted a C program to test hw capabilities.
>
> Perhaps it could be useful in your case too?
> I could send you the source provided in that thread if you don't find it.
> I think it is ustill ok...
> HIH,
> Gianluca
Can you tell me if hw:0,0 is exactly equivalent to the "default" ALSA
device *if* dmix is disabled with the following in /etc/asound.conf:
pcm.!default {
type plug
slave.pcm hw
}
I do know "default" device audio is not being resampled with dmix
disabled like this. Does that make it exactly equivalent to hw:0,0?
- Grant
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
