Hi,

TheEmpathicEar wrote: ↑Fri Jul 07, 2023 6:31 pm I am still wondering what to use in MM5 for a delimiter for Genre(s)?

as pointed by Lowlander above, each tagging format have it sown way to save multiple genres and other multi tag data, sone uses // some NULL some actual multi values some ; and so on.

I have personally accepted ; as a common separator (mail clients use it, CSV use it also, ...)

It doesn't matter as it doesn't affect how it's saved to the tags. It only affects how it's displayed in MMW (and what you use to enter multiple values).

Peke wrote: ↑Fri Jul 07, 2023 4:56 pm Hi,
But some tag formats have specific standards how to write multi tags eg. ID3v2.3 MP3 TAGs had big issues with AC/DC when Multi artist standard was established. Problem is that still some hardware only partially support ID3v2.4 and that was the one of main reasons why only in MM5 ID3v2.4 was default format.

I am still wondering what to use in MM5 for a delimiter for Genre(s)?

Lowlander wrote: ↑Fri Jul 07, 2023 5:10 pm Hardware like MP3 players and such.

I have the S22+. Are some of these hardware changes "progressive"? IOW, improvements?

Hardware like MP3 players and such.

Peke wrote: ↑Fri Jul 07, 2023 4:56 pm Hi,
But some tag formats have specific standards how to write multi tags eg. ID3v2.3 MP3 TAGs had big issues with AC/DC when Multi artist standard was established. Problem is that still some hardware only partially support ID3v2.4 and that was the one of main reasons why only in MM5 ID3v2.4 was default format.

I think I understand the rationale for MM5. But, what does hardware have to do with it?

Hi,
But some tag formats have specific standards how to write multi tags eg. ID3v2.3 MP3 TAGs had big issues with AC/DC when Multi artist standard was established. Problem is that still some hardware only partially support ID3v2.4 and that was the one of main reasons why only in MM5 ID3v2.4 was default format.

I thought the delimiter for Genre(s) in MM5 was either a comma or semi-colon?

Hi again Lowlander,

Thanks for confirming what I thought. Whilst the interface uses the semi colon, the effect on the file itself would/should be the same as the double backslash.

dsmacdo wrote:MM by default uses the semi colon but can also be configured to use | under the options menu. As far as I know, Mp3Tag by default uses a double backslash.

As said what is shown and used in MediaMonkey isn't what is read and written with the files themselves. The double backslash is the delimiter used in ID3v2 (used in MP3s) and MediaMonkey also adheres to that.

Hi Funkeyro,

MM by default uses the semi colon but can also be configured to use | under the options menu. As far as I know, Mp3Tag by default uses a double backslash.

Please note that I am in no way an expert at all this stuff and realize that tagging can be quite problematic as multiple media players or devices support one format but not necessarily others. My impression is that MM "officially" supports ID3V2 natively and thus, I was hoping that it would also handle much of the standard as defined. MM handles multiple genre fields & values with flac tags and I would have thought, that it would behave similarly with ID3V2.

MM does seem to understand that the file contains multiple genre values but for whatever reason, inserts a non-visible character on the second and subsequent field. I had a look at both the Flac's frame and equivalent frame contained within the MP3 file using a hex editor, and from my perspective, there is no difference whatsoever. Foobar does not seem to have an issue with the MP3 as tagged either.

At the request of support, I just tried to synch the tag from within MM and it seems to not re-tag correctly either. Despite having used the semi colon delimiter within MM's GUI, the resulting tag "merged" the separate fields into one. IMHO, there is indeed an issue with how MM handles ID3v2.3 tags. I had previously sent support the file (which was originally tagged with MP3Tag) and from what I got as a response, the file itself is fine. Please understand this is not to dis MM but rather, I am simply trying to resolve what I consider a "bug".

I am tagging in Unicode. Would anyone know if MM expects ISO- 8859-1 tags rather than UTF-16?

Tools > Options > Appearance, by default it is ; Do note that this doesn't reflect how multi-value fields are saved to the tags, this depends on the tagging standard.

I have not noticed anyone identify the multi-value field separator. Doesn't MM require semi-colons? Several Tag editors, including MP3Tag, use a comma to separate the values. I believe that MM interprets this as a string, and then adds it to your field database ie.: "Crime, Mystery, Action" instead of recognizing 3 separate Genres ie.: "Crime" and "Mystery" and "Action". As you might guess, I work with a lot of .mp4 files as well as .mp3 files, and this drives me a little nuts.

Sorry for taking so long to respond and thanks for your input Scott.

Thankfully, most of my music collection is in Flac which does not suffer from the same "glitch". I have manually corrected all the entries within MM but it remains quite a pain just the same.

IMHO, this is MM related issue. The tag itself (ID3v2) seems fine when viewed in hex. Your take seems interesting but alas, I fear that my skill set is not up to par to completely pin it down. I will test what happens within Foobar with my MP3s again in order to be sure that it doesn't happen within it. In my view, that should help to determine whether this is an issue within MM's handling of the tag. That said, I had to rebuild my system due to a hardware change & I fear that I'm about to have to clean it all up again as my structure has changed and I'll have to create a new database.

Lowlander: I'll have a peak at the script you pointed out. Thanks again.

Doug