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: MusicBrainz64 (Read 12141 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: MusicBrainz64

Reply #25 –
It's interesting. Since the first time I ripped a music CD a long time ago, the album artist tag field has always been filled in, so I thought it was natural.
Really interesting, I was missing something very basic  :))
I will update to 2.4
Thank you very much

Re: MusicBrainz64

Reply #26 –
Now that this is 32-bit I get to use it, so cheers for that.

I had 'Write standard tags' unchecked and 'Always write ORIGINAL RELEASE DATE' unchecked, but it was still written because I guess it differed from the DATE as mentioned in the change log, even though DATE (standard tags) is not written. That seems not right. Both were greyed out in the preview.

Performer (Instrument) tagging is neat. Now to decide what to do with it ... ;D

Re: MusicBrainz64

Reply #27 –
Yeah, I guess that is a bug. I'll post again when I've fixed it.

Re: MusicBrainz64

Reply #29 –
Quote from: anamorphic on
Performer (Instrument) tagging is neat. Now to decide what to do with it ... ;D

If you ever want to display them in layout, the Properties + Other Info script with JScript Panel3 does a better job than other components by displaying multi-value tags on their own lines.

Re: MusicBrainz64

Reply #32 –
It gives me an error when installing

Nevermind. I had 2.5 and missed that you bump minimum requirements to foobar2000 2.24 and Windows 10 in 2.6
Changing wine to emulate windows 10 and all fine

Re: MusicBrainz64

Reply #33 –
Urgh, seems like musicbrainz have changed their output since I last did some serious tagging. performer values are getting polluted with attributes like guest or additional without a type which is useless. It needs to be guest something. It seems I need to combine them myself. :/

I'll try and get a fix out later.

Re: MusicBrainz64

Reply #34 –
Scratch the above, it's more likely I was doing things wrong.

2.8 should fix this...

https://github.com/marc2k3/marc2k3/releases

I can only apologise for any inconvenience caused by duff PERFORMER values being written previously. You can inspect using refacets with a %<performer>% column and then searching for guest or additional

Re: MusicBrainz64

Reply #35 –
When using your application, I encountered such a problem - I download tracks from streaming services, and often the tags are filled in correctly, but for example, the song register does not match, so I have to change

So - if you put all the checkboxes, then the necessary fields are replaced, you don't want to go into the settings every time, it would be a good addition to put them in front of the standard tags "MUSICBRAINZ_" as it is implemented in yandex.discogs, then I would be able to configure it more flexibly with filters, search and sorting.

you need a window for flexible settings and displaying all the information entered into the tags, with the ability to edit on the fly.
 

Re: MusicBrainz64

Reply #36 –
You should be looking at Picard for that type of stuff. I have no interest in any of it.