How to read the Pro Tools Session's sample rate

Hi Richard,

To answer question 1;

var is an old method of declaring a variable;

Here is a great article that I found that walks through the differences between var, let & const.

The short version is that it is best to declare a variable using let instead of var as let is scope specific (ie. cannot be accessed through function walls). And use const to declare variables that will not change after they have first been declared.

I hope that make sense. :-)

For question 2,

I should make a video for this. :-)

Its good practice to organize your code so that it is clean and reusable.

A great way to do this is to have your script broken up into functions that do just one thing each.

Here is an example, I have three simple functions myFirstFunction, mySecondFunction & myThirdFunction, Then I have a main function where I call the individual functions.

function myFirstFunction(){
    log('This text is being logged from "myFirstFunction"')
}

function mySecondFunction(){
    log('This text is being logged from "mySecondFunction"')
}

function myThirdFunction(){
    log('This text is being logged from "myThirdFunction"')
}

function main() {

    myFirstFunction();

    mySecondFunction();

    myThirdFunction();
}

main();

So in your situation you would do this (see the comments inside the code block);

function getSessionSampleRate() {
    if (!sf.ui.proTools.windows.whoseTitle.is('Session Setup').first.exists) {
        sf.ui.proTools.menuClick({
            menuPath: ["Setup", "Session"],
        });
    }

    const win = sf.ui.proTools.windows.whoseTitle.is('Session Setup').first;
    const sessionFormatPanel = win.groups.whoseTitle.is('Session Format').first;
    const sampleRateString = sessionFormatPanel.children.whoseRole.is("AXStaticText").allItems[2].value.invalidate().value;

    sf.ui.proTools.menuClick({
        menuPath: ["Setup", "Session"],
    });

    const sampleRate = Number(sampleRateString.split(' ')[0]) * 1000;

    return sampleRate;
}


function main() {
    //Add the code that occurs before getting the Session Sample Rate here;

    const sampleRate = getSessionSampleRate();
    log(sampleRate);

    //Add the code that occurs after getting the Session Sample Rate here;
}

//This calls the main function;
main();

Then if you need to reuse the function in another script you can easily copy and paste it.

Let me know if that makes sense :-)
Rock on!

Answer to your last question: Yes. If you set a keyboard script trigger with the same PT keyboard shortcut then the SF trigger overrides it. I have a script that automatically fills in the bounce window info (Bounce filename, sample rate, bit depth, include MP3, etc) and fills in the MP3 window automatically with the Artist Name, etc. I use cmd-B to trigger it which is the PT keyboard shortcut as well. That keyboard command now triggers my script instead of Bounce to Mix. If I ever need to use a normal Bounce to Mix I just use the mouse and select it from the widow.

Another thing I do is use shift-cmd-W to trigger a script which asks me if I want to back up the session before closing. There are a lot of possibilities…

How difficult would it be to create super-power versions of the existing Pro Tools functions, that will automatically check and then populate the correct session settings on the next windows for those 3 actions (Bounce, Export Audio Files, Save Session Copy)?

Not that hard at all