RFC: Remove auto-scan of ALSA devices from winealsa.drv
austinenglish at gmail.com
Tue Dec 11 13:11:36 CST 2012
On Tue, Dec 11, 2012 at 9:39 AM, Max TenEyck Woodbury
<max at mtew.isa-geek.net> wrote:
> On 12/11/2012 10:46 AM, Henri Verbeet wrote:
>> On 11 December 2012 16:05, <Joerg-Cyril.Hoehle at t-systems.com> wrote:
>>> Cost to users:
>>> Users with a working ALSA device "default" should experience no
>>> drawback, only benefits. I believe this is the vast majority of users.
>>> Users that edit their ~/.asoundrc to define other devices without
>>> simultaneously overriding !default will have to additionally edit the
>>> Wine registry to name their working ALSA capture and render devices,
>>> e.g. "asnoop" and "amix".
>> It will also pretty much just remove device selection on setup with
>> multiple audio devices, which is actually fairly common these days
>> with USB audio devices and HDMI outputs on graphics cards. I think the
>> correct approach would to work with upstream ALSA to fix things,
>> instead of just removing device enumeration.
> I do not think this is a particularly good idea. I do have two sound
> systems on my machine and I have assigned each to different roles. That
> seems to work quite well. What does not work well is leaving the role
> set to 'default'. That results in the selection of the highest latency
> device with corresponding stutters and over-runs. The current
> requirement for selecting an output device is mildly annoying, but no
> where near as annoying as being forced to use a faulty device.
You'd still be able to select a different device in the registry.
More information about the wine-devel