Let me pressent my latest personal project, Harmony Assistant!
This tool helps you quick and easy import multiple albums one after another automatically using Harmony.
Longer read:
I’m currently in the works of sorting my personal music library using beets but a lot of albums does not exist in MusicBrainz.
I started using Harmony while processing using beets but after maybe 10 additions but still being on the letter A in my library I decided to automate it more and Harmony Assistant was born!
This tool automates as much as you want and has options to pause before publishing an album on MB for manual review, or you can just let the script ripp through all the albums.
It tries to solve any errors possible like lables or duplicate by checking if the available options matches what you’re currently trying to add. It it doesn’t it will pause and notify you to maunally fix the problem.
I see this tool in some kind of blend between manual import and a bot. If you let it go 100% automated it could be counted as a bot but if you let it pause for manual review it won’t be any direct difference between manually importing using Harmony.
Would love some feedback and throughts and what could be done to improve it even more
Both yes and no. The script pauses if errors that can’t be fixed automatically and it pauses before submitting the edit so you can double check the info. The last part can be disabled and that would make it act more like a bot.
The release actions-stage of Harmony is fully automated. It will add the ISRCs, link external IDs and upload the highest resolution cover art to the release. This is info that Harmony gathers and not super much to double check wany way.
From your video, I didn’t see it try and reuse existing recordings, and looking at some of your recent edits, it looks like you’ve entered some duplicate recordings already. Just browsing through your recent additions, I noticed the release I Do You by Anna of the North which added 5 duplicate recordings, but thankfully another editor took the time to merge them: osdt.de
Those could have been real human errors, we’ve all accidentally added duplicate data before, but if they were added with this tool it could mean a lot of cleanup duty for a lot of editors.
There’s also the fact that Harmony is not perfect. Yes it is a great tool, but there are cases where it will show incorrect data. Could be as simple as a capitalization / style mistake to completely jumbled tracklist order. Things like these can be spotted by editors paying attention to what they’re submitting, but less likely to be picked up by an automated process.
The script checks if MusicBrainz finds any duplicates and if it does it pauses the process so you can check if any matches the album you’re trying to import.
From my understanding the osdt.de merges is for recordings, not releases. Eg the recording Meteorite exist in both the release Crazy Life and the releaase I Do You, so the merge it to say that the song in both releases is the same recording?
I know I did a bunch of duplicate release uploads for the artist [.que] when I started developing this tool. This was before I knew about https://test.musicbrainz.org/ for stuff like this. I have added some code to modify Harmonys URls to point to https://test.musicbrainz.org/ but I can’t seem to login to the site. The only login I could get working was to the user mb but that one can’t upload releases. There doesn’t seem to be any information about this ether in the docs. I might be missing something…
I’m gonna record a better video showing off all the edge cases and better explain what’s going on but first I’ll take care off the test.musicbrainz.org login problem.
I took the liberty of creating an account with your username and pass mb (like all others in the test database) that you can test with. I force-verified an example email so it can edit.
