Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Anonymous's avatar
Anonymous
7 years ago

Audio output problems in Wwise, sound disappears.

I am working on a Quest build, using Unity and Wwise.

A two specific points in the Quest build, all audio disappears. The first time it comes back (again at a more or less certain point) the second time it newer comes back.
When profiling in Wwise, the Output peak is hitting 774 dB, when the audio dissappears (see picture). None of the sounds playing at the given time, has unregular volume output. The CPU is not doing anything unusual, there is no voice starvations or anything else that would "justify" the behavior. This is ONLY a problem on the Quest. When build for Rift this never happens.

I am using Resonance Audio as spatializer, i tried removing it. It didn't help.
If I'm removing all ambience, then the problem doesn't happen. Even though the ambience is not doing anything out of the usual in the instances.

Does anyone have experience with something similar to this? or maybe a solution?

I appricated anything you can throw at me. Questions, tips or solutions.

Thank you in advance.


4 Replies

  • 40dB's avatar
    40dB
    Honored Guest

    We are also experiencing this issue. If anyone else has and has any suggestions please let us know. We are also using Wwise and Unity on a Quest. The issue when the issue happens the audio can cut out of the left ear or completely but is very similar in terms of the profiling on Wwise above. we get the flatline of 774.16db.

    Has anyone else experienced this?

    • MetaStoreHelp's avatar
      MetaStoreHelp
      Community Manager

      Hey there @stevenharmongames! Thanks for reaching out. We completely understand how it feels to have issues with developing an app. We recommend reaching out to our specialized developer support team, as they have access to more tools in order to better assist with these sorts of issues. 

  • Were any of you able to solve this? We are getting the same error for Meta and Pico platform.