MétaCan
Menu
Back to cohort
Record W2064244293 · doi:10.1117/12.586888

MPEG-4 constant-quality constant-bit-rate controls

2005· article· de· W2064244293 on OpenAlex
Cheng-Yu Pai, William E. Lynch

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueProceedings of SPIE, the International Society for Optical Engineering/Proceedings of SPIE · 2005
Typearticle
Languagede
FieldComputer Science
TopicVideo Coding and Compression Technologies
Canadian institutionsConcordia University
Fundersnot available
KeywordsComputer scienceConstant bitrateBitstreamVideo qualityAlgorithmViterbi algorithmComputational complexity theoryBit rateReal-time computingDecoding methodsVariable bitrate

Abstract

fetched live from OpenAlex

Most video rate-control research emphasizes constant bit-rate (CBR) applications. These aim to produce a CBR bitstream with the highest possible quality, within the bitrate constraint and with no consideration for quality variation. In this paper, two MPEG-4 Constant-Quality (CQ) CBR controls are proposed. These aim to produce a CBR bitstream that meets a target quality level whenever possible. The Frame-level Laplacian CQ (FLCQ) algorithm uses a distortion model based on a Laplacian model for DCT coefficients. In contrast, the MB-level Viterbi CQ (MVCQ) algorithm uses the Viterbi algorithm to determine the best combination of MB-QP’s. “CQ” is measured by the deviation of the mean quality from the target quality, and by quality variance over time. Simulation results suggest that the proposed algorithms perform better than Q2 and TM5 under these measures. In some cases, they produce bitstreams with fewer bits while having higher average PSNR, and smaller variance. The FLCQ algorithm has more variation in quality than the MVCQ algorithm. With extra computational complexity, the MVCQ algorithm gives the best performance over all algorithms tested. Often, it precisely meets the target PSNR with no variation. This is truly a CQ rate-control algorithm.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.647
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.002
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0000.001
Science and technology studies0.0000.001
Scholarly communication0.0010.001
Open science0.0040.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.020
GPT teacher head0.256
Teacher spread0.236 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it