View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007271 | MMW v4 | Other | public | 2011-01-31 11:09 | 2011-05-06 07:26 |
| Reporter | zvezdan | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | duplicate | ||
| Fixed in Version | 4.0 | ||||
| Summary | 0007271: Add/Rescan Tracks doesn't update existing tracks in database always | ||||
| Description | Tested 1294 and 1345, both have the same behavior. | ||||
| Steps To Reproduce | - Turn off Infer track properties option; - turn on Update Track info from Tags when rescanning files; - turn off Only for files with changed timestamp (only needed if Modify timestamp when updating tags is turned off); - find some track already added to the Library which have entered several tags, e.g. Artist, Album, Title...; - choose Clean ID3v1 and v2 Tags on that track; - look at that track in some another program, e.g. Winamp or just as binary file in Total Commander -> there is not any tag in it (as it should be); - choose Add/Rescan Tracks to the Library and choose folder with the same track -> none field is emptied, i.e. database still contains all old tags from that track. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1368 | ||||
|
|
Could you explain me how this issue is resolved and how is it a duplicate with your mentioned issue? I am not talking about changing tags in some another program like foobar, that are not detected or should not be detected into MM. I am talking about MediaMonkey and two of its options. I have used one MediaMonkey's option (Clean ID3v1 and v2 Tags) and I expect that another MM option (Add/Rescan Tracks) respect the modification made by that first option. |
|
|
It's the same issue, MM retains the information in the Database when it's missing from the tag, regardless of how it was removed. |
|
|
OK, you are right, this is the same issue. However, it is not resolved. The current implementation is ridiculous. If I turn on the "Update Track info from Tags when rescanning files" option, I expect just that - that track info are updated when rescanning files, as its name says. What is a purpose of that option if it has not effect? |
|
|
Reasons are given in the other ticket, such as the fact a piece of information may not be storable due to tagging standards for certain file types. As for it being resolved, it's because it's being resolved as a _duplicate_ (notice that it wasn't resolved as _fixed_). The issue is already tracked through 0001502. |
|
|
Yeah, that issue is reported 2004-07-23, which means that it would never be resolved. I am sorry, but you didn't give me an answer to my question. What is a purpose of the mentioned option if it has not any effect? |
|
|
Because it does work, when tags have been changed or added. The only case where it doesn't work is when they have been deleted or otherwise not present (which has been stated is to prevent potential loss of data). I can see some logic in the way it functions now (again, due to possible data loss due to tagging standards, or potential failure for tagging process to complete properly), however there are several (myself included) that expects the database to remove the data that's no longer in the tags. The ratings thing the previous ticket brings up is a good example of where this could trash things for some people however. Especially since one work flow for individuals to share the same media files between several users is to each have their own database, and disable the POPM frame for ID3 tags so that they can each store their own rating in the database and not have to fight over the rating frame in the tags (which could then overwrite their own ratings with someone elses). Sure, that bug entry may have been opened in 2004, but Rusty last commented on it in April of 2009, and the last activity on the bug was in August of 2010. Again, this is a duplicate because the issue already has a ticket. |
|
|
That option has a bug since it doesn't work in all cases. Its name is "Update Track info from Tags when rescanning files" and it should work always as its name says, not just when some condition is accomplished. If MM developers want some specific behavior in some specific situations, e.g. when tag is empty, they should add one new sub-option to cover such situations, e.g. "Don't clear Track info if Tag is empty". We are not talking only about Rating, there are many other tags which are affected. We are talking about MP3 format that I am using, which supports all tags represented in database. If you don't want to clear Rating, there is no excuse not to clear Artist, Title, Album since all that fields exists in ID3 format... By the way, I don't know how to take your comment about Rusty's comment from 2009 - it is joke or what? What activity you are talking - there is no activity with that issue. We could just forget about it like with many other issues posted several years ago. |
|
|
http://www.ventismedia.com/mantis/view.php?id=1502#c17579 "(0017579) rusty (administrator) 2009-04-24 12:39 edited on: 2009-05-05 16:14" and "Last Update: 2010-08-02 16:43" |
|
|
Yeah, I saw that issue already, but I cannot call that "activity". "Following discussion with Petr, we decided to defer." - just comment, nothing more, almost two years ago. Assigning some another issue to it I cannot call as "activity" either. |
|
|
Tagging as fixed--Jiri's fix to issue 0001502 should have resolved this problem. |
|
|
Verified with 1368. Thanks! |
