Wwise provides some tools to enhance the workflow to import large amounts of assets and easily create many simple audio structures in the editor.
A typical proposed workflow could go as follows:
- Use the Voice Asset Importer (from the project menu)
-> This will automatically import a large number of wav files with filenames and sound object names (as well as other information) specified in a tab delimited file in Wwise.
- Multi select all imported assets and use the multi-editor to set sound properties and set conversion
settings for all selected sounds simultaneously.
- Use programmatic sound stops using
StopPlayingID() to avoid the need to create explicit stop events.
- Organize newly created events into various sound banks using sound bank definition file loaded in
the SoundBanks explorer view with a right click -> Import soundbank
definition... .
-> This will automatically create all the banks defined in
the file and assign events to these banks as specified in the soundbank
definition file (see details in SDK -> Windows -> Going Further
-> Using SoundFrame)
Despite these tools, sometimes this workflow is not enough and Wwise users
wish they could automatically generate some of the Wwise work unit
files from an in-house tool managing assets like dialogs for example.
Important warning: The automatic generation of Work unit project files is not officially supported, but may be used as last resort when the workflow tools mentioned above are not sufficient. Some knowledge of Wwise persistence is required and there is no documentation provided on the topic. This document only provides pointers to get you started.
The XML schema for Work Units is available in the Schemas folder in the Wwise installation (ObjectDataSchema.N.xsd - use the one with the biggest number). This schema can be used to understand the format of Work Unit files, and it can also be used to validate the XML file generated. Looking at the .WWU files saved by Wwise with simple projects will also allow you to see how information should be organized. The schema version is present in all .WWU files and indicates which version of the XSD file was used to generate the content of the work unit file. With this information, Wwise can correctly load projects created from previous versions and migrate it towards the schema used by the current version.
Every new object created should have its own GUID value. To keep things simple, ShortIDs should all be set to a unique (arbitrary) value. Wwise will output warnings for these invalid values on the first project load but will be able to fix these to unique (valid) values. Note that avoiding warnings is possible if one wants to mimic the way Wwise generates ShortIDs through a hashing function but the above method frees you from understanding the details regarding this.
