Table of Contents

Example

Setlist - Fire a specific track

by: Sebastian Beutel, July 2018
published: [here]
description: fire a specific setlist track
remarks: based on an idea by Chris M., see https://www.facebook.com/groups/Avolites/permalink/1288644587934439/?comment_id=1288649477933950&reply_comment_id=1288841831248048

Albeit there are various functions to fire and edit setlist tracks, the main challenge is to identify the particular track. After a number of pointless tries Gregory confirmed that currently usernumbers for setlist tracks are not implemented. Hence the only way to identify a track is its id. And as it is also not possible to make a track show its id and it's also not shown via Web API the only way to get the id is to retrieve it from the showfile. And finally, as SetList.FireTrack comes from the namespace SetList passed TitanIDs are parsed in the SetList context which fails. The only way to make it work is the string notation SetList.FireTrack(“trackHandleID=1840”).

In order to make it easier to get a setlist track id the showfile parser has been extended to show them (click Show Setlists).

functions

identifier

Code

firesetlisttracks.xml
<?xml version="1.0" encoding="utf-8"?>
<avolites.macros xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Avolites.Menus.xsd">
 <macro id="wiki.macros.fire.1840" name="sb fire track 1840">
    <sequence>
      <step>SetList.FireTrack("trackHandleID=1840")</step>
    </sequence>
  </macro>
</avolites.macros>

Explanation

This explains the functional steps within the sequence. For all the other XML details please refer to Formats and syntax

This simply fire a specific setlist track, identified by its id.

How to use it

  1. create your show with all required setlists and tracks
  2. upload the showfile to the showfile parser and hit Show Setlists to get the setlist track ids
  3. create one or more of the macros like above with the ids you have just found (replacing all three occurencies of '1840' with the respecitve id)
  4. fire the macros as needed. You might e.g. copy the macros to buttons in the macros workspace window and trigger them via MIDI.