Toggle SonarWorks in LUNA

Heya Chris,
The macros you're using are specific to Protools. 'Track Scroll and Toggle'. Their interactions with Luna are invalid and throwing the error - If you convert to script you'll see 'sf.ui.protools' -- and that's as far as the script will go.
I'm faffing with an idea atm that could work for you.
Should be able to share something with you soon.

Adam.

Here's a simple script that will do what your after if the Midi implementation doesn't work.
As Luna doesn't support the UI elements selection - It's a workaround using a structure of mouse clicks and key commands so there are some caveats/prerequisites.

For this to work the following has to be taken into account:

• Luna's main window must be positioned in the same place/desktop every time. Fullscreen or in a unique offset position... however you work. Make sure that your 'default' positioning is how it will remain when you collect your own coordinates. - This is because the click coordinates are relative to the entire desktop.
• You must be in mixer view
• Your MAIN/MASTER or track containing the plugin must be positioned as the first track in view in the mixer. (this is to ensure that when we extend the view to the Left the targeted Track is in position.

Use Shift+Cmd+4 to change your cursor and get your click point coordinates -

// A quick run of 'ESC' key commands to clear any currently selected (if any) Searches, Console selection etc
// that may extend the size of the Leftmost focus browser, throwing off the scripts click coordinates
sf.keyboard.press({
    keys: "escape",
});

sf.wait({
    intervalMs: 100,
});

sf.keyboard.press({
    keys: "escape",
});

sf.wait({
    intervalMs: 100,
});

sf.keyboard.press({
    keys: "escape",
});

sf.wait({
    intervalMs: 100,
});
    
// mouse click of null area to ensure that the following 'Press Key'
// command is valid -- replace x,y position with user specific coordinates anywhere 
// in the grey area below the modifier buttons
sf.mouse.click({
    position: {"x":640,"y":780},
});

// key command to extend mixer view to the far left
sf.keyboard.press({
    keys: "cmd+alt+left",
});

// simulate a CMD Click to isolate the inserts only in mixer view
// replace x,y position with user specific coordinates on the text 'INSERTS' in the Navigation
// window (above the modifier buttons)
sf.mouse.click({
    position: {"x":650,"y":270},
    isCommand: true,
});

// simulate a CMD click on the plugin you wish to Enable/disable on the last track in the mixer view
sf.mouse.click({
    position: {"x":800,"y":500},
    isCommand: true,
});

Even if the Midi thing works for you, this should give you an idea as to how I'm getting things working with this kind of workaround/methodology . Once you understand the method it's easy to start to think of ideas that can automate (almost) any sequence. It's not as graceful as what Protools or other more accesible daws can acheive but it works.
This was all created using Macros btw, converted to script to share. Like you, I'm not that experienced with Javascript just yet!!