Emotion FX with DMX Output enabled

As periodic questions arise how to setup Emotion FX with DMX Output enabled, I’ll try to summarize the most important information here.

In the “System Manual LAS” in chapter “Emotion FX DMX Output” this is explained with more details for a RDM enabled installation. That requires two systems. In contrast this post handles the same setup without RDM (just DMX Output through Emotion FX), which is able to run on one machine.

Please note, that it will not be possible to have the same Butlers online in Programmer at the same time.

First, some preconditions have to be met:

  • Emotion FX must be able to run in Fullscreen mode (LCE dongle needed!)
  • you need two distinct network cards
  • they need an IP address assigned, so cable needs to be plugged in
  • the IP addresses of both network cards have to be on different subnets! (e.g. one on 192.168.123.* and the other on 172.22.122.*)
    As example lets say we have and
  • the network card with IP address 192.168.123.* has to be connected to the e:cue Butlers
  • of course the Butlers IP address have to be in the same subnet, so in this example something in 192.168.123.* and have to be connected to the network card
  • you need a patch (*.patx) where the Butlers universes are mapped (in Patchelor, Butlers checked online and Universe set, then save/export)
  • be sure that Programmer and Emotion FX are of the same version.
    A Programmer V6.1.* only works with an Emotion FX V6.1.*
    A Programmer V6.0.* will not work with Emotion FX V6.1.*

First, we set up Emotion FX:

  • go to Options > Network Setup > set “e:net Network Interface” to the IP address that connects to the Butlers, in this example it is the
  • go to Options > Network Setup > set “Discovery Service Network Interface” to the other IP address, we had chosen
  • machine restart required!

Next, Programmer:

  • go to Application Options > Advanced > set “e:net” to one of the IP addresses, as example we choose
  • in Seqeuncer, create an Emotion FX sequence. In the IP Address field, the “…” Button will show your – use it.
  • Emotion FX will be started and your Sequence connects to it. Content will already be shown on Emotion FX windows.
  • open the Sequence Properties > DMX Output Settings > Patch File and choose the .patx you previously created. Also tick the “Enable DMX Output” checkbox.
  • optionally also tick the “Show Mapped Pixels”. It will show a grid on top of the content of the Emotion FX fullscreen signal, that marks the pixels that are used to generate the DMX Output (according to your patch).

That’s it, the Butler should be online now and DMX output should be as the patched pixels grab it from the content that Emotion FX shows.

If you have problems with this, please state which steps are unclear or where you get stuck!

Here is a sketch that may help for quick reference.


Lighting Application Suite 6.1 SR1

LAS 6.1 SR1

LAS 6.1 SR1

There is a service release available für the LAS 6.1, ready for download from our website. Most important changes and fixes are:

* NEW: make Action Pad “Push” buttons become ‘active’ while being pressed

* FIX: improved stability of Programmer communication with EmotionFX in high load scenarios
* FIX: VersatileMasterSetValue can set values above the 4096 max
* FIX: LCE2 display text
* FIX: fix DMX input for LCE2 Input module
* FIX: Action Pad item resize handles do not work with Item Padding settings
* FIX: Dynamic Scroll Text: the “Enable Autotext” checkbox is not available for “File Source”
* FIX: some export warnings regarding crossfade were missing
* FIX: export log, trigger index is now 1-based, according to Trigger List dialog
* FIX: ActionPadSetItemBorderColors() does not work for Box3D buttons in Browser
* FIX: Macro-Manager with many macros scrolls to top after saving a macro
* FIX: Programmer without main window, without tray/taskbar icons
* FIX: CuelistSubMasterSetValueOnPage() does not work
* FIX: Fade time of cues with GotoCue e:script commands do only work once in suspended macros
* FIX: deleting the last fixture in the “Fixture Patch” dialog results in a crash
* FIX: Kiosk Mode is not started correctly, Action Pad is not full screen
* FIX: a show with many Serial Drivers (RS232) takes a very long time to load
* FIX: Screen ID re-numbering for Screen IDs above 10000
* FIX: GrandMaster does not affect Amber channel in live operation (in Programmer View)
* FIX: ActionPadSetItemBorderColors() does not work when button had this color before
* FIX: strreplace() cuts strings to 127 chars
* FIX: Media player window is behind the programmer window when starting in fullscreen mode
* FIX: Programmer crashes when typing text into scroll wizard
* FIX: SequenceTrackSetEnabled has no effect on action tracks
* FIX: Action Pad full screen sometimes behind Windows taskbar
* FIX: adding a Fx Effect touches the Intensity channel

The Programmer 6.1 SR1 is no longer compatible in all details with older/earlier Programmer show files before v6.1 SR1.
That means, showfile created in 6.1 SR1 can NOT be loaded in 6.1.
Please use “e:cue Action Pad App for Android/iOS” in Version 3.2.1 with this Programmer.

DALI? Salvatore?

