Video transcript

During busking, the combination of static scenes and running phasers once in a while produces really nice looks that one may want to recall. However, as they are a random result, they are hard to reproduce by standard means.

I will show you a workaround that allows capturing of the complete DMX output, store that in a cue of a sequence for quick access.

• These cues can also be stored to presets.
• The presets can be used for building a phaser

Okay, let’s start.

First, we need some space for two new windows.

We create a window with an „All-Preset “. In this case All-Preset 5  – or – nummerically preset pool 25

Next, we need a new layout view.

Let’s see where the next free layout window is. In my case it is number nine.

I type into the command line: store layout 9 and switch over to it.

Let’s activate the setup mode of the window and click on the „plus“-icon on the left side to add content.

We draw 3 rectangles.

Don’t worry about the exact size. We will fix that in a second.

Just delete this artifact. Ooops.

Switch back to normal edit mode and lasso the rectangles.

Do a right click with the mouse to open the settings dialog.

In the second tab, we can set the size for the three rectangles.

Now, in the first tab, we can assign an appearance to them. I have a lot of them in my showfile. However, in this case, we keep it simple. I scroll to the end of the list an choose „New“.

Assign a white background and close the dialog.

Next, we add some functionality.

We need a sequence as a container for the stored looks as well as a macro that stores the DMX output to the sequence cues.

Find an empty place for the macro and the sequence. In my case number 5001 will work for both.

In the commandline type:

store sequence 5001, press enter.

Then, store macro 5001, enter.

Now type edit macro 5001 and an empty macro editor window will appear.

we type „blind on“. This will hide all things we do from the programmer“ and so it won’t get messed up.

Next line is „Capture“, This creates a snapshot of the dmx values currently be output“

Then: store sequence 5001

Just a reminder: when you store the second look, you will be prompted with options. Choose „Create second cue“. This appears only once.

We release the values from the blind programmer: „ClearAll“

Next: „blind off“ and we are done.

Blind On
Capture
Store sequence 5001
ClearAll
Blind Off

The layout window is ready to get functionality.

Right click on the first rectangle, making sure you are still in setup mode.

Blind On
Edit Sequence 5001 Cue 1
Store Preset 25.1 /Overwrite
Edit Sequence 5001 Cue 2
Store Preset 25.2 /Overwrite
Edit Sequence 5001 Cue 3
Store Preset 25.3 /Overwrite
Edit Sequence 5001 Cue 4
Store Preset 25.4 /Overwrite
Edit Sequence 5001 Cue 5
Store Preset 25.5 /Overwrite
Edit Sequence 5001 Cue 6
Store Preset 25.6 /Overwrite
Edit Sequence 5001 Cue 7
Store Preset 25.7 /Overwrite
Edit Sequence 5001 Cue 8
Store Preset 25.8 /Overwrite
Edit Sequence 5001 Cue 9
Store Preset 25.9 /Overwrite
Edit Sequence 5001 Cue 10
Store Preset 25.10 /Overwrite
Clear
Blind Off

We assign our Macro 5001 to the button and set its mode to go plus.

In the second tab, we switch off the name display and in the third tab, we set a custom text.

Set the placing, the color and the font size.

Then, we assign the sequence to the next button.

The button function is set to goto.

This will present a clickable cue list when in run mode.

Turn off the default text and again edit the custom tect in the third tab.

Ooops, again …

Same for the third button.

The action will be a go plus. This will go to the next cue in the sequence when the button is clicked.

Again, some housekeeping.

Now we should be ready for some testing.

Switch off the edit mode.

We don’t care about the strange display of the button text. Hope it will fix itself in a while.

Okay, start a phaser and generate some looks and store them to the sequence.

Just confirm the second cue.

Set Wings to four.

We can display the list with the second button.

And we can cycle through the cues step by step with the third button.

When right clicking on the second and third knob, we can add fade time and so on.

Here we could delete some cues if necessary.

