Alexandre Julliard a écrit :
Eric Pouech <[EMAIL PROTECTED]> writes:
I don't think we want to add yet another driver just for
autodetection. Each driver should simply refuse to load if its
hardware isn't present, then winmm can load each of them in turn
until one succeeds.
you must then ensure tha
Alexandre Julliard wrote:
[...]
I don't think we want to add yet another driver just for
autodetection. Each driver should simply refuse to load if its
hardware isn't present, then winmm can load each of them in turn
until one succeeds.
Note that this pretty much works already. To try it out, edit
Eric Pouech <[EMAIL PROTECTED]> writes:
>> I don't think we want to add yet another driver just for
>> autodetection. Each driver should simply refuse to load if its
>> hardware isn't present, then winmm can load each of them in turn
>> until one succeeds.
> you must then ensure that the list of d
I don't think we want to add yet another driver just for
autodetection. Each driver should simply refuse to load if its
hardware isn't present, then winmm can load each of them in turn
until one succeeds.
you must then ensure that the list of drivers from the registry fits you
desired order (e.g.
Eric Pouech <[EMAIL PROTECTED]> writes:
> there were at that point two different discussions, which may boil
> down, someday, to the same thing:
> 1/ don't put driver detection in winmm. we want winmm to load drivers
> from the registry settings, so that it can be shared between, say,
> Wine and R
For now I'll use winemmdetect, and if we decide to change it later,
then that's ok...I can change it.
On Sun, 3 Oct 2004 18:00:54 +0200, Andreas Mohr
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Sun, Oct 03, 2004 at 11:11:56AM -0400, James Hawkins wrote:
> > > >What about winemmdetect ?
> > > I vote
Hi,
On Sun, Oct 03, 2004 at 11:11:56AM -0400, James Hawkins wrote:
> > >What about winemmdetect ?
> > I vote for winemmd, winemma or in most lengthy case - winemmauto.
>
> hehe what's it gonna be?
Who knows, but I vote for winemmauto or winemmdetect (or _ variants
of those) or wineaudioauto etc.
> >What about winemmdetect ?
> I vote for winemmd, winemma or in most lengthy case - winemmauto.
hehe what's it gonna be?
On Sun, 3 Oct 2004 17:57:30 +0200 (EET), Saulius Krasuckas
<[EMAIL PROTECTED]> wrote:
> On Sun, 3 Oct 2004, Eric Pouech wrote:
> > James Hawkins a ïcrit :
>
>
> > >>they ar
On Sun, 3 Oct 2004, Eric Pouech wrote:
> James Hawkins a écrit :
> >>they are more than that. they also implement wave in, midi, mixer type
> >>of interface... You need to proxy all of that.
> >
> >
> > Ok, well I think I have enough information to start churning out this
> > driver. Does the na
James Hawkins a écrit :
they are more than that. they also implement wave in, midi, mixer type
of interface... You need to proxy all of that.
Ok, well I think I have enough information to start churning out this
driver. Does the name winemmautodetect work?
perhaps a bit long. What about winemmdet
> they are more than that. they also implement wave in, midi, mixer type
> of interface... You need to proxy all of that.
Ok, well I think I have enough information to start churning out this
driver. Does the name winemmautodetect work?
On Fri, 01 Oct 2004 23:24:13 +0200, Eric Pouech <[EMAIL PR
James Hawkins a écrit :
I want to make sure I'm getting the right idea. So I would implement
a new audio driver like winealsa, wineoss etc but named something like
wineautodetect.
yes (I'd rather put a ref to sound or MM in the driver name)
This driver is actually a proxy that checks each of
the
I want to make sure I'm getting the right idea. So I would implement
a new audio driver like winealsa, wineoss etc but named something like
wineautodetect. This driver is actually a proxy that checks each of
the available drivers to see if they are available, and if so,
initialize that driver and
> If you want to get a glimpse at what a proxy driver should be, look
> inside dlls/winmm/wavemap
Ok, thanks Eric. I'll take a look at what we have and see if I can
come up with something useful.
On Fri, 01 Oct 2004 21:29:44 +0200, Eric Pouech <[EMAIL PROTECTED]> wrote:
> > I remember working on
I remember working on this a couple months ago. I put the driver
detection in winmm.c, but that was wrong. I can't remember exactly
what I was supposed to do to fix it...something like put the driver
detection in each driver. I'm not really sure what that means or how
it would work if it does wh
>From Mike Hearn's winecfg post:
> > - Obviously, once audio autodetection has been moved into the drivers we
> > need to kill the audio tab.
>
> Still needs to be done. Not all that hard.
I remember working on this a couple months ago. I put the driver
detection in winmm.c, but that was wrong.
16 matches
Mail list logo
