The latest updates seem to not be updating metadata properly.
Every time I sync back from MMA to MMW it increments the playcount on MMW
I know this is the case because I removed my entire library on my phone and re-synced. Played some tracks. Ran a sync and the play counts updated on MMW. Running sync again, MMA says it's syncing metadata and the playcount is incremented once more on MMW.
I am running MMW 4.1.25.1895 on Windows 10
MMA 1.3.5.0872 on a Samsung Galaxy S10+ running Android 9
Any ideas? This has been working flawlessly for a long time but looks like it's been broken with the recent build
Metadata keeps re-syncing
Moderator: Gurus
Re: Metadata keeps re-syncing
I can confirm that this is an issue with MMW 4.1.25.1895.
I reinstalled my previous version 4.1.24.1883 and I can now play a track, sync and it increments the playcount. Sync again and the playcount remains correct.
Please can you raise an issue for this
I reinstalled my previous version 4.1.24.1883 and I can now play a track, sync and it increments the playcount. Sync again and the playcount remains correct.
Please can you raise an issue for this
Re: Metadata keeps re-syncing
Hi, I have just tested this and cannot replicate your issue.
Also, I am not aware of any change in this area between 4.1.24 and 4.1.25
Are you sure that you have tested 4.1.24 and 4.1.25 on the same database?
If yes, then probably debug log will be needed (item 4b here: https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69 ) and accompanying MMA log ID.
Also, I am not aware of any change in this area between 4.1.24 and 4.1.25
Are you sure that you have tested 4.1.24 and 4.1.25 on the same database?
If yes, then probably debug log will be needed (item 4b here: https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69 ) and accompanying MMA log ID.
Re: Metadata keeps re-syncing
Thanks for looking at this.
I can run both versions on another Windows machine without issues. I think it might be down to the low-spec of the machine it was running on
I can run both versions on another Windows machine without issues. I think it might be down to the low-spec of the machine it was running on