"Invalid signature" response when authorising connection from C++ SDK

[andrewmoore-nz]

Can confirm, that's working for me on macOS 10.15 now. Seems that each command and the subsequent params must be on a single line, with every command separated by a newline character. So I'm getting output like:

andrewmoore@Andrews-MBP Release % ./ptslcmd -file ~/Desktop/command.txt
AuthorizeConnection Response:
is authorized: 1
message: Success
GetPTSLVersion Response:
PTSL Host version: 1
GetSessionPath Response:
session path: Macintosh HD:Users:andrewmooreocuments:PTSL_ImportTest:PTS L_ImportTest.ptx
session path is online: No
GetSessionName Response:
session name: PTSL_ImportTest
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Client
[ RUN ] Client.Result
[ OK ] Client.Result (0 ms)
[----------] 1 test from Client (0 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (0 ms total)
[ PASSED ] 1 test.

Aside from how impractical it is to write your commands to a file on disk in order to be able to do anything, the results are pretty unusable anyway, so I don't quite understand what the expectation is here when it comes to actually doing anything meaningful with it.

[jaydeesm]

Wow. Good sleuthing! Would be good to have the docs improved for sure!

[jaydeesm]

Ummm. Is the session path returning in OS 9 format?!? Sheesh! I haven’t seen a : in a path for 16 years!

[smurfyou]

Originally Posted by jaydeesm

Ummm. Is the session path returning in OS 9 format?!? Sheesh! I haven’t seen a : in a path for 16 years!

Ha! Why were you using OS 9 that late

[rmajors]

Hi all - to clarify, ptslcmd is an example application only. Its command line interface is intended as a way to test out interactions with Pro Tools via the scripting APIs, not as a production application.

[jaydeesm]

Should it not then, both in the docs and the built in help specify to use a -file to issue test commands, and forgo the other "usage".

Sorry for sounding harsh, but this wasn't put out as a developer preview, and yet I feel that's what we're all wasting time doing...

[rmajors]

If you wish to build an application that interacts with Pro Tools then you can use ptslcmd as an example of how to implement your own application to interact with the PTSL SDK.

We will definitely clarify the usage and purpose of the ptslcmd application in the next revision. Thanks for pointing this out.

[Darryl Ramm]

Originally Posted by jaydeesm

Ummm. Is the session path returning in OS 9 format?!? Sheesh! I haven’t seen a : in a path for 16 years!

Only 16 years? it brings back memories of shuffling floppies from a development Lisa to a Mac. OK Avid where is the Pascal API

But seriously I'm following along here as I think this is a very nice move by Avid. (and it was me who shot off his mouth recently about Avid not being open/having open APIs... this is a nice kind of "open" and especially with support from Avid to developers to get things kick started).

[rmajors]

Starting with the Pro Tools Scripting SDK 2023.3, PTSL now uses POSIX style file paths on macOS.