On Tue, Jun 14, 2011 at 9:47 AM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > Hmm, we really don't need more cmdline options IMHO, it is quite easy to > detect > if an alsa device supports mmap mode, and if not fall back to r/w mode, I > know > several programs which do that (some if which I've written the patches to do > this for myself). Agreed. >> It should be noticed that the driver tries first to access the alsa driver >> directly, >> by using hw:0,0 output device. If it fails, it falls back to plughw:0,0. >> I'm not sure >> what's the name of the pulseaudio output, but I suspect that both are just >> bypassing >> pulseaudio, with is good ;) > > Right this means you're just bypassing pulse audio, which for a tvcard + > tv-viewing Actually, the ALSA client libraries route through PulseAudio (as long as Pulse is running). Basically PulseAudio is providing emulation for the ALSA interface even if you specify "hw:1,0" as the device. > app is a reasonable thing to do. Defaulting to hw:0,0 makes no sense to me > though, we > should default to either the audio devices belonging to the video device (as > determined > through sysfs), or to alsa's default input (which will likely be > pulseaudio). Mauro was talking about the output device, not the input device. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
