1183 Failure of Auto-sync to detect tag changes

[chrisjj]

If I:

1 Edit some Album and Title file tags in Mp3tag
2 In MM do Add/Rescan to update MM's DB - and verify in the tracklist
3 In MM do Auto-sync to carry the updates to the tracks already on the device
4 Look on the device for the updates

then the updates do not reach the device. If I manual sync, they do. It looks like Auto-sync is failing to notice tags updates!!!
EDIT: Further info: the same failure occurs if instead of Step #1 and #2, I make a tag edit directly in the MM tracklist.

This bug has been present for at least one year.

Anyone know a workaround in Auto-sync?

Ayone know how MM detects changes for it's auto-sync? Because if it is something mickey-mouse like checking only file size, this is probably where I give up try to get MM to work properly for device sync.

Thanks.

[nohitter151]

Ayone know how MM detects changes for it's auto-sync? Because if it is something mickey-mouse like checking only file size, this is probably where I give up try to get MM to work properly for device sync.

Thanks.

It checks Timestamp. See Tools | Options | Library and Tools | Options | Tags & Playlists.

[chrisjj]

> It checks Timestamp.

Add/Rescan sure, but Auto-sync???

> See Tools | Options | Library and Tools | Options | Tags & Playlists.

I am sure that's for Add/Rescan not Auto-sync.

[nohitter151]

> It checks Timestamp.

Add/Rescan sure, but Auto-sync???

> See Tools | Options | Library and Tools | Options | Tags & Playlists.

I am sure that's for Add/Rescan not Auto-sync.

I know that, I meant to check those options to make sure that you're timestamps were updating.

EDIT: Proof here

[chrisjj]

> I meant to check those options to make sure that you're timestamps were updating.

I see no option there that relates to this external tag edits - I see only "[X] Modify timestamp when updating tags" which relates to MM tag edits.

> EDIT: Proof here

"MediaMonkey auto-synchs tracks whenever the track's current timestamp is more recent than the time that the track was last synchronized."

Well, not here. Explorer shows Step #1 is setting the timestamp more recent than the last auto-sync. Yet still MM's next auto-sync fails.

Any other ideas?

[nohitter151]

Any other ideas?

What does the Timestamp field in MediaMonkey show?

[chrisjj]

What does the Timestamp field in MediaMonkey show?

2008-10-11 16:44 (from the tracklist - strange this field is missing from Properties). And an auto-sync at 2008-10-13 02:15 failed to sync this update.

One explanation could be "the time the track was last synchronised" is misrecorded. Any idea where I can find this?

EDIT: Not stored in the device suggests WMLog output e.g.:

Code: Select all

            1.MP3
              WMDM/Bitrate = 0
              WMDM/Author = From Camille Saint Saens
              WMDM/AudioBitDepth = 0
              WMDM/AudioWAVECodec = 0
              WMDM/FormatCode = 12297
              WMDM/Duration
              WMDM/Title = C-0 Aquarium, from Carnival Of The Animals curtain
              WMDM/UserRating = 0
              WMDM/PersistentUniqueID = {00027DCC-0000-0000-0000-000000000000}
              WMDM/SampleRate = 0
              WMDM/Genre = Curtain
              WMDM/BuyNow
              WMDM/FileSize
              WMDM/Track = 1
              WMDM/AlbumTitle = ~C Aquarium, from Carnival Of The Animals curtain
              WMDM/FileName = 1.MP3
              WMDM/NumChannels = 0
              WMDM/NonConsumable
              WMDM/PlayCount = 0
              WPD/PassthroughPropertyValues (1193)
              Attrib: 48020

so one has got to wonder where MM /does/ store it .

[chrisjj]

> One explanation could be "the time the track was last synchronised" is misrecorded. Any idea where I can find this?

In the DB, suggests this debug log:

Code: Select all

[3876] 3628 DB prepare SQL: INSERT OR REPLACE INTO DeviceTracks (IDDevice,IDTrack,DevicePath,Rating,PlayCount,UploadTime,Converted,PreModified,Status) VALUES (?,?,?,?,?,?,?,?,1)

(I assume the ? is a false report, since it shows on tracks that don't suffer from sync failure.)

Note: On this debug version, five of the six auto-sync's I tried failed - one doing a spurious 170-track transfer which I had to let complete to avoid the playlist loss I see on termination. I've reverting to the non-debug version!

So, time to root in MM.DB, I guess. Can anyone suggest the best viewer tool?

[Mizery_Made]

Shortly before my other computer bit the dust, I started using SQLite Spy, and it was a nice little tool. Free too, so you might look into it.

[chrisjj]

Coo... nifty! Many thanks.

Can anyone tell me how to convert MM DB numeric dates into readable e.g. ISO format?

[nynaevelan]

You could also try Bex's SQL Viewer script to run sql queries within MM or Bex's Debug Helper script, it gives alot of information relating to the track.

Nyn

[chrisjj]

> Bex's Debug Helper script,

That looks the one - thanks.

[chrisjj]

> EDIT: Further info: the same failure occurs if instead of Step #1 and #2, I make a tag edit directly in the MM tracklist.

Note, on 1256 and an MSC device (a HD SUBST) this failure does not accur.

[chrisjj]

> the same failure occurs if instead of Step #1 and #2, I make a tag edit directly in the MM tracklist.

EDIT: On an MSC device (SUBST drive) on 1256, the issue does not show in either the Add/Rescan case or the direct edit case.

[gblum]

Just want to chime in here and indicate that I'm experiencing the same problem. I update the tag in MM and re-sync, but device does not get new version of file.