CoreVQ technology
The engine behind the evidence
One native engine powers measurement, versioned scoring, and inspectable results in Studio and corevq. Explore its evidence and integration paths.
One measurement implementation
Studio and corevq share one native engine, configuration, models, and result contracts.
Details: One measurement implementation
Interactive and automated use
CoreVQ Studio and the bundled corevq CLI link the same native CoreVQEngine for common measurement, scoring, Full-Reference comparison, and result functionality. Stream startup probing is native CoreVQ functionality; Studio owns its interactive TTFF and transport-probe workflow, while the CLI provides its documented stream commands.
Suite provides media selection, previews, execution controls, and exports. Shared result fields can be compared under the same inputs and configuration; each interface also exposes fields specific to its workflow.
Measurements with execution context
The engine keeps results connected to the input, selected range, sampling, analyzed coverage, completion state, and warnings. Partial and incomplete results retain their status so downstream systems can decide whether the evidence is sufficient.
Scoring and evidence
Measurement values stay connected to confidence, coverage, execution state, and retained provenance.
Details: Scoring and evidence
Context for decoded-content quality
The perceptual pipeline combines normalized primary measurements, bounded supporting deductions, confidence, applicability, and a versioned video model. Scene pooling, transition handling, and motion context determine how observations contribute to a result.
Results that can be inspected and retained
CSV and JSON carry measurements, score context, configuration, and execution evidence. Structured JSON also identifies scoring, calibration, model, and export provenance. Full-Reference results record paired-frame coverage; stream results retain available startup components, decoded-frame cadence, and failures.
The versioned perceptual verification covers a specific score version, profiles, configuration, and test partitions. It does not validate every workflow, future SDK package, customer plugin, or deployment. The verification record states the tested scope and evidence identities.
CoreVQ technology and its foundations
CoreVQ combines its scoring and workflow layers with established metrics and third-party components.
Details: CoreVQ technology and its foundations
CoreVQ product layers
- CoreVQEngine integration and workflow execution.
- Perceptual score composition, normalization, profile behavior, scene handling, and evidence semantics.
- CoreVQ Studio, CLI automation, and versioned result exports.
- Package integration, configuration, and product documentation.
Established metrics and third-party components
CoreVQ uses established measurements including NIQE, BRISQUE, VMAF, PSNR, and SSIM, together with third-party code, models, and media runtime components. Their algorithms, materials, and license rights remain distinct from the CoreVQ product layers.
Exact component versions, licenses, model records, and dependency inventories accompany the qualified package. See third-party notices and package requirements.
Integration scope today and ahead
Use Suite for local analysis and automation, Services for customer-specific work, and the planned SDK for future embedding.
Details: Integration scope today and ahead
| Offering | Delivery scope | Integration path |
|---|---|---|
| Suite | Current desktop and CLI product; access and support depend on the qualified platform package. | Local analysis, internal automation, and exported results. Product embedding and redistribution require separate rights. |
| Services | Paid engagements with agreed deliverables and acceptance criteria. | Integration assessment, prototypes, specialized analysis, test automation, monitoring, and deployment work scoped to the customer's system. |
| SDK | Planned external integration product. | A supported native API and optional frame-analysis plugin contract. Released packages will define ABI, platforms, toolchains, deployment rights, and support. |
The internal engine used by Suite is not a released external SDK contract. CoreMF supplies a design baseline for planned plugins; binary compatibility and customer analyzers require explicit definition and qualification.
Published technical material
Continue the technical review
Review the versioned score evidence, Suite operating documentation, SDK interface scope, and third-party component boundaries directly.