3D

Description
Fixtures that are used with gobo position shake enabled could show artefacts on grandMA3 consoles.
If you used the Calibrate Position tool, the values would not update properly when using the calculator.
The calculators in the Edit Camera pop-up did not display a value range in the title bar.
In the 3D viewer, the 3D stage could disappear when changing attributes in the patch.
In the 3D viewer, when fixtures were rotated on the Y axis and used grandMA3 default meshes, the yoke and lens would set off to the base and head with the greatest offset at 45°.
Reset Properties in the 3D position settings in the patch did not work.
Setting Multi LED Beam Mode to Single Beam Dynamic Gobo in the Render Qualities settings did not work as expected. Outer pixels were on, but the light beam would not render.
A number of show files had a memory leak when the 3D viewer was open.
If you deleted all render qualities, the software would crash. Now, if you delete all render qualities, a new render quality is created automatically.
A color wheel selection was only visualized in the beam but not on geometries. They were still visualized in white.
If you set a value for Rot X, Rot Y, or Rot Z using the calculator with the 3D viewer in setup mode and rotation mode set to Group, the fixtures would rotate around their own axis as if rotation mode was set to Single.
The software could crash, when you opened the 3D window with a grouping fixture as a subfixture of another fixture.
If Multi Led Beam Mode of a render quality was set to Single Beam Dynamic Gobo or Mean Color, the direction of rotated beams was wrong.

Command Line and Macro

