Streaming buffer?

Quote:

Original post by katsh ya u right. in directsound,u can write(into buffer) and play at the sametime. thats the main concept of streaming-play. btw theres no "streaming buffer".

Quote:

Using Streaming Buffers A streaming buffer plays a long sound that cannot all fit into the buffer at once. As the buffer plays, old data is periodically replaced with new data. To play a streaming buffer, call the IDirectSoundBuffer8::Play method, specifying DSBPLAY_LOOPING in the dwFlags parameter. To halt playback, call the IDirectSoundBuffer8::Stop method. This method stops the buffer immediately, so you need to be sure that all data has been played. This can be done by polling the play position or by setting a notification position. Streaming into a buffer requires the following steps: Ascertain whether the buffer is ready to receive new data. This can be done either by polling the play cursor or by waiting for a notification. Lock a portion of the buffer by using IDirectSoundBuffer8::Lock. This method returns one or two addresses where data can now be written. Write the audio data to the returned address or addresses by using a standard memory-copy routine. Unlock the buffer using IDirectSoundBuffer8::Unlock. The reason IDirectSoundBuffer8::Lock might return two addresses is that you can lock any number of bytes, up to the size of the buffer, regardless of the start point. If necessary, the locked portion wraps around to the beginning of the buffer. If it does, you have to perform two separate memory copies. For example, say you lock 30,000 bytes beginning at offset 20,000 in a 40,000-byte buffer. When you call Lock in this case, it returns four values: The memory address of offset 20,000. The number of bytes locked from that point to the end of the buffer; that is, 20,000 bytes. You write this number of bytes to the first address. The memory address of offset 0. The number of bytes locked from that point; that is, 10,000 bytes. You write this number of bytes to the second address. If no wraparound is necessary, the last two values are NULL and 0 respectively. Although it's possible to lock the entire buffer, you must not do so while it is playing. Normally you refresh only a fraction of the buffer each time. For example, you might lock and write to the first quarter of the buffer as soon as the play cursor reaches the second quarter, and so on. You must never write to the part of the buffer that lies between the play cursor and the write cursor. The following function writes data to a sound buffer, starting at the position passed in dwOffset:

Quote:

Original post by Evil Steve I think what katsh means is there's no seperate interface (Like IDirectSoundStreamingBuffer8 or someting).

Quote:

Original post by Evil Steve The way it works is you only lock part of the buffer, so the sound card can still use the part of the buffer that's not locked.

Quote:

Original post by Evil Steve What I guess DSound does, is just copies the chunk of the buffer you want into system memory, then gives you a pointer to that data. Then when you unlock, it chucks it back to memory addressable by the sound card.

Quote:

Original post by paradoxnj You only want to use streaming buffers for conversation or music. For performance reasons, small sounds like gunshots should be a static buffer.