Table of Contents

Known Issues and Limitations

Audiokinetic is constantly working to provide you with the highest quality software; however, you should be aware of the limitations and issues in this version of Wwise.

Wwise Known Limitations

The following list describes the limitations in this version of Wwise.

  • Ambisonics
    • 2D panning has no effect on ambisonics voices/busses.
    • 2D panning of voices/busses with standard channel configurations (mono, stereo, 5.1, and so on) has no effect when encoded in ambisonics.
    • The Wwise Matrix does not support ambisonics configurations.
    • When processing ambisonics, the Wwise RoomVerb's Front, Rear, and Center levels are ignored for late reverberation, and the Center level is ignored for early reflections.
  • Audio Busses
    • If you are ducking a bus that is playing a series of short sounds within a looped sequence container set to Continuous, you may experience a loss in ducking between the short sounds or at the loop point of the container. To avoid this behavior, you can either add sample accurate transitions between the sounds within the container, or set the ducking recovery time to anything but zero.
  • Audio File Management
    • The audio pipeline uses real-time sample rate conversion nodes when playing sounds that differ from the platform's native sample rate (48 kHz for Windows). To prevent possible conversion rate aliasing artifacts, content that does not require pitch-shifting such as music should be converted to match that of the native platform. For Windows, it is also possible to have a native format of 24 kHz using the audio quality option that is available from the SDK.
    • The Vorbis encoder library may result in poor audio quality for sounds using sample rates below 16 kHz. The Vorbis codec was specifically tuned for higher sample rates and performs very well above 16 kHz. Audio quality below the 16 kHz sampling rate, however, can vary considerably depending on the encoding settings used and the audio asset itself.
    • Minor artifacts may result when the Wwise loop fixing algorithm specified in some formats' conversion settings is applied. These artifacts, which result from slight time-stretching or pitch-shifting in the algorithm, are less noticeable for sources with a long duration.
    • During the audio conversion process, loop regions that are shorter than the sample boundaries (format-specific) are removed.
    • Looping music clips may lose timing accuracy each time the loop point is crossed due to loop fixing. However, the Play and Stop position in the segment are always sample accurate.
    • It is not recommended to try to align the last and the first samples of two contiguous XMA-converted clips.
    • On the Xbox One, if streamed XMA sounds are played back at very high pitch values (around 2.3x) the last few milliseconds may repeat indefinitely. In general, pitching up streamed XMA sounds with large amounts is not recommended as it can easily lead to source starvation.
    • WG-30292 The SoundBank definition file for the Init SoundBank ('Init.txt') contains a listing of State Groups for each State that is included in a project. However, unless there is a transition time associated with a State Group, Init.bnk does not - and does not need to - contain any information about the State Group. Adding or renaming a State Group will not modify the contents of the Init.bnk, and will therefore not require a regeneration of Init.bnk. The generation of 'Init.txt' is tied to the generation of the 'Init.bnk'. To force 'Init.txt' to reflect an added or renamed State Group and to be regenerated when the contents of 'Init.bnk' have not changed, it must be manually deleted.
    • WG-32821 XMA, OpusNX and AAC do not support Media relocation from one bank to another. This means that if your media content is duplicated in two different sound banks, when a sound is playing while referencing the data of one bank, when this bank is requested to be unloaded, it will cause the sound to stop.
  • Containers
    • Although you may use a Switch Container as a child of a random or sequence container with sample accurate transitions, transitions will not be sample accurate if the Switch Container plays more than one sound simultaneously.
    • The maximum number of children in any type of container is 65,535. Although Wwise lets you create more than 65,535 in the authoring application, no parent-child link can be made between the parent and the child above this limit. Without the link, these child objects cannot receive any notification updates during playback, including changes to volume, positioning, and so on.
    • There are several restrictions and limitations that currently exist when using the crossfade, sample accurate, and trigger rate transitions with random and sequence containers. For more information on using crossfade transitions, refer to the Wwise User Guide's Using Caution with Crossfade Transitions.
    • If the playback instance limit is reached for a Random or Sequence Container using Trigger Rate as the transition type, the currently playing sound as well as the container itself will be killed.
  • Effects
    • Since you cannot apply a crossfade when bypassing or unbypassing an Effect, you may experience clicking when using the Enable/Disable Bypass Event Action.
    • For motion Effects, trigger motors (Default and Xbox One) cannot be activated from the Wwise authoring tool. Only a PC UWP application can use them.
  • High DPI Support
    • With Windows 8.1 and up, when Windows settings are set to display larger text, Wwise will appeared as zoomed-in with slightly blurry text.
  • Interactive Music
    • A Music Switch transition rule cannot use both the options Sync To - Same Time as Playing Segment and Use transition segment. Whenever Use transition segment is enabled, Sync To - Entry Cue is used instead.
    • The Break event action has no effect on objects of the Interactive Music hierarchy. Its functionality may be reproduced with the help of a music switch container.
    • The empty space on a track before a clip will be considered as the clip's pre-entry, possibly causing music transitions to occur later.
    • Run-time sample rate conversion makes sounds longer by approximately 12 samples per minute, causing slight inconsistencies for music objects. Sources in the following sample rates are affected: 44100 Hz, 22050 Hz, 11025 Hz.
    • The wave data displayed in the Music Segment Editor for a converted file represents the original file and not the converted file.
  • Live Edition
    • Some operations are not allowed during playback or when connected to a game, but are erroneously possible to edit using the List View or the Multi-Edit features. These operations include:
      • Modifying the Output bus or the Override bus option.
      • Enabling/Disabling voice limitation system.
    • Editing these during playback could cause instability in the game and could require restarting the sound engine to recover.
  • Positioning
    • If you add or remove a point along the path during playback, the sound will continue to play, but there will be no propagation. The next time you play back the sound, the changes that you made will be applied.
    • Wwise uses an "equal power" schema to ensure that no audio source exceeds 0 dB in any speaker. As a result, all stereo sounds set to 2D positioning will be played 3 dB quieter by Wwise. To maintain the same mixing reference, boost the 2D sounds by 3 dB.
  • Projects
    • When a project is saved to a mapped network drive, performance may be seriously affected. If you decide to save your projects to a mapped network drive, Audiokinetic will not support these projects.
  • Remote Connections
    • If the IP address of a computer changes while the Remote Connections dialog box is open, the computer will be displayed in the Available list using the LAN IP address instead of the usual "Local Host" IP address. If you connect to this computer, this computer will be added to the History list using the LAN IP address even if the same computer is already in the list using the "Local Host" IP address. Wwise doesn't recognize that these two entries are the same remote computer. The next time you use Wwise, both entries will remain in the History list. Despite the duplication, you can connect to the computer using either entry.
    • For information on troubleshooting the remote connection, refer to the Wwise Help list entitled "Troubleshooting Remote Connection Issues" found in the page "Profiling Tips and Best Practices".
  • SDK
    • Debug versions of the Wwise SDK sample effect and source plug-ins cannot be used with the Wwise authoring tool.
  • Streaming
    • Streamed external sources are ignored by the caching system.
    • A soft deadlock may occur when running out of memory in the Stream Manager pool while profiling, as the I/O thread may flood the profiling queue with out-of-memory notifications.
  • Video Drivers
    • Older versions of AMD Radeon drivers may cause Wwise to crash when opening / creating a project. Updating the drivers to the latest version should solve the issue.
  • Voice Behavior
    • In order to save performance, an estimate of the total Voice volume is computed before starting a Voice. (Starting a voice includes streaming, instantiating Effects, and instantiating the mixing Bus hierarchy.) The estimate does not take the volume of mixing Busses or Auxiliary Sends into account. Consequently, voices with virtual voice behavior set to Kill Voice may be immediately killed even when the Bus volume on the output Bus would cause the voice to be above threshold at the time of playback. Likewise, when the output Bus volume is below the threshold but there is an Aux Send, then the voice is killed instantly when played. However, if the sound is playing and then the output Bus volume drops below the threshold, then the sound is - as expected - not killed.

