We have decided to release yet another release candidate for Picard 3 after we got more fixes and small improvements.
Thanks to everyone who tested and provided feedback. And special thanks to all the translators.
6 Likes
I normally use Picard for the initial MB metadata pull and foobar for everything else, so when I used foobar’s inline editing syntax in Picard it wasn’t immediately obvious what was wrong.
In an attempt to add a second artist to the artists tag I double clicked and appended “; AN Other”, which in foobar results in a second field but in Picard results in a concatenation.
In the attached image artists is a single field whereas artistsortorder is multi-valued. Could we somehow differentiate between the two? One option is to highlight the addition of the multi-valued separator (; ) in orange when it’s been used in a single field, though this could result in false positives.
Righ click and choose “Edit…”, then you can add multiple values. Not sure about the coloring, we already use coloring to show differences.
1 Like
Thanks @outsidecontext but I’ve worked out how to add multiple values in Picard, my request was to extend the highlighting so it differentiates between valid (multi-value) and invalid (delimited) data.
I notice that the application icon for mac is different whether the app is open or closed.
Is this by design, or a bug to be fixed?
App closed icon has a white background.
App open icon has a transparent background.
Can you share a screenshot and the macOS version you are running? That sounds like maybe macOS now supports multiple icons for closed / opened, but Picard does not provide this.
Two things I’ve noticed. If I open the settings and click Metadata, the section becomes greyed-out, the panel will still be visible though any changes won’t stick once I’ve made it so. If the section is greyed-out, once I click to another section, e.g. General, I cannot select Metadata or any of its subsections. If I open the settings and click one of Metadata’s subsections, the Metadata subsection does not become disabled.
And the other thing is: if I’ve loaded a release in to tag, once it’s been recognised and is over in the right panel, with files matched, I can click the release title, i.e. the line with the rollout arrow on the left, and see the releases general metadata in the metadata panel, but if I select an individual track, the metadata panel is completely empty, with no information about the track from the release, or the file that’s been matched, and no title column for the metadata fields.
Do you start from scratch or from an older config file?
That was going from a 2.13.3 config. Backing that up, and starting from zero solves both issues.
Can you share your 2.13.3 config (you can mail it at zas@metabrainz.org)? I’ll have a look, this shouldn’t happen.
1 Like
Ok thanks, it is sent!
Thanks, I found the Options > Metadata issue (tracked by PICARD-3464) and the fix was merged. It isn’t strictly related to your config, that’s a nasty issue with internal option management.
About the second issue I still need to investigate.
3 Likes
About this issue, it is due to missing $album_all / $album_max in a script you have in the Picard 2 config, probably provided by a plugin (from Determining whether condition applies to multiple files - #5 by outsidecontext) which isn’t available (yet) on Picard 3, but it reveals a robustness issue: it should not prevent display of the metadata box.
I have a fix for the robustness issue, but not for the script or plugin.
Related to: Determining whether condition applies to multiple files - #13 by outsidecontext
3 Likes