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 282107 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_musicbrainz

Reply #225 –
This may seem odd but I've noticed that any songs with an apostrophe use a different apostrophe (’) than the one found on musicbrainz ('). Obviously not an issue in and of itself, but since I scrobble to last.fm the tags end up being wrong. Is there any way to fix it manually without having to change each individual apostrophe?

foo_musicbrainz

Reply #226 –
file>preferences>tools>tagging>musicbrainz tagger>convert unicode punctuation characters to ascii

foo_musicbrainz

Reply #227 –
Simple as that. Thank you.

foo_musicbrainz

Reply #228 –
Quote from: ForestD on
This may seem odd but I've noticed that any songs with an apostrophe use a different apostrophe (’) than the one found on musicbrainz ('). Obviously not an issue in and of itself, but since I scrobble to last.fm the tags end up being wrong. Is there any way to fix it manually without having to change each individual apostrophe?


I believe you're mistaken - MusicBrainz has an official policy of preferring (’) over (').  (I think this is stupid.)

foo_musicbrainz is therefore probably pulling in exactly what's found on MusicBrainz.

foo_musicbrainz

Reply #229 –
Quote from: neothe0ne on
I believe you're mistaken - MusicBrainz has an official policy of preferring (’) over (').  (I think this is stupid.)

foo_musicbrainz is therefore probably pulling in exactly what's found on MusicBrainz.

I hate that preference so much. I wrote my own tagger which uses MB (outside of foobar so wouldn't be of interest to anyone else probably) and that was one of the first issues I fixed.
 

foo_musicbrainz

Reply #230 –
Instead, First release date <ORIGINAL RELEASE DATE>, duplicated <DATE>.

foo_musicbrainz

Reply #233 –
Hi everyone! You've probably noticed that there was no updates in the last couple of years to foo_musicbrainz. The explanation is quite simple: I have switched from Windows to Mac, and from foobar2000 to cloud-based music players. I should have announced this mush earlier, but better late than never: I won't be supporting this plugin anymore. The good news is that the source code is on Github, and whoever wants to take ownership of the project will get my blessing.
There's actually an unreleased patch (on the master branch on Github), so simply building and releasing the new version with this patch would mark a new beginning

foo_musicbrainz

Reply #234 –
Meanwhile, I experimented with Hackintosh on my previous desktop, which is now a dedicated Windows machine, and moved to a Retina 5K iMac, where I use OS X most of the time now.

But I pay about $84/mo for a Windows VPS with a Visual Studio license, so I can continue to maintain my Windows projects, regardless of which operating system or computer I am using, or even wherever I happen to be in the world at the time. Which shows dedication, considering I probably have pumped out about 5-10 updates since switching to this system many months ago. Expensive, but I can currently afford my expenses.

foo_musicbrainz

Reply #236 –
Quote from: kode54 on
Meanwhile, I experimented with Hackintosh on my previous desktop, which is now a dedicated Windows machine, and moved to a Retina 5K iMac, where I use OS X most of the time now.

But I pay about $84/mo for a Windows VPS with a Visual Studio license, so I can continue to maintain my Windows projects, regardless of which operating system or computer I am using, or even wherever I happen to be in the world at the time. Which shows dedication, considering I probably have pumped out about 5-10 updates since switching to this system many months ago. Expensive, but I can currently afford my expenses.

It's good that you are dedicated to the software you've written. However, the fact that I'm not using the plugin or foobar2000 anymore made me realise it would be better for someone else from the community to take over. Even if I were to continue maintaining the plugin I wouldn't be able to put as much effort into it as someone who's actually using it.

Quote from: marc2003 on
lvqcl has already provided a component built from master some months ago..

https://www.hydrogenaud.io/forums/index.php...st&p=887441

Good, didn't know about that!

foo_musicbrainz

Reply #237 –
Since I forgot to say it in my last post, thanks for the making the component. I like the consistency it offers compared to picard when handling files with different tag specifications.

foo_musicbrainz

Reply #238 –
Quote from: marc2003 on
Since I forgot to say it in my last post, thanks for the making the component. I like the consistency it offers compared to picard when handling files with different tag specifications.

You're most welcome!

foo_musicbrainz

Reply #239 –
I've updated the component to 0.3.1 using the build provided by lvqcl.

foo_musicbrainz

Reply #240 –
If anyone is interested, I've made some minor tweaks to the main dialog. I've added country to the date column and increased the height a tiny bit just so we can see 12 tracks without a scrollbar.



https://github.com/19379/foo_musicbrainz/releases

The changes can be viewed in this commit: https://github.com/19379/foo_musicbrainz/co...3a13b48a80eb5a6

At least Windows Vista and foobar2000 v1.3 is required. I've bumped the version to 0.3.2.

foo_musicbrainz

Reply #241 –
I've tried compiling this with VS2015 Update 1 to support Windows XP but for some reason the date and first release date aren't showing??

)

