No internet connection
  1. Home
  2. Support

prevent SF auto-update

By samuel henriques @samuel_henriques
    2021-04-05 16:29:14.369Z

    hello everyone,
    I have a machine still using an iPad 2, now unsupported with SF V4.2.4, and until I upgrade the surface, I need to keep SF on version 4.1.3. The workaround is keep installing SF all the time. Is there a way I could prevent SF from Auto-Update?

    Thank you so much

    Reply
    • 4 replies
    1. samuel henriques @samuel_henriques
        2021-04-05 17:44:44.147Z

        I guess the answer is here:
        IPad v1 problem.

        let me know if here is any workaround.

        Thank you

        Reply
        1. In reply tosamuel_henriques⬆:
          Christian Scheuer @chrscheuer2021-04-08 15:01:20.737Z

          Hi Samuel,

          We specifically don't allow users to block the auto-update process, since it's important for us to keep users on the most recent version, for a few reasons:

          • Our pricing model is centered around that we can keep costs low. Supporting users on old software versions would be prohibitively expensive for us. Google "pro tools compatibility" or system requirements for example, and you'll see the amount of headache you can easily get into when support between hardware, software etc. becomes complex.
          • SoundFlow Cloud Indie/Pro is a hybrid environment/solution between cloud and macOS. The software works in very close collaboration with our servers in the cloud. When we need to make changes to the servers, we need those changes to be performed in sync with changes to the client machines. Think about it a bit like Chrome - to support cloud/web content, you need your local platform to stay in sync with the latest development. The alternative to this is version compatibility hell.

          I've written more about these core architectural decisions here:
          https://soundflow.org/docs/getting-started/licensing-and-purchasing/why-subscriptions

          The issue here is that you're using an unsupported device and trying to use an unsupported way to work around a core component in SF.

          Reply1 Like
          1. samuel henriques @samuel_henriques
              2021-04-08 15:50:06.490Z

              hi Christian,

              That's what I figured, it would be crazy to support such old platforms. Eventually you need to draw a line on the support possibilities.
              This was really a workaround while we fix this.
              BTW, his is on another user account and has nothing to do with the memory problem I asked you about before easter.
              I'm still trying to understand that.

              thank you so much for your time

              Reply1 Like
              1. Christian Scheuer @chrscheuer2021-04-08 15:55:39.497Z

                Thanks for your understanding :)

                Reply
            • Progress
            • @chrscheuer closed this topic 2021-04-08 15:02:02.408Z.
            Reply (discussion)