Available for download:
Lighting Application Suite 6.1

Since end of July 2013 available for download: version 6.1 of our Lighting Application Suite. Here is the link.

RDM Autotext in Action Pad

RDM Autotext in Action Pad

One of the main changes is the reworked RDM (Remote Devive Management) subsystem allowing more RDM, not only from e:sscript, but also as Autotext. Use RDM in the Action Pad, use e:script to automate RDM logging or watching. More info? Use the System Manual and Advanced System Manual for the LAS, also available for free download.

e:script

Various new RDM commands like GetRdmControllerCount, RdmDriverHasRdmSupport,
RdmPortEnableByController, SendRdmRequestByController, GetRdmResponseCodeDescription, GetRdmSubDeviceCount, GetRdmSubDeviceID etc. See the e:script Reference in the Programmer for details.

There is a new event, RDMEvent, that can be registered. More about events and RDM in the Advanced System Manual.

Autotext

There are several new Autotext functions for RDM. See the chapter about Autotext and the Action Pad for in the System Manual for details. See also the post about RDM Autotext below.

Device Manager

LCE2 Devices

LCE2 Devices

The Butler PRO is supported as DMX output device. The LCE2 I/O Interface is available as DMX/RDM input and output  and as terminal driver. Butler XT2, XT, S2 and PRO have a new RDM Discovery Mode definition. Discovery mode can now be defined as complete, discovery or off.

Blackmagic Intensity Pro (LCE2-fx)

In order to support the capture card Blackmagic Intensity Pro in the LCE2-fx the capture dialog in the Media Player was extended. For every capture device in the dialog the resolution in Hertz is now displayed as well.

Update Dialog

The Update Dialog is now just a topmost window and the Programmer will start as usual with the Update Dialog shown on the top.

MIDI Learn for Triggers

MIDI Learn for Triggers

Trigger Rule Dialog

The Trigger Rule Dialog has a new MIDI Learn button. When the button is pressed, the next MIDI input will be used to configure the trigger rule.

Cuelist Actions

Two new options to the Cuelist Actions have been added: Skip Forward and Skip Backward. The actions behave exactly like the Skip Forward and Skip Backward buttons in the Cuelist Dialog.

Show Export

The show export log view shows now, which triggers where exported and which could not be exported.

Versatile Masters setup

MIDI Learn for Masters

MIDI Learn for Masters

The Versatile Master configuration dialog now has a MIDI Learn button. The MIDI Learn button will only listen to MIDI control change input (cannot be added to a fader).

 

LCE2 Page Setup

You can create individual display pages for the LCE2 display. Actions can be connected to every display page. They are available in the “* Custom Menu *” by default. See the chapter Settings for details.

RDM with Butler XT2, XT, S2 and PRO

There is a new RDM Discovery Mode definition available. Discovery mode can now be defined as complete, discovery or off. Complete is the default mode in which all RDM devices are discovered and all RDM parameters and sensors are polled. Discovery means, that the devices are only discovered. So only their RDM unique ID will appear in the RDM Browser. Off means, that RDM communication is enabled if the port is enabled but no discovery communication will be performed. You can sent custom RDM requests per e:script in this mode.

Sequencer properties

The Sequence Properties dialog has two options now to adjust the amber/white level for
RGBAW, RGBWA or RGBW LEDs.

Autotext and RDM

One of the most helpful features in the Programmer is Autotext. But what is Autotext?

An ancient feature

Autotext was implemented in a rather early version of the Programmer and realizes access to internal data and parameters of the Programmer. This can be system time and date, astronomical times like sunset or twilight, even network parameters, cuelist parameters or Versatile Master names and values. The most prominent use of Autotext  is in the Action Pad. In a textfield, for example, use the expression <nicetime %X> and the Programmer will substitute this expression with the systemtime. <master 1 name> will show the name of the Versatile Master #1. A complete list of Autotext parameters can be found in the LAS Advanced System Manual, for free download from the Traxon or e:cue website.

The next big step

With LAS 6.1 it is possible now to access the RDM subsystem of the Programmer as Autotext. In this way you can show fixture data like lamp lifetime, up-time and all other RDM values and parameters in the Action Pad. And these are not static values, but updated all the time while the fixture runs RDM communication. The best way to see this is to watch the RDM timestamp of a fixture. To insert RDM Autotext in a textfield is very simple, because there is an interactive method to do this. You can, but you must not create the Autotext by hand.

Autotext sources

Autotext sources

In the Action Pad create a textfield. Double-click the created field or select Properties from the element’s context menu (right mouse button). The properties dialog has a button for Autotext. Clicking the button, a subselection gets displayed where you can choose the Autotext source. Here you can see the many sources to Autotext. For RDM select RDM and Create RDM Autotext. The RDM Autotext dialog opens.

