Media Server 24.1

# TimestampCondition

Specifies a time limit for matching records, based on the record timestamps. The time limit that you specify must place an upper bound on the `Input1` timestamp, relative to the `Input0` timestamp.

You can define the limit based on the following timestamps:

- `startT` - the start time of a record from track `InputT`
- `peakT` - the peak time of a record in track `InputT`
- `endT` - the end time of a record in track `InputT`

You can also include an optional time constant, for example `startT + 5s`. The units you can use are days (d), hours (h), minutes (m), seconds (s), milliseconds (ms), and microseconds (us).

The default value (`start1 <= start0`) specifies that the record in the Input1 track must start before or at the same time as the start time of the record in the Input0 track.

Type: | String
Default: | `start1 <= start0`
Required: | No
Configuration Section: | TaskName
Example: | With the following example, the record in the `Input0` track is combined with the latest record in the `Input1` track where the peak time of the `Input1` record occurs up to 5 milliseconds after the end time of the `Input0` record.
    TimestampCondition=peak1 < end0 + 5ms
In this case the "latest" record is defined as the record with the latest peak timestamp that matches the condition (using the peak timestamp for the `Input1` track means that the records are sorted by peak timestamp).
See Also: |

Copyright 2023 Open Text
Version 24.1 | Last updated December 2023

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: IDOL Media Server 24.1

Topic Title: TimestampCondition