[winecfg] add sound driver test

Robert Reif reif at earthlink.net
Wed Nov 16 17:47:32 CST 2005


Steven Edwards wrote:

>Hi,
>
>On 11/13/05, Robert Reif <reif at earthlink.net> wrote:
>  
>
>>Changelog:
>>- add a simple sound driver test
>>
>>Download the test wave file from:
>>    
>>
>
>This is 3 megs. Could we not use a higher level studd and use winemp3
>to docode a mp3 that can be embedded in a resource script? I wrote a
>patch a few months back alot like the one you submitted but I decided
>to trash the idea when I saw how large and how much of a pain it would
>be to deal with a *.wav test.
>
>Thanks
>Steven
>  
>

One problem when using a compressed wave file is that you loose
the ability to use the wave mapper to resample the sound on the
fly for playback on drivers or soundcards that don't support
multiple sample rates.  For example, you can't use PlaySound
to play back a 44100 Hz mp3 on an i810 based (fixed 48kHz)
sound card (with 100% certainty) or Jack set to 48kHz.  This
will lead the user to believe that sound doesn't work when in
fact it may work but just not with that file using PlaySound.

One way to work around this is to modify the wave mapper to
pass data through more than one codec.  I can't get a native XP
msacm32.drv to work with wine so I can't verify if windows
will do multiple serial conversions.  I doubt that it will but I
will continue to look into this.

Another option is to duplicate the functionality of PlaySound
and the wave mapper in winecfg so it will play any arbitrary
wave file on any hardware.  This is a lot of work for a simple
test.

What are the down sides of using a large wave file?




More information about the wine-patches mailing list