DALI is an important communication interface for fixtures and controls. Compared to DMX it is much simpler with a restrichted functionality. Nevertheless, DALI is a market standard. There is a very good documentation available at DALI AG, which describes DALI in detail, but also with an overview and most important things to know. The manual is available in German and in English.

Sending RDM commands via e:script

This script shows how to reset a device via RDM to factory settings. All you have to know is the RDM address of the device, you don’t have to know the port or controller to which the device is connected, as the the reset command is sent via all ports that support RDM. And you don’t have to activate RDM. This is an easy and simple way to reset a device without a former RDM discovery. Even devices not answering to discovery requests can be reset. This is the procedure:

After declaring and initialising the necessary variables, an iteration run is executes over all controllers and corresponding ports. This includes ports that have no activated RDM. The key function here is SendRdmRequestByController.

// RDM reset script by Till Wiebke
// Traxon Technologies Europe, Paderborn
int controller = 0;
int port = 0;
int success = 0;

// Unique RDM ID of the target device.
string target = "4845:000002C6";
// The binary object block is needed for the custom RDM request.
int bobHandle = BobAllocate(0);

for (controller = 0; controller < GetRdmControllerCount(); 
   for (port = 0; 
        port < GetRdmControllerPortCountByController(controller);
      // Enable the controller if necessary.
      success = RdmPortIsEnabledByController(controller, port);
      if (0 == success)
         success = RdmPortEnableByController(controller, port);
      if (1 == success)
         // Sending a "factory reset" (0x0090) 
         // set-request (0x30) to the root-device (0).
         printf("FACTORY_DEFAULTS to %s, controller %d,port %d.\n",
                                         target, controller, port);
         SendRdmRequestByController(controller, port, target, 
                                    0, 0x30, 0x0090, 0, bobHandle);

Video tutorials for LAS 6.x

LAS video tutorials

LAS video tutorials

We have created some new videos about the Lighting Application Suite. At the moment, there are six videos available. Select Downloads and then Tutorials. Be aware that the videos are in 720p resolution, so your wires into the Internet should not be too thin. The AVI versions are smaller, the FLV versions much bigger, but with a better resolution.

Stay tuned, more to come soon …

Ramp Intensity Start / Stop actions

Today I realized that the Ramp Intensity Start and Ramp Intensity Stop actions are not intuitively understandable. The idea was to mimic the “Intesity Up” and “Intensity Down” actions from the Butler XT Stand Alone Mode triggers. That is, while holding a button, the corresponding fader will move up (or down) until the button is released.

To do so, create an Action Pad button with Toggle State = Push
As Action#1 use Ramp Intensity Start for the desired fader and a delta of 1.
As Action#2 use Ramp Intensity Stop for the same fader.

Here is an example Action Pad page:
Action Pad page - Ramp Intensity example (953)

A delta of 1 means that the fader changes by 1% per frame, so it takes 3 seconds to go from 0% to 100% (or vice versa).

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.


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.


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

More performance, more universes, more flexibility

This is what the press reads:

LCE2 and Butler PRO

LCE2 and Butler PRO

Traxon Technologies, a global leader in solid state lighting and control systems, introduces two new high performance lighting control servers – Lighting Control Engine 2 (LCE2) and Lighting Control Engine 2 fx (LCE2-fx) – together with a new Butler PRO output engine for running large numbers of DMX512/RDM or e:pix universes. Featuring innovative technology, these important additions to Traxon & e:cue’s lighting control engine and software portfolio take control systems to new heights. They significantly enhance the flexibility, reliability, scalability and performance of lighting, media and show control programming.

The Lighting Control Engine 2 (LCE2) and Lighting Control Engine 2 fx (LCE2-fx) are designed to orchestrate fixtures, media, interfaces, and user terminals in medium to large lighting installations. Supporting a wide range of standardized and Ethernet-based control protocols, a variety of input and outputs and ports, the engines are designed specifically to act as the core of any complex lighting installation. With the Lighting Application Suite (LAS) software pre-installed, these high-performance servers succeed the successful LCE and LCE-fx with increased capacity to control sophisticated lighting projects and guarantee uninterrupted operation. Similar to the LCE2, but with dynamic real-time video capabilities and extended software tools, LCE2-fx is the ultimate solution for the most demanding projects including mixed media installation.

Butler PRO is a new DMX512/RDM or e:pix output engine that interfaces seamlessly with the Lighting Application Suite (LAS) and offered maximum control scalability. The Butler PRO DMX512/RDM version is the optimal choice for running a large number of DMX512 universes — up to 16 DMX512/RDM universes (8,192 channels) — with full RDM (Remote Device Management) capability for bidirectional communication, while the Butler PRO e:pix version – available Autumn 2013 – is running up to 16 e:pix universes (32,768 channels). Connected to a server via Ethernet, Butler Pro can be easily mountable in a standard 19-inch rack and accommodates wall mounting via rotatable 19-inch mounting brackets.