• Support

  • Control ST3 on ipad from iphone

Version 4 will have remote control capabilities.

peter no disrespect, but how long do we still have to wait? I know it’s a lot of work to implement all the stuff you want to do, and it takes time, but for those that need certain functionality now, I would encourage to keep looking for ways to get things accomplished, until that glorious day when ST4 is released. I am certainly looking forward to the day!

      metamorfosis18 pretty sure it’s a complete rebuild, therefore there’s no way to currently add remote functionality to the current version, I say this as someone who is also waiting on this feature and possibly one of the first to suggest it a long time ago

        metamorfosis18 no disrespect, but how long do we still have to wait?

        As long as it takes, I rather get an improvement on ST3 than just a different version , Apple is very good at that , but Peter is not , thank goodness.

          The other thing that often occurs across major versions is that the 'internals' of the app are re-written, updated, etc. Apple releases new frameworks every year that provide more feature, capabilitiy, performance, reliability (lol! well, maybe...) and Peter will be evaluating which of these he updates from ST3 to ST4. And it's not like upgrading the RAM or GPU on your PC where you just take the old one out and slot the new one in. You usually also need to update the code in your app that interfaces with these frameworks.
          Then you have to test everything, because there's never only 1 way to do anything, and what Apple document may not necessary work, or work as expected.

          Yes, it's a lot of 'under the hood' stuff that we don't actually see most of in the final shiny product, but it is necessary. To not do it, means keeping older and older code. Even if it worked reliably now, that doesn't mean it will work as expected with the next iOS/MacOS update. So by updating the code, Peter is also trying to futureproof as much of the app as possible, for as long as possible.

          Developers also need to make hard calls on when to stop adding new features to a current, stable version of a product. Especially when they are already working on the next version. Every time Peter has to go back and change ANY code in ST3, there is a risk of introducing new issues (regressions). To add a new feature compounds that risk significantly. It may not even be possible without making significant changes to other parts of the code base which again compounds the risk. So as frustrating as it can be to us users, the absolute right thing to do is to stop adding any new functionality to ST3, and only fix major bugs. Also, all that time could be spent on working on ST4, where that same feature we want has been factored in from the start and will likely take less time and effort to implement. So, where do we want Peter spending his finite time? I think most of us would be saying on ST4.

          Being a developer can be thankless. Everything takes too long according to your customers and management. Vendors don't document stuff properly. Stuff doesn't work as expected, or sometimes even as documented.

          It is a complete rebuild from the ground up based on everything I have learned in version 3. Especially remote functionality does not work at all with how data is handled in version 3. I realised just recently that version 4 data handling also did not meet the requirements needed for remote capabilities. So I spent the last 2 weeks completely rebuilding the data layer. It's things like these that lead to long development times together with the fact that Apple likes to change technologies. Version 3 user interface is based on Apples UIKit framework which, knowing Apple, will be deprecated and completely replaced by SwiftUI sometime in the next couple of years. So Version 4 is build on SwiftUI which works completely different and require all views to be rebuild from the ground up.

          So the bottom line is: There is a little bit of code I can reuse from the Audio Engine but the rest is rebuild from scratch. And ST3 is no small app. It just takes time to move all functionality over and improve it. But it will be worth it. And ST3 works just fine the way it is. So there is no immediate need to replace it.

            peter Peter, I was just thinking about remote control this morning and had a question about the functionality.

            In a future version of ST that has remote control, I don't want every band member using ST as a Client to be able to remotely control the Host. Will there be some way to only grant remote control ability to specific users/devices?

            I know it could be as simple as a toggle switch in ST Settings that says "allow remote control of Host Session" that defaults to Off, and I'd just have to make sure no other band member turns this On.
            However, a bit like another thread (https://support.stagetraxx.com/d/3297-st-feature-req-roleidentity-based-lyric-sheetsnotesformatting) which also ran into this idea of role-based or identity-based access to features/functions when in Client/Host setup, are you considering building something like this into ST4? Or does that fall into the 'adding too much complexity' bucket?

              Remote control will most likely be enabled by defining a password on the host that you can set on the client if you want to use remote functionality. With no password or the wrong password you will just be able to see what happens on the host.

                peter I understand a bit better your work and efforts. I am using ST3 because I haven’t found anything better for running tracks, including Ableton Live which I used for many years. In my opinion your app is awesome and not to complicated for “regular” users. Thank you and really looking forward to an even stronger app when ST4 comes out.

                    metamorfosis18 no disrespect (your words) but you haven’t found anything better because there isn’t anything out there even remotely close.

                    And we are all waiting for Peter patiently. I can’t even think what it’ll take to get this done. I have been with the app since the beginning the first version, and I have other pro apps for different projects and things and Peter is the only developer that’s even shares progress, ideas and testing properly with users, many of us becoming his friends.
                    This app has become so great and solves so many issues and helps so many of us to perform.
                    Other apps I have haven’t even updated in a couple years, let alone regularly.

                    V4 will be here when he’s ready ☺️

                      Thanks Sharon 🙂. And I still think I can stick to my original plan of releasing end of the year.