Skip to content

Music

Tip

Also see the guide on how to work with music!

For music sources it is often desirable to have more control over their playback, e.g. (cross) fades, stateful playlists, etc. This is realized through hierarchies of specialized music containers that lead into music segments and tracks.

Music Switch Container

Wwise documentation

Similar in purpose to SwitchContainers, however, they allow to use more complex decision trees that choose a child based on one or more multiple game_parameters. They also define transition rules between children. As the name implies, these are intended for transitioning between different music tracks.

Music Random Sequence Container

Wwise documentation

These are comparable to RandomSequenceContainers, but with the ability to define multi-layered playlists with different playback/randomization modes per layer. In addition, they allow to define transition rules for their children.

Segments & Tracks

Wwise documentation

Music containers will at some point lead into a MusicSegment node, which by itself only defines a fixed duration and a set of markers, e.g. loop points.

Each segment can contain one or more MusicTrack nodes, which will be played back in parallel and cut off once the segment duration has been reached. Music tracks can also have multiple sources, and depending on the track type, these will either be played in sequence or picked at random.

Note

Soundbanks have a size limit of around 90MB, so music tracks are almost always stored as (Prefetch-)Streaming sources.

Info

As far as I know, Fromsoft has never used more than one music track per segment, nor have I seen more than one source per music track; but it is nice to know what would in theory be possible.

Ko-fi donations