Feature request: Optional tag delimiters

[simoncn]

(07-08-2013 22:04)AMP Wrote:  As far as I know it's not that JRiver is interpreting any specific tag type incorrectly as the issue appears to impact any format. From what I understand JRiver indexes the first instance of any given tag and ignores any others.

I tried this by using JRiver MC 18 to import a local FLAC file that has multiple Artist tags. JRiver imported both tags correctly and shows the artists with a semicolon delimiter. The semicolon seems to be JRiver's visual indication that there are multiple tag values for the same tag name.

Quote:JRiver (similar to iTunes in this regard) builds a database out of the file tags and then uses the database for its functionality. A user can add database fields to meet his needs and in doing so has options as to the name and structure of those fields. Most common fields are strings and are interpreted as a blob of text regardless of content. For tags which store multiple unique values the structure is set as a "list" in which the content is a group of strings delimitated by semi-colons. The user has the option, for each database field, of maintaining that information solely in the database or writing it out to the files as well. In the case of lists JRiver writes them out as a single tag with items delimitated by semi-colons.

I tried this as well. The updated artist values were both written correctly to the FLAC file. They were written as separate tags, not as a single tag with a semicolon delimiter.

Based on these tests, it appears that JRiver and MinimServer are fully interoperable without any need for a change to either JRiver or MinimServer.