Lookup in Browser: Clicking the green ‘Tagger’ button doesn’t seem to affect anything. Should it? Does it have something to do with my setup, or am I barking up the wrong tree?
When I find the right MBID Release ID, can I copy and paste that somewhere in the Picard GUI? I tried pasting it in the lower right quadrant ‘Release MBID’ field, but it doesn’t seem to affect anything in the top right quadrant.
Same with a ‘Disc ID’ from the website. Is there somewhere I could paste that in Picard to teach it the right release for the current album?
Question about the Lookup function algo/heuristics. How much weight does Picard give to the number of tracks in an original album? Often Picard will settle on a release with the wrong number of tracks. If I right-click ‘Other Versions’ and guess based only on the number of tracks, it’s often a great match. Does Picard prioritize number of tracks in it’s release matching algorithm?
I’d like to be able to script Linux and Picard to churn through my originals overnight, one album at a time, and if it’s a good-enough match then autonomously go ahead and Save & Remove. (Gold record icon is a good-enough match for me.) Is it possible to set up something like this? I’ve seen some documentation to this effect, but don’t know how to use it. Any scripts or pointers would be much appreciated! Originals are in one source directory, some are organized as artist-album/tracks, others are artist/album/tracks. Picard’s renaming shifts them into a different destination directory. (Yes I keep backups of everything.)
Thank you. Terrific software and learning as fast as I can.
Tagger button will load the release you are looking at back into Picard. Just does it silently, so go look at Picard after pressing it. If that actual release is already in Picard then you won’t see a difference.
You can copy\paste the MBID of a release into the search box at top right of the Picard GUI.
Not DiscId to Picard. You can only go the other way round on, taking a DiscID into the Website (either from a CD or Rip Log).
A DiscID is sometimes associated to more than one Release so you’d still need to go to the Release Page first. You could then manually add “?tport=8000” to the Release URL to trigger the green tagger button
Don’t know
Don’t know, but it would give you a lot of errors. Easier to use the GUI. Picard can make good guesses once you tweak the matching choices, but still needs a human check. As you notice, sometimes it can split an album between two releases or maybe pick a deluxe instead of the specific version you have. A task like this doesn’t need Linux scripting as it can be done by drag and dropping batches of folders into Picard and just leaving overnight to churn. Focus on making Picard your automation tool and not the OS. Work in batches.
Personally I work in batches of only 4 or 5 albums at a time as I like to visually check every match, but I am not working through a huge collection as did that long ago. Most of my matching now is as I am ripping newly purchased CDs. Some people will drop thousands of albums in, but I wonder how they check and their error rate. Picard can churn through large lists, you just need patience
Turns out my restrictive browser settings were preventing interaction with the Tagger function. First I noticed that if I manually pasted the Tagger’s url into my browser, it works. And then created a new firefox profile that’s less restrictive that also allows it to work.
Been using Picard for a week and hadn’t tried pasting a release MBID into the search bar lol.
My hope would be scripting that only renames/saves an album if it’s a satisfactory match, according to some internal Picard metric I guess. Then I’d manually process each of the remaining albums.
I’ve tried batching albums into Picard, for example one artist at a time. I guess this set of originals are in bad enough shape from a tagging perspective (and slightly off song lengths) that 5 albums turn into 13 partial matches. I’ve found it faster (and saner) to just go one album at a time. Maybe I’ll get better at batching, I’m only through the D’s in my alphabetical artist ordering.
Thanks all for the help. Each time I re-read various docs/forum posts, a little more sinks in.
I’ve experimented with both Lookup and Scan. In a few instances when Lookup fails, the releases surfaced by Scan often includes a good match, reducing time spent browsing the website.
Also I’m having much better luck with batching now. I think in my haste I might have skipped the Cluster step before Lookup a couple of times.