search for: open_callback

...ng a long time to open before they start playing. I have about 30+ OGG files that I have joined together, now the engine I am working on has its own file management and when I use the OV open_callbaks it spends a long time constantly seeking and reading in different sets of 8500 bytes inside the open_callbacks function, some time for as long as 20-30 seconds, I assume this is doing something to find out the information for each of the individual oggs inside the packed file, is there anyway to speed this process up, or not make It search for the info at all as I have all the offsets to each ogg stored in...

...I've verified my audio playback code by using a generated sine wave (sounds correct). So that leads to a problem with how I'm using ov_read(). I've modeled my code around the sample code, and I check my error returns fairly religiously. The only weird thing I'm doing is using ov_open_callbacks(). My callback routines simply read data out of an in-memory bit bucket, so there's not much code there, e.g. my read function is basically: memcpy(pDst, myStreamPtr, bytes ); myStreamPtr += bytes; ..etc. etc. I didn't bother implementing a close function (I just stubbed it out). Look...