Jump to content

FFprobe Has Improved Awareness for Multivalue Audio tags


Recommended Posts

ginjaninja
Posted (edited)

https://trac.ffmpeg.org/ticket/3125#comment:3

 

@@Luke

Hi Luke,

Last year i couldnt work out why my multivalue tags were never seen by MB3.

such as artist =

ABBA1 and

ABBA2 and

ABBA3

 

such as album artist =

AA1 and

AA2 and

AA3

 

Turned out that there were two ways clients could write multivalue tags

1. A long string with a separator

2. True Multi Value Tags (as seen by as hex editor) (eg. accomplished by using \\ separator in mp3tag)

 

Turned out ffprobe could only see type 1 properly, not type 2.

earlier versions of ffprobe only output the last multivalue tag for type 2.

Type 1 was fine and MB3 would separate ffprobes output.

 

old FFprobe output with type 2

ARTIST          : ABBA3    GENRE           : Greatest Blues - Golden Greats Disc 1    album_artist    : AA3
latest version of FFrobe, handles type 2 and shows the following output
ARTIST          : ABBA;ABBA2;ABBA3    GENRE           : Greatest Blues - Golden Greats Disc 1    album_artist    : AA1;AA2;AA3
Anyways for people with multivalue 'Type 2' tags, you can expect that ffprobe and MB3 will support. (checked with artist, albumartist and genre tag and mp3tag)

given MB3 parses ffrobe output and supports ';' separator there is no issue.

But potentially this does pave the way for firming up multi value appreciation in MB3, as currently more artists are separated than should be e.g with ','s in name..

If all users were recommended to use 'actual' multivalue tags, this would prevent unwanted separation around ','s and '/', and the need for additional logic/remedial action to handle.

Edited by ginjaninja

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...