Posts by Andreas

Quote from MarkvanderMeulen

Could someone explain how the relation is between the values shown in the colorpicker and the values in the encoderbar/fixturesheet/dmxoutput?

if you want a 1:1 relation, set the colorpicker to use the colorspace of the fixturetype

(top-right button in colorpicker)

if you change the colorpicker from Fader to CIE, you can easily see how the different colorspaces map the RGB triangle, and thereby the values in the colorpicker's Fader mode.

https://en.wikipedia.org/wiki/Color_space
https://help2.malighting.com/P…rate_color_picker/en/1.8/

tips:

as macroline-names cannot contain the character tilde (~) which is normally used for unequal (~=), you can instead use the logical operator not in conjunction with equal (==), e.g.

[a == b] do something

[not a == b] do something else

the plugin upload in initial post contains a typo that prevents the menu-choice "Enchant existing macro" to work

to not only create new mules, but also enchant existing macros, please change line 169 of plugin version 1.0.0.0 from

Printf('MULE: enchanting '..macro.ToAddr())

to

Printf('MULE: enchanting '..macro:ToAddr())

or download this updated plugin version 1.0.0.1:

for the exact scenario given in hoss example, a plausible workaround could be to apply the fixture at fixture command directly to the cue, instead of taking a detour via the programmer and the update procedure.

Fixture 2 at Fixture 1 If Cue /o

assuming your non-numerical order is created by a single lasso-action in the layout view, you could rather apply the patch command directly to the lassoing, by entering the Patch keyword into commandline, before you draw the lasso

it is a tool that enables you to create more advanced macros, by using the Lua engine to interpret and playback the content of your macro.

try

Set Selection MAtricks Property "PhaserTransform" "Mirror"

mule (noun) /myül/ - a macro under lua enchantment

Please scroll down this thread to find the latest version of the MULE creator plugin.

Quote from ispeedyg

I am curious. Would this be the syntax I would use to listen for 'next' pressed on MA3?

No it doesn't work like that

signalTable in the scenarioof the OP merely represent the vessel that transports functionality from the plugin to any ui-elements the plugin opens onscreen

This has no relation to hardkeys (like Next)

not very elegant, but something like this could probably do the job:

Store World "MyActiveProgrammer" /o

World "MyActiveProgrammer"

At Width 33 Step 1

World "Full"

Delete World "MyActiveProgrammer" /nc

use quotes like this:

SetUserVar "SongName" ("SongName?")
SetUserVar "SongNr" (SongNumber?)
Label page $SongNr $"SongName"

The Timer function is intended for loops that should be executed totally separately from your main script.

if you want something in your script to follow after a loop, use an internal loop via generic Lua commands like for, while or repeat, and yield processing to other plugins, in the time you want your loop to wait.

- use CmdIndirectWait instead of Cmd, to allow the previous command to process before the next command is executed

something like this (not tested)

local function main()

  CmdIndirectWait('Highlight On')
  CmdIndirectWait('MAtricks "x/ w2"')

  local selectedFix = SelectionCount()
  SetVar(UserVars(),'SelectedFixtureCount', selectedFix)

  for i = 1, SelectedFix do 
    CmdIndirectWait('Next')
    coroutine.yield(0.15) 
  end

  CmdIndirectWait('Reset Selection MAtricks')
  CmdIndirectWait('Highlight Off')
                                                                                                                                          end



return main

No I would not do that

I would use a plugin for my Lua code, Plugin "Touch the file" "something.txt"

And I would use Lua not commandline, to add such plugin call to a cue command.

As Ryan said, there is no spoon

When you apply the Select command to an executor, it will pass it to the sequence and select that sequence, not the exec.

try to assign the same sequence to two different exec. e.g. 201 and 211 and you will see that both seems to get selected, as it is the sequence that actually gets selected.

Nevertheless, your earlier post indicates that your macro knows the name of the sequence.

As executors take the name of the assigned object you can use that name to access the exec:

Set Sequence Property "Name" "2 Part"

Assign Configuration "Flash Button" At Executor "2 part"

If you want to set a predefined text, and not trigger the label popup, instead of Label, use the Set function (on the Name property):

Set Sequence Property "Name" "2 Part"

try

local currentcue = cue.No/1000

something like this should do the job

Lua "SetVar(UserVars(),'Total', 100/GetVar(UserVars(), 'Variable'))"

replace UserVars() with GlobalVars() if you are using global variables

something like this might do the job:

CD ScreenContent Default

Set 1 Property "scrollv" "80,80"

CD Root

I think this is an undocumented change of behavior for the ReloadPlugins keyword.

Lua is used by both plugins and the userinterface.

To force a full reload of the Lua-engine try using the ReloadUI keyword