No internet connection
  1. Home
  2. Support

All key commands have suddenly stopped working, please help

By Curtis Macdonald @Curtis_Macdonald
    2021-03-17 20:24:08.362Z

    All key commands have suddenly stopped working, please help

    System Information

    SoundFlow 4.2.3

    OS: darwin 19.6.0

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

    Steps to Reproduce

    Expected Result

    Was working, no

    Actual Result

    Workaround

    None determined

    Other Notes

    I can only trigger commands via clicking "Run Command" in the SoundFlow app, but keyboard commands are no longer working. I checked Mac OS X's system privacy settings and accessibility control, nothing looks like it has changed. I've reinstalled, rebooted, and yet the same problem persists. What else can I try to help remediate? Thank you so much.

    Links

    User UID: BAHRTrNpErQGSMCXb1Gj6AHsSU13

    Feedback Key: sffeedback:BAHRTrNpErQGSMCXb1Gj6AHsSU13:-MW0r0qR2u0xsLcUFcFw

    Feedback ZIP

    Solved in post #6, click to view
    Reply

    Linked from:

    1. Ventura Upgrade. Soundflow unresponsive
    2. SoundFlow can't display a dialog - Filed by AScheps
    3. Soundflow logged in but not working
    4. Granted access but doesn't accept it
    • 10 replies
    1. Christian Scheuer @chrscheuer2021-03-17 20:31:11.724Z

      Hi Curtis,

      The first thing to double check is that the correct profile is selected. Can you double check this?

      Reply
      1. Christian Scheuer @chrscheuer2021-03-17 20:33:53.524Z

        From your settings, it looks like the profile "Default Profile (Copy)" is selected, so from that, that looks correct, I presume.

        Reply
        1. Christian Scheuer @chrscheuer2021-03-17 20:35:15.640Z

          The log file doesn't appear to be showing anything out of the ordinary.

          Can you give an example of a shortcut that used to work and now doesn't? I know it's a general issue, but we need to have a specific command to start reproing/testing with.

          Reply
      2. In reply toCurtis_Macdonald⬆:
        Christian Scheuer @chrscheuer2021-03-17 20:40:12.497Z

        One other thing we can do to help narrow down why this is happening (I haven't seen a report like this before) is to try to reinstall 4.1.10 temporarily to see if it changes anything:

        https://soundflow.org/cp/downloads/sfsx-1/soundflow-4,1,10

        Reply
        1. In reply toCurtis_Macdonald⬆:
          Christian Scheuer @chrscheuer2021-03-17 20:41:28.037Z

          And yet one more suggestion to help troubleshoot. If it for some reason has to do with macOS permissions, it may help to reset those completely using this command in Terminal:

          tccutil reset All org.soundflow.sfsx
          ReplySolution
          1. In reply toCurtis_Macdonald⬆:
            Curtis Macdonald @Curtis_Macdonald
              2021-03-17 21:15:57.719Z

              Hi Christian, thanks for the quick response on this! I tried downgrading to 4.1.10, and also reset permissions as you described. Rebooted, reinstalled version 4.2.3, and problem still persists :(

              I'm trying to test via simple, general commands like 'Bypass SoundFlow', [ctrl + esc], but still not registering... what else can I try or where else can I look?

              Reply
              1. Curtis Macdonald @Curtis_Macdonald
                  2021-03-17 22:23:22.635Z

                  aaaand now it's working, I don't understand it, but it has been resolved. once again Christian I very much appreciate your FAST reply to tech issues. thank you again

                  Reply1 Like
                  1. Christian Scheuer @chrscheuer2021-03-18 08:57:28.348Z

                    Thanks for keeping a positive approach to fixing it :) I know this stuff can be stressful, and even more so when the errors make no sense.
                    Lmk if this ever occurs again and hopefully we can use that to better understand the pattern that leads to the error. But let's cross our fingers it was magically fixed and won't ever return ;)

                    Reply
                • In reply toCurtis_Macdonald⬆:
                  Curtis Macdonald @Curtis_Macdonald
                    2021-03-26 16:20:52.019Z

                    After some more testing, this bizarre behavior keeps coming up for me, but is solved by logging out and logging back in to mac os x. Each time I log back in, soundflow works as expected. A little annoying, but workable.

                    Thanks again!

                    Reply1 Like
                    1. Christian Scheuer @chrscheuer2021-03-28 12:12:07.592Z

                      Hi Curtis,

                      Thanks for this additional info. I suppose there might be a possibility of SoundFlow ending up blocking itself if for some reason another macOS user is logged in and SF is running on that account.

                      Reply
                    ReplyAdd progress note