Feature request: Optional tag delimiters

[simoncn]

(07-08-2013 20:34)AMP Wrote:  I understand that in order for Minimserver to interpret tags with multiple values that those tags have to be repeated in the file rather than entered with a delimiter character. I understand the reasoning for this... but...

Would it be possible in a future version to have a configuration option for a specific delimiter to be interpreted for a specific tag field?

Here's why... I'm an audio dealer and use USB-connected playback devices just about as much as UPnP devices. For USB I'm using JRiver (or Audirvana) for playback and I also use JRiver to manage my library and keep metadata up-to-date. Some of the features of JRiver make the tagging process very easy and the majority of my customers are happy with this solution.

Unfortunately, when a database field in JRiver is setup for multiple values it writes the tag to the file as a semi-colon-deliminated string into one tag entry. Furthermore, JRiver doesn't interpret multiple instances of the same tag in a file (so re-tagging with mp3tag won't work either).

In my case I make extensive use of the 'Soloists' tag in JRiver for my classical library, but Minimserver can't properly interpret the Soloist tags for which multiple soloists have been entered.

Although I understand that a delimiter isn't the "proper" way to tag the files it has become an unfortunate default for a lot of software packages.

Would it be possible to add an option which would allow one to specify that for a certain tag (say Soloists) Minimserver should interpret a specific character as a field delimiter and build its cache accordingly?

I undertand the reason for this request. However, the standards are very clear on this point and MinimServer is complying with the standards. If JRiver is not complying with the standards, this is a bug in JRiver that JRiver should fix. I don't think MinimServer should provide an option to "do the wrong thing" just because others are also "doing the wrong thing".

Can you be more specific about which type of file tag with multiple values is not interpreted correctly by JRiver? For example, are these:

Vorbis comment tags in a FLAC file
iTunes tags in an MP4 or M4A file
ID3v2 tags in an MP3 or AIFF file (and if so, is this ID3v2.3 or ID3v2.4?)