Lighting Application Suite 7.0 – news and fixes

PLEASE NOTE:
The Programmer 7.0 is no longer compatible in all details with older/earlier Programmer show files before v7.0. That means, showfiles created in 7.0 can NOT be loaded in earlier versions. Please use “e:cue Action Pad App for Android/iOS” in Version 3.2.1 with this Programmer.

  • Programmer
  • Library Editor (prerequisite for the Programmer and the Patchelor)
  • Patchelor
  • Imagine
  • Emotion FX (restriced Demo which runs only with an e:cue Programmer Enterprise dongle, works only with Programmer 7.0)
  • HASP (prerequisite for the Programmer 7.0 Enterprise and Premium)

Programmer

  • NEW: DALI Manager for setup and controlling OSRAM DALI ballasts and inputs.
  • NEW: ETH2DALI support for DALI, DMX OUT and TERMINAL device driver.
  • NEW: The trigger machine has been extended to support conditions for every trigger. A trigger will only fire if all conditions are fulfilled.
  • NEW: Action and Trigger clipboard function for copy and paste.
  • NEW: The Emotion FX Sequence properties have been extended to configure the patched pixels overlay mask
  • NEW: It is possible now to let a video loop automatically for Emotion FX sequences.
  • NEW: Timrecode support for Standard Sequences (SMPTE or MTC).
  • NEW: Some new string processing e:script commands.
  • NEW: New V-Master registrated event.
  • NEW: Support for Moxa E1242
  • NEW: No longer support for Nano RS-232, Faderunit RS-232, Elink 512/1024 and Excite (the old Excite, NOT the Excite+).
  • NEW: The bitmap wizard has been extended to use the current Programmer View content as wizard input.
  • NEW: The “Pages Setup” has been moved from the cuelist directory into a separate dialog.
  • NEW: The patch import can be configured to work addivtive now instead of clearing the current patch.
  • NEW: The Patch dialog offers an option now where you can specify into which section the fixtures should be inserted.
  • NEW: new DALI Trigger, Backup Trigger and Ethernet Input Trigger Event.
  • NEW: The export dialog has a new option “set all masters to maximum” which is part of the export master device configuration.

Emotion FX

  • NEW: A transparrent overlay mask based on the mapped pixels can be displayed now to help with the layer positioning.

Patchelor

  • NEW: ETH2DALI support

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 192.168.123.20 and 172.22.122.44
  • 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 192.168.123.20
  • 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 192.168.123.20
  • go to Options > Network Setup > set “Discovery Service Network Interface” to the other IP address, we had chosen 172.22.122.44
  • machine restart required!

Next, Programmer:

  • go to Application Options > Advanced > set “e:net” to one of the IP addresses, as example we choose 172.22.122.44
  • in Seqeuncer, create an Emotion FX sequence. In the IP Address field, the “…” Button will show your 172.22.122.44 – 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.

EmotionFX_DMXoutput

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.