feline1 wrote: βFri Sep 30, 2022 12:18 pm
Yet again, after a couple of months of behaving itself, I had an error message in MediaMonkey about a json lock file (? it left the screen before I could screenshot it), and now I am back in that state where I have a 1TB microSD card half full of music,
but MediaMonkey no longer recognises it as being a copy of my library (which is on my PC).
And it looks like the only workaround is gonna be to re-format the microSD card and spend several days trying to resync the entirely half a terabyte library all over again.
I'm strongly suspecting there's some kind of cache file that MediaMonkey is using to refer to my SDcard, that has gotten messed up. And if I could reset that, would return to happily resyncing my library again without me needing to wipe the card and start from scratch....? No?
I hesitate to contradict Peke, because knows more that I do, but ..
I am not sure that your problem is coming from the json file that he mentioned.
I have looked into that file a few times .. It is long long boring read, but I didn't notice anything in there that is controlling sync state at the target end.
The cache that you have been asking about should be at the target end.
I have never sync'd to s SD disk, but you should find it in the MediaMonkey directory on the card, or the device which is hosting your card..
example; when I sync to my android phone (no SD card), the cache is at \Internal shared storage\MediaMonkey\files in the mmstore.db file with most current date. But you shouldn't mess with that.
Instead,
go here and familarise yourself with locations on your device|SD card that MM is able to delete things from
Then go here, and do a empty "sync" with the delete, and CONFIRMATION option set as shown.
That should show you which files MM5 has forgotten that it transferred.
Read the list carefully before allowing it delete anything.
The only thing that I know to do, is allow MM to delete them, and then try again. ... And hope this time you don't get a crash .. which is what probably caused this "forgetting".
But the other things to say is this
- you really are making a large job so much harder trying to do it at USB 2 speed .. USB3 is much better ... and WiFi is probably better too ... try it with a limited file set ... very long run times, at slow speed, just opens the door for issues to happen, IMO
- but the real problem is that you are trying to do an industrial sized job with a toy IMO
I have come to the opinion that MM sync is just a toy tool for little jobs .. like you I saw MM sync and had big plans ... I had a large empty phone, and a couple of tb of empty space at Dropbox ... so I tried MM5 to transcode and sync my large collection to .mp3 at these locations ... it is just not up to the job ... it easy to get started, but it all falls over in a heap when you try something big, or go back and try to refresh what you have done.
And when it does fall in a heap you have got a start-all-over-again mess to contend with.
And think about this thread. It took you 10 tries, and lots of patience, to get just one on-topic response, from the paid "support" guys, to your main issue.
And, from what I understand (guess?), that response is at least suspect.
I have
this issue being tracked since February this year.
As you can see, it is not getting much love.
Also I spent a lot of frustrating hours trying to get it sorted in a Support Ticket.
There are so much higher priority issues there at the moment ... so I have abandoned MM Sync for the moment.