• Features

  • Misc features request for the future

A wish-list for the future from our first month of use.

  • 1. The joined client should have a button to (or maybe automatically) save the file that the session host sends. Then the musicians can rehears by themself at home and this also makes it a smooth to add new local song files to be able to make personal edits.

  • 2. Persisted settings of "Host Session" and "Join Session".

  • 3. Metronome.

  • 4. Ability to "start/stop" and "move next" from joined clients.

  • 5. Disable audio and its screen components to make room for font size / scroll speed on small screens.

  • 6. The “Elapsed bar” should be relative so wherever you touch the bar, the movement should do a relative change.

  • 7. On Iphone, in portrait mode, it would be nice to be able to view the playlist in joined session. This is for the the musicians that only want the setlist.

  • 8. Paypal for donations

    rowe2000 2. Persisted settings of "Host Session" and "Join Session".
    Can you explain this request please? Cause i also made a comment about how easy it was to drop off the host connection and am wonderring if you found this to be an issue as i feel once you join a session you expect it to be rock solid untill you make a more solid decision to disconnect, now all you have to do is accidently drop to close a window and bang youre disconnected, it to me seems very unnecessary as you have decided to be a slave and you want to stay a slave with no chance of disconnection unless you make a deffinite decision to disable this operation by either unticking join session or restarting the software.

        Damir We haven’t experienced any trouble of network drop, but I’m happy you noticed that.

        The request is more about don’t need to go to settings and start host and then go to settings on clients and join, in that order, at the start of every rehearsal, sound check and performance. I think that could be persisted and automated!

        I just simulated Wi-Fi dropout by disabling the Wi-Fi, when enabling it seems that the client don’t join automatically. I will test that more…

        Maybe the request could improve this too if the clients could continue to hammer to join the session…!

            rowe2000 OK! I see what you are saying it would be good if once you enable host and slaves and you loose wi fi connection once you reconnect it would be good if the host and slave settings are remembered and automatically connect again so you don’t have to go through this setup process again,
            Am I correct in my understanding?

            I think that is a good idea because you know what you want and if you have set it up how you want to work it should be remembered until you change it again , you should not need to keep recreating you work environment preferences, it should be remembered so when you fire up your ST3 it all just works the way you last left it.

            I noticed this idea has improved with foot pedals , now you can turn on your pedals and they work immediately while before you had to play around with settings to get them to operate.

                rowe2000 The request is more about don’t need to go to settings and start host and then go to settings on clients and join, in that order, at the start of every rehearsal, sound check and performance. I think that could be persisted and automated!

                The problem with this is that both host and client need to keep running all the time even if you locked your device. This will drain your battery very quickly. And if you forget to turn off the network feature at the end of the evening you can be sure that your device will be dead next morning.

                Whereas if there is no network session running and no audio playing when you lock your screen ST3 will consume no battery at all with the current implementation.

                    peter so you can’t make it when you power up ST3 it has remembered your preferred settings, which include host/ slave settings and all other settings no matter what, when you close Your iPad at end of gig it should place all opened programs to sleep and low power usage called sleep.

                    I think if we had an option I would rather have all my settings remembered, just turn on ST3 and hit play and presto everything is as was left last gig, the power issue should not be an excuse to not have it that way, I always run power to my iPad if I’m using it in a power hungry mode but that’s my choice, what’s important is having your device perform exactly how you want it every time without having to recreate its options every time.
                    When the device is closed it should disable ST3 power usage and when you open it up again it should be setup the same as you last used it in all respect, it’s the users choice how they want to run and so it’s made simple to use.

                    Perhaps have it when you shut down ST3 it resets to a power saving default like now, but if you just go to another software and return to ST3 it remembers everything how it was , and if you just shut down without exiting ST3 it remembers all settings but goes in to power saving mode, sleep, when you start up the device again it remembers the ST3 settings and just works as last setup.

                      Take a look at the host for example: if you are hosting and your screen locks for whatever reason, ST3 has only two options:

                      a) Keep the network session running and consume battery (this is currently done)
                      b) Terminate the session (and therefore drop all connected clients) and engage sleep mode

                      If I would choose b) then all clients are dropped and when the host is unlocked again, I can start the hosting session again, but all dropped clients will still be dropped. There is no way to initiate a connection request for previously connected clients from the host. And on the other hand the client can not try reconnects, because the restarted session will have a new id and therefore seem to the client like a different session.

                      So b) is not an option at all.

                      peter you revealed some aspects of that I didn't thougth of and maybe there's more...

                      But maybe could the "app in foreground" vs "app in background or screen locked" be the condition for when client will try to join a network session.

                      And the same for the host but with the addition that it keeps the host avaliable as long as there are clients connected.

                      When a ST3 client isn't visible, it shouldn't be necessary to stay connected to the host anyway. To me it seems very lightweight to connect to a host so then it might not cause problem if a client disconnect temporarily for some reason, and then try to join again when ST3 again shows in foreground.

                      Couldn’t the hostname be used as a key for the session so clients can merge with the previous session after the host reestablished and clients reconnected...?! I mean what's the probability that there is two different ST3-host's that have the same name running on the same network?!

                      MacOS hosts on charging maybe shouldn't disconnect.. but for iOS devices, I think this might save the battery.

                      Damir yes, I think if there could be a convenient condition for when to stop hammering to join a network session, I think this could solve most of network reconnect issues.

                      I see that the joined client already keeps scrolling if the connection drops, so most of the times you may not even would notice that it was gone if it could reconnect automatically.