Macros not updating, commands not found
System Information
SoundFlow 5.10.1
OS: darwin 22.6.0
ProductName: macOS
ProductVersion: 13.7.1
BuildVersion: 22H221
Steps to Reproduce
This is going to be a tough one to reproduce exact steps for, because it seems like a collection of related bugs.
For many macros and scripts, I get a "command not found" error. For others—and this unfortunately seems random—I will make a change to a macro and when I execute it the change will not have taken place. Also, sometimes the same macros don't provide the same results in situations that should be identical.
Happy to send a log file.
Expected Result
Whatever the goal of the macro or script is
Actual Result
Sometimes nothing, sometimes the wrong thing
Workaround
Nope, been trying
Other Notes
I've uninstalled and reinstalled SoundFlow, and am always on the newest stable PT release, Mac OS 31.7.1
Links
User UID: qc6IBwD1stND4tFZaxUtM2qPuWS2
Feedback Key: sffeedback:qc6IBwD1stND4tFZaxUtM2qPuWS2:-OEeOXwy7NT1M2rGPOmb
Feedback ZIP: HZM/QG15P8j+nL4MIrEHw4wCbxzHXlmzfnDJwFMXMxm8rhg+gfX8vZC/D3T4Nn/u4WSnNo66qLARGY5h8qqifGvsa3e6FM1HDu1WC19368HhudC3oEFLBI1TSe7SgD3LpzqPthrpPfYJSqcRx8KJ+PgD3SNo9dIp4m16nzv0w7xiKS8w5a4uGUKOgoDoSjxYFy5PI1FdXCdClXiaacJGGNWLyyOzQgYptmAgUFfw1TKbsxmz69e86l+/BPlhe/KifSbKapSxUmwuDi2ysHGV3ixBoRtI1ALje0tUEYtwzgFsSX+536vG9nrM5z5VlGFkCL14pYuIHFkeD2MnQgkL1u1K4p5vzztekgq6NMGzrkA=
Chad Wahlbrink @Chad2024-12-21 18:38:48.014ZHi, this is Chad, a member of the SoundFlow team.
For issues like this, which involve multiple scripts, macros, and decks, it can be helpful for our support team to open a copy of a user account to diagnose issues. Do you approve of me looking at your account this way to help us hopefully find the source of an issue?
Note: This will not affect your account in any way; I would only make a copy of the account for testing purposes.
Chad Wahlbrink @Chad2024-12-21 18:44:48.823ZLooking through the logs that were uploaded with this support post, it does seem like there are some errors being thrown when your Pro Tools Deck , "Nick's Pro Tools Deck" is being shown. It could be some kind of issue related to activating this deck or a macro/script on the deck not compiling as expected.
For instance, I'd be curious if this BMP 2024 Clip Gain by Clip Name command is potentially having an issue:
0.12.2024 12:58:15.79 <info> [Backend]: Error parsing command BMP 2024 Clip Gain by Clip Name (Line 82): Unexpected token ; [ServerController] Trying to run command from sfgui, but not found: user:ckzrx0vrg0001jm10vruv3r07:cm4d1ts5s0002bo10jics2vv3 20.12.2024 12:58:15.100 <info> [EditorWindow:Renderer]: Unhandled Promise Rejection:Command not found: user:ckzrx0vrg0001jm10vruv3r07:cm4d1ts5s0002bo10jics2vv3 (This could be because the command had a compilation error) - undefined Line 10963 file:///Applications/SoundFlow.app/Contents/Helpers/SoundFlow.app/Contents/Resources/app.asar/dist/editor.js 20.12.2024 12:58:21.53 <info> [EditorWindow:Renderer]: Active Focus Container: app Line 33963 file:///Applications/SoundFlow.app/Contents/Helpers/SoundFlow.app/Contents/Resources/app.asar/dist/editor.js
Nick Norton @notNickNortonHey Chad, that script is indeed broken (in fact it's the one I've been working on) and this would make sense!
I renamed that deck maybe a month ago. Wonder if I can remember the old name...
Or is there a way to do a find/replace to update all if that's what needed?
- Chad Wahlbrink @Chad2024-12-21 20:47:02.680Z
Thanks, @notNickNorton.
Echoing Christian's comments below, we'd need you to isolate a scenario where a "Command Not Found" error is thrown so we can diagnose your issues better.
However, a few comments after looking into your account a bit:
- The only 'command error' I see in your log is when running the command "[NAME] sfX Automatic Clip Gain." This makes sense because that command is calling the `BMP 2024 Clip Gain by Clip Name Script" - a script with a few errors. Anytime there are red lines under a line of code or red highlights in the scroll bar of the script editor, that code is likely unusable.
So, in the BMP 2024 Clip Gain by Clip Name Script, the following two lines are giving it trouble:
- Delete the semi-colon at line 82
- Comment out or delete the "setClipListFilter()" function in line 193 - that function is currently undefined in the script. I'm unsure if that definition was deleted at some point while you were editing that script.
Finally, the other thing I would consider is that you are currently triggering your Pro Tools Deck twice from the deck and once from a macro:
I would delete the "Show Pro Tools Deck" macro from your Default Package, Delete the assignment to the application trigger on the "Nick's Pro Tools Deck" deck, and then re-add that Application trigger to respond to "Pro Tools" activating.
The ideal setup would be just this:
Generally, it's best practice to show only one deck on a device with one application trigger. (i.e., Don't have two decks tied to the same application trigger/device combo).
Again, if you have more specific scripts or macros that are causing you trouble, use the red "need help" button from the macro or script editor as outlined here:
https://soundflow.org/docs/help#script-help - In reply tonotNickNorton⬆:Chad Wahlbrink @Chad2024-12-21 20:48:04.495Z
Thanks, @notNickNorton.
Echoing Christian's comments below, we'd need you to isolate a scenario where a "Command Not Found" error is thrown so we can diagnose your issues better.
However, a few comments after looking into your account a bit:
- The only 'command error' I see in your log is when running the command "[NAME] sfX Automatic Clip Gain." This makes sense because that command is calling the `BMP 2024 Clip Gain by Clip Name Script" - a script with a few errors. Anytime there are red lines under a line of code or red highlights in the scroll bar of the script editor, that code is likely unusable.
So, in the BMP 2024 Clip Gain by Clip Name Script, the following two lines are giving it trouble:
- Delete the semi-colon at line 82
- Comment out or delete the "setClipListFilter()" function in line 193 - that function is currently undefined in the script. I'm unsure if that definition was deleted at some point while you were editing that script.
Finally, the other thing I would consider is that you are currently triggering your Pro Tools Deck twice from the deck and once from a macro:
I would delete the "Show Pro Tools Deck" macro from your Default Package, Delete the assignment to the application trigger on the "Nick's Pro Tools Deck" deck, and then re-add that Application trigger to respond to "Pro Tools" activating.
The ideal setup would be just this:
Generally, it's best practice to show only one deck on a device with one application trigger. (i.e., Don't have two decks tied to the same application trigger/device combo).
Again, if you have more specific scripts or macros that are causing you trouble, use the red "need help" button from the macro or script editor as outlined here:
- Nick Norton @notNickNorton
Well, that sure fixed a whole lot of problems in one move!
Got a bit more to tweak on that BMP script, but that aside I think we might've solved it all. Thank you!
In reply tonotNickNorton⬆:Christian Scheuer @chrscheuer2024-12-21 19:25:36.200ZFor others—and this unfortunately seems random—I will make a change to a macro and when I execute it the change will not have taken place
This could be due to a slow network connection or CPU contention, leading to a delay before your setup has been recompiled after the change.
For many macros and scripts, I get a "command not found" error.
We'd need to know more details/context to investigate this. Where do you see the error - how are you triggering them, etc. Full details would be needed to understand what goes wrong here.
Also, sometimes the same macros don't provide the same results in situations that should be identical.
This might be yet a 3rd issue/problem. It would help if you could provide a new bug report being more concrete - it appears you're experiencing issues which may seem related/generic on your side, but it's much easier to diagnose a specific instance of a problem rather than too broadly/early attempt to generalize.
Christian Scheuer @chrscheuer2024-12-21 19:26:49.783ZI'd highly recommend using our Script Help workflow to get help with one of the specific macros or scripts you're having problems with (ie. the command not found error). If we can find the source of one of the problems, it's easier to generalize after the fact, rather than not having anything concrete to go on.
- Nick Norton @notNickNorton
Hey, looks like Chad jumped on this with the logs.
The connectivity thing would make sense since my Internet has been buggy this week!
Will see if that fixes all, and will check out that workflow you suggested.
Update: I did not know about the priority/specific ways to report different things, will do for future!