Irrlicht Engine

Update: This is now possible in irrKlang 0.7, use ISoundEngine::removeSoundSource() or ISoundEngine::removeAllSoundSources().

Another release is done now, irrKlang 0.7: http://www.ambiera.com/irrklang/ Fixes some bugs, adds some few new features, most have been requested in this forum.

Just blogged about it: http://www.irrlicht3d.org/pivot/entry.php?id=495
It will take just a little time, I'm really annoyed by this dely as well. It's not my fault, I'm going to explain it when it is released

Everything is fixed in irrKlang 0.7 now. Hope it helps. The events will be implemented in a future release of the library.

If you don't shut down the engine (usually done calling engine->drop()) it will continue to play. And it looks like you don't call this when the user presses the 'x' button

For the software drivers (WinMM, ALSA, you can specify this as first parameter in the createIrrKlangDevice() function), there is no limit.

For DirectSound, this depends on the DirectSound implementation (driver, operating system), but from irrKlang's side, there is no limit as well.

Update: The bug has been fixed in irrKlang 0.7. Hope it works for you now.

Hm, this works for me. (Apart from in your example code, the line creating the device should have been 'engine = createIrrKlangDevice(); ', without the ISoundEngine*)
What OS are you using? Are you using the latest version of irrKlang (0.6)?

Ah, thanks for the details. Going to take a look at it. Maybe I should set win mm as default driver

I had no time until now, but I'm going to look at it in the next few days and try to push out a bug fix release if possible.

Right, that's what I'm intending to do

Sounds like some really bad driver for me. I'll integrate that feature into the next irrlicht engine version, and I guess we can find a solution for this problem more quickly then.

Thanks for posting, the events are planned, and yes, the playback position issue is a known problem, going to fix this soon.

Strange, this should work. Going to check it. Maybe you could try out if it does work with the other sound output driver (specify another one via the first parameter when creating the sound engine)

Yep, it should have been corrected in irrKlang 0.6. Please tell me if it works or doesn't work for you in that version.