MediaMonkey forum

dtsig wrote: I have searched the id3 group and have not found a specific definition saying that it has to be semi-colon. I probably just missed it. I will continue looking for it though.

Thanks

That's because it isn't semi-colon, that's just a visual representation of the actual separator, which is a slash.

The problem you run into when you define your own splitter prior to import is that it can make strange things happen when you have files from multiple sources, all potentially using different splitters. I think sticking to a standard, or de-facto standard, is still the best practice.

dtsig wrote:Scott967 thanks for that. It is always great to get peoples opinions on things.
I have still not found anything specific at the id3 site saying on way or another ... and it really shouldn't matter there as again I am not talking about writing to the tag .. but how it is generated to the DB and how MM then displays.

But i guess i will just have to get used to it not working as it appears to have been designed (per image). The genre listing does look a little odd as


thanks a lot

I don't think MM uses any "separator" within the database. The separator that you select in the options is used when entering data into the "properties" page of an item, and in displaying the library contents in the details pane. If the separator appears within the ID3 TCON frame (for media files using ID3v2), MM when scanning the media file will interpret that as a separator and make entries for each genre. As I wrote before, MM will write the ID3 TCON tag using the separator as well. I think you will find that MM will not interpret \\ as a separator within TCON. You can verify this with a hex editor. I think \\ is used as a separator in wma, don't know if that includes genre but I never use wma so can't give any more detail on that. \\ is also used in mp3tag.

scott s.
.

I been wondering if this would be handled the same way as data in the custom fields,?
And in those i find the only thing that seperates words is a blank space if i use the ( , ) it is connected to the word and that changes what mm is to look for by doing the adding. It makes rock in to rock, and that is not the genere or correct word since mm is looking for rock it ignores the word with the ( , ) in the spelling.

In doing the different words in custom tags and keeping them different i find that even a blank space then ( , ) and the word is not working as it again is attached to the word it leads, so only a blank space is useable to seperate words, if this is how you get it working in mm great. but if this works in other programs i dont know because i use mm.

I use the (;) delimiter setting.

Sometimes my genres appear without a delimiter.
For example: HardRock Heavy BluesRock LiveConcert.
In my Genres tree node it is incorrectly listed as HardRock Heavy BluesRock LiveConcert.

To correct this I simply insert (;).

For example: HardRock; Heavy; BluesRock; LiveConcert

Hope that helps.

Thanks everybody for any/all information.

First .. it has nothing to do with // or NULL or anything. I have searched and searched the ID3.org pages and have only found a small reference to it but nothing that states that it is a requirement. It is called a text field.

It appears from all tests that MM automatically *knows* that a semi-colon (;) is THE muli-part delimiter. In genre, artists etc MM will automatically split, index and display individual information.

I tried using the "Tools->Options->Appearance->Split Multiple-value fields with:" option to make MM use a comma (,) instead of the default semi-colon (;) but no matter how many restarts it simply ignored it.

So using a great tool add-on, RegExp Find and Replace (found here http://www.mediamonkey.com/forum/viewtopic.php?t=28510 ). Using this I converted all commas to semi-colons in my 10.3K albums/150K songs AFTER a disc image for backup. This add-on saved me years of work.

So even though I never did get a response from my 'bug report' i posted .. heck even became a gold member to get a response .. the help here was pretty good and pointed me in the direction i needed.

Thanks everyone again

dtsig wrote:I tried using the "Tools->Options->Appearance->Split Multiple-value fields with:" option to make MM use a comma (,) instead of the default semi-colon (;) but no matter how many restarts it simply ignored it.

I wonder if making a tagging changes (or merely have MM write the tags again to the file) would have worked in this scenario.

I *think* i tried making a genre change when set to comma and nothing happenend but will try that again tonight to be sure i have the right information here.

Thanks

dtsig wrote:Thanks everybody for any/all information.

First .. it has nothing to do with // or NULL or anything. I have searched and searched the ID3.org pages and have only found a small reference to it but nothing that states that it is a requirement.

I believe that // is not an id3 standard but something that Windows Media Player introduced and it has become a "de-facto" standard.