In the first four lessons, you’ve learned how to use both sequential and layered approaches to create music that dynamically changes. Thus far, this dynamic change has been driven primarily by randomization. For music to be interactive, something the player is doing in the game should drive decisions about how the music sounds. This could be that when a player scores a goal, celebratory music is heard; and when a driver accelerates, guitars roar with the car’s motor; or when a certain wand is held, its unique theme is played.

For the game to have this kind of interactivity, game calls delivered from the game engine to Wwise need to be tied into the music system. The game calls can be conventional calls such as Events, Game Parameters, Switches and States, or specialized calls designed specifically for music applications called Triggers. Different types of calls can act on the music in different ways, so you’ll explore a few different ideas for tying the game play within Cube to the musical score that accompanies it.

	Be sure to use the Interactive Music Layout (press F10) to make it easier to follow the Lesson 5 steps.