Re:DirectSound, new patch available for testing

[Robbert Xerox]

Hi Davin,Two questions about this:
the patch fails here at hunk 5 with current cvs.
2nd question: is creating the key
\HKEY_CURRENT_USER\Software\Wine\Alsa
Driver\UseDirectHW
necessary? If so, i'll have to do that manually (in
regedit) i guess, as winecfg does not create such a
key anywhere. And is this some undocumented key that
also has 
some effects without your patch? thanks in advance for
your answer.

___________________________________________________________ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

DirectSound, new patch available for testing

[Davin McCall]

On Wed, 2 Nov 2005 14:02:55 +0000 (GMT)
Robbert Xerox  wrote:
> Hi Davin,Two questions about this:
> the patch fails here at hunk 5 with current cvs.

Works for me... I just made sure I had the latest files from CVS, but there have been no updates to these files since wine-0.9, apart from a small fix to mixer.c which wouldn't have caused a conflict even if you didn't have it.

Can you give me any more info? How are you applying the patch?

Does anyone else have this problem?
> 2nd question: is creating the key
> \HKEY_CURRENT_USER\Software\Wine\Alsa
> Driver\UseDirectHW
> necessary? If so, i'll have to do that manually (in
> regedit) i guess, as winecfg does not create such a
> key anywhere. And is this some undocumented key that
> also has 
> some effects without your patch? thanks in advance for
> your answer.

a) No, creating the key is not strictly necessary, but at this stage I'd recommend it

b) Yes, this is an undocumented key which also has some effects without my patch.

ALSA provides several type of device. Two of these are "hw" (direct hardware access) and "plughw" (a virtual device representing software layer which does sample rate and format conversion, before passing data on to the hardware).

The key lets you force a "hw" device to be used.

"hw" is the only one which gives you a try mmap'd hardware buffer. If a "plughw" device is used, you can still use ALSA calls to set up an mmap'd buffer but this will be an emulated mmap and as a result you either let latency get ridiculous or you try and feed the hw "just in time". My patch opts for the latter approach but there is a third option (using buffer locking) which I will implement at a later date.

Davin

DirectSound, new patch available for testing

[Jonathan Ernst]

Le jeudi 03 novembre 2005 à 10:08 +1100, Davin McCall a écrit :
> On Wed, 2 Nov 2005 14:02:55 +0000 (GMT)
> Robbert Xerox  wrote:
> > 2nd question: is creating the key
> > \HKEY_CURRENT_USER\Software\Wine\Alsa
> > Driver\UseDirectHW
> > necessary? If so, i'll have to do that manually (in
> > regedit) i guess, as winecfg does not create such a
> > key anywhere. And is this some undocumented key that
> > also has 
> > some effects without your patch? thanks in advance for
> > your answer.
>
> a) No, creating the key is not strictly necessary, but at this stage I'd recommend it
>
> b) Yes, this is an undocumented key which also has some effects without my patch.

It's not undocumented anymore ;-) :
http://wiki.winehq.org/UsefulRegistryKeys

DirectSound, new patch available for testing

[Robert Reif]

Jonathan Ernst wrote:
> Le jeudi 03 novembre 2005 à 10:08 +1100, Davin McCall a écrit :
> > On Wed, 2 Nov 2005 14:02:55 +0000 (GMT)
> > Robbert Xerox  wrote:
> > > 2nd question: is creating the key
> > > \HKEY_CURRENT_USER\Software\Wine\Alsa
> > > Driver\UseDirectHW
> > > necessary? If so, i'll have to do that manually (in
> > > regedit) i guess, as winecfg does not create such a
> > > key anywhere. And is this some undocumented key that
> > > also has 
> > > some effects without your patch? thanks in advance for
> > > your answer.
> >
> > a) No, creating the key is not strictly necessary, but at this stage I'd recommend it
> >
> > b) Yes, this is an undocumented key which also has some effects without my patch.
>
> It's not undocumented anymore ;-) :
> http://wiki.winehq.org/UsefulRegistryKeys

All driver registry settings should be in the audio driver property
page so it can be set from winecfg.

See line 85 in the file wine/dlls/winm/winealsa/alsa.c where
sending a DRV_CONFIGURE message to the driver currently
just pops up a message box.  This message is sent from the winecfg
audio property page when the configure button is pressed. 
Unfortunately it doesn't currently work because opening an audio
driver is broken.

Getting the audio driver property pages working would be a great
project for someone.