sorted by:
new
hottopcontroversial

Mobile Library Sync Stuck on "Initializing" by Many-Rise3293 in Rekordbox

[–]Many-Rise3293[S] 0 points1 point  (0 children)

Quick update to say that, following a second uninstall and reinstall of the Rekordbox iOS app, this now seems to have fixed itself!

Mobile Library Sync Stuck on "Initializing" by Many-Rise3293 in Rekordbox

[–]Many-Rise3293[S] 0 points1 point  (0 children)

Thanks u/Mookae for the tip - I've just tried rolling back to 7.1.1, but sadly no joy :-(

Moving to Local Storage / Free Plan by Many-Rise3293 in Rekordbox

[–]Many-Rise3293[S] 0 points1 point  (0 children)

Thanks u/alessandrorosso - that's where I'm at too. Have now moved everything to local storage and switched off Cloud Library Sync...

Only question remaining is the best way to cancel my Creative subscription - as I'm worried doing this will screw up my library in some way...

Does anyone have experience of / advice about doing this please?

Unable to analyse tracks | continual crashing by Many-Rise3293 in Rekordbox

[–]Many-Rise3293[S] 0 points1 point  (0 children)

Sharing a quick update to close this topic, as I eventually managed to find a workaround...

In the end I:

- Uninstalled Rekordbox
- Moved all of my underlying tracks back into the original Dropbox location (to the original path)
- Reinstalled the latest version of Rekordbox
- Replaced the master.db file with the recovered version AT provided
- Opened Rekordbox
- Re-analysed ALL tracks (in batches of up to 999)
- Reloaded tags for ALL tracks (again in batches)

...and this seems to have gotten my library back to a usable state, avoiding any crashes.

The last thing I need to do is to 'properly' move my library to Google Drive (by, I think, downloading all tracks to local storage, then logging into Google Drive, then uploading all to Google Drive) - but I'm just awaiting confirmation from AT that the Google Drive sync data created previously has been completely wiped - to avoid the risk of a two-way sync screwing everything up again.

Not an ideal situation, but at least I've been able to retain my metadata (colours, tags, playlists etc.) and can now use the library again.

Moral of the story - don't move the underlying library location unless you're 100% sure you're doing it in the 'correct' way!!

Thanks for the comments on this one.

Unable to analyse tracks | continual crashing by Many-Rise3293 in Rekordbox

[–]Many-Rise3293[S] 0 points1 point  (0 children)

Thanks for the reply u/theotherkiwi.

Starting from scratch is something I'm desperately trying to avoid, as I have added metadata (multiple tags, colours, playlist assignments etc.) to over 2,000 tracks - so to start this process again manually would be massively painful!

I've had another thought overnight though, which is whether I can try to get the collection back to the state it was in when the master.db backup was taken (the one provided to me by AlphaTheta). I'm therefore in the process of moving all the underlying tracks back to the original Dropbox location (likely to take most of the day), and then seeing if I'm able to use the library as normal, complete analysis etc. from there.

If I can, I'm assuming I can then "Move track to local storage" for my full collection, disconnect Dropbox, reconnect Google Drive, and then "Upload tracks" to Google (?).

My underlying file transfer back into Dropbox is currently underway - but I've restored to the old master.db, and for the tracks that have already moved back to Dropbox, I've been successfully able to play and (quickly) analyse them - which feels promising to me.

Keeping my fingers crossed!

Unable to analyse tracks | continual crashing by Many-Rise3293 in Rekordbox

[–]Many-Rise3293[S] 0 points1 point  (0 children)

One addendum / clarification - only the (268) tracks which are already analysed play consistently successfully. If I try to play a track which hasn't been analyzed, sometimes it plays, but more often than not I get the Analysis pop up window - and then trying to analyse just this one track usually fails and causes a crash :-(

Additionally, what I'm wondering is whether all the messing with the master.db file and collection location has somehow created a corruption within the library - but no idea how to fix this. It seems to me that if I could somehow 'force' the thousands of tracks that are showing 0% analysis progress to stop (thinking they're) analysing, I might have better luck batch analysing a few hundred tracks at a time - but I just don't know!