Wwise Help

Inclusion

Determines whether the element is included or excluded. When selected, the element is included. When unselected, the element is not included. By default, this applies across all platforms. Use the Link indicator (to the left of the check box) to determine or to set platform-specific customizations.

When this option is unselected, the property and behavior options in the Property Editor become unavailable.

Default value: false

Name

The name of the object.

Notes

Any additional information about the object properties.

Controls the Mute and Solo states for the object and shows the implicit mute and solo states for the object.

Muting an object silences this object for the current monitoring session. Soloing an object silences all the other objects in the project except this one.

A bold M or S indicates that the Mute or Solo state has been explicitly set for the object. A non-bold M or S with faded color indicates that the object's Mute or Solo state was implicitly set from another object's state.

Muting an object implicitly mutes the descendant objects.

Soloing an object implicitly mutes the sibling objects and implicitly solos the descendant and ancestor objects.

	Tip
	Hold the Ctrl key while clicking a solo button to exclusively solo the object for which the solo button is associated.

	Note
	Mute and Solo are designed to be used for monitoring purposes only and are not persisted in the project or stored in the SoundBanks.

Sets the display of the Property Editor's selected tabs. By default, there is one panel displaying only one selected tab. You can, however, click a splitter button to split the panel into two, either side by side or one on top of the other, for two different tabs. The currently selected option is highlighted with a background color.

	Note
	You cannot display the same tab in both panels. If you select the tab that is currently displayed in the other panel, then the other panel will automatically display another tab.

	Shortcuts for selecting tabs
	Press Ctrl and the number corresponding to the number of the Property Editor tab you want. For example, Ctrl+4 would select the RTPC tab if that were the fourth visible tab.

Stinger Settings

Click the Configure Columns... shortcut (right-click) option from the column header band.

The Configure Columns Dialog opens. Specify which columns to display and their order.

Trigger

The name of the Trigger being used for the current stinger.

Opens the selector menu where you can select the Trigger that will call the current stinger.

Segment To Play

The name of the Music Segment that will play when the Trigger Event occurs.

Opens the Project Explorer - Browser where you can select the segment that will play when the Trigger calls the stinger.

Play Segment At

Determines the point at which the Stinger will play. The following options are available:

Default value: Immediate

Custom cue match name

Determines which custom cues are eligible to be selected as the ‘Play At’ position. If no name is specified, any custom cue will match.

String comparison is not case-sensitive, but it must be exact (there is no wildcard).

This option can only be used when ‘Play At’ is set to ‘Next Cue’ or ‘Next Custom Cue’.

Name matching affects the selection of custom cues only; it has no effect on the eligibility of the entry or exit cues.

Adds a new row to the Stinger table where you can define the following:

the Trigger that will drive the stinger.

the Music Segment that will play.

the point at which the Music Segment will play.

Removes the currently selected Stinger and its associated components from the Stinger list.

Stinger Options

Don’t play this Stinger again for x seconds.

The number of seconds that must elapse before the Stinger can be used again.

If the Trigger calls this Stinger within the specified number of seconds, the Trigger is ignored or dropped. A message saying that the Stinger could not be played will appear in the Capture Log. Note that the “don’t play Stinger again for” time is relative to the stinger’s synchronization point, that is, the moment in time where the stinger’s entry cue occurs.

For example, say you have a segment with 1 second-long beats, which defines a Stinger that has a 1.5 second long pre-entry, a “next beat” synchronization rule, and a “don’t play Stinger again” property of 3 seconds. Imagine now that this segment is playing and that the cursor is precisely over a beat boundary when the Trigger is posted. Because of its 1.5 second long pre-entry, the stinger’s entry cue cannot be synchronized to the next segment’s beat, so it is synchronized to the next beat instead (that is, in 2 seconds). Consequently, all Triggers that will be posted for the next 5 seconds (2 seconds before synchronization time, plus 3 seconds of “don’t play again time”) will be dropped.

Furthermore, this time value is inclusive. For example, with a “don’t play again” time of 0, all Triggers are dropped until the synchronization point is reached, inclusively. It is thus impossible to have two or more Stingers scheduled precisely at the same time.

Default value: 0
Range: 0 to 3600

Allow playing Stinger in next segment (if applicable)

Determines whether this Stinger can be played in the next segment in the playlist. If a Stinger is called by a Trigger and the next opportunity to play the Stinger occurs too late in the current segment, the Stinger is not played. When you select this option, however, the Stinger will play at the first defined opportunity of the next segment in the playlist. The Stinger entry points are defined in the Play At field.

Default value: Yes