JS bindings for PT SDK in SoundFlow
Less of an idea and more of a general question about PT SDK integration. Thought it would fit in here.
I'm curious about the team's thoughts on longterm integration of PT SDK functionality into SoundFlow. I know it is already being used in various places but is there an overview somewhere of which SDK functions/messages have equivalents in SoundFlow? Would be really, really nice if there was a full JS/SoundFlow binding to the SDK so that it could be called directly.
Right now I'm stuck in this gray area where for some functionality I can use SoundFlow directly, and for others I have to use my python PTSL binding (or whichever language I want to choose) and then figure out how to call that from SoundFlow.
Christian Scheuer @chrscheuer2024-08-12 05:52:08.752ZHi Alex,
Our policy generally is to support everything in the Pro Tools SDK, but we do more rigorous testing on our side before porting a SDK command to SoundFlow.
As a general rule, if there's a SDK command SoundFlow doesn't support yet, it's most likely because we found bugs in the implementation of that command on the Pro Tools side (or some other similar reason) which means we can't support the use of that command yet. As SoundFlow generally needs to have full backwards/forwards compatibility, we need to clear a higher bar for quality of any command we support. For example, a command should continue to always do the exact same thing with the same input parameters - something that at this moment, SDK commands don't always do. For this reason, we'll wait until a SDK command is properly tested and we feel certain its behavior won't change, before we introduce it in SoundFlow.You can always get a full list of what's available by typing
sf.app.proTools.in SoundFlow and look at the dropdown/code completion popup.If there are specific commands you're missing, please do let us know and we can take a look at prioritising them.
- Ddanielkassulke @danielkassulke
Hi @chrscheuer - potentially daft question alert. Periodically I'll check to see whether these SDKs have been updated, but I've noticed that the SF changelog tends to be a few versions behind the most current version. Is there a way I can log the sf.app.proTools methods, so that I don't need to keep referring to the code completion popup?
Christian Scheuer @chrscheuer2024-11-04 10:28:25.349ZAh yea, sorry, our changelog here needs a manual nudge for me to update it - just updated now:
https://soundflow.org/changelog- Christian Scheuer @chrscheuer2024-11-04 10:28:54.280Z
Is there a way I can log the sf.app.proTools methods, so that I don't need to keep referring to the code completion popup
I tried this just now but couldn't find an easy way to do that, unfortunately. But do let us know what methods you might be missing!
- Ddanielkassulke @danielkassulke
Thanks, Chris. No - definitely nothing missing. Just hoping for a slightly easier way to browse that list.
- Christian Scheuer @chrscheuer2024-11-04 13:22:51.145Z
Totally get it. We have some other work scheduled that's also aiming to build a more constantly updated list of all actions - I think by the time that work is complete, we'll be able to surface this info on the website.
Hi Christian,
One PTSL command that would be really useful to have is ExportMix(). It replicates almost all the functionality of the Bounce Mix window and would make scripting a ton easier.Thoughts?
- Christian Scheuer @chrscheuer2025-01-04 13:54:58.068Z
Thanks for the bump on this. I've been wanting to add ExportMix for a while. It's more complex due to it having many nested configuration objects that need to be serialized properly, and our current macro editor doesn't fully support this. But I think I have some kind of plan for how to approach it so we can get proper support for it.
- SSoundFlow Bot @soundflowbot
This issue (adding ExportMix) is now tracked internally by SoundFlow as SF-1551