Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_musicbrainz (Read 278394 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_musicbrainz

Reply #150
Thanks Dremora for the plugin, I've been using it for quite a while now and find it very useful.
I still have a little "problem" with it though :
Would it be possible to add the Release Group date of an album to a specially created field in addition to the print date?
I'm asking this because it makes more sense for me, in a musical logic, to have the date of when the music was first released instead of when the record was made and since I'm using foobar to sort and move my music it would help a lot.

foo_musicbrainz

Reply #151
Thanks for the great plugin!
I'd like to ask whether it will support download of album art from musicbrainz in the future?

foo_musicbrainz

Reply #152
Hello again Dremora.
I know I’ve already said it but it seems you are not around these months.



There is a problem with foo_musicbrainz as it currently takes the recording names instead of the track names.
Take this LATIN release for instance (pseudo release). Usually people chossing this one would like to have LATIN track names and artists.
It would be nice to have foo_musicbrainz take the track names instead of recording names (it could also be in settings).



The other minor stuff is that, rather than exact MBID paste in Get tags from Musicbrainz (by Musicbrainz album ID), we could paste a full MB URL.
URL from which the MBID would be caught by a regex match :
Code: [Select]
([a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12})


I hope you don’t drop this wonderful component.

foo_musicbrainz

Reply #153
There is a problem with foo_musicbrainz as it currently takes the recording names instead of the track names.
Take this LATIN release for instance (pseudo release). Usually people chossing this one would like to have LATIN track names and artists.


Oh really? Have you made a poll for people across the world so now you know what they prefer? If not, please use statements as "I would like".

foo_musicbrainz

Reply #154
Are you kidding?
Look at the LATIN RELEASE and then look at the ORIGINAL RELEASE (and for your information, this is the latter that I would want anyway).
They are looked up by the same TOC, the aim of this is to choose what you want.
I was just pointing out a flaw in the component that makes that whichever release you choose, you will get the same recording names. ← UC?

foo_musicbrainz

Reply #155
Are you kidding?
Look at the LATIN RELEASE and then look at the ORIGINAL RELEASE (and for your information, this is the latter that I would want anyway).
They are looked up by the same TOC, the aim of this is to choose what you want.
I was just pointing out a flaw in the component that makes that whichever release you choose, you will get the same recording names. ? UC?


Okay. So this is just a bug but not the matter of user preference. I mean bug assuming MusicBrainz API works in the same way their UI works.

foo_musicbrainz

Reply #156
Well, their API returns both track names and recording names (cf. MB web service call for this release).
I think Dremora might have taken the recording names instead of the track names.
The fix could be quite easy and fast.

foo_musicbrainz

Reply #157
Hi Dremora

I recently have encountered a weird situation with featured artists. Sometimes foo_musicbrainz will write the "feat. artist" to the artist tag for the track resulting in "artist feat. artist." I'm not sure if this a problem because of something with NGS or what, but it does not do that all the time. For example, with this release (http://musicbrainz.org/release/14a5c8d1-37ec-4124-b988-30bdacbc0cc4) foo_musicbrainz tags the first track artist as Alan Menken feat. Charles Heston and the track title as Long Ago... If I tag the same album with Picard, the artist for the first track is just Alan Menken and the track title is Long Ago... (feat. narration Charles Heston). I do not have Remove feat. artists from track titles checked. I assume this is unintended because it doesn't do it all the time, but if you could make it configurable that would be excellent as it saves a bit of work on my part to correct it.

foo_musicbrainz

Reply #158
Hi Dremora

I recently have encountered a weird situation with featured artists. Sometimes foo_musicbrainz will write the "feat. artist" to the artist tag for the track resulting in "artist feat. artist." I'm not sure if this a problem because of something with NGS or what, but it does not do that all the time. For example, with this release (http://musicbrainz.org/release/14a5c8d1-37ec-4124-b988-30bdacbc0cc4) foo_musicbrainz tags the first track artist as Alan Menken feat. Charles Heston and the track title as Long Ago... If I tag the same album with Picard, the artist for the first track is just Alan Menken and the track title is Long Ago... (feat. narration Charles Heston). I do not have Remove feat. artists from track titles checked. I assume this is unintended because it doesn't do it all the time, but if you could make it configurable that would be excellent as it saves a bit of work on my part to correct it.


Hi, it’s the exact problem I was saying above, but Dremora seems away from the project for a while…
«??. foo_musicbrainz takes the recording name, not the tracklist track name. It should be either the opposite or configurable.
In this case?:
Recording name (the one foo_musicbrainz gets)?: Long Ago... by Alan Menken feat. Charlton Heston.
Track name (the one you want)?: Long Ago... (feat. narration Charles Heston) by Alan Menken

foo_musicbrainz

Reply #159
Ah, I did not realize we were describing the same thing! Some good news is that Dremora as posted code updates within the last few days!

foo_musicbrainz

Reply #160
Wow, Szekely… I wondered how you would know that…
Then I found this GIT thing !
It’s awesome ! It is over there that I should leave my comments and everything.
Here is a foo_musicbrainz user conversation, but over is the bug reports and everything ! 

foo_musicbrainz

Reply #161
I'm dreaming of a plugin ("foo_discbrainz"?) which would take info from artist discogs page and transfer it to musicbrainz. I have a problem with Molly Nilsson - she's already present in discogs database and not existent at musicbrainz.
end of line

foo_musicbrainz

Reply #162
I'm dreaming of a plugin ("foo_discbrainz"?) which would take info from artist discogs page and transfer it to musicbrainz. I have a problem with Molly Nilsson - she's already present in discogs database and not existent at musicbrainz.

You might be interested in this Greasemonkey plugin.

To everybody: thanks for your comments, suggestions and bug reports! I've already started working on a new version, but due to very tight schedule can't promise any dates. The list of planned features is on the Github page.

foo_musicbrainz

Reply #163
To everybody: thanks for your comments, suggestions and bug reports! I've already started working on a new version, but due to very tight schedule can't promise any dates. The list of planned features is on the Github page.


Thanks very much for your great work Dremora?!
I was scared you dropped the plugin until I eventually was pointed to something called github by Szekely.
Is there an easy way to see where a plugin version applies, what are fixes waiting for next release??
For instance, current version is 0.3 beta 2, what line does match this version/date in commit history or in another view maybe??

foo_musicbrainz

Reply #164
Sure, git has tags for this


foo_musicbrainz

Reply #166
Sure, git has tags for this

So I go to tags page, I copy the last commit for 0.3-beta-2 version (which is 50cdeb59f8) and then go to commits page and look for this ID??
Is there a faster click?? It’s already quite cool anyway, thanks?!
This way I saw that Total medium count is now actually used (2011-06-03) was the last commit included in release so all the later commits (2012-01-29 and upcoming) are the ones that are waiting for the next release. Did I understand it correclty??

foo_musicbrainz

Reply #167
Dremora plz can you add function, similar to picard: "Use standardized artist names". It's very useful, because in MB a lot of compilation have artist name titles how in cover, but in my library to easy navigation (and autoplaylist stuff) I wanna to have only one artist name variant. Thx.

foo_musicbrainz

Reply #168
still beta status
is development dead already?

foo_musicbrainz

Reply #169
I must apologize for a long delay of a new release. I've been quite busy lately finishing my master's degree. The component development, apart from a couple of fixes, hasn't been progressing, as you may have seen on GitHub. The fact that I've switched to Mac as my main machine only adds to it (but I still use foobar2000 under VirtualBox). Nevertheless, I'm planning to continue development as soon as I get proper internet connection (my Windows 7 development machine is located in another country and can only be accessed remotely).
Regarding the beta status, there's only been one bug discovered (and fixed), and for some reason I didn't want to release a new version of the component just with one fix 6 months after the beta version. However, I'm changing my mind, as having this fix now (and a small feature) is better than sometime in the future. The source code is available on GitHub, I'll provide a binary version ASAP (or you can build it manually). Thanks for the patience!

Update: binary component is there, enjoy!

 

foo_musicbrainz

Reply #170
Finally!  I've been waiting for some progress on this for ages!~ Thank you very much.
I might fork at some point in the future and help you out, if you don't mind that is.


foo_musicbrainz

Reply #172
Finally!  I've been waiting for some progress on this for ages!~ Thank you very much.
I might fork at some point in the future and help you out, if you don't mind that is.

Sure I wouldn't mind, that's why the project is on GitHub


foo_musicbrainz

Reply #174
I use this plugin almost every day. My workflow consist from 1. download release from what (yarrr) 2. make APL files for album by script (it's unbelievability good solution for fb2k library and unique, because i can seed data and edit tags in my own way, collect statistic and even sync stats and files with automatic conversation to iPod)  3. Take tags from MB by TOC (or add it, if it miss).
And I collect to notebook all usability issues and features what I miss. I think future developers must take look to foo_discogs for some good solution for such kind of plugin. Here my list:
  • Separate menu item in context tagging menu and may be with not so long strings, look at discogs screen.
  • [/b]When you take tags by TOC (by hotkey) and if nothing found, will be great to show window with 2 option: first add TOC to MB, second take tags by artist & album. Now you get only error window if nothing found.
  • In getting tags by artist & album, must used "more similar search algorithm". I mean that now, result of successful searching will be possible, if search string very similar to MB names Especial problematic releases with title such as "%title% Vol. #".
  • Make possible when you add TOC, also send album title to page search window, or get it, into buffer, because now, it so boring every time manually get release name to buffer (even with hotkey)
  • I think it necessary to give user possibility to "Edit tags Mappings" like in discogs plugin. It really flexible to choose what data you need and how it must stored (i think many of users with big and long live libraries may have own tags, such as "record date" or "style" for example and useful to write "original release date" to first and "tags" for second).
  • Must have feature is to colorful highlighting changes between all new tags and already exist. It help to both side, for quality MB database, if consciousness user feel something wrong  and for end user, not to be confused by wrong song titles or anything else.
  • Add 2 multi value tags. %album artist multi% and %artist multi% (anyway name of them must be editable in tag mappings) but name strings must be resolved to main MB artist name. This allow to give best advantages of MB data, to have super correct navigation in library (like in MB site). Because, now so many album artist have "artist1 meets/&/feat./etc artist2" and it's not good for navigating in large libraries. Also this features help autoplaylists maniacs, like me.
  • Plugin lack in data which can be taken. I wrote in my priority what I miss (in MB names): releasecountry, originaldate, comment, media, language. And all other form http://wiki.musicbrainz.org/MusicBrainz_Tag because may be someone find useful to have "mixers" and other relationships, or proper sorting titles. Also in last changes of MB "Release Type", I think know it's must be also multi value tag.
  • I dream about having multi value tags for %album artist% and %artist% country. It will so beautifully for making autoplaylist such as "Europe Modern Reggae", "Jamaican Dub Golden Era", "Russian Classical", "Third WORLD music", "UK stepeer", "USA hip-hop" and so on. I think, it will be more good, like in 7 point to have both %album artist country% and %artist country% to more flexibility in library navigation or making "album" auotplaylists.
  • Suggestion witch already in github, give possibility choose what tag to resolve and how. I already suggest it at private email to dremora, but now i think if we have possibility to have 2 mulit value tags with "correct & main" MusicBrainz name of artist for navigation, it will be nice to have normal tags (for last.fm maybe) how them written at covers, may be it makes sensation of original release

I know that place of all writing above at github, but with my english spell... may be I don't correct explain my thoughts. Also someone said something about fork, so I think this thread good place for such discussion. In this post I wrote what I really miss, also i have many diffent other thoughts about not primary features. Some of them require account connection:
1). send ratings (with auto calculation overall release rating) 2). add to personal MB collection (I heard that in summer google code, them will add possibility to get notification about release in personal collections, primary it done for VA releases, but I think it will be nice, if you get tags automatic by foo_musicbrain  add to "My Collection" (with checkbox in getting tag window) to get emails about changes concrete release what you have, and not tons of spam about artist edits) 3). Import fb2k tags to MusicBrainz, like "Import to MB from Discogs" usersript, because it's really fast to edit data with masstager scripts in fb2k, rather then site editing 4). Getting CoverArt to customizable folders and name files, and ability to choose what type of cover you whant (may be only "Front"). For example i use temple "_cover_art" in files folder, because in separate path, it boring to rename folder if you change tags.

P.S. I am glad to help in anyway to anyone who continue to work with plugin. Of course with my knowledges I can't develop, because I am not coder, but I can wrote simple scripts, find and analyses information  But I think the main help, that I can give is TESTING. Anyway you are welcome to PM or mail me.