TBH this isn’t something I’ve been doing, so, yes, I’ll be more mindful of red releases in future before I start my method - cheers
However, when I initially add files to the left pane MBP automatically generates red releases in the right pane. After running a scan I get no additional red releases, so running the scan first doesn’t appear to offer much…?
How often do you find MBP discovers additional red releases (I’m guessing often enough to make it part of your process)?
Those probably already have MBID’s attached, so they automatically get “shoved” right if you have that option enabled. If you want to “sanity check” your whole collection just to give it a try, you could temporarily set the option “ignore MBID tags when adding new files” and run a scan on it, to see what would change (just make a backup or be very careful not to safe anything ;)).
To clarify: I don’t mean red release icons - those are just error messages (like p.E.: “couldn’t load album art from X”). I meant the red tinted recordings: The more tags would get changed, the stronger the red tint of that recording is. This is why I use acoustid / scan initially. Most of the slightly reddish tinted recordings will just be updated data (year, accents added, featured artist updated etc), but then there’s some that will be deep red, because the tags from the fingerprint match are totally different from how it was tagged before:
(problems with the files: )
File has (initially) been tagged VERY incorrectly
Tracks have been switched around somehow
Recording is actually from different artist / cover version
File is broken / contains silence from a ghost track and bonus track that shouldn’t be there for the release it was tagged as
or (Problems with musicbrainz DB):
Someone added an acoustid to the wrong recording
The acoustid has simply been added to the same recording from a different release group (p.E. compilation), in which case the information attached to your files was right but sometimes it might make sense to merge recordings online if noone already has.
How often you get those depends mainly on where you get your music from. If it’s a competent & trustworthy source, the files have been tagged well before and you focus on complete / whole albums from widely known artists, you might not discover anything useful except that “those files are probably really in good shape!”.
If on the other hand you get “mixtapes” from random people sometimes or something like that, this could help detect a lot of mis-identified recordings.
Either way - it doesn’t usually take long since I can just “expand all” + scroll through it, then drag it all back if there’s no problem. I’d guess when I first add files, for every ~300 files from ~100 different artists, I find about 1 “terrible mixup” (totally wrong release + band + title) that way that I wouldn’t have had a chance to catch - ever - otherwise… and that alone makes it worth that extra step in my case.
Just scanned some of my existing files again just to see if the acoustids that have been submitted since I last checked changed anything. In ~2000 files from ~1000 releases that have already been checked several times before, I found:
7 recordings that were tagged as the correct work but wrong recording (/ mostly different intros/outros, radio version etc : same release group but release from a different country and something was bleeped etc)…
1 that was a cover / “reinterpretation” from an entirely different (less known) artist than what the tags said…
2 where my tags were correct but someone else seems to have submitted the acoustid from a wrong track (have yet to figure out how to report that)…
1 that was recognized as an obscure live bootleg by “lookup” somehow when really it was just the (non-live) “album version” from a compilation (no idea how that slipped by me - had that file for years)…
1 file where the last few seconds were simply missing and I thought it was supposed to end that abruptly :D…
several recordings that should be dupes in the MB DB (have yet to figure out which ones should be merged)
NB I’ve included some stats in the top right [search] form field
Don’t think I’ve experienced much red activity, which isn’t “Could not load album…”, but I will be more vigilant in future and perhaps follow up this thread with any questions if that’s okay?
In any case, I do certainly get better, initial, results from using [checking] “Automatically scan all new files” and “Ignore MBID when loading new files”, so thank you for elaborating on @tommycrock’s original point
Gold and Silver are just the coloring of the discs in Picard. If Gold, it means there is exactly one match for every track (possibly with some special tracks excluded, like data). Silver means that you don’t have track matched perfectly - could be missing some tracks, missing an entire disc of a set, or possibly duplicates for a single track. @ldexterldesign is using that matching to describe his process of gold and silver passes.
Did you try scanning the mp3 file (Ctrl-Y in Picard, it will build an acoustic fingerprint that can be used to find the match.
If all else, fails and the file is good, you will have to manually drag it into the correct place. Once you’ve saved the metadata on the file, though, this shouldn’t happen again.
I’m not sure what this means, how can I check this>
I just tried scanning now, what should happen? It doesn’t seem as if my computer is doing anything.
Would you be free to Skype or screen share with me and show me what this involved. If someone goes through this with me I am sure I can pick it up all very easily and fast.
This is going all over the place a little bit… but a few short answers that may help clear things up a little bit:
This means that we don’t have the AcoustID in our database/it hasn’t found a match.
Note that Lookup:
Uses your existing tags to find a match. If your files already have some existing tags, like track numbers and an album name, the best way to do it is to hit ‘cluster’, and then hit ‘lookup’ on the cluster/ the whole album. Scan:
Uses the actual audio data on the file, and tries to find the same audio data in our AcoustID database. If nobody’s submitted the data for that track, it’s not going to find it. Note that this method ignores all of your existing tags, making it much more likely that a song from an album is going to be put into a Various Artists release, and so on. But it’s very useful if you have no information for a track and need to find out what it is, or similar situations.[quote=“1uke, post:24, topic:63749”]
Would you be free to Skype or screen share with me and show me what this involved. If someone goes through this with me I am sure I can pick it up all very easily and fast.
[/quote]
I’d actually be keen to do this, as it’ll save everyone a lot of time!
You can find me by searching for aerozol1 or try Simon Hartman, with a picture of a kiwifruit. I’m on +12 time but it should work out.
I actually gave this a shot, and made a video, but I can’t get the quality as nice as the tutorial @caroline-g made…
If you can give me some pointers on what screen capture software and what export settings you used Caroline, then I’d be keen to give it another shot?
Let’s not even get started on my mic quality!
Still better than nothing… possibly
Of course! I used OBS (open source!) to record my screen (it recorded the entire screen, I later edited out the browser) https://obsproject.com/. After recording, it saved to my desktop as a .MOV file I believe. You can mess around with the settings inside OBS to change how it saves. I’d be happy to share my current settings with you if that’d help. After recording, I used iMovie to edit the tutorials.
All my videos were recorded on my MacBook Air! No special mic system.