Troubleshooting and Operator¶
| Finding | Next useful action |
|---|---|
| No camera source | Select a detected device/mode, or Import Media; check the vendor driver and signal. |
| Input color undeclared | Confirm the actual camera curve/gamut/range/matrix, then apply Input Color. |
| Exposure | Revisit the opening slate and camera/input transform; lock exposure and take a new measurement. |
| Highlight clipping | Check camera/signal clipping; clipped pixels require a new recording. |
| Chart detection | Include the full central patch and chart; retry analysis with a suitable region. |
| Gray response | Check range, ramp and processor processing before calculating a correction. |
| Setup changed | Restore the saved settings or create a new run; stale results cannot authorize writes. |
| Missing result | Keep the sources; retry the affected job in a new job directory. |
| Approximation outside limits | Keep the numerical failure visible; reconsider the transform or use the more accurate route. |
| Unknown processor outcome | Read the recovery journal and prepare recovery; do not automatically retry. |
| Comparison rejected | Check the baseline link, separate new frames, readback, timestamps and unchanged camera settings. |
Ask Studio Operator¶
Open Operator or press Ctrl+K. Enter a question and choose Diagnose Local. Local diagnosis uses the current calibration step, declared settings, quality checks and available device/capture findings. It remains usable offline.
Exact commands such as “open results” can propose a bounded action. Run Action is separate. Editing the question or changing its context revokes the proposal. Asking for help never applies a processor correction or starts output.
Outside Demo, hosted assistance requires Studio sign-in and an explicit Ask Hosted action. Its confirmation explains the text diagnostics sent; camera images and recordings are not automatically uploaded. Hosted answers are advice and cannot execute tools. Live account/server acceptance remains unverified in this development build.
Keep the run, referenced captures, result manifests and deployment journal together when reporting a problem. Record the firmware, camera settings, capture mode and visible error, plus whether it happened in Demo or on hardware.