Doomsday Engine

There is already the "logical sound manager" code that handles audio also on the server. Are you thinking of something different here? At least in the past, it has been necessary for some server-side gameplay code to know whether a specific sound is still playing or has been stopped.

Here's a scenario worth considering:

• The server should only send deltas to the client about sounds audible to the particular client.
• If a long-running/looping sound is started far away, how will the server know when a client is close enough to the sound for it to become audible and then send the appropriate delta?

I began working on this several months back in a local branch in which I have already achieved the following:

• Introduced an AudioSystem on client side for managing systems and components used for playback
• Made all components used for playback client-only

In the next phase my plan is to revise the "logical sound manager" design, specifically regarding client/server separation. While there is certainly some overlap here there is not enough to justify the model used presently. Furthermore, one has to consider that a client may not be using the same sound samples as the server.

Scheduling sounds on server side is fundamentally a map-domain concern. A generalized system could be used for scheduling all manner of client side effects.

skyjake wrote:

It would be nice to see some issues here in the tracker regarding that work (and other local work you might have ongoing).

I've got a few different branches on the go, covering a variety of different things :) Once I've cleaned up these branches, I'll push them to the repo and add issues to tracker if missing (although, most of what I've been working on is already covered by existing issues, at least loosely).

skyjake wrote:

Also, does this so far have any relation to the audio classes in libgui (Sound, Waveform, WaveformBank)? My hope was to (re)build the client's audio playback on these.

Thus far I've tried to avoid making too many changes at component level. Its mainly been about high-level architecture and reorganization.