Playback View

The Playback view records in-flowing data to a playback file, and plays the captured data back into a running Event Stream Processor instance. You can also use it in place of the File Upload tool to upload data files at a controlled rate.

Playback View Options
Feature Description
Select playback file Select file format to use with Event Stream Processor recorder.
Start playback Starts playing the current playback file.
Stop playback Stops playback or record, closes the associated file and closes the associated playback or record context.
Start Recording Prompts user to select the file in which to store recorded data and starts Event Stream Processor recorder
At timestamp rate This slider is used during playback to vary the rate of playback
Playback Mode Options
Feature Description
Full rate Full rate indicates that the speed of playback is not imposed by ESP Studio. Full rate is dependent on factors such as the computer that is running ESP Studio, or network latency.
Timestamp column

The Timestamp column option tells the recorded file to play back using the timing rate information from a specified column. You must complete the Timestamp column to use it. During playback, timestamps determine the time interval between records.

If you check Use Recorded Time, the playback file runs as if it is the time when the data was recorded. Otherwise, the playback file uses the current time and plays as if produced now.

Rec/ms The records-per-millisecond (rec/ms) mode lets playback occur at a records per millisecond rate. The option allows you to set an initial rec/ms rate that you can then modify using the At timestamp rate slider tool.
The ESP Studio Recorder supports these file formats:
  • .xml (ESP XML)
  • .csv (comma-separated values)
  • .bin (ESP Binary)
  • .rec (ESP Studio recorded file)

Refer to the Supported File Formats topic for details.

Event Stream Processor records in .rec format, preserving the original timing of the incoming data.
Note: Binary messages are architecture dependent. Binary messages created in a big-endian machine cannot be loaded into an ESP server running in a little-endian machine, and vice-versa.