We're currently seeing issues with posting on the forum. We're looking into this issue.
No internet connection
  1. Home
  2. How to

I/O issues

By Ryan DeRemer @Ryan_DeRemer
    2022-04-03 09:11:39.181Z

    Hey all,

    I'm having an issue generally with scripts having to do with changing Ins/Outs on tracks, be it the "Selected tracks to no input" command or routing tracks to an existing folder. Not sure what's going on or if I have a funky setting somewhere. Any ideas @Kitch @chrscheuer ? Here's the info from the log:

    03.04.2022 02:06:43.55 [Backend]: [ServerController] Running command from sfgui: 'No Input' (user:cl11whpfk000cmg10uzz5h8x7:cl1j1ov9o000nbm10gouw7skr)

    03.04.2022 02:06:43.56 [Backend]: >> Command: No Input [user:cl11whpfk000cmg10uzz5h8x7:cl1j1ov9o000nbm10gouw7skr]
    Checking for running apps with bundle 'com.avid.ProTools'
    NSArray.ArrayFromHandle count = 1

    03.04.2022 02:06:43.72 [Backend]: Could not get UIElement for AxPtTrackInputPathButton: Could not find Audio Input Path selector button
    Logging error in action (01) TrackOpenInputMenuAction: Could not find selected track's input button

    03.04.2022 02:06:43.72 [Backend]: !! Command Error: No Input [user:cl11whpfk000cmg10uzz5h8x7:cl1j1ov9o000nbm10gouw7skr]:
    @Error invoking proTools.track.input.openMenu (No Input: Line 7)
    Could not find selected track's input button
    Could not find Audio Input Path selector button (AxPtTrackInputPathButton)

    << Command: No Input [user:cl11whpfk000cmg10uzz5h8x7:cl1j1ov9o000nbm10gouw7skr]

    Solved in post #11, click to view
    Reply

    Linked from:

    1. Move track to routing folder
    • 11 replies
    1. Christian Scheuer @chrscheuer2022-04-03 09:58:26.740Z

      This looks like you may not be displaying I/O in your session?

      Reply
      1. Ryan DeRemer @Ryan_DeRemer
          2022-04-03 19:41:46.606Z

          @chrscheuer that's the thing, the I/O is displayed. That's why I'm confused about why this is happening.

          Reply
          1. In reply tochrscheuer⬆:
            Ryan DeRemer @Ryan_DeRemer
              2022-04-03 19:50:55.066Z

              Below is a screenshot of the result of the "Select No Input for Selected Tracks" command. The log is the same as above. This also happens with any command that requires a track I/O change (eg. @chadwahlbrink 's "Add and Route Tracks to Existing Folder Track")

              Reply
              1. Chad Wahlbrink @Chad2022-04-03 20:08:22.702Z

                Could you try some of these scripts with some different track heights? That could be a good way to pressure test the issue.

                Possibly try a fresh install of soundflow from the website?

                Reply1 Like
                1. Christian Scheuer @chrscheuer2022-04-03 21:03:11.796Z

                  Also try checking if your Tooltip settings are set as you see here:
                  https://help.soundflow.org/en/articles/5637993-known-issues

                  Reply1 Like
                  1. Chad Wahlbrink @Chad2022-04-03 21:29:58.515Z

                    Interesting! I never knew this about tool tips. Good to know.

                    Reply1 Like
            • In reply toRyan_DeRemer⬆:
              Kitch Membery @Kitch2022-04-03 21:10:44.551Z

              Hi @Ryan_DeRemer,

              I'm not sure the exact script you are using, however, the following script will set the input of the selected track to "no input", regardless of track heights.

              sf.ui.proTools.selectedTrack.inputPathButton.popupMenuSelect({
    menuPath: ["no input"]
});

              and the following will set the output of the selected track to "no output", regardless of track heights.

              sf.ui.proTools.selectedTrack.outputPathButton.popupMenuSelect({
    menuPath: ["no output"]
});

              And this script will route a track to a folder;

              sf.ui.proTools.selectedTrack.outputPathButton.popupMenuSelect({
    menuPath: ["bus", "Folder 1 (Stereo)"],
});

              Let me know if those scripts work for you.

              Rock on!

              Reply1 Like
              1. Kitch Membery @Kitch2022-04-03 21:15:22.022Z

                @Ryan_DeRemer,

                Looking at your screenshot from earlier... It looks like you may have capitalized the menu path... "No Input", should be "no input". :-)

                Rock on!

                Reply1 Like
                1. Chad Wahlbrink @Chad2022-04-03 21:28:23.219Z

                  @Ryan_DeRemer

                  I noticed on the system requirements for Soundflow, that they suggest the versions of Pro Tools listed below. You told me on our other thread that you were running PT 2021.6 because 2021.10 gave you issues. It could be worth trying to update to 2021.12 if you are willing to do that.

                  Recommended versions
                  macOS*: Catalina 10.15.7, Big Sur 11.6 or Monterey 12.3
                  Pro Tools (HD): 2021.7, 2021.10 or 2021.12 (English language only)***

                  After that, I'd suggest (as I said on the other thread) downloading the latest version of SoundFlow here.

                  Reply
              2. In reply toRyan_DeRemer⬆:
                Ryan DeRemer @Ryan_DeRemer
                  2022-04-03 21:57:06.564Z

                  @chadwahlbrink @chrscheuer @Kitch You guys are awesome!

                  Turns out I'm the guy that turns off all the Tool Tips! Lol Turned them back on, restarted PT and SF, fixed everything. All the scripts function as intended now. :D

                  So happy, these scripts are freaking amazingA

                  Reply3 LikesSolution
                  1. Kitch Membery @Kitch2022-04-03 22:10:12.683Z

                    Rock on, @Ryan_DeRemer!! :-)

                    Reply1 Like
                  ReplyAdd progress note