Change to the Designer layout, select the Music Event in the Event Viewer and then drag the Combat Music Playlist Container to the first line in the Event Property Editor.

	You may be asked if you want to replace the Explore Music Playlist Container. If asked if you want to replace Explore with Combat, choose Replace.

Now you need to test that the Music Event is properly playing the Combat music; however, remember that earlier in this lesson you pinned the Transport Control view directly to the Combat Music Playlist Container. You need to unpin it and then go select the Music Event once again for it to be in the focus of the Transport Control.

Unpin the Transport Control view, select the Music Event in the Event View and press Play.

You now hear the Combat music playing, so you know the Music Event has been properly reassigned to play the Combat music. To contrast with what you saw when you integrated the Explore music, take a look at what Wwise is doing in the background to carry out your implementation by using the Profiler view.

Start a capture session, change to the Profiler layout and observe how the number of objects displayed in the Advanced Profiler view increases.

Notice how the Advanced Profiler view shows many more active objects, as there could be 10 or more playing unique tracks simultaneously. You may also notice that if a Random Step track chose one of the blank Sub-Tracks, it does not appear as an active object in the Voices Graph tab. This is because there is no volume on the track to exceed the minimum threshold necessary to be played.

Stop playback, change to the SoundBank layout, generate the Music SoundBank and play the Wwise-201 level in Cube!

You should feel a definite change to the vibe of Cube now with the new more aggressive music. You can see how powerful, yet simple, re-orchestration is. Now that you can see things from the implementation side, it will likely change how you think about composing music. Move on to Lesson 3 to start combining the concepts you've learned so far.