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.

0 votes

Hello!

I've been doing some experimentation with 3D spatialization in Wwise 2024.1.6 and noticed that routing to a stereo bus results in some unexpected behaviors.

My mono sources positioning settings are:

    Center %: 0
    Speaker Panning: Direct Assignment
    Listener Relative Routing: Enabled
    3D Spatialization: Position + Orientation
    Speaker Panning / 3D Spatialization Mix: 100
    Attenuation: Enabled
    3D Position: Emitter

This is then routed to a bus that is explicitly set to stereo.

If I set this sound source 1m away and rotate it along the horizon clockwise, I notice that there is a "deadzone" between +/- 45 and +/- 135 deg where the source is hard panned (fully left or fully right). Between +45 and -45 degrees or +135 and -135 degrees I see equal power panning. Personally, I would've expected to only see hard panning when +/- 90 deg in accordance with VBAP / equal amplitude panning.

I also tried rotating the source along the frontal plane (i.e. azimuth is 90 deg and elevation changes). I noticed a similar dead zone between +/- 30 deg elevation. Repeating this experiment when the azimuth angle is not 90 also shows that there is some unintuitive mapping between azimuth & elevation -> channel power.

Does anyone have information regarding the underlying panning algorithm here or why it is set up this way? I'm working on a plugin where mimicking this positioning behavior would be very useful. I looked for information elsewhere (e.g. these docs), but didn't see any clear answers. Any help would be greatly appreciated!

in General Discussion by Mick M. (100 points)
edited by Mick M.

Please sign-in or register to answer this question.

...