No internet connection
  1. Home
  2. Support

when logged in to Soundflow the focus is always pulled away from Pro Tools

By Martin Pavey @Martin_Pavey
    2025-01-19 18:41:10.101Z

    when logged in to Soundflow the focus is always pulled away from Pro Tools

    System Information

    SoundFlow 5.10.1

    OS: darwin 23.6.0

    ProductName: macOS
    ProductVersion: 14.6
    BuildVersion: 23G80

    Steps to Reproduce

    1. Logged in to Soundflow
    2. Try to start a new session from the menus in Pro Tools
    3. Menus close themselves before they can be selected
    4. Tried stopping all running items in Soundflow
    5. Does not fix problem
    6. Quitting Soundflow fixes the problem

    Expected Result

    Menus to be available

    Actual Result

    Pro Tools menus close themselves

    Workaround

    Quitting Soundflow

    Other Notes

    I can see a constantly running process in activity monitor but even if I quit it the problem persists.

    Links

    User UID: O9PPunNg7NTZzSJwHFxicCAh37q2

    Feedback Key: sffeedback:O9PPunNg7NTZzSJwHFxicCAh37q2:-OGzra_lWKeyP2XyaRCY

    Feedback ZIP: vQqgwxhM11IfnCAFWiiCamoBIl0Tc2uK0XzWzxjBL3/vknxBm3xsYL9OK7dPBjXh/orhsDtUyM5qUqr9jcqnllyBUhBpJ8U9OuU1YOOgEkhAoaknGTgtqFMz/tEggWa3vFjpsKhVDVTfAnFGZzIM6AB5aAK2Rx/MtnuwS849nJQpLBnwJKHEo/0NQk+sujqiHWJ/2yTvNDFrJf4MauDVia6QR2RNDFGFZcWtlwem6tPi+yNNj7ifSBI8hTINBgWBpURp5Iqyl2C+gF4qKvtCFzuqJcBL56MBTj6QCqZoLwTJVas0sw7hg33/WpQLXG0a9XXhikFe8/zB97j7zqsgQgQewzM8tQzZnTo/ezdXE70=

    Reply
    • 12 replies

    There are 12 replies. Estimated reading time: 14 minutes

    1. Christian Scheuer @chrscheuer2025-01-20 14:32:51.859Z

      Hi Martin,

      There was a bug in a previous version of Pro Tools, where, when any program (SoundFlow including) would try to ask a question (such as, "where is this button"), Pro Tools would close any popup menus.
      We worked with Avid to fix this a few versions ago. Looking at your logs, you're running PT 2024.10, so this is surprising that you're seeing the issue on the newest version of PT.

      The workaround is to avoid having any scripts run in the background (for example, decks that send questions to PT).

      You can search "SF-1189" in the forum to see more details of similar reports.

      Reply
      1. MMartin Pavey @Martin_Pavey
          2025-01-20 17:03:40.680Z

          Hi Christian

          I'm running 2024.10.2.
          Do you think they have re-instated the bug?

          The only running process I know I use is 'open output window on attentioned track'.
          But I have that switched off when I'm not using it.

          Thanks

          Martin

          Reply
          1. Christian Scheuer @chrscheuer2025-01-20 17:19:14.751Z

            open output window on attentioned track

            This script most likely runs in the background and causes the problem. I would disable this completely - make sure it's never started. Even disabling it after it already started running could mean it's still doing stuff in the background, due to how runForever scripts work.

            It does sound like the bug has come back, but I'm not sure exactly why this would happen, as I'm pretty sure we did very thorough testing of this.

            @Chad can you reproduce this behavior using the script Martin talks about (on macOS 14.6)?

            Reply
            1. MMartin Pavey @Martin_Pavey
                2025-01-20 19:29:35.487Z

                Hi Christian
                Here is the constant message Soundflow is sending.
                Can you tell what command is causing this, or is it standard?
                Thanks

                20.01.2025 19:26:34.31 [Backend]: Logging error in action (01) EnsureTrackListViewIsAccessibleAction: SoundFlow.Shortcuts.Ax.AxNodes.AxPtTrackListView could not get required UI element from null UIElement of type SoundFlow.Shortcuts.Ax.AxNodes.AxPtMainWindow because:
                Logging error in action (01) GetTrackSelectionAction: Could not ensure Track List View is accessible

                Reply
                1. Christian Scheuer @chrscheuer2025-01-20 20:09:34.981Z

                  Hi Martin,

                  Without full context of your log file, looking just at that part is not meaningful. There's nothing inherently right or wrong about what you're quoting here.
                  If it's happening all the time, as I said, you've most likely got a script running in the background. Remove any scripts that use runForever and you should be good to go again. This also includes potential apps that could be making calls in the background.

                  Reply
                  1. Christian Scheuer @chrscheuer2025-01-20 20:37:04.955Z

                    From what I can tell, it's likely you might be using a meta command on one of your decks, which may be using a service that runs in the background.

                    This could be the Stream Deck Plus you've got set up. The deck that has the button using a service gets loaded around this time in the log:

                    
