<discordbrainz> "<UltimateRiff> a good example is..." <- The only good thing about that, being an example! 😂
aerozol[m]
Thx!!
Oh, the mastodon link I posted only got broken on the Discord end, interesting
discordbrainz
<04elomatreb> weird
joessexmpp has quit
<10volumetrique> URL encoding? Weird
<05rustynova> Oh hey. I remembered I got a Mastodont account AND the app by clicking the link... Although I'm more of a Lemmy person, but over there MB is inexistent
MeatPupp3t has quit
MeatPupp3t joined the channel
iconoclasthero joined the channel
iconoclasthero
is there some reason that the "long" in "long Beach, CA" would not be capitalized by the case guesser? i.e., is this a bug?
wiktionary suggests it is not a prepostion in English, only in Chineese and a couple languages I've never heard of.
discordbrainz
<04elomatreb> I don't think that's intentional
<04elomatreb> @iconoclasthero is there something more in the title? When I try it, it capitalizes both words for me
iconoclasthero
"Thunder on the Mountain [2006-10-21: Long Beach, CA]"
I threw an s in front of long and it capitalized it.
discordbrainz
<11iconoclasthero> it started out Long and the guesser made a change.
<04elomatreb> my guess would be that it gets capitalized because of the ETI capitalizer for "(long version)"
<04elomatreb> sorry, I meant it gets lowercaseed
<04elomatreb> but I can't find the relevant bit of code right now
<04elomatreb> But "Long Beach" is a name so it should be capitalized in all contexts
<11iconoclasthero> aside from the fact that it is a proper noun, Long should be capitalized in a title regardless. if "(long version)" should be lowercased then the regex or whatever is probably insufficient?
<04elomatreb> it gets capitalized outside of brackets
<11iconoclasthero> oh
saumon has quit
iconoclasthero has quit
iconoclasthero joined the channel
saumon joined the channel
Maxr1998 has quit
Maxr1998 joined the channel
Maxr1998 has quit
leonardo has quit
lojik has quit
leonardo joined the channel
lojik joined the channel
Maxr1998 joined the channel
<06jbloom91> Is there a way in Picard to retain vinyl/cassette track numbes instead of the tradition 1,2,3 and retain A1,A2,A3 etc?
<11iconoclasthero> is the underlying data in that format?
iconoclasthero has quit
<06jbloom91> On Musicbrainz? Yeah
reosarevok[m]
Yeah the guess case special cases are very much not smart
discordbrainz has quit
Other than having some stuff only be lowercased in parens under the assumption that it will be ETI more often than not
discordbrainz joined the channel
IIRC it has to operate on single words so it's hard to make it smarter without hacks or a full rewrite
ijc has quit
ijc joined the channel
discordbrainz
<06jbloom91> Okay, so just a manual process? Not a huge deal, I was just wondering if there was a way I could be lazy lol
Maxr1998 has quit
<04elomatreb> @jbloom91 I think reo was referring to an earlier conversation
<06jbloom91> Oh lol whoops
<04elomatreb> (this channel is bridged and the bridge doesn't mirror the "replies to" links yet)
<04elomatreb> to answer your question, I don't think there is such an option. It is also technically against the spec for e.g. the ID3 metadata format (which mandates that the track number must be purely numeric)
<04elomatreb> not that it matters too much
<02UltimateRiff> I vaguely remember something letting you pull the track number as credited... whether that was built in or a plugin, I don't remember (and I may be misremembering anyways)
<06jbloom91> Awesome, thanks @elomatreb ... Now uh, where do I enter said script?
<04elomatreb> Options > Scripting > Add New Tagger Script
<06jbloom91> Thank you
<06jbloom91> Would I just add it to the already existing chain?
<04elomatreb> you can have multiple scripts active at the same time, either add it to an existing one or add a new one that just contains that line
<04elomatreb> unless your other scripts already change the track number variable, it won't affect other fields
Maxr1998 joined the channel
<06jbloom91> okay, thank you. I like, have never messed with scripting before so I just wanted to make sure
<04elomatreb> yeah it's not super user friendly
<04elomatreb> but hard to avoid that kind of unfriendliness with a powerful interface
<06jbloom91> Hmmm.. I must have done something wrong, cause nothing changed.
<06jbloom91> I'll monkey with it a bit more
<06jbloom91> Hmmm
<06jbloom91> Oh I see, I'm an idiot
<06jbloom91> Wait, no I am but still no change...
<06jbloom91> THERE WE GO
<06jbloom91> Thank you @elomatreb
reosarevok[m]
🥳
scrumplex_ joined the channel
scrumplex has quit
Maxr1998 has quit
mll_ joined the channel
Maxr1998 joined the channel
mll has quit
trolley has quit
trolley joined the channel
Anton[m] joined the channel
Anton[m]
I have someone credited as "Recording Supervision" for an opera recording. Which relationship fits this best?
discordbrainz
<04elomatreb> Anton[m]: I would probably treat that as a recording engineer
Anton[m]
Thanks! May I also ask: I can add e.g. the conductor for the opera as a release relationship, or instead as a relationship for each track. Is there a difference/preferred way?
iconoclasthero joined the channel
reosarevok[m]
Each track, unless you're not sure if he conducted every track
Release level is only if you're not sure what recordings something applies to
(for example, for the singers, they might only sing on some tracks but you might not have that info)