man, 28,.02.2005 kl. 11.23 -0600, skrev Jeremy White:
> In other words, afaict, the current code computes the difference
> between the number of bytes that have been played from the input
> source stream (buf_writepos) and the end of the data the app has
> written (probably_valid_to). It then clip
Ove Kaaven wrote:
tor, 24,.02.2005 kl. 22.56 -0600, skrev Jeremy White:
Case 1: In the first case, in DSOUND_MixOne, we compute
a 'probably_valid_to' based on the 'write_pos', which seems quite
wrong; I believe the logic should be testing whether or not
there is sufficient data in the mixing buffe
tor, 24,.02.2005 kl. 22.56 -0600, skrev Jeremy White:
> Case 1: In the first case, in DSOUND_MixOne, we compute
> a 'probably_valid_to' based on the 'write_pos', which seems quite
> wrong; I believe the logic should be testing whether or not
> there is sufficient data in the mixing buffer, not whe
Okay,
So I'm trying to clean up dsound before I make it run properly
in different scheduling conditions, and I'm having a heck of
a time with it; hoping for some advice/thoughts.
First, I encountered two glitches in dsound/mixer.c that appear
to be bugs, but I do not understand the code well enough
