PerfectMeta: Meta-Data Formating Suggestions

[Porcus]

Re: PerfectMeta: Meta-Data Formating Suggestions

Ex:

5446 Thats My Number / Ball and Chain
vs
5446 Thats My Number/Ball and Chain

Also, what about & and +, which I presume might be used for two-releases-on-one-CD?

[Porcus]

Re: PerfectMeta: Meta-Data Formating Suggestions

Just to avoid double posting the entire content from http://forum.dbpoweramp.com/showpost...31&postcount=2:
If one (or more) sources are already given priority for a majority of the field, weigh their votes heavier for the rest.

[EliC]

Re: PerfectMeta: Meta-Data Formating Suggestions

Ex:

5446 Thats My Number / Ball and Chain
vs
5446 Thats My Number/Ball and Chain

There should be an option to ignore spaces on either side of "/" when deciding if meta-data is a match
There should also be an option to decide to prefer xxx / xxx over xxx/xxx



There should also be an option to ignore all spacing when deciding if text matches between sources.

[EliC]

I would like to make this a thread for suggestions / options that would improve PerfectMeta.

-Treat GD3 "[***]" as "(***)" when comparing meta-data. So " [Solo] " from GD3 should be treated the same as " (Solo) " from MusicBrainz or freeDB when comparing to see if there is a match. This is especially important as AMG does not seem to include data from discs in "(***)".

-Option to threat ***/*** as *** / *** when comparing meta-data

-Option to prefer *** / ***