No internet connection
  1. Home
  2. Support

Pro Tools Menu Background Color and track output routing error

By Matthew Facca @Matthew_Facca
    2020-11-24 17:05:00.028Z

    Pro Tools Menu Background Color and track output routing error

    System Information

    SoundFlow 4.1.6

    OS: darwin 17.7.0

    ProductName: Mac OS X
    ProductVersion: 10.13.6
    BuildVersion: 17G66

    Steps to Reproduce

    1. Open pro tools
    2. Create blank session
    3. Create new tracks
    4. Use SoundFlow command from an ipad surface to change track outputs to internal busses
    5. route audio tracks using macros and move into appropriate folders

    Expected Result

    Menu remains with its usual dark background and continues to route audio

    Actual Result

    Track output menu background changes to a light grey - this happens regardless of whether Pro Tools is in dark mode or not.
    Occasionally, after routing some tracks using macros and moving audio into approptiate PT folders, the macros would quit working and produce an error regarding the track's bus output. I cannot narrow it down to a specific bus or action which causes this. I've tried starting from my vocal and FX routing on the right of the session or from drums at the left, and there doesn't seem to be a specific point where this happens. Simply restarting Pro Tools will fix this, and if not, restarting the computer will.

    Workaround

    Pro Tools restart and/or computer restart

    Other Notes

    OS 10.13.6, PT 2020.11.0, SoundFlow v4.1.6


    Links

    User UID: baVmEIaEePaHE8BBMQGO2si5EFk2

    Feedback Key: sffeedback:baVmEIaEePaHE8BBMQGO2si5EFk2:-MMvCmvikEYltxUdXBgz

    Feedback ZIP

    • 9 replies
    1. Matthew Facca @Matthew_Facca
        2020-11-24 17:26:46.561Z

        Here are some screenshots of the affected output menu:

        My edit and mix windows are each on their own screen, in case that affects anything.

        and after running soundflow to change a track (or a group of tracks) output:

        Here's an example of one of my macros which seems to be causing the errors (apologies if screenshots aren't the best route to posting macros in the forum). It's never immediate, but happens over time after I've done a bunch of routing. I'm wondering if I need more wait time in the macro, maybe PT slows down slightly after more audio has been routed? I also have simpler macros which are simply the final "set track output" action, and these will also stop working at the same time, as well.

        1. Kitch Membery @Kitch2021-01-12 03:59:27.534Z

          Hi @Matthew_Facca,

          We've finally gotten around to making a video...

          Click here for more information about the Pro Tools Menus Issue and workarounds;

          I hope that helps.

          1. Matthew Facca @Matthew_Facca
              2021-01-12 20:14:42.107Z

              You guys are the best. Thanks!

          2. In reply toMatthew_Facca:
            Matthew Facca @Matthew_Facca
              2020-11-24 20:08:11.430Z

              Here's a shot of a failed macro and the log I receive afterwords This is the only action in the macro. Restarting Pro Tools & SoundFlow didn't help, neither did restarting the computer, so I'm thinking the issue must be in my selection of macros.

              Again, exerything was working as expected and suddenly stopped. I get a similar error with attempts to use SoundFlow to send to any active bus in the session.

              If I create a blank session without my template of folders and aux tracks, I can't seem to break the macros and they work as expected, so it's only with my template in the session (about 45 tracks of folders and auxes that it locks up. I've ensured that the I/O settings are identical before and after I import the template, so I know all the same busses are present in each situation.

              When I import the template but disable all the plugins so there is no significant DSP being used, the macros start working as expected but will eventually break.

              Thanks if you've read this far through my nonsensical ramblings!

              1. In reply toMatthew_Facca:

                Hi Matthew,

                The menu background color change is a known issue that SF has no control over. See here for more info:

                1. In reply toMatthew_Facca:
                  Matthew Facca @Matthew_Facca
                    2020-11-25 00:18:42.239Z

                    Thanks Christian. I think what I'm most confused about now is why the "select track output" macro gets locked up. If there were more actions in a chain with that macro I can understand it, but one action on its own isn't making sense to me. Do you have a recommended workaround for it? I've tried "Open Track Output Menu" but I haven't been able to find a suitable action to follow it to allow me to either select a bus or type text to enter a bus name.

                    1. Your screenshots seem to indicate you're using this from the Mix window. The command is designed to work from the Edit window. Maybe that's the issue?

                      1. Matthew Facca @Matthew_Facca
                          2020-11-25 02:27:45.397Z2020-11-25 03:20:53.534Z

                          Damn, I sure typed a lot in this thread for what ended up being such a simple solution. I'm embarrassed I didn't think to try this from the edit window at any point. I've tried everything I can and I can't seem to break it if I simply do it from the edit window, so the problem is solved.

                          Is it safe to assume that most commands have been written for the edit window? I do a lot of my work in the mix window, but if I can just add a menuPath: ["Window", "Edit"] and a wait for the edit window UI before the necessary commands, I should be in good shape.

                          Thanks Christian!

                          1. No worries :) It's much easier to help when somebody offers up a lot of context, so thank you for providing all that :)
                            Yes, I think it's fair to assume most are designed for the Edit window (I come from film, and we do most of our work in the Edit window so that's the historical reason for it).
                            Great we got it sorted :)

                      2. Progress
                        with handling this problem
                      3. @chrscheuer marked this topic as Done 2020-11-25 13:44:20.683Z.