Re: [winecfg] Show detected audio systems, and offer selection
On Wed, 26 Jan 2005 15:21:28 +0100, Paul van Schayck wrote:
Never thought a simple popup with a few radio boxes would be this hard...
Welcome to Win32 :(
Changelog: Show the detected audio systems in a popup dialog and offer selection.
I don't think we want to do this, to be honest. The idea for a while has been to just delete that tab entirely and have the driver detected at runtime automatically. An attempt was made before but Alexandre wasn't happy with it. That's what we need to do, rather ask the user questions they shouldn't need to care about. thanks -mike
On Wed, 26 Jan 2005 16:55:14 +0000, Mike Hearn <mh(a)codeweavers.com> wrote:
I don't think we want to do this, to be honest. The idea for a while has been to just delete that tab entirely and have the driver detected at runtime automatically. An attempt was made before but Alexandre wasn't happy with it. That's what we need to do, rather ask the user questions they shouldn't need to care about.
That would be great. But right now we have an autodetect button that will return the first working driver it encounters and then quits even when there are multiple available. And the first in the list would be aRts for most systems. Not really the preferred one. Would it be better to add some info to the audio drivers available in that dialog. Like "Preferred" or "Works best" for example? Paul
On Wed, 26 Jan 2005 20:37:53 +0100, Paul van Schayck wrote:
Would it be better to add some info to the audio drivers available in that dialog. Like "Preferred" or "Works best" for example?
Basically it just involves making each audio driver load in turn and the first one which loads succeeds then having a hardcoded order in winmm.dll, not really hard to code up. thanks -mike
On Wed, 26 Jan 2005, Mike Hearn wrote:
On Wed, 26 Jan 2005 20:37:53 +0100, Paul van Schayck wrote: [...] Basically it just involves making each audio driver load in turn and the first one which loads succeeds then having a hardcoded order in winmm.dll, not really hard to code up.
AFAIK this already works. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy
On Thu, 27 Jan 2005 09:25:53 +0100 (CET), Francois Gouget <fgouget(a)free.fr> wrote:
On Wed, 26 Jan 2005, Mike Hearn wrote:
AFAIK this already works.
So we can just merge the audio and graphics tab into a "Media" tab and put the audio driver selection under an advanced button like in the Drives tab? And remove the autodetect button completely? Paul
Hi, On Thu, Jan 27, 2005 at 10:03:54AM +0100, Paul van Schayck wrote:
On Thu, 27 Jan 2005 09:25:53 +0100 (CET), Francois Gouget <fgouget(a)free.fr> wrote:
On Wed, 26 Jan 2005, Mike Hearn wrote:
AFAIK this already works.
So we can just merge the audio and graphics tab into a "Media" tab and put the audio driver selection under an advanced button like in the Drives tab? And remove the autodetect button completely? (replying in cautionary mode again) Please don't do that!! Media is sooo descriptive, you know... Almost as descriptive as Multimedia. *shudder* Not to mention that this is a *severe* conflict with data storage *media*.
Also, you can bet that in two years the audio area will have some more (i.e.: too many for one tab) features listed, at which time someone will have the great "why didn't we think of this before?" idea to split the media tab up again into its separate parts. Andreas Mohr
On Thu, 27 Jan 2005 13:23:51 +0100, Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> wrote:
(replying in cautionary mode again) Please don't do that!! Media is sooo descriptive, you know... Almost as descriptive as Multimedia. *shudder* Not to mention that this is a *severe* conflict with data storage *media*.
Also, you can bet that in two years the audio area will have some more (i.e.: too many for one tab) features listed, at which time someone will have the great "why didn't we think of this before?" idea to split the media tab up again into its separate parts.
Got the idea from Mike's todo list: http://www.winehq.org/hypermail/wine-devel/2004/07/0427.html "We should probably merge the X11 Driver and Audio tabs together as they both have lots of empty space, and rename it to "Audio and Video"" So just keep the Audio tab and remove the autodetect button. Or keep it all the same. But that would bring us back to the original question. How should we handle multiple detected audio systems? I think removing the auto detect would the best solution. Paul
On Thu, 27 Jan 2005, Paul van Schayck wrote:
On Thu, 27 Jan 2005 09:25:53 +0100 (CET), Francois Gouget <fgouget(a)free.fr> wrote:
On Wed, 26 Jan 2005, Mike Hearn wrote:
AFAIK this already works.
So we can just merge the audio and graphics tab into a "Media" tab and put the audio driver selection under an advanced button like in the Drives tab? And remove the autodetect button completely?
I don't know what's the impact on winecfg. All I'm saying is that normally if you set "Drivers" = "winearts.drv:winealsa.drv:wineoss.drv" it should try each in turn. Actually, it does not stop at the first one. It loads all those that work but that seems right to me: each is exposed to Windows apps and some apps let you choose which one to use. It's a bit like having more than one soundcard in your PC. I believe dsound has some problems with that though. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Hiroshima '45 - Czernobyl '86 - Windows '95
On Thu, 27 Jan 2005 10:03:54 +0100, Paul van Schayck wrote:
So we can just merge the audio and graphics tab into a "Media" tab and put the audio driver selection under an advanced button like in the Drives tab? And remove the autodetect button completely?
No, the idea is to have *no* UI for audio in winecfg at all. If users want to override Wines autodetect algorithm for some reason they can edit the registry. If this already works then we need somebody to test it (eg, enable/disable arts and see if wine chooses the right driver) and then delete that code from winecfg if it does. Right now I think the drivers don't fail to load properly if they are non-functional, that needs to be fixed. thanks -mike
participants (4)
-
Andreas Mohr -
Francois Gouget -
Mike Hearn -
Paul van Schayck