FMOD - Revision history

Imgettingpissedoff: /* General techniques - starting up. */

2009-11-11T15:42:15Z

‎General techniques - starting up.

BryanDerksen: /* Creating Events */ tidy up a couple of associated images

2009-07-19T23:52:24Z

‎Creating Events: tidy up a couple of associated images

BryanDerksen: add subheaders

2009-07-19T23:43:45Z

add subheaders

BryanDerksen: /* 4.0 ambiences and 3D placeable level emitter events. */ some more image formatting

2009-07-17T20:46:43Z

‎4.0 ambiences and 3D placeable level emitter events.: some more image formatting

BryanDerksen: /* Definitions and vocabulary - FMOD particulars */ shrink some big screenshots a bit

2009-07-17T19:25:15Z

‎Definitions and vocabulary - FMOD particulars: shrink some big screenshots a bit

BryanDerksen: Category:Sounds

2009-07-02T12:03:54Z

Category:Sounds

BryanDerksen: imported from extranet

2009-06-27T18:18:21Z

imported from extranet

Show changes

@@ Line 37: / Line 37: @@
 === General techniques - starting up. ===
-When you begin to create and FMOD project there are certain steps to follow in order to get you project up and running.
+When you begin to create an FMOD project there are certain steps to follow in order to get your project up and running.
 <U>Step 1-</U> create a new project on your local DA directory.
@@ Line 53: / Line 53: @@
 Please note that all folder names are lower case and have spaces represented by underscores.
-<U>Step 3-</U> open new FMOD project and delete untitled event that FMOD creates and save the project.
+<U>Step 3-</U> open your new FMOD project and delete the untitled event that FMOD creates by default and save the project.
 [[Image:DA_Audio_Design_Documentation_Ambience_Content_html_1a3044b1.png|frame|center|Erase this.]]
-<U>Step 4-</U> click on Sound Definitions page and you are ready to bring audio into FMOD.
+<U>Step 4-</U> click on the Sound Definitions page and you are ready to bring audio into FMOD.
 === Folders and subfolders - setting up audio for FMOD. ===

@@ Line 229: / Line 229: @@
 Upon selecting “add event”, you will be prompted to name the event and select a template if desired. We are not using templates in DA level design projects as they have proved to be too problematic and confusing. All sound designers must learn how to create events from scratch, although you can copy and paste similar existing events that suit your needs. If you do use a template to create you event, the sound designer must remember to deselect the template used in the “Use template” field, otherwise you will not be able to edit the event.
-[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_11d9d743.png]] [[Image:DA_Audio_Design_Documentation_Ambience_Content_html_3217d88b.png]]
+{|
+|-
-<I><B>New event named for same sound definition.</B></I>
+| rowspan="2"| [[Image:New FMOD event dialogue.png]]
 All events should be named the same as the sound definition they contain. If the events are using multiple sound definitions then name them appropriately.
 ==== Creating the 3 main event types ====

@@ Line 239: / Line 239: @@
 ==== Creating the 3 main event types ====
-. <U>4.0 ambience event-</U> these events are meant to be used as assigned sounds to an audio volume, they will play in 4.0 and will either just cross-fade at the edges of the volume or cross-fade in volume and change from 2D to 3D, which will be explained more fully in part ii) of this chapter.
+===== 4.0 ambience event =====
 Upon creating the event itself, we are ready to make it into a 4.0 ambience looping event, as follows:
@@ Line 355: / Line 357: @@
 This curve represents the usual 5 meter volume roll-off for the 4.0 ambience. You can add other effects as desired in the same fashion. The event can be monitored by pressing the “play” button and the effect of your parameters over distance can be monitored by grabbing the red cursor and dragging it left to right.
-. <U>3D Placeable event-</U> these events are designed to be placed as directional emitters in the level and serve the purpose of enabling the sound design for point source ambient sounds or environmental VFX in the level such as fires, waterfalls and other similar sound effects. They are designed to be completely directional or can become more or less 4.0 over distance.
+===== 3D Placeable event =====
 The events are created in this fashion, we’ve already discussed the basics in the previous chapter and all events start out the same way, it’s just what parameters you assign to them that determine how they behave.
@@ Line 377: / Line 381: @@
 [[Image:DA_Audio_Design_Documentation_Ambience_Content_html_1b9ac367.png]]
-. <U>3D area effect event-</U> these events are purely 3D events that are placed as emitters on the map to provide an area, or “umbrella” effect for one shot sounds such as birds, dogs or ambient thunder. These events are set up in the sound definition to randomize in volume, pitch and 3D position and when placed will play the one shot sounds in this fashion.
+===== 3D area effect event =====
 The event creation, as before is similar to all events except for two factors, the first being the 3D pan level value and the event layer parameters itself, as follows:

@@ Line 107: / Line 107: @@
 Two main types of event can be created to design sound for the levels in DA. These main types are 4.0 ambiences or 3D placeable events. The 4.0 ambiences are used for expressing sounds like air tones, winds or any other sounds that you will assign to play in an audio volume in the area editor. These sounds will play in 4 speakers, the Left and Right front speakers and the Left and Right rear speakers. These sounds will not specialize but can be either constant loops or spawned sounds that spawn over time or used as loops.
-A typical 4.0 event is shown below:
+[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_m78db5ae3.png|thumb|center|600px|A typical 4.0 event]]
-−
 [[Image:DA_Audio_Design_Documentation_Ambience_Content_html_m78db5ae3.png]]
 These events will need to be created as 3D events, as they have elements of 3D positional sounds. Although these sounds play as 4.0 within a defined space, their edges can be made to be 3D positional. The event above defines an example the volume and 2D-3D roll-off at the edge of the volume. If desired, the event will now be increasingly 3D to 2 meters and totally 3D after that. This is a typical exterior event with a roll-off of 5 meters, interior event roll-offs will usually be no more than 2 meters as the sounds will bleed room to room if it’s any bigger.
@@ Line 117: / Line 115: @@
 or created as an area effect wherein the sounds will randomize position and volume, such as birds, dogs or distant thunder, as seen as the second example below:
-A typical directional 3D event:
+[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_4084754f.png|thumb|center|600px|A typical directional 3D event]]
-−
-[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_4084754f.png]]
-−
-A typical 3D area effect event:
-[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_5d15187.png]]
+[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_5d15187.png|thumb|center|600px|A typical 3D area effect event]]
 There are certain ways to set up sound definitions and events both 4.0 and 3D placeable sounds. This will be explained in detail in the “c) Event setup and convention” chapter of this document.

@@ Line 13: / Line 13: @@
 . [[Image:FMOD event editor label.png]] on this page you will edit the event itself. In here you assign sound definitions, create layers and assign control parameters to the event, as seen below.
-[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_4084754f.png]]
+[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_4084754f.png|thumb|none|600px]]
 . [[Image:FMOD sound definitions label.png]] this is the directory for all of the audio files that will be called in events. They can be single audio files that play once or loop, or multiple files that you want to behave in a certain way based on the parameters for the sound definition. Within the sound definition you can define behavior parameters, as seen below:
-[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_47ac008a.png]]
+[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_47ac008a.png|thumb|none|600px]]
 These parameters will define the behavior of the audio file in the event you assign it too. When creating audio assets for the game and updating existing ones, the sound designer will usually start here.
@@ Line 23: / Line 23: @@
 . [[Image:FMOD wave banks label.png]] this is the function of FMOD that controls the data portion of the audio assets in the project. In here you will create a bank that contains audio files that you want treated a certain way, mainly for optimization and data compression schemes. All audio files in the project will be contained in a bank and these are what are built when you build the project for use in the game. This bank build creates a .fev (event information) and .fsb (sample bank (audio) information) files that you will copy to your override folder and is read by the game, as seen below:
-[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_600b0549.png]]
+[[Image:DA_Audio_Design_Documentation_Ambience_Content_html_600b0549.png|thumb|none|600px]]
 Wave banks are automatically created when you import audio into FMOD. They need to be manually conformed to naming standards and what properties they will contain.

← Older revision		Revision as of 12:03, 2 July 2009
Line 496:		Line 496:

	The optimization slider operates within a range of sample rate frequencies from 100%, which is the sample rate that the audio file is brought in at, in this example 48 kHz, to 4 kHz. Sound designers are encouraged to only use sample rates that are even numbers, i.e. 44 kHz, 32 kHz, 24 kHz, 16 kHz, etc. you will then be able to monitor the change in sample rate by clicking the play button and selecting the best result.		The optimization slider operates within a range of sample rate frequencies from 100%, which is the sample rate that the audio file is brought in at, in this example 48 kHz, to 4 kHz. Sound designers are encouraged to only use sample rates that are even numbers, i.e. 44 kHz, 32 kHz, 24 kHz, 16 kHz, etc. you will then be able to monitor the change in sample rate by clicking the play button and selecting the best result.
		+
		+	[[Category:Sounds]]