No internet connection
  1. Home
  2. Support

Execution of Izotope Preset caused a loop between PT and Izotope that wouldn't end

By Stephanie Brown @Stephanie_Brown
    2025-06-27 15:20:04.051Z

    Execution of Izotope Preset caused a loop between PT and Izotope that wouldn't end

    System Information

    SoundFlow 5.4.2

    OS: darwin 23.6.0

    ProductName: macOS
    ProductVersion: 14.7.5
    BuildVersion: 23H527

    Steps to Reproduce

    1. I am in the process of setting up my stream deck. Izotope is a program I use quite extensively. I was assiging a premade preset from Izotope to my stream deck.
    2. It was the Izotope--RX Connect--Send to RX--continuous clip. In the Soundflow app, I hit the run preset button, just to make sure it worked.
    3. This caused my system to go into an endless loop switching between PT and Izotope. I couldn't get use of any other part of my computer until I did a hard reboot.
    4. I kept getting a console 'failed action' error for every loop and got up to 250 times before I could do the hard reboot. However, the 'failed action' was referring to a script I had tried to execute the day before (launching the plugin Spectral Layers) and it failed. I deleted the script from my stream deck but somehow it's still in the cache someplace.

    Expected Result

    What should have happened was that the selected clip in PT should have been sent to Izotope with the settings of entire selection, continuous clip.

    Actual Result

    The system went into an endless loop between PT and Izotope.

    Workaround

    No. I did not try again in fear of the loop happening again.

    Other Notes

    I have the Soundflow log from yesterday but not sure how to upload it.

    Links

    User UID: GevRLXsZeuYuCrkgzyjTx6acQL42

    Feedback Key: sffeedback:GevRLXsZeuYuCrkgzyjTx6acQL42:-OTlyLyeiofln21ePeSA

    Feedback ZIP: uZ2k/uwW4qVyq6sDo4eVUVOMjINgXtH8DF9rLQRo1hbRgbH37GQcY5nkEwZMHtOKBS06my2KG4hgnOBxHTdwyF2B/hn7ob65tQ8qgNpw3OXAzOmGM50AplpxubtKWPX46tkdHxRDtMGH1tSyruTTNEzUtjiJ+ZECm2iTot5STOpH7YvmHX8t2QAQHKbKd41yayHL7nceVWMcaPAYaCofyXaAvoDwq/xOB2yyIdkZUhTBYZVHJ9tQrw0FulzwisZFVni6D9oWs4HP5TGLav3KpNoJ5dJvu4bDsb/1dIEwCbz2lAYLP1pHyulTxl3CWuY/3Dj3FZiUSmXehcKIEQGXNw==

    Reply

    Linked from:

    1. Constant console Log notification that an action failed
    • 3 replies
    1. Chad Wahlbrink @Chad2025-06-27 18:10:34.762Z

      Hi, @Stephanie_Brown,

      I understand why this may have happened yesterday. We can discuss it together on the call next week, but I wanted to go ahead and give you some context.

      I confirmed that you removed the Application Triggers from your "Default Profile" in SoundFlow. Profiles are a feature in SoundFlow that allows you to have different commands mapped for different contexts. In your case you have 3 profiles:

      Profiles can be changed from the "Profile" menu in the menubar or the "Profiles" tab in the SoundFlow Editor.

      Removing a mapping to an Application Trigger or Keyboard Trigger in one profile does not translate to all your other profiles.

      In your other profiles, there were multiple commands with Application triggers firing when Pro Tools was activated, and then other commands firing when iZotope RX was activated:

      I suggest closing both Pro Tools and iZotope RX and clearing the Application Triggers for each profile. I'm happy to do this together on the call next week if that feels easiest, though!

      Thanks again for logging this here. We will get it sorted out together!

      Reply
      1. Christian Scheuer @chrscheuer2025-07-08 15:27:18.123Z

        I'll also add that this report was from SoundFlow 5.4.2, which is more than 2 years old. Updating to a supported version should be the first step.

        Reply
        1. Chad Wahlbrink @Chad2025-07-08 15:54:57.684Z

          Thanks, @chrscheuer - through further support, the workstation used was updated and it did solve many issues.

          Reply1 Like
      ReplyAdd progress note