Hey,
I stupidly let my machine update to Sonoma 14.5, whilst Pro tools 2024.3.1 seems fine, it appears the previous issues with menus and selecting presets has come back. Just wondering if anyone else is having this issue or if a fix is coming. Hopefully can be fixed again with the next pro tools/soundflow update.
Thanks in advance
James
- SSoundFlow Bot @soundflowbot
Thanks for contacting SoundFlow support.
Please note, that the best way to get help with a script, macro or other content installed from the Store or content that you've made yourself, is to select the script/macro, then click the red Need help button, and then click "Get help with this script or macro".
By using this method, we will get access to more information and so should be able to help you quicker.
You can read more about how this works here: bit.ly/sfscripthelpIf you're seeing an error that isn't related to scripts or macros, and you think this is a bug in SoundFlow, please file a Help/Issue bug report.
You can see how to do this by going to bit.ly/sfhelpissue - In reply toJames_Ezra⬆:Christian Scheuer @chrscheuer2024-06-07 09:33:24.830Z
Hi James,
I'm sorry to hear that you're seeing issues with Sonoma 14.5.
You're the first to mention this issue. Would you be able to provide a screen recording? And if possible, also send us a Help/Issue report so we have your log files?
- JJames Ezra @James_Ezra
Hey,
Here is a screenshot of an example of the macro used and the error. It's at the preset stage it seems to hang.
I do have a screen recording but it won't let me upload the mov
Cheers,
JamesChristian Scheuer @chrscheuer2024-06-07 10:15:21.988Z
Hi James,
Thanks for the added details. Could I get you to do the Help/Issue so we have your log files? For screen recordings, please share via a Google drive / Dropbox link if you can.
Christian Scheuer @chrscheuer2024-06-07 10:16:56.545Z
Were you upgrading from 14.4 or from a previous version (ie. 13.x?)
Christian Scheuer @chrscheuer2024-06-07 10:17:37.989Z
I just got some added details from our beta group that 14.5 should be running fine for them, so this may be an isolated problem related to AudioSuite windows - please let us know if you're seeing this in other cases too.
For now, I've updated our system requirements to point out 14.5 may have problems.
- JJames Ezra @James_Ezra
It was an upgrade from 14.4
It does seem related to audio suite only. For instance it works fine when selecting pan, show hide volume etc, I have no issues
Christian Scheuer @chrscheuer2024-06-07 10:26:05.312Z
Ok, that's good to know. We might be able to further narrow it down to see if there's a workaround possible, or if it's something we need to fix inside SoundFlow.
@Chad_Wahlbrink will you help James troubleshoot this? It'd be great to try to isolate it in a script to the exact popupMenuSelect call that fails. Also to try to make sure the window is focused before (elementRaise).
We should also troubleshoot if the popup menu cancellation is happening due to other AudioSuite windows or other software querying Pro Tools causing those cancellations. Lmk if you need clarification.
- In reply tochrscheuer⬆:JJames Ezra @James_Ezra
Just submitted the help/issue.
Google link for the screen recording below
https://drive.google.com/file/d/1yT7rjZG_Zb4c5neZdAW0Sx9E828tC-ul/view?usp=sharingChristian Scheuer @chrscheuer2024-06-07 10:20:53.786Z2024-06-08 01:54:00.076Z
Thank you!
Do you have any "runForever" scripts? (You'll probably know what I mean if you do). And/or do you have any dynamic decks running on Stream Decks / iPads that are updating something in Pro Tools?
We are tracking an issue in Pro Tools where popup menus disappear if Pro Tools has input events occurring (for example if SF queries it for information). This looks like what could be happening, ie. the popup menu shows very, very briefly. (SF-1189)
- JJames Ezra @James_Ezra
No I don't, they are mostly based of the Barry Weir macro's for my most common functions with RX, DxRevive, Clear etc. I work in TV as a mixer so it mostly that for of thing.
Chad Wahlbrink @Chad2024-06-07 13:57:04.177Z
Hi, @James_Ezra!
Thanks for the help/issue report and the screen recording. I've just updated my test machine to Sonoma 14.5 and Pro Tools 2024.3.1 to see if I can reproduce this issue.
My first very basic test would be to have you try moving the AudioSuite windows around on the screen and try to fire the command. So far, I have only been able to get the behavior you are experiencing to happen if the AudioSuite window is on the very right edge of my screen.
I have been using the following test script:
Here's a video from my system:sf.ui.proTools.audioSuiteOpenPlugin({ category: "Noise Reduction", name: "RX 10 Mouth De-click", }); if (sf.ui.proTools.firstAudioSuiteWindow.title.value !== "Audio Suite: RX 10 Mouth De-click") { sf.ui.proTools.windows.whoseTitle.is("Audio Suite: RX 10 Mouth De-click").first.elementRaise(); } log('AudioSuite Open'); sf.ui.proTools.firstAudioSuiteWindow.audioSuiteSetOptions({ processingInputMode: "ClipByClip", processingOutputMode: "CreateIndividualFiles", }); log('AudioSuite Options Set') sf.ui.proTools.firstAudioSuiteWindow.popupButtons.allItems[6].popupMenuSelect({ menuPath:["JE MC"]}) log('Preset Selected'); sf.ui.proTools.audioSuiteRenderCurrent(); log('preset rendered')
- JJames Ezra @James_Ezra
Hey,
If I move the window it does work, however if I don't close the plugin window and press it again, or a similar script I get the error. Once moved, If I close the plugin window after it renders, it seems to work though the next time I trigger a macro.- JJames Ezra @James_Ezra
It does seem screen position is almost irrelevant as long as the window gets moved, it will always fail the first time when opening a session regardless of location, if I move, then close the window. It will work the next time I trigger, even if almost in the same spot. As long as I close the window after the render it seems to work the next time.
Christian Scheuer @chrscheuer2024-06-08 00:41:54.687Z
@Chad might be an invalidate that's needed for firstAudioSuiteWindow?
- In reply toJames_Ezra⬆:
Chad Wahlbrink @Chad2024-06-08 02:10:13.378Z
Thanks, @James_Ezra!
I'm not experiencing the same issues when opening a session on my Sonoma setup. However, I did try optimizing a script a bit to see if it helps.
As Christian suggested, I'm usingsf.ui.proTools.firstAudioSuiteWindow.invalidate().audioSuiteSetOptions
to invalidate the first audio suite window. This method ensures SoundFlow is referencing the most up-to-date UI on the screen.
I'm also waiting for the render to complete and closing the AudioSuite plugin window. You mentioned that closing the window after the render seemed to make the script work better on your system.
Furthermore, you can set the plug-in name and preset at the top of the script for easier customization.
// Define Preset let preset = "JE MC" let plugin = "RX 10 Mouth De-click" //////////////////////////////////////////////////////////// if (!sf.ui.proTools.isRunning) throw `Pro Tools is not running`; // Activate Pro Tools sf.ui.proTools.appActivateMainWindow(); sf.ui.proTools.mainWindow.invalidate(); // Open RX 10 Mouth De-click sf.ui.proTools.audioSuiteOpenPlugin({ category: "Noise Reduction", name: plugin, }); // Focus RX 10 Mouth De-click Window if (sf.ui.proTools.firstAudioSuiteWindow.title.value !== `Audio Suite: ${plugin}`) { sf.ui.proTools.windows.whoseTitle.is(`Audio Suite: ${plugin}`).first.elementRaise(); } // Invalidate the UI Cache and set the processing modes sf.ui.proTools.firstAudioSuiteWindow.invalidate().audioSuiteSetOptions({ processingInputMode: "ClipByClip", processingOutputMode: "CreateIndividualFiles", }); // Set the Preset Path sf.ui.proTools.firstAudioSuiteWindow.popupButtons.allItems[6].popupMenuSelect({ menuPath:[preset]}) // Wait for Preset to Load while(sf.ui.proTools.firstAudioSuiteWindow.popupButtons.allItems[6].value.value !== preset){ sf.wait({ intervalMs: 50 }); } // Render the AudioSuite Window sf.ui.proTools.getAudioSuiteWindow(plugin).audioSuiteRender(); // Close the Window sf.ui.proTools.firstAudioSuiteWindow.windowClose();
- JJames Ezra @James_Ezra
Hey,
Thanks for that, this seems to solve the issue. As long as the plugin window isn't open when you open the session. But if everything is closed it works. Tried it on other audio suite plugs and works too.
Thanks again
- In reply tochrscheuer⬆:
Chris Shaw @Chris_Shaw2024-06-07 15:56:20.750Z
@chrscheuer / @Kitch: Could you send me a link to this issue via Slack? I may have a similar issue re:
runForever scripts
and popups.
ThanksKitch Membery @Kitch2024-06-07 16:20:58.717Z
Hi @Chris,
I'm not sure which issue Christian is referring to, but please log a separate report and we'll link it to the other issue if it's related. :-)
Thanks in advance.
Chris Shaw @Chris_Shaw2024-06-07 16:47:11.591Z
Cool, Just trying to avoid redundant posts. Thanks
- In reply toChris_Shaw⬆:
Christian Scheuer @chrscheuer2024-06-08 00:26:07.161Z
SF-1189 is the issue re. popup menus closing unexpectedly when PT is receiving messages from the outside world.
Chris Shaw @Chris_Shaw2024-06-08 01:40:03.602Z
Thanks!
- SIn reply toJames_Ezra⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-1206