Try

> Technically it would be possible, though it would increase the amount of lock contention when using multiple devices simultaneously. That's more than fine, I think, assuming that extra locking...

Hi, @kcat , thanks for quick response! > Two devices could have the extension, but not be able to share buffers This is not intended to work, in case if...

Thanks for response! I'll need to take a look into [AL_EXT_STATIC_BUFFER](https://github.com/Raulshc/OpenAL-EXT-Repository/blob/master/AL%20Extensions/AL_EXT_STATIC_BUFFER.txt) first and see if it's good fit for the job and will be back!

After examining [AL_EXT_STATIC_BUFFER](https://github.com/Raulshc/OpenAL-EXT-Repository/blob/master/AL%20Extensions/AL_EXT_STATIC_BUFFER.txt): while static buffer can be used to achieve the goal, it has development and abstraction cost: game-engine would have to maintain something like a `map`, that maps...

Small bump to review: just want to sync on a direction of how extension is evolving

> I don't know the actual effect it'll have, but I'd expect different systems to have different behaviors, making it a potential danger even if it appears to work. Depend...

> I am not confident that this will work context-less. In current implementation `mLastThreadError` will cause null-pointer error. This is why return value for context-less api is important. > The...

> But even with just OpenAL Soft, if it's used through the router for whatever reason, an OpenAL call won't get to OpenAL Soft without a context or device handle....

Closing: moved to [AL_EXT_STATIC_BUFFER](https://github.com/Raulshc/OpenAL-EXT-Repository/blob/master/AL%20Extensions/AL_EXT_STATIC_BUFFER.txt) in my engine.

> You are refering to this as a solution for e.g. the Greg to Dexter example, so I assume _LOOP influences moving NPCs after story triggers. No, maybe I was...