Re: alGetSourcei and AL_BUFFERS_PROCESSED gives junk.
Chris Robinson <[email protected]>
| Newsgroups | gmane.comp.lib.openal |
|---|---|
| Message-ID | <[email protected]> |
On Monday, July 26, 2010 8:34:01 pm Mr Anthony Arnold wrote: > The actual symptom of this is that processed is declared but not > initialised so its final value is the initial junk value that it starts > out with. (Usually something like -8834824334). > > Would this be expected behaviour? The OpenAL specification states that the > value should be from "0 - any" but is not really any more specific than > that. The programmers' guide is the same. Hi. The number of buffers processed should never exceed the number of buffers queued on the source. That it is does, suggests the function is failing and not modifying your variable, as you say. > I am quite sure I have created a context and generated the source correctly > (otherwise it would give errors, right?) It should give errors if the source fails to generate, yes. In the Windows version, however, there is a bug that alGetError() will *always* return AL_NO_ERROR if no context is set current. If you can, double check that alcOpenDevice and alcCreateContext didn't return NULL, and that alcMakeContextCurrent didn't return ALC_FALSE. It does sound like a context isn't properly set up, causing the later calls to silently fail. _______________________________________________ Openal mailing list [email protected] http://opensource.creative.com/mailman/listinfo/openal