Functionality roadmap

[bigsocks]

Is there a roadmap for the SDK in terms of future exposed functionality? I am building a tool in C++, the SDK connects thru gRPC flawlessly and all is well but it feels as though some simple functionality that would go a long way is missing (such as Select Track, or Set Active Track, or move edit cursor / play head to position). Or am I treating this incorrectly in that we should be using the SDK as more of a way to receive data from PT we can then use to manipulate in other ways (the only way I can think of really is interfacing with keyboard maestro). Sorry for the ramble - just feels like either I'm missing something obvious or the SDK isn't designed how I have it pictured (which is odd as it's called a Scripting SDK)

Example
Creating a selection (either session wide or on defined track(s) only) would be huge because then you could define edit points (or just grab the start and end selection points from the memory location data) then have access to edit tools (we have trim edit to selection I believe), we can quickly create a dialogue workflow for ADR/game audio

Also being able to get plugin info on a track and reading automation data (the automation types, the anchor points and values) etc.

[rmajors]

Thank you for your feedback.

The intention of this SDK is to be able to script Pro Tools, with a focus on actions to automate editing of the session. We are working to extend the list of available commands and we plan to continue expanding the command set with each Pro Tools release.

All feedback on this forum is reviewed and we consider it along with the planned work on our backlog, though we do not provide a public roadmap of planned enhancements.

Of the things you mention, we are already looking into Set Selected Track and Set Timeline Position for possible inclusion in a future release.

Could you tell us more about the Set Active Track request to make sure that we understand what functionality you would like?

Thank you,
Rob

[bigsocks]

Apologies, I missed the response - set active track would be to move to the track in focus (string name I'm assuming). To allow for copy/paste/spot etc commands on that track - or having a more indepth edit function whereby you choose the command enum (copy, paste, spot) and where you want the command to take place (track name etc).