> The sa.c code generated by sfront for Windows DirectSound output (-aout
> dsound option) contains a bug that causes compilation to fail. [..]
> Even with the patched code, however, in the perc example the DirectSound
> output on my PII 450 MHz contains some clicks and the timing sounds wrong. I
> suspect the driver contains some incorrect buffering or looping code.
Basically, the driver code generated when using the "-aout dsound" and
"-cin dsound" options is up to the community to either fix up or abandon
for a better driver at this point -- I can integrate changes on these
that people send in, but since I didn't write the original code, and I
don't have a Windows machine to test the code on, there's little else I
can do.
Changes to the dsound code, however, should be made to the following
files:
sfront/src/lib/asys/dsound.c
sfront/src/lib/csys/win32.c
sfront/src/lib/csrc/winmmp.c
sfront/src/lib/csrc/winmmt.c
which are the source files that are used to create the asyslib.c, asyslib.h,
csrclib.c, csrclib.h, csyslib.c, and csyslib.h, by the simple program
sfront/src/lib/libmaker
I run libmaker every time I do a distribution to create new *lib.{c,h} files,
so changes need to start there (plus, its much easier to edit those files
anyways).
--jl
This archive was generated by hypermail 2b29 : Wed May 10 2000 - 12:15:36 EDT