Wwise Known Issues

The following list describes the relevant outstanding issues that could not be resolved in this version of Wwise.

  • Audio Conversion
    • WG-19165: AAC encoding may crash or stall when run from a remote desktop.
  • Audio Files
    • WG-11260: Audio from file with too many markers fails to play. If the marker data chunk in the file header is larger than the granularity of the file streaming, the code fails to read the header.
  • Contents Editor
    • WG-14785: Objects displayed in the Contents Editor are not sorted alphabetically, which can make it difficult to find objects quickly.
  • Decoded SoundBanks
    • WG-30133: (tvOS only) It is not possible to save locally decoded SoundBanks.
  • Game Object 3D Viewer
    • WG-16246: The Game Sync Monitor doesn't update as expected until you add or remove a watch from the Watches list.
  • Integrity Report
    • WG-15569: The integrity report message "Streamed XMA files do not support region loops" may be displayed even when the audio file doesn't contain a region loop.
  • Interactive Music
    • WG-14711: Two 'bar', 'beat' or 'grid' notifications may be sent in a row at segment synchronization points.
    • WG-15728: When a transition segment is added to the Any to Any transition and then removed, the music segment and corresponding media file is still included in the SoundBank, in error.
    • WG-16269: Effect tails are trimmed when effects are inserted in objects of the interactive music hierarchy.
  • Integration Demo
    • WG-40445: The Android Gradle project for IntegrationDemo will fail to build if located under a path containing spaces (such as "Program Files").
  • Keyboard Shortcut manager
    • WG-19947: OS keyboard shortcuts using the "Windows" key can't be remapped in Wwise.
  • Motion
    • WG-14852: Motion FX objects do not work as expected within a Dialogue Event.
    • WG-38787: Xbox One controllers are not working properly in the authoring tool due to compatibility issues between the controller and the Windows driver. We suggest using Xbox 360 controllers instead.
  • Multi-Channel Creator
    • WG-16302: Sample loop markers within a source file are not kept in the multi-channel files generated by the Multi-Channel Creator.
  • Obstruction/Occlusion
    • WG-15678: When updating the Obstruction/Occlusion curves in Wwise while connected to a game, the curve information is not propagated to the game, as expected.
  • Playback Limit
    • WG-15124: Playback limit involving Motion busses may continue to be applied even though it is grayed out in the Wwise application.
  • Profiler
    • WG-15476: Error message missing in the profiler when Wwise detects two similar media files that don't have the same size.
    • WG-15617: When an error occurs in the profiler, Wwise displays the Event ID, but not the Event name.
  • RTPCs
    • WG-14506: Audio glitches may occur when using a Peak Limiter as well as a Parametric EQ that has an output level driven by an RTPC.
  • SDK/Sound Engine
    • WG-15501: Memory address may be reused by Switch container after a game object is unregistered causing Wwise to play a different sound than is expected.
    • WG-16185: Speaker volume matrix callback is not called for 2D sounds in IsInitiallyUnderThreshold.
  • SoundBanks
    • WG-14186: When SoundBanks are generated, Wwise loses registered game objects registered by the SoundFrame preventing sounds from playing.
  • Source Plug-ins
    • WG-16232: Clipping may occur when using the Pink or Red noise color setting within the SoundSeed Air - Woosh source plug-in.
  • Streaming
    • A race condition exists when canceling all transfers (io_bCancelAllTransfersForThisFile is true) directly from within the AK::StreamMgr::IAkIOHookDeferred::Cancel() hook. If you handle the io_bCancelAllTransfersForThisFile == true case, you need to defer calling the completion callback to later (from your usual I/O completion thread, for example).
  • Workgroups
    • WG-15558: When using the Perforce plug-in, the file history scrolls unnecessarily as the information is received.
    • WG-15559: When using the Perforce plug-in, the history returned by P4 truncates the description removing useful information.
    • WG-16257: Wwise may crash when loading a work unit that includes an audio source with a space at the beginning of its filename.
    • WG-20587: Issues may arise when creating nested Work Units whose path on disk exceeds MAX_PATH (255) characters.

