Houdini Karma Light Groups: LPE Tags, Light Linking and Blockers
Karma gives you three tools for per-light control: LPE tags for light-group AOVs, light linking for what each light touches, and (new in Houdini 22) blocker light filters. Key points for Karma XPU:
- Groups: tag lights and turn on Split per LPE Tag to get C_Key, C_Fill…
- Custom: write LPEs such as C.*<L.'Key'> in Extra Render Vars
- XPU limits: only coat and sss BSDF labels; shadow linking limited to 4 rules
- Linking: Light Linker LOP writes the rules onto the lights
- Blockers: Karma Blocker Light Filter (H22); filtered lights stay out of the light tree
Lighting changes are the most common notes on a shot. If each light has its own AOV, many of those notes can be handled in compositing; if lights affect only the objects they should, fewer notes come back at all. Karma handles both with USD-native tools: light path expressions (LPEs) with light tags, rule-based light linking, and light filters.
This guide explains how light-group AOVs work in Karma, how to write custom LPEs, what Karma XPU supports in light and shadow linking, and how the new Houdini 22 blocker light filter fits in, including its effect on sampling.
Checked against the SideFX Houdini 22 documentation (Light Path Expressions, Light Linker, Karma Blocker Light Filter, Karma XPU), November 2026.
Light-group AOVs with LPE tags
Every LOP light has an LPE Tag parameter in the Light section of its Karma tab; the LPE Tag LOP sets tags on many lights at once. SideFX calls Split per LPE Tag the most convenient way to see each light’s influence: many default AOVs on the Karma Render Settings LOP have the checkbox, and with tags Key, Fill and Rim the beauty AOV splits into C_Key, C_Fill and C_Rim.
Each split AOV is a full frame buffer. Tag only the lights the compositor will grade separately, and split only the AOVs they will use; our Karma AOV guide covers what each buffer costs on Karma XPU.
Sources: Light Path Expressions, AOVs.
Writing custom light path expressions
An LPE describes which light paths an AOV collects, from the camera C to a light L or an emissive object O. Tags are written in single quotes, so C.*<L.'Key'> collects every path that ends on a light tagged Key.
Light and geometry tags can be combined, for example to isolate the key light’s contribution on one wall. Add custom LPEs as render vars in the Extra Render Vars section or with the Additional Render Vars LOP:
The shadow; prefix returns the ratio of occluded to unoccluded light from the beauty pass, which compositors use for shadow passes. The holdout; prefix outputs the lighting on holdout objects. On Karma XPU, keep custom expressions to the built-in events: SideFX notes that custom BSDF labels work only with VEX-based shaders, MaterialX is not supported, and coat and sss are the only BSDF labels Karma XPU supports.
Sources: Light Path Expressions.
Light linking and shadow linking on Karma XPU
The Light Linker LOP creates USD light link properties from rules, using a custom interface that takes over the parameter editor. All relationships are authored on the lights, so a rule that involves many lights is written onto each of them.
Because the relationships sit on the lights, a rule that touches many lights is written many times; when a link looks wrong, inspect the light’s properties first.
Light control features and their Karma XPU status
From the Houdini 22 Karma XPU, LPE and Light Linker pages.
| Feature | Karma XPU | Note |
|---|---|---|
| LPE tags and Split per LPE Tag | Supported | Tags set on the light’s Karma tab or with the LPE Tag LOP |
| Shadow and holdout LPEs | Supported | shadow;C.*[LO] and holdout;C.*[LO] |
| Custom BSDF labels | coat and sss only | Custom labels need VEX shaders; MaterialX is not supported |
| Light linking | Supported | Rules authored on the lights by the Light Linker LOP |
| Shadow linking | Limited | XPU page: up to 4 rules or groups per scene; Light Linker help still says CPU only, so test it |
| Blocker light filter | Houdini 22 | Sphere, capsule or box; Invert lets light through only inside the shape |
Light linking is supported on Karma XPU. Shadow linking needs care: the Karma XPU page lists it with a limit of four rules or groups per scene, while the Light Linker help still states that shadow linking is only available for Karma CPU. Because the two pages disagree, render a test frame on XPU and check every shadow-linked object before a long run, or keep shadow linking for shots rendered on Karma CPU.
Sources: Light Linker LOP, Karma XPU.
Blocker light filters in Houdini 22
Houdini 22 adds the Karma Blocker Light Filter LOP. It authors a USD blocker light filter that uses a simple shape (sphere, capsule or box) to remove or reduce light in part of a light’s beam, or to create shadows from invisible objects. Invert turns the shape into the only area where light passes.
Light filters have a sampling cost. On the light tree, the Karma render settings help lists lights that cannot be added to the tree and are always sampled: dome, distant and point lights, lights with shaping controls such as spot lights, and lights with light filters. In scenes with many lights, the light tree can be significantly faster, so use blockers where they replace extra geometry or a compositing fix rather than on every light. Houdini 22 also lets geometry lights use instancing and light filters, and moves volume and geometry lights into the light tree.
Sources: Karma Blocker Light Filter LOP, Karma render settings: light tree, What’s new in Houdini 22: Karma.
SaaS or IaaS render farm for light-group renders?
Which farm type fits a light-group workflow
Both render LPE AOVs; they differ in how quickly you can check them.
| Situation | Usually a better fit | Why |
|---|---|---|
| Light groups and links already tested on XPU | SaaS (managed farm) | Submit and collect the AOVs |
| Shadow linking or custom LPEs not yet checked on XPU | IaaS (remote workstation) | Render a frame, compare CPU and XPU, adjust in the same session |
| Scene with many lights and filters | IaaS | You can time frames with and without blockers before the full run |
| Lighting notes expected during the render window | IaaS | You keep the scene open on the machine and re-render changed shots |
| One-off render with standard lights | SaaS | No setup time |
Rule of thumb: once every LPE AOV and linked light has been checked on Karma XPU, a managed farm is the least work. While you are still testing shadow linking or custom LPEs, a machine you control saves round trips.
Rendering light groups on an iRender server
On iRender you rent a whole Windows workstation with your own Houdini, so you can check each light-group AOV before the full render:
- Upload the project through iRender Drive with relative paths.
- Start a 4x RTX 5090 server, 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 one frame and check every C_ tag AOV, custom LPE and linked light in your compositing package.
- Render the range with husk or the USD Render ROP.
Light-group checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. How do I render one AOV per light in Karma?
Give each light an LPE tag on its Karma tab, then turn on Split per LPE Tag on the AOVs you want. The beauty AOV C becomes C_Key, C_Fill and so on.
2. How do I write a light path expression for one light?
Use the tag in single quotes, for example C.*<L.’Key’>. Add O to include emissive objects: C.*[<L.’Key’>O].
3. Does Karma XPU support light linking?
Yes. Light linking is supported. Shadow linking is limited to four rules or groups per scene according to the Karma XPU page.
4. Can I use custom BSDF labels in LPEs on Karma XPU?
Only coat and sss. SideFX notes that custom BSDF labels work only with VEX-based shaders and MaterialX is not supported.
5. What is the Karma Blocker Light Filter?
A Houdini 22 LOP that authors a blocker light filter: a sphere, capsule or box that removes or reduces light in part of a light’s beam.
6. Do light filters slow down Karma?
Lights with light filters cannot join the light tree and are always sampled, which can cost render time in scenes with many lights.
7. How do I get a shadow-only pass in Karma?
Add an Extra Render Var with the LPE shadow;C.*[LO]; it returns the ratio of occluded to unoccluded light from the beauty pass.
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: Light Path Expressions, AOVs, Light Linker LOP, Karma Blocker Light Filter LOP, Karma render settings, Karma XPU, What’s new in Houdini 22: Karma. 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).


