View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015958 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2019-09-19 14:11 | 2019-09-23 21:18 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0015958: Auto-tag: many auto-tagged tracks are saved with tags that don't match the DB | ||||
| Description | It seems that having auto-tagged large numbers of tracks in my collection, in many cases auto-tagging saved one set of Genre tags to the DB and a different set to the tag (evidenced by their appearance in files to edit > out-of-date tags ) ! I haven't yet determined the cause of this with certainty, but seems that it might be related to auto-tagging not saving 'disabled' tags (i.e. tags that don't exist elsewhere in the DB) to the tag (exactly as specced), but then saving those 'disabled' tags to the DB (not expected!). | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 2201 | ||||
|
|
I don't think it was caused by auto-tag functionality. Most probably it was caused by any freeze/crash (maybe after auto-tag?). Also check Options - Library - Tags&Playlists - Update tags when editing properties. |
|
|
I'm able to replicate this with many tracks. I shared a sample track 'Heart Attack' by Demi Lovato . |
|
|
Here's a video that better illustrates the problem (along with a debug log): https://www.screencast.com/t/V8C0IUIyCfWh |
|
|
As discussed offline, the comparison failed on genre "Pop;Pop/rock" (database) <> "Pop/Pop/rock" (tag) ID3v2 tag uses '/' as multiple-value separator (according to spec) -- so in the file tag it is considered as 3 genres ("Pop/Pop/rock" -> 'Pop', 'Pop', 'rock') database uses ';' as mutliple-value separator so it is considered as 2 genres ("Pop;Pop/rock" -> 'Pop', 'Pop/rock') Solution: Before auto-tagging use this conversion: "Pop;Pop/rock" => "Pop;rock" |
|
|
But what I still don't understand is that if after the auto-tag operation I select the 'Heart Attack' open Properties, edit Disc # to '1' and save it; then when I navigate to Out-of-date tags, the track no longer appears (even though it still contains Genres: Pop; Pop/rock)! i.e. if it's a tagging issue then the issue should also occur via the Properties dialog. |
|
|
Fixed |
|
|
Verified in 2200. i.e. now a recommendation of "Pop;Pop/rock" is saved as Pop; rock But I still don't understand why we're taking this approach. i.e. as I asked at 0015958:0054731, I _can_ enter a set of tags in Properties where Genre =Pop;Pop/rock and the tag is saved correctly (i.e. no mismatch between tag and DB). So if that works, then why can't Auto-tag save tags in the same manner as Properties ? |
|
|
Fixed |
|
|
Verified 2201. |
