Walk through the full GSDF calibration workflow with PerfectLum and a SmartSensor — from baseline measurement to signed conformance report.
What you will need
- A calibrated workstation
- A supported colorimeter (X-Rite, Calibrite, Datacolor, or QUBYX SmartSensor)
- QUBYX software installed and licensed
Step 1 — Baseline measurement
Take a baseline reading of the current display state before applying any calibration. Note ambient luminance and ambient reflection.
Step 2 — Apply the target
Pick the smart preset or custom target appropriate for the workflow. Apply calibration. Allow display warm-up if needed.
Step 3 — Verify and document
Run a verification pass against the applied target. Generate a PDF report. Archive with project metadata.
This guide will be expanded as we collect feedback. Tell us what is missing.
Premium consumer hardware usually ships with thin return policies. We chose to do the opposite with SmartSensor S2: 30 days, no questions, free return shipping.
What the policy forces us to be
A real 30-day return policy is a forcing function. Every sensor that leaves our calibration line has to be good enough that the customer keeps it. Every documentation page has to be clear enough that setup happens without a support ticket. The packaging has to be premium enough that returning feels like a step backward.
What we built to back it up
- Each S2 individually calibrated against a master reference before shipping
- Calibration certificate with measured deviation included in the box
- Quick-start designed to get you measuring in under five minutes
- Native software support across PerfectLum, PerfectChroma, PerfectEPD, and RemoteQA
QUBYX today announced the successful completion of its second consecutive SOC 2 Type II audit, conducted by an independent third-party auditor. The audit confirms QUBYX’s controls across the Trust Services Criteria including security, availability, and confidentiality.
“SOC 2 Type II is a baseline expectation from our hospital, defense, and enterprise customers,” said the QUBYX security team. “Sustaining it year after year is what matters — not the first audit.”
Customers under NDA can request the full SOC 2 report from security@qubyx.com.
Studios often ask which monitor they should upgrade to next. Almost always, the better answer is: calibrate the ones you have, and put it on a schedule.
Why uncalibrated premium monitors lose to calibrated mid-range
A premium reference display that has not been calibrated in eighteen months will under-perform a mid-range monitor calibrated last week. Display panels drift. The bigger the panel and the higher the original spec, the more visible the drift, because the user has higher expectations.
What we recommend
- Calibrate every color-critical display monthly minimum
- Verify weekly with a quick Delta-E pass against your target
- Document with a PDF that gets archived with the project
- Use the same target across editor, colorist, and AD stations
QUBYX today released PerfectChroma 6.2 with native 3D LUT export designed to drop directly into DaVinci Resolve, Premiere Pro, and Final Cut Pro timelines.
“Colorists asked for LUTs that work without a conversion step,” the product team noted. “6.2 generates them in the format each NLE expects, with the calibration target baked in.”
The update is free for Pro Bundle and Studio customers and ships through the in-app update channel.
How PerfectLum/EPD/Chroma sign reports, embed measurement metadata, and survive long-term archival.
Context
This technical note is intended for integrators, engineering teams, and customers who want to understand the implementation underneath QUBYX products.
Technical detail
We work through the relevant data model, measurement pipeline, and verification steps. Where helpful, we point to existing standards and our deviations from them.
References
- Internal engineering note
- Public standard documentation
- QUBYX SDK reference
For deeper integration questions, contact engineering@qubyx.com.
Major PerfectChroma release adding native NLE LUT export pipelines and expanded creative workflow support.
- 3D LUT export tuned per-NLE (DaVinci Resolve, Premiere Pro, Final Cut Pro)
- Smart Presets expanded with HDR10 and Dolby Vision targets
- Test Pattern Generator integration: jump straight from preset to test pattern
- Multi-monitor calibration session: calibrate Editor + Colorist + AD displays in one pass
- History journal now exports as JSON for ingestion into asset management systems
CIE76 vs CIE94 vs CIEDE2000 vs CIEDE2000 graphic arts — what each measures and when it matters for verification.
Context
This technical note is intended for integrators, engineering teams, and customers who want to understand the implementation underneath QUBYX products.
Technical detail
We work through the relevant data model, measurement pipeline, and verification steps. Where helpful, we point to existing standards and our deviations from them.
References
- Internal engineering note
- Public standard documentation
- QUBYX SDK reference
For deeper integration questions, contact engineering@qubyx.com.
Display QA at one workstation is straightforward. Display QA at scale needs structure. RemoteQA uses a four-level hierarchy that mirrors how organizations actually work.
The four levels
- Facility — a physical site. A hospital, an imaging center, an analyst building.
- Workgroup — a logical team within a facility. Radiology, mammography, GEOINT analyst pool, post-production suite.
- Workstation — a single seat. One desk, one or more displays, one operator role.
- Display — an individual screen with a unique serial.
Why the structure matters
Policy lives at the level it should. Mammography needs higher luminance targets than general radiology — that is a workgroup policy, not a facility policy. Air-gapped briefing rooms need different scheduling than internet-facing analyst pools — that is also workgroup-level. Each layer overrides the layer above without losing the inheritance.
How the S1 OEM module exposes calibration and measurement registers, with read/write examples.
Context
This technical note is intended for integrators, engineering teams, and customers who want to understand the implementation underneath QUBYX products.
Technical detail
We work through the relevant data model, measurement pipeline, and verification steps. Where helpful, we point to existing standards and our deviations from them.
References
- Internal engineering note
- Public standard documentation
- QUBYX SDK reference
For deeper integration questions, contact engineering@qubyx.com.