This section details the authoring workflow in CRI Atom Craft, as depicted by the diagram below.
Here is an overview of the workflow:
The first task is to create is a project (one project per game).
Work Unit is a file that collectively manages CueSheets and audio materials.
You can create multiple Work Units, allowing you to manage each work contents or each person in charge.
It is convenient when you are working on a team for the same project.
However, even if there is only one person working on the project, you still need at least one Work Unit.
In order to be able to create encoded data based on the original waveform files, they must be regitered as Materials.
Create a CueSheet that will use the registered waveform files.
The binary CueSheets are the files that are loaded by the game.
After converting the waveform files, you can adjust several playback parameters in the tool.
This combination of waveform data + playback parameters is called a Cue. A Cue can play several waveforms, using different behaviours.
The simplest Cue has a single Track with a single waveform.
The Cues are stored in CueSheets.
You can use the preview feature to play the Cues within the tool.
Multiple waveforms and playback parameters are packed together and converted to binary CueSheets.
Integrate the data of the CueSheets (acb files) and the global settings (acf file) into the game.
When the game is being modified or you want to adjust the sound parameters, you can use the in-game preview feature to modify the audio data while running the game.
Unlike the preview done by the tool, since the playback comes from the game, it gives a better idea of the final result.
It is possoble to investigate issues and find potential optimizations by checking the project with the profiler.
During the audio implementation for your game, repeat steps 2 through 10 as required.