View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015032 | MMW 5 | Sync | public | 2018-08-10 23:34 | 2022-09-14 14:39 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 5.0 | ||||
| Target Version | 5.2 | ||||
| Summary | 0015032: MM5 - MMS metadata sync issues | ||||
| Description | 1) In cases where a user wants to migrate from an MMW-based library to one based on MMS, there is currently no way to do so unless the user is willing to live with tracks that are missing tags. For example: a) in the case of a family with UserA, UserB, UserC, where userA is running MM5 and MMS (i.e. content is stored to that user's machine), when userB or userC update metadata for content shared from MMS to MM5, MMS doesn't tag the tracks. Only when user A edits the content will the tags be updated (or at least they should be) b) in the case of a family with userA, UserB, UserC where MMS is running on a different machine, any edits by any of the users won't result in tags getting updated. 2) When users update metadata, some fields don't update in the MMS database. I only tested the fields on the first tab of the properties panel thus far, but of those, the following failed to update: Disc#, Conductor, Lyricist 3) When MMS reads tracks tagged by MM5 (during the scanning process), it sometimes fails to read the Rating tag. Sample tracks saved to ftp. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
1) There isn't a full short term solution to this. We plan to achieve server tagging by some LAN connected MM5 instance, that can tag batches of tracks that need it, either on request or automatically. Ludek will look into it. 2&3) Assigning to Ludek to review. |
|
|
1) As short term solution (until MMS has own tagger) the local MM5 instance (on LAN) could download the track, tag it and upload to MMS again. I would just probably add a checkbox for this (disabled by default), namely maybe two checkboxes like this: [ ] Update file tag on server (aside from updating the metadata into database it also modifies file tag remotely, consumes bandwidth though as it needs to download/re-upload the file ) -- [ ] Update only on LAN 2) fixed in upcoming MM5/MMS builds (together with lyrics and date field issues), i.e. MM5 5.0.0.2121+ and MMS 0.0.6+ 3) Couldn't this be a test error? I copied both the tracks to a new folder, in the MMS's web UI added the folder to scan and accessed it via UPnP, in both MM4&MM5 the correct rating is shown: https://www.dropbox.com/s/zr7dgidmicp23d2/Screenshot%202018-08-28%2012.21.55.png?dl=0 I also verified on MMS side that the rating value(s) have been read correctly from the file tag. I've just found that ISRC and 'Initial Key' aren't read from ID3 tag => fixed in MMS 0.0.6+ |
|
|
1) I'm not sure that it's worth implementing the 'download and tag' hack--it really depends on how much work it is to implement tagging in MMS (i.e. how long before that feature is implemented) since I'd expect that implementing this in MMW might be a lot of work. e.g. if the user makes a bunch of tag edits to cached tracks in MMW, then it would have to have the logic to automatically tag those files when it connects to the server, and it could be difficult to do this in a way that wouldn't cause confusion for the user (since it would result in high CPU/network utilization even though no tracks are being transferred). There are probably several other usecases that would need to be supported for tag updates to occur transparently on the server side. In other words, I don't think it's a great idea to spend a lot of time on a throwaway solution if it's going to take a lot of time. But if it really does make sense, then the UI could be: [ ] Update file tags on the server (uses extra bandwidth) {"In addition to updating the database for metadata changes, MediaMonkey will modify the file's tag. This will consume bandwidth as it needs to download/re-upload the file."} -- [ ] Update only on LAN {"Tags will be updated only if the server is local or on a local network"} |
|
|
I don't think that MMS tagging (writing of tags, to be exact) will match MM5 features any time soon. For that reason, I think that this feature make sense to be implemented, and probably won't be too complicated. Technically, I suppose that MMS will keep a list of modified tracks (by latest update date), either by MMA or MM5, and so any MM5 instance will be able to perform proper tagging. Since it will be done synchronously, i.e. track by track, I don't think that it'd cause any significant slowdowns. To be sure, we possibly can even throttle it down by some pause between tagging of each track. Assigning to Ludek to look into it, time permitting. |
