Velocity Script stopped working
Title
Velocity Script stopped working
What do you expect to happen when you run the script/macro?
Add velocity
Are you seeing an error?
What happens when you run this script?
It used to work. My guess is after upgrading to Protools 2024.6 it stopped working.
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": "Add velocity",
"inputIsError": false,
"inputWhatHappens": "It used to work. My guess is after upgrading to Protools 2024.6 it stopped working.",
"inputHowRun": {
"key": "-Mpfwh4RkPLb2LPwjePT",
"title": "I used a keyboard shortcut within the target app"
},
"inputImportance": 5,
"inputTitle": "Velocity Script stopped working"
}
Source
//Preset converted to script
//Invoking preset "Add: 10" of template "Event: Change Velocity" in package "Kitch's Command Template Collection"
sf.soundflow.runCommand({
commandId: 'user:ckgelz7r9000b0j10dxbuq7dx:cloxyn0nn0001kc109z9dnya7',
props: {
Enable Note Value & Type: "Enable",
addSliderValue: 10,
noteOff: "Enable",
noteOn: "Enable",
option: "Add:",
},
})
Links
User UID: ugsrnIjRISR3rAN6xI5A0mhSdss1
Feedback Key: sffeedback:ugsrnIjRISR3rAN6xI5A0mhSdss1:-O6EJvRXZzFUUyMkJqrS
Feedback ZIP: WE0+70lM/RPiDi2nxw+SeUD1ig/Kjns3hE2tawfqBGV1KIXtlGq2Dg87e430/i6cyOBY3YMdyxEAcp1D5wjkA6ojtgpDJwc7dsK74Zn+H9cy0bRMZ9BIOMEDL7wfe3ee9UBnuonqMW3HJqY63LGJkDdECiyp31PC1PNN8+4pB5+heUDisGG/zcj/AItEhiu2n0LwH7VazRZ2Z7YbIbMNHQlZcTn3kjtPisKM95vmbjg/PSjepVyarMkf/wFAKORkc4nYilJWomgVL67lquGePitjfmw5P2F27Fg1fgvbyVwNDrlrs0qWop0Mqo3i4n2se6YWb4yD46zqNidPgw/QOg==
- SSoundFlow Bot @soundflowbot
Thanks for posting a question or an issue related to the 'Kitch's Command Template Collection' package.
This package is made by @Kitch. We're auto-tagging them here so that they will hopefully be able to help you. 
In reply toKim_Planert⬆:Kitch Membery @Kitch2024-09-09 17:07:03.005ZHi @Kim_Planert,
Thanks for letting me know. I shall take a look this week. :-)
Kim Planert @Kim_PlanertHi Kitch, did you have any time to look at this issue yet? Thanks!
Kitch Membery @Kitch2024-09-18 16:39:42.150ZHi @Kim_Planert,
It looks like this may be a regression in SoundFlow and not due to the Pro Tools 2024.6 release.
As a troubleshooting test, can I get you to try installing SoundFlow 5.7.8 and see if it works correctly? If so I'll report the issue internally so that it can be addressed in an update.
Thanks for your patience, and for bumping this thread. :-)
- Kim Planert @Kim_Planert
Hi Kitch, I installed 5.7.8 and am now getting the error message Add: 10 failed Could not set clipboard text: Value cannot be null. (Parameter 'str') (Event:Change Velocity: Line 393). What could that be now? Thank you!
- Kitch Membery @Kitch2024-09-18 23:16:18.758Z
Hi @Kim_Planert,
That looks like a different issue. I'll look into this first thing tomorrow morning.
It would be really helpful for this new issue if you could provide a screen recording so that I'm able to reproduce it.
Was there an error message thrown when you were running the script on the most recent version of SoundFlow, and if so can you provide me with the error message?
Thanks in advance. :-)
- In reply toKim_Planert⬆:Kitch Membery @Kitch2024-09-18 23:20:46.965Z
It would also be helpful to get a screenshot of the preset you are using, so I can replicate it. :-)
- Kim Planert @Kim_Planert
Hi Kitch, there was no error message in 5.8. Nothing happened when the script was triggered. Just nothing happened.
I did some more testing. Sometimes the scripts work. Some other times I error messages. They can also vary. Most of the time it's the line 395 error. Other times Couldn't get item #0. see screenshots.
I did a screen recording. You can see that +56 worked, then I did a -5 and the error appeared.
https://www.dropbox.com/scl/fi/ulqp2j0e68thb9s5e4j6w/Screen-Recording-2024-09-19-at-10.58.50-AM.mov?rlkey=2e7spzhdzmgf6cj8k2rte2zlq&st=0amsxk2k&dl=0Strange. Hope that helps. Thank you!
- Kitch Membery @Kitch2024-09-19 18:10:16.904Z
Thanks you @Kim_Planert,
Thanks for providing so much info. This will be very helpful when troubleshooting. :-)
Re: "there was no error message in 5.8. Nothing happened when the script was triggered. Just nothing happened." Great I can reproduce.
The other issues look like it could be a issues with my code. I shall report back.
- In reply toKim_Planert⬆:Kitch Membery @Kitch2024-09-19 23:43:22.538Z
Hi @Kim_Planert,
I found a few bugs in the script. And have addressed support for new versions of Pro Tools where the Apply button was not being found. I plan on doing another refactor when I have some more time.
Note I'm still trying to work out if there is a regression in SoundFlow that's causing the presets not to trigger in versions above 5.7.8.
Can I get you to check that your "-5" preset looks like the image below, in your account? The way you phrased it in your reply made it seem like you had possibly typed "-5" in the "Add:" property rather than "5" in the "Subtract:" property. Let me know if you need further explanation about this.
I've pushed another version of the package to the store, version 1.8.2. It will only work in SoundFlow 5.7.8 till I've worked out the other issue though. Thanks for your patience, I'll report back when I have more info.
- Kim Planert @Kim_Planert
Hi Kitch, I updated your Command Template Collection to 1.8.2.
You were right. I had -5 in Add. Whoops! Corrected all the commands.
Sending you another lot of error messages I am getting.
Often it can't find the close button.
- Kitch Membery @Kitch2024-09-21 00:50:31.185Z
Hi @Kim_Planert,
I'm glad correcting the values fixed that first issue.
Unfortunately, the other error messages, by themselves, are of no use to me without context.
For each issue, I'll need a screenshot of the preset you are using when the error is thrown. That way I can attempt to recreate the issue on my system.
Thanks in advance.
- Kim Planert @Kim_Planert
Hi Kitch, sending the screenshots.
- Kitch Membery @Kitch2024-09-21 01:16:13.138Z
Thank you.
So, are you saying all of the errors you are seeing happen on all of these presets? Or are you seeing specific errors when running specific presets?
Also, is the Event window open before you run the preset? And how are you triggering the presets? (From a Stream Deck, iPad, Keyboard Shortcut, etc)
- Kim Planert @Kim_Planert
It's on all but there is a pattern. I close the Event Window after each attempt. Let's focus on + and - 5.
First attempt always leads to an error. After the first error the preset works. Then I switch to another preset which has an error. Then the next time pressing the same preset there is no error.Two types of errors, close button and array length errors.
Triggering via Midi from Lemur. No change triggering via keyboard.
- Kitch Membery @Kitch2024-09-21 01:43:16.867Z
Thanks, that's great info. I'll attempt to reproduce it when I have a moment.
- In reply toKim_Planert⬆:Kitch Membery @Kitch2024-09-21 02:13:51.061Z
Just pushed out 1.8.3. I've added a code to wait for the slider to be available after the "Option" popup menu is selected. This may fix some or all of the issues. Let me know if any of the issues still remain. :-)
- In reply toKim_Planert⬆:Kitch Membery @Kitch2024-09-21 02:20:32.140Z
Just pushed 1.8.4. I've added a wait for the Event window's close button, just in case.
- Kim Planert @Kim_Planert
Installed 1.8.4 a new error turned up again only on the first use of preset + or - 5.
Could not set slider number.
Sorry...
- Kitch Membery @Kitch2024-09-21 02:57:35.986Z
No worries at all...
Out of interest, what operating system are you on?
I'll have to dig deeper later.
- Kim Planert @Kim_Planert
Sorry for the late reply. Catching back up ... Am on Sonoma 14.7
- Kim Planert @Kim_Planert
Hi Kitch, checking in on this. Any progress? Thank you!
- Kitch Membery @Kitch2024-10-08 00:46:11.168Z
Hi @Kim_Planert
I've been in transit for the last four days but will continue troubleshooting over the next couple of days.
- Kim Planert @Kim_Planert
Hi Kitch, any luck yet?
- Kitch Membery @Kitch2024-10-21 17:44:54.088Z
Hi @Kim_Planert,
It looks like Christian has fixed an underlying issue with the command template property names that contained colon characters. This fix will be available in 5.9 which is due to be released in a few weeks.
I plan on testing the fix today on Sonoma to see if the cause of the issue was due to the regression.
I shall report back once I've had a chance to test it.
- Kim Planert @Kim_Planert
Thanks for the update Kitch. Good News!
Any chance you could have a look at this one as well? Dotted, Triplet Selection #post-2
- In reply toKim_Planert⬆:Kitch Membery @Kitch2024-10-31 06:58:05.868Z
Hi @Kim_Planert,
Ok... massive apologies for not getting this one sorted sooner.
The "Event: Change Velocity" script should work now. I was finally able to reproduce all the additional edge cases you were experiencing in Sonoma.
The update should fix the "Could not find close button in window", "Could not set Slider Number Field" and "Could not get item #0 as array length..." errors.
Be sure to update the package to 1.8.6 and download the latest version of SoundFlow 5.9.0 by logging into your account soundflow.org/account/install. :-)
I haven't had a chance to check out the "Set Quantize Note Value" script yet, but I'll update you on the other thread as soon as I've had a chance to fix it.
- Kim Planert @Kim_Planert
Thanks Kitch, there is a definite improvement. One error left. Sorry! Every time I try a command first time it fails with:"Could not set clipboard text: Value cannot be null. (Parameter 'str').
Any idea?
Thank you! Almost there!
- Kitch Membery @Kitch2024-11-06 22:14:42.632Z
No worries at all...
Can you provide me with steps to reproduce this issue every time? Knowing how to reproduce the "first time" would really help. Maybe it's navigating away from something or running another script?
And again thanks for your patience on this!
- Kim Planert @Kim_Planert
Hi Kitch,
I made a little video. not navigating anything as far as I can tell. example with velocity 30.
- Kitch Membery @Kitch2024-11-11 22:53:43.003Z
Hi @Kim_Planert,
Unfortunately, I'm unable to reproduce this issue in Pro Tools 2024.10 on Mac Sonoma 14.7.
I did however find a couple of other bugs and added some code to ensure there is no Null value when trying to set the text from the clipboard.
Hopefully, the updates fix your issue (Please update the "Kitch's Command Templates" package to Version 1.8.7).
- Update: Change Velocity Script checks that all non "Change Velocity panels" are closed before proceeding.
- Update: Change Velocity Script waits for a non-null value.
- Bug Fix: Change Velocity Script does not use the Note Off Checkbox if the property is null.
If the update does not fix the issue, I'll need you to select the preset that is failing, click the "Need Help" button and create a new report.
In my previous post, I may not have clearly explained my question, as it’s a bit complex. Here’s what I’m trying to clarify:
I need to understand and reproduce what qualifies as the “first time” the command is run, as this is critical for troubleshooting and resolving the issue. Could you specify:
- Is it considered the “first time” when you run the preset on a new or different session?
- Or is it the “first time” when running the preset after restarting SoundFlow?
- Or perhaps it’s the “first time” after opening a MIDI file in the MIDI Editor?
If we can pinpoint what defines this “first time” scenario, I’ll have a clearer path to identifying and fixing the issue.
This version emphasizes each possible scenario and frames the question as a key to solving the issue.
Thanks in advance.
- Kim Planert @Kim_Planert
Hi Kitch,
installed 1.8.7 with no change.
It's the first time running that specific command after any other. For example I run Velocity 10 with notes selected in an open Midi Editor and it will fail, run it again it will work, with same notes or other notes selected in the same midi file I trigger Velocity 20 and it will fail, I run it again it will work and so on.
It happens on all Velocity commands probably because they are all based on the same Factory Preset.
Tried a fresh preset of Velocity +5 with the same result.
Sorry that I don't have better news.
Shall I open another report via Need help now?
- Kitch Membery @Kitch2024-11-13 02:40:32.114Z
Thanks for clarifying @Kim_Planert
That seems easily reproducible. With that said it seems strange that it was not happening on my system.
And can you confirm that you are on?
Sonoma v14.7
Pro Tools v2024.6
Kitch's Command Templates Collection v1.8.7
Are you on the Latest Version of SoundFlow (available from soundflow.org/account/install)Can you take a screenshot of one of the presets that is failing for example "Velocity 20"?
When running the preset the first time, is the Events window closed? And if so does it happen if the window is open?
What Keyboard Shortcut are you using to run the preset (in case that is interfering)?
Thanks in advance.
- Kim Planert @Kim_Planert
A miracle has happened. I had switched sessions and your message came in. I tried again and it worked. Went back to the original session. Still worked.
Maybe it did something as I had updated to the new version of KCT 1.8.7.
Anyhow thank you very much!!! Hurra!
Still answering your main questions just in case:
Sonoma v14.7
Pro Tools v2024.10
Kitch's Command Templates Collection v1.8.7
Soundflow 5.9.0Events window was always closed, but now works either either
- Kitch Membery @Kitch2024-11-13 03:08:46.027Z
Awesome!!! Was scratching my head on this one.
Thanks for your patience. I'm glad we worked it out. :-)