Yes, unfortunately, it gets fixed during first sync after MMW update only. But you had the 598 build that wasn't correct :(. I am sorry. It is really fixed in 599.

So please go to Options->Check for new/changed media and start wifi sync to resync with MMW. It will redownload all the rest of the tracks. But it will be ok after this sync. Thanks

MCow,
Just before you send LOG make Screenshot from phone (POWER+VOLUME DOWN) and you will have LOGID for sure.

I retested this on 5 devices and had no issues at all with 599.

No, it did not.

I just tried to send logs, twice. The first time, I did not have the "save bug number" set, so I didn't get the full number, but it began with SMANY.
The second time, I tried to send again and set the "save bug number." I got the list of items where I could save it. I selected Google Keep. Nothing happened... and then "Unfortunately, Mediamonkey has stopped". Apparently you can't open Google Keep to save logs. GREAT JOB, GUYS! REALLY INSTILLS THE CONFIDENZ.

<profanity-laden rant elided>

Build 599 containing the fix has been uploaded. It should appear in the Google Play store shortly.

Let us know if it does the trick for you. Thanks!

-Rusty

I have found the cause. Please update to new build of MMA. It will be available soon.

Hi mcow,

Before you wipe the DB, could you generate logs again using the latest builds?

Thanks.

-Rusty

Thanks for investigating that further.

There's a comment at that bug that shows "MMA" having been fixed as well, presumably to implement the one-off hash recalculation and prevent additional re-downloads.

If that was the intent, it did not work for me. MMW 1798 and MMA 598, still re-downloaded the last 16 tracks I'd played on MMA -- everything since the log files I supplied earlier.

But maybe I should just wipe the database and resync everything before saying it's not fixed?

Hi, thank you for the logs.

We investigated the issue and there was really a bug in this area, these are the symptomps.
More details here: http://www.ventismedia.com/mantis/view.php?id=13305

First try, got the symptom.

MMW log: https://drive.google.com/file/d/0B753nU0Ll2heZXVkZ3FFZUxUNW8/view?usp=sharing
MMA log: nhkl6sk6dz

Hi Mcow,

Could you do a small sync operation for which this occurs and:
- send me a link MMW debug log generated with dbgview?
- post an MMA debug log ID after the sync operation

I know that you did so in the past, but it would be helpful with the latest MMW/MMA builds.

Thanks.

-Rusty

I'm bringing this up again.

I have a new Android device, a Nexus 5X. I've installed MMA and sync'd two playlists, each full of albums: one smart (items new in past six months), one fixed.
I set up my conversion rules to have one rule: if FLAC, convert to MP3 192kbps (the standard/fast conversion option). I have not changed this rule since setting it up, two weeks ago.
Today I sync'd for the first time in a couple days. A FLAC album that I played yesterday reconverted and redownloaded.

[quote="Ludek"]I wonder whether it could be a device profile swap that could happen in the past or something like this? Do you see more device profiles for the same device in Options -> Portable device sync ?[/quote]
No. Was not the case for the tablet, is not the case the for the new phone.

[quote="Ludek"]In any case the tracks are re-downloaded only if the auto-convert rules are changed or the file is updated somehow (as Peke confirmed by his tests).[/quote]
Yes, the file was updated somehow: it had been played, and the last-played date and play count changed. But only that.

This problem not only continues, it has gotten worse. There is definitely no change being made to the auto-convert settings.

Hi,
your MMA logs indicated that the reason was changed auto-convert state .
I wonder how you could get to the state that auto-convert rules for those tracks changed without your manual changing of the rules.

I wonder whether it could be a device profile swap that could happen in the past or something like this? Do you see more device profiles for the same device in Options -> Portable device sync ?

In any case the tracks are re-downloaded only if the auto-convert rules are changed or the file is updated somehow (as Peke confirmed by his tests).

Thanks for looking into it.

I haven't changed auto-convert rules in, probably, over a year; since whenever I last needed to reset the device profile in MMW. I have always been set up to copy MP3s and to convert FLACs. I don't think I've done a rescan, but if I had, wouldn't it have caused [i]all[/i] the old tracks to refresh, rather than only after they've been played?

I recall seeing a message about a database udpate with the first run of some version in the 1.1.3 development, and I'm guessing tracks that were already on the device at the time of the change become marked as stale once they get played (updating file info). I suppose I could just delete all the music files and resync to overcome this, but just letting the old files refresh as they get updated wastes less time. It'll only be a problem if the same files keep re-syncing.

I've just done tests and I can confirm bhiefer findings with one more addition.

MMW always initiate Re-download in these cases:
1. New Auto-Covert rule is applied.
2. File Info gets updated and MMW consider file as new which happen if file gets updated outside MMW and MMW monitor folder or you Re-Scan folder for updated Metadata so that FileModified or FileSize gets changed which set FileModified in MMW library.

To conclude test, this behavior looks like as designed and correct at least based on MMW 1783 and MMA 539.

@mcow: If you find MMW/MMA sync works differently for you please inform and we will retest.