We can also access the sequence setting by the button in the upper right corner.

Now, let’s copy the cues to presets

We create the placeholder presets that are just empty.

Store preset 25.1 thru 10 – press enter

Assign preset 25.1 thru 10 – don’t presse enter.

Click into the layout view instead.

Bring the layout into edit mode.

Draw a rectangle.

Exit for now and create another macro.

Store macro 5002 – enter.

Back into the edit mode.

Assign an appearance. Why not green.

Assign the macro 5002 to the button.

Action is go.

Housekeeping.

Still Housekeeping.

We need to edit macro 5002.

edit macro 5002 – enter.

Blind on.

edit seq 5001 cue 1.

store preset 25.1 /overwrite.

copy and paste the 2 lines.

Edit the others.

I will have the complete Macro in the description and on my homepage.

To be more flexible, I wrote a plugin that handles any number of cues and presets. You find it in the description and homepage, too.

Leave edit mode and fire the button.

Now we have the presets.

We can swipe to edit the preset and give a fade time.

We can also create a phaser from the presets, like for normal presets.

2 steps.

3 steps.

4 steps.

Thanks for watching!

Macro

Blind On
Edit Sequence 5001 Cue 1
Store Preset 25.1 /Overwrite
Edit Sequence 5001 Cue 2
Store Preset 25.2 /Overwrite
Edit Sequence 5001 Cue 3
Store Preset 25.3 /Overwrite
Edit Sequence 5001 Cue 4
Store Preset 25.4 /Overwrite
Edit Sequence 5001 Cue 5
Store Preset 25.5 /Overwrite
Edit Sequence 5001 Cue 6
Store Preset 25.6 /Overwrite
Store Preset 25.6 /Overwrite
Edit Sequence 5001 Cue 7
Store Preset 25.7 /Overwrite
Edit Sequence 5001 Cue 8
Store Preset 25.8 /Overwrite
Edit Sequence 5001 Cue 9
Store Preset 25.9 /Overwrite
Edit Sequence 5001 Cue 10
Store Preset 25.10 /Overwrite
Clear
Blind Off

LUA-Script

return main

local function main()

     local numPresets = 10   -- How many presets do you want

     local seq = 5001        -- Sequence to copy

     Cmd("Blind On")

     for n = 1, numPresets, 1

     do

         Cmd("Edit Sequence " .. seq .. " Cue " .. n) 

         Cmd("Store Preset 25." .. n .. " /Overwrite")

    end

    Cmd("Blind Off")

end

return main

