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.

How To Connect Web Html To Wwise Profiler

0 votes

Connecting the Wwise Profiler to a web application using Wwise

Connecting the Wwise Profiler requires running a proxy server in the background. This proxy server acts as a message broker; the Wwise runtime automatically connects to the proxy via WebSocket on startup, and the Wwise Profiler connects to the same proxy via TCP.

To run the proxy server, you will require node.js version 14 or later.

  1. Open a command-line interface, and navigate to the SDK\samples\SoundEngine\Emscripten\WwiseProfilerServer directory.
  2. Install dependencies by running the command npm install.
  3. Start the server by running the command node WwiseProfilerServer.js

This will bind local port 8095 to a WebSocket server. By default, the Wwise runtime connects to ws://localhost:8095/. This can be changed in AkCommSettings::szCommProxyServerUrl on the game side.

Once the server is up, start the web application integrating Wwise. Use your browser's devtools panel to make sure there are no connection errors in the web page's console log when the application starts. If there are no errors, you should see an active WebSocket connection in the devtools' Network tab, and Wwise Authoring should be able to detect the game instance on the local network, just as it would for a more typical desktop application.

Hi everyone,

I'm trying to connect IntegrationDemo WebGL (2024.1.1.8691 SDK/Emscripten_mt/Profile Version) to wwise profiler.

I ran the WwiseProfilerServer,and ran a local server to run IntegrationDemo in chrome.

IntegrationDemo html page worked well,WwiseProfilerServer console also printed ports correctly.

But wwise profiler remote can not see any instance of IntegrationDemo WebGL.

How to fix it?Thanks!

in General Discussion by Shuo L. (100 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...