Subkeys: Asubkeymeansa folder in the parameter files’ tree structure, shown in the DigaSystem Administrator.
Parameter level:
Subkeys (sometimes also called folders) and parameters can be located in three different parameter files (levels): The GlobalSettings, the Local Settings and the User Settings.
If the parameter level can be chosen at will, the parameter path is shown as e.g. …|Settings| (the three dots in the beginning),that indicate the Settings subkey of any parameter level.
Vertical bar (|) and parameter syntax
If the vertical bar, that separates the subkeys, appears at the end, then a subkey is meant, e.g. …|DigAIRange|Crossfade|Extra| - the Extra subkey in the Crossfade folder. Without the bar the manual refers to a parameter, e.g. …|DigAIRange|Crossfade|Extra|FadeInCurveType.
If a parameter value is pointed out or recommended it will be shown as Parameter=Value. As an example: UseOnAirTrackMixer=TRUE means, the parameter “UseOnAirTrackMixer” is (or should be) set to “TRUE”.
Variable <n>
The subkey variable <folder name> or just <n> means the parameter folder can have multiple names or there can be several folders of this type.
Default path
Parameters being listed without a reference path are always stored under:
|DigAIRange|Crossfade|Extra|
|TurboPlayer|GUI|Windows|CFM|[n]|Extra|
|DBM| further DBM parameters are defined within the OTMSettings parameter
Not default path
Other pathes than the default one are shown like this
Reference Path
"..|DigAIRange|Crossfade\Extra|AdvancedVoiceTracking|Ducking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|AdvancedVoiceTracking|Ducking"
OnAIR TrackMixer Parameters
The bold and underlined value is the default value. For DBM by design all parameters for recording, Multitrack actions or view i.e. crossfades or mostly all fade curve modification parameters are not applicable.
When an audio is ducked it will be lowered by %Amplification% dB in the ducking area.
"Amplification" is used for duck targets ducked by duck source audios and by audio segments from the recording.
Reference Path
"..|DigAIRange|Crossfade\Extra|AdvancedVoiceTracking|Ducking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|AdvancedVoiceTracking|Ducking"
"..|DigAIRange|Crossfade\Extra|StartNextAutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|StartNextAutoDucking"
AttackOffset
0...100000
150
AttackOffset in milliseconds for Start Next Auto-Ducking.
The "AttackOffset" will be used together with the "AttackTime", the "AttackThreshold" and the "ThresholdTolerance" to detect the start of an audio segment in the recording.
The %AttackOffset% ms offset will compensate for internal delays by the detection logic with a default value of 150 ms.
The %AttackOffset% ms offset is not needed to compensate for the %AttackTime% ms offset.
The %AttackOffset% ms offset can also be used to further correct the detected start position of an audio segment in the recording to the left or the right in the timeline.
Reference Path
"..|DigAIRange|Crossfade\Extra|StartNextAutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|StartNextAutoDucking"
AttackThreshold
-100.0...0.0
-30.0
AttackThreshold in dB for Start Next Auto-Ducking.
The "AttackThreshold" will be used together with the "AttackTime", the "ThresholdTolerance" and the "AttackOffset" to detect the start position of an audio segment in the recording.
The start of an audio segment in the recording is detected if the signal is above %AttackThreshold% dB for at least %AttackTime% ms and in at least %ThresholdTolerance% percent of the values
Reference Path
"...|DigAIRange|Crossfade|Extra|StartNextAutoDucking" or "...|TurboPlayer|GUI\Windows|CFM|1|Extra|StartNextAutoDucking"
AttackTime
0...100000
100
AttackTime in milliseconds for StartNext-Autoducking.
The "AttackTime " will be used together with the "AttackThreshold", the "ThresholdTolerance" and the "AttackOffset" to detect the start position of an audio segment in the recording.
The start of an audio segment in the recording is detected if the signal is above %AttackThreshold% dB for at least %AttackTime% ms and in at least %ThresholdTolerance% percent of the values.
Reference Path
"...|DigAIRange|Crossfade|Extra|StartNextAutoDucking" or "...|TurboPlayer|GUI\Windows|CFM|1|Extra|StartNextAutoDucking"
When auto-ducking: Amount of volume reduction in dB (negative values are used in the registry).
Remark: This parameter is only present in the user registry, it is only available when using OTM and you should always use the settings dialog of DigAIRange to change it!
When auto-ducking the fade down is executed over this period of time in milliseconds.
Remark: This parameter is only present in the user registry, it is only available when using OTM and you should always use the settings dialog of DigAIRange to change it!
When auto-ducking: fade down of the previous item is finished x milliseconds before the selected element starts.
Remark: This parameter is only present in the user registry, it is only available when using OTM and you should always use the settings dialog of DigAIRange to change it!
When auto-ducking the fade up is executed over this period of time in milliseconds.
Remark: This parameter is only present in the user registry, it is only available when using OTM and you should always use the settings dialog of DigAIRange to change it!
When auto-ducking: fade up of the following item is finished x milliseconds after the selected element ends.
Remark: This parameter is only present in the user registry, it is only available when using OTM and you should always use the settings dialog of DigAIRange to change it!
Reference Path
"...|DigAIRange|Crossfade|AutoDuckFadeUpAfter"
AutomaticZoomAllOut
0, 1
Enables or disables the new "Automatic Zoom All Out" feature. When enabled, the OTM timeline zooms out to display all audio when 3 or more audios are loaded. When disabled (old behavior), the timeline zooms to the default range.
CollapsePanes
TRUE, FALSE, 1, 0
Collapse Detail Panes:
TRUE - The panes "Marker Details" and "Show Overview" will collapse/expand, when the tracks are collapsed/expanded.
FALSE - The panes "Marker Details" and "Show Overview" will not change, when the tracks are collapsed/expanded.
CrossfadeTrack
True, False
Crossfade track for the fade in track of the crossfade:
True - Delete old fade in curve and create new fade in curve according to setting FadecurveType.
False - Leave the current fade in curve.
Reference path
"..|DigAIRange|Crossfade\Extra|CrossfadeFadeInParameters" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|CrossfadeFadeInParameters"
"..|DigAIRange|Crossfade\Extra|CrossfadeFadeOutParameters" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|CrossfadeFadeOutParameters"
DefaultMode
True, False
Modes for the fade in track of the crossfade:
True - Use the current play position to calculate the fade time
False - Use the FadeTime setting as the fade time
Reference path
"..|DigAIRange|Crossfade\Extra|CrossfadeFadeInParameters" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|CrossfadeFadeInParameters"
"..|DigAIRange|Crossfade\Extra|CrossfadeFadeOutParameters" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|CrossfadeFadeOutParameters"
DistanceOfFadePoints
0...5000
100
Defines the minimal distance in milliseconds, between any two adjacent fade points when volume is adjusted. This value is used to honour limitations of the play-out software or hardware which may not be able to process fade points that are too close to each other. Must be zero or a positive number not above 5000.
This restriction is applied for non-linear fade curves, as well when one of the ↑ or ↓ buttons is pressed (which in fact also creates a small fade).
"FadeUpBefore" is used for duck targets ducked by duck source audios and by audio segments from the recording.
Reference Path
"..|DigAIRange|Crossfade\Extra|AdvancedVoiceTracking|Ducking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|AdvancedVoiceTracking|Ducking"
"..|DigAIRange|Crossfade\Extra|StartNextAutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|StartNextAutoDucking"
FadeUpCurveType
Linear, Log1, Log2, LogMinus2
FadeUpCurveType of the ducking settings.
"FadeUpCurveType" is used together with "FadeUp" to define the form and size of the fade up part of the ducking curve.
"FadeUpCurveType" defines the form of the fade up curve.
The supported values are:
Linear - Creates a linear curve.
Log1 - Creates a Log 1 curve.
Log2 - Creates a Log 2 curve.
LogMinus2 - Creates a Log -1 curve.
Reference Path
"..|DigAIRange|Crossfade\Extra|AdvancedVoiceTracking|Ducking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|AdvancedVoiceTracking|Ducking"
"..|DigAIRange|Crossfade\Extra|AutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|AutoDucking"
"..|DigAIRange|Crossfade\Extra|StartNextAutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|StartNextAutoDucking"
GlueMarkInToLinkIn
When moving Mark In, Link In is moved together with Mark In. You still can move Link In without moving Mark In.
To activate in the Settings dialog
This function you need to activate in DigAIRange's and Turbo Player's setting dialog.
GlueMarkOutToLinkOut
When moving Mark Out, Link Out is moved together with Mark Out. You still can move Link Out without moving Mark Out.
To activate in the Settings dialog
This function you need to activate in DigAIRange's and Turbo Player's setting dialog.
HoldOffset
0...100000
150
HoldOffset in milliseconds for Start Next Auto-Ducking.
The "HoldOffset" will be used together with the "HoldTime" the "HoldThreshold" and the "ThresholdTolerance" to detect the end of an audio segment in the recording.
The %HoldOffset% ms offset will compensate for internal delays by the detection logic with a default value of 150 ms.
The %HoldOffset% ms offset is not needed to compensate for the %HoldTime% ms offset.
The %HoldOffset% ms offset can also be used to further correct the detected end position of an audio segment in the recording to the left or the right in the timeline.
Reference Path
"..|DigAIRange|Crossfade\Extra|StartNextAutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|StartNextAutoDucking"
HoldThreshold
-100.0...0.0
-30
HoldThreshold in dB for Start Next Auto-Ducking.
The "HoldThreshold" will be used together with the "HoldTime", the "ThresholdTolerance" and the "HoldOffset" to detect the end position of an audio segment in the recording.
The end of an audio segment in the recording is detected if the signal is below %HoldThreshold% dB for at least %HoldTime% ms and in at least %ThresholdTolerance% percent of the values.
Reference Path
"..|DigAIRange|Crossfade\Extra|StartNextAutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|StartNextAutoDucking"
HoldTime
0...100000
1000
HoldTime in milliseconds for Start Next Auto-Ducking.
The "HoldTime " will be used together with the "HoldThreshold", the "ThresholdTolerance" and the "HoldOffset" to detect the end position of an audio segment in the recording.
The end of an audio segment in the recording is detected if the signal is below %HoldThreshold% dB for at least %HoldTime% ms and in at least %ThresholdTolerance% percent of the values.
Reference Path
"..|DigAIRange|Crossfade\Extra|StartNextAutoDucking" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|StartNextAutoDucking"
LevelModification
0.5...5.0
1.0
Amount in dB by which the fade curve is increased or decreased when one of the ↑ or ↓ buttons is pressed. Decimal digits are allowed; a dot (fullstop, period) servers as decimal separator. Must be positive in the range of 0.5 to 5.0.
LevelModification in dB for leveling settings in AdvancedVoiceTracking Mode.
"LevelModification" is used together with "DistanceOfFadePoints" to define the size of the fade for level up/down.
The height in dB between the start and the end of the fade is %LevelModification% dB.
Reference Path
"..|DigAIRange|Crossfade\Extra|AdvancedVoiceTracking|Leveling" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|AdvancedVoiceTracking|Leveling"
Logging
<empty>
Within the OTMSetting parameter you can define the logging path.
Defines the threshold in dB by which OTM distinguishes between "low volume" and "high volume", in the context of the DUCK/UNDUCK key. The DUCK/UNDUCK key increases the volume to full (unducks) if the current fade curve is below this limit; it decreases the volume to the Amplification value, if the current fade curve is not below the limit. Although any negative value between -10.0 and -3.0 is allowed, you should define this parameter to be approximately one half of the Amplification value.
MinimumDuckLevel in dB for Leveling settings in AdvancedVoiceTracking Mode.
The "MinimumDuckLevel" controls the ducked state of the AdvancedVoiceTracking mode.
If the current duck level is below or at the same level of %MinimumDuckLevel% dB, the state is ducked.
In the ducked state the fade line and the duck symbol in the track header are shown in blue.
The ducked state can be reached with the level down shortcut(s) or with the duck shortcut(s).
Reference Path
"..|DigAIRange|Crossfade|Extra|AdvancedVoiceTracking|Leveling" or "..|TurboPlayer|GUI|Windows|CFM|1|Extra|AdvancedVoiceTracking|Leveling"
MinimumFadepointDistance
100...
Default 200
Minimum distance between automatically generated fade points in milliseconds.
MouseButtonRight
PausePlayback, None
Right mouse button behavior in OnAIR TrackMixer:
PausePlayback - Right mouse button pauses the playback. This is the default behavior of OTM.
None - Right mouse button does not pause playback.
For example: <MouseButtonRight>PausePlayback</MouseButtonRight>
MouseWheelUp
MoveWaveformToLeft, MoveWaveformToRight
Mouse wheel scrolling behavior in OnAIR TrackMixer:
MoveWaveformToLeft - Waveform is moved to the left for Mouse-Wheel-Up. This is the default behavior of OTM.
MoveWaveformToRight - Waveform is moved to the right for Mouse-Wheel-Up. This is the default behavior of most DAVID Applications
MoveFadepointsWithMarkpoints
1, 0, Yes, No,
If a Fade In / Out has been defined and you move the Mark In / Out points, the fade points will be moved together with the mark points.
Note: The behavior can be toggled holding SHIFT.
Reference Path
"User|xyz|DigAIRange|Crossfade" or "..|TurboPlayer|GUI|Windows|CFM|1|"
If DBM is configured to use OTM for editing mark/fade/link properties (i.e. "DBM/Crossfade/UseOnAirTrackMixer"=TRUE), then this parameter can be set to define an external XAML file, which will be used as a GUI template by OTM.
The full path name of the XAML file must be given. XAML example files are delivered with the OTM software package and are located in the folder "OtmAlternateGui".
Invalid since DBM version 4.8.7372.0, use xml parameter DBM|OTMSettings instead and define tag "MultiRecSkinfile" holding the path to the OTM xaml file.
OpenSelectedElement
0, 1
Controls which element is loaded after switching from multi-track into 1-track mode:
0 - the first element (i.e. the element from the top track of multi-track mode)
1 - the element that was originally loaded into OTM
When you drag one audio element into OTM, OTM (since version 1.3 or so) attempts to load a complete transition. With OpenSelectedElement=0, the first element of this transition is loaded into 1-track mode; with OpenSelectedElement=1, the element is loaded into 1-track mode that was dragged into OTM.
This parameter is only used for OTM versions 1.3.346.19 and higher patch levels, or 2.0.497.0 and above.
OTMSettings
XML string (empty as default)
Xml file providing OTM specific settings to DBM, e.g.
True - Output Fader is visible. This is the default behavior of OTM.
False - Output Fader is hidden.
PropertyTwoTrack
TRUE, FALSE, YES, NO
With this setting the used crossfade mixer - CrossfadeMixer version 2 or OnAIRTrackMixer - visualizes a sound file within two tracks in that way that begin and end of file near-overlap. This allows user to test fading.
This Parameter contains configurable Metadata that OTM will write for every recording (regardless of the recording mode). The format of the value is a list of XML segments.
Example:AudioString1
The admin is responsible for setting meaningful XML values and to spell them correctly according to the BCSTechManual. E.g. setting values that are critical to the BCS System (Time_Start, etc.) doesn't make any sense.
The parameter values are set on element creation and can be overwritten later on by the OTM.
As of version 2.2 it is possible to overwrite the "Title" field.
RememberZoomRange
0, 1
This parameter defines the behavior of the zoom level.
0: As before, the zoom level is reset to the configured default value for NextTransition/PreviousTransition command.
1: The zoom level is retained for NextTransition/PreviousTransition command.
This parameter controls if the Main-Element/Sub-Element button is shown in the Track Header:
NoTransitionChannels - the Button is shown if no Transition channels are configured in the BCS.
Always - the Button is always visible.
Never - the Button is never visible.
SkipbackAfterLinkoutSet
0 .. 10 ..
A time in second which is only used by OnAIR TrackMixer. It is the time, the soundhead is positioned back if the user sets the LinkOut during playout by pressing LinkOut button.
Note: Invalid since DBM version 4.8.7372.0, use xml parameter DBM|OTMSettings instead.
Reference Path
"..|DigAIRange|Crossfade\" or "..|TurboPlayer|GUI|Windows|CFM|1"
SourceEnvelopeType
Visible, Hidden, VisibleOutsideOfMarkInOut
Behavior of source waveform (without fading).
Volume changes such as fades/ducking are reflected at the waveform.
Hidden - The area before mark in and after mark out is completely hidden and fades/duckings reduce the height of the waveform. No gray waveform in the background.
Visible - New behavior: Gray waveform in the background of the entire audio. This is the default value.
VisibleOutsideOfMarkInOut - Behavior of CFM: Gray waveform before Mark-In and after Mark-Out. No gray waveform between Mark-In and Mark-Out.
StopPlaybackWhenSave
TRUE, FALSE
Stop the playback of the audio when the changes are saved.
TRUE: Stop the playback.
FALSE: Continue the playback.
ThresholdTolerance
Default value: 150
Possible values: 0...100000
AttackOffset in milliseconds for StartNext-Autoducking.
The "AttackOffset" will be used together with the "AttackTime", the "AttackThreshold" and the "ThresholdTolerance" to detect the start of an audio segment in the recording.
The %AttackOffset% ms offset will compensate for internal delays by the detection logic with a default value of 150 ms.
The %AttackOffset% ms offset is not needed to compensate for the %AttackTime% ms offset.
The %AttackOffset% ms offset can also be used to further correct the detected start position of an audio segment in the recording to the left or the right in the timeline
TransitionFlaggingClasses
Possible values: [class];[class];...
The main audio elements will be converted to sub audio elements, if the class is in this lis
TransitionFlaggingLength
integer from 0 to 100
default 30
Percentage criterion; audios shorter than this percentage of the longest loaded audio are set to "sub element" status during (semi-)automated flagging.
TransitionFlaggingMode
1, 2, 3, 4
Controls when audio elements are converted between main and sub elements. If transition channels are configured, this is the same as routing to main or transition channels.
1: Conversion runs after each change. The button in the control bar is hidden.
2: Conversion must be triggered manually by a click on the button in the control bar.
3: The button in the control bar toggles automatic conversion (like mode 1) on or off; initially automatic conversion is ON.
4: The button in the control bar toggles automatic conversion (like mode 1) on or off; initially automatic conversion is OFF.
Notes:
In modes 3 and 4, the button indicates the ON or OFF state.
Depending on whether or not transition channels are configured, the button has different appearance in modes 2, 3, and 4.
TransitionFlaggingRecording
Default, ForceOn, ForceOff
Default: The transition flagging logic respects class and length (as in release 2017.2.0)
ForceOn - OTM forcibly flags all recordings (identified by: Generator field equals "OTM" with Time_StartOnTransitionChannel=1. It also means recordings are always sub-elements and never main-elements.
ForceOff - OTM forcibly flags all recordings (identified by: Generator field equals "OTM" with Time_StartOnTransitionChannel=0
TransitionView
TRUE, FALSE, 1, 0
Only important elements in a transition are focused. Therefore a different visualization is applied for non-rundown elements that are not located in the middle of a transition.
Assuming a rundown that consists of several regular rundown elements and many transitions, it is key that OTM tries to load only a single transition. In order to not hide elements that are relative to the loaded rundown elements, but are not part of the transition currently being edited, these elements should also be loaded, but visualized differently.
TRUE - Activate feature
FALSE - Deactivate feature
UseForTransitions
TRUE, FALSE, Yes, No, 1, 0
With this flag you can declare a line to be a transition line. All elements belonging to a single transition can be played on this line. In other words: these elements are treated as a unit. The transition elements must be marked with the flag "Time_StartOnTransitionChannel". Enough channels must have been assigned to this line so that all elements of a transition which are intended to be played simultaneously can be played. For more information see TurboPlayer TechManual chapter "Concepts/Transition lines".
Although this parameter does not affect the way OTM works, it is important to understand its effect in relation to "sub elements". "Sub elements" are played out on transition channels if transition channels are correctly configured.
Reference Path
"...|TurboPlayer|Lines|Line-<m>"
UseOnAirTrackMixer
TRUE, FALSE
Enables OnAIR TrackMixer.
DBM V4: If not enabled, CrossfadeMixer will be used instead.
DBM V5: If not enabled, no crossfade tool is available