Feature request: Optional tag delimiters

[winxi]

(12-08-2013 16:10)simoncn Wrote:  

Quote:I've seen it mentioned elsewhere on this forum that your interpretation of the standard is that the NULL delimiter doesn't apply to TXXX frames, and having read the spec I can see that interpretation. Unfortunately, it would appear that few others are reading it that way and instead are creating multiple-entry TXXX frames using the null character. I've yet to find a program which will write a multiple-value tag out as multiple TXXX frames with the same descriptor.

Given that multiple TXXX strings with the same description aren't allowed, and the statement in the ID3v2.4 spec that the TXXX frame 'is intended for one-string text information concerning the audio file in a similar way to the other "T"-frames' (which do allow null separators), I think it's reasonable for MinimServer to treat null characters in ID3v2.4 TXXX tags as separators for multiple values.

Is this the reason that MinimServer currently indexes only the first value of a multi-value custom ID3v2.4 tag saved in Mp3tag?

[simoncn]

(31-08-2013 20:11)winxi Wrote:  Is this the reason that MinimServer currently indexes only the first value of a multi-value custom ID3v2.4 tag saved in Mp3tag?

If the custom tag is represented as an ID3v2.4 TXXX frame, this is the reason. I will fix this in the next release.

[winxi]

(01-09-2013 21:17)simoncn Wrote:  If the custom tag is represented as an ID3v2.4 TXXX frame, this is the reason. I will fix this in the next release.

Thanks! Good to know that this will change. Besides Mp3tag, the 'MusicBrainz Picard' tagger also seems to use null separators for multi-value ID32.4 TXXX frames.