Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Instruction Guide Need some advice about Multiple Genres FLAC tags.
#1
Hi there! 

Thank you for receiving me, and thank you in advance for excuse my misspelling (rough english here).


I’m new to moode. 

I was dealing with volumio in the past, so I greatly appreciate the way moode loads a large library array on the browser. It’s just great!
Still having some issues with moode related to my own configuration, 

but the first thing I’ve faced is the Multiple Genre ‘thing’.

When moode populate the genres tags on library I’m getting the classic one-line-genre.

Genre1; Genre2; Genre3


I was reading old threads about the related issues, where @Tim Curtis , @TheOldPresbyope, @Atair  and @Nutul made a marvelous research.

So, I think I’m starting to undestand how it works, and how it has to be to work.


I have a nice collection of +10k albums, including FLAC and MP3 files.

The whole collection was made through years with a same folder/name/tag scheme.
Musicbrainz Picard was the used tool.



MP3s was tagged with ID3v2 2.3, and I’m starting to convert all those tags to 2.4.

I can forget about this ones for the moment.

But (testing the mp3-id3 convertion) noticed that FLAC files are showed in the same way.


Moode file info, Mediainfo and Kid3 display it as ; separated values. 

Genre1; Genre2


I’ve checked the frames are stored on vorbis comment metadata.

metaflac --list gives me every genre on their own separated frame. 

Code:

GENRE=Genre1

GENRE=Genre2




I’ve already rescanned the library, and then cleared the Library tag cache.


Is there something I’m missing? 
Some advice?
Are the GENRE caps messing with MDP interpretation, and I need to convert or retag the whole collection?

In that case: is there a way to update those uppercase tags without going the whole round of retag everything on picard?

Shy
Reply
#2
Sorry, I'm not sure I understand the problem we're supposed to comment on.

What is it you expect to happen (in terms of moOde usage) and what is it that does happen instead?

As an aside, what is the driving force in converting your MP3 collection from ID3v2.3 tags to ID3v2.4? 

Regards
Kent
Reply
#3
1. moOde shows the genres of a track like you see: separated by commas (or semicolons, I'm not at my desk now...). This is just for ease of visualization; they are indeed a set og genres, and not a single string...
2. just to check, enable the GENRES tab in the library (in the preferences) and if you see any line in it showing two ro more genres separated by commas / semicolon / etc. then you knoe that at least one track is mis-tagged in your library.
Reply
#4
I can't believe after a week of reading and testing things here and there, now asked and found the issue. 
As I said, this collection has years of building. Now I suspect that Picard do not managed tags in the same way over the years (even when I've used the same tagging/renaming script).

I just picked up a random track to show you what I called 'one-line-genre'.
[Image: M0thUPs.png]

Then, when I check that specific track on metaflac, I saw that described genres are all in the same frame! 
Code:
comment[14]: GENRE=2 Tone; Contemporary Pop/Rock; New Wave; Pop Music; Pop/Rock; Punk/New Wave; Reggae; Ska; Ska Revival; Synth-Popcomment[14]: GENRE=2 Tone; Contemporary Pop/Rock; New Wave; Pop Music; Pop/Rock; Punk/New Wave; Reggae; Ska; Ska Revival; Synth-Pop

So, I recreated the multiple tags manually and check it again... Its works as expected. Love it!
 

My bad Blush
My first assumption was that all my files has the same tags, just because how are displayed on Picard (just today started to check it via metaflac).
Btw, don't get frightened by that extreme folksonomy, not all albums has so much (although jazz and classical can be tricky). Now I'm thinking on a way to just mass rewrite the genre tags on older albums like that.

About MP3 files, and considering your question @TheOldPresbyope, that's maybe another false assumption I've made.
I was reading a conversation between the both of you, where you test it that MDP can correctly parse the ID3v2.4.
I remember to get that idea from there. Isn't needed?


It will be a long travel of learning to get it tidy, but every day it feels closer.
Thank you folks!
If any recommendation, I'm always grated.
Reply
#5
I don't care for MP3 files and have only a few MP3 tracks from old sources I never got around to replacing.

My problem with ID3v2 tagging is that various software apps and tools don't all treat the metadata in the same way and even widely used tools such as MP3tag and MusicBrainz Picard tend to hide the details from me.

Since you mentioned FLAC files, I should point out that the only metadata tagging scheme allowed in the FLAC documentation is the Vorbis Comment scheme. The separate Vorbis Comment documentation, in turn, says the tag field names (such as Track, Artist, Genre, etc.) are case insensitive.

Testing moOde 9.0.4 with my synthesized FLAC files shows that moOde/MPD are also insensitive to case as far as FLAC metadata fieldnames are concerned. Whether "Genre", "genre","GENRE"...makes no difference.

Regards,
Kent
Reply
#6
Oh, is great to know that moOde/MPD is insensitive to case.
I sorted out the MP3 tags with musibrainz picard, and corrected the bad formated FLAC ones.
Slow on undestanding, I noticed that moOde populate the genre tag (usually different on every track of an album) and not albumgenre. So I'm planning a complete rewrite of the genre tag in the whole collection.
Even reducing their number to 2 o 3 genres.
I need to find some tools for that, but it's all working like a charm!
I'm really happy!
Reply
#7
(07-27-2024, 02:21 AM)francoestrubia Wrote: I need to find some tools for that

I have used bliss for doing major surgery on my music collection.  I found it worked well, if slowly at times.  It isn't free but it's very good for making sure all your files follow the same rules.
----------------
Robert
Reply


Forum Jump: