I’d suggest Roon support using the user-specified delimiter for multiple personnel&role entries. I would use the current new-line delimiter, but my tagger of choice, Metadatics, doesn’t accept multiline entries. (I tried my semicolon delimiter on a one-line entry without success). Yes, multiple PERSONNEL tags are possible, but why put me through that? After all, multiple ARTISTs are supported.
Second, I don’t get the need for an approved list of PERSONNEL duties (except I suppose for Roon to know where to put them on the credit list). But if you must, then include an area to enter PERSONNEL tags within Roon and offer an error checking routine to flag incorrect roles.
Third, I’d really like it revealed how related personnel tags (and others) are handled (i.e. what maps to where etal), rather than the current try-it-and-see method. I know it’s complex but it’s not too complicated. One spreadsheet-like reference sheet and you’re done. Bury it somewhere where only true nerds with no other life can find it. (I did see a version in the KB but it wasn’t in print form).
Wait a sec. All I said was to support the user delimiter that Roon asks for. It is Roon that displays two or more artists entered on one line with a semicolon (my delimiter). I’m merely suggesting that Roon also display two or more personnel entered on one tag with a semicolon. Parallel treatment.
Right now, personnel can be entered one per tag, or multiple per tag separated by the new line delimiter. That’s what Roon can interpret now. I’m suggesting it also interpret multiple personnel separated by the user-set delimiter.
But I can stand down if it’s controversial. Its not a hill I want to die on.
I get what you’re saying, and agree there’s a consistency change needed Roon side also. Having said that, delimiters like ; should strictly speaking only be written to mp3 tags because VorbisComments (which is what is used in the FLAC file specification) allows for multiple entries for the same tag name. So whilst the tagger enables capture as x;y;z, it should write out 3 entries for FLAC files.
As an example in puddletag, whilst multiple entries are displayed and can be captured in puddletag using a delimiter:
This is what puddletag saves to the underlying file:
Maybe we’re talking two sides of the same coin. Metadatics doesn’t explicitly show what it writes to the file. But Roon and it communicate well when a) a different Composer is entered three times; b) three Composers are entered once separated by semicolons; and c) three Composers are entered once separated by the new line delimiter (CTRL Enter).
In all three cases, the Roon interpretation is something like this:
Just to complete the experiment, I EXPORTED the album to the outside world, and opened that copy with Metadatics. Here’s there display of the tags:
I still can’t confirm where the translation to three composers is taking place, but Metadatics and Roon do it well. Meta correctly SHOWS multiple values, and Roon correctly interprets it.
So my sole desire was parallel treatment of tags. If this:
COMPOSER=Susan Anthony;Thomas Jefferson;Johann S Bach
works (and it does), then so too should this:
PERSONNEL=Susan Smith - Flute;Tom Thumb - Bass; Tim Smith - Drums
Agreed. For teh PERSONNEL tag, does Roon correctly interpret/ show PERSONNEL=Susan Smith - Flute;Tom Thumb - Bass; Tim Smith - Drums if you enter if entered once separated by the new line delimiter (CTRL Enter) or not under any circumstances?
Thx, I suspect that pretty much also means Metadatics is writing the entry as a literal and only writing multiple entries if you force the new line delimiter. If there’s no config option in Metadatics to write multiple entries by default, with or without the new line delimiter I’d request an enhancement that side too.
If I recall correctly Puddletag writes multiple entries by default but includes a function to consolidate multiple entries into a single delimited entry should you want to. The versatility is handy.
I’m toying with the idea of having Puddletag refactored and made Python 3.5 compliant. If I go ahead with it it’ll run on OSX, possibly still does now.
