by pbpb » Sat Jul 11, 2020 6:00 pm
Interim report. I did a dry run before tackling setting up debug logging. Since I failed to remember that you said "Setup a sync with just those five files
and also their duplicate filename versions", I created a playlist with only the offending tracks, but of course the duplicates were already on the device in the desired directory. The result was that it copied the 5 files, but NOT to the parent directory, but rather to the desired location. This implies that using the playlist hack is not going to be informative.
Next, ran a "normal" sync for all music from server to device, which includes the previously offending files. Now, it wants to delete the playlist and the 5 tracks. I said ok. The result: As best I can tell it did not actually delete the tracks that were in the correct place, and ALSO now it did not put those (or any other) tracks into the parent directory. This implies it will now be forever a mystery as to what the original problem was, since now I can't reproduce it.
My guess is that there was some small error in the database that got fixed by using the playlist to sync. Of course, that's a totally random guess, since I have no clue what the code looks like.
It occurs to me that I could try this again with *all* the duplicate versions in the playlist, and see if anything new happens. I did that and it said it downloaded the playlist, but nothing changed. I also then went back to syncing everything, and it said it deleted the playlist, but nothing changed.
However, I now note that at least one of the previous offending files now has a filename that is the same as the filename on the server, but which does not conform to the naming I specified in the device configuration, and I don't believe that was the case before, when one of the files was ending up in the parent dir. Since I had "enforce use of sync mask" set, and "delete unselected" also set, that as best I understand it, should not happen.
It seems that things are rather messed up, and I'm thinking that the best way to proceed is to just do a clean install of mma, and start from scratch, since currently things seem to be fubar. I am currently syncing the library from scratch after a clean install (including deleting all mma data on the device as per
http://www.mediamonkey.com/support/inde ... an-install ).
That takes many hours even with very fast wifi; will let you know what happens afterwards.
Interim report. I did a dry run before tackling setting up debug logging. Since I failed to remember that you said "Setup a sync with just those five files [i][b]and also their duplicate filename versions[/b][/i]", I created a playlist with only the offending tracks, but of course the duplicates were already on the device in the desired directory. The result was that it copied the 5 files, but NOT to the parent directory, but rather to the desired location. This implies that using the playlist hack is not going to be informative.
Next, ran a "normal" sync for all music from server to device, which includes the previously offending files. Now, it wants to delete the playlist and the 5 tracks. I said ok. The result: As best I can tell it did not actually delete the tracks that were in the correct place, and ALSO now it did not put those (or any other) tracks into the parent directory. This implies it will now be forever a mystery as to what the original problem was, since now I can't reproduce it.
My guess is that there was some small error in the database that got fixed by using the playlist to sync. Of course, that's a totally random guess, since I have no clue what the code looks like.
It occurs to me that I could try this again with *all* the duplicate versions in the playlist, and see if anything new happens. I did that and it said it downloaded the playlist, but nothing changed. I also then went back to syncing everything, and it said it deleted the playlist, but nothing changed.
However, I now note that at least one of the previous offending files now has a filename that is the same as the filename on the server, but which does not conform to the naming I specified in the device configuration, and I don't believe that was the case before, when one of the files was ending up in the parent dir. Since I had "enforce use of sync mask" set, and "delete unselected" also set, that as best I understand it, should not happen.
It seems that things are rather messed up, and I'm thinking that the best way to proceed is to just do a clean install of mma, and start from scratch, since currently things seem to be fubar. I am currently syncing the library from scratch after a clean install (including deleting all mma data on the device as per http://www.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/154/24/android-how-do-i-do-a-clean-install ).
That takes many hours even with very fast wifi; will let you know what happens afterwards.