https://bugs.freedesktop.org/show_bug.cgi?id=50256
--- Comment #5 from Tanu Kaskinen <[email protected]> 2012-05-27 06:06:28 UTC --- (In reply to comment #4) > This is not understanding the problem. hw:0 may or may not include mixing. > If > it does not include mixing wine can break and so can applications based off > winelib if they are running there own audio based. > > So the only device other than default you can use in Alsa only or pasuspender > system be sure it has mixing is sysdefault. hw:0 percentage of users will > fail > to have operational audio due to the hardware not supporting mixing. I thought the use case was comparing, for debug purposes, application behavior when using pulseaudio and when using direct alsa. In such cases mixing is not usually needed. pasuspender should never be "the solution" to audio problems with open source software such as wine. pasuspender is only a debugging tool, or a workaround for proprietary software that can't be fixed. In any case, feel free to replace hw:0 in my example with sysdefault, if the lack of mixing is a problem when debugging. Are "sysdefault's" semantics defined somewhere, btw? It's not documented at [1] at least. I doubt that it actually guarantees anything about mixing - my guess would be that "sysdefault" just happens to be usually be defined as card 0 with dmix, and therefore it usually also supports mixing. [1] http://www.alsa-project.org/main/index.php/DeviceNames -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are the assignee for the bug. _______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
