◎ Radiance Export QC Report

Radiance QC Pro gives you a structured report as a string on the canvas. That's great for reading on screen and useless the moment you need to archive a delivery or hand a shot record to a review tool. ◎ Radiance Export QC Report is the tiny node that closes that loop: one wire in, real files on disk.

It's a deliberately boring node, and that's the compliment. You don't configure it so much as point it. It takes the JSON report that QC Pro emits, timestamps it, writes it to disk in whatever format your pipeline wants, and tells you where it went.

How it works

Wire qc_report_json from Radiance QC Pro's JSON output into this node. It parses that string, builds a filename from your filename_prefix plus a %Y%m%d_%H%M%S timestamp, and writes the file(s) to the output directory. The CSV export is a flattened frame-by-frame table (frame number, status, crushed %, clipped %, gamut %, banding %) - which is exactly the shape a spreadsheet or a review sheet wants. The HTML export is a self-contained page with a styled pass/fail table, handy for emailing to someone who isn't going to open a JSON file on a good day.

Behind the scenes the path is run through a safe-join helper that validates the output directory, so you can't silently write outside the intended area - a small but real relief if you're driving this from a shared box.

The inputs that matter

• qc_report_json - required, and it's forced as an input socket, so it has to come from another node (like Radiance QC Pro). You won't type this by hand.
• output_path - where files land. Empty uses ComfyUI's default output folder; set an absolute path to point at a delivery directory.
• filename_prefix - base name (default qc_report); the timestamp is appended so nothing gets overwritten.
• export_format - json, csv, html, or all for the kitchen sink.

The single output, export_status, is a string like ✓ Exported 3 file(s): followed by the full paths - which is also your debugging tool: if the write fails (bad path, permissions), the status string carries the error instead of the run silently dying.

How to install it

It's part of the radiance pack - install the pack and you get both QC nodes. ComfyUI Manager: search "Radiance". Or:

cd ComfyUI/custom_nodes
git clone https://github.com/fxtdstudios/radiance.git
cd radiance
pip install -r requirements_windows.txt

Restart ComfyUI. You'll find it in the FXTD Studios/Radiance/Analyze menu next to QC Pro. No extra models, no API keys - this node is pure file I/O.

Common issues

The most common "problem" is really a placement issue: you must wire the JSON output, not the text output, from QC Pro - they're both strings, so it's an easy mix-up if you're tabbing through sockets. Second: if you set output_path to something the ComfyUI process can't write, you get the error back in export_status rather than a crash, which is good but means you should read that output. And remember this node doesn't re-analyze anything - it's only as good as the report you feed it, so keep QC Pro's thresholds honest.

For a one-off sanity check you genuinely don't need this node. The moment you start keeping per-shot QC records, it's the difference between screenshots and a searchable archive.