"Pick UI Element" is still not working for 5.7.7 on my Mac.
Title
"Pick UI Element" is still not working for 5.7.7 on my Mac.
What do you expect to happen when you run the script/macro?
After starting to analyze an audio file for loudness, I'm trying to pick the UI Element for "Rendering" that appears to have Soundflow wait until it "Disappears" before moving on to the next event. I can't even get that fair as the "Pick Element" interface won't allow me to pick an element.
Are you seeing an error?
"Could not pick UI element: Disconnected"
What happens when you run this script?
Nothing, I can't even run the macro because I can't pick the element. Oh, by the way, when I try to run the macro to test each added element, nothing happens in PT's. If I run the macro from Streamdeck, it works just fine, but using the "Run Macro" button on Soundflow does absolutely nothing.
How were you running this script?
Other
How important is this issue to you?
5
Details
{ "inputExpected": "After starting to analyze an audio file for loudness, I'm trying to pick the UI Element for \"Rendering\" that appears to have Soundflow wait until it \"Disappears\" before moving on to the next event. I can't even get that fair as the \"Pick Element\" interface won't allow me to pick an element.", "inputIsError": true, "inputError": "\"Could not pick UI element: Disconnected\"", "inputWhatHappens": "Nothing, I can't even run the macro because I can't pick the element. Oh, by the way, when I try to run the macro to test each added element, nothing happens in PT's. If I run the macro from Streamdeck, it works just fine, but using the \"Run Macro\" button on Soundflow does absolutely nothing.", "inputHowRun": { "key": "-MpfwoFyZNOpBC3X5xGI", "title": "Other" }, "inputImportance": 5, "inputTitle": "\"Pick UI Element\" is still not working for 5.7.7 on my Mac." }
Source
//Macro converted to script
//Calling command "Select All" from package "iZotope RX" (installed from user/pkg/version "uOwKfD26NbWKAWotin3dmnSne7B3/cl57rzt16000nrq10fns16dg1/clptf90ux0002bi10dm7vm9gt")
sf.soundflow.runCommand({
commandId: 'user:cl57rzt16000nrq10fns16dg1:cl5d6fdjf0001uc10i2odx2ga#cl5d6ra20000fuc10yuhuqmtz',
props: {}
});
sf.wait({
intervalMs: 500,
});
sf.keyboard.press({
keys: "alt+a",
});
sf.ui.proTools.audioSuiteOpenPlugin({
category: "Sound Field",
name: "iZotope RX Loudness Control",
});
(throw 'context missing').elementWaitFor({
waitType: "Appear",
});
Links
User UID: XWbksG0UXMYCLSaHNNZ6iQHCF5P2
Feedback Key: sffeedback:XWbksG0UXMYCLSaHNNZ6iQHCF5P2:-Nw1d_SjIulOoG-Auuv3
Feedback ZIP: T+qpn/y3U76lPLKOAUrC6aXc0KCciCnKU436n9gDSiMgEVlRpfnrs+KzzXH2jv4GUlq+KFgjRtvHeJ2DtWdV3uiA7eH6TYk0qWjm92SHD3MYJb+eg43woYUxUJNcbUPjnwk3L+Uzli6lx5OICKQ24xYx8NhlwI+TSO1e6mmFMGZbjOcr0LEZt+RaT+Iw4qkfJOSadVfFsmCNyJxX0/kmW0lowTUgTiX7c0GWbEzBI3iq7POY0B6CUVtRus1YCealhlczGGcyivDlKRzR1ZqTb+Tt4xMf1p4p5vptvCTVsInWoaVuD9h3LH+Et0XH25JkcQqwsdMPxiw9ubc5aCyeJPQ76nGFqY2fV/jNHleJBNo=
- Christian Scheuer @chrscheuer2024-04-30 02:35:56.284Z
Hi Rhett,
Is this happening when you try to use Pick UI Element on all apps, or just one app in particular?
If we could narrow this down to something we can reproduce on our end, that would be super helpful.- RRhett Samuel Price @Rhett_Samuel_Price
This is occurring in Pro Tools. If you need a video of this, let me know and I’ll send you a link.
Christian Scheuer @chrscheuer2024-04-30 14:46:11.889Z
Thank you! That would be super helpful.
Do you have any AudioSuite windows open? It would also help if we can narrow down the specific setup one needs to have in Pro Tools to make this happen (as obviously, normally and for most users, this just works)
- RRhett Samuel Price @Rhett_Samuel_Price
Well, yes. That's what I'm trying to pick, is an Audiosuite function. I use the iZotope Loudness dialog constantly, and I would like to automate it in with some of the other Audiosuite functions I use to prepare the final audio. However, for this particular dialog, I need Soundflow to "Wait" until a dialog box appears and disappears. I'm trying to pick that box.
Here's a link to the video I made:
Christian Scheuer @chrscheuer2024-04-30 16:08:30.069Z
Ah, okay! Thank you.
This is most likely because while PT is busy rendering, it's not responding to SoundFlow's commands.
I can't see any audiosuite plugin in your screen recording, but I'm assuming you're rendering something off screen.
You should use the built-in action to render the current audiosuite window as it would already take care of waiting.- RRhett Samuel Price @Rhett_Samuel_Price
Got it. I'll try that. I forget you updated everything. Thanks.
- In reply tochrscheuer⬆:RRhett Samuel Price @Rhett_Samuel_Price
Hi Christian,
Now I remember why I couldn't use the regular Render command module. For this particular module there are two components. It Analyzes the audio first, then it renders the analyzed audio. Put two instances of the Render command in the script does nothing, as the program see it as two separate functions and simply analyses the audio again, without ever rendering it with the analyzed audio. Does that make sense?
Hence, why I was trying to do it the like in the video.
- RRhett Samuel Price @Rhett_Samuel_Price
One last thing. I know I could use the picker to select each one once the Audiosuite plugin is available, yet I run into the problem of "how long" do I tell it to wait. The clips are of different lengths and I run into the problem of waiting too long for something to happen, or not long enough and the script stops because processing hasn't finished. Thanks!
Christian Scheuer @chrscheuer2024-04-30 19:31:11.100Z
You can script the waiting on the confirmation/progress dialog manually in this case. I'd recommend doing a search on the forum or google for "soundflow wait on render window" or something like that :)
Here's an example:
Wait for Render window