Moving Light Assistant v1.4 Beta 26 & Beta 27

The latest Moving Light Assistant beta is now available for macOS and Windows OS. This release contains bug fixes and feature enhancements. Please read the ‘MLA v1.4 Beta Read Me’ in the ‘Help’ folder for more details.

A new more flexible Preset Documentation photo zoom window has been implemented.
An option when adding channels to presets has been added to ignore the cells of multicell fixtures on ETC EOS consoles.
Check the online manual for more details.

Important for macOS users.

MLA v1.4 Beta 26 is an Intel build (as have all previous beta versions) and will run on Intel machines natively and under Rosetta on ARM based machines. MLA v1.4 Beta 27 is a Universal build which means it contains the code to run natively on both Intel and ARM based machines. There are no feature changes between Beta 26 and Beta 27. The way the Computer/Machine Identifier (used for license activation) is generated has had to be changed for ARM builds. As a result if you are running on an ARM based machine and have used a previous MLA beta version, you must launch MLA v1.4 Beta 26 (or Beta 24) first and deregister your machine (Apple menu ‘Deregister this computer…’), quit MLA v1.4 Beta 26 and then launch MLA v1.4 Beta 27 and activate your machine. You MUST be connected to the internet when you do this. If you encounter any issues, from MLA v1.4 Beta 26 (or Beta 24), open the Registration dialog and click on the ‘Email Activation’ button. Send the email to support@movinglightassistant.com explaining you are upgrading to MLA v1.4 Beta 27. If you have not run a previous beta version of MLA on your ARM based machine, you can just use MLA v1.4 Beta 27 and activate as normal. MLA v1.4 Beta 27 can be used on Intel based machines without needing to reactivate your machine.

This is the first ARM native build, and as a result you may encounter new issues. There may be compatibility issues with image capture devices, AV Foundation etc, so check everything is working before you are in time critical situations. You can force the application to run translated as Intel code under Rosetta by quitting the application, getting info for the MLA application in the Finder and checking the ‘Open using Rosetta’ checkbox, then re-launching. This may fix compatibility issues.