From: "Luke Bishop" <lbishop AT calvin DOT stemnet DOT nf DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Locked Streams in Allegro
Date: 4 Mar 1998 18:04:31 GMT
Organization: The Zone
Lines: 14
Message-ID: <01bd46de$b9adc8a0$0348a5c6@technoid>
References: <01bd3a85$0198e2a0$0201a8c0 AT technoid> <b8tF7EA+KJ$0EwBF AT talula DOT demon DOT co DOT uk>
NNTP-Posting-Host: n072h003.thezone.net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

> - In terms of overall usefulness, what would you really be able to do
> from a timer based stream update? In most cases I imagine that audio
> streaming code will either be reading a waveform in from disk on the fly
> (impossible from an interrupt handler), or doing some relatively
> expensive calculations to generate it (not a good idea from an interrupt
> handler because it can upset the timer accuracy, and will crash horribly
> if your code ever starts taking longer than the timer speed).

I plan on using it for a 3D positional background sound-effect library for
my 3D game.  The routine prototype checks to insure that it doesn't eat
timers, and will scale itself down in execution length if it takes too
long.  The problem is, in conjunction with an optimized rendering pipeline,
it is almost impossible to get real-time buffer fills.