19.01.2025 18:35:26.08 <info> [Backend]: #App: Activate "com.apple.finder" -> 1 Streamdeck Finder [ckfyjcqua00013z1079sp1oyn]

19.01.2025 18:35:26.08 <info> [Backend]: [AxDeckInstance] Setting up render frequency at 15 frames/sec, equalling 66 ms per render
[AxDeckInstance] InstanceShow: user:ck09nfzux0000k710yemj9ut5:ckbi9s0k4000zbq10rz6k5jy8:streamDeckHid.CL18I1A01601.d62d5331-f0f2-47ac-8224-41066faac00f (1 Streamdeck Finder) Device: 'CL18I1A01601'
[AxStreamDeckDevice id#5] Device 'CL18I1A01601' -> ShowDeckInstance: user:ck09nfzux0000k710yemj9ut5:ckbi9s0k4000zbq10rz6k5jy8:streamDeckHid.CL18I1A01601.d62d5331-f0f2-47ac-8224-41066faac00f
[AxStreamDeckDevice id#5] HideDeckInstance

19.01.2025 18:35:28.52 <info> [Backend]: #App: Activate "com.avid.ProTools" -> 1 Streamdeck left [ckfyjdd9d00023z10fgqdstjl]

19.01.2025 18:35:28.52 <info> [Backend]: #App: Activate "com.avid.ProTools" -> 1 Streamdeck Right [ckfyjdqwn00033z10euugc8om]
#App: Activate "com.avid.ProTools" -> 1 Streamdeck Audiosuite [cljwrf7tx00000e106442u370]
#App: Activate "com.avid.ProTools" -> 1 Streamdeck Plus [cljwrg4ny00010e10rgt9na7n]
#App: Activate "com.avid.ProTools" -> 1 Streamdeck Pedal [cllmde08m0005oo10knfkyqfu]
#App: Activate "com.avid.ProTools" -> 1 Streamdeck Audiosuite 2 [cls7r7lrz0000uj10f35nui79]
#App: Activate "com.avid.ProTools" -> Follow Focused Track [cm30ian240002dh10lgsuqy4g]

19.01.2025 18:35:28.52 <info> [Backend]: [AxDeckInstance] InstanceShow: user:ck09nfzux0000k710yemj9ut5:ck9yhqrzj00015p10pyq4kddd:streamDeckHid.CL30I1A03741.84472f14-f9dd-44a9-886d-dc7203a2b4a2 (1 Streamdeck left) Device: 'CL30I1A03741'
[AxStreamDeckDevice id#1] Device 'CL30I1A03741' -> ShowDeckInstance: user:ck09nfzux0000k710yemj9ut5:ck9yhqrzj00015p10pyq4kddd:streamDeckHid.CL30I1A03741.84472f14-f9dd-44a9-886d-dc7203a2b4a2
[AxDeckInstance] Setting up render frequency at 15 frames/sec, equalling 66 ms per render

19.01.2025 18:35:28.53 <info> [Backend]: [AxDeckInstance] InstanceShow: user:ck09nfzux0000k710yemj9ut5:ckbhzjyb300002a10kda0x0v0:streamDeckHid.CL18I1A01601.b1d73c3e-9145-4b3d-81cf-1955c27135e4 (1 Streamdeck Right) Device: 'CL18I1A01601'
[AxStreamDeckDevice id#5] Device 'CL18I1A01601' -> ShowDeckInstance: user:ck09nfzux0000k710yemj9ut5:ckbhzjyb300002a10kda0x0v0:streamDeckHid.CL18I1A01601.b1d73c3e-9145-4b3d-81cf-1955c27135e4
[AxStreamDeckDevice id#5] HideDeckInstance
[AxDeckInstance] InstanceShow: user:ck09nfzux0000k710yemj9ut5:cljlt2p310000v510ont1hekl:streamDeckHid.CL28K1A08800.2f5b0f14-aa7e-46c7-87aa-a61573d1aa40 (1 Streamdeck Audiosuite) Device: 'CL28K1A08800'
[AxStreamDeckDevice id#3] Device 'CL28K1A08800' -> ShowDeckInstance: user:ck09nfzux0000k710yemj9ut5:cljlt2p310000v510ont1hekl:streamDeckHid.CL28K1A08800.2f5b0f14-aa7e-46c7-87aa-a61573d1aa40

19.01.2025 18:35:28.53 <info> [Backend]: [AxDeckInstance] Setting up render frequency at 15 frames/sec, equalling 66 ms per render
[AxDeckInstance] InstanceShow: user:ck09nfzux0000k710yemj9ut5:cliej9rxl00008g1086e0n160:streamDeckHid.A00WA31412XI5F.d3f8c823-1e43-49a8-a116-c02a531bac85 (1 Streamdeck Plus) Device: 'A00WA31412XI5F'
[AxStreamDeckDevice id#6] Device 'A00WA31412XI5F' -> ShowDeckInstance: user:ck09nfzux0000k710yemj9ut5:cliej9rxl00008g1086e0n160:streamDeckHid.A00WA31412XI5F.d3f8c823-1e43-49a8-a116-c02a531bac85
[AxDeckInstance] Setting up render frequency at 15 frames/sec, equalling 66 ms per render

19.01.2025 18:35:28.53 <info> [Backend]: [AxDeckInstance] InstanceShow: user:ck09nfzux0000k710yemj9ut5:cllmcu5pc0002oo10vp4nz2k7:streamDeckHid.FL09L1A07791.5b1281b8-08f6-4e5e-b3d0-0f4e6823cc41 (1 Streamdeck Pedal) Device: 'FL09L1A07791'
[AxStreamDeckDevice id#4] Device 'FL09L1A07791' -> ShowDeckInstance: user:ck09nfzux0000k710yemj9ut5:cllmcu5pc0002oo10vp4nz2k7:streamDeckHid.FL09L1A07791.5b1281b8-08f6-4e5e-b3d0-0f4e6823cc41
[AxDeckInstance] InstanceShow: user:ck09nfzux0000k710yemj9ut5:ckw25fo4000007s1082l8yhpa:streamDeckHid.CL05K1A00274.8c12a38a-f335-4797-94a6-d72ce5a8f5d5 (1 Streamdeck Audiosuite 2) Device: 'CL05K1A00274'
[AxStreamDeckDevice id#2] Device 'CL05K1A00274' -> ShowDeckInstance: user:ck09nfzux0000k710yemj9ut5:ckw25fo4000007s1082l8yhpa:streamDeckHid.CL05K1A00274.8c12a38a-f335-4797-94a6-d72ce5a8f5d5

19.01.2025 18:35:28.53 <info> [Backend]: [BasicServiceInstance #1] Constructed

19.01.2025 18:35:28.53 <info> [Backend]: [BasicServiceInstance #1] Setting up basic service
                    Reply
                    1. Christian Scheuer @chrscheuer2025-01-20 20:37:54.653Z

                      There's a bunch of scripts and decks being activated here at the same time. It could both be the "Follow Focused Track" that causes the problem, or a meta command on one of the decks.

                      Reply
                      1. MMartin Pavey @Martin_Pavey
                          2025-01-20 20:50:08.199Z

                          Could it be this on the streamdeck plus?

                          if (globalState.isFollowFocusedTrackActive) {
    if (sf.ui.proTools.selectedTrack.outputWindowButton.value.invalidate().value == 'open') {
        sf.ui.proTools.selectedTrack.outputWindowButton.elementClick()
    }
};

globalState.isFollowFocusedTrackActive = !globalState.isFollowFocusedTrackActive;

sf.interaction.notify({
    title:`Follow Focused Track is now: ${globalState.isFollowFocusedTrackActive ? 'ON' : 'OFF'}`
})
                          Reply
                          1. Christian Scheuer @chrscheuer2025-01-20 20:58:25.487Z

                            It might be quickest to follow Chad's advice to turn everything off, ensure things are stable, then turn them on one by one until you find the culprit.

                            Reply
                            1. MMartin Pavey @Martin_Pavey
                                2025-01-20 21:01:24.031Z

                                Ok will do.
                                Thanks

                                Reply
                    2. In reply tochrscheuer⬆:
                      Chad Wahlbrink @Chad2025-01-20 20:51:56.029Z

                      Hi @chrscheuer and @Martin_Pavey,

                      I'm not able to reproduce this bug on my end Sonoma installation with Pro Tools 2024.10.2. I tried running the "Output Window: Follow Selected Track" command and running Pro Tools Track Control, which either use some runforever or services.

                      I am currently running macOS 14.7.1, so I'm not able to test with macOS 14.6 at the moment.

                      I would try disabling the Application triggers for some of the devices and scripts which activate when "Pro Tools" is activated.

                      It seems like the errors in your logs begin once you activate Pro Tools, which is in turn activating each of the following:

                      • 1 Streamdeck Left
                      • 1 Streamdeck Right
                      • 1 Streamdeck Plus
                      • 1 Streamdeck Pedal
                      • 1 Streamdeck Audiosuite
                      • 1 Streamdeck AudioSuite 2
                      • A "Follow Focused Track" script

                      Try toggling this Application Trigger off for each deck. Then add one back in at a time, test menu functionality, and see if you can isolate it to one of the decks or scripts being active.

                      You could try updating Sonoma to the latest version to see if it helps. You don't have to update to macOS Sequoia, but sometimes updating to the latest version of your current macOS is helpful.

                      Reply1 Like
                      1. MMartin Pavey @Martin_Pavey
                          2025-01-20 20:55:33.038Z

                          Thanks Chad and Christian,
                          I'll try tracking it down tomorrow.
                          I might upgrade the OS, but I'm just starting a new project and it's pretty stable apart from this one thing.
                          Perhaps I can live with it for a bit longer?

                          Reply1 Like
                  ReplyAdd progress note