View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018478 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2021-10-27 15:28 | 2021-11-06 18:29 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0.2 | ||||
| Target Version | 5.0.2 | Fixed in Version | 5.0.2 | ||
| Summary | 0018478: Auto-tag: album art fails to save for some tracks | ||||
| Description | By default, MM is configured to save artwork to tags, if possible, however, when auto-tagging certain tracks, MM looks up the artwork but doesn't save it to the tag (it's saved as 'unsaved image'). e.g. 1 Scan track 'again & again' 2 In Locations > Path [List], select the track and initiate Auto-tag --> AA is looked up, but the artwork flashes several times (this doesn't occur with other tracks)! 3 Click Tag & Continue to save the changes 4 Click Properties > Artwork --> The artwork displays (it's a 640x640 196KB image) but the status is 'Unsaved image'! 5 Click the 'Save' button --> Artwork saves to the tag as expected (as subsequently verified) Note: if I attempt to lookup and save artwork manually, it saves to the tag as expected. The problem only occurs with Auto-tag! | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2516 | ||||
|
|
Fixed |
|
|
There's something strange going on here. Now when the track is tagged, it's impossible to remove the artwork from Properties > Artwork! i.e. clicking the 'garbage can' icon has no effect! This is really strange because it only occurs with some tracks (e.g. it'll occur for some m4a files but not others)?! |
|
|
Can you analyze it more? For me and Petr it works, tried several files of several formats, artworks in tag and in folder, and they are removed as they should. Is it related only to some specific files or some exact steps? Do you reproduce it with another installation of MM5 and same files? |
|
|
Fixed in build 2516. Problem was related to covers of newly scanned files, for such files editing of covers was buggy. |
|
|
Verified 2516 Inable to reproduce anymore |
