I have an issue where Picard sets the front cover position randomly. What i want is the front cover set in position nr. 1. This is how it looks like in mp3tag:
As you can see. One of two medium covers are set in position 1. The rest are back cover, medium and lastly the front cover in 4/4.
I was hoping to make a script that sets front as nr.1.
I checked the script documentation and could not find any info about cover tags.
Is this posible at all in Picard?
It’s not possible to change the order of the images in the file. But we pretty much would like to have the front cover always be the first image by default.
Currently this does not work because mutagen, the library Picard uses to access the file tags, always orders all the tags by data size, with smallest size first, to work around some issues with tag reading in some software. That means embedded images usually end up last, with smallest image first.
Please see the following tickets for details:
01:38PM - 19 Dec 19 UTC
The ID3 classes store frames sorted by some frame ID priority, then frame size a
… nd hash.
This causes some issues when storing APIC frames of different type. The user might expect certain image types, such as "Leaflet page" to be saved in a certain order. Further more images of type "Cover (front)" might be expedted first. In regards to sorting images of different types sorting them by data length does not make too much sense.
For the second issue I found actually a concrete example: Previews in the Nautilus file browser seem to always use the first APIC frame no matter the type. So files don't necessarily get shown with their actual cover but just with the smalles APIC frame.
At a minimum I propose to change the sorting to:
- Keep same frame IDs together
- For APIC frames, sort type 3 "Cover (front)" first
But I think it might be even better to generally leave APIC frames in the order they were provided. @lazka Thoughts?