#musicbrainz

Hey! Could I ask you to help me figure out if I made any mistakes in a release I added?

Asking so that I can improve next time

This is the release: https://musicbrainz.org/release/a225717d-750a-4...

RaelZero: you linked to discogs master release, in MB terms that is ReleaseGroup. You need to link the specific release from discogs on MB release

also, you've marked the tracks as 'video', but you linked to a bandcamp release that contains no video (as far as I noticed in my quick visit)

Whoops! Will fix the video thing right away

Ah, that was an auto-match

Easy fix

oh I looked incorrectly about the discogs/releasegroup thing, it is linked under releasegroup, sorry

Phew

Now, on the main releasegroup page, I see that my release is flagged as "unknown" rather than "official". Did I miss another setting somewhere? https://musicbrainz.org/release-group/a9fbed4c-...

Maybe just status = official on the release info page? I got confused because that was greyed out :P

yes, if it is unset it is unknown

Got it, fixed it now

Looks decent now, right?

Link is the same: https://musicbrainz.org/release/a225717d-750a-4...

yah, looks good :)

Thanks! :D

Hello

I hope I'm in the correct channel, I apologize in advance otherwise :)

I have a Picard question and would appreciate directions if possible

Using File Naming when saving an album, I'd like to substitute automatically some characters

Is that something that would be doable through a file naming script, or am I looking at the wrong place?

(XY question: I'd actually like to replace slash ASCII '/' characters with division '∕' unicode character)

Are you wanting to replace it in the tags saved in the files?

The problem with replacing it in the file naming script is that the forward slash (/) is used to indicate a new directory.

If you want to replace it in the tags themselves, then you need to make the replacements in a tagging script (as opposed to the file naming script).

quinq: ^

Sorry rdswift, was in a meeting

Not in the tags, but in the filenames

(which would be named *from* the tags indeed)

Yes, I want to replace slash with the unicode division character *because* it's a forbidden character in filenames :)

You would have to replace it in the tags (using a tagger script), but even then I'm not sure that Picard wouldn't automatically replace it with an underscore. It *might* work if you disabled the "Replace non-ASCII characters" option in the File Naming options.

i personally wish there ws a 2use x instead of y" for those "illegal characters"

so i want to just us space or nothing for most of them in filenames

but for : maybe " - " works

it's actually really annoying thati have to manually rename files to remove underscores

I don't care about the file names generally. it's fine to just ommit any "illegal" glyphs

CatQuest, exactly, that was my question :)

Can I suggest that you enter a ticket? I suspect that there would be a lot of users interested in that sort of option.

indeed. pls link it i'll want ot follow it

I've got to cook a cake, but I'll try to!

:D

Done: https://tickets.metabrainz.org/browse/PICARD-2514

PICARD-2514: Ability to replace characters in filenames

Please fill free to comment if the description isn't clear enough

s/fill/feel/

Thanks for this. I don't know when it will get looked at, but at least it's recorded and shouldn't get lost.

Sure, no hurry there

having a fun, buggy day

anyone ever open an edit on a release and the track names are all in the number fields, and the times are in the name fields?

and i had to cancel and redo an edit because the title change disappeared from it, and it corrupted one of the track changes

(sounds like one of my friday mornings)

yeah, weird stuff

https://musicbrainz.org/edit/90937396 here's my cancel

note the lack of a title change, and the weird shit happening to the 14th track

that's not what it was when i submitted it

Is there a musicbrainz rule about using ASCII quote ' instead of apostrophe ’ in track names?

i'm not sure, but i think the usual preference is to be as accurate as possible

whatever the release has

that said, for usability stuffs, i definitely would prefer things that are more universal

for example, when i do romaji transliterations, i use wapuro instead of other methods, because it avoids special characters not in the simple a-z set

It's not often clear what a “release” has

It's more in par with the language script

yeah

using the language relevant characters is probably correct

Thanks :)

and then translations/transliterations can use a more compatible one

for example, japanese uses an L shape thing for quotes

in romaji, i switch that to "

allright

Bit late but - typographical apostrophe is preferred. Picard can then be configured to make it ASCII (other way round is trickier because it's context dependent)