SoundFlow is not Recognizing RX Pro Audio Editor
Title
SoundFlow is not Recognizing RX Pro Audio Editor
What do you expect to happen when you run the script/macro?
As you can see this macro is very simple, it selects RX Pro Audio Editor and activates it ensuring it's in the foreground then proceeds to use a "Press Keys" function [Command Enter].
This version of RX is iZotopes most current and up to date via their subscription NFR that they sent me.
Also I'm only using a "Press Keys" function as a workaround because if I choose "Click UI Element" SoundFlow does not recodgnize the RX interface.
Are you seeing an error?
Could Not Find Running App with Bundle ID
What happens when you run this script?
Nothing Happens (sorry I can't be more detailed than that this is simply the case)
How were you running this script?
I clicked the "Run Script" or "Run Macro" button in SoundFlow
How important is this issue to you?
5
Details
{
"inputExpected": "As you can see this macro is very simple, it selects RX Pro Audio Editor and activates it ensuring it's in the foreground then proceeds to use a \"Press Keys\" function [Command Enter]. \n\nThis version of RX is iZotopes most current and up to date via their subscription NFR that they sent me.\n\nAlso I'm only using a \"Press Keys\" function as a workaround because if I choose \"Click UI Element\" SoundFlow does not recodgnize the RX interface.",
"inputIsError": true,
"inputError": "Could Not Find Running App with Bundle ID",
"inputWhatHappens": "Nothing Happens (sorry I can't be more detailed than that this is simply the case)",
"inputHowRun": {
"key": "-MpfwYA4I6GGlXgvp5j1",
"title": "I clicked the \"Run Script\" or \"Run Macro\" button in SoundFlow"
},
"inputImportance": 5,
"inputTitle": "SoundFlow is not Recognizing RX Pro Audio Editor"
}
Source
//Macro converted to script
sf.ui.izotope.appActivate();
sf.keyboard.press({
keys: "alt+return",
});
Links
User UID: VXN5zGasMzQkQNCz7bJwlhjmmSh1
Feedback Key: sffeedback:VXN5zGasMzQkQNCz7bJwlhjmmSh1:-MyiTHPD28o8KBOCmIxq
Christian Scheuer @chrscheuer2022-03-21 22:02:22.520ZHi Nick,
Thanks for reporting here. Can you share the specific iZotope RX version? We need something more specific than "the newest" since this can mean many things depending on how NFRs are issued etc.
Christian Scheuer @chrscheuer2022-03-21 22:03:41.427ZI'm asking since SoundFlow has support for iZotope RX up to and including version 9. If you're running a beta or otherwise non-released version of, say, iZotope RX 10, that would explain the issues you're seeing.
- NNick Squillante @Nick_Squillante
The specific version is iZotope RX Pro Audio Editor, Version 9.3.0
- Christian Scheuer @chrscheuer2022-03-21 22:38:19.469Z
Hm, that is very weird. Do you have multiple versions of RX open at the same time by any chance?
Controlling RX9 (9.3.0) works just fine here and I know we have tons of users who use this.Can I get you to create a new script, put this code and assign a global keyboard trigger to it:
log(sf.ui.frontmostApp.activeBundleID);Then, make sure RX9 is focused and run the shortcut, then copy/paste the log entry it shows.
It should showcom.izotope.RX9- Christian Scheuer @chrscheuer2022-03-21 22:40:51.027Z
If you've had multiple versions of RX open and not having restarted SoundFlow in between I think there's a small chance that SF could get confused as to which iZotope version it's supposed to be controlling (even if just a single version is open by the time you actually run the script). That could be one guess. To check if that's related, restart SoundFlow and see if it starts working.
- Christian Scheuer @chrscheuer2022-03-21 22:42:18.148Z
To restart SF (the engine part), click the SF icon, then swipe left or click the small grey dot next to the blue dot to go to the 2nd page, then click Restart SoundFlow.
In reply toNick_Squillante⬆:Kitch Membery @Kitch2022-03-21 22:58:53.767ZHi @Nick_Squillante,
Just thought I'd chime in with a potential solution if what Christian suggested does not resolve the issue.
Certain apps (iZotope RX Advance included) sometimes require their main window to be focused before they can receive keyboard shortcuts from SoundFlow.
Right now you are using the "Activate App" macro which activates iZotope but does not activate iZotope's main window. Try instead to replace the "App Activate" macro with the "Activate App's Main Window" Macro Action. Your Macro should look like this;
I assume the keyboard shortcut "alt+return" is something you have assigned to an internal preset shortcut in iZotope RX?
If that is the case this will hopefully resolve the issue. :-)
- NIn reply toNick_Squillante⬆:Nick Squillante @Nick_Squillante
Hey fellas,
So I did what Christian suggested with the script and the image attached shows the log entry I'm receiving.
Also, @Kitch I tried your suggestion, no luck (see screenshot below)
- NIn reply toNick_Squillante⬆:Nick Squillante @Nick_Squillante
@chrscheuer, Apologies that first screenshot is incorrect. Below is what I'm getting when I try the script you gave me.
- NIn reply toNick_Squillante⬆:Nick Squillante @Nick_Squillante
It looks like the App (even thought it's running version 9.3.0) is not recognizing it as 9 but as RX.Pro
- Christian Scheuer @chrscheuer2022-03-22 00:19:45.191Z
Hi Nick.
Yea - thanks for letting me know about this. This is the issue - I've never seen RX being identified like that before. I'm wondering whether that's intentional or not.
Do you have the app installed in a non standard location? I think a good idea would be to uninstall RX and reinstall it fresh - we've seen in the past that some installers may incorrectly overwrite old installations, so if you upgraded RX from an earlier version, it's possible this is a faulty install.@Kitch this is an issue about bundle IDs, not about app focus (for now).
- Christian Scheuer @chrscheuer2022-03-22 00:23:35.268Z
I seem to remember RX had a "Pro" tier way way back in something like version 5 or 6. I'm thinking your install may have the bundle identifier still from that old install/version (it comes from a Info.plist file in the Application's bundle).
Also note that macOS caches these identifiers so if the upgrade was made in-place you may need to restart the Mac to have macOS refreshen this.- Christian Scheuer @chrscheuer2022-03-22 00:24:54.723Z
Hm but your app is also called "iZotope RX Pro" (look in the menu bar). There's definitely many things indicating this is not the most recent version of the RX app you're running. The most recent version is called "iZotope RX 9 Audio Editor".
- Christian Scheuer @chrscheuer2022-03-22 00:27:55.671Z
How a normal install of iZotope RX 9 Audio Editor should look:
Wondering if this is related to you having an old NFR code, if that makes the iZotope app behave non-standard somehow.
- NIn reply toNick_Squillante⬆:Nick Squillante @Nick_Squillante
As I mentioned earlier, iZotope has subscription based plug-ins now too (In the past it was only perpetual licensing). Basically what that means is they let you pay monthly for the most current software that they have... For example if you have the subscription plan from iZotope and their current version of RX is RX 8 when they upgrade to RX 9 you are able to download the update at no extra charge. So again they keep you on the most current version, that said everything is called "Pro" no more version numbers. Below is the "Get Info" tab of the version (9.3.0) of RX I have as well as a screenshot of what my startup page looks like (different from yours).
Now to answer your install location/upgrade question: This is a brand new M1 Max MacBook Pro running Monterey 12.3 with a fresh install of iZotope RX Pro, no upgrades, no non-standard locations. It's essentially as fresh as you can get it to be. Also, I don't believe "Pro" was ever used as a tier identifier. Izotope, for as long as I can remember had their standard versions and versions with the suffix "Advanced." Hope this helps!
- Christian Scheuer @chrscheuer2022-03-22 00:51:41.070Z
Ah that's very interesting. I guess you're the first SF customer to have that new combination then (or at least the first to report it).
We'll have to add support for this new tier in a new build of SoundFlow, I'll log a report here (SF-545) and then we will update this thread when there's a new release ready.
Thank you so much for helping update me on this (I had no idea about that new product line).
- SIn reply toNick_Squillante⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-545
- NIn reply toNick_Squillante⬆:Nick Squillante @Nick_Squillante
Thanks Christian, looking forward to the new build!
- Christian Scheuer @chrscheuer2022-03-22 02:06:35.826Z
Hi Nick,
Can I get you to check if it works with this new build?
- NNick Squillante @Nick_Squillante
That worked, SoundFlow now recognizes the App and brings it to the front allowing the command to send the file back to Pro Tools. Thank you.
That said, I am still unable to select any individual modules or anything for that matter within RX Pro when using the "Click UI Element" action. Thoughts?
- Christian Scheuer @chrscheuer2022-03-22 02:59:05.282Z
Hm, it's possible the RX Pro version has UI accessibility turned off for some reason. Or it's possible we need to do some more digging on our end.
- Christian Scheuer @chrscheuer2022-03-22 03:05:15.850Z
If you have a module window open can you select anything inside that module?
- NIn reply toNick_Squillante⬆:Nick Squillante @Nick_Squillante
Just tested it with one of the modules open and to answer your question, yes it can select parameters within the modules, it's just unable to select them from the main window. A workaround for now can simply be to choose a menu path with a different action to get the modules open.
- Christian Scheuer @chrscheuer2022-03-22 10:06:24.886Z
That's usually how we do it. It's possible what you're seeing is not specific to that version, on my first few tests I wasn't able to select the module buttons themselves either.
- SIn reply toNick_Squillante⬆:SoundFlow Bot @soundflowbot
This issue has been marked as Done