sf.app.proTools.openSession + 2025.6 problems
Title
sf.app.proTools.openSession + 2025.6 problems
What do you expect to happen when you run the script/macro?
Since updating to PT 2025.6 i'm noticing that sf.app.proTools.openSession call seems to stay active until missing dialogs are cleared. At the moment it just hangs once it reaches missing files dialogs. If I manually dismiss the dialogs it successfully finishes without error.
Previous to the update it would open the session, then call my waitForSessionToOpen(); function which would handle such dialogs
Are you seeing an error?
What happens when you run this script?
As described earlier
How were you running this script?
Other
How important is this issue to you?
3
Details
{ "inputExpected": "Since updating to PT 2025.6 i'm noticing that sf.app.proTools.openSession call seems to stay active until missing dialogs are cleared. At the moment it just hangs once it reaches missing files dialogs. If I manually dismiss the dialogs it successfully finishes without error.\n\nPrevious to the update it would open the session, then call my waitForSessionToOpen(); function which would handle such dialogs", "inputIsError": false, "inputWhatHappens": "As described earlier", "inputHowRun": { "key": "-MpfwoFyZNOpBC3X5xGI", "title": "Other" }, "inputImportance": 3, "inputTitle": "sf.app.proTools.openSession + 2025.6 problems" }
Source
sf.app.proTools.openSession({sessionPath: 'path'});
Links
User UID: ZPSSH9Crt9fMIadCRVLNqA1931F2
Feedback Key: sffeedback:ZPSSH9Crt9fMIadCRVLNqA1931F2:-OTwJDhXuoOPtjNWetwF
Feedback ZIP: yQVIhmg7i2PnLfdUA9XIBZKeUOdc+VDSK9aaa2J6bloPEFCMMY3sOoTf3SElnTAK4qEUoapc6E2aBQesPjOY/Hmz+8mulacsFUkq8zk7Kfsq6Czbsqftqcjbektrju7E3byoLb+6KTsfk2fmGvXK4avp6jW7e7cMSu0cRripro22k/b/4k8Ix8suX+EIivqf7vRNzeeORICZC5riPRfjXKiXyKkw0W+SdBpos7bdhq3p/Yc22T4cYn+jAP88zS2aoIbYQDf4Sr9fSAi8r4SPF0HNL+vh/fEL2uO4n4z8q5XbNA/y6wkmHJ0v5LU3aHNvTy/h/CVXXgaVEACgiEDaPMVZXqQ5MMZwJAqvxNJFczs=
- Christian Scheuer @chrscheuer2025-06-30 10:56:42.686Z
Hi Tristan,
Thank you for reporting this. We're aware of this regression. It's a purposeful change on the Avid side that requires changes in SoundFlow before we can support it fully.
At the moment, we've been delayed in addressing this due to our work on the next version of SoundFlow, but I hope we can fix it soon.
- SIn reply toTristan⬆:SoundFlow Bot @soundflowbot
This report was now added to the internal issue tracked by SoundFlow as SF-2019