This is an old revision of the document!
Table of Contents
Web API example
Programming playbacks
Starting point to programm playbacks using the Web API. Inspired by a project where the customer shall be able to program simple cues. Also this might be the starting point for more sophisticated applications.
Also this solves the mystery about the 'separate programmer'.
| author, date | Sebastian Beutel, February 2022 |
|---|---|
| published | here, Youtube |
| prog. lang./ framework | simple text editor (I used the Web API Demo to play with the requests) |
| description | collection of http requests used to program simple cues. |
| other requirements | This is essentially just a collection of requests. You can send them with a web browser or with other tools. |
Screenshots
Video
Separate Programmer
By default the Web API is available on network port 4430 (hence the requests start with something like 'http://localhost:4430/…'. Also, actions on the user interface, e.g. changing pages or selecting fixtures, do not reflect in the Web API. In turn anything done in the API doesn't reflect in the normal user interface, e.g. if you select fixtures or set a level you won't see it in Titan. This is pretty much like the blind mode or another user. Unfortunately this makes it really hard to debug any API requests as you see the outcome only when everything is correct and you did succeed programming something.
However there is a solution: you can tell Titan to also listen on another port, with the user and interface you see directly in Titan. In order to do this you need to set specific parameters:
- open the .exe.config file of the Titan application you are using (e.g.
C:\Program Files\Avolites\Titan Mobile\Mobile.exe.config) - find the
<appSettings>part - add these lines:
<add key="webapi.enabled" value="true" />
<add key="webapi.port" value="4431" />
- maybe these lines already exist but you need to change
falsetotrue - restart the Titan software. Now, the Web API is available on both, port 4430 with the traditional separate user, and port 4431 with the same user and interface you see in Titan.
In order to make it easier to work with these settings the WebAPI test page now also features a port toggle button where you can switch between port 4430 and 4431:
