https://www.avosupport.de/wiki/ 2026-04-15T09:17:06+00:00 https://www.avosupport.de/wiki/ https://www.avosupport.de/wiki/_media/logo.png text/html 2018-08-26T10:39:24+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/controlname?rev=1535279964&do=diff Identifier ControlName ASSUMPTION This is the name of a fixture attribute as it is set in the personality. It is assumed that this refers to the set Attribute Id. Thus, there is no closed list. There might be controlNames like “Pan”, “Dimmer” or “Colour1 text/html 2024-04-18T13:03:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/fixturecontrolid?rev=1713445434&do=diff Identifier FixtureControlId Type: Int32 Each control, i.e. controllable attribute of a fixture, is assigned a number. Example in <http://forum.avolites.com/viewtopic.php?f=21&t=5189> "...this is a special ID assigned by the Titan system and references the specific attributes within a fixture. There are a number of fixed ID’s which I have listed below and relate to common attributes. Some are specifically created depending on the fixture type. For the purposes of this guide we only need to … text/html 2024-08-24T08:50:20+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/handle?rev=1724489420&do=diff Identifiers Handle ASSUMPTION (see About this wiki) " " "Handle is a specific object type used to describe a particular item inside the whole Titan show structure. Examples for handles are: playbacks (the physical faders/buttons, as well as the touch buttons), palette handles (palette buttons, touch or real, as well as palettes addressed by their name/number), fixture handles (again: real buttons or touch buttons or abstract places addressed by their number). text/html 2020-04-19T18:03:10+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/location?rev=1587319390&do=diff Identifier Location Within Titan, each and every single item which has been programmed and assigned to a handle (button, fader or key) also has a location - the 'address' of the handle it is assigned to. While more intuitive for the human user, this is slightly more complicated in terms of programming: a location comprises of the handle group (i.e. which window or which section of faders/buttons), the page ( 0-based: number 0 is displayed as page #1), and the handle index (which button on that… text/html 2018-09-16T09:58:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/menueventtypes?rev=1537091938&do=diff Identifier MenuEventTypes This identifier of type Enum determines upon which event something is about to happen. See <http://api.avolites.com/11.0/Avolites.Menus.MenuEventTypes.html>: Member Value DescriptionOnButtonDown Fires when a button is pressedOnButtonUp Fires when a button is releasedOnSelect Fires when a button or menu item has been selected (button down followed by button up) text/html 2018-09-16T11:00:56+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/panelmidicommands?rev=1537095656&do=diff Identifier PanelMidiCommands List of the various MIDI commands. From the example in Trigger - Add MIDi trigger it is believed that it is implemented as type Enum <!-- lines wrapped only for readability --> <step>Triggers.AddMidiTrigger( Triggers.SelectedMappingId, Triggers.PendingTriggerTarget, 1, <!-- here the MIDI command is determined --> Math.ToEnum( "Avolites.Titan.Controllers.Console", "Avolites.Titan.Controllers.Console.PanelMidiCommands", … text/html 2018-06-25T12:15:08+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/profileid?rev=1529928908&do=diff Identifier profileId As stated elsewhere, each item within Titan is addressed by its ID. Technically, each ID is a simple integer number. Profile IDs are IDs for the key profiles. It seems that the factory key profiles have some numbers like -1, -4, -6, -7, while all user-defined profiles have IDs like 1821, 493448 or 503444 - entirely random. text/html 2024-08-24T08:51:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/titanid?rev=1724489517&do=diff Identifier titanId Within Titan, each and every single item has an Id - simply an integer number which is this item's unique identifier. This can be used to refer to a specific item by calling this object with its id. Usually, each id is set by Titan itself - you have no means - and no reason - to alter a particular item's id. Also, that's why text/html 2024-08-24T08:36:43+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/trackhandleid?rev=1724488603&do=diff Titan Identifier trackHandleId This is the Id which identifies a particular setlist track. Used e.g. in Setlist - Fire a specific track. Please see the explanation there: " 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… text/html 2021-06-13T14:51:30+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/usernumber?rev=1623595890&do=diff Types/Object/Handle userNumber Within Titan, each and every single item which you program has a number - simply an integer number, which you, within reason, can assign freely. In most cases, this is either not conciously used at all, or used in a user-specific system (e.g. group #1 might be the front truss or a specific group of fixtures text/html 2018-08-25T15:10:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://www.avosupport.de/wiki/macros/identifier/windows?rev=1535209854&do=diff Identifier Windows Titan has a number of workspace windows. Some are available only in a certain context, others can be opened almost anywhere. All windows have these attributes (any attributes are written in double quotes, even a numeric type):