No internet connection
  1. Home
  2. Support

Pro Tools SDK fades bug

By Martin Wrang @Martin_Wrang
    2025-01-27 22:16:46.884Z

    Title

    Pro Tools SDK fades bug

    What do you expect to happen when you run the script/macro?

    Create fades based on preset

    Are you seeing an error?

    What happens when you run this script?

    After running this command once, the regular fades in Pro Tools (using the f-key) do not work until Pro Tools has been restarted.

    How were you running this script?

    I used a keyboard shortcut within the target app

    How important is this issue to you?

    4

    Details

    {
        "inputExpected": "Create fades based on preset",
        "inputIsError": false,
        "inputWhatHappens": "After running this command once, the regular fades in Pro Tools (using the f-key) do not work until Pro Tools has been restarted.",
        "inputHowRun": {
            "key": "-Mpfwh4RkPLb2LPwjePT",
            "title": "I used a keyboard shortcut within the target app"
        },
        "inputImportance": 4,
        "inputTitle": "Pro Tools SDK fades bug"
    }

    Source

    // Right now the use of this command first seems to kill the 'f'-key keyboard focus.
    // Pro Tools will have to be restarted to regain ability to fade as normal. Closing or restarting SoundFlow does not restore the ability to use the regular fade command.
    // I tried changing the keyboard shortcut for 'crossfade using last setting' (keyboard focus 'f') in Pro Tools. Now, instead of no response I get the 'That command could not be run at this time'-pop up.
    // This command has also crashed Pro Tools for me.
    // Running Pro Tools 2024.10.1 and Soundflow 5.10.1 on M1 Mac Mini Sonoma 14.7
    
    // Only Batch Fade presets are relevant or needed.
    // When single in/out/cross-fades are made the fade shapes for the given type will match the batch fade preset
    
    sf.app.proTools.createFadesBasedOnPreset({fadePresetName: 'Linear 80', })
    

    Links

    User UID: 4VZqDm8dumS6yRFAejf9YBZtRpQ2

    Feedback Key: sffeedback:4VZqDm8dumS6yRFAejf9YBZtRpQ2:-OHdpevMdOFkISwdiIHN

    Feedback ZIP: NhwrA+vw9gpAevvP/MuJYx6DQS5JhyBohuMIS8WMcuvQyewIaoAGAOYYC2S8E4OkEdny+N07wLuGp0xUehDZyGCLdbwvYqA7PlKcb8IzM+A/SetHJp2vZu1An8vh0vbm65ZAoLaqjQWVj/3QnUIHMwJm8x7JPoSayahiJm1n9BRvjuKDuL9vgLME5J0BFXAIBFlHxu97E8QnGRBChgOwNhsVkM1uJNkLQ/AphEUfUENDhb/Sff6+S2c3+vyqtHfZkRCgXl7ogGdz8o7xCdVzmYQZJeDQiFJbc+vHXpD5c6HnSAM1ptf7xPNRMfxZH49CnRTi/gfAMRL1vgLc3JQ5Kw==

    • 2 replies
    1. Dustin Harris @Dustin_Harris
        2025-01-31 15:14:49.035Z

        For the record, this is happening for me too. I think it's an SDK issue instead of a soundFlow one...

        1. In reply toMartin_Wrang:
          Dustin Harris @Dustin_Harris
            2025-01-31 18:13:30.724Z

            I've logged a bug with AVID, we'll see if they can reproduce it.