Blog homepage

Using Templates in Wwise

Wwise Tips & Tools

WwiseTemplates_01.png 

Like many tools in a game developer's toolbox, Wwise is a deep, complex program with documentation longer than most novels. Who has time to read through entire documentation these days? I wanted to show off a simple, often overlooked feature in Wwise, which may not be readily apparent to someone who hasn’t read the manual. The ability to import a folder structure and apply a Wwise structure as a template to it can save a ridiculous amount of time when setting up structures in your project that may have a similar layout to other ones already in your project. With a little forethought and a few mouse clicks, the process of setting up complex structures in Wwise becomes an automated dream.

To start, let’s say we have a series of impact sounds which blend between soft and hard impacts based on the force of the impact and an additional layer of bounce sweeteners which only play above a certain force. We also do some filtering and pitch randomization based on the force and hardness of the objects colliding (via an RTPC). This is organized in Wwise as a Blend Container with some child Random Containers, which each contain audio files:

 Wwise_template_blend_container_layout-1024x472.png

 

Now, let’s start thinking about each of these structures as a folder. If we want to use this structure layout elsewhere in Wwise, we can “rebuild” or emulate this structure layout in Windows using folders. Where we have structures in Wwise (the Audiokinetic nomenclature for containers, Actor-Mixers, Virtual Folders, and so on) we create folders in Windows, which will serve as a guide for Wwise when we import new sounds. A Windows folder-based layout mirroring the impact structure above would look something like this:

 

3-_PC_folder_layout_02.png

 

Similar to the Blend Container in the Wwise example above, we have a “master folder,” in this case obj_sheet_metal_impact, which contains three folders: bounce, impact hard, and impact soft. And within each of those folders are corresponding WAV files. With a folder structure in Windows that mirrors the structure we want in Wwise, we can import it into Wwise—complete with all of our bussing, RTPCs, crossfades, and so on created for us! (As an aside, I always build my folder structures directly in the Originals folder so that the organization is already in place without having to move WAV files and folders around as an extra step in the File Manager.)

Once your folders are laid out in a similar manner to your Wwise hierarchy, open the Audio File Importer in Wwise and click the “Add Folders” button. Navigate to the top-level folder of your new structure, in my case “obj_sheet_metal_impact,” and click “Select Folder.” This will open that folder in the Audio File Importer. You can now assign each folder level as a different structure in Wwise, such as a Random, Sequence, or Blend Container. The magic, however, happens when we click the arrow in the Template column and select “Browse,” then navigate to an existing sequence whose layout and parameters we want to emulate:

 

4-_Wwise_template_layout-1024x657.png

 

As you can see above, Wwise automatically fills in which structure each folder should represent and even handles having more (or less) audio assets in a folder. Shuffle things around as needed, then click Import and you’ll have a new structure mirroring the template structure complete with all RTPCs, crossfades, and other structures.

 

5-_Wwise_template_blend_container_new-1024x487.png

 

Once we import the folder structure using an existing structure in Wwise as a template, we’re then free to tweak it to our hearts’ (or games’) content; but, most of the grunt work has been taken care of through some simple folder organization. Happy templating!

 

 

 Article originally published on Designing Sound

 

Bradley Meyer

Audio Director

Sucker Punch Productions

Bradley Meyer

Audio Director

Sucker Punch Productions

Audio Director and sound designer with 18+ years of experience in game sound design, systems design, scripting and integration, voiceover direction, and more.

 @AuralSurgeon

Comments

Tom Todia

September 07, 2016 at 03:35 pm

Great post Brad, I am going to have to try this out right away.

Leave a Reply

Your email address will not be published.

More articles

How to get a hold on your voices -  Optimizing for CPU (PART 1)

It is pretty common for any project to experience performance issues at some point during the course...

15.8.2017 - By Mathieu Jean

Image Source Approach to Dynamic Early Reflections

In our previous blog, Simulating dynamic and geometry-informed early reflections with Wwise Reflect...

14.11.2017 - By Thalie Keklikian

Wwise 2017.2 is now live!

We’re excited to announce that Wwise 2017.2 is now live! Below, a short-list of what’s new in Wwise...

8.1.2018 - By Audiokinetic

New Features with Wwise State-based Mixing - All the Parameters!

Wwise 2017.2 is out, and amidst a lot of great improvements and under-the-hood optimizations, an...

13.2.2018 - By Bradley Meyer

The Wwise-251 Certification comes to the rescue! 

With the Wwise-101 and Wwise-201 certifications, you learnt how to build fantastic interactive audio...

21.3.2018 - By Simon Ashby

The Making of SoundSeed Grain

We have wanted to build a general purpose granular synthesizer for Wwise for a very long time due...

11.12.2018 - By Louis-Xavier Buffoni

More articles

How to get a hold on your voices -  Optimizing for CPU (PART 1)

It is pretty common for any project to experience performance issues at some point during the course...

Image Source Approach to Dynamic Early Reflections

In our previous blog, Simulating dynamic and geometry-informed early reflections with Wwise Reflect...

Wwise 2017.2 is now live!

We’re excited to announce that Wwise 2017.2 is now live! Below, a short-list of what’s new in Wwise...