EDIT:let me know how I can best scan for this issue BEFORE doing a RenameFiles action which is where things get most disruptive. Before I do RenameFiles, it’s super easy for me to fix stuff in Picard (although my obvious preference would be to figure out the root issue and have it all done using SongKong).
Spoke too soon. After doing test imports of maybe 50 albums I went for a big one and there are a ton of albums coming in with the same issue. Initially I thought it was just live or comps, but no I’m getting this issue with a number of albums. Again, all of these are in the logs I sent you but I’ll also send you the logs for the last file rename/import action where all this becomes very obvious.
A few of the albums that have this issue:
imperial bedroom
from her to eternity
I heard they suck live
nevermind
riddim warfare
It depends on your music player but the composer will be added to the Composer field which is commonly supported and we also add the Work to the Work field (which is less well supported). So if you want to play by composer, simplay use the composer field.
e.g this is the Browse By Composer view of one of your reports.
But as you can see nothing listed. Unfortunately the problem is that this list is generated by the Matched to MusicBrainz section of report, and this section only shows albums that have actually been matched to by SongKong, and these problem albums were not rematched by SongKong but they do have MusicBrainz Ids from previous time so they are not listed. This is a bit confusing and I may have to change something.
So I think this will work
Start Metagrater task and add MB Recording Id, MB Release Group Id, MB Release Id, MB Track Id to remove these ids.
Re-run Fix Songs, then check the Summary:MusicBrainz Inconsistencies:Only One Song matched section, and if now lists some albums match them one by one using Match To One Album task.
Edit:Alternative
I think the problem with Matched to MusicBrainz Release is only issue when rematching, if you temporarily set For Songs Already Matched to Update Metadata Only and rerun Fix Songs then the Summary:MusicBrainz Inconsistencies:Only One Song matched should list the albums we we were unable to fix.
I like the functionality you’re proposing in the issue you just posted a lot. Having to know ahead of time which FixSongs profile to run (e.g. your “Alternative” method above) isn’t realistic at least with how I’m doing things, so knowing this issue can’t ever be hidden from the user would be super helpful.
Along these same lines, I think it would be massively helpful to incorporate conditional highlighting [in red] for important errors, like this. I’m super visual and when I first started using songkong I was TOTALLY overwhelmed by the options, reports etc… and in the reports it was all just a blur of light blue links everywhere. Now after spending many hours with the app this is a bit less of an issue, but until you mentioned it I still wasn’t paying any attention to any of the Summary:MusicBrainz Inconsistencies or Discogs etc… but if those links turned red when there were issues I’m 100% certain I would have investigated them to understand what the issue was. So yeah I’m throwing in a HUGE +1 for conditional highlighting for important errors.
I use PlexAmp and afaik there’s no easy way to see composer info, at least in the iOS app. Please correct me if I’m wrong because it would be wonderful to have access to this tag!
OMFG I just looked through that initial report under the Summary:MusicBrainz Inconsistencies:Only One Song matched section and if I had seen this (conditional highlighting) and fully understood what was happening (unlikely until I knew there was an issue) this would have saved me HOURS of troubleshooting and later cleanup. Holy crap. Funny how much time you could save previous you with the knowledge present you has gained lol.
Yes it was just a temporary workaround to resolve your current issues rather than a general purpose way to do things.
But the Metagrater method is probably better.
I take your point, however the title is background is Yellow this indicates a warning, because we cant know for sure it is an error. For example if you only actually have one song of an album then it is not really an error.
If there was no issues then the section would not even be displayed, so if the section is there this indicates there are potential issues that should be checked.
The hyperlinks are blue because they are hyperlinks, and by default hyperlinks are blue.
I don’t use it but if Plexamp doesnt support Composer field I would sggest it is not really a viable tool for playing Classical music.
Gotcha. I’m commenting as a new user not an expert. Your app is very powerful but frankly somewhat overwhelming. I didn’t even notice that different tabs/links appear or disappear depending on the data returned. I’m not spending an hour pouring over each report… I just want to tag my library properly, know if there are issues, and go about my day.
What I was referring to with the conditional isn’t specific colors… yellow is totally fine, and now that I know what I’m looking for it makes perfect sense when I’m already on that page. What I am taking a bit of an issue with and pushing back on, is the top level link… so sure if I’m a SongKong expert I would notice "hey Summary:MusicBrainz Inconsistencies:Only One Song just popped up, better look into that. But for a filthy casual such as myself, there’s no way I’ll have the entire UI memorized. Sure I’ll know to look for this particular link now but it would’ve been helpful to have say a yellow background highlight in the main summary page. Basically IMO, anything like “inconsistencies”, “errors”, “warnings” etc should be called out to the user in the top level so casual users don’t have to literally read each thing searching for any issues. This is a suggestion (not an attack) from a new user who spent hours troubleshooting a probably outlier issue that would be obvious to an experienced songkong user.
Lol nice snark. The links here are being used in a very specific way, therefore could be handled in a slightly different way. But your app, your call of course
No snark intended. it didnt occur to me that it could be okay to have different colours for some links until I saw they could be changed on Bootstrap to have different coloured hyperlinks for different reasons - I have always had them consistent over the site
But I think the issue is we need some possibly coloured links on the main summary page such as the text highlighted blue in screenshot below
I also think it would be incredibly helpful to conditionally call out warnings/inconsistencies in the top level tabs of the summary to make it obvious to noobs there’s something to at least look into. It would make parsing the report super fast because no highlight = no worries. But if a warning/inconsistency is highlighted, it’s something to look into. This would be even more important for stuff that doesn’t disappear.
I just grabbed a random report to show what I’m talking about. Just glancing at this FixSongs report as it’s presented now, I wouldn’t know there was a possible issue (maybe there’s an indication YOU would see but as a noob, to me it just looks like a report without any issues), however, there are Discog inconsistencies but there aren’t musicbrainz ones. This wouldn’t be obvious to me. Anyway, I just manually highlighted the text and took screenshots, but you could do whatever you wanted to do color/style-wise. The different screenshots just make it super obvious what I’m trying to say here. You WOULDN’T have musicbrainz conditionally highlighted here since there aren’t any issues, but you WOULD have Discogs highlighted because there are.
Hard to say. I brute forced though the issues by manually cleaning up the problem albums using Picard.
That said, once I made the changes you suggested and reran FixSongs the problem went from hundreds of albums to a handful. I’m still not sure exactly what the cause is/was but it was manageable after the settings changes. I would say it happened to maybe 5 albums in my final run. If it’s something you want to research let me know how I can help and I can rerun FixSongs on a duplicate backup of untouched albums or whatever.
I also want to thank you for the solid support and even with the issues I had SongKong saved me hours of drudgery
I made a start with adding the hyperlinks, but Im not sure if a bit confusing having yellow hyperlinks for the inconsistencies ones, and blue for the others, what are your thoughts?
I don’t think it’s confusing at all… think of it from a noobs pov: first couple runs and everything is clean and blue. Run three and suddenly there’s a bright yellow tab up top. It will catch their eye for sure and force them to investigate.
However, I do think it’s a bit hard to read the yellow text.
I think doing a mock up with BACKGROUND set to yellow and the text set to the blue is something to try. It’s probably not going to look beautiful as a color combo, but the bottom line here is calling attention to those tabs, which I think a yellow background will do better than text color being yellow since it will be easier to read and look like it’s highlighted rather than maybe a UI glitch.
That said I think any visual indicator is an improvement, so I’m stoked to see this version!
This is the summary tab, not an error tab so doesn’t make sense to me to make this tab yellow. This is a version using red, that at least would grab the attention as red usually indicates an issue
I’m 100% fine with this. Red is great, it’s readable, and most importantly it says “hey look at me there’s something going on that needs your attention” which is exactly what the summary needed. Bravo!
