(2018)
Vis Insita
Vis Insita
Vis Insita
Vis Insita
Vis Insita
(2018)
Vis Insita
(2018)
(2018)
(2018)
(2018)
A software interface that provides instant and intuitive control of Eos using any MIDI controller.
KontrolEos
ABOUT
1. KontrolEos
2. The
3. Why this controller ?
​
IMPLEMENTATION
​1. Setting up the controller
2. First steps with KontrolEos
2.1. Downloading and launching
2.2. Overview of the interface
2.4. Network configuration
2.5. Presets
2.6. FCB mode
CustoMap option
EncoDis page
2.7. FADER mode
MacroFad page
2.8. Eos Snapshots
​
VARIOUS NOTES
1. Futur dev
2. Limitations and know bugs
2. Versions
3. Contact
4. Thanks
​
TECHNICAL COMPLEMENT
1. Troubleshouting
2. Tips and tricks
​
​
Main interface of KontrolEos
Foreword
- KontrolEos is an open-share interface designed primarily for my own use. Although it seems to work great for most users, it is not tested with the specifications of a commercial application (on multiple OSs for example). Please use it knowningly and take note of the limitations and known bugs at the bottom of this page.
- KontrolEos requires very little configuration and learning. As this documentation is meant to be as explanatory as possible, it may seem the opposite.
- I am not affiliated to ETC or DJTech Tools with this app.
​
​
ABOUT
​
1 - What is KontrolEos ?
​
KontrolEos is a software interface for direct control of ETC's Eos software using a MIDI controller, without the need for time-consuming mapping.
It is aimed at lighting designers and lighting technicians who want a hardware control surface for software parameters such as faders, automatic fixture attributes, snapshots, macros or the intensity wheel.
It offers complete pre-assignment of the controller buttons, optimized for Eos, while allowing customization of certain parameters (fixtures parameters you wish to control, snapshot numbers, macros, etc.) via a simple graphical interface.
It runs under Windows 10+ and macOS (as well as in the Max software with which it was created), and makes your MIDI controller directly ready for use with Eos, with intuitive ergonomics.
Unlike the majority of control interfaces encountered for Eos, KontrolEos realistically emulates the behavior of the encoder wheels of physical Eos consoles, making control of FCB parameters simple and fluid.
​
With KontrolEos, the Eos GUI responds in real time to commands from the MIDI controller (e.g. parameter display in the Encoder Display), and conversely, feedback from Eos is displayed on the controller LEDs (e.g. fader level and type).
In addition to the initial commands offered by the controller's buttons, logical and easily memorized button combinations managed by KontrolEos increase the controller's possibilities and the number of directly accessible commands.
KontrolEos enables your MIDI controller to :
-
Control 18 pages of 10 faders, with for each fader the level, the Bump, the Group/Assert and the Load keys.
-
Control the Master fader and the Rate.
-
Control all the FCB parameters (coarse/fine/superfine adjustment, Home, Min, Max) in displaying them in the Eos Encoder Display in the same way as an ETC's Programming Wing.
-
Emulate the level wheel with a permanently accessible rotary knob.
-
Recall 24 customizable Eos Snapshots.
-
Recall 6 customizable Eos Macros.
KontrolEos doesn't install anything on your computer; it's an executable file. Once the application is open, it runs in the background without you having to intervene.
Each KontrolEos customization can be saved as presets that can be instantly recalled, multiplying its already extensive possibilities.
IMPLEMENTATION
1 - Configuring the MIDI controller
First of all, you have to configure the controller internally
2 - First steps with KontrolEos
2.1 - Downloading and launching
​
Note: this version of KontrolEos (2.21) has been tested with Eos sssss
​
You can download the latest version of KontrolEos by clicking on the Google Drive link below (no Google account required):
Once the file is unzipped, open the main directory.
Inside are several files and folders (including a folder named "resources").
These files must always stay together in the same main folder and the "resources" folder must not be deleted, modified or renamed, otherwise the application will not work.
​
• Windows 10+
KontrolEos doesn't require any installation. Simply double-click on the "KontrolEos.exe" file in the main folder to launch the application. The file must remain in its folder, but for convenience you can easily create a shortcut on your desktop (right-click on the file --> "Send to" --> Desktop).
When you first open KontrolEos, you may see a Windows Defender firewall window. You must allow access to use the application.
​
• MacOS
Unzip the .dmg package and then Ctrl+click on the KontrolEos icon that appears on your desktop (this manipulation with Ctrl is necessary to open an application not known to Apple).
2.2 - Overview
[A]- Network configuration.
[B] - Presets management.
[1] - Active mode view (Fader or FCB).
[2] - Snapshots.
[3] - Alt (alternative) buttons.
[4] - Pages buttons.
[5] - Level wheel.
[6] - Selection of the FADER mode.
[7] - Selection of the FCB mode.
KontrolEos can be seen as an interpreter allowing the controller and Eos to communicate with each other.
On the one hand, it receives MIDI commands from the controller and translates them into OSC to send them to Eos.
On the other hand, it receives OSC messages from Eos that will modify in MIDI the LED display on the controller.
​
​
No command to Eos can be made directly from the KontrolEos graphical interface (by clicking on an encoder symbol with the mouse for example).
To control a parameter in Eos, you must use the controller.
The KontrolEos graphical interface is used to visualize and customize certain parameters such as fixtures attributes, Snapshots and Macros.
These customizable parameters are all highlighted in dark blue (except for the network parameters [A]).
It is these parameters that are stored in the KontrolEos preset system ([B]).
The interface is divided into two main areas: the upper panel, which allows general management of the application (network configuration and management of presets) and the large lower window representing a generic MIDI controller controls.
​
KontrolEos is entirely designed around two distinct modes:
â–º The Fader mode for managing the Eos faders.
â–º The FCB mode for managing the FCB parameters of the automatic projectors.
The two buttons [6] and [7] on either side of the controller (and in the KontrolEos window) select the mode and display the corresponding commands in the main window [1].
Important note: the 10 encoders in window [1] are relative to both modes, and the commands associated with them differ according to the mode selected.
The other encoders are independent of the mode and the associated commands are always the same, whatever the mode selected.
Fader mode
FCB mode
• Page window [4]
​​
Fader and FCB modes are organized in several pages that can be recalled via the Page buttons.
The color of the Page buttons LEDs changes according to the selected mode (FADER: fuchsia, FCB: blue-green).
This is the way of quickly identifying the active mode on the controller.
​
A special page for each mode can be accessed by pressing the Page1 and Page2 buttons simultaneously, namely the MacroFad page and the EncoDis page respectively in Fader and FCB mode.
​- PUSH : page selection.
​- PUSH Page1 + PUSH Page2 : selection of the special page.
- ROTATION : no action.
• Alt buttons [3]
​
The Alt1 and Alt2 buttons can be seen as the ALT key on a computer keyboard: used in combination with some of the other buttons on the controller, they allow you to give them a different functionality than the basic one.
Only the Push of these two encoders has an action. The rotary has no effect.
- PUSH : Alt1 (or Alt2) to be used in combination with others encoders.
- ROTATION : no action.
• Level wheel [5]
The level wheel is common to both modes in order to be permanently accessible whatever the selected mode.
​- PUSH : [Select Last].
- ROTATION : level wheel.
• Contextual help
​
In order to simplify the use of KontrolEos without having to resort to this online documentation, a small contextual help appears after one second when you hover the mouse over an element of the graphic interface.
2.4 - Network configuration
​
To enable KontrolEos to communicate in OSC with Eos simply enter the IP address 127.0.0.1 in Eos setup :
- Go to Setup / System settings / Show Control / OSC.
- Enter the address 127.0.0.1 in the "OSC UDP TX IP Address" field.
- Check that the "OSC RX" and "OSC TX" buttons are enabled and that the RX and TX ports are set to 8000 and 8001 respectively.
​
In KontrolEos, leave the default settings in the top-left window (if you have no particular reason to change them).
OSC settings in KontrolEos
OSC settings in Eos
Note 1: if you have problems communicating between KontrolEos and Eos, please try disabling your firewall for KontrolEos (or for Max if you use KontrolEos in Max).
​
Note 2: if needed, you can still use the old method with an active external IP address.
Please go to the Troubleshooting section for more information.
​​​2.5 - KontrolEos Presets
The KontrolEos preset system allows you to save and instantly recall all of your settings manually customized in the interface (in the dark blue fields).
These include FCB parameters, Snapshot and Macro numbers, color forcing pads, CustoMap button status, etc.
​
You can save up to 11 presets:
- Save a preset: [Shift] + Click in a small grey box.
- Update a preset: select the preset to be modified, make the changes, then do [Shift] + Click in its box again.
- Copy a preset : select the preset to be copied then [Shift] + Click in the destination box.
- Delete a preset: select the preset to delete and click on "Clear active".
- Delete all the presets: click on "Clear ALL".
You can enter a name for each preset in the text field below the boxes. This name will be saved in the preset itself when you save it.
- Preset 1 is loaded by default when you open the application.
- Preset 11 is an empty preset by default allowing to start from scratch without having to empty all the fields one by one. It is therefore advisable not to overwrite it (although it is of course possible).
All the presets can be exported to a file and then re-imported via the Import and Export buttons.
KontrolEos automatically loads the last imported file when it is opened (not the last saved file).
If a change is made to a preset, a save window will open automatically when you close the interface to propose you to save the file again.
2.7 - Fader mode​
The Fader mode is obtained by clicking on the FADER button [6] on the interface or on the controller.
It allows you to check the controller buttons layout for this mode, to manually configure the Eos snapshots that can be recalled when changing fader pages, and if necessary, to force the color of the LED segment of the encoders to match the fader mode selected in Eos.
The color of the 10 encoders in KontrolEos and on the controller automatically adapts to the content of the selected Eos fader page.
- ROTATION : level of the fader
- PUSH : [BUMP]
- ALT1 + PUSH : [Grp/Assert]
- ALT2 + PUSH : [Load]
Automatic adaptation of the color of the encoders LED according to the faders content
When changing fader pages, the color of the LED below the controller's encoders adapt automatically to the type of content of the Eos faders. The ETC color code was tried to be respected as much as possible: golden yellow for Subs, green for Cue Lists, red for Grand Master, brown for Palettes and Presets, etc. (a bit difficult with the rather basic color of the controller's LEDs).
In addition, a fader with no content in Eos will appear off in KontrolEos and on the controller.
Manual color forcing of an encoder according to the fader mode
Unfortunately, it was impossible to do the same thing with the fader mode chosen (Additive, Inhibit or Effect) because Eos does not send this information when changing pages. If you change the mode of a fader in Eos, it can happen that its color and the color of the LED below the controller encoder differs.
To avoid this visual inconvenience, it is possible to manually force the color of an encoder in KontrolEos using the small dots to the right of each encoder :
- Cross: cancels the "forcing" of the color
- Red dot: forces the color of the encoder to red (i.e. for a fader in Inhibit mode)
- Yellow dot: forces the color of the encoder to yellow (i.e. for a fader in Effect mode)
Just like the FCB settings, the color forcings (and their cancelation) need to be saved in a KontrolEos preset so that they can be retrieved in a later session (the dots are on a dark blue background! ;-) ).
​
Warning: when you change presets, it is necessary to recall the fader page you are on with the controller so that the forced color of the encoders is updated (both in the KontrolEos interface and on the controller itself).
Functions of the Page buttons in Fader mode
- PUSH: pages from 1 to 3.
- DOUBLE PUSH*: pages from 4 to 6.
- ALT1 + PUSH: pages from 7 to 9.
- ALT1 + DOUBLE PUSH: pages from 10 to 12.
- ALT2 + PUSH: pages from 13 to 15.
- ALT2 + DOUBLE PUSH: pages from 16 to 18.
- ROTATION: no action
Fader button
* Press it twice as fast as you would with a double click on a mouse.
The 18 fader pages are therefore divided into 6 banks of 3 pages each (bank #1: pages 1 to 3 - Bank #2: pages 4 to 6 - Bank #3: pages 7 to 9 - Bank #4: pages 10 to 12 - Bank #5: pages 13 to 15 - Bank #6: pages 16 to 18).
Even if you don't use all the pages, you can take advantage of this division and organize your pages more easily by choosing, for example, which type of fader will be in each bank (standard subs in bank #1, special subs in bank #2, effects in bank #3, etc.).
​
Note: the animation of the Page button LED segment is specific to each bank:
- Bank 1: steady LED
- Bank 2: flashing LED
- Bank 3: 1 pulse
- Bank 4: 1 pulse then 2 flashes
- Bank 5: 2 pulses
- Bank 6: 2 pulses then 2 flashes
Mnemonic: Alt1 = 1 pulse, Alt2 = 2 pulses. Double push = 2 flashes.
An unique Eos snapshot number that will be called up at the same time as the fader pages can be specified in the small boxes under the encoders (see Eos Snapshot).
A snapshot of each of the 18 fader pages can thus be created in Eos (Tab 28) and recalled each time the corresponding button is pressed on the controller.
The same applies to the special MacroFad page.
Use the mouse hover in the KontrolEos interface to check which page the boxes correspond to.
Fader mode
Special MacroFad page
In Fader mode, the key combination Page1 + Page2 gives access to the special MacroFad page allowing to control the Master fader and the Rate of Eos with the encoders 1, 2 and 3 of the controller.
It also gives access to 6 customizable Macros as well as the Eos Fader hardkey.
​The MacroFad page is accessed by pressing the Page1 and Page2 buttons simultaneously in Fader mode ({5}).
{1} - Master Fader.
When activated, the GO Auto Reset and Q End Auto Reset buttons automatically initialize the Rate to 100% when the GO is pressed and at the end of a cue, respectively. The main purpose of these functions is to avoid forgetting the Rate at a value other than 100% after manipulating it during a transfer.
This feature can also be activated/deactivated directly from the controller by double-pushing the encoder. Activation switches the buttons on in the state in which they have been manually configured in the interface (either one on, the other, or both). Deactivation switches both buttons off.
As soon as one of the two buttons is switched on, the encoder's LED segment flashes.
The state of these buttons are stored in KontrolEos presets.
Important note: In order to obtain the expected behavior with the Rate encoder programmed in KontrolEos, you need to configure Eos fader 8/page 100 as in the screenshot below.
It must be configured with cuelist 1 and in "3x" so that the Rate fader corresponds to the tenth fader on the page:
​Encoder 1:
- PUSH: Go​.
- ROTATION: fader level.
- ALT1 + PUSH: Stop/Go Back.
{2} - Rate Fader.
​- PUSH: no action.
- ROTATION: Rate adjustment between 0% and 200%.
- ALT1 + PUSH: Reset the rate to 100%.
- ALT2 + PUSH: Eos [RATE] key.
- DOUBLE PUSH: activation/deactivation of "GO Auto Reset" and "Q End Auto Reset" functions as configured from the KontrolEos interface.
{3} - Eos [Fader] button.
​- PUSH : Eos [FADER] key.
- ROTATION : no action.
{4} - Customizable Macro buttons.
​- PUSH : triggers the macro configured in the field below.
- ROTATION : no action.
Encoder 2 :
- PUSH: no action
- ROTATION: fader level.
- DOUBLE PUSH : active/deactive "Linked"
When activated, the Linked button connects the right master fader to the left one, turning only the latter to perform symmetrical transfers. The main purpose of this function is to enable you to use just one hand to perform this type of transfer, and to do so more precisely.
For more convenience, this feature can be activated/deactivated directly from the controller by double-pushing encoder 2. The double Push has a "toggle" action, i.e. it activates/deactivates the function alternately. Activating the button sends the value from encoder 1 to encoder 2 when turned. Deactivating it disengages the two encoders, restoring their original independant functionality.
As soon as the Linked button is switched on, the LED segment of encoder 2 flashes.
The state of the Linked button is stored in KontrolEos presets.
The box under each encoder allows you to choose the Macro number that will be called.
This number is highlighted in blue, so it will be saved in the KontrolEos presets.
To make sure that no Macro is called, enter "0" (the box turns dark blue).
You can enter the number either with your computer keyboard or with the mouse wheel (hold down the SHIFT key on your keyboard for more precise scrolling).
{1} - Master fader.
​
{2} - Rate Fader.
​
{3} - Eos Fader hardkey.
​
{4} - Customizable Macro buttons.
​
{5} - Selection of the MacroFad page.
2.8 - Eos Snapshots
Each of these boxes in KontrolEos allows you to select a Snapshot that will be recalled in Eos when you press the corresponding button (note the number in the Snapshots box in orange, which differentiates it from the Macro box in light green)..
It is thus possible, for example, to create a "Fader" and an "FCB" snapshot in Eos which will be recalled each time the "Fader mode" or "FCB mode" button on the controller is pressed.
The other two buttons on either side allow you to recall any snapshot of your choice.
Similarly, you can create snapshots with an individual view of each of the 18 fader pages that will be called up when the corresponding Page button is pressed and thus view your virtual fader in Eos at the same time as you operate the controller.
The number specified will correspond to the Snapshot triggered by the first Page button of each bank.
Snapshots of the other two pages are automatically incremented by 1 by KontrolEos.
For example, if you enter "101" in the Snapshot box marked "1>3", the Page 1 button will trigger Snapshot 101, the Page 2 button will trigger Snapshot 102 and the Page 3 button will trigger Snapshot 103.
You can therefore choose Snapshot number "n" for the first page of each bank, and those for pages 2 and 3 will automatically be numbered "n+1" and "n+2".
​
A Snapshot number can also be specified for the KontrolEos MacroFad page.
​
Snapshot numbers are shown in boxes on a blue background, so they will be saved in KontrolEos presets.
If you don't want any Snapshots to be recalled, enter "0" (the box turns dark blue).
VARIOUS NOTES
1 - Futur dev
- Implementation of the TCP protocol to further facilitate OSC configuration between Eos and KontrolEosand make the controller totally plug and play.
- Management of the size and rate of the Effects (difficult because no native OSC in Eos for these controls...).
- Added pages 4 to 6 to the standard FCB mode to interact with the Shutter, Image and Form categories in the Eos Encoder Display when the CustoMap option is activated in KontrolEos.
- Option to add a second MIDI controller for Fader mode (NanoKorg, Xtouch, etc.).
-...
2. Limitations and known bugs
​
Limitations:
Known bugs :
3 - Versions
Version 2.21
​
In Fader mode
Correction of a bug with encoder n°2, which sends wrong data (when it passes around 13%).
​
4 - Contact
​The best way to stay informed about KontrolEos updates and news is the dedicated Facebook page:
For any questions or suggestions, if possible please use the comments below the posts to share with others or direct messaging me for more specific things.
​
If you don't have Facebook, you can contact me via the others links at the top of this page.
​
5. Thanks
A big thank you to Thibault d'Aubert, Eos trainer and head of the lighting department of the Théâtre National de Strasbourg (France), for his suggestions, his constructive feedback and his minutious beta tests.
Thanks also to the users who give me bug feedback and who contribute to the improvement of KontrolEos (Vincent, Sébastien, Tim, Mitch, Gregory, Ross...).
Thanks to Grégoire and Junn for their help on the mac compilation.
And finally, thanks to those who just take the time to tell me that it works fine and that they are happy! :-)
TECHNICAL COMPLEMENT
1. Troubleshooting
This section will give you some ideas for investigating malfunctions in KontrolEos or your controller.
If you still can't get your controller to work and you plan to contact me, please specify :
- Your operating system (Windows or mac) and its version
- The version of KontrolEos you are using
- The version of Eos you are using
- And describe what seems to work and what doesn't
having of course read carefully sections 1 and 2.1, 2.2, 2.3 and 2.4 of this online documentation.
Note: It is also a very good idea to have in mind the small diagram in section 2.2 to know how the controller, KontrolEos and Eos communicate with each other.
In any case, to identify the problem:
- Start by eliminating all potential external sources of problems: use only a minimal configuration with your Eos computer and the controllerconnected directly (without using a USB hub). Disconnect the computer from any network (but leave your network card or Wi-Fi enabled). Disconnect any other USB and MIDI devices.
- Next, open only KontrolEos (give it time to launch) --> at this point the three LED segments of the Page encoders at the bottom of the controller should be blinking alternately, indicating that the controller is receiving MIDI from KontrolEos .
- Now try selecting the Fader mode and FCB mode with the controller's side buttons facing you the most, as well as switching pages with the Page encoder push buttons --> the KontrolEos GUI should respond to these commands, indicating that it is receiving MIDI from the controller, even though it hasn't yet set up anything on the network.
- If this is not the case, your controlleris not communicating with KontrolEos (so there is no need to open Eos) --> see the first point below.
- If it does, you can continue prospecting using the other points below.
• Problem: my controller doesn't seem to communicate with KontrolEos.
The controller communicates with KontrolEos via MIDI.
To check if your controller is recognized by KontrolEos, go to File / MIDI setup.
--> The name of your controller must be checked in the Inputs and Outputs columns in the "On" column.
If this is not the case, it may be that the controller is recognized by Eos or another software (a MIDI device can only be recognized in one application at a time).
Check if MIDI is enabled in the Eos setup. Go to System / Show Control / USB MIDI/SMPTE and check the status of the "USB MIDI/SMPTE" button. If it is activated and you see your MIDI controller in the table on the right it is probably Eos that has taken over the controller and KontrolEos cannot see it.
For this reason, it is recommended to disable MIDI in Eos if you don't need it, and to start KontrolEos first, before Eos, and before any other third-party application.
​• Problem: I can't launch KontrolEos at all.
If for some unknown and weird reason you can't open KontrolEos directly on Windows or mac, it can be opened using the free trial version of Max and the .mxf file in the main directory of KontrolEos:
​
- Go to the Cycling `74 website.
- Download and install the latest version of Max for your operating system.
- Go to the KontrolEos folder and open the "KontrolEos.mxf" file with Max.
Note: the trial version of Max allows you to create and save patches for a period of 30 days. After this period, the Save options will be disabled but you can continue to open patches, including KontrolEos.
The mxf files are read-only Max patches, it is not possible to modify them.
​
Check that there are no problems when starting KontrolEos in Max.
To do this, open the Max console with Ctrl+M and check that no lines in the console are highlighted in red.
If this is the case, there is a problem.
In particular, Max may not be able to find certain external libraries that are necessary for KontrolEos to function, such as the library named "CNMAT" containing the [OSC-route] object.
If this is your case, you can install it manually. To do this:
- Check that your computer is connected to the internet (to be able to download the package).
- In Max, go to the "File" tab then to "Show package Manager".
- In the search bar at the top right, type "CNMAT" and install the proposed package.
- Restart KontrolEos
​
It also happens that Max does not find a library named "11strokes2". This is not a big deal at this point, it is only used for a very localized special function of KontrolEos and does not affect the general functioning of the application.
​​• Problem: KontrolEos controls some parameters in Eos but not others, and seems to react erratically.
​
Maybe the buttons are not configured with the MIDI messages they are supposed to send.
To be sure, you can monitor the MIDI messages that the controller sends directly with KontrolEos:
- In KontrolEos, click in the lower right corner of the Network Setup window, in the area just to the right of the white OSC receive indicator dot. This will open three small fields below with the MIDI signals that are coming into KontrolEos.
- Operate the various Mcontroller FT controls and check that the incoming MIDI messages match those in the four illustrations below for each of the two modes and two sub-modes of KontrolEos.
â–ºThe first number shown is the MIDI channel (Ch) number and the second is the note (or CC) number. For example 1-12 means Channel 1, Note 12 (or CC 12).
â–ºFor each encoder, the message in the center corresponds to the Push and the one in the upper left to the rotary potentiometer.
If you notice differences between the signals sent by the controller displayed in the small monitoring windows and those it is supposed to send, you can try to:
• Do a factory reset of the controller :
​
​• Problem : IP address 127.0.0.1 doesn't work.
Check that you are using a version of Eos higher than 3.1.x. If not, the local address 127.0.0.1 will not work. Update your Eos software to the latest version supplied by ETC and available on the website.
​
For Mac users, it's possible that an older version of the OS is preventing KontrolEosfrom working with the local IP. For information, the OS on which KontrolEoswas tested with the address 127.0.0.1 is Sonoma 14.2.1.
If, for any reason, the 127.0.0.1 IP address still doesn't work, you can always try the old method, using an external active IP:
The IP address to be entered in KontrolEos is that of the online network adapter in Eos.To find out this address, launch Eos, then in the launcher (ETCnomad shell) go to Settings / Network and check the IP address displayed for the online network adapter in green:
IMPORTANT: in order for Eos to send OSC data to KontrolEos, the IP address must also be entered in the "OSC UDP TX IP Address" field (exactly the same address, not another one from the same range).
Note: even if KontrolEos and Eos are on the same computer, it is necessary to have an active connection.
The localhost address or 127.0.0.1 does not work in Eos (unfortunatly).
For more details on my own configuration, please visit the Tips section.
Then, for KontrolEos to receive the OSC information from Eos, you must configure the network settings in KontrolEos, in the top left window:
- Launch Eos (in Master mode)
- Open the CIA at the bottom of the main screen (keyboard shortcut: F9 + up arrow)
- Go to Setup / System Settings / Show Control / OSC
​
The transmit (TX) and receive (RX) OSC ports in Eos must be enabled and must match those in KontrolEos:
- The TX OSC port in KontrolEos must be the same as the OSC UDP RX port in Eos.
- The RX OSC port in KontrolEos must be the same as the OSC UDP TX port in Eos.
The default ports in KontrolEos are those of Eos, namely 8000 and 8001. If you have no particular reason to change them, you can leave them as they are.
​If you have problems communicating between KontrolEos and Eos, please try disabling your firewall for KontrolEos (or for Max if you use KontrolEos in Max).
The network configuration is not saved in the KontrolEos presets except in preset 1 (see next paragraph 2.5 - KontrolEos presets).
To avoid having to reconfigure the network parameters each time you open the application, you can fill them in and then create a preset 1 (or update it if it already exists), export your project and import it again.
As the preset 1 of the last imported project is loaded by default when the application is opened, its network parameters will become the default ones.
When a network setting is entered that differs from the one saved in preset 1, it will turn white instead of light blue.
2. Tips and tricks
​​In this section you'll find some tips on how to use KontrolEos with the controller as well as some "hidden" or slightly "exotic" key combinations, especially with the Alt and Pages rotary knobs (supposed to have no action!... 😉 ).
Beware, even if these key combinations (and the associated commands) keep a certain logic with the rest of the interface, some of them are a little odd! They are therefore for users who are already familiar with KontrolEos.
If you are a new user, please skip this section for the moment !
Special button combinaisons
​
There are two kinds:
- Those common to both modes (Fader and FCB), located on the Page buttons.
- Those specific to each mode, located on the Alt buttons.
Some of them are a special kind of manipulation that we will call "Hop-hop" and that consists in quickly turning an encoder about 1/8 turn counterclockwise and then immediately clockwise about 1/4 turn.
A little tricky, but very handy!
​
• Commands common to both modes:
​
â–ºHop-hop with Page2 encoder: Sneak Enter
â–ºHop-hop with Page3 encoder: Shift+Clear (clears the Eos command line).
Note: no Hop-hop on Page1 encoder for the moment !
• Commands specific to each mode:
​
In Fader mode:
â–º Holding Alt1 + Alt2 for 0.5s: initializes to Home the 10 faders of the current page.
(Note: this command clears the Eos command line beforehand).
â–º Hop-hop with the Alt1 encoder: deploys/folds the CIA.
â–º Alt1 + Fader View side button: activates FCB View (equivalent to FCB View button).
(Explanation: since I place the controller on the left side of my computer, this sometimes saves me from having to use my right hand to switch to FCB View. This way I can access almost all the commands with my left hand and keeping my right hand on the keyboard).
In FCB mode:
â–º Holding Alt1 + Alt2 for 0.5s : clear the Eos command line and sends "select_last home enter".
This command thus instantly puts in Home the selected fixtures in Eos.
â–º Hop-hop with the Alt1 encoder: deploys/folds the Eos Encoder Display.
â–º Hop-hop with the Alt2 encoder: activates/deactivates the "Custom" softkey (in the Encoder Display).
Tips
• Since it is very quick to switch between the standard FCB mode and the Encodis mode thanks to the Page buttons that are always accessible, it is convenient to use both modes in parallel:
- the standard FCB mode to manage your current or favorite parameters, organized on the three pages as it is most convenient for you and as you are used to,
- the EncoDis mode to manage more occasional parameters.
• Nothing prevents you from selecting the same parameter several times among the three pages of the standard FCB mode. So you can decide for example to dedicate each page to a type of machine, and put back in each one the parameters they might have in common (like pan and tilt perhaps for example).
• It's handy to be able to call up Snapshots with the Page buttons in Fader view, but this can sometimes be bother, especially in show playback.
Since it's easy to duplicate a preset in KontrolEos, don't hesitate to make a second preset by clearing these Snaphots boxes.
Also, don't hesitate to make a "basic" Snaphot in Eos that you can come back to whenever you're a little lost, and that you can configure on one of the controller's side buttons, which are permanently accessible.
• All the controller buttons that have an encoder behavior have their central LED lit (blue for the FCB wheels, red for the level wheel).
These LEDs are sometimes difficult to see when the controller is laid flat. A small support to tilt it at 45° (or more) allows to see all the LED rings and to materialize the location of the side buttons at the same time. ;-)
• Setting up KontrolEos with Eos Client.
If you have an installation with two networked Eos, one configured as Master and the other as Client, and you wish to use your controller with the Client, this is possible.
To do this, you need to open KontrolEos on the Client (there's no need to open it on the Master).
Since in this case only the Master receives and sends OSC, the IP addresses must be configured as follows:
- The IP address of the Master must be entered in KontrolEos.
- The IP address of the Client must be entered in the Client and the Master OSC setup.
OSC ports do not need to be modified (RX 8001 and TX 8000 for Client and Principal, and RX 8000 and TX 8001 for KontrolEos).
-
© 2024 Nicolas Bazoge
All rights reserved
