Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

Routing 3D Audio Object Busses to a Processing Buss can cause Audio Objects to not get deleted

0 votes
We've been experiencing this issue, and I found a culprit that fixed our case today.
I'll explain what I did, and hopefully, it will help anyone who may have encountered it. I believe this to be a bug.

We recently enabled spatial audio on our project and have been experiencing this message excessively: "3D audio object limit exceeded; object xxxxx instigated by voice/bus will be mixed."

Upon thorough investigation using the Audio Object Profiler while profiling our game, we discovered an excessive number of audio objects labeled as 'xxxx' (No voice data).' Further inspection revealed that one of our events, which played a looping random container attached to a moving actor, was the source of the issue.
Everytime a sound would be played in the looping container, it would seem to immediately get converted to this "No voice data" audio object, which is never removed.

We would then very quickly exceed the total number of allowed audio objects and all our new audio objects become mixed in the main mix.

Looking at the routing of busses, we could see that the random container was routed to a newly added audio object bus which was routed to a processing bus.

Moving the audio object bus out of the processing bus, and into an existing mixing bus, fixed this issue.

For context, the processing bus had the Delay plugin, with Feedback enabled and set to 97, Process LFE On, and a State that would set the Wet/Dry Mix to -100 under normal circumstances, and 100 when a condition was met in our game.
So it's possible that the delay was causing the audio object to persist even though the Delay was, audibly, off
in General Discussion by Jon E. (100 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...