• Beta
  • Open Beta Version 3.7.0

iCloud syncing does not work that way. There is no difference between a master and client device. All devices are the same. The technical term how this functions is "last write wins". So if you edit the same entry on 2 devices at the same time, the device that saves last, will win. A distinction between master and slave therefore makes no sense.

Manual sync would technically be possible with the audio files but not with the database content. And that would be very confusing if database changes are always synced automatically but files needed a manual action.

    peter Manual sync would technically be possible with the audio files but not with the database content. And that would be very confusing if database changes are always synced automatically but files needed a manual action.

    Agreed, i don't know the nitty gritty of the systems operation but if you can get it to reliably replace all iCloud data when you choose to upload to icloud from any device , and then update on all devices when any changes happen on any device would be perfect for me, and simple as if you dont want any sync just turn icloud off but when you turn it on i expect icloud to just update the device with the new turn on and quickly correct the new changes , i dont expect for the device to renew the whole icloud data, as that would take ages if you have a big database.
    If thats possible than thats all i expect.
    I can turn off the devices i don't want synced and easily turn the sync on and only update to new icloud sync but only with newly aded data.
    I still think when database is updated the information should have the number of data files that were updated on last sync so you know if all updates happened as you have the number of files in Song mode and can compare , thats why i want to see SONG NUMBER ON ALL DEVICES TO BE SEEN AT ALL TIMES. To make iclud syncing easier to track.
    Cheers Damir

      Hello Peter, thanks for the hiding chords change as well as all the improvements. Where do i report issues.
      I noticed that the counter icon on the history button isn’t resetting. It resets after restarting the App
      I also changed the assignable buttons to MIDI and now they seem to retain the MIDI text even if I change the buttons to another function. It resets after a restart the App.

        Hi Peter, i just experienced multiple crashes while syncing to the st3 database, i sent you the log of today but i am not sure there is anything in it , if not it means there is an issue with the log system.

          Damir I can turn off the devices i don't want synced and easily turn the sync on and only update to new icloud sync but only with newly aded data.

          Unfortunately that would work with the files but not with the database. I tried it that way in the first place but the problem is that as soon as you enable iCloud sync, the local database will contain sync information for each database entry. When you disable sync, this information is kept and can not be deleted as it is not accessible to the app. When you reenable iCloud, it will try to sync all local changes you made while sync was off even if you select to only download changes from iCloud. And that is rooted deep inside of iOS and I can not change that. The only solution is to drop the whole database file when you enable iCloud sync with the download option and reload everything from the cloud.

          So you should not switch sync on and off on a regular basis. Either you want to use syncing, then leave it on. Or you don't and then don't turn it on at all.

          Tim_pbjp Where do i report issues.

          Report issues here. That's why we have this tread 🙂. Which counter do you mean? I am not a aware of any counter on the history page or icon.

          Damir if not it means there is an issue with the log system.

          If an app crashes it no longer runs. How on earth should it log anything if it is no longer running? We will have to wait for the crash log to show up in Testflight.

            peter If an app crashes it no longer runs. How on earth should it log anything if it is no longer running? We will have to wait for the crash log to show up in Testflight.

            I don't know how the crash log is interfaced in to the system i thought it was an external thing monitoring the behaviour of the software but its obviously not.
            Eventually i managed to get a full database sync and now i am up to date with iCloud for now.

            peter The only solution is to drop the whole database file when you enable iCloud sync with the download option and reload everything from the cloud.

            So you should not switch sync on and off on a regular basis. Either you want to use syncing, then leave it on. Or you don't and then don't turn it on at all.

            I don't mind that as long as everything works , i would be happy to run that way as its the same what i have now with other apple apps.
            Good luck with the repairs.

            Hi Peter, I badly explained myself.
            Regarding the History button “icon” there is a red number attached to the icon that increments by one each time a song is played. This number was not resetting even after I reset the history and only reset itself after I restarted the App.

            I hope this helps.

              Tim_pbjp There should never be a red number displayed above the History tab button. This number should only be displayed on the Queue tab button which you have most likely not enabled in the Queue settings. The question is: how did the number show up in the first place? I don't see it no matter what I do.

                Regarding my other point raised:
                The text “MIDI” does not disappear when I change Assignable buttons. See below:

                peter The queue Tab number is working fine.
                Sorry, but I don’t know how I got it showing up on the history tab button. If it happens again, I will trace my steps back and let you know.

                The midi button issue is a good find. I can reproduce it and will fix it in the next update. Thanks!

                The next update will need a bit more time. I have updated my iPads and Phones to iOS16.4 and now I can no longer deploy the app to these devices for testing. The Apple developer forum is full of reports about this issue. Without testing I can not release a new update. Now I have to wait for a new version of Xcode from Apple or try to work with a beta version of Xcode which I would like to avoid.

                New beta build 8725

                Apple updated XCode today and I was able to finishe the next beta version.

                Bad news is, that I ran into some issues when enabling iCloud sync with the option to upload the data into the cloud. There is simply no way to delete the iCloud data from a device that is not yet part of the iCloud sync group. Whenever I tried to do the, the remaining devices immediately started to reupload their data into the cloud.

                On one hand this is a good thing, as it will minimize the risk of data loss but this means, that the upload option will try to merge local data with the cloud data which can lead to duplicates if a device joins for the first time as each song on that device will be considered a new song in the cloud.

                The merge option however does work well if you disable iCloud, work make some changes and reenable iCloud. All changes are tracked even when iCloud is disabled and merged back into the cloud.

                Added

                • Sync button in settings to start a full sync
                • More logging messages throughout the app
                • Added shutdown message so that users are not confused when app shuts down on iCloud changes

                Changed

                • Downloads are now done one after another to avoid throttling from iCloud server
                • Wording of some dialogs

                Fixed

                • Some crashes that occured when a remote change modifies an item that is currently being edited
                • Some missing files did not download
                • Titles of assignable midi buttons are not cleared
                • Database is emptied when user disables iCloud for Stage Traxx in iOS settings while it is still enabled in the app
                • Autoplay broken at end of playlist

                Hi Peter
                First testing of new beta version went as follows - Crash log sent to you.

                1. Deleted all existing ST date from iCloud
                2. Updated iPad with latest beta version
                3. Set ipad to merge data (831) files to iCloud via Sync switch,
                4. Updated iPhone with latest beta version
                5. With sync still running on iPad I set iPhone to sync with iCloud
                6. iPhone sync started
                7. iPhone beta crashed. iPad sync still running with210 files to go

                It’s possible I had a storage problem with the iPhone - will clear out some large files and resume testing.

                Interesting. I do get an error from iCloud if you lack enough space on iCloud, but it ignores the space you have on your device and tries to download anyway. Guess I will need to add a failsafe for this case when downloading files.

                  peter since my last post I’ve rebooted my iphone and cleared some space. I’ve repeated the sync process which appears to be been successful - ie all files appear to have been downloaded and none are showing red. I will continue testing.

                  Good news I’ve now got 3 devices synced to iCloud without any missing files. So far all changes I’ve made to songs any one device are quickly reflected on the other two. Fingers cross you’ve cracked it - well done! Oh one thing I did notice is that user preferences are not synced across devices - presumably this is intentional. Is it possible these could be included if required?

                    Hi Peter have just been checking and find that there are many songs on all devices where the lyrics and chords etc have been lost in the sync process.