#musicbrainz

I mean, you're probably right tho

iirc tags with 'year' and 'date' usually refer to the same thing, but the year version just has the other parts of the date removed

yes

(this is needed for compat with some players)

ah. i've always wodnred why both.. compat. cool

KassOtsimine: the first release date per recording is available via the %__recording_firstreleasedate% variable

:o

ok so if i want that to go into the "date" tag...?

(but only for VA)

and VA are ones i put as "compilation" =1"

then you'd need to write some tagger script. Inside an $if statement (match on e.g. compilation rg type?) you could use the $set function to set a tag.

...

so something like $if($eq(%compilation%,1),$set(original_year,%__recording_firstreleasedate%)

where you can change 'original_year' to be whatever tag name you want to put it in

and i forgot to add the last closing )

But remember that will change the value of original_year only for that track. There is currently no way to apply the change to all tracks on the release.

well, for recording dates it makes sense to do it per recording :)

Yup.

hmm

ok so my use case is thus: for releases with "one artist" (not compilation) i will want it it named as $artistname - $releasename/$tracknumber $tracktitle.tld with the date as whatever mb has for that loaded release (or whatever i override it in but that's irrelevant to a naming script iiuc.)

but for things that are compilation =1 I want

$release title/$tracknumber $tracktitle - $track artist.tld

+ that tagging with original recording date

is it possible to acomplish both these?

so far i am going itno options whenever i have a va release and jsut moving parens around using noop

which works, but is uneligant

(i also have the problem that with releases with more thna one disc i want $discnum-$tracknum) but i laso *don't* want to save that i nthe tags, i only want it for names. but in order to be able to tag for it, i must leave discnum intact and manually remove this tag

yeah, that's all possible

my current tagging script is

$noop()%artist% - %album%/

$if($gt(%totaldiscs%,1), $num(%discnumber%,1)-)$num(%tracknumber%, 2) %title%$noop( - %artist%)

this is file naming pattern, not tagging script

ack i don't know the diff, sorry

but yeah, you can wrap that all in an $if that checks the compilation tag value and picks between the different formats

ah i have a lot of $unset as a taggerscript

like $unset(totaltracks) (I'd liek to use it for totaldiscs too, but i can''t that becasue thne the $discnum has nothing to work with)

it's all just $if($eq(%compilation%,1),<put compilation naming pattern here>,<put non-compilation naming pattern here>)

compilatio is what's set as being comp=1 thoguh, not from mb

(unless it's got that fro mmb)

but if i set something as comp=1

the %% syntax refers to whatever you have set in variables/tags

.. right.. one problem is that i have "$unset(compilation)"

so, what's the condition you want to use to choose between the two patterns, then?

because that some thinggs from mb are comp but i wouldn't use it.. maybe i should remove that

you have to figure out a way to describe this condition that a computer can understand and can be determined from information in picard :)

the condition is.. things where the tag is thre in the file i load or that I set it myself

yea

I suggest changing your tagging script to ```$set(_compilation,%compilation%)$unset(compilation)``` and then test the value of %_compilation% in your naming script.

In current versions of picard, the file naming pattern can use tags loaded from a file or set manually (as long as you don't $unset() them of course)

(I prefer not to set things manually, of course, my file naming pattern is all automated so i don't forget something)

heh

i liek setting things manually so things aren't autmatically something i didn't wnated :D

for instance , a disngle artist comp i would not want this naming thing

picard has a bunch of tags and hidden variables that provide enough info to figure that sort of thing out, if you're up to programming it.

the "compilation" tag is specifically only set on "Various Artist" albums, not multi-artist or single-artist compilations, fwiw

alright

so if i make a new taggerscript with thaat kepstin suggestion, shoudl it be before or after the other one with all the unsets?

are you talking about the tagger script or the file naming pattern?

yes

taggerscript

inside the tagger script, order of operations matters - you can't use %compilation% after you unset it for example :)

hm. it doesnt seem to work.. (set this new kepstin thing before the other one)

That's why I suggested copying %compilation% to %_compilation%, unset %compilation%, and use %_compilation% in your file naming script test.

i pasted that to the unset taggerscrip. i'm not using dates for renaming

hmm, "__recording_firstreleasedate" isn't in the picard docs, where did you see that?

is there maybe a plugin that generates that?

oh, hmm, musicbrainz blog says added in 2.6

oh shi. i have 2.1

i have to update it

Tags starting with an underscore will not be written to the files.

i wish the variables weren't split up on multiple pages in the docs, it makes it hard to find things

i miss the big old list of everything on one page :(

kepstin, see https://picard-docs.musicbrainz.org/en/variable...

oh, it should be %_recording_firstreleasedate%

$if($eq(%compilation%,1),$set(original_year,%_recording_firstreleasedate%))

will make a tag named "original_year", you can change that name if you want.

probably should be "originaldate" instead

i want it in the Date" field tho

i figured out how to do that, change it to "date" isntead of "originalyear"

but sicne it was only added in 2.6 it just blanks it.. wich is fine for now

lemme see what he updated picard will say

The problem is that %date% is on the release, not the track / recording.

but

outsidecontext> KassOtsimine: the first release date per recording is available via the %__recording_firstreleasedate% variable

where are scripts and picard settings stored?

Should be just one leading underscore (not two).

yes

i want to have more thna one version of picard installed (for reasons.) but i want to copy the settings etc to the new installement

where picard settings are stored depends on the operating system

i has windows 7

note that current versions of picard support option profiles, that let you switch between different settings within one version of picard

yea i know

i havent played with that (yet)

i haven't yet either, heh. looks pretty complicated.

If you're wanting to install another version for testing or whatever, I suggest installing the portable version (which saves the config file in a subdirectory of where the program is executed). That allows you to make changes to the config without affecting your "main" installed version.

kepstin, it's actually pretty straightforward once you get used to the idea of settings stacks.

The next version of Picard (rc1 being released next week) will actually also allow you to backup your config file and restore from a backup. That will allow you another way of changing configurations.

I might not actually need it, heh, the only thing i really change back and forth is the file naming pattern and there's a separate thing for that

Yeah, the only thing that I haven't found a way to automate yet is changing my file naming script for releases tagged in Classical format (with composers as the track artists).

ah! in taggerscript. is there a way to make it always replace some glyp by another glyp?

like i want hypen-minus isntead of hyphen

and jsut regular ' isntead of.. a thing i have to copy paste to find

there's a plugin to do that, specifically

i forget what it's called, 'ascii punctuation' or something like that?

oh, it's not a plugin, it's just an option in the Metadata section, "Convert Unicode punctuation characters to ASCII"

(there's also a "Non-ASCII Equivalents" plugin which tries to do a bit fancier of a job if the built-in method doesn't do what you want)

i think that plugin also might remove accents, so that's probably not very good for non-english stuff

(you could edit the plugin to replace whatever sets of characters you like tho)

Metadata section, "Convert Unicode punctuation characters to ASCII" <<-- yea I don't want that, because it coverst things like fullwith characters or whatever too, i only want those two tings

i can't really edit plugins because I can't code at all. all these taggerscripts seem like hoodoo to me :(

and idunno what the ascii-fyer will do with æøå

and I don't mine emdash

and I don't mind emdash

or unicode fuckery

or ffing zalgo, it's those damn hyphen and uuhh right single quotationmark used instead of apostrophe or even modifyer letter apostophe

ʼ which atleast makes *sense* somewhat and doesn't also look like an acute ´

doesnʼt

doesn’t

doesn't

beets uses https://pypi.org/project/Unidecode/

CatQuest, you can probably do what you want by using the $replace() function like $set(title,$replace(%title%,-,-))

a taggerscript right?

also i want it for title and releasetitle and artist name too

and for the apostrophes, it's a second line of $set(title,$replace(%title%,',’)) like right?

derwin: yea

>>> unidecode('kožušček')

'kozuscek'

that's exactly what I *don't* want :)

jesus2099: you had a windows tool that was an extended charmap sort of program exe, do you remember that? i'd like to get a hold of that again (unrelated to the current convo btw)