Avid Edition Insert Presets for Bypass and Activate not functioning (PT 2024.10.12 - macOS Sequoia)
Title
Avid Edition Insert Presets for Bypass and Activate not functioning (PT 2024.10.12 - macOS Sequoia)
What do you expect to happen when you run the script/macro?
I expect the insert in slot 1 of the selected track to toggle between active and deactivated states
Are you seeing an error?
The preset fails to perform the function - instead a Pro Tools context menu appears
What happens when you run this script?
The preset trigger the same dialog as if I were clicking on an empty insert slot (to add a plugin) or changing the plugin on an existing slot
How were you running this script?
I used a keyboard shortcut within the target app
How important is this issue to you?
5
Details
{
"inputExpected": "I expect the insert in slot 1 of the selected track to toggle between active and deactivated states",
"inputIsError": true,
"inputError": "The preset fails to perform the function - instead a Pro Tools context menu appears",
"inputWhatHappens": "The preset trigger the same dialog as if I were clicking on an empty insert slot (to add a plugin) or changing the plugin on an existing slot",
"inputHowRun": {
"key": "-Mpfwh4RkPLb2LPwjePT",
"title": "I used a keyboard shortcut within the target app"
},
"inputImportance": 5,
"inputTitle": "Avid Edition Insert Presets for Bypass and Activate not functioning (PT 2024.10.12 - macOS Sequoia)"
}
Source
//Preset converted to script
//Invoking preset "Insert 1" of template "Toggle Insert Active on Selected Track" in package "Pro Tools"
sf.soundflow.runCommand({
commandId: 'user:ckp49i4j60000a2100yfwywgf:ckoyc047u000nua10eehf9up4',
props: {
insertNumber: 1,
},
})
Links
User UID: lJGUxtX64mQtqiZEv3crPGKQcoL2
Feedback Key: sffeedback:lJGUxtX64mQtqiZEv3crPGKQcoL2:-OOclNKmZEBBlIzy4pt7
Feedback ZIP: jpdd7m0WdtfXJnbk5ZLqD1iCq2V3WXfKwl5vnXSLlY29OTexd+1ToB5zR922tswclOpz0rEC/qXgHMTTnRPAwudQPi/ejoR/2uY7FJnuowY2i0MSjyGzeQU2RaVBeKVGA5LcAd7Yo75Eq7EwUlbgX84jarL+eYw9vsguUr85USYvCbUxuFbgY0Z2raWndu/FKpXb2naFtK2IS/He6c9grtM9fpWgNbcz2p+TnujpzkcWveegJ29+aP5KribSquvEeBftFp+JxZAQ5k4imTCU9qtmhsI81WRXQeLkpuw/kJ2n8alngY9Nl+pzJFCyBu2U4w1F6LFBpY8tiNO8GDeBrJADehRVigbKXTmU09Y3DXg=
- JJames Beeson @James_Beeson
I've confirmed that Tooltips are enabled (as per known issues document here) and that displays do not have separate spaces.
In reply toJames_Beeson⬆:Kitch Membery @Kitch2025-04-24 21:57:19.407ZI'm sorry you're experiencing this issue with this.
Can you tell me more about how and when you are running this macro?
What is the Keyboard shortcut you have assigned to the macro?
Are you in the Edit or Mix window when you run the macro?
Is the selected track in view when you run the macro?Thanks in advance.
- JJames Beeson @James_Beeson
Hi @Kitch
Triggering via a keyboard shortcut (checked for uniqueness) in the mix window of Pro Tools with the track selected and in view.
- In reply toKitch⬆:JJames Beeson @James_Beeson
Keyboard shortcut used is ctrl-option-command + numeric keypad 1-10(0) (for each insert slot)
Kitch Membery @Kitch2025-04-30 21:12:52.407ZSorry for the delay getting back to you.
There are a couple of things that stand out here that may be causing the issue.
You mentioned that you are in the Mix window. Right now, SoundFlow commands are designed to be run in the edit window.
There is also a chance that the keyboard modifiers you're using to trigger the preset could be conflicting with the Pro Tools shortcut for bypassing inserts, so it might be good to try using a different combination that's not in conflict with the Pro Tools keyboard shortcut. Try using "Shift+1" instead.
I hope that helps. :-)
- JJames Beeson @James_Beeson
Thanks Kitch - I must have missed the bit in the documentation where is says SF doesn't work in the mix window.
Using the stock presets, the macro to open the plugin in an insert slot works in both Mix and Edit windows.
The stock macro to enable/disable and bypass an insert only works in the edit window - which itself seems strange.- Kitch Membery @Kitch2025-05-01 16:46:51.292Z
Yes I can understand how this may seem strange. However, opening/closing an insert only requires a programatic element click, but toggling the bypass state requires a modifier key to be held down with a mouse click, therefore it needs to be visible when doing so.
I hope that make sense. :-)