Automation AppleScripts for Pro Tools (Mac)

[Oliver M]

Originally Posted by its2loud

You think KM was messing that up?

Well, it was years ago when I shared my first packages and tried KM with them. They wouldn't be triggered correctly causing all kinds of weird issues.
I would try to just trigger compiled Script files with KM and then also try to just enter the AppleScript code in KM and run this. Maybe you'll notice a difference.

There is definitely no flaw in your code, the only thing I would add is to let the Script wait for the AS window to appear before the Render button gets addressed.

But that the Render button is being clicked several times makes me think that it is an issue with whatever method you use to trigger the code.

[its2loud]

All great suggestions. I’ll try a few things and report back. I agree that it’s the trigger used to execute that is the problem.

Thanks again.

Good idea on the wait part, hadn’t thought of that but I don’t recall it being an issue in the past.

Would you mind telling me what that line would look like if I needed it?

[Oliver M]

Originally Posted by its2loud

Would you mind telling me what that line would look like if I needed it?

Here it is:

tell application "System Events"
    tell process "Pro Tools"
        set frontmost to true
        if exists (window "Audio Suite: iZotope RX De-click") then
            click UI element "Render" of window "Audio Suite: RX 8 De-click"
        else
            click menu item "RX 8 De-click" of menu of menu item "Noise Reduction" of menu "AudioSuite" of menu bar 1
            repeat until exists window "Audio Suite: RX 8 De-click"
            end repeat
            click UI element "Render" of window "Audio Suite: RX 8 De-click"
        end if
    end tell
end tell

[its2loud]

Thanks!

[its2loud]

Thanks for your help Oliver,

I've discovered that creating a hot key in Keyboard Maestro and executing the script with a macro works as expected.

I'm not really sure why the native OS shortykey doesn't work but I'm not gonng mess around with it. Now that I think about, I might have been having this issue way back when, but I'm not really sure.

For now, problem resolved. I might switch to FastScripts at some point but right now I have so many things I use KM for it would just be a pain to have to switch.

Also, the script to open the AS plugin and render works great even without the wait.

Thanks again!

[Oliver M]

Great. 👍



BTW, the wait is just a safety measure, because if the Audio Suite window doesn’t open fast enough, which can happen from time to time, the Render click will be performed regardless of the Audio Suite window state and thus before the window is open, and you don’t want that. 😉

[Audio Editor]

Hello all,

since I upgraded to 2021.7 I´m experience a similar problem to my automation shortcuts on izotope RX triggered via automator. Every time i´m using a shortcut the process gets triggered 3 times. Those shortcuts have been working flawlessly before the update. Has anyone found a solution to this?

[its2loud]

Originally Posted by Audio Editor

Hello all,

since I upgraded to 2021.7 I´m experience a similar problem to my automation shortcuts on izotope RX triggered via automator. Every time i´m using a shortcut the process gets triggered 3 times. Those shortcuts have been working flawlessly before the update. Has anyone found a solution to this?

I was having the exact same issue. My solution was to execute the script using Keyboard Maestro and ditch the Mac OS native shortcut key execution. Thanks to Oliver’s suggestion.

[Audio Editor]

Originally Posted by its2loud

I was having the exact same issue. My solution was to execute the script using Keyboard Maestro and ditch the Mac OS native shortcut key execution. Thanks to Oliver’s suggestion.

Hey Its2loud,

I was hoping to find a solution that works without another programm. But I've only heard good things about keyboard maestro so far.

[Audio Editor]

Hello all,

I have heard many great things about Keyboard Maestro. However, I would be interested in a solution that would allow me to continue working with the automator. Has anybody a Solution ?