Description
EncoderBank X At Y would only apply to one attribute.
Park EncoderBank X and UnPark EncoderBank X would only park or unpark the first encoder page of the respective encoder bank.
If you set a long custom command in the handle tab of the assign menu, the command would overlap and in some cases be unreadable. Now long commands are cut off and square brackets [...] indicate that the command is longer than what is displayed.
If you shuffled fixtures on one axis with the shuffle mode Linked and the numbers of fixtures on another axis were different compared to each other, the shuffle would not appear as linked.
If you changed a gobo or a color value by spinning the encoder with the readout set to Natural or Physical, the value could jump unexpectedly.
The index numbers for mask buttons had a 0-1 shift.
In connector configurations that were set and locked by the user in the previously loaded show file, the user lock would be transferred to a new show.
Lines in the system monitor would sometimes overlap when echoing multi-line strings in Lua.
Clone Group X At Group Y would not work properly if one group did not have CIDs.
If you called a preset where  Recipe Template was enabled when it was created, and then edited the preset and disabled Recipe Template again, the recipe of the preset would not be called into programmer and also not be cooked.
Lines in the system monitor would overlap when Lua Echo functions were executed, for example Lua "Echo('Test 123\n456\n789')".
It was not possible to store views using apostrophes in the name.
If you performed a clean start before loading and saving a show file, the onPC software would not load the previous show file but instead perform another clean start if you restarted it.
If you stored a look using pan/tilt values, the look would be stored using XYZ values and vice versa. Additionally, the fixtures would move to the center or XYZ 0/0/0, respectively.
The software could crash when executing Lua commands with the Echo and GetObject function (Lua "Echo(GetObject("")).
If you assigned encoder bar 1 to a view button and saved and reloaded the show file, the reference of encoder bar 1 to the view button would break.
Cloning color presets created using the color wheel resulted in incorrect RGB values being applied to the destination fixture.
Objects that were locked were not excluded when cloning was performed.
With XYZ, turning the X encoder past 10 and then back under 10 did not immediately lower the value.
Pressing Off and then an object in the running playbacks window disabled the object, but also selected it. This bug is now fixed. The object will be disabled but not selected.
In the layout editor, the column filters for Custom Text Vertical and Full Resolution open a calculator instead of a dropdown menu.
Exchanging executors when the executor was greater than 1×1, and an executor other than the bottom left one was addressed at the source and destination using the Exchange keyword, for example Exchange Page 1.106 at Page 1.107 split up the executors and changed assignments.
In layouts, when a group was selected in setup mode and then Clear was pressed, the group remained selected.
The command Cleanup *.* deleted all unreferenced objects, including those that could not be referenced. This bug is fixed. Now, only objects that are user generated and can be referenced in the software can be addressed by Cleanup.
Copying a custom mesh did not copy the material of the mesh.
Copying a default mesh created an invalid mesh.
Loading a show file of previous versions into 2.3, corrupted strings with handles inside macros.
Assigning an encoder function using the command line, for example Assign FaderTemp Page 1.301, assigned the function but did not remove the encoder left and right function that was previously assigned.
Removing a fixture from a cue overwrote stored selective data from the cue if a preset with a recipe was stored in the cue.
Timing calculations of cues were wrong if you combined individual timings and timing masters.
If you executed Next  without a selection and Group as the command line default, the software would crash.
It was not possible to unlock a macro and then add a new line in the editor. Instead, you had to close the editor and open it again.
If you were in a cue that had a number with .9 and stored a new cue using Store Cue +, the cue would merge into the next cue with a whole number instead of creating a cue .91.
Commands with SelectFixtures in combination with Data Pool selected the wrong fixtures. For example, SelectFixtures DataPool 1 Group 1 - Fixture 1 Thru 2 selected all fixtures instead of fixture 1, 2, and 5 to 10.
In rare cases, if you executed Block Cue Thru, a new cue part with the name "Blocked" would be added to a cue.
If you moved and then edited a cue part that had a command, an ownership conflict pop-up would appear.
If you cut a rule in a filter and tried to paste it into a new ruleset, the rule would be lost and could not be brought back back using Oops.
Editing and updating an embedded preset, discarded embedded references of the preset.
If you turned an encoder in one direction and then changed direction, in some cases, the second input would not work.
Disabling a recipe line in a sequence and then using the SelFix command on the sequence, did not select the fixtures of the sequence.
Selecting fixtures would lag if the selected sequence had a large number of recipes and the sequence sheet was open.
In some rare cases, the software could crash when executing an At Cue Thru command.
In a multi user session, instead of stomping only the selected fixtures with a multistep phaser, all fixtures with a multistep phaser were stomped.
Executing Copy _FrameSelection 1 At Frame 2 after a lasso selection could cause a crash.
For attributes that were on break two or higher, the default values would be reset if you saved and loaded a show file.
If you cloned color values to a fixture of a different fixture type, in some cases, the color would not be converted correctly.

Connections

Description
If you sent Art-Net from one console to another and changed the value in the Amount column of transmitted universes, the Art-Net input could get lost.
If you tried to create the first timecode in a session using the timecode viewer, all stations would disconnect from the session.
If a target was repeatedly triggered via MIDI input, setting the same value again, an error message would be displayed.
The RDM protocol requirement of a minimum of 176 μs of spacing was not met between any other packet and an RDM packet.
Switching an encoder bank in the encoder bar window using web remote, does not display the currently selected bank in yellow text.
If a fader wing or command wing was connected to an onPC on Mac and onPC got restarted, the grandMA3 USB devices would not reconnect automatically.
Some cue commands would not be executed when the sequence was triggered by a timecode event through a MIDI timecode source.
If audio equipment connected to Sound Out had more than one mixer element to control volume, the volume of the sound output would change.
In a session, and where Show Midi Data in System Monitor was enabled for the use of MIDI remotes, only the master station would display MIDI data in the system monitor. This bug is now fixed. Now all stations display MIDI data in the session.
The CID for sACN was saved with the show file and then loaded with the local settings. This could result in multiple stations with the same sACN CID. This bug is fixed. Now, each station has a unique CID. Therefore, the output signals of the stations can be clearly distinguished.
Extensions could not be dismissed. They would immediately reconnect to the console.
The context sensitive help did not work via web remote.
Storing a mask button was not synchronized on connected devices in the network.
In certain show files, the OSC output stopped functioning after the file was saved and reloaded. To restore functionality, users had to toggle the OSC output off and back on.
For the first 60 seconds after startup, the faders on the grandMA3 devices responded at different speeds when all were assigned to the same sequence.
After setting the Connection Limit to 5 on grandMA3 onPC, saving the show file, and reopening it on a grandMA3 console, the system displayed the connection limit incorrectly.
Sending a MIDI note that set the master of a sequence to 100%, and then sending the same note again, caused an error message.
While booting a console, wings did not display the desk lock if you locked the desk before they finished booting.
The console unlocked again after it was locked and an external display was connected.
Joining a session could lose the selection of the user profile. After merging, the default user profile was selected.
The software could crash after the session data merge pop-up when object references collided in the session.
Locking the console using Pause and then connecting an external display unlocked the console.
In a session after session data merge, SpeedMaster values could get lost and were reset to their default values.
Label Please did not label the current cue, instead it labeled the Sequence.
The lavender marker in the ID Type column of the fixture sheet that indicate groups that have their mode set to additive was not displayed on connected stations in a session.
The indicators on the bitmap pool object, which are displayed when the bitmap is used, were not displayed on connected stations in a session.
In some cases, the software could crash if the resolution of a connected web remote was higher than the resolution limit set in the Web Remote tab.
The shutdown process of processing units was inconsistent. A confirmation pop‑up appeared depending on where the shutdown was triggered from - remotely from a console or onPC, button, or key.
If you were in a session, changes of MAtricks on a connected console would not always be applied to the layout correctly in setup mode.
Moving a fader to configure OSC output using the playback window and hardware fader, created two different actions in the system monitor, "......FaderMaster, 1 ,........." and "......FaderMaster, 3 ,.........". This bug has been fixed. Both methods now ouput "......FaderMaster, 3 ,.........".

Patch

Description
Filters would not be updated if you made changes concerning layers in the patch.
The software could crash while editing the DMX mode of a newly created fixture type. This crash occurred if you tapped Insert New DMX Channel while New Object Line and Merge Children were disabled and you unfolded a Logical Channel and then folded it again.
The software could crash, if Show 3D Positions and all labels in 3D Positions Settings were enabled, and then all fixtures were removed from the patch.
Some fixture types were not imported correctly from the world server.
In a show file, all multipatched fixtures got lost after using PSR.
GDTF files with "GDTF" written in caps in the file name, for example "Strobe.GDTF", could not be imported.
It was not possible to import compressed GTDF zip files.
Exporting MVR files also exported redundant xml files to the hard drive.
Exporting MVR files lost emitter and filter data if they were not linked.
Meshes of grandMA3 default environmental fixtures were not exported to an MVR file.
Meshes were not automatically updated when importing a GDTF file that had new meshes using the same file name.
MVR export did not work with file names containing special characters in it on consoles.
If media pools were renamed in a show file and you imported a fixture type, in some cases, the fixture type modes would be imported to the universal fixture type instead of the imported fixture type.
If you copied a fixture type that had a DMX break index greater than 8 into the fixture type folder and opened the fixture wizard in the patch, the software would crash.
Editing logical channels of fixture types sometimes resulted in the loss of assigned DMX curves.
The software could crash if you tried to import fixture types that have more than 8 DMX breaks. This bug is fixed. Now, the fixture type will be imported, and any breaks with an index greater than 8 will be ignored.
In some fixture types, the incorrect DMX footprint was displayed in the user library.
In the PSR patch, Reset and Reset Filter reset everything, except the filter input field.
In some cases, if you exchanged a fixture type or deleted something in the patch, the software would crash.
If you edited the IDType in the live patch, the software would crash. Now, the IDType cannot be edited in the live patch.
In some cases, stored default fixture values were deleted from the local show after PSR.
The software could crash when importing a user profile where EditRecipe was enabled.
Importing certain meshes could crash the software.
Universal color presets were not consistent in the attribute conversion of the target fixtures.
Importing previously exported universal presets did not work as expected. This bug is now fixed. Importing universal presets creates universal values on existing fixtures.

Phaser

Description
Speed masters stored in a preset would be overwritten with MAtricks speed values.

Playback

Description
In some circumstances, pressing Flash did not work if a cue was loaded.
When the encoder resolution in the handle tab of the assign menu was set to a value greater than 1%, the click intended to reach exactly 0% or 100% would only result in a value of 1% or 99%, requiring an additional click to reach 0 % or 100 %.
A CueFade before the last cue with an empty cue at the end was not executed and fixtures would snap off if you went through the cue list before and started the sequence again from the top.
After setting the speed master to "Speed1", DoubleSpeed and HalfSpeed would not be applied, unless your restarted the sequence.
Using the (Add Multiple Events At Time Cursor) in the timecode viewer could play back cues multiple times.
Timecode record mode did not playback events the same as in play mode, as events could jump too quickly.
When new values were stored in a cue while a multi-step phaser was running and the cue was being played back, the new cue values were not output immediately. Restarting the cue was necessary for the new values to be output.
The output of fixtures was different when using special values in dimmers, for example when fading up from a dimmer value, Hold was following the outfade time instead of the infade time.
In some cases, if you stored values to a preset and then pressed Off and then the preset, all values would be knocked out instead of only the preset values.
Tracking values through a break did not work for an attribute if there was a changed relative value in the attribute in the tracking range.
Fixture data could have been lost when ‘Unblock‘ was used and did not update the content of cue zero.
Storing "0" as a relative value into a cue, could break the tracking shield.
When trying to remove active values from a cue, for example Store Cue 5 /Remove, the active values did not reset to the previously stored values. Instead, the fixtures fell back to their default values.
If a cue had preset data stored and a cue recipe that referred to the same preset, updating the preset caused the fixtures to snap back to the old values instead of the updated ones.
The two 100 mm master faders did not indicate their location with a red line in the bottom of the executor.
The output of a group with the mode set to Additive was unaffected by the Grand Master.
Importing a new video into a video pool object currently assigned to a bitmap that was played back caused the software to crash.
If a sequence had more than one break and blocked absolute values, relative values of a phaser would only be released in the last break of the sequence.
Removing data from a cue with an active tracking shield could release attributes in following cues so they were no longer protected.
In some cases, if you started a sound file, a short sound would be audible before the sound file would play back.
In some cases with relative pan and tilt values, Stomp did not work as expected and running phasers did not stop.
Attributes of the main instance did not do MIB, if only the subfixtures had dimmers and they were all closed.
If you were in a session and cues were played back using timecode, in rare cases, these cues would not play back as intended although the software would indicate that they were.
In some cases, when a fixture was part of two sequences — one set to HTP and the other to LTP — moving the LTP sequence fader to 100% displayed a dimmer value of 0% instead of the stored value from the HTP sequence.
In sequences with many cue parts and tracked pan and tilt values, sometimes a cue that had XYZ values in a cue part would not output these XYZ values when using goto.
The software could crash when an encoder had Go+ and Go- assigned and you scrolled fast through a sequence.
Fade transitions of cues could be slightly faster when using Go+.
Selecting a filter in Output Filter for a preset in the Edit Setting tab of the assign menu, did not filter correctly and created wrong output in some cases.
Removing values from layers in presets that were part of a cue kept the preset link and set value to 0 in a cue.
A preset that contained a phaser and was assigned to an executor that had a defined executor time would sometimes snap off instead of fading.

Windows, Views, and Menus

Description
Changing the time zone on a connected station would not change the time in the clock viewer on the master station and the connected station would readjust to the time on the master station.
The range of values offered in the calculators for width and height in the configure display menu was too big and allowed for negative numbers. This bug is now fixed. Now, the possible values range from 0 to 255. Additionally, it is possible to subtract a value from the current width or height.
The title bar button Page in the playbacks window displayed the text "Page X" in front of the custom name.
Timecode objects would not have an indicator bar in the off menu and running playbacks window.
The names of some columns in the fixture type editor were lowercase, and the order of the columns was improved.
Executors of a bigger size that spanned across two executor banks were not displayed correctly and could not be resized in the assignment editor.
Instead of MasterSpeed, the title bar of the assign menu would only display Master as the category if you assigned a speed master.
Blocked values were displayed with red text in the Dimmer+ and Sheet/Filter mode in the fixture sheet.
If Merge Cells was set to Feature in the fixture sheet settings, the PanTilt and RGB cells would not display any of the markers.
It was not possible to select an executor in the handle tab of the assign menu by tapping on the title bar of the executor.
The list of functions of the Key Unpress pop-up in the handle tab of the assign menu did not match the list of functions below the trigger options.
The user profile setting Preset Readout could not be applied in the fixture sheet and sequence sheet, because the setting Preset in the Display tab did not have an Auto option.
Even if a filter referenced by a mask button was deleted, it wo still shown as active and not grayed out.
The software could crash, when a layout was deleted and then a new layout was created in the drop-down of Layout in the title bar of the layout viewer.
Enabling CLI in the quickey pool settings while a different data pool was selected did not enable CLI for the pool. Instead, it enabled CLI for the quickey pool of the selected data pool.
It was not possible to use settings of the title bar in really small windows by tapping the overhang pop-up button () in the title bar.
Changing Cue Mode in the content sheet with Show Recipes enabled from Manual to another mode, still displayed the recipes of the recent cue selected in the Manual mode.
When typing a note in the Note tab of the Info window for a selected sequence, the focus and cursor would jump to the note section of the first cue after typing the first character.
The camera arrangement in the layout encoder bar did not work with subfixtures.
If no secondary function is assigned to an executor, the first function will not be displayed in the playbacks window and playback bar by pressing MA.
Messages in the messages grid of any category in the message center were listed from bottom to top, instead of top to bottom.
On onPC with a really small software window it was not possible to select the command line for input.
The displayed list of objects in the object tab of the assign menu did not scroll down to the assigned object.
Special dialog for shapers did not work in some fixture types. If you then moved the blades, they would be displayed with a slight offset starting from a designated position.
Moving a selected object in the encoder bar pool could result in the software crashing or the object losing its selection.
In the fixture sheet, cells would sometimes randomly flash different merge cells states after knocking in values in the programmer.
In the assign menu, the assignable functions for button press/unpress were not displayed in the playbacks window. This bug is fixed. Also, the unpress function is shown in all executor displays, once the executor is pressed.
In some cases, although notes were listed, the Note tab in the Info window and the List Reference pop-up displayed a (0) or (x) in the title bar.
The heights of headers of statuses and messages were not the same in the message center.
Cloning presets from fixtures did not work if Presets was selected in the middle of the clone menu and all the other object buttons in the middle of the clone menu were deselected.
It was not possible to scroll the At Filter window with the mouse wheel.
The turquoise arrow in the upper right corner of sequence pool objects that indicates that the sequence is assigned to an executor was not displayed.
Cloning with a dimmer filter active, for example Call Filter 2 'Only Dimmer', and then Clone Group 1 At Group 3 If Sequence 2, also cloned color information.
If you filtered a drop-down list that can be filtered, such as the drop-down list for Code in Quickeys or Selection in the Recipe Editor, by typing some characters into the search field, the indicators for the previous selection and your current location in the list would not be displayed correctly.
With Add Executor enabled in the handle tab of the assign menu, custom commands were displayed in the wrong order. For example Cue 1 Page x.y, instead of Page x.y Cue 1.
When storing a help window with changed zoom as a view, the set up zoom was not stored.
In the show creator, tapping an object in the pool list of around 100 objects caused the pool list to scroll and collect the wrong object.
The fade and delay buttons, such as, FadeFrom/To X and the DelayFrom/To X buttons displayed incorrect formating when setting a value of 59 and then increasing the value with + or the swipe function.
Resizing an executor did not apply the new assignments to the single executors that already existed. Only the new executors inside the greater executor had the new assignments for the new size. This bug is now fixed. Executors inside a greater executor do not apply the new assignment they will get during resize if the single executor was manually changed by the user to a different assignment (cyan colored icon). Executors inside a greater executor apply the new assignment during resize when they are still on their default assignment (no cyan icon).
In some cases, the number displayed in the lower right corner of each tab in the running playbacks window indicating how many playbacks of its object type are currently running was incorrect.
Sometimes, if an executor spanned two sections, it would be displayed incorrectly in the Xkeys and Playbacks window.
The software could crash when loading a show file that contained fixture types with invalid channel functions.
Special executors with no function assigned to them displayed "Proxy xx" on the executor in the custom master section instead of nothing.
Special executors with a secondary function, did not display the function on the executor in the custom master section.
If a locked layout was moved from the default data pool to another data pool, it was possible to enable setup in the layout viewer although it was locked.
Enabling shortcuts on a console and pressing the left shift key, highlighted the right MA instead of the left MA, and vice versa.
Storing a view of the timecode viewer did not store the zoom settings.
When bar windows, such as the align bar window and the special dialog window were open on the same screen, tapping different options in the Align Bar window caused the encoder bar to react in unexpected and incorrect ways.
In some editors, oops did not cancel the last action, and closed the editor pop-up.
The software could crash if all render qualities were deleted in the pool and the 3D viewer was opened.
The sequence editor displayed an empty toggle button in the title bar.
Messages about power loss or a faulty battery were not displayed in the Power category in the message center.
A custom text inside a layout element was not automatically wrapping the text to the size of the layout element. This bug is fixed. The text now adjusts automatically and the element name will no longer be displayed.
It was not possible to copy an executor by tapping the bottom-left executor when its size was larger than 1×1.
In the shaper special dialog, it was not possible to reset a value to 0 using the calculator.
If you selected an appearance in the label pop-up and edited the name of the appearance, an infinite amount of new label pop-ups could be opened. Now only one pop-up opens to edit the name.
If you enabled Add Alpha in the image editor, the transparency would not be displayed until you saved and loaded the show file.
Setting Empty in the object tab of the assign menu still displayed the previously assigned selection in the handle tab of special executors.
Long text was not wrapped on layout elements.
Editing a layout element and changing the SelectFixtures action, then tapping Save as Default, removed the action from the Preferences and Timings menu for fixtures. This is why fixtures could not be selected anymore.
The layout encoder bar did not display correct values, when Setup was enabled in the layout viewer.
In some cases, the calculator of Preferred IP in the Art - Net tab of DMX protocols had no "/".
In some cases, moving views in the pool via swipey command did not work.
When a user was logged in with Rights set to None, title buttons in the 3D viewer were not grayed out. Instead empty buttons were displayed.
Sorting lines by Command column in macros did not work. The order was not alphabetically or numerically sorted.
On OnPC, changing the scaling in the Configure Display pop-up to 0.75 and double-clicking on the title bar of a window to maximize it did not work. Instead, the window became larger than the screen.
When not all FeatureGroups were used by the patched fixtures, the feature group indicator bar displayed wrong indicators.
Adding a "." in the calculator of IP column in network interfaces using the key ., deleted the following character.
The sequence sheet flickered when the DMX Tester encoder bar was used.
Make Handles did not convert handles with cue numeration correctly.
Layout elements were jumping around and resizing, when you tried to move them.
After loading a show file from version 2.2 into 2.3, some fixtures lost their appearances in the layout viewer.
It was not possible to filter for cue numbers in the Goto Cue and Load pop-up for sequences.
The temporary help pop-up did not respect the overlay fade set in the user profile.
Saving a show including "%" as a character could crash the software and connected stations.
EditSetting a second preset entered the Edit mode, and deleted the current programmer values. This bug is fixed. Now, it is possible to edit only one preset at a time.
The Countdown cell of agendas displayed the wrong time between midnight and 04:47:44 a.m.
In some rare cases, if a sequence was running and you tapped the Sheet Mode button in the settings of the content sheet several times, the software would crash.
Using a mask with the filter rule "IfOutput" on a fixture and sequence sheet, switching to a different view, and then calling the view again, displayed the wrong content on the sheets as if the mask was disabled.
If the phaser editor was open in 2D mode, swiping Pages in the phaser encoder bar could crash the software.
The encoder bar did not display current values of the respective encoder components if you drew new layout elements in Setup mode. Instead, it displayed 0 for all the encoder components (PosX, PosY, etc.)
Some filters would not work in the Sheet/Filter mode of the fixture sheet.
The encoders, for example At: Speed, in the Phaser Bar did not reliably open the calculator when pressing the encoder.