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.

+8 votes

WAMP CALL error ‘ak.wwise.locked’ invoking ‘ak.wwise.core.getInfo’: ‘Cannot execute call because Wwise has an exclusive lock. Please try again later.'

 

When I generate SoundBanks I get this message. I haven't found it to be an issue with any of the workflow but is it something that bite later if I ignore / don't address?

Thanks in advance!

in General Discussion by Edward D. (210 points)
I have this also. Can someone please answer for use both
Love love love these unanswered questions
Strange fix: Start the Unity project (press play)... Connection is then established between WWise and Unity.

1 Answer

0 votes

Errors of the type '‘ak.wwise.locked’ are caused by a modal window or a task in Wwise that cannot allow for WAAPI calls to be processed concurrently. This is the case, for example, when a project is being loaded, a User/Project Preference window is open or SoundBank generation is in process.

Game engine integrations send a 'ak.wwise.core.getInfo' WAAPI call to Wwise at a regular interval for synchronization purposes: if those call occur while the Authoring application is in one of the aforementioned states, this error would be logged.

This is something we are working to address in a future release, but for now these WAAPI log errors can be safely ignored in your workflow. You can also filter out log messages from the Log view settings.

by Samuel L. (Audiokinetic) (23.6k points)
...