No internet connection
  1. Home
  2. Support

Open Send on Next Available Slot not finding popupMenus

By Gary Philips @Gary_Philips
    2022-01-13 20:39:51.197Z

    Open Send on Next Available Slot not finding popupMenus

    System Information

    SoundFlow 4.3.8

    OS: darwin 19.6.0

    ProductName: Mac OS X
    ProductVersion: 10.15.7
    BuildVersion: 19H1615

    Steps to Reproduce

    1. select a track in PT
    2. run script

    Expected Result

    open selected path on first avail insert

    Actual Result

    error at line 70

    Workaround

    no

    Other Notes


    Links

    User UID: SvvTAi4f55Q3ZPiR87JW0e8nJNs2

    Feedback Key: sffeedback:SvvTAi4f55Q3ZPiR87JW0e8nJNs2:-MtK9kXEkZg3TTgdl1Ry

    Feedback ZIP

    • 28 replies

    There are 28 replies. Estimated reading time: 12 minutes

    1. Kitch Membery @Kitch2022-01-13 20:46:03.824Z

      Hi @chrscheuer

      Please se @raphaelsepulveda's post regarding this;

      1. Thanks.
        Is there a screen recording of this? I'd need to see that to understand what's going on. It's a very long thread - can you give a quick summary - how does one reproduce this?

        1. Gary, do you have Tooltip Settings set to on?

          https://help.soundflow.org/en/articles/5637993-known-issues

          1. Gary Philips @Gary_Philips
              2022-01-13 21:00:13.764Z

              checking

            • In reply tochrscheuer:
              Gary Philips @Gary_Philips
                2022-01-13 21:00:03.767Z
                1. Gary Philips @Gary_Philips
                    2022-01-13 21:03:37.806Z

                    tool tips set to ON

                    FWIW I'm having no problem recall track presets or instantiating plugins via UI

                    1. In reply toGary_Philips:

                      Thank you. This is exactly what I expected. Something is stealing the focus from the popup menu before SF is able to click it. I don't know what that would be, but make sure you're not running any runForever scripts or any other keyboard automation software etc. or other things that could be the reason why the menu is not allowed to stay open.

                      1. It could also be if you're using macOS spaces or something else that could steal focus (again, that could be a million things). I can't really tell from the video how this is being invoked but the culprit here seems to be external to the script itself.

                        1. To be a bit more clear - this is my theory, just based on the speed in which the popup menu is dismissed/cleared. I can't be 100% certain that's what's happening, but it would explain the errors if that's the case.

                          1. Do you have a EuCon device attached with the system?

                            1. Gary Philips @Gary_Philips
                                2022-01-13 21:26:43.578Z

                                YES. Avid S3 and Avid Control on a tablet.

                                1. As a troubleshooting step, try to completely disable Eucon. Not as a solution, but to see if it's Eucon interfering with the focus in PT. My theory is that something - it could be Eucon - tries to change the focus of the PT app when you click the send popup menu.

                                  1. Hmm.. How are you triggering the script? I can't see any triggers set up in your account.

                                    1. @Kitch @raphaelsepulveda have you tried with having an appActivateMainWindow call as part of the script to ensure that PT is focused prior to the script running?

                                      1. Kitch Membery @Kitch2022-01-13 21:40:54.058Z

                                        I have not. @raphaelsepulveda have you tried that?

                                        1. Gary Philips @Gary_Philips
                                            2022-01-13 21:52:07.188Z

                                            I have tried that. @raphaelsepulveda gave me that line when we were initially troubleshooting. Gave us the same result but with protools focused.

                                          • In reply tochrscheuer:

                                            I suggested it here as part of troubleshooting but may have gotten lost in the noise Open Send on Next Available Slot issue #post-17
                                            Might be worth trying again. cc: @Kitch

                                        2. In reply tochrscheuer:
                                          Gary Philips @Gary_Philips
                                            2022-01-13 21:39:01.289Z

                                            Aargh. Same error with Eucon off. I also use a Wacom pen table. Disconnected that. Still same result. Kensington trackball, but most people have that running. Turned off Hazel. Same result. Turned off Keyboard Maestro, same result. Hmmm

                                            1. Hm ok, but that's good, making progress in isolating what's going on :)

                                              1. Could you try with just this code. Make a new script, add this code, then add a Keyboard Trigger to it and then press that key combination.

                                                sf.ui.proTools.appActivateMainWindow();
                                                sf.ui.proTools.selectedTrack.sendButtons[0].popupMenuSelect({
                                                        menuPath: ['no send'],
                                                });
                                                

                                                Also, as mentioned, make sure you aren't using macOS Spaces with PT in some kind of full-screen mode or in a separate "space" as I believe that can mess up focus as well.

                                                1. Gary Philips @Gary_Philips
                                                    2022-01-13 21:54:27.664Z

                                                    OK, I don't even know what Spaces is so I doubt I have it set up. not using full screen mode on anything. Will paste this code next.

                                                    1. Gary Philips @Gary_Philips
                                                        2022-01-13 21:58:06.249Z

                                                        it threw an error at line 2. Here is the log info. thanks for your persistence!

                                                        << Command:  PopUP test [user:default:ckydifbru0000y210fw7nta8g]
                                                        
                                                        13.01.2022 13:56:36.09 <info> [Backend]: #Key: ctrl+command+alt+t  (17) ->  PopUP test [ckydifhwi0001y210plak3mhe]
                                                        Validating command... user:default:ckydifbru0000y210fw7nta8g
                                                        Invoking command...user:default:ckydifbru0000y210fw7nta8g
                                                        
                                                        13.01.2022 13:56:36.09 <info> [Backend]: >> Command:  PopUP test [user:default:ckydifbru0000y210fw7nta8g]
                                                        
                                                        13.01.2022 13:56:36.17 <info> [Backend]: Clicking with mouse here: 1991, 28
                                                        
                                                        13.01.2022 13:56:36.33 <info> [Backend]: Clicking with mouse here: 397, 767
                                                        
                                                        13.01.2022 13:56:38.23 <info> [Backend]: [SF_FIREBASE_WS]: Sending keep-alive
                                                        
                                                        13.01.2022 13:56:38.60 <info> [Backend]: Logging error in action (01) WaitForPopupMenuAction: Popup window was not found after waiting 2000 ms
                                                        Logging error in action (01) OpenPopupMenuFromElementAction: Popup menu was not found
                                                        
                                                        13.01.2022 13:56:38.60 <info> [Backend]: Logging error in action (01) PopupMenuSelectAction: Could not open popup menu
                                                        !! Command Error:  PopUP test [user:default:ckydifbru0000y210fw7nta8g]:
                                                        Could not open popup menu ( PopUP test: Line 2)
                                                            Popup menu was not found
                                                            Popup window was not found after waiting 2000 ms
                                                        
                                                        << Command:  PopUP test [user:default:ckydifbru0000y210fw7nta8g]
                                                        
                                                        
                                                        1. Got it. So something's definitely still stealing focus. Wrt macOS Spaces I was asking that since your video didn't show the full screen, so it could either do that if you only select a portion of the screen to record of course, or it could look that way if you have macOS Spaces turned on.

                                                          1. Since you're the only person to ever report this, and since I'm not seeing this issue when using a copy of your account (and none of the other guys can repro this either) the issue would have to be with some local setting on your computer. Either incompatibility with some configuration setting in macOS, or some other piece of software interfering.

                                                            You already were able to rule out a bunch of them earlier. My suggestion would be to keep digging in that direction, simply turning off other pieces of software until you only have PT running on as "clean" a setup as you can (without uninstalling anything, hopefully, just disabling/quitting things).
                                                            Hopefully at one point it starts working and then you'd found the culprit.

                                                            1. I noticed somebody yesterday had some Logitech Control software running that was stealing keyboard strokes. I wonder if you have some kind of special touch-based mouse driver installed that could be trying to revert focus based on mouse clicks. Just a very wild guess. But try to think along those lines in terms of what could be interfering. When you run the script you should see the popup menu be open for longer. The fact that it gets dismissed so quickly points to that some other app receives focus or simulates a mouse click somewhere else.

                                                              1. Kitch Membery @Kitch2022-01-13 22:21:59.073Z
                                                                1. In reply tochrscheuer:
                                                                  Gary Philips @Gary_Philips
                                                                    2022-01-13 22:23:05.994Z

                                                                    Ok. Thank you. I’ll start heading down that road. Perhaps it’s not disconnecting the peripherals so much as turning off any software that goes with them. Question: why is it not a problem with Teezio plug package? Or with loading track presets? But only with these sends?

                                                                    1. That inconsistency is what lead me to believe that it was Eucon or peripheral related, since Eucon might have some kind of specific thing it does when a send gets focused.
                                                                      But yea, it's a mystery right now why those would work different from each other.