Bounce Mix - Select Mix Source Sub-Path
Title
Bounce Mix - Select Mix Source Sub-Path
What do you expect to happen when you run the script/macro?
Bounce Mix Window: Select Mix Source when source is a bus or output sub-path. This script works as long as it's selecting a bus or main output. But it can't seem to find anything that is a sub path. I saw the forum pasts from a few years ago and wondered if there's a way to do this now. Or a workaround.
Are you seeing an error?
Could not click popup menu item (Select Bounce Source: Line 5)
What happens when you run this script?
Fails if I add the 3rd menu path. With only two menu paths it works. For example:
output, MIC (7.1.2) - this works
output, MIC (7.1.2), MIC.C (Mono) - does not work.
How were you running this script?
I used a keyboard shortcut within the target app
How important is this issue to you?
3
Details
{
"inputExpected": "Bounce Mix Window: Select Mix Source when source is a bus or output sub-path. This script works as long as it's selecting a bus or main output. But it can't seem to find anything that is a sub path. I saw the forum pasts from a few years ago and wondered if there's a way to do this now. Or a workaround.",
"inputIsError": true,
"inputError": "Could not click popup menu item (Select Bounce Source: Line 5)",
"inputWhatHappens": "Fails if I add the 3rd menu path. With only two menu paths it works. For example:\n\noutput, MIC (7.1.2) - this works\noutput, MIC (7.1.2), MIC.C (Mono) - does not work.",
"inputHowRun": {
"key": "-Mpfwh4RkPLb2LPwjePT",
"title": "I used a keyboard shortcut within the target app"
},
"inputImportance": 3,
"inputTitle": "Bounce Mix - Select Mix Source Sub-Path"
}
Source
//Macro converted to script
sf.ui.proTools.windows.whoseTitle.is("Bounce Mix").first.popupButtons.allItems[1].popupMenuSelect({
menuPath: ["output","MIC (7.1.2)","MIC.C (Mono)"],
});
Links
User UID: KI5JeIGNSQbxx0hwB8QOimtFV812
Feedback Key: sffeedback:KI5JeIGNSQbxx0hwB8QOimtFV812:-N2PmAJO_ndQbEF-2E0R
- SSteve Bissinger @sbiss2022-05-19 05:30:14.703Z
Kitch Membery @Kitch2022-05-19 17:43:53.819ZHi @sbiss
At a glance, it looks like the menu path should be ["output"," MIC.C (Mono)"]
With four spaces in front of MIC.C (Mono).
- SSteve Bissinger @sbiss2022-05-20 00:31:50.374Z
I tried 1, 2, 3, and 4 spaces but it didn't work. There were some posts from 2018-19 that this was not possible. Not exactly sure why as long as the names match exactly.
- Kitch Membery @Kitch2022-05-20 01:48:04.462Z
Hi @sbiss,
If you run this script...
sf.ui.proTools.appActivateMainWindow(); const mi = sf.ui.proTools.windows.whoseTitle.is("Bounce Mix").first.popupButtons.allItems[1].popupMenuFetchAllItems({dismissMenu:true}).menuItems const miPaths = mi.filter(mi=>mi.path[1].endsWith("MIC.C (Mono)")).map(mi=>mi.path)[0] log(miPaths||`Could not find path`)It will log the path that you need for the popup menu.
It should look like this;
[ "output", " MIC.C (Mono)" ]If it logs "Could not find path" I'll have to investigate further.
Let me know
- SSteve Bissinger @sbiss2022-05-20 16:58:02.168Z
Kitch! It works! I cannot for the life of me figure out what is different from the text with four spaces your script returned vs. my previously having typed the same thing, but I'll take the win. This turns out to be extremely useful :) As always, thank you!
- Kitch Membery @Kitch2022-05-20 18:35:36.356Z
Rock on!