menu
search
language
English
Français
日本語
한국어
中文
Community
Blog
Creators Directory
Q & A
Events
Wwise Tour
Wwise Ambassador
Wwise
arrow_drop_down
Strata
arrow_drop_down
Solutions
arrow_drop_down
Learning
arrow_drop_down
Community
arrow_drop_down
Documentation
arrow_drop_down
Help
arrow_drop_down
Sign In
Download
 

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.

source starvation on sounds in memory

0 votes
Hello

We are seeing some source starvation errors in the Wwise profiler, but they are for sounds that are in memory, not streamed!

From what I understand from the documentation, source starvation errors refer to streamed file IO, and I shouldn't be seeing them on memory sounds.

Anyone seen this kind of error before? Is there anything that can cause source starvation errors to be reported for non-streaming sounds?

Cheers
in General Discussion by Simon G. (1.0k points)

1 Answer

0 votes
Hi,

I'm currently having this problem as well, running on NX. Did you learn what was the cause of this?

Jens
by Jens A. (200 points)
We had some feedback that it could be that the wrong error is being reported when the hardware decoder doesn't supply buffers fast enough. We were seeing it on atrac9 encoded files with some extreme runtime pitch shifting.
by Simon G. (1.0k points)
Thanks. That turned out to be the case for me as well. Moving the Wwise threads to a different cpu core in combination with splitting up the load between the hardware audio format and ADPCM solved this for us.
by Jens A. (200 points)
Powered by Question2Answer
...