Use the sheet below to reach the Measurement Desk. A technical question, a benchmark note or a
correction all land in the same mailbox, and a member of the desk answers each one.
Direct contact
Codec Lab Analytics — Measurement Desk
4180 Harborview Way, Suite 210, Seattle, WA 98109
+1 206-555-0119 · [email protected]
What to include
A useful note names the page, the clip class and the figure in question, and states what was
expected. A correction is easiest to act on when it points to the run note behind the figure.
How the desk handles a note
Every note arrives in one queue and is read in the order it lands. A note that names a page and
a figure is the easiest to act on, because the desk can open the run note behind that figure and
compare the two side by side. A note that describes a symptom without a page still gets an answer,
but the reply may open with a question rather than a finding.
Technical questions form the largest group. They usually concern a rate factor, a key frame
interval, a ten-bit path or the choice of engine for a given host. The desk answers each one from
published bench runs where it can, and says plainly when a question falls outside the recorded
set.
What a correction needs
A correction should name the page, the table or figure, and the reading that seems wrong. If the
note carries a counter-measurement, the desk will ask for the clip class, the rate mode and the
host class, so the two runs can be compared on equal terms. A correction that survives this check
triggers a dated revision on the page, and every page that relied on the old figure is revisited in
the same pass.
Response times
A technical question is usually answered within two working days. A correction takes longer,
because it is checked against the run note and then reviewed by a second operator before a page is
changed. An editorial request is scheduled against the current review cycle and answered with a
date.
Working with the desk on a bench question
If you want the desk to measure a specific clip class, say what the class is and why it matters.
Grain, motion, gradients and screen content each stress a different part of an encoder, and a
useful request names the stress rather than the codec. The desk will reply with the source class it
can reproduce and the figures it can report.