Do you need help getting started in grandMA3? Perfect! Here we describe a few quick steps to get you rolling. The manual will explain functionality in detail while the MA e-Learning in the MA University offers you all kinds of training. All information can be accessed through the MA Lighting website www.malighting.com.
Let's go! To leave the Release Notes, tap I agree on the top right corner. The main screen of grandMA3 software opens. On the right side, you can see predefined views on view buttons. To switch between the views, tap the view buttons.
If this is your first time starting grandMA3 software, patch some fixtures first. Or you can load one of
the
demo shows delivered with the software. Either way, press Menu. If you
use
grandMA3 onPC software, there is a symbol
in
the top left corner there. Clicking the
symbol
is
the same as pressing Menu on a console.
Tap Backup and then Load, now
you are
ready to load shows. Would you like to get right on it? Switch Shows
to Demo Shows in the title bar first. To do so, tap Shows
repeatedly until it says Demo Shows. Once Demo
Shows is displayed, it is possible to select any demo show in the list. After you
selected a demo
show, tap Load.
In case a show was already loaded, a pop-up will appear asking if you want to save the current show
first before
loading the new one. It's up to you!
Here we go! Now you are ready to work with the grandMA3 software. It is as easy as that! Again - there are view buttons there, which change the screen content. At the bottom, you will find the encoder bar and the command line. Technically that is all you need to get started. For more information, see the grandMA3 help menu. To access the help in the console or the onPC, tap the view buttons named Help or visit the Online Manuals on the MA Lighting website. If you want to learn the grandMA3 software step by step, please see the Quick Start Guide and join the MA e-Learning - it's free of charge and available on the MA Lighting website.
Have fun with using our grandMA3 software! Find all the improvements and changes of this software version further down.
![]() |
Hint: |
The grandMA3 software will start using the show file (or status) that was in operation before the software was shut down. |
The latest release of grandMA3 version 2.2 rolls out several enhancements that enrich your lighting experience. Besides numerous improvements based on your highly appreciated feedback, many new and clever features have found their way into the software. Read on for a quick introduction and find links for more information.
New
in
this release
The new Tags feature allows you to organize, link and cross-reference objects throughout the software. It is also a great tool for busking shows. All objects that have the same tag can be triggered or selected together.
To open the Tags pool, open the Add Window dialog and go to Pools - Tags.
There are three ways to assign tags to objects:
For more information on how to use tags in the command line see the Tag keyword.
When a tag is assigned to a pool object, is displayed on
the
pool
object. The names and numbers of assigned tags are displayed on Tags in the
pool
object settings.
Editors like the Sequence editor or the Macro editor display the assigned tags of the object in an area
between
the title bar and the grid. They can be edited and perform pool actions like the pool objects. The background
color of the appearance assigned to the tag defines the
background
color of the tag displayed in the editor.
To open the tags pop-up
Already assigned tags can be unassigned or vice versa. The left side of the pop-up shows tags that are
assigned
to the corresponding pool object. The right side shows tags that are not assigned.
In the pop-up, tags can also be locked and unlocked and protected against Kill Instant and Kill Delayed
(see
below).
The default action of objects in the tags pool is ListReference.
The Tag Editor shows the objects the tag is assigned to in the grid offering information about:
Multiple objects can be assigned to a tag at the same time using Add New Tag Reference in the tag editor. In the Add Tag References pop-up, multiple objects can be selected and assigned consecutively. To do so, select an object line and tap Assign.
If you enable Settings in the title bar of tag editor, Name, Scribble, Appearance, Tags, Note, and Tag Type can be set and Forward Commands can be toggled on or off. Tags are recursive, meaning it is possible to assign a tag to another tag.
The following Tag Types can be selected:
When a playback is started by a tag, the Trigger column in the Off Menu and Running Playbacks window will
report the tag.
![]() |
Hint: |
Kill Protect does not protect a sequence from being disabled by Kill Instant or Kill Delayed if executed by a tag. For more information on Kill Protect see Sequence Settings and Kill Keyword. |
If Forward Commands is toggled on, playback commands can be executed for
all references of a tag. It is on by default.
This applies to >>>, <<<, Go+, Go-, Goto, HalfSpeed, Load, On, Off, Pause, Rate1, Speed1,
Toggle, and Top.
Improved
in this release
The Recipe Editor is introduced to improve and speed up the workflow for creating and editing recipes. This is done by using the user interface to define selections (Groups), values (Presets, Bitmaps, Generators), filters (Filters, Worlds), and MAtricks. Recipes are cooked when a recipe is generated based on LTP. The Recipe Editor replaces and is based on the Programmer Parts window.
The Recipe Editor can be found in the Add Window pop-up in Tools - Recipe Editor.
To create a recipe using the recipe editor, enable the edit recipe mode. There are multiple ways to do this:?
For more information on how to edit recipes using the command line see the EditRecipe keyword.
To disable the edit recipe mode, press Esc or use one of the options described to enable it. Once the edit recipe mode is disabled, all pools work as usual.
While the edit recipe mode is enabled, Edit and Esc flash alternately.
Each object type that can be used for a recipe will have
its pool window marked with a green .
The following windows use the recipe indicator:
![]() |
Hint: |
Make sure you set the Pool Action setting in the corresponding
pools to
SelFix/At or At so you can use them for recipes.
|
To create a recipe:
![]() |
Hint: |
The order of recording selections and values has an impact on how the recipe is
handled. The last recipe line determines the output if several recipe lines with the same selection
referring to the same attribute.
|
![]() |
Hint: |
It is possible to create recipes with empty groups.
|
![]() |
Hint: |
It is not possible to directly enter values into a recipe, they have to be stored in a preset first. If no preset is selected, the values are stored into the programmer. |
Executing EditRecipe with a corresponding cue or preset, for example,
EditRecipe Cue 1, EditRecipe 1,
or EditRecipe Preset 2.2, enables the edit mode for the specific object in the
recipe editor. With sequences and executors, for example, EditRecipe Sequence 1,
EditRecipe Page 1.204, the running cue is edited.
Tap CleanUp in the title bar to delete all recipes that use the same selection with multiple presets of the same feature group. Only the last object that generates the output is kept. For example, when Group 1 + Red + Yellow + Blue is selected and then CleanUp is tapped, the recipe lines for Group 1 + Red + Yellow will be deleted. If you tap an already selected preset again to deselect it, the corresponding recipe line will also be deleted. CleanUp is only active when the same fixtures are used with multiple items of one feature group. Otherwise the button will be grayed out. With Edit Recipe disabled this button is not visible.
Off Group ["Group_Name" or Group_Number], Off Preset ["FeatureGroup_Name" or FeatureGroup_Number].["Preset_Name" or Preset_Number], or Off and tap a group or a preset can also be used to remove the corresponding recipe line. If a group has multiple lines linked, all of them are removed in the recipe.
You can define a different selection, for example, by tapping Group 2. A brown frame around pool objects indicates the values for previous selections, for example, Group 1. Tap Group 1 again and the previously defined values for this selection are highlighted in green again.
Open the MAtricks overlay to define specific MAtricks values to the recipe
lines. While using the MAtricks editor to edit a recipe, the editor is displayed with "(Recipe)" and the
green pot icon in the title bar.
Use the Columns tab in the window settings to adjust the columns of the recipe editor individually.
Find more improvements for recipes below in Other Enhancements.
Updated predefined content:
Updated
Carallon fixture library to v19.9.
Improved
Recipes:
Improved
the Sequence Sheet:
Improved the behavior when changing properties of cues or sequences:
When a sequence is running, commands like, CueFade 5, will address the running
cue. When the sequence is off, the sequence itself will be addressed. This applies to properties of
sequences and cues. For example, the name: Label will address the sequence
when
the sequence is off, and it will address the running cue when the sequence is on.
Improved Preferences and Timings:
To set a timing master:
This menu allows you to set the default values for actions triggered by Goto, Go-, >>>, and <<<. They can be set to CueTiming, using the timings set in the cue (only for Goto and Go-), a numeric value, or a timing master. CueTiming sets the timing values of the target cue and ignores the timings of other cues. Values that are tracked into the target cue, and therefore do not have a defined timing in that cue, will use the timing of Part 0.
The default values are:
Improved
Content Sheet:
Added
a special value to Specials in the attribute calculator called
Deactivate:
For more information on how to use deactivate in the command line see the Deactivate keyword.
Improved Layouts:
Improved
the Gel Editor:
Improved
the Appearance Editor:
Improved
the display of selected cells in conjunction with appearances:
Cells that are selected by the user and that display an appearance now also display a thick blue
frame and the appearance in the center.
Improved
Scribbles Editor:
Improved
the Label Dialog:
Improved
Text Input:
Improved
Notes:
Improved
Notes in the Info Window:
Improved
Help:
Improved
the 3D Viewer:
Improved
PSR:
Improved
the Clock Viewer:
![]() |
Hint: |
The corresponding name in the title bar changes accordingly to the selected style, for example, when "Digital AM/PM" is selected, the title bar will display "Clock PM" at midday. |
Improved
the Fixture Sheet:
Improved
the Universes Pool:
Improved
the Network:
![]() |
Hint: |
Be careful when changing the MulticastBase address as it affects the entire network structure. Each grandMA3 device must have the same multicast address to allow communication between the devices. |
![]() |
Hint: |
Please check the network environment of a device if rates of NACKs are
constantly above
0.
|
![]() |
Hint: |
For more information about the individual values, see https://www.iana.org/assignments/dscp-registry/dscp-registry.xhtml. |
![]() |
Restriction: |
On grandMA3 onPC for Windows? the DSCP values are overwritten with the default value CS0. |
![]() |
Hint: |
Changes to DSCP, TTL, Data Merge Default Mode, and Data Merge Default Timeout require admin
rights.
|
Syntax: NetworkSpeedTest [DeviceType] ["Device_Name" or Device_Number]
For more information on how to test the speed of the network see the NetworkSpeedTest keyword.
![]() |
Hint: |
TCP and UDP Speed are displayed in percent. 100% refers to the recommended bandwith.
For more information, see Network
Design.
|
Improved NDI:
Improved the Art-Net input:
Improved
MIDI:
Improved the Message Center:
Improved
the Pool Action settings:
Added
Individual Object Action Settings:
![]() |
User name[Fixture]>Assign Temp At Sequence 5 |
Improved Timecode
Pool:
Improved
Window Settings:
Improved
the resizing of windows:
Improved
New Show Files:
Improved
the Configure Display Pop-up:
Improved
the Syntax when storing new Objects:
Improved
the Add Window Menu:
Improved
the Handle tab of the Assign Menu and Executor Configurations
pop-up:
Improved
the Patch Menu:
Improved
the Hardware Detection of grandMA3 onPC running on Windows:
Improved
Clone Window:
Improved
Preset Pools:
Presets with infinite circular references of recipes have an additional light red icon () in the
background of the pool object.
Improved
the automatic naming of presets, for example embedded presets:
The mechanism uses the name of one preset of
each used function group before using other preset names of the same function groups.
Improved
Playback Bar: Indicators for Masters are displayed in the top right corner of executors and special
executors.
They are:
Improved
the Selection button in the Encoder Bar: If a fixture is placed at a position in the selection grid other than
0/0/0, the button indicates which axis the fixture is positioned on with X, Y, and Z labels.
Improved
Random Generators:
It is now possible to set a speed master for a generator.
Improved
the Command Line History:
Commands, that are executed through macros and cue commands, now display the source
of the
commands in front of them.
For example:
OK : | Call Macro 1 |
(Macro 1 'Select EncoderBar') OK: Select EncoderBar 1 |
Improved
Lua:
Added
the possibility to asynchronously execute remote commands, using the /Async option keyword.
For more information on how to use /Async see the /Async option keyword.
Added
the possibility to assign an object to multiple targets at the same time:
![]() |
User name[Fixture]>Assign Appearance 1 At Sequence 1 + 2 + 3 |
For more information on how to use CopyCrashLog see the CopyCrashLog keyword.
Added the option /Remove as an extended
functionality
to
the CopyCrashLog keyword. In combination with the CopyCrashLog keyword, the /Remove option keyword
deletes
crash logs on the device after copying.
For more information on how to use /Remove in combination with CopyCrashLog see the /Remove option keyword.
Added new keyword ListCrashLog. ListCrashLog
lists all
crash logs in the command line history.
For more information on how to use ListCrashLog see the ListCrashLog keyword.
Improved
the keyword DumpLog:
For more information on how to use /Limit in combination with the DumpLog keyword see the /Limit option keyword.
Improved
the If command:
Improved
the CleanUp keyword:
Example:
![]() |
User name[Fixture]>CleanUp Sequence 1 Cue 2 Part 0 /Type "Recipe" |
or
![]() |
User name[Fixture]>CleanUp Sequence 1 Cue 2 Part 0 /Type "Recipe" /Recipe "NoOutput" |
Added new keyword HelpKeyword. HelpKeyword directly
triggers
the list of keywords in the command line history. Execute HelpKeyword and subsequently tap
on the left in the
command
line.
![]() |
Important: |
It is still possible to trigger the list executing Help + Please, however, it will be removed in a future version. |
For more information on how to use HelpKeyword see the HelpKeyword keyword.
Added the possibility to unassign objects from other objects
(for example Tags from Sequences, or Appearances from Groups) by using commands that combine Assign
and Off:
Assign Off [Object] ["Object_Name" or Object_Number] At [Object] ["Object_Name" or Object_Number]
Example:
To unassign the appearance called "Red" from the group "Spots DS", type:
![]() |
User name[Fixture]>Assign Off Appearance "Red" At Group "Spots DS" |
![]() |
Hint: |
For more information about the new keywords, please read the corresponding sections above. |
Description |
---|
Pointing beams into the 2D camera lead to visual artifacts.
|
If the 3D viewer was open and different groups were selected, illegal array values in 3D caused the console to freeze. |
Incompatible diver versions for AMD RX 5700 XT and RX 570 graphic cards could cause the software to crash when opening the 3D viewer. |
When using Position Calibration, the calibration points were not displayed in the 3D Viewer window. |
Description |
---|
Pressing and holding Help and then pressing
Page+, Page-, or Oops
executed the command additionally to opening the help viewer. This bug is now fixed.
Now the corresponding topic opens in the help viewer without executing the command. |
If you edited a macro, the command preview would sometimes be wrong. |
If you assigned a sequence to an empty sequence, a pop-up would ask whether you wanted to overwrite the new sequence although it was empty. If you pressed Yes, the sequence would be successfully assigned, however, the command line would show an "Illegal Object". |
If you used the Label keyword to label cues of a selected sequence, the command line would show an “Illegal Object Error”. |
Assigning a sequence to another sequence using the command line without writing
"sequence"
a second
time, for example Assign Sequence 1 at
2, did
not work.
|
It was not possible to assign appearances and scribbles to mirrored sequences.
|
Assigning objects to sequences created new and empty sequences in the pool. |
If you selected fixtures by typing the FIDs connected with a + in the command line, for example 1+2+3, all attributes would be knocked in into all fixtures except for the first fixture. |
A pop-up opened by a macro, that required an input which was not a string, only appeared on
the
screen
that was in focus. This bug is now fixed.
The pop-up now appears on all screens. |
Oopsing lasso selection in the layout was not possible. Instead the command line was oopsed. |
If you copied fixtures from one layout to a different layout that already included the copied
fixtures and
tapped on "Create Empty Element" in the appearing pop-up, duplicates of the selected fixtures
would be
inserted.
|
It was possible to store and overwrite view buttons after their view has been locked. |
Assigning a sequence to an empty view button did not delete the screen content. |
Elements were hidden by default when assigning fixtures to layouts. |
Keyboard shortcuts Ctrl+Z and Ctrl+Y both
triggered
Oops. Now only Ctrl+Z triggers Oops.
|
Commands that employ a defined range of objects using handles could fail.
|
If you opened the Off Menu pressing Off twice, one Off would still remain in the command line. This bug was fixed. Now the command line will be cleared after pressing Off twice. |
It was not possible to use properties of encoder banks in variables. |
If you tried to delete an object in a layout that was not in setup mode, a pop-up would inform you that this is not possible, but Delete would still be shown in the command line and Delete would still light up. |
If you created a customized encoder bar and made changes to the patch, this would occasionally break the selector of the encoder bank. |
MAtricks From/To properties are returned as integers instead of floats, for
example, when
using Lua "Printf(ObjectList('Cue 1 Part
0.1')[1].FadeFromX)".
|
If you edited a macro line or cue command and pressed Oops, the characters would not be deleted in the expected order. |
Updating fixtures in other cue parts, except for part 0, could cause them to be moved to part 0 of the cue. |
Updating a specific cue with the command line while another cue was running, for example Update Cue 1, did not update the specific cue, but the running one |
Changes to the device configuration, output configuration and local settings did not
trigger a
pop-up asking the user to save the show file.
|
If you imported a layout that contained multiple fixtures with the same name, only the
first fixture
with that name would appear in the imported layout.
|
If you changed the Action setting in a sequence pool to something other than Select and tapped on an empty tile in the pool, an empty
sequence
would still
be created and selected.
|
When a gel was stored and recalled
outside the sRGB color space, the stored gel was recalled on the edge
of
the sRGB color space.
|
The software could crash after deleting a track or a single event in Timecode due to invalid memory access. |
Cutting and Pasting multiple timecode events while you are in
a
session, may have caused other stations to drop out of the session.
|
In some cases, timecode events behaved as if Assert previous Events was enabled
even if it was not.
|
The software could crash when executing EditSetting for a recipe in a programmer part. |
The command line, command line history, and system monitor would show an illegal property if you opened the color picker in the Special Dialog window in the Book view and tapped on View or Sort By. |
Some invalid syntax in the command line, for example Page 1.201 thru 1.203 at 100,
created multiple unwanted objects.
|
If you stored a cue using tracking shield, in some cases values from a previously referenced preset would be stored as hard values in the cue without the preset reference. The data output was not altered by this. |
If you had multiple fixtures with the same name in a layout, copied
them
and
pasted them to a different layout, only the first line would reference a fixture, the other
lines would
not display the selected fixtures.
|
If you selected a grouping fixture in the fixture sheet, sometimes the
software
would crash or the GUI would freeze.
|
If you imported pages with playback masters from a show file using
PSR,
the
playback master would be an empty executor object.
|
If you were renumbering cues, the incremental delta used to enumerate cues would not be
taken
from
the first one in the list, but all cues would be processed.
|
Sometimes the selected color of a fixture was bound to the sRGB color space, even if the
fixture
was capable of having colors outside of this color space.
|
When having a lot of objects in a layout selected and then opening the layout editor the software scrolled through all selected items, and when finished it was not possible to select items. |
Layout elements did not have dependencies to their assigned objects. This bug is now
fixed.
When exporting and importing layouts or importing layouts using PSR, the dependencies are imported as well. When fixtures are exported as dependency, they need to exist in the destination show file as well. Sequences are not exported as dependencies, as they have usually also a lot of dependencies. |
The software could crash when overwriting an existing user profile during the import of user profiles. |
Importing of environmental fixtures via PSR did not import the 3D models correctly. |
The software could crash after selecting a show file for PSR and initializing the PSR process.
|
When fixing or unfixing a page, the assigned objects did not change their fix indication immediately. |
The software could crash when storing a preset using DMX as data source while having several programmer parts with duplicate values. |
If you cloned a large number of unordered fixtures, the cloning could fail and the command line history would only display a green bar instead of the syntax. |
Importing files with an apostrophe in the name could lead to the name of the file being interpreted as command line input and the file not being imported. |
If you were in a session and added a note to a cue using the command line, the note would not be visible on the connected stations. |
Using Dimmer Cue Only would sometimes track the stored dimmer value into the next cue if a fixture had two or more attributes in which dimmer was set in the special column in the attribute definitions. |
Starting the PSR process could lead to broken handles in commands. |
In imported layouts that were previously exported, the appearance of some layout elements would sometimes not be imported. |
Imported sequences that had previously been exported had wrong values for individual timings below 0.1
seconds.
|
If you overwrote an existing cue, the name of the cue would be reset.
|
If you extracted values from a preset and another preset could be updated with those values, Update would not light up.
|
On some mac devices an error appeared, stating that the hard drive was full. This can happen if the
folder permissions are set up in a way that do not allow a "shows" folder to be
created. This has been improved.
A pop-up now informs the user about this and tells to check the folder permissions. |
Deleting a generator in data pool 2 or higher deleted the entire data pool.
|
When editing Column Sets while being in session, the changes were not immediately
transferred to the other stations.
|
When storing to an existing view with an appearance and the screenshot
functionality was not used when storing, the appearance was removed from the view.
|
When Color Readout was set to CMY and channel sets of ColorRGB attributes
were used, the values were not inverted.
|
When you loaded a show file where the Layout Element Defaults were renamed, a new
set of Layout Element Defaults would be imported. This bug is now fixed.
It is no longer possible to rename Layout Element Defaults. In v2.2, show files with renamed Layout Element Defaults are corrected when loading the show file. After that renaming is no longer allowed. |
If you imported a plugin in the show converter and then selected and imported another one, the first plugin would be added to Local a second time. |
If you executed a command with IfOutput, all fixtures would be displayed on grid
position 1/1 in the selection grid. This bug is now fixed.
Now the fixtures are displayed as a linear selection in the selection grid for all except for selective presets. |
If you changed the FID of a fixture using Lua, the software would crash. |
If you exported a user profile after enabling Hide Environmental in the PSR Patch and imported it into a show file, the software would crash. |
If you included an empty group in a command, the command would not be executed. |
If you created a new page by pressing Page+ and assigned an executor
configuration to that page, assigning an appearance to the new page would cause the executor configuration
to be lost the first time.
|
Changing values for specific cue parts did not take the corresponding cue part into account. Instead, part 0 was used. |
Show file names that contained a ' in the file name could not be loaded.
|
The software could freeze when multiple pop-ups were open at the same time and the user tried to close the
top one.
|
Assigning a Sequence to a ViewButton created a hidden object on this button.
Afterwards it was not possible to move a View onto this ViewButton.
|
The Preset Timings defaults for cues in the Preferences and Timings menu displayed
empty buttons when no additional feature groups were existing. |
The software would sometimes crash when executing ListRef. |
Description |
---|
It could happen that a device was displayed twice in the output configuration if you joined and
left a
session
several times and used Remove
Absent in between.
|
When the Root Bridge of an RSTP changed, the session did not work anymore.
|
If DMX Remotes In From and In To were inverted (255-0), the resulting fader movements for the assigned object would not be executed. |
If you left a session with the master device, changed the sACN configuration and then rejoined the session and merged all data, the devices in the session would have different sACN configurations. |
If you joined a session with a different show file, a Session Data Merge pop-up would appear despite the
show files not being compatible.
|
While in a session, a station could drop out of the session if a sequence was deleted.
|
If two devices in a session were receiving two Art-Net or SACN streams input on the same local universe with HTP, the output of the connected station would flicker. |
PSR import of show file from external USB drive failed with an "PSR input file
invalid" error message.
|
grandMA3 onPC on running on Windows only listed real network interfaces. This bug is
now fixed.
grandMA3 onPC running on Windows also lists virtual network interfaces. |
When the grandMA3 software sent an RDM packet to an RDM fixture, for example when
changing the DMX Personality, it could happen that the RDM packet was sent with the previous value instead
of the new one.
|
Sound input was not transferred to other devices in a session. |
When connecting to a processing unit using an older show state than on the console, an unnecessary
Session Data Merge pop up appeared.
|
Inviting or dismissing grandMA3 stations to a session changed the output when the
current output was coming from tracked values and playbacks with blocked values in the background were still
active. |
Description |
---|
If you deleted data in a fixture type in the fixture type editor and then oopsed the deletion, physical descriptions that were linked would not be oopsed. |
If you changed the pretty name of the dimmer in the attribute definitions tab of the
patch, all sheet modes, except for the fixture, would appear blank in the fixture
sheet.
|
In some cases, if a station joined a session, there would be no option for the merge of show
data. Instead, a
pop-up would ask the user to choose between two show files without displaying the affected
data.
This
could for example happen, if a station with a high priority dropped out of a session and
rejoined the
session after changes were made to preset data that was used as a default in the patch,
resulting in
patch changes.
|
Alphabetical sorting of the Fixture Type column in the
patch
did not
work.
|
If you performed a Partial Show Read with Merge PSR after
changing the
Attribute Definitions in the Patch, the changes would not be kept in the merged show
file. This bug
is now fixed.
The Attribute Definitions of the local show file will be used when using Partial Show Read. |
With Partial Show Read some fixture of the local running show were deleted.
|
If the stages
in the local show file had the same name (or default names), the same size and the same
orientation, when you performed a Partial Show Read, stages of the local running show other
than Stage 1 were deleted and all patched fixtures of the local show were added to Stage
1.
|
PSR did not work with files that were stored on an external USB flash drive. |
If the mode of a fixture type was changed, for example from “Basic” to “Extended”,
fixtures of this type would not share previous values of global preset data anymore. Instead, only the
first
patched fixture would keep values of the global preset data.
|
If fixtures had been exchanged in the patch, recipes of cues containing the exchanged fixtures had to be
recooked or merged again.
|
When editing a fixture type and then deleting the DMX Mode rows,
conflicts would occur when pressing Oops.
|
If a mode of a fixture type had conflicting attributes in geometry, for example two different color
mixing systems, the fixture type could not be imported in any mode, even if other modes did not have
any
conflicting attributes. This bug is now fixed.
Now in the fixture type editor, conflicting modes and their channels are displayed in red and can be adjusted. Additionally, information about conflicting attributes in geometry are shown in the conflicts information window. All other modes work as expected. |
Rearranging the order of stages in the patch would hide all fixtures. |
If a fixture had unused DMX channels, the DMX Footprint shown in the Library in the Patch would be wrong. |
Description |
---|
Entering the desk lock while touching the faders kept the faders highlighted after releasing the fingers of the faders. |
If you oopsed a preset selection for a recipe in the programmer, the value in the
programmer would be lost instead of returning to the previously selected preset.
|
Bitmaps and generators in programmer recipes did not generate output. |
If you used the bitmap generator, switching off the source did not switch off the output. |
The Zoom fader of the bitmap generator did not refer to the center of the input, but to the center of the canvas. |
When increasing the value of virtual dimmers by using the relative layer, the color tone of the other ColorRGB channels increased further even if the first ColorRGB channel had already reached 100%. |
If a sequence was not running, executing Go- or <<< would always trigger the first cue. This bug is now fixed.
Now if a sequence is not running and Restart Mode is
set to First Cue, executing Go- or <<< triggers the first cue.
If Restart Mode is set to Current Cue or Next Cue it behaves the same way as Go+. |
When addressing a non-existent cue in a playback command, either the first cue was executed if the
sequence was off, or the current cue was executed again if the sequence was on. This bug is now fixed.
When addressing a non-existent cue in a playback command, the command line now returns
an error.
|
The output for mirrored sequences was not updated immediately. Instead, the sequence
had to be restarted to see the changes.
|
Description |
---|
The error pop-up "Load show failed." could appear on any screen. This bug is now fixed.
Now the pop-up always appears on all screens. |
If you changed the width of a column in the sequence sheet, the column editor sometimes would not display all columns. |
A screenshot that was previously stored on a view button would not disappear if you disabled the screenshot function and stored the view again. |
Pool window preference settings were not applied directly after saving. This bug is fixed. When storing a pool window on the screen the first preference stored is used in all pool settings except for preset pools. |
The Edit Columns pop-up in the sequence sheet could be opened several times. |
Removing fixtures in the selection grid by pressing - did not consider MAtricks positions, so the wrong fixtures were removed. |
If Setup was
enabled
in the selection grid, the selection of fixtures would not be cleared after moving them
around and then selecting different fixtures. Pressing Clear now
sets all fixtures as partly selected.
Therefore, the
workflow "Select -> Change -> Select" is possible.
|
Symbol and gobo previews were not displayed when imported from the symbols and gobos pool. |
Properties of sounds were not displayed in the sounds tab of the running playbacks window. |
If you toggled through the different column sets within the column set editor, the column area would be blank when cycling through the sets the first time. |
When the login pop-up appeared, the cursor was set to the Password input field. This bug is now
fixed.
The cursor is now set to the User input field. |
It was not possible to change the display intensity and color theme on xPort nodes and I/O nodes. |
The indicators for parked and DMX Tester did not analyze fine and ultra channels.
|
If you adjusted the hue value of a color using the color picker after changing the saturation, the saturation would jump to a different value. |
If you created a square using the shaper dialog and tried to adjust it afterwards, the shapers would sometimes not work as expected and could jump to full or zero. |
If you resized layout elements in y direction in a layout in setup mode, the snap grid setting would not be respected and the elements could be resized without restriction. |
If you scrolled in the help using the two-finger gesture, the scrolling of the page would not be in sync with the movement of the fingers. |
It was not possible to edit a note in the Info Window by tapping anywhere below the last item in the note tab due to a very small text field. Now the text box extends to the bottom of the window and can be easily edited. |
Recipes were displayed in
the Notes tab of the Info window if they were children of cue part 1 or higher.
|
When editing an appearance in the appearance pool, the fader for Background Color showed different values than those entered using the calculator. |
In the Appearance Pool, it was not possible to select a color from the Color Picker if the RGB values were set to 0%. |
If you changed values in the HSB color picker and then used the hue encoder within 2 seconds, the color picker unexpectedly jumped to the wrong position. |
If you changed values in the dimmer encoder bank and then changed the encoder bank, and then
pressed Off + tapped the Dimmer
encoder bank
button, you could not enter the dimmer encoder bank again.
|
Fixtures were deselected when doing a 2 finger scroll gesture in a Layout
Viewer
window while
it had Setup enabled.
|
If you opened the on-screen keyboard for the command line and typed in Help,
the help pop-up would not open.
|
If you assigned elements to an Xkey and then tried to edit the Xkey, the Edit overlay would open on the small Screen 7, making it unusable. This is fixed and the Editor now opens on Screen 1. |
If display 1 was not connected on CRV consoles, windows with
encoder
bar
functions, such as the 3D Viewer window in S
etup
mode, did not display their encoder bar on the letterbox screen of the
console.
|
Help overlay was displayed defective on small screens. |
When using the virtual keyboard to write a description in the Backup
menu,
the text was not saved when tapping Please.
|
Entering special characters in notes using the on-screen keyboard resulted
in incorrect text being entered in the note.
|
The list of stations in the Software Update menu did not refresh
automatically after reboot.
|
Layout elements of fixtures could be displayed at full intensity but the intensity of the fixture was not set to 100%. |
Changing the mode of a fixture could lead to data from a global preset not being applied to that fixture anymore. |
If you had a user-defined area that was bigger than the display and had a special dialog window open on the shapers tab, scrolling down would lead to the visual being displayed on top of the command line instead of being hidden by it. |
If the fixture sheet was in channel mode, in some cases fixtures would be displayed with a red background despite not having active values in the programmer. |
In the Generator Editor, the Speed fader did not allow values above 60 BPM. This bug is now
fixed.
Now the maximum is 255 BPM with the fader and 3600 BPM with the calculator. |
In the Info window, if you wrote a note for a sequence, after the fist letter the text would jump to the cue. |
If Setup was enabled in the Layout Viewer, shutting down and restarting the console would shift the view by 50 px. |
The ViewMode pop-up of the
Agenda window did not display its items with the correct width.
|
If you loaded a new show file and Clock Source was set
to Timer, the Clock Window would not display the default stopwatch
from the Timers pool.
|
Some editors, for example for macros and MAtricks, would stay open whenever logging in with a different user. |
If you created a view with a help window and stored it with a changed the zoom factor, the content of the help window would not be zoomed if you recalled the view later. |
If you wanted to select elements in a window and the lasso was ended outside of the valid area, the selection would not be made. |
The output layer in the Layout Viewer did not show the output of unpatched fixtures. |
If you had a grouping fixture that had a multi-instance fixture as a child, in some cases Hide Subfixtures would not hide the subfixtures of the multi-instance fixture. |
If Show Title Bar was toggled off in window settings,
it was not possible to tap elements below the MA logo in the lower right corner.
|
If you opened the network menu in the tab Station
Control, it would be possible to operate some elements of the Stations
tab if you tapped on the black areas.
|
When activating the Setup mode of the Layout Viewer again, former selected
layout
elements could be displayed as selected.
|
Reset 1, Reset 2, Reset 3, and Reset 4 in the Encoder Bar of the Shapers Dialog did not work. |
The Recipe area in the Content Sheet did not display the recipes immediately after
starting the sequence.
|
If you pressed Please in the Label Dialog while having
text in the Notes area selected, the selected text would be deleted and the remaining text would be
applied at once. This bug is now fixed.
Pressing Please in the Label Dialog while having text selected does not delete the selected text anymore, but applies the current state. |
The software could crash if you switched the Window Mode in the Info window. |
The Layout Viewer window did not display the information about the selected layout elements so that it was readable. |
Enabling Transpose in the sequence sheet settings would lead to unnecessary line breaks and text being cut off. |
When adjusting values in the Special Encoder bar of the Shaper Dialog, it could happen that the shaper
jumped or the shapers did not move.
|
AutoCreate for dimmer presets did not work when Dim2,
Dim3, ... were used in the show file, and when they had the Special property set to Dimmer in the
Attribute Definitions.
|
Recipe icons would display the wrong status in the sequence sheet if recipes in a cue part could not be cooked. |
Vertical alignment for text did not work for layout elements that had fixtures assigned. The text field was always above the fixture. |
![]() |
Hint: |
The following is deprecated and will be removed in the software in the near future. Make sure you read the sections stated below, so you can adjust your macros and plugins accordingly, if necessary. |
![]() |
Software update via network to onPC stations requires confirmation during the install process at the destination system. |
![]() |
When multiple GlobalMasters exist on the network, each with the same session and location
name,
the
station with the higher priority takes over automatically.
If all stations have the same priority, the station with the longest Online Time becomes the GlobalMaster of all stations. |
![]() |
Recast will only recast presets to cues if there is a preset link in the absolute layer. |
![]() |
Loading show files that were saved in previous versions deletes the programmer content. |