RDM parameter dialog

RDM parameter dialog

In the RDM dialog you now can select the fixture and subdevice, as well as what sensor or parameter will be used. Click the varoius areas in the dialog to define the Autotext source from the RDM vaue stream, the click OK.

This will insert the proper Autotext definition in the textfield of the Action Pad.

Do not forget to enable Autotext substitution for the field in the element properties of the field. Otherwise you will only see the Autotext definition instead of the real value.

Action Pad and RDM

Action Pad and RDM

That’s all. You now have dynamic, realtime RDM data in your Action Pad page.

A complete description of RDM and Autotext is in the LAS Advanced System Manual for the LAS 6.1, available in the product page for the LAS in the Traxon website, and a complete description of the LAS as LAS System Manual (after release of LAS 6.1, of course).

Autumn Update 2012

Three major product updates happened for October 2012.

Mobile Action Pad

Mobile Action Pad

The Lighting Application Suite 6.0 is released. New features are the Color Picker for Action Pad, Emotion FX DMX Output and the Dynamic Scrolltext for Live FX. More to read in the e:cue website.

With the Butler XT2 firmware version 2.0 you now can control the engine with Action Pad in standalone mode. Either with a Flash-enabled PC web browser or with …

The Mobile Action Pad for iOS and Android. Supports the new styles in the Action Pad and the Color Picker. Read more

 

How to configure the Mobile Action Pad

The Mobile Action Pad for iOS and Android is a great tool to control the Programmer or the Butler XT2 with a firmware version 2.x. Here is a short description how to configure the Mobile Action Pad, assumed that there are Action Pages created in the Programmer, and downloaded to the Butler XT2, if it is used with this DMX engine.

Google Play Store

Download the app from the iTunes App Store or from the Google Play Store, search for “e:cue” to find it, install it on your smartphone or better on a tablet. Add the app to your menue to have fast access. Start the app and the following steps are the same for iOS and Android. Here shown for the Android version.

When started the first time the Mobile Action Pad does not have a previous session with a server, so it will display the server selection, there are already two sessions defined: to two test servers at ecue.com. You can use these two entries for a basic test, both are simulations, one for smartphones, one for tablets. If not in the server selection, use the «Back» button to return to it.

Server definition

In the server selection, tap «Edit» in the upper right corner. All available sessions are displayed, delete sessions via the stop symbol, tap the cog wheel to edit an existing session. The cog wheel in the upper left corner are the application options.

 

To enter a new server, tap «Add» in the upper right corner. In the following form enter:

Server data

A symbolic name for the connection, then the address of the server. For a Butler XT2 this would be the IP address, e. g. 192.168.123.220. Use the server address, not the address of a switch or a WLAN router. For the Programmer use the IP address of the server, make sure that the HTTP server in the Programmer is enabled in the Application Options. A symbolic name like “ap.myserver.com” could only be used when a DNX server is available. In most LAS installtions this is not the case.

Default for the port number is 80. «Group» and «Start Page» are not mandatory, they are necessary when you use page groups in the Action Pad and if you want to define a certain page as start page.Server selection

After entering the data, tap «Ok», check your entry and tap «Done», the server selection returns. Tap your server oder use the cog wheel to edit the entry. That’s all. With the application options via the upper left cog wheel you set few display options or you can protect access to the app with a password.

 

Application settings

 

The app remembers the last valid session, so restarting the app later will first try to re-establish the last active session with a server.

LAS 6.0 – Color Picker

Get the Flash Player to see this content.

LAS 6.0 – Setting up a show with Color Picker

Get the Flash Player to see this content.

How to write a post

Some general guidelines

Formats

Feel free to write a post as you like, but watch the following points:

  • Please do not use categories, either one uses categories or tags. As tags reflect the importance of topics we use tags and not categories (using both grants confusion).
  • Do not create new tags if not absolutely necessary. Go to Posts -> Tags to see already available tags. If you place the cursor into the tag field and you begin to type, available tags spelled like this will be shown.
  • Posts are public in general. There is a checkbox at the right bottom for “Access”. If you set this checkbox the post is handled at internal, only logged-in users can see the post. Logged-in users are those, who have a login.
  • Please use only Heading 1 for the main title and Heading 2 for subheaders (due to Google and SEO).
  • For longer posts please create a summary or a lead at the very beginning to help the user to see if this is relevant. Set the summary/lead in bold to mark it as what it is.

Users

Internal users are Traxon employees, not students or trainees. Do not create new users if they are not Traxon intern. If users from outside Traxon want to have a login, please check with Chris Loeser. Better check with him in any case.