[Openal-devel] Bug within alSourcePlay

[J. Valenzuela]

Spoke too soon.  Fixed in cvs.

--
jv

On Jan 27, 2004, at 3:00 PM, J. Valenzuela wrote:

>
> On Jan 27, 2004, at 2:45 PM, lee winder wrote:
>
>>> This would indeed be a bug -- but are you sure that this is
>>> what you're seeing?  One thing that confuses people (that is,
>>> me) is that alSourcePlay() on an already-playing source is not
>>> a no-op, but rather will cause a reset-and-play.  So, if you're
>>> accidentally causing two alSourcePlay()s (say, the key on the
>>> keyboard whose being down causes an alSourcePlay() is down for
>>> two frames in a row or is key-repeating) then you'll be causing
>>> a reset of the playing position too.
>>
>> No I'm sure thats not the case.  If I alter code so that it plays 
>> alSourcePlay() after alSourecPause() (checking that the state is 
>> indeed AL_PAUSED) and step through the code, then it defently resets. 
>>  I have looked at the ALsource structure, and the bytes played etc. 
>> variables all seem to reset within the function
>
> That's pretty weird.  I'm looking at the code in al_mixer.c 
> (_alAddSourceToMixer) and it looks like it should resume at the same 
> soundpos.  I guess it's possible that soundpos is getting clobbered 
> somewhere.
>
> --
> jv
>
> _______________________________________________
> openal-devel mailing list
> openal-devel at opensource.creative.com
> http://opensource.creative.com/mailman/listinfo/openal-devel
>