No internet connection
  1. Home
  2. Support

Macros to launch my most commonly used Third Party Plugins not working in Ableton Live (12.2 Beta)

By wolaud @wolaud
    2025-05-22 19:27:41.114Z

    Title

    Macros to launch my most commonly used Third Party Plugins not working in Ableton Live (12.2 Beta)

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

    Simple macro to open my most commonly used plug-ins and add to a track in Ableton.

    Are you seeing an error?

    Add Eventide Blackhole failed Error: Load Plug-ins: Line 59 (Add Eventide Blackhole line 1)

    What happens when you run this script?

    Nothing happens, the error described simply pops up.

    I will add that a few other plugins I have tested (for example Valhalla Delay) do seem to work but most do not for me.

    How were you running this script?

    I clicked the "Run Script" or "Run Macro" button in SoundFlow

    How important is this issue to you?

    5

    Details

    {
        "inputExpected": "Simple macro to open my most commonly used plug-ins and add to a track in Ableton.",
        "inputIsError": true,
        "inputError": "Add Eventide Blackhole failed\nError: Load Plug-ins: Line 59\n(Add Eventide Blackhole line 1)",
        "inputWhatHappens": "Nothing happens, the error described simply pops up.\n\nI will add that a few other plugins I have tested (for example Valhalla Delay) do seem to work but most do not for me.",
        "inputHowRun": {
            "key": "-MpfwYA4I6GGlXgvp5j1",
            "title": "I clicked the \"Run Script\" or \"Run Macro\" button in SoundFlow"
        },
        "inputImportance": 5,
        "inputTitle": "Macros to launch my most commonly used Third Party Plugins not working in Ableton Live (12.2 Beta)"
    }

    Source

    //Macro converted to script
    
    
    //Calling command "Load Plug-Ins" from package "Ableton Live" (installed from user/pkg/version "oMDTMcbKv2OT4GaE3NFzdjMdeXj2/clrm7ovg00000wm10jrwimta1/cmamkgdi700001510iefadfp6")
    sf.soundflow.runCommand({
        commandId: 'user:clrm7ovg00000wm10jrwimta1:cm9n9e90f0001ou10j8nnu5em',
        props: {
            pluginType: "VST",
            pluginPath: ["Eventide","Blackhole"],
            targetPosition: "First",
        }
    });
    
    
    

    Links

    User UID: YwZWhQkNk9YC9IGtGtlgw4vfPEt1

    Feedback Key: sffeedback:YwZWhQkNk9YC9IGtGtlgw4vfPEt1:-OQtSnEFc-UdCP7E7xPO

    Feedback ZIP: ABc/fU+JLz/SIBxLs6V4XM9ctEpgvOzq7xOorG7C3+S/R7M5kZUAX1lz+DB3PMAeyc7e7PchxW9HS4DF0onau7bLG0U/EUFyHUjFxbmz27C+KVEQoJfj6F5YTdB3hgwQ86RcCjbeGYimxXIEn1blSuVzGsfhZZTH7peRfoF3YyC2I79R3oXL2uTVUofXLOFmF+YhJL106lgVL19xiGKXP2WxL04pqFXWiM9eD98Py4zCHG5D6KzL/21YOd0uCfrRjbKjHLVvfTfL9zAfaYWfCv1Uxaug/JWpdQn3nr8HCK0LjqCW8cy4udqan1eCDrywPjOKk5OTEKvUwXlCCucC0iO6iniw0N91pD03soOJ6QE=

    • 4 replies
    1. Chad Wahlbrink @Chad2025-05-22 21:37:49.799Z

      Hi, @wolaud,

      Thanks for the question. To confirm, can you share a screenshot of your Ableton Settings for "Plug-Ins"?

      Like this:

      For it to work as expected, we will need to make sure that you have specified the type of plug-in that will load accurately according to what's scanned and available on your system. Are you using custom VST folders for any plug-ins that haven't loaded?

      Another thing to confirm is that there is a "VST" of the Eventide > Blackhole plug-in in your Ableton Browser, like this:

      If only a VST3 or AU is showing in the browser, we'd need to adjust the preset accordingly.

      Finally, here's a quick video demoing how to set up the plug-in loader presets:

      1. W
        In reply towolaud:
        wolaud @wolaud
          2025-05-23 01:55:03.687Z

          Thank you, this clarified things — I was using custom VST folders but if I turn them off everything works as expected.

          1. Chad Wahlbrink @Chad2025-05-23 02:09:48.885Z

            Awesome!

            Okay, I'll look into the custom VST folders and see if we can get those working. Thanks for the heads up.

          2. S
            In reply towolaud:
            SoundFlow Bot @soundflowbot
              2025-05-23 02:10:14.088Z

              This issue is now tracked internally by SoundFlow as SF-1846