The example above uses 5 parent fixtures, starting at FID 401. Selection starts with the first warm-white beam (subfixture #2: 401.2). The fixture in total has 24 subfixtures. Stepsize „2“ means the gap between selected subfixtures is „1“, every second subfixture is selected.
For some applications the parent fixture has to be selected either. Just select the checkbox.

Download LUA script

-- Messagebox code from Hoss at
-- https://forum.malighting.com/forum/thread/5913-lua-messagebox-and-var/

-- Stefan Krumm, 20231103
-- tutorials@stkrumm.de
-- https://stkrumm.de/grandma3-tutorial/




function BOX()
    local options = {
        title="Select subfixtures",         --string
        backColor="Global.Focus",           --string: Color based on current theme.
        messageTextColor=nil,               --int|string
        message="Please enter values",      --string
        display= nil,                       --int? | handle?
        
        inputs={
            {name="1:   Parent FID                 ", value="401", blackFilter="", whiteFilter="0123456789", vkPlugin="TextInputNumOnly", maxTextLength = 6},
            {name="2:   No. of fixtures       ", value="5", blackFilter="", whiteFilter="0123456789", vkPlugin="TextInputNumOnly", maxTextLength = 6},            
            {name="3:   First child                ", value="2", blackFilter="", whiteFilter="0123456789", vkPlugin="TextInputNumOnly", maxTextLength = 6},
            {name="4:   No. of subfixtures", value="24", blackFilter="", whiteFilter="0123456789", vkPlugin="TextInputNumOnly", maxTextLength = 6},
            {name="5:   Step size                ", value="2", blackFilter="", whiteFilter="0123456789", vkPlugin="TextInputNumOnly", maxTextLength = 6},
        },
        states={{state=false, name="Select also parent fixture "}},
        commands={{value=1, name="O K"}}
    }
    
    local messageBoxResult = MessageBox(options);   
    
    local startfix = tonumber(messageBoxResult["inputs"]["1:   Parent FID                 "])
    local endfix = tonumber(messageBoxResult["inputs"]["2:   No. of fixtures       "]) + startfix -1
    local startchild = tonumber(messageBoxResult["inputs"]["3:   First child                "])
    local numchild = tonumber(messageBoxResult["inputs"]["4:   No. of subfixtures"])
    local stepchild = tonumber(messageBoxResult["inputs"]["5:   Step size                "])
    
   
      
    for i = startfix, endfix, 1
	do
	   if messageBoxResult["states"]["Select also parent fixture "] then
	       Cmd("Selfix Fixture " .. i  ) 
	   end
	    
	    for k = startchild, numchild, stepchild 
	    do
	        Cmd("Selfix Fixture " .. i .. "." .. k  )
	    end
   end
  
    
end

return BOX

This is about error corrections, user questions, and updates for the third tutorial of the series.

Content:

• Commercial plugin for controlling the screen encoders by midi available. No additional software needed.
• Why modifying the original grandMA3 module for Chataigne?
• Commands from key presses are sent twice
• Connect several midi controllers at once
• Disadvantages of standard (absolute) midi encoders

–

Commercial plugin for controlling the screen encoders by midi available. No additional software needed.
The solution for handling the on-screen encoders is just a workaround by setting absolute values. Since March 2023 there is a plugin available, that brings true functionality to the encoders by midi. No additional software needed, only a midi controller that can be configured to send „relative“ values. The best: one can combine this with a setup using Chataigne mapping. It costs 35$, but I think it is worth the money. More info on „Midi Encoders Pro“.

Why modifying the original grandMA3 module for Chataigne?
When it comes to encoders, the original file by YASTEFAN was written for true endless encoders. Those add or subtract a certain value from the attribute on encoder movement, working in relative mode. However, Behringer and other midi controllers send integer values from 0 to 127, based on the position of the encoder, similar to volume potentiometers. The original routine must be rewritten to send absolute values and extend the value range to allow negative values for Pan and Tilt.

–

Commands from key presses are sent twice
In the standard setup, pressing a button on the midi device sends a „note on“, on releasing the button sends a „note off“. Mapped actions are send to grandMA3 in both cases, resulting in getting each command in double. Chataigne allows for filtering the input value. In the filters dialog click the „+“ sign and select „Condition“. Filtering for „127“ (midi note on) will discard the note off, so only one command is sent. See the screenshot below.

–

Connect several midi controllers at once
The X-Touch has a built-in USB hub. So, why not connect e.g. an additional midi keyboard for firing up sequences or looks, especially blinders? In Chataigne each controller can be mapped separately. There is no need to set different midi channels. Control changes with the same number on both devices do not interfere with each other (although you can set it up to do that, if you wish).

In the „Modules“ dialog add a second midi device

Label the devices with their name

Map the A2 note on the MPK mini

Select preset 4.3 on key press of note A2

–

Disadvantages of standard (absolute) midi encoders
Many encoders on midi devices (MPK mini, X-Touch in standard mode) work just like regular volume knobs and not as an endless (relative) encoder. Therefore, their range is limited to values from 0 to 127, each as an integer number. This makes it almost impossible to accurately set e.g. pan and tilt values. If endless encoders are no option, one could build a workaround with assigning one knob to the coarse attribute, another to fine.
Maybe it is possible to join the 2 values in Chataigne. Worth thinking about it …

Watch on YouTube

Setting up midi in onPC is no rocket science. However, there are some steps that can easily be overlooked. At least, I did …

There is an update/FAQ available for this video! Please check that!

More:    Top Page        Part I         Part II

On this page:        Groups/Presets        Modified files        Feedback & Syncing       Manage pages

Watch on YouTube

This episode deals with how to map midi encoders to encoders of GrandMA3 onPC, how to use the executor faders, and how to send feedback to the motor faders of the X-Touch.
Here is some supplemental stuff and background to the video.

–

How to select fixtures, groups or presets in Chataigne


If you want to map a button or key on the midi device to select a group in onPC or to fire up a preset you can do that like this:
From the grandMA3 mapping select „Send command“ and add one of the options below as parameters:
      select a group: „group 1“ or „selfix group 1„
      select fixtures: „selfix 101 103 105 201 202 203„
      activate dimmer presets: „at preset 1.3„
      activate position presets: „at preset 2.1„
      activate „all“ presets: „at preset 21.4“
You can download my (not yet complete) example X-Touch2grandMA3 Chataigne file.

–

Modified Chataigne files

Some of the Chataigne support files for grandMA3 must be tweaked a little bit. The original files are by yastefan, and are made with true endless encoders in mind. So each turn would add or substract a defined value from the attribute. However, the encoders of X-Touch send increasing (absolute) values between 0 and 127. We therefore must adjust the range and also switch from relative to absolute in the grandMA encoders.

On a Mac the files can be found at
/users/your_name_here/documents/Chataigne/modules/grandMA3-Chataigne-Module-main
On Windows the path is a little bit different but you may find it.

module.json
Please replace the „Turn Encoder“ section with the code below. Note that we added two new devices „Blower“ and „Hazer“.
The main modification is the range of the slider. We allow negative values that are necessary for Pan and Tilt.

 "Turn Encoder":
    {
      "menu":"",  
      "callback":"turnEncoder",
      "parameters":
      {
        "Encoder": 
        {
          "type":"Enum", "options": 
          {
            "Dimmer": "Dimmer",
            "Pan": "Pan",
            "Tilt": "Tilt",
            "Color1": "Color1",
            "ColorRGB_R": "ColorRGB_R",
            "ColorRGB_G": "ColorRGB_G",
            "ColorRGB_B": "ColorRGB_B",
            "ColorRGB_W": "ColorRGB_W",
            "ColorRGB_WW": "ColorRGB_WW",
            "ColorRGB_CW": "ColorRGB_CW",
            "ColorRGB_UV": "ColorRGB_UV",
            "Blower1": "Blower1",
            "Haze1": "Haze1"
          }
        },
        "Multiplicator": {"type": "Float", "min":-10, "max":10, "default":1, "description":"Speed of the encoder movement"},
        "Value": {"type": "Float", "ui":"slider", "min":-100, "max":100, "default":0, "mappingIndex": 0}
      }
    },

grandMA3.js

Please replace function „turnEncoder“ with the code below. The original code used „ at + “ what allows increasing values only. A simple „ at “ is the solution.

function turnEncoder(encoder, multiplicator, value) {
  // script.log("Attribute " + encoder + " at + " + value*multiplicator);
  script.log("Attribute " + encoder + " at " + value*multiplicator);
  // local.send("/cmd", "Attribute " + encoder + " at + " + value*multiplicator);
  local.send("/cmd", "Attribute " + encoder + " at " + value*multiplicator);
}

–

Feedback, Syncing
The X-Touch Compact allows the motor faders to be controlled remotely by midi control change commands. The script below is a plugin that sends the current fader values of the onPC towards the X-Touch. Currently, no perfect feedback is possible.
The plugin can be configured to run one time only or to loop a chosen number of times with a certain delay in between. This is not a perfect solution and I prefer the sync on demand option.
Why?
I found that when I move a fader slowly in the onPC and have sync set to permanent, the faders of the X-Touch produce a lot of noise, that may disturb less loud scenes.
Download lua script

--[[
This plugin reads the executor values from onPC and sends them to TouchOSC by OSC
and to Behringer X-Touch Compact by midi

The plugin does not yet track changes in the faders. You have to call it each time syncing is needed.
Or, you run it in a looop (configure nTimes etc. below)
Or put it as a Cmd in a sequence cue an adjust firing of the cue to your needs.

It is based on code by user "mr-button"
https://forum.malighting.com/forum/thread/7614-osc-out/?postID=16983


V 0.80

**************************************************************************************************
--]]



-- adjust the following variables to fit your setting

local OSCchannel=3
local nTimes = 1   -- you can loop the read out. "1" = single shot
local delay = .3   -- sleep between update loops

-- executors to read
local executor_table = {
		201, 202, 203, 204, 205, 206, 207, 208, 
		216, 217, 218, 219, 220, 221, 222, 223
	}




local function main()
    
	
	
	function Read_Fader_Send_OSC_nn(executor_nr)
	
		local FaderDataStructure = {}
		
		my_ex_obj_1 = GetExecutor(executor_nr)
		
		if my_ex_obj_1 == nil then
			-- Echo("Executor not assigned")
		else
			local fader_current_Value = my_ex_obj_1:GetFader(FaderDataStructure);
			local exact = fader_current_Value  / 100
			Cmd("SendOSC 3 \"/Page1/Fader" .. executor_nr .. ",f," .. exact .. "\"")
			
			local fdr_nr = 0
			-- translate for Bank A of Behringer X-Touch compact
			if executor_nr < 209 then
			    fdr_nr = executor_nr-200
			else
			    -- translate for Bank B
			    fdr_nr = executor_nr-188
			end    
			Cmd("SendMidi \"Control\" " ..  fdr_nr .. " " .. fader_current_Value*1.27 )
		end
	end
	
	
	for xx=1, nTimes, 1
	  do
	    for i, name in ipairs(executor_table) do
		   Read_Fader_Send_OSC_nn(name)
	    end
	  
	    -- get the GrandMaster value 
	    local val = Root().ShowData.Masters.Grand.Master.NormedValue
	    
	    -- Send GrandMaster value to X-Touch, midify it before
	    Cmd("SendMidi \"Control\" " ..  9 .. " " .. val*1.27 )
	    Cmd("SendMidi \"Control\" " ..  36 .. " " .. val*1.27 )
	    Cmd("SendOSC 3 \"/Master"   .. ",f," .. val/100 .. "\"")
	
	  coroutine.yield(delay) -- sleep well for a while
	end
	
end

return main

Midi feedback must be enabled in onPC.
Menu -> Settings -> onPC Settings -> in and out
There is a video about that on Youtube.

–

How to manage pages with X-Touch and grandMA3
Some lighting people are used to preparing individual pages for e.g. each song of a show. However, the X-Touch provides only 2 pages and I use one for the 201 to 208 executor faders and the other page for group masters.
My workaround in onPC is, that I store all my pages from page 501 onward.
This means, when I finish editing my page #1, I will copy it to page #501, doing the same for the other pages with 502, 503 etc.
I have two helper macros. One asks for where to copy page #1 to. The other aks which page shall be recalled, i.e. copied to page #1, my actual working-with page.

Macro 1: Copy page xxx to page one, call Plugin 1 that syncs the X-Touch faders

Copy Page (Page - Page 1 will be overwritten!) At 1
Plugin 1

Macro 2: Copy page 1 to page xxx

Copy Page 1 At (Target Page#)

–

On this page:        Groups/Presets        Modified files        Feedback & Syncing       Manage pages

Modified files Feedback & Syncing

Part II of this series deals how to map control elements of a X-Touch Compact midi controller via OSC to GrandMA3 step by step. The mapping is done by the free software „Chataigne“.

https://benjamin.kuperberg.fr/chataigne/en#about

More: Part I

Note:
There is an error in the spoken comment at 3:24. Should read „control change 9“.

Although I use the Behringer X-Touch Compact, any other midi controller or even a midi keyboard can be used.

A word of warning: I had issues with 3 of the X-Touch devices. Behringer was very helpful, but finally I had to decide to live with it and build a work around. All my devices didn’t initialize correctly afte power on. The faders would only send either „0“ or „127“. I must activate layer „B“ and switch back to „A“ for sending a continuous stream of values between 1 and 100. One error remains. On fader movement a CC26 is sent sporadically.

This is the first video of a series that deal with connecting midi devices like the Behringer X-Touch Compact by OSC to GrandMA3 onPC. Part I gives a general overview. The upcoming episodes will deal with the details and provide configuration files and plugins. Stay tuned!

The software used is: Chataigne for midi to OSC mapping

and TouchOSC MKII

More: Part II

Video transcript below:

This video is about how to control M A 3 by a X-Touch Compact Midi-controller and via iPad or touchscreen using a template in Touchosc.

As the MA3 software does no longer allow direct access to the executors, e.g. the faders, the midi commands from the Behringer x-Touch compact ist converted to OSC messages by the software Chataigne.

The Behringer X-Touch Compact has many control elements that can be mapped to Grand M A using two banks.

Each bank has 9 motorized faders.

There are 39 buttons in each bank.

And there are 16 rotary encoders per bank. Each has also an additional push function that can be mapped separately.

One thing I like with the X-Touch Compact is that one can replicate the typical MA executor assignment with 101, 201, 301, and 401 labelling. So, look and feel is consinstent over the x-touch and the MA onPC executor window.

Please note:

instant feedback is currently one-way only

    from X-Touch to onPC and

    from TouchOSC to onPC

a plugin is available that syncs the X-Touch

and TouchOSC from the onPC fader setting

This is an example preset for the X-Touch compact

The lower most buttons serve as flash buttons

The faders are for controlling sequences and the grand master 

Above the  go plus buttons there are buttons assigned to presets

Positions, Zoom and color presets

The encoders at the right side adjust dimmer, red, green, blue and white, as well as pan and tilt.

Pressing these encoders select groups one to eight

The buttons below are for:

store,  Assign, Clear, and for updating the X-touch and o s c settings.

Now!

How to do the midi to OSC mapping?

There is a software, Chataigne, that is a central hub between almost anything.

Protocols, like TCP-IP, midi, osc

Various kinds of software, and there are a lot of community modules available.

Chataigne runs on a variety of operating systems and it is free!

However, you are welcome to donate to author to keep him motivated further developping that great piece of software.

The link to the homepage is in the video description.

In Chataigne we must select our input and outputmodules

In our case the midi module and the Grandma 3 module.

Select the X-Touch compact as input and output device

Here we see a list of the notes and control changes chataigne is already knowing

 Analog, the settings for the Grandma 3 module

And here is a list of all the mappings already created

So we mapped control chnage one to fader 201 on page 1

And this is the list of all items mapped to Grandma3

This are all the options we have for mapping in the Grandma3 module.

This was just an overview. We will have a build from scratch, step by step tutorial in the next episode.

TouchOSC is another great software, that lets you control your show from anywhere in the venue. Even from the bar. Although I would not recommend that.

We have several pages here.

First the executor pages.

The Encoder page is helpful in programming looks.

Same holds for the „Basic“ page.

The group page holds the group masters and individual groups can be set at any level there.

So lets fire up some sequences from your iPhone or tablet while sitting in the audience.

Do the programming with the remote encoders.

Use „Store“ and „Clear“, bring up the lights

Various things from the group pane.

I hope you enjoyed the video.

The next episodes will cover things in more detail.

Thank you for watching!