How to isolate and connect the Wwise profiler to only server or client game instance within UE4 running on same machine

Question

We are trying to hear one player experience versus both when starting a play session in UE 4.22 with 2 players (one as listen server and the other as a client). The challenge is the audio device is shared between both game instances and connecting the Wwise profiler to one or the other doesn't create an isolated player experience. This is important because we have switches that identify co-op players as local / remote that have separate attenuation and spatialization settings. Is there a method that allows us to have this kind of selectivity in Wwise 2019.1.1?

Answer 1

The solution is to open two instances of Wwise using the same project. Then in UE4, launch the game in editor with 2 players. The Editor will be a listen server. Make sure to not have "Use Single Process" checked. This creates two exe instances which can be individually profiled. In one wwise window, profile connect to the editor and in the other wwise window connect to the standalone version of the game. Pick any sound to solo, effectively muting the server or client.

This is very touchy though as they're both working in the same cache. Be sure to disconnect the profiler from each instance before closing any of the game sessions. That seems to have the best results on not having one instance muted until the editor is closed and opened again.