Table des matières
Wwise SDK 2018.1.11
WG-25210 Bus and voice "volume callback" (AkSpeakerVolumeMatrixCallbackInfo)
Bus and voice "volume matrix" callback now share the same structure. The ID of both the destination bus and input (voice or bus) is accessible through the use of the AK::IAkMixerInputContext and AK::IAkMixerPluginContext interfaces, although the ID is internal in the case of voices. In the case of a voice, the callback is called as many times as there are connection to a mix bus, for example, once for the direct path and once for each send to auxiliary busses.
Multi-channel volume vectors and matrices are not represented by a structure with channel names anymore, but instead as a pointer to a float, typedef'ed as AK::SpeakerVolumes::VectorPtr or AK::SpeakerVolumes::MatrixPtr. The size of these vectors/matrices depends on the channel configuration(s). In the case of a volume matrix, input channels should be accessed using AK::SpeakerVolumes::Matrix::GetChannel(). Elements of vectors should be accessed using the standard bracket  operator. See AkSpeakerVolumes.h for more details. The channel ordering follows the channel bit ordering defined in AkSpeakerConfig.h, except for the LFE which is always placed at the end. This change affects the AkSpeakerVolumeMatrixCallbackInfo callback and AK::SoundEngine::SetListenerSpatialization().
See Enhanced Voice/Bus Volume Callback (AkSpeakerVolumeMatrixCallbackInfo) and Metering Access from SDK, Advanced Mix Customization Using the Speaker Matrix Callback, AkSpeakerVolumeMatrixCallbackInfo and AK::SpeakerVolumes for more details.
WG-25442 GenAudio RTI plug-in is migrating to the new Mixer plug-in system.
In Wwise 2014.1, we will conjointly support the legacy GenAudio RTI Effect plug-in and the new GenAudio RTI Mixer integrated plug-in. We strongly suggest switching to the new mixer system as it offers a more flexible solution.
Note: If you decide to continue using the legacy GenAudio RTI Effect plug-in, there is a behaviour change in the legacy effect plug-in:
- The "Azimuth" control range is now [-180, 180], previously it was [0, 360]. It is most likely that if you previously had matched an RTPC graph to this value, the graph will need to be re-done to match the new control values.
- Also take note that, starting with Wwise 2014.1, there is a new feature allowing you to have an RTPC automatically driven by the actual Azimuth/Elevation/Distance without the need for the game side to drive the RTPC values, see information on Built-in Game Parameters.
WG-25190 User SoundBank Settings persistence system was improved.
Pre-2014.1 User SoundBank Settings will be lost when migrating as of 2014.1
- Prior to this change, migration of User SoundBank Settings was not possible. With this change, it is now included in the Wwise project folder and can now be properly migrated along with the other project files.
- Project SoundBank Settings will still be correctly migrated.
Starting from 2014.1, User SoundBank Settings will be properly persisted in the Wwise Project User's *.wsettings file.
Please refer to the Installation and Migration Guide for general advice about migrating projects to a new version of Wwise.