No internet connection
  1. Home
  2. Support

Cant use Soundflow app. See screen recording

By Kurt Oldman @Kurt_Oldman
    2024-10-14 16:55:17.767Z

    Cant use Soundflow app. See screen recording

    System Information

    SoundFlow 5.8.2

    OS: darwin 22.6.0

    ProductName: macOS
    ProductVersion: 13.6.4
    BuildVersion: 22G513

    Steps to Reproduce

    1. Open Soundflow
    2. "Something Went Wrong" message

    Expected Result

    Don't know, cant use the app

    Actual Result

    Don't know, cant use the app

    Workaround

    NA

    Other Notes


    Links

    User UID: i8aNOLsjgBX6nVfauKuuKMGS2ID2

    Feedback Key: sffeedback:i8aNOLsjgBX6nVfauKuuKMGS2ID2:-O9Ax8wxBm2TTn7RdCib

    Feedback ZIP: faFKpO8NWneOC98aP3eazOfDnFs1JDsf8HchtFL7bVktgNNRXxeFGrpbwk5G5Mr35dBRUxjQg1+T01oXnRVZ8wQMt6PPOuSXD3ONe56oyIRs2TKoKcFVkG9kyp6D28vP4aId/Q7qHBCDwM2rrs6T9rKy/yFfIktEVngHlmXxLHZX2uxxfA4T9F59S82BAQoq7nU3P3mKKUJfZln++TYy+YLNaRkDXsG1SG5DC6SEuKCrJbL7hqSKG4yIeclwMep8iMVh4X3MMkG3ciRce3DL7SdbEfPpnzLEutvu/iulCiVu7S0FZ3rq7AzDHZ5tViT812mlQwhcx2j2G+XmsEjMnFlWhsA33a4JkCWwlwALx64=

    • 17 replies

    There are 17 replies. Estimated reading time: 12 minutes

    1. In reply toKurt_Oldman:

      Hi Kurt,

      Thanks for providing the Youtube reproductions. I can confirm I see the same bug if I click the "Learn SoundFlow" button on the Start page.

      To work around this, please avoid clicking that button for now (you can go to that content here: https://soundflow.org/docs )

      To get SoundFlow responsive again, please close the app, then click the SF icon and choose "Edit macros & shortcuts".

      I'll make sure we log a bug for the broken "Learn SoundFlow" button.

      1. K
        In reply toKurt_Oldman:
        Kurt Oldman @Kurt_Oldman
          2024-10-14 17:03:47.756Z

          Don't have a "Learn Soundflow" as you can see on the video. This is the startup screen.

          1. The error came up after you clicked the "Learn SoundFlow" button on the Start page here (screenshot from your video):

            Avoid clicking that button, and you should be good to go.

            To get the app working again, close the window, and relaunch it as per the instructions I shared.

            1. I'll CC @Chad for further troubleshooting if needed.

          2. S
            In reply toKurt_Oldman:
            SoundFlow Bot @soundflowbot
              2024-10-14 17:12:17.497Z

              This report was now added to the internal issue tracked by SoundFlow as SF-1315

              1. K
                In reply toKurt_Oldman:
                Kurt Oldman @Kurt_Oldman
                  2024-10-14 17:12:51.740Z

                  This is what I get on startup:

                  1. Please follow the instructions I shared closely to get out of the error. You are likely clicking "Open SoundFlow". Since it was caught in a bad state, this will repeat unless you follow the instructions closely.

                      1. Close the app completely, by clicking the SF icon in the top right corner, and choose Quit.
                      2. Open the app again from Applications.
                      3. Now, click the SF icon again, and click "Edit macros and shortcuts" (not Open SoundFlow, as that would remember the state from you last opened it, which is the problematic state)

                      If this doesn't work, we'll likely have to clear your cache since it may be remembering the bad state - that being said, I had no problem following these steps here, so I think it's likely you missed one of them.

                  2. K
                    In reply toKurt_Oldman:
                    Kurt Oldman @Kurt_Oldman
                      2024-10-14 17:59:57.500Z

                      There was an older version of SF on this machine from month ago, maybe that's the issue.

                      1. Chad Wahlbrink @Chad2024-10-14 18:51:09.048Z

                        @Kurt_Oldman, could you open SoundFlow on your machine following Christian's instructions?

                        If not, you could also try installing the latest version of SoundFlow, 5.8.3. It's available on the website here:
                        https://my.soundflow.org/install

                        Let me know if you cannot open the app, and we can try to troubleshoot further.

                      2. S
                        In reply toKurt_Oldman:
                        SoundFlow Bot @soundflowbot
                          2024-10-14 19:17:55.470Z

                          Linked issue SF-1315 updated: The buttons on the Start Page that were not working has now been fixed internally. The fix will be part of 5.9.0 which is scheduled to come out in a few weeks.

                          1. K
                            In reply toKurt_Oldman:
                            Kurt Oldman @Kurt_Oldman
                              2024-10-14 19:42:47.831Z

                              OK will check back when 5.9 is released. Brocken startup page issue remains in 5.8.3 even after trashing related Application Support folder.

                              1. Chad Wahlbrink @Chad2024-10-14 20:26:09.919Z

                                Hi @Kurt_Oldman,

                                Thanks for the update. The "Learning SoundFlow" button will still have an issue on 5.8.3; however, that issue should be fixed on 5.9.0 in the coming weeks.

                                However, if you open the app without pressing that specific button and cannot use it currently, there may be a separate issue we need to resolve.

                                Here's a quick video that demonstrates how to avoid getting into the "bad state" when clicking the "Learning SoundFlow" button on the Start Page. Let me know if your system behaves differently than shown in this video. We can try other troubleshooting steps if you need them.

                                Thanks!

                                1. KKurt Oldman @Kurt_Oldman
                                    2024-10-14 21:49:05.876Z

                                    Thanks Chad, Yes that is not the case on my current machine, thanks for trying. The virtual MIDI port issue is probably an equally crippling problem when it comes to Cubase on M1/M2 and certainly a dealbreaker at this end. - Don't have access to an Intel machine at the moment to test. The virtual ports would have to be disabled one by one after every machine restart and would expand the cubase port setup file exponentially. Would need to be able to disable these ports (like in MIDI translator for example)

                                    1. Chad Wahlbrink @Chad2024-10-14 22:45:01.824Z

                                      Hi @Kurt_Oldman,

                                      Thanks for the reply. I'm sorry you are still having a technical issue with SoundFlow.

                                      Regarding the MIDI ports, I think taking that issue on a separate thread would be best. SoundFlow's virtual MIDI ports should only be active while the SoundFlow App is running. Quitting SoundFlow should remove all virtual MIDI ports. However, if that is not happening, we should explore that.

                                      To troubleshoot the issue of opening the app, here are a few thoughts:

                                      • Are you connecting to SF from behind a firewall or VPN? If so, it's best to use the SoundFlow Proxy product: https://soundflow.org/docs/licensing/offline#proxy

                                      • Is the computer's date/time set manually? There have been issues with machines that manually set dates and times. It's best to leave this setting as "Set date and time automatically" in System Settings.

                                      If the problem persists, I'd suggest taking another quick screen recording, starting with the app fully closed and launching it from Finder. That way, we can see what you are seeing on startup.

                                2. K
                                  In reply toKurt_Oldman:
                                  Kurt Oldman @Kurt_Oldman
                                    2024-10-15 00:09:46.709Z

                                    OK will do when we have more time available. PFSense firewall, no issues with any other apps, DAW / accessibility controls other than sound flow issues described above and the occasional Soundtoys server call crash. Maybe the MIDI port issue can be addressed in a future update. It's a function issue for ports like that since they create a new ID# on every start. Would have to pass on a $500 license fee for a proxy access.

                                    1. Chad Wahlbrink @Chad2024-10-15 21:25:16.484Z

                                      Understandable, @Kurt_Oldman. Thanks for your troubleshooting so far.

                                      When you have time, I will temporarily disable the PFSense and see if SoundFlow loads as expected. I'd imagine that is the likely roadblock in this scenario.

                                      The MIDI ports issue you describe is certainly worth exploring. As you did for this thread, it'd be best to log this separately using the Help/Issue Workflow.

                                      I'm not seeing any buildup from the virtual MIDI ports on my system. However, I'm unsure if this scenario is relevant to Cubase or MIDI Translator––I don't own a license for these specific apps. There is no code in SoundFlow instructing other applications to use the SoundFlow virtual MIDI ports, and these ports are only created and available when the application is open. You can read more about the MIDI ports in Soundflow here: Soundflow took over my midi controller, I can no longer get it to work. #post-4

                                      DISCLAIMER: The thread I linked just above references editing the appSettings.json with disableMidiInterface":true - however, I don't believe this functionality works on recent versions of SoundFlow.

                                    2. Progress
                                      with handling this problem
                                    3. K@Kurt_Oldman deleted this topic 2024-10-14 16:55:45.087Z.
                                    4. K@Kurt_Oldman undeleted this topic 2024-10-14 16:56:43.231Z.