No internet connection
  1. Home
  2. Support

Stream Deck does not wake from SF Screensaver

By Jim S @Jim_S
    2022-05-17 17:20:36.603Z

    Stream Deck does not wake from SF Screensaver

    System Information

    SoundFlow 5.1.4

    OS: darwin 19.6.0

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

    Steps to Reproduce

    1. Allow mac to sleep or screensaver to start.
    2. Wake mac.

    Expected Result

    Stream Deck displays deck, either through application trigger or via the SF app interface

    Actual Result

    No change to Stream Deck. Continues cycling colored SF logo.

    Workaround

    Restart SF or plug/un-plug Stream Deck.

    Other Notes


    Links

    User UID: pnEVPxO9mmWlUQ2QpPAw89fFZ8q2

    Feedback Key: sffeedback:pnEVPxO9mmWlUQ2QpPAw89fFZ8q2:-N2I1I1mhOE4P8q-HTmg

    Feedback ZIP

    Solved in post #10, click to view
    • 9 replies
    1. Kitch Membery @Kitch2022-05-17 17:43:48.914Z

      Hi @Jim_S,

      This 99% of the time is due to the Stream Deck device restarting because it temporarily is lacking enough power delivered on the USB bus.

      You can read more about how to troubleshoot the issue in the following article. :-)

      https://help.soundflow.org/en/articles/5761177-troubleshooting-stream-deck-freezing-connectivity-issues

      1. I think in this particular case it might be bug SF-482 that we're tracking internally.

        @Jim_S in any event thank you for reporting this. I'll add this to our internal bug report so we can take a look at your log files when we have time to look into the bug.

      2. J
        In reply toJim_S:
        Jim S @Jim_S
          2022-05-17 22:29:09.785Z

          Thanks @Kitch and @chrscheuer! Re: the power issue… Nothing in my setup has changed since I started using SF, and I had no issues for the first several months. Maybe the Stream Deck is giving out (it's a old v1 5x3)? But in the event it is SF-482, I'll keep an eye on the forum!

          1. It could be related, but I don't know for sure. Definitely worth checking out the article Kitch linked to. Wrt the freezing / connectivity issues, USB power delivery can change for a very long list of reasons, so it's worth checking out the troubleshooting steps for most Stream Deck related issues.

            But the screen saver stuff to me sounds more like SoundFlow not properly detecting that macOS came back from sleep, so is not necessarily Stream Deck hardware related (if you still see the color animation)

          2. J
            In reply toJim_S:
            Jim S @Jim_S
              2022-05-24 16:03:03.587Z

              Quick update: I've gone through the article Kitch linked to, and have swapped out the USB extender (both Tx and Rx sides) and continue to have the same issue. Direct-connect is not an option for security reasons. I have a few colleagues who use the same USB extender but have never had this "stuck on SF screensaver" issue. They, however, are using a Stream Deck XL instead of the 5x3 Mk1, so I think I'll try a different Deck.

              1. Hi Jim,

                Yea I think if the SF screensaver is still looping through the SF icon in various different colors, then that indicates the SF <> SD connection is good, but that SF doesn't understand it should stop showing the screensaver for some reason. That's what I meant in my original comment, and that's what we're tracking in SF-482.

                1. JJim S @Jim_S
                    2022-08-18 18:41:12.422Z

                    Hey @chrscheuer, I know you're tracking this as a bug, but wanted to give an update. I was using a v1 5x3 Stream Deck and decided to upgrade to an XL (I just have too many Soundflow keys :D ) and voila, no more stuck-on-screensaver. Hasn't happened since the day I plugged in the XL a couple weeks ago.

                2. S
                  In reply toJim_S:
                  SoundFlow Bot @soundflowbot
                    2022-08-29 07:18:34.173Z

                    This issue has been marked as Done

                    1. This should be fixed with SoundFlow 5.1.8 :)

                      Reply1 LikeSolution