We have released a third release candidate for Picard 3. We got good feedback for the previous one and did quite some testing ourselves. The RC 3 addresses all the found issues and even has some feature improvement.
I just installed RC2 today. You are too fast ![]()
I’ve just spotted a couple more niggles with Picard rc3 on Windows.
-
Restore all Defaults doesn’t remove file naming scripts so importing a profile can result in duplicate entries.
-
Inserting/Pasting a line of text triggers a font change in File naming script editor and Tagger Script(s)
Steps to reproduce
- Options > File naming scripts > Edit scripts
- Copy some text
- Position the cursor at the end of the last line of the script > Enter > Enter (only happens when leaving a blank line before pasting)
- Paste
The new font applies for the rest of the session
- (album)artist sort tags
Not really a bug (more like a fix) but a change in behaviour. In v2 the native multi-valued (album)artistsort tags (%_albumartists_sort% and %_artists_sort%) were always standardised, but in v3 it’s no longer possible to natively tag:
(ALBUM)ARTIST = as credited
(ALBUM)ARTISTS = as credited
(ALBUM)ARTISTSORT = standardised
I can get the standardised sort tag using the ‘Additional Artists Variables’ plugin so I have no problem with the change, however, is there an expectation that users can seamlessly upgrade between versions?
I actually don’t think it should. File naming scripts are rather complex and intentionally managed in the script editor dialog. There also can be multiple. The option dialog should reset what is being managed there.
Rather the profile import should deal with the case.
Yes, Picard 3 now tries to find a sort name matching the credited name from aliases. As artist credits don’t have a sort name it previously simply fell back using the artist sort name, which meant in some cases name and sort name didn’t match.
They’re usually not as complex as tagger scripts so I’m not sure that’s relevant.
I agree that having their management outside of the options dialogue does muddy the waters somewhat, but aren’t they most likely dependent upon tagger scripts, I know mine are.
Yes, I confirm the issue, thanks for reporting. I created https://tickets.metabrainz.org/browse/PICARD-3439