ADTF
3.14.2
|
The Playback Service plays back .adtfdat Files recorded with the ADTFDAT File Recorder.
Plugin Filename | adtf_playback.adtfplugin |
---|---|
Plugin Description | adtf_playback.plugindescription |
Plugin Name | Playback Service Plugin |
License | ADTF |
Support Mail | support@digitalwerk.net |
Homepage URL | https://support.digitalwerk.net/ |
Plugin Version | 3.14.2 |
---|---|
Plugin File Version | 1.0 |
adtf | 3.14.2 |
adtf::ucom | 3.1.0 |
Name | Playback Service |
---|---|
CID | playback.service.adtf.cid |
Description | Use this System Service to extend the ADTF System with playback support for ADTF 3.x .adtfdat and ADTF 2.x .dat files. |
Type | Service |
Default Runlevel | system |
Name | Value | Type | Description | Subproperties |
---|---|---|---|---|
emulate_clocks | true | tBool | If enabled, clocks recorded in the files will also be emulated during playback. | |
extract_attached_files_from | cFilenameList | A semi-colon separated list of ADTFDAT files that the attached files should be extracted from during service initialization. | ||
extraction_destination_directory | cFilepath | The directory where all attached files should be extracted to. | ||
ignore_open_errors | false | tBool | if enabled, files that can not be opend are ignored. | |
ignore_unknown_classes | false | tBool | If enabled, playback will continue even in case it cannot find the deserializer implementation of one ore more streams. | |
interpolate_stream_time | false | tBool | When enabled the stream time will continue to go forward between two playback items being sent. Otherwise the time will be increased in discrete steps. | |
load_referenced_files | true | tBool | if the property is set, additional files referenced in the current playback file are loaded as well. | |
loop_mode | 0 | tUInt32 | Whether or not and how playback should be restarted when the end of all streams is reached. | Value List: do not loop = 0 seek to start = 1 change runlevel = 2 |
maximum_playback_thread_count | 1 | tUInt32 | Specifies the maximum number of threads that should be used for playback. If this is not equal to 1, multi threaded playback will be used. Keep in mind that the order of samples is non-deterministic in this case! Note that you have to set interpolate_stream_time = True and emulate_clocks = False in this setup. A value of 0 means that as many threads as possible will be used for the current set of files. | |
playback_clock_mode | 0 | tInt32 | Whether or not the playback clock should advertise itself as a system clock. This is relevant for Sync2Ref handling during playback. Auto-detect tries to make a guess based on timestamp size and clock names. | Value List: auto detect = 0 system clock = 1 independent clock = 2 |
playback_filenames | cFilenameList | The list of files (semi-colon) that should be played back. This might be overriden by the Playback Input Source. | Filename Extension Filter: ADTF DAT files (*.dat *.adtfdat),All files (*) | |
playback_speed | 1.000000 | tFloat32 | The playback speed factor: e.g. 0.5 = half the playback speed, 4 = four times faster. | |
read_ahead_queue_length | 1000000 | tUInt64 | The time span (us) that the read thread will contineously read form the file in advance. | |
runlevel_after_end_of_streams | 4 | tInt32 | If the property is != -1 then the service will decrease the runlevel to this value after the end of all streams has been reached. Note that it will never increase the runlevel based on this property. | Value List: none = -1 Filter Graph = 4 Streaming Graph = 3 Session = 2 System = 1 Shutdown = 0 |
try_realtime_playback | true | tBool | If this property is true, the hardware clock of the host will be used to determine when a sample/trigger should be sent. Otherwise the player will simple sleep for the time difference between to playback items. This is usefull when using a debugger. |
IID |
---|
reference_clock.osborn.streaming.adtf.iid |
kernel.devil.services.adtf.iid |
adtf_file_objects.devil.services.adtf.iid |
IID |
---|
playback_service.services.adtf.iid |
player.ant.services.adtf.iid |
player.bat.services.adtf.iid |
player.elasto.remote.adtf |
The Playback Service will register itself as the time source for the ADTF Stream Time at the Reference Clock Service. (see Offline Mode (Playback)). Any other component will work with this simulated time. Thus there can be only one ADTFDAT File Player in the current Streaming Graph and Filter Graph.
To create a Streaming Source for a Player instance within your Streaming Graph / Filter Graph to provide the Samples, use the ADTFDAT File Player.
The Playback Service supports playback of multiple .adtfdat Files and will always play back the recorded Samples in correct relation and timestamps compared to recording. This is not only mandatory to guarantee that the Offline Mode (Playback) is equal to to the Online Mode (Live) during recording, it also required when loading several .adtfdat files at once. These are the possible options for simultaneously playback of multiple .adtfdat files:
In both cases, ADTF will merge all files together and plays each Sample according to its timestamp.
The delivered service implementation follows the interface definition of adtf::services::ant::IPlayer.
The Playback Service can be control from any instance. It will not react on or result in a runlevel change of the system! See ADTFDAT File Player for controlling.
The control interface is delivered within your installation:
See adtf::services::ant::IPlayer for interface documentation.