Le mer 16/11/2005 à 18:47, Robert Reif a écrit : > Steven Edwards wrote: > > >Hi, > > > >On 11/13/05, Robert Reif <[EMAIL PROTECTED]> 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.
Would it be possible to decompress it (from mp3) to a (whatever rate) wav in memory (or on disk) on the fly, and then play that uncompressed wav through the wave mapper so frequency scaling is applied to it? > 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. The approach is similar, just a bit more manual (for the app). > 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? A larger download size for the source/binary archives. 3MB is about 30% of the source package. Vincent