November 7, 2026 Maddie Quach

Karma Sequence QA: Logs, Missing Frames and Re-rendering Only What Failed

Sequence QACheck a finished sequence before you deliver it
From SideFX documentation

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:

iRender
A Sequence QA Loop for Karma Renders
Schematic
Renderhusk with -V 2eRead logserrors, warnings, timeCheck listmissing frame numbersCheck files0 bytes, size outliers, headerRe-render--frame-list of bad framesrepeat until the list is emptyAutomatic resume (--skip-existing-frames, Cache Mode) trusts any file on disk, including a broken one.
render and logsfile checksfix
Schematic; flags from SideFX husk docs

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 2e keeps the default verbosity and adds elapsed time; t adds timestamps and a prints Alfred-style progress that queue managers parse.
  • Houdini 22 adds --enable-usd-errors to show USD warnings and errors that are usually suppressed (a missing reference or layer often shows up here) and --error-summary for 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:

  • --timelimit cancels a render after N seconds; unless you add --timelimit-nosave-partial, a partial image is saved.
  • --snapshot saves a partial image every N seconds, with the _part suffix 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.

iRender
What a Frame-by-Frame Check Finds
Schematic
1001100210031004100510061007missing10081009101010111012101310140 KB101510161017101810191020small1021102210231024--skip-existing-frames would re-render only 1007; 1014 and 1020 exist on disk and are skipped.A size and header check catches them before delivery.
missingempty filesize outlier
Illustrative example

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.

iRender
Find missing, empty and undersized frames
python
1# qa_frames.py - run with any Python 3: python qa_frames.py
2import os, statistics
3DIR, PRE, EXT = "D:/proj/render", "shot.", ".exr"
4FIRST, LAST = 1001, 1100
5MAGIC = b"\x76\x2f\x31\x01" # first 4 bytes of an EXR
6
7sizes, bad = {}, []
8for f in range(FIRST, LAST + 1):
9 p = os.path.join(DIR, f"{PRE}{f:04d}{EXT}")
10 if not os.path.exists(p):
11 bad.append((f, "missing")); continue
12 with open(p, "rb") as h:
13 if h.read(4) != MAGIC:
14 bad.append((f, "not EXR / empty")); continue
15 sizes[f] = os.path.getsize(p)
16
17med = statistics.median(sizes.values()) if sizes else 0
18for f, s in sizes.items():
19 if s < 0.5 * med:
20 bad.append((f, f"small: {s} bytes"))
21
22for f, why in sorted(bad):
23 print(f, why)
24print("--frame-list", " ".join(str(f) for f, _ in sorted(bad)))
Last line prints a ready-made husk --frame-list for the re-renderEXR magic number: OpenEXR file layout · --frame-list: SideFX husk docs

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?

CompareNeutral guide

Which farm type makes QA easier

Both deliver frames; they differ in where and how you can check them.

SituationUsually a better fitWhy
Frames checked by the farm before deliverySaaS (managed farm)Download and run your own check once
You want to check and re-render on the same machineIaaS (remote workstation)Run the script next to the frames and fix them before downloading
Long frames with time limits or snapshotsIaaSYou control which partial files exist and where
Large sequences on slow connectionsIaaSCheck before transferring hundreds of GB
Short one-off renderSaaSNo 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

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.hip · .usd1 GPUYour iRender serverscene.hip · .usdup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found

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:

  1. Upload the project through iRender Drive with relative paths.
  2. 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.
  3. Install your Houdini build. The Karma XPU kernels compile on the first render and the cache stays on your saved server image.
  4. Render with -V 2e and one log per process, then run the QA script on the output folder.
  5. 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.

ChecklistSequence QA checklist
0 / 7 done
Tip: tick each item as you set up the job; the ticks reset when the page reloads.

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.

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).

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by 4x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , ,

Maddie Quach

Maddie Quach, from iRender's customer support team, has written more than 100 articles for the iRender blog on Maya, Houdini, Arnold, Karma XPU and Redshift.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →