<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://avosupport.de/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://avosupport.de/wiki/feed.php">
        <title>AVOSUPPORT - macros</title>
        <description></description>
        <link>https://avosupport.de/wiki/</link>
        <image rdf:resource="https://avosupport.de/wiki/_media/logo.png" />
       <dc:date>2026-04-24T00:52:36+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/action_and_menus?rev=1511105266&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/active_binding?rev=1546620210&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/console_and_simulator?rev=1511103122&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/control_structures?rev=1549487242&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/deploying?rev=1512679352&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/examples?rev=1745932165&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/examplesdate?rev=1587294914&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/formats_and_syntax?rev=1587291324&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/function_list?rev=1535380020&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/function_syntax?rev=1535390094&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/identifiers?rev=1529422222&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/macro_file_format?rev=1511104818&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/macrolocation?rev=1511185730&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/namespace?rev=1511105438&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/properties_list?rev=1529422804&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/recorded_vs._coded_macros?rev=1511882646&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/sidebar?rev=1587291270&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/start?rev=1724487398&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/step_pause?rev=1511105308&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/types?rev=1536485246&amp;do=diff"/>
                <rdf:li rdf:resource="https://avosupport.de/wiki/macros/xml_file_format?rev=1724487470&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://avosupport.de/wiki/_media/logo.png">
        <title>AVOSUPPORT</title>
        <link>https://avosupport.de/wiki/</link>
        <url>https://avosupport.de/wiki/_media/logo.png</url>
    </image>
    <item rdf:about="https://avosupport.de/wiki/macros/action_and_menus?rev=1511105266&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-11-19T15:27:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Action and Menus</title>
        <link>https://avosupport.de/wiki/macros/action_and_menus?rev=1511105266&amp;do=diff</link>
        <description>Action and Menus

When dealing with macros you&#039;ll soon learn that even simple actions might require several steps: in general, programming is a very fine-grained business.

One of the aspects of this is that the menu - which is displayed to you - is independent from the things which are going on inside the programm. And while there might be measures in place to keep menus and the core in sync, there are also occasions where it is your duty to deal with this. In doubt, try to find out if there is…</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/active_binding?rev=1546620210&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-01-04T16:43:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Active Binding</title>
        <link>https://avosupport.de/wiki/macros/active_binding?rev=1546620210&amp;do=diff</link>
        <description>Active Binding

You will have noticed that the factory macros for palette fade time and palette overlap feature something special: if e.g. you fire the macro to set palette overlap to 50%, this macro handle (key or button) is highlighted as active until you set palette overlap to another value. In this case, this is very useful to always have an overview what values overlap and fade time are set to.</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/console_and_simulator?rev=1511103122&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-11-19T14:52:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Console and simulator</title>
        <link>https://avosupport.de/wiki/macros/console_and_simulator?rev=1511103122&amp;do=diff</link>
        <description>Console and simulator

When it comes to describing actions on the real console (or on the simulated one), the following conventions are used (an extensive example is Recorded vs. coded macros):

	*  always write as like as you were performing on a real console, even if playing with the simulator</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/control_structures?rev=1549487242&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-06T21:07:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Control Structures</title>
        <link>https://avosupport.de/wiki/macros/control_structures?rev=1549487242&amp;do=diff</link>
        <description>Control Structures

When a macro is called, all its steps are executed sequentially.

However, you can define conditional steps - steps which are only executed if a condition is met. In order to do this, simply give the step a condition property, like in</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/deploying?rev=1512679352&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-12-07T20:42:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Deploying macros</title>
        <link>https://avosupport.de/wiki/macros/deploying?rev=1512679352&amp;do=diff</link>
        <description>Deploying macros

Now you have written your groundbreaking macro... but: how to make Titan aware of it and use it?

All you need to do is

	*  copy the macro file to your usermacro location
	*  restart Titan - macro files are only read upon software start
	*  after the software has come back on again you may open the show library (or select</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/examples?rev=1745932165&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-04-29T13:09:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Examples list</title>
        <link>https://avosupport.de/wiki/macros/examples?rev=1745932165&amp;do=diff</link>
        <description>Examples list

This is a list of the examples in this wiki. Please feel free to add more. If you are not into writing in a wiki but want to contribute neithertheless please send an email to &lt;sebastian.beutel@avolites.de&gt;

For those who follow this wiki and are keen on the newest additions, please check the</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/examplesdate?rev=1587294914&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-04-19T11:15:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Examples list by last change date</title>
        <link>https://avosupport.de/wiki/macros/examplesdate?rev=1587294914&amp;do=diff</link>
        <description>Examples list by last change date

This is a list of the examples in this wiki, newest additions first. Please feel free to add more. If you are not into writing in a wiki but want to contribute neithertheless please send an email to &lt;s.beutel@avolites.de&gt;

For those who follow this wiki and are keen on the newest additions, please check the</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/formats_and_syntax?rev=1587291324&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-04-19T10:15:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Formats and syntax</title>
        <link>https://avosupport.de/wiki/macros/formats_and_syntax?rev=1587291324&amp;do=diff</link>
        <description>Formats and syntax

This wiki attempts to introduce you to writing macros even if you had not studied computer science. However, it is like reading and writing: there is some spelling and grammar to adhere to, and knowing the basic rules makes life easier. You&#039;ll soon get used to it, and will refer back to this documentation only in rare cases.</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/function_list?rev=1535380020&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-27T14:27:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Function list</title>
        <link>https://avosupport.de/wiki/macros/function_list?rev=1535380020&amp;do=diff</link>
        <description>Function list

This is a list of the functions which are used in the examples resp. explained in this wiki. A full - but sparsely documented - list of functions is available at &lt;http://api.avolites.com/&gt;.

Currently there are  functions explained in this wiki:


	* ActionScript.SetProperty
	* ActionScript.SetProperty.Boolean
	* ActionScript.SetProperty.Double
	*</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/function_syntax?rev=1535390094&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-08-27T17:14:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>The Syntax of Functions</title>
        <link>https://avosupport.de/wiki/macros/function_syntax?rev=1535390094&amp;do=diff</link>
        <description>The Syntax of Functions

Functions are the heart of macros, functions are listed here and - much more so - in the API documentation. But how should we read something like this:
Void Group.StoreMenu.StoreOnButton(String group, Int32 index, AcwUserNumber userNumber)
Essentially functions are the part of the code where the system is instructed to do something.</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/identifiers?rev=1529422222&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-06-19T15:30:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Identifiers</title>
        <link>https://avosupport.de/wiki/macros/identifiers?rev=1529422222&amp;do=diff</link>
        <description>Identifiers

This is a very special section: &#039;identifiers&#039; tries to list and explain all the values you need to identify a certain item or state. As such, &#039;identifiers&#039; are not part of pure programming logic or documentation. In fact in most parts this is just convention and system design: how to identify a certain button/playback/palette, how to tell which state a certain item to set to, etc.</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/macro_file_format?rev=1511104818&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-11-19T15:20:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Macro file format</title>
        <link>https://avosupport.de/wiki/macros/macro_file_format?rev=1511104818&amp;do=diff</link>
        <description>Macro file format

The macro files shall be UTF-8 encoded, no BOM, Windows-style line endings (CR LF).

For a better understanding you are encouraged to have a look at the factory macro files which you can find in 

C:\Program Files\Avolites\Titan\Macros</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/macrolocation?rev=1511185730&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-11-20T13:48:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Macro Folders</title>
        <link>https://avosupport.de/wiki/macros/macrolocation?rev=1511185730&amp;do=diff</link>
        <description>Macro Folders

As stated elsewhere, macros are xml files. However, in order for Titan to find and read these files, they must reside in designated locations which might differ depending from your installation. Also, this is different on real consoles and with Titan PC suite (Titan One, Titan Mobile, Titan Simulator):</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/namespace?rev=1511105438&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-11-19T15:30:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Namespaces</title>
        <link>https://avosupport.de/wiki/macros/namespace?rev=1511105438&amp;do=diff</link>
        <description>Namespaces

If you have already had a glance at the online API documentation then you know that there really is a huge number of functions and properties - currently there are almost 3000 (three-thousand) entries in the API. Not even the most professional programmer could know all these by heart.</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/properties_list?rev=1529422804&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-06-19T15:40:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Properties list</title>
        <link>https://avosupport.de/wiki/macros/properties_list?rev=1529422804&amp;do=diff</link>
        <description>Properties list

Stricly, this is only about the system&#039;s properties (e.g. Timecode.Enabled).

In contrast, general object&#039;s properties (e.g. titanId as property of the Handle object) are explained at the respective objects.


	* Attribute.Mask.Clear.Value
	* Audio.AudioTriggersEnabled
	* Chases.ConnectedHandle
	* CueLists.LiveCueNumber
	* Editor.Shapes.EditingPlaybackShapes
	* Editor.Shapes.EditShapesEmpty
	* Editor.Shapes.PhaseOffset
	* Editor.Shapes.ProgrammerShapes.Empty
	* Editor.Shapes.Spr…</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/recorded_vs._coded_macros?rev=1511882646&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-11-28T15:24:06+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Recorded vs. coded macros</title>
        <link>https://avosupport.de/wiki/macros/recorded_vs._coded_macros?rev=1511882646&amp;do=diff</link>
        <description>Recorded vs. coded macros

For quite many years/versions Avolites Titan allows for recording macros one the fly. This involves the &lt;Macro&gt; button, and records all the button presses you do, in exactly this order. This sequence can then be played back by just recalling the recorded macro. More information on this is available</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/sidebar?rev=1587291270&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-04-19T10:14:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Macros</title>
        <link>https://avosupport.de/wiki/macros/sidebar?rev=1587291270&amp;do=diff</link>
        <description>Macros

Introduction to macros

Recorded vs. coded macros

Formats and syntax

Macro file format

Macro Folders

Deploying macros

XML format

The Syntax of Functions

Function list

Properties list

Namespaces

Types

Identifiers

Examples list

----------

Start page</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/start?rev=1724487398&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-08-24T08:16:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Introduction to macros</title>
        <link>https://avosupport.de/wiki/macros/start?rev=1724487398&amp;do=diff</link>
        <description>Introduction to macros

Overview

Macros are a way to automatically call specific functions or set specific values. Macros can be called from workspace buttons, or can be triggered from specific actions (like: from starting a cue in a cue list or – as of Titan v10 – starting a set list track).</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/step_pause?rev=1511105308&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-11-19T15:28:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Step Pause</title>
        <link>https://avosupport.de/wiki/macros/step_pause?rev=1511105308&amp;do=diff</link>
        <description>Step Pause

Pause is a direct property per step and defines a delay time before this step is executed. While some macros will flawlessly work without a step pause set, others may show unreliable behaviour. This is due to the fact that each command and action takes a certain time to complete, and if the next step is called before the previous one is completed, undesired results may occur.</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/types?rev=1536485246&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-09T09:27:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Types</title>
        <link>https://avosupport.de/wiki/macros/types?rev=1536485246&amp;do=diff</link>
        <description>Types

All data - in particular properties and functions&#039; parameters - need to be of a certain type. Essentially, this is a convention you know from everyday&#039;s life. There are some information which are always a number - e.g. the phone number. Then there are other information which are always words, e.g. a person&#039;s name.</description>
    </item>
    <item rdf:about="https://avosupport.de/wiki/macros/xml_file_format?rev=1724487470&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-08-24T08:17:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>XML format</title>
        <link>https://avosupport.de/wiki/macros/xml_file_format?rev=1724487470&amp;do=diff</link>
        <description>XML format

There are dozens of books on XML only - it is a widely used language for many purposes. As always, wikipedia is a good read. however, based on an example, the (for this purpose) essential items will be explained.

An example macro file might look like this:</description>
    </item>
</rdf:RDF>
