Karma Sequence QA: Logs, Missing Frames and Re-rendering Only What Failed
A finished job is not a finished sequence. What to check after a long Karma render:
- Logs: husk -V 2e for times; --error-summary and --enable-usd-errors in Houdini 22
- Gaps: list every expected frame and find the missing numbers
- Broken files: resume flags trust any file on disk, even a partial one
- Partials: time limits and snapshots can leave partial images; know your flags
- Fix: re-render only bad frames with husk --frame-list
A render job that reports success can still deliver a broken sequence: a frame that crashed and was skipped, a file written half way when a machine restarted, a partial image saved by a time limit, or a frame that rendered with a missing texture. Automatic resume makes this worse in one way: options like husk’s --skip-existing-frames and the TOPs Cache Mode treat any file on disk as done.
This guide shows what to read in the husk logs, which flags leave partial images behind, a small script that finds missing, empty and undersized frames, and how to re-render only the frames that failed.
Checked against the SideFX Houdini 22 documentation (husk, What’s new in Karma, USD Render TOP), November 2026.
A QA loop for every sequence
The checks are cheap compared with re-delivering a shot, and they follow the same loop every time:
Run the loop on the render machine while the project is still there; it is much faster than downloading a broken sequence and uploading the scene again.
Read the husk logs
Logs are the first place to look, so make them useful when you start the job:
-V 2ekeeps the default verbosity and adds elapsed time;tadds timestamps andaprints Alfred-style progress that queue managers parse.- Houdini 22 adds
--enable-usd-errorsto show USD warnings and errors that are usually suppressed (a missing reference or layer often shows up here) and--error-summaryfor error reporting. - Write one log file per process, so a failed frame can be traced to the run that produced it.
Compare elapsed times across frames: a frame that took a fraction of its neighbours’ time often rendered without some of its data. For crashes without a message, our guide to Houdini exit codes and logs covers what the exit code tells you.
Sources: husk, What’s new in Houdini 22: Karma.
Flags that can leave partial images
Several husk options are useful for long frames but write images that are not finished:
--timelimitcancels a render after N seconds; unless you add--timelimit-nosave-partial, a partial image is saved.--snapshotsaves a partial image every N seconds, with the_partsuffix by default.--karma-percent-of-samples(Houdini 22) stops a Karma render at a percentage of its samples.
Resume options do not know the difference. --skip-existing-frames skips frames that already have files for all render products, and in TOPs a work item whose expected output exists is marked as cooked without being scheduled. Before you rely on either, make sure partial images cannot sit at the final file name.
That is why the file check matters: it is the only step that looks at what is actually on disk.
Sources: husk, USD Render TOP.
Find missing, empty and undersized frames
The script below needs only a standard Python 3 install. It lists every expected frame, flags missing files, files that do not start with the EXR magic number (empty or truncated at the start), and files less than half the median size, then prints a husk --frame-list for the re-render.
A size outlier is a hint, not a verdict: a frame with the camera looking at the sky is legitimately small. Open the flagged frames before re-rendering. For a deeper check, Houdini 22 adds OpenEXR Python bindings, so a hython script can open every EXR fully and read its channels.
Sources: Houdini 22 platform notes, OpenEXR file layout.
Re-render only what failed
husk’s --frame-list takes a space-separated list of frames and overrides -f, -n and -i, so the script’s last line can be pasted straight into the original command. Delete the bad files first, then render the list, then run the check again until it reports nothing. In TOPs, delete the bad files and recook: with Cache Mode set to Automatic only those work items are scheduled. See our husk command-line guide and TOPs rendering guide for the full commands.
Sources: husk, USD Render TOP.
SaaS or IaaS render farm for sequence QA?
Which farm type makes QA easier
Both deliver frames; they differ in where and how you can check them.
| Situation | Usually a better fit | Why |
|---|---|---|
| Frames checked by the farm before delivery | SaaS (managed farm) | Download and run your own check once |
| You want to check and re-render on the same machine | IaaS (remote workstation) | Run the script next to the frames and fix them before downloading |
| Long frames with time limits or snapshots | IaaS | You control which partial files exist and where |
| Large sequences on slow connections | IaaS | Check before transferring hundreds of GB |
| Short one-off render | SaaS | No setup time |
Rule of thumb: with a managed farm, run the check after download. On a machine you control, run it before download and re-render the bad frames in the same session.
Sequence QA on an iRender server
On iRender you rent a whole Windows workstation, install your own Houdini build and sign in with your own SideFX license, so the scene opens exactly as on your desk:
- Upload the project through iRender Drive with relative paths.
- Start a 4x RTX 5090 server (32 GB per card), which we recommend for Karma XPU; 8x servers also render Karma XPU, but it does not get proportionally faster.
- Install your Houdini build. The Karma XPU kernels compile on the first render and the cache stays on your saved server image.
- Render with -V 2e and one log per process, then run the QA script on the output folder.
- Re-render the printed –frame-list, check again, then download the clean sequence.
Sequence QA checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Does –skip-existing-frames check that a frame is complete?
No. It skips frames that already have files on disk for all render products, whether or not those files are complete.
2. Which husk options can leave partial images?
–timelimit saves a partial image unless –timelimit-nosave-partial is set, and –snapshot saves partial images every N seconds.
3. How do I re-render only some frames with husk?
Use –frame-list with a space-separated list of frames; it overrides -f, -n and -i.
4. What does –enable-usd-errors do?
It shows USD warnings and errors that are usually suppressed. It was added in Houdini 22.
5. How can I tell if an EXR is truncated?
A missing EXR magic number or a size far below its neighbours is a strong hint; opening the file with OpenEXR tools confirms it.
6. Will TOPs re-render a broken frame automatically?
Not if the file exists: with Cache Mode Automatic, an existing expected output is marked as cooked. Delete the bad file first.
7. How do I find which husk run produced a bad frame?
Write one log file per process and compare elapsed times across frames; a frame much faster than its neighbours often rendered without some of its data.
Render your Houdini Karma XPU scenes on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 4x NVIDIA RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Houdini and use your own SideFX license; your server image is saved between sessions, so Houdini, your packages and the Karma XPU kernel cache stay installed. For Karma XPU we recommend the 4-GPU servers.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This video walks through rendering a Houdini Karma XPU scene on an iRender server in five steps:
New users get a 100% bonus on the first top-up (minimum $50). See the Karma XPU render farm page for server options, or download the iRender GPU app.
Sources: husk, What’s new in Houdini 22: Karma, Houdini 22 platform notes, USD Render TOP, OpenEXR file layout. Checked November 2026.
If Karma XPU renders are slow on your machine, iRender’s Karma XPU render farm gives you a dedicated remote server where you install Houdini, bring your own license and render on multiple RTX 5090 GPUs (for Karma XPU, 4 GPUs is usually the most efficient setup).


