(Deprecated) ADTF GUI Control

This guide covers the functionality of the (Deprecated) ADTF GUI Control. After reading this guide, you will know:

Note that on different screens and resolutions (especially High-DPI) there might be some strange combinations regarding Qt/QML, OS and scaling, especially when moving applications like (Deprecated) ADTF GUI Control between screens with different resolutions. There is still no out-of-the-box solution to handle monitor dpi awerness by default. You can try to adapt OS scaling or starting (Deprecated) ADTF GUI Control with compatible mode options given by OS, sorry for that trouble. We will bring the same scaling options known by ADTF Configuration Editor from ADTF 3.7.0 to an upcoming version.

Available commands

Although the (Deprecated) ADTF GUI Control is a GUI application it still has some command line arguments.
Type: adtf_guicontrol.exe --help into a console to get the list of the supported commandline arguments:

The Start Screen

The GUI-Control offers two ways to control an ADTF launcher:

The recoder start screen

Run an ADTF Session locally

Click the "Open Session or Project" button to select an ADTF Session file (*.adtfsession) directly or a project file (*.adtfproject) to list all ADTF Session files contained in this project.

Open project file

Next select one of the available ADTF Sessions and click the Launch button. A dialog with start settings will show up. You can adopt the launcher command and the port the URL however should not be changed because it has no effect. The launcher is always started on the local PC and the URL is shown for convenience only.

Launch settings

Connect to Remote Session

If you want to control an already running ATDF launcher maybe on an other PC in the same network click on the "Connect to Session" button. A dialog will show up where you can specify the URL and port pointing to the remote ADTF Launcher. The ADTF Launcher must have been started something like this on another pc to listen on the public interface: adtf_launcher.exe -session="path/to/session.adtfsession" -control-url="http://10.10.10.36:8000" -console

Connect to remote

Tab Controls

As soon as the connection to the ADTF Launcher is established a new tab with the name of the running ADTF Session will show up inside the GUI-Control representing the new connection. Pressing the "X" on the tab header terminates the connection and optionaly shuts down the ADTF Launcher. The (Deprecated) ADTF GUI Control offers the same functionality as the ADTF Control but with a convenient graphical user interface. To make further connection you can switch back to the first tab with the name "Start" and repeat the preceding steps.
In the header section you can see some common information about the connected ADTF Launcher e.g. the loaded ADTF System, loaded ADTF Session and the currently active Streaming Graph and Filter Graph. Bellow you can find the buttons Shutdown, Init and Run to control the runlevel of the Filter Graph. Pressing the Run button starts the data flow through the Streaming Graph and Filter Graph.
Runlevel mapping between GUI-Control and ADTF Launcher:

Button Clicked Runlevel change within ADTF Launcher
Launch System
Init Filter Graph
Run Running
The "Player" and "Recorder" sections are only available if the loaded ADTF Session contains the "ADTFDAT File Player" or "ADTFDAT File Recorder" respectively. All file recorded with any of the Recorders are listed with in "Recorded Files".

This is waht the ADTF GUI Constrol looks like

The Player Control

The Player can handle ADTF3 DAT files (*.adtfdat) and, if a data type mapping is avaiable, ADTF2 DAT files (*.dat). The player enables the user to:
  1. Open a *.adtfdat/*.dat file
  2. Play a *.adtfdat/*.dat file
  3. Pause a *.adtfdat/*.dat file
  4. Step to next trigger in paused mode
  5. Enable/disable loop-mode
  6. Adapt playback speed
  7. Slide within the stream time

The Recorder Control

If the currently active Streaming Graph / Filter Graph (referenced in the running ADTF Session) has more than one ADTFDAT File Recorder each recorder gets it own control. Additionally one master control is added for convenience which drives all other recorders. The Recorder serves these functionalities:
  1. Start recording
  2. Stop recording
  3. Split recording
  4. Open marker dialog
  5. Add QuickMarker

A red button means recording a green button means ready to start recording. The recorded data goes into a DAT file. The DAT files can be split into several chunks by clicking the split button. The given name to a recoreded file is configured as property of the ADTFDAT File Recorder inside the Configuration Editor.

Marker

The GUI-Control offers two possibilities to mark important events during recording. On the one hand you can use Quick Markers to place a marker immediately with a default label and the current time. On the other hand you can use the marker dialog button to specify a name and adjust the timestamp.

The recoder and its buttons

Quick Marker

Click the Quick Marker button and a marker is set immediatly at the current stream time with the default marker name

Marker Dialog
  1. Click marker dialog button
    Marker dialog will open. 'Name' is set to default marker name. 'Position' is set to current stream time.

    Marker Dialog

  2. If necessary, change marker name
  3. If necessary, adjust marker position
    Accepted pattern: [hhh:]mm:ss
    For example:
    • 01:12:34
    • 1:12:34
    • 100:00:00
    • 23:42
  4. Click 'OK' Button
    Marker dialog will close and marker is set in DAT file.
Short Cuts

ctrl + 0 sets a QuickMarker for all recorders, note it is zero not the character 'O'

ctrl + m opens the marker dialog for all recorders

Recorded Files

All recorded DAT files are displayed in this table. Remember that the files are generated on the system where the ADTF Launcher was started which is not necessarily the ADTF System where the (Deprecated) ADTF GUI Control is running! Each row of the table offers a context menu:

Recorded Files

Where to go next?

Have a look at the ADTF Plugin Description Generator to understand how the information of the ADTF Components will be generated for e.g. ADTF Configuration Editor.