Writing

• New content is written or imported to Consequence.
• If in Needs Review status, it should be reviewed by a Writer and then set to Draft. Once reviewed by a Lead Writer, it should be set to Approved.
• Writing should be approved before it is recorded when possible in order to minimize downstream impacts of rewrites.
• Once you are ready to record your Approved lines, set them to Final to reflect that they should no longer be changed.

Exporting

• To export lines for a recording session:
  • Search for and bulk select all the lines you wish to record from the Write page.
  • Go to Data → Export Selected Lines - CSV to export to CSV.
  • This CSV can be used for the recording session, and includes the names that the resulting .wav files should be called (listed as engine_id).
• It's recommended that after you export lines to CSV for recording, you Bulk Edit them and update their Recording Status to Recording Scratch or Recording Final, depending on whether the recording is for temporary or final audio.

Recording

• Audio gets recorded, selects are made, the .wavs are cleaned up.
• The .wav files and Wwise events should be named according to the engine_id from the recording sheet, and the name of the Wwise events must end in _[0-padded UID], e.g. _001234. This will allow Consequence to associate the right events later.
• Ultimately the audio team imports the recorded .wav files into Wwise and to Perforce.
• Wwise events for each audio file must be created.
• You should have one .wav per Wwise event. In order for Consequence to support randomization between lines and display the correct subtitles, Wwise cannot also randomize within an event.
• Create the AkAudioEvent Uassets for the Wwise events in your Unreal project. They must be placed in a subdirectory of the location you selected as your Consequence Ak Event Parent Directory in the Engine Settings.

Update / Associating

• In the Engine, open the Consequence window and click the Update button to update your Consequence data.

• This Update / Import step associates all the latest Wwise events in your engine directory with the Consequence lines they relate to.

Syncing Audio in Consequence

• This step is not essential to triggering audio in Consequece, but it allows you to automatically update audio status in Consequence as lines become available.
• When you use Commands → Sync Audio, Consequence will sync the audio directory you specified in your Consequence Client setup.
• For any Consequence lines where a newly updated .wav file is found whose name ends in _[line UID], e.g. my_event_line_001234.wav, Consequence will try to update the Recording Status:
  • If the status was Unrecorded, it will be set to Scratch VO.
  • If the status was already Scratch VO, it will stay Scratch VO. The same for Final VO.
  • If the status was Recording Scratch, it will be set to Scratch VO. If the status was Recording Final, it will be set to Final VO.

Triggering

Consequence triggers audio in 2 ways, one of which is totally automatic, and the other of which requires some setup.

• Automatic Triggering in Consequence Conversations
  • When you trigger a dialogue event using Trigger Consequence Event or similar (see Trigger Events In Engine), if audio is available for a line, the Wwise event will be triggered for the appropriate actor. The conversation will wait for each line to complete before proceeding.
• Triggering in Sequencer
  • Add a Consequence Lines track to your Level Sequence.
  • In the header for the track, search for the Consequence event you need and click Add All Lines.
  • If you keep the audio box checked, you can simultaneously add the Wwise events that were associated as part of the Update process. This will only work if you have added the Wwise events to the engine and updated Consequence.
  • If you don't have audio yet you can add the Consequence Lines track first and then manually add the Wwise events later and align them to the subtitles (and adjust the subtitle length to match the final audio).