A tool to analyze audiovisual experiment recordings and transcripts Jens Lammert jens.lammert@st.ovgu.de 2012 2013 Otto-von-Guericke Universität Magdeburg The following document illustrates how to install, configure and use the Experiment Player to analyze experiments.

https://github.com/rhaberkorn/experiment-player

http://sourceforge.net/projects/exp-player/

To install the Experiment Player on a Windows-based operating system, the GTK+ 2 widget toolkit must first be downloaded and installed. A convenient GTK+ installer can be downloaded from the "GTK+ for Windows Runtime Environment Installer" project page. It is only necessary to install the GTK+ runtime. Additional themes may be installed as well - but the default GTK+ theme should be sufficient. Precompiled Windows 32-bit binaries of the Experiment Player itself are available as ZIP archives from the Sourceforge project page. The ZIP archive merely has to be extracted somewhere. Afterwards the included experiment-player.exe can be executed. All library dependencies except GTK+ are included in the ZIP archive.

To install the Experiment Player on a Linux-based operating system, it first has to be built from source. It can either be built from a local Git repository clone, or from a source code package that can be downloaded from the project's download archive on Sourceforge. In either case, further build instructions are given in the included INSTALL file.

After startup there will be two windows, a player window and a data window. They are explained in the following sections.

Player Window after startup The image above depicts the player window after startup. No experiment is yet opened in the application, so several controls are greyed out. Experiments can be opened via the File menu or the Quick Open menu. The process of opening experiments via the Quick Open menu is explained later on. The remaining interface components are self-explanatory.

Data Window after startup The image above depicts the data window after startup. The data window is used to display additional information of an experiment. This information is time-dependant and synchronized with other time-dependant data, like the current video position. If the time is changed in one component, it changes in all the other ones as well. The current implementation is able to display an experiment transcript (in the Transcript view area). The transcript view is divided up into a left part showing the proband's text contributions and a right part showing the wizard's text contributions. The different experiment phases are displayed hierachically in the Transcript navigation area. Transcripts can also be highlighted but this feature is explained later on.

A video recording of an experiment and its related transcript file are considered as an experiment. A video is an AVI or MP4 file while transcript files are special XML applications. The experiment's files can be opened separately or by using the Quick Open feature. Empty Quick Open menu Quick Open can be performed using the Quick Open menu. The menu has items for all experiments found in a selected directory. The directory may be selected using the Choose Directory... menu item. Experiment files with identical basenames (file name without extension) are listed as single menu items. For instance, if the directory contains two files 20101117.xml and 20101117.mp4, the menu will look like: When an experiment item is activated in the menu, the corresponding experiment files are loaded (replacing any already opened experiment). The configured location of the Quick Open directory persists after application restarts.

If the transcript is opened and a files was selected the transcript widget shows the dialog between proband and wizard. The dialog monitor is divided up into two seperate widgets so there can be different settings and fonts at each widget. Also it is possible to markup matches separate from each other. There two way to search matches: regular expressions and format files.

For more information how to use regular expressions have a look at glib documentation for Perl compatible regular expression. Regular expressions are case-insensitive so both lower-case and upper-case character will match the same expression. Regular expression matches will be formated bold by default. Captures are not be supported.

By default a search term will be regarded as regular expression. If the markup toggle is activated the input expression will be regarded as format expression which is a combination of regular expression and Pango mark up. That means if the regular expression matchs at the text the markup expressions will apply. For more information refer to the Pango Markup documentation..

Format files are collection of multiple format expressions. At first there has to be selected a quick open directory in menue Format entry Choose Directory. After that all available format files in the selected directory will be listed under menue Formats. To create an own format file care the following: Each line will regarded as a single mark up statement. Leading whitespace characters will be ignored. A line beginning with '#' will be ignored complete. Only whole lines can be ignored. The format file has to save as a FMT-file (*.fmt). Incorrect lines will cause an error message. Let be the whole text referring to a single time stamp a text fragment. For each text fragment each format expression in the format file will be iterated and the associated regular expression will matched. For each match all associated mark ups will apply cumulatively at the matching text.

The config file is located in the users default directory where each config files are. By editing the config-file default keys which can not changed via gui can set. More details about the structure of the config file can be found in the glib documentation. The following table shows all additional keys :

Key	Description
Default-Format-Font	For detailed information follow pango font description
Default-Format-Text-Color	An RGB color specification such as '#00FF00' or a color name such as 'red'
Default-Format-BG-Color	An RGB color specification such as '#00FF00' or a color name such as 'red'