date (doesn't work with XP)
Code: [Select]
uSetWindowText(date, static_cast<pfc::string8>(release->get_date()));


album (works with XP)
Code: [Select]
uSetWindowText(album, release->get_title());


Any ideas??



foo_musicbrainz

Reply #242 –
Quote from: marc2003 on
I've tried compiling this with VS2015 Update 1 to support Windows XP but for some reason the date and first release date aren't showing??

Any ideas??


Compiled with VS2010 it works fine in XP / win10.
https://www.dropbox.com/s/njjm8zzhjuka1yr/f...brainz.dll?dl=0

I can't though help you why it doesn't in VS2015.
I'm a complete beginner .   

foo_musicbrainz

Reply #243 –
Quote from: Rarn on
I believe this plugin is writing MusicBrainz IDs to the incorrect tags. At the very least it is writing them differently than Picard, and I believe Picard is the reference standard.


The full tag mappings are here:
http://musicbrainz.org/doc/MusicBrainz_Picard/Tags/Mapping

As you can see, Picard tags Album ID in ID3v2.3 in "TXXX:MusicBrainz Album Id"
However, foo_musicbrainz tags Album ID to MUSICBRAINZ_ALBUMID

this also occurs with Artist IDs (though not Track IDs strangely)


This can be tested easily by tagging an album in foobar first with foo_musicbrainz, and then tagging the album again in Picard (make sure to not have it delete all prior tags before writing). You'll have redundant tags, with both "MUSICBRAINZ ALBUM ID" and "MUSICBRAINZ_ALBUMID" populated with the same data.

I'm not sure which is correct, but I would lean toward Picard. Regardless they should be doing the same thing.

What should I do if I want to adhere to musicbrainz standards?


I have just noticed this too, all the tags are mapped differently, and I'm not sure if or how this affects other software that reads MusicBrainz tags, such as Beets. I suspect the fix [assuming the fb2k plugin is incorrectly mapping the tags] is to make a fb2k masstagger script. For example, to remap the MUSICBRAINZ_ALBUMID tag:

Format value from other fields where destination field name is MUSICBRAINZ ALBUM ID, and the formatting pattern is %MUSICBRAINZ_ALBUMDID%. Then add another action to the script to remove the MUSICBRAINZ_ALBUMID field. I would repeat the same thing in the same script for each tag, and attach the masstagger script to a keyboard shortcut. At least that would make remapping the MusicBrainz tags painless.

foo_musicbrainz

Reply #244 –
Quote from: metal_termite on
I have just noticed this too, all the tags are mapped differently, and I'm not sure if or how this affects other software that reads MusicBrainz tags, such as Beets. I suspect the fix [assuming the fb2k plugin is incorrectly mapping the tags] is to make a fb2k masstagger script. For example, to remap the MUSICBRAINZ_ALBUMID tag:

Format value from other fields where destination field name is MUSICBRAINZ ALBUM ID, and the formatting pattern is %MUSICBRAINZ_ALBUMDID%. Then add another action to the script to remove the MUSICBRAINZ_ALBUMID field. I would repeat the same thing in the same script for each tag, and attach the masstagger script to a keyboard shortcut. At least that would make remapping the MusicBrainz tags painless.

This is by design. I've used names from the “Internal name” column from Picard documentation.
Picard establishes mappings between these internal names (what is shown to the user in Picard) and how the tags are actually stored. The names of stored tags are dependant on the tag format — for instance, musicbrainz_trackid is stored as TXXX:MusicBrainz Release Track Id in id3 and as MusicBrainz/Release Track Id in Windows Media. Unfortunately, it's impossible to override these mappings in foobar2000. That is, if you open a Picard-tagged file in foobar2000, you'll see different tags depending on the tag format. In case of ID3, foobar2000 will display TXXX:MusicBrainz Album Id as MusicBrainz Album Id (because it's not aware that it should be called musicbrainz_albumid), but in case of APE it will show MUSICBRAINZ_ALBUMID as it is. This is not helpful for titleformat scripts. Even worse, certain tags won't even be readable in fb2k, such as (I believe) UFID:http://musicbrainz.org in ID3.

Re: foo_musicbrainz

Reply #246 –
Why is it that I get the error message 'MusicBrainz Server is busy, try again later' about 85% of the times I try to use the tagger?
If I keep on trying over and over again and again on the same album, eventually, it will work in the end (I did this just to test), but surely it isn't meant to be this bad?  If I try with Picard, it hits dead on 99% of the time, but I find FB2k preferable for many other reasons.
I have a feeling the script is not tuned properly or something? At least, the error message is not accurate as the MusicBrainz server definitely is not that busy - always.

Ideas anyone?

Re: foo_musicbrainz

Reply #247 –
Quote from: oyvindo on
At least, the error message is not accurate as the MusicBrainz server definitely is not that busy - always.

What makes you think so? The plugin uses MB API which might have its own level of service, including "busy 85% of time" for particular requests. You can't know for sure the problem is solely at the client side.

It might be, however, that API usage pattern employed by the plugin is suboptimal. This can lead to the situation when requests are dropped by the server.

Re: foo_musicbrainz

Reply #248 –
Quote from: innou on
What makes you think so? The plugin uses MB API which might have its own level of service, including "busy 85% of time" for particular requests. You can't know for sure the problem is solely at the client side.
I agree, I can't know for sure. The reason I said that, is because if I turn to Picard, I almost never ever get a server busy error, while in Foobar I get this most of the time. Doesn't that lead you to think the problem is on the client side?

Re: foo_musicbrainz

Reply #249 –
When using this "tagger", I discover that most of the time the field "Album Artist" is deleted (or filled with "nothing"). In addition, leading zeroes in the track numbers are stripped. This is annoying, cause it takes too much effort to edit and correct these things after tagging. Is this behaviour a client side effect, or is it because all fields are filled with whatever it finds at MB? (regardless of whether a tag that already holds data is overwritten with nothing (deleted)?
Is there a way to modify/configure this whithout having to modify the actual code of the plugin by me (as I am no programmer)?