Forced to downgrade to Pro Tools 2024.6 - Now Soundflow does not work

Hi, @Jeremy_Kittel,

Sorry to hear you are having more issues.

The issue is that the scripts you were using for soloing were really designed to take full advantage of the advancements from SFX in Pro Tools 2025.10+. Namely, they use mouseClickElement() which simulates a mouse click. In Pro Tools 2025.10+, this works regardless of whether the track is scrolled into view because it leverages the SFX connection. However, on older versions of Pro Tools, SoundFlow uses accessibility to simulate mouse clicks - meaning that Pro Tools has to be in focus and the track has to be scrolled into view to work. This is likely why you are experiencing issues where the mouse seems to click randomly - it's technically trying to click on the track, which is currently off-screen, etc.

So yes, on Pro Tools 2025.10+, your scripts worked great with the more modern setup.

With all this, I think the best option is to approach this workflow using the Pro Tools SDK rather than accessibility and mouse clicks.

Here's the script structure you would use:

// Add or remove named track from soloed tracks - Pro Tools 2023.12+

function soloAdd(trackName) {
    const currentlySoloedTracks = sf.app.proTools.tracks.invalidate().allItems
        .filter(track => track.isSoloed)
        .map(track => track.name);

    const isAlreadySoloed = currentlySoloedTracks.includes(trackName);

    if (isAlreadySoloed) {
        // Un-solo just the named track; all other soloed tracks remain
        sf.app.proTools.setTrackSoloState({
            trackNames: [trackName],
            enabled: false
        });
    } else {
        // Add the named track to the current solo set
        sf.app.proTools.setTrackSoloState({
            trackNames: [...currentlySoloedTracks, trackName],
            enabled: true
        });
    }
}

soloAdd('EGT');

You can replace your current script with this setup - changing soloAdd('EGT'); at the end of each script, and it should work on Pro Tools 2023.12+