Page 1 of 1

Change Multi-Value Separator

Posted: Tue May 16, 2023 9:21 pm
by YellowpowR
Hi everyone,

I've been using MediaMonkey for a while now, though I'm still not-well-versed in its intricacies, so apologies if this is obvious to some degree. I know to separate items in multiple-value fields I use the semicolon. But I was wondering how, if possible, I can change which mark is used to separate items. I've tried the option in Tools>Options>Library>Fields, but it doesn't seem to do anything. I'd like to find this out since it seems most metadata by default separates items with plain commas, and I wish I could just have that work in MediaMonkey too, instead of changing it to semicolons for each album.

Thanks in advance!

Re: Change Multi-Value Separator

Posted: Tue May 16, 2023 10:05 pm
by Lowlander
This setting is display only and doesn't affect how the tags are written to the files. Are you looking to display multi-values separated by , in MediaMonkey? If so, does changing that setting from ; to , not change how it's displayed in MediaMonkey for you?

Re: Change Multi-Value Separator

Posted: Wed May 17, 2023 12:33 pm
by YellowpowR
If that setting is only suppose to change things visually, then I don't think it's actually doing that either, since I'm still seeing semicolons visually.

But I was initially wondering if there was a way to separate artists and whatnot with commas in the metadata, as opposed to having to change it to semicolons for every single new album in MediaMonkey.

Re: Change Multi-Value Separator

Posted: Wed May 17, 2023 12:59 pm
by Lowlander
I am unable to reproduce, on change of separator in settings it immediately changed how it's displayed in MediaMonkey itself. Which Build (Help > About) of MediaMonkey are you using?

Re: Change Multi-Value Separator

Posted: Wed May 17, 2023 4:27 pm
by YellowpowR
I'm using 5.0.4. Actually, I just figured out that changing the separator in that option did indeed affect things. I just didn't notice initially, I see it affects the details when you enter its properties, for example, and in my organized playlists. The only place I don't see it changing, however, is when viewing soundtracks under Albums. Also, it doesn't seem to allow artists to actually be separated by commas (i.e. "[Artist 1], [Artist 2]" seems to be recognized as one artist still.) Although that problem doesn't seem to occur with the playlists I've already set up to have semicolons as a separator. So is all that option doing is make semicolons look like another symbol, like a text substitute, and not even all the time, only in select places?

Re: Change Multi-Value Separator

Posted: Wed May 17, 2023 5:58 pm
by Lowlander
It won't make multi-value out of fields that already used , prior to changing the setting to , However any newly tagged files should use , as separator.
YellowpowR wrote: Wed May 17, 2023 4:27 pmThe only place I don't see it changing, however, is when viewing soundtracks under Albums.
Is this an issue of , being used prior to the change, or ; not changing to , on change? A screenshot may help explain.

Re: Change Multi-Value Separator

Posted: Wed May 17, 2023 9:44 pm
by YellowpowR
Okay, I actually fixed the issue with the separator not changing, you were correct, I solved it by switching any commas to semicolons and then switching the separator over to a comma. So that's that part solved. You are saying, then, that any future fils with metadata including a comma will find that as the separator automatically?
Lowlander wrote: Wed May 17, 2023 5:58 pm Is this an issue of , being used prior to the change, or ; not changing to , on change?
It's an issue of the ; not changing to a ,.

Re: Change Multi-Value Separator

Posted: Wed May 17, 2023 10:15 pm
by Lowlander
YellowpowR wrote: Wed May 17, 2023 9:44 pm You are saying, then, that any future fils with metadata including a comma will find that as the separator automatically?
Any entries you make with , will become multi-value. Any files you import would need to be tagged according to the tagging standard for the file type.

A screenshot may help show the second issue.