Re: SB and 2.1.126 [NOT THE COMPILE PROBLEM]

Jamie Lokier (lkd@tantalophile.demon.co.uk)
Wed, 28 Oct 1998 13:22:56 +0000


On Tue, Oct 27, 1998 at 11:24:52AM +0100, Daniel J. Rodriksson wrote:
> This should be the quake case but quake is opening the
> device in read_write mode, so it gets 16 bit input
> and 8 bit playback. I said transparent !!! This is so
> unless you use the mmap technique ( quake uses it ), which
> implies that no software conversion can happen.

BTW, Quake is not the only program that uses mmap(/dev/dsp), nor even
the only game, though it may be the only well known one.

If the full-duplex stuff breaks mmap playback, the /dev/dsp driver
should at least clear the DSP_CAP_MMAP bit. So that programs which use
mmap when available and fall back to write() when not continue to work.
I know such programs exist: I wrote one.

Also I don't think it's obvious that all apps want 16 bit input and 8
bit output in full duplex mode. A record-to-disk program, music studio
etc. obviously wants 16 bit recording to have priority.

I'm not sure which way round an internet telephone program would prefer
-- 16 bit recording might produce a clearer encoding to send, but 16 bit
playback permits better filtering on the reconstructed signal at the
receiver.

A game with atmospheric sound effects and also a chat capability between
players would surely prefer 16 bit playback, so that the subtle effects
produced by the sound generator can be heard.

-- Jamie

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/