Tagger multiple genres problem
Posted: 06 Dec 2012 23:42
I am so confused because each software uses its own format for storing multiple genre tags.
I 've tested foobar, xmplay, mediamonkey, musicbee, mp3tag
I don't know finally which is the correct.
For example when I save "Alternative; Dance" in PF Tagger it is saved as :
(20)/(3)
MediaMonkey reads : "Alternative; /; Dance"
Foobar reads: "Alternative"
MusicBee reads: "Alternative; /(3)"
xmplay reads: "Alternative"
mp3tag reads: "Alternative"
When I save "Alternative; Dance" in foobar I read:
mediamonkey reads: "Alternative; Dance"
xmplay reads: "Alternative;Dance"
musicbee reads: "Alternative; Dance"
PF Tagger reads: "Alternative;Dance"
mp3tag reads: "Alternative; Dance"
Mediamonkey saves the same as foobar.
When I save "Alternative; Dance" in MusicBee I read:
mp3tag has 2 genre tags of "alternative" and "Dance"
MediaMonkey reads : "Alternative; Dance"
xmplay reads : "Alternative"
PF Tagger reads : "Alternative; Dance"
And so on...
Finally... is there any standard on writing multiple genres or every program uses it's own method ?
(is that / in PF a bug ?)
I 've tested foobar, xmplay, mediamonkey, musicbee, mp3tag
I don't know finally which is the correct.
For example when I save "Alternative; Dance" in PF Tagger it is saved as :
(20)/(3)
MediaMonkey reads : "Alternative; /; Dance"
Foobar reads: "Alternative"
MusicBee reads: "Alternative; /(3)"
xmplay reads: "Alternative"
mp3tag reads: "Alternative"
When I save "Alternative; Dance" in foobar I read:
mediamonkey reads: "Alternative; Dance"
xmplay reads: "Alternative;Dance"
musicbee reads: "Alternative; Dance"
PF Tagger reads: "Alternative;Dance"
mp3tag reads: "Alternative; Dance"
Mediamonkey saves the same as foobar.
When I save "Alternative; Dance" in MusicBee I read:
mp3tag has 2 genre tags of "alternative" and "Dance"
MediaMonkey reads : "Alternative; Dance"
xmplay reads : "Alternative"
PF Tagger reads : "Alternative; Dance"
And so on...
Finally... is there any standard on writing multiple genres or every program uses it's own method ?
(is that / in PF a bug ?)