The following list describes the limitations specific to this version of the Wwise Authoring Tool for Mac®.

  • Audio File Importer:
    • WG-23920: Mac Authoring Tool: Cannot import WAV files in Wwise using CTRL-Drag and Drop/CTRL-SHIFT Drag and Drop.
  • Audio File Management:
    • WG-24779: Mac Authoring Tool: Prevent moving WAV files outside the "Originals" folder and give an error message.
  • Crankcase Audio REV:
    • WG-29775: Mac Authoring Tool: Users cannot use Crankcase Audio REV.
  • Game Object 3D Viewer:
    • WG-22219: Mac Authoring Tool: The Game Object 3D Viewer doesn't work. Missing view in the Game Object Profiler layout.
  • Keyboard Shortcuts:
    • WG-22228: Mac Authoring Tool: Find a way to expose Mac keyboard shortcuts.
    • WG-25129: Mac Authoring Tool: Wwise keyboard shortcuts are broken when using the Japanese "Romaji" and "Katakana" input sources.
  • Layout/Toolbar/View:
    • WG-22214: Mac Authoring Tool: Wwise layouts get messed up when you use the Mac OS X window management buttons.
    • WG-22217: Mac Authoring Tool: White borders appear when you display/resize a floating view.
    • WG-22388: Mac Authoring Tool: The Default tab selected in every view is not highlighted as expected.
    • WG-22389: Mac Authoring Tool: View content disappears when you try to dock/undock it from the layout.
    • WG-22717: Mac Authoring Tool: Loudness Meter view toolbar UI isn't updated properly when you resize the view (floating and docked).
    • WG-25029: Mac Authoring Tool: New object name is not highlighted by default in Object Creation dialog.
    • WG-25031: Mac Authoring Tool: User interface doesn't refresh properly when connected to a game sending a lot of data.
    • WG-26263: Mac Authoring Tool: Mixing desk user interface doesn't refresh properly when one or two meter-equipped busses are active.
  • Mac OS X version specifics:
    • WG-25485: Mac Authoring Tool: Wwise becomes unresponsive if left open overnight under Mac OS X Mavericks.
    • WG-25990: Mac Authoring Tool: When connecting a Bluetooth or HDMI audio device, the audio doesn't switch automatically to the new device.
    • WG-26203: Mac Authoring Tool: Extra folder icons appear in the Dock when you launch Wwise under Mac OS X Yosemite.
  • Motion:
    • WG-22220: Mac Authoring Tool: Wwise CRASH when you close the Wwise Motion Generator Source Editor.
  • Platforms:
    • WG-22234: Mac Authoring Tool: Select "Mac" as default platform on Mac OS X.
  • Profiler:
    • WG-23660: Mac Authoring Tool: The Performance Monitor contextual menu is not available.
    • WG-25032: Mac Authoring Tool: Missing progress bar when you connect to a Profiling Session file.
  • Projects:
    • WG-22237: Mac Authoring Tool: Cannot open a Wwise project by double-clicking the *.WPROJ file.
  • Project Explorer:
    • WG-24807: Mac Authoring Tool: Object name color doesn't update automatically in the Project Explorer when you delete a WAV file in the MacOS Finder.
  • Project Settings:
    • WG-22244: Mac Authoring Tool: Source Control plug-ins (Perforce and Subversion) are not supported.
    • WG-22387: Mac Authoring Tool: The Windows Volume Threshold entry is missing/empty in the Project Settings dialog.
  • Property Editor:
    • WG-24778: Mac Authoring Tool: Renaming an object in the Property Editor doesn't rename it in the Project Explorer right away.
  • RTPCs:
    • WG-22231: Mac Authoring Tool: There's no anti-aliasing on RTPC curves.
  • SoundBanks:
    • WG-24974: Mac Authoring Tool: Edit box content does not update properly when you edit the SoundBanks Path or Pre/Post Generation Steps.
    • WG-26291: Mac Authoring Tool: The File Packager is not supported on Mac.
  • SoundBank Manager:
    • WG-22243: Mac Authoring Tool: Pressing the ESC key in the SoundBank Manager User Settings dialog clears its content instead of closing it.
  • Source Plug-ins:
    • WG-22216: Mac Authoring Tool: Slider value font size changes on mouse over in the SoundSeed Air plugins source editor.
    • WG-26198: Mac Authoring Tool: Losing audio in SoundSeed Wind while quickly adjusting parameters during playback.
  • User Preferences:
    • WG-22241: Mac Authoring Tool: There's a noticeable Audio Latency when using a 4 buffers (85.33ms) Output Buffer Latency in the User Preferences.
    • WG-22390: Mac Authoring Tool: There's no audio output if you select XAudio2 in the User Preferences.
  • Workgroups:
    • WG-24808: Mac Authoring Tool: Operations performed in the File Manager Work Units tab do not prompt to reopen the Wwise project.