Frostune:VO supports two complementary Wwise workflows:
This workflow pushes content directly into Wwise Authoring using WAAPI.
Steps:
Open your Wwise project and make sure WAAPI is enabled.
In Frostune:VO, open the Export panel.
Select Wwise – WAAPI and TSV.
Either:
Result:
This is the fastest way to sync dialogue into Wwise during production.
When using Wwise localization, Frostune:VO uses short locale codes internally, such as en, fr, es, de, it, and pt.
However, Wwise does not use these short codes as language names. Wwise expects the actual language names configured in the Wwise Language Manager.
Before pushing localized dialogue to Wwise, make sure the required languages exist in Wwise using clear language names such as:
| Frostune:VO locale | Recommended Wwise language name | Other accepted names |
|---|---|---|
| English | English(US) |
English, English(UK) |
| French | French(CA) |
French(France), French |
| Spanish | Spanish(Spain) |
Spanish(Mexico), Spanish |
| German | German |
Deutsch |
| Italian | Italian |
Italiano |
| Portuguese | Portuguese(Brazil) |
Portuguese(Portugal), Portuguese |
Important: do not create Wwise languages named only FR, ES, DE, IT, or PT.
Those are Frostune:VO internal locale codes. In Wwise, use full language names such as French(CA), Spanish(Spain), or Portuguese(Brazil).
If Frostune:VO cannot find a matching Wwise language during a native localization push, it will report the available Wwise languages so the project can be corrected in the Wwise Language Manager.
Frostune:VO also supports Wwise-oriented workflows through the Custom Engines API.
This workflow does not push directly into Wwise Authoring. Instead, Frostune:VO exposes or exports a structured JSON manifest that can be consumed by a custom engine, proprietary pipeline, automation tool, or studio-specific Wwise importer.
The manifest can include Wwise-compatible routing hints such as:
This approach is ideal when:
In this workflow, Frostune:VO provides the structured data, filenames, scene metadata, speaker metadata, status information, and Wwise-compatible template fields. Your own pipeline decides how to create or update the final Wwise objects.
More details:
06_Custom_Engines_API