#musicbrainz

first time i've had to tag a remix-style release; any pointers on how to organise metadata?

i don't know if the track artist should be the original, and album artist as the remixer

sbaildon: I usually look how it's done on other, similar albums

sbaildon: ^ if some things are unclear then let me know since it's a fairly new guideline

:bow:

those guidelines align wonderfully with my own preferences - thanks for the link

what do i do about E: 12:41:46,485 acoustid._on_fpcalc_error:254: Fingerprint calculator failed error= execvp: No such file or directory (<ProcessError.FailedToStart: 0>) program='/usr/bin/fpcalc' arguments=['-json', '-length', '120', '/dev/shm/cache/VA (?

iconoclast_hero: In Options > Fingerprinting set the path to the fpcalc executable. You might need to install this first

that's what i was asking about, how it is provided for normally, but it's libchromaprint-tools

this might be more of a metabrainz question, but shouldn't that be a dependency installed by the package manager? (not 100% how picard was installed)

well it's from the dev channel : MusicBrainz Picard 3.0.0.dev2

yes, it usually is. what OS are you on? some distributions choose to have this an optional dep

Linux gigabyte 6.7.6-060706-generic #202402230933 SMP PREEMPT_DYNAMIC Fri Feb 23 09:43:37 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

you probably shouldn't use the current master branch right now. no plugins will be supported

i've noticed.

let's get to that in a minute

no, I mean which distro?

i'm running Rhino because i got tired of the 2 year LTS cycle.

and last time i ran uname -a it said Noble whatever

so it's running on some frame of 24.04

ok, no idea about rhino and how they package. actually never heard of it :)

it's supposed to be a rolling ubuntu

which will hopefully solve my problems but i have serious reservations that what you just said is going to be a gigantic PIMA

ok. how did you install picard then?

either rpk > nala or apt.

but i added the dev channel from my install script.

i must've done it manually after i migrated to rhino as it isn't in my "first-install" script.

if it's ubuntu based you can probably also use the PPAs listed on https://picard.musicbrainz.org/downloads/ . both the stable and daily should be fine, both are currently providing Picard 2.x builds

sudo mv musicbrainz-developers-ubuntu-daily-noble.sources "#musicbrainz-developers-ubuntu-daily-noble.sources#"

this makes apt ignore it, but is there some way I can "comment out" the file name but leave it in /etc/apt/sources.list.d ?

(not the best place to ask, butmaybe someone knows)

don't know if there is a naming that disabled the file. but you can comment out the sources inside the file by prefixing with "#"

inside the file, yeah, that's a plan.

so if the "daily(unstable)" PPA on that downloads page should be fine then ....

it's providing the version i pasted above.

MusicBrainz Picard 3.0.0.dev2

because i'm looking at the sources file and the source is:

is the url from launchpad: https://launchpad.net/~musicbrainz-developers/+...

that's odd, it's supposed to build the 2.x branch

which implies to me that the daily has the x-dev version and that's got all the plugins disabled.

log a bug?

#metarainz?

let me check

i'll put my sourced file up

i assume that public key is fine to leave up as it's "public" and not min?

I have the 2.11.0~final.0-1+git5206~ppa25~ubuntu22.04.1 package installed here, and Picard reports itself as 2.11.1dev1 as expected. There is no reason why it should be different for the 24.04 build, same build recipe

are you sure you are running /usr/bin/picard and not some picard installes elsewhere?

let me look

i would say that no i'm not sure of that.

and it's looking fairly doubtful, sorry.

ok.

so there's no point in me running that 3.0.0.dev2 ? I'll ununstall it.

i'm fairly sure I'll find it's git in ~/bin/gits.

yes, there is currently no point really to run it. due to the larger changes currently in work it is not really suited for daily use.

makes sense.

i was just trying to get everything migrated as quickly as possible

and there was probably an issue with the package manager so i just grabbed the git (yes, that's how it was installed)

I see :)

thanks for the help and sorry for the trouble

all fine, you're welcome

usually the git master is fairly ok. it can contain some unexpected bugs always, but we usually keep it pretty stable. it's just right now that things are moving

yeah, i thought the plugins were just old, but this makes more sense

the plugins will need updating. but as we are about to redo the actual plugin architecture this won't happen to soon (but I hope to get back to the new plugin system soon and then there should be an initial version). but it will stay unstable for still a while