Users Guide to FlightGear sound configuration
-Version 0.7.10, Mar 02 2002
+Version 0.7.11, apr 27 2002
Author: Erik Hofman <erik@ehofman.com>
This document is an attempt to describe the configuration of
allowing for configuration of the sounds via XML to address this
limitation.
-About The Property Manager:
---------------------------
-The
-
Sound Architecture:
------------------
All of the sound configuration files are XML-encoded* property lists.
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
- <property>/engines/engine/running</property>
+ <condition>
+ <property>/engines/engine/running</property>
+ </condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
< ... >
This is the event seperator. The text inside the brackets
can be anything. Bit it is adviced to give it a meaningfull name
- like:
- crank, engine, rumble, gear, squeal, flap, wind, stall or click.
+ like: crank, engine, rumble, gear, squeal, flap, wind or stall
The value can be defined multiple times, thus anything which is
- related may have the same name.
+ related may have the same name (grouping them together).
<name>
This defines the name of the event. This name is used internally
and, although it can me defined multiple times in the same file,
- should have a unique value unless you realy know what you're doing.
+ should normally have an unique value.
- Defining it multiple times could lead to unexpected behaviour.
+ Multiple definitions of the same name will allow multiple sections
+ to interfere in the starting and stopping of the sample.
+
+ This method can't be used to controll the pitch or volume of the
+ sample, but instead multiple volume or pitch section should be
+ included inside the same event.
+
+ The types "raise" and "fall" will stop the playback of the sample
+ regardless of any other event. This means that when the type "raise"
+ is supplied, sample playback will stop when the event turns false.
+ Using the type "fall" will stop playback when the event turns true.
+
+ IMPORTANT:
+ If the trigger is used for anything else but stopping the sound
+ at a certain event, all sections with the same name *should* have
+ exactly the same sections for everything but property and type.
+
+ In the case of just stopping the sample at a certain event, the
+ sections for path, volume and pitch may be omitted.
<path>
This defined th path to the sound file. The path is relative to the
FlightGear root directory but could be specified absolute.
+
+ <condition>
+ Define a condition that triggers the event.
+ For a complete description of the FlightGear conditions,
+ please read docs-mini/README.conditions
+
+ An event should define either a condition or a property.
<property>
Define which property triggers the event, and reffers to a node
- in the FlightGear property tree.
-
- The value is converted to an integer value (anything less than 0.5 is
- is considered to be 0) and handled if it were a boolean value
- (0 = false, anything else = true).
-
- The triger depends on the value of <type>.
-
- <type>
- This specifies how the event is triggered.
- There are multiple options:
-
- level: events are active if the value is true.
- this is the default behaviour.
-
- inverted: events are active if the value is false.
-
- flipflop: events are triggered on state changes.
- this is only usefull for samples which are played
- once.
+ in the FlightGear property tree. Action is taken when the property
+ is non zero.
+
+ A more sophisticated mechanism to trigger the event is described
+ in <condition>
<mode>
This defines how the sample should be played:
looped: the sample plays continuesly,
until the event turns false.
-
+
+ in-transit: the sample plays continuesly,
+ while the property is changing its value.
<volume> / <pitch>
Volume or Pitch definition. Currently there may be up to 5
volume and up to 5 pitch definitions defined within one sound
- event. Normally all <offset> values are added together and the
+ event. Normally all offset values are added together and the
results after property calculations will be miltplied.
- A special condition occurs when the <factor> value is negative,
+ A special condition occurs when the value of factor is negative,
in which case the offset doesn't get added to the other offset values
but instead will be used in the multiplication section.
<property>
Defins which property supplies the value for the calculation.
+ Either a <property> or an <internal> should be defined.
The value is treatened as a floating point number.
+
+ <internal>
+ Defins which internal variable should be used for the calculation.
+ The value is treatened as a floating point number.
+ The following internals are available at this time:
+
+ dt_play: the number of seconds since the sound started playing.
+
+ dt_stop: the number of seconds after the sound has stopped.
<type>
+ Defines the function that should be used upon the property
+ before it is used for calculating the net result:
+
lin: lineair handling of the property value.
this is the default.
ln: convert the property value to a natural logarithmic
- value before scaling it.
+ value before scaling it. Anything below 1 will return
+ zero.
log: convert the property value to a true logarithmic
- value before scaling it.
+ value before scaling it. Anything below 1 will return
+ zero.
+
+ inv: inverse lineair handling (1/x).
+
+ abs: absolute handling of the value (always positive).
+
+ sqrt: calculate the square root of the absolute value
+ before scaling it.
<factor>
Defines the multiplication factor for the property value.
<min>
Minimum allowed value.
This is usefull if sounds start to sound funny. Anything lower
- will be converted to 0.
+ will be truncated to this value.
<max>
-
Maximum allowed value.
This is usefull if sounds gets to loud. Anything higher will be
truncated to this value.
+
+ <position>
+ Specify the position of the sounds source relative to the
+ pilot's ears. The coordinate system used is a right hand
+ coordinate system where -X = left, +X = right, -Y = down, +Y =
+ up, -Z = forward, +Z = aft. Distances are in meters.
+
+ <x>
+ X dimension offset
+
+ <y>
+ Y dimension offset
+
+ <z>
+ Z dimension offset
+
+ <reference-dist>
+ Set a reference distance of sound in meters. This is the
+ distance where the gain/volume will be halved. This can be
+ useful for limiting cockpit sounds to the cockpit.
+
+ <max-dist>
+ Set the maximum audible distance for the sound in meters.
+ This can be useful for limiting cockpit sounds to the cockpit.
+
+
+Creating a configrationfile:
+---------------------------
+
+To make things easy, there is a default falue for most entries to allow a
+sane configuration when a certain entry is omitted.
+
+Default values are:
+
+type: lin
+factor: 1.0
+offset: 0.0 for volume, 1.0 for pitch
+min: 0.0
+max: 0.0 (don't check)
+
- Calculations are made the following way
- (function can be one of: none, ln or log ):
-
- if (scale < 0) {
- value[i] = offset[n] - abs(scale[n]) * function(property[n])
- offset[i] = 0;
- } else
- value[i] = scale[n] * function(property[n])
+Calculations are made the following way (for both pitch and volume):
- And the end result will be:
-
- result = offset[0..max] + value[0..max];
-
+ value = 0;
+ offs = 0;
+ for (n = 0; n < max; n++) {
+ if (factor < 0)
+ {
+ value += offset[n] - abs(factor[n]) * function(property[n]);
+ }
+ else
+ {
+ value += factor[n] * function(property[n]);
+ offs += offset[n];
+ }
+ }
+ volume = offs + value;
+where function can be one of: lin, ln, log, inv, abs or sqrt
projects / flightgear.git / blobdiff