verbosity attribute in MediaTrace

[dericed]

Some implementation checks require --ParseSpeed 1 or other verbose MediaTrace options, such as testing to make sure all Seek elements resolve (this fails on low verbosity mediatrace, since not all Clusters are noted).

I propose a verbose attribute to be added where ever the parser attribute is used, so in block, ref, and MediaTrace.

[JeromeMartinez]

I don't like we terms ParseSpeed(no real meaning) and verbosity(it is not about verbosity but how much data we check).

completeness="full", completeness="fast", completeness="medium"? (I don't like the idea of having numbers, is "1" full or fast and is "9" full or fast?)

[dericed]

you're right, i remember we debate this before. I was on the side of coverage

[JeromeMartinez]

ho, I forgot the debate.

coverage="full" (--ParseSpeed=1), coverage="fast" (--ParseSpeed=0), coverage="medium" (--ParseSpeed=0.5 and default)?

[dericed]

I suggest number with coverage with words as aliases to numbers.

[JeromeMartinez]

which number? which alias?

[JeromeMartinez]

I prefer something unique (number or text), having 2 methods for saying the same thing may be confusing.

[dericed]

Check the man page for the flac utility. There is something like this in the compression option.

[JeromeMartinez]

we talk of an XML output, so a parser will have to support both if we accept both. This is not similar to command line options