export const meta = {
title: "How to Set Up an Output Card, LUT Box, and Reference Display",
description: "Learn how to choose a Blackmagic or AJA output card, route SDI through a LUT box, and configure levels, color transforms, and monitor modes for reliable reference viewing.",
tldr: "Set the reference display target first, then choose and configure the output card, LUT box, SDI path, software output, levels, and monitor mode to match that target. Use the LUT box for one clearly defined job, such as display calibration or a viewing/show LUT, and avoid double transforms or range mismatches. Test the full chain with known patterns and save named presets for SDR, HDR, bypass, and client feeds.",
slug: "how-to-set-up-an-output-card-lut-box-and-reference-display",
publishedAt: "2026-08-19",
readingTime: 10,
thumbnail: "https://cdn.aspectlabs.dev/blog/how-to-set-up-an-output-card-lut-box-and-reference-display/cover-9f8b4517524c.png",
authors: ["bright"],
primaryTopic: "technical-solutions",
topics: ["technical-solutions"],
tags: ["monitoring"],
faq: [
{
"question": "Why should I use a video output card instead of judging color from the computer viewer?",
"answer": "A video output card sends a dedicated video signal from the NLE or grading system to the monitoring chain, separate from the operating system desktop. This avoids interference from GPU color management, ICC profiles, desktop scaling, UI overlays, browser color handling, and other non-reference display behavior. The computer viewer can be useful for navigation, but the reference display should receive a clean signal through the dedicated output path."
},
{
"question": "Should the LUT be applied in the software, the LUT box, or the monitor?",
"answer": "The LUT should live in the stage that matches its purpose. Creative or show LUTs may belong in the project if they're part of the creative pipeline. A display calibration LUT often belongs in the LUT box or inside the monitor. A viewing transform may be applied in software or hardware, depending on the workflow. The important rule is to avoid applying the same transform twice. Document which stage handles project color management, output transform, LUT box processing, and monitor mode."
},
{
"question": "Is SDI better than HDMI for a reference monitoring chain?",
"answer": "For professional post monitoring, SDI is usually preferred because it locks reliably, supports longer cable runs, carries embedded audio, and behaves predictably with routers, patch panels, and machine room infrastructure. HDMI can work in smaller rooms or for client displays, but it often introduces more uncertainty around EDID, level range, color space flags, HDCP, and consumer display processing."
},
{
"question": "How do I know whether I need 3G-SDI, 6G-SDI, 12G-SDI, or quad-link SDI?",
"answer": "The required SDI format depends on raster size, frame rate, bit depth, sampling, and whether the signal is HD, UHD, 4K DCI, SDR, or HDR. A 1080p Rec.709 room may only need 3G-SDI. UHD or 4K monitoring, especially at higher frame rates, may require 12G-SDI or multi-link SDI. Confirm that the output card, LUT box, cabling, router, and monitor all support the exact signal format you plan to use."
},
{
"question": "What causes a calibrated monitor to look washed out or crushed?",
"answer": "A common cause is a mismatch between video/legal levels and data/full levels. A full-range signal interpreted as video range can look washed out, while a video-range signal interpreted as full range can crush shadows and highlights. Incorrect gamma, a wrong monitor mode, or a double-applied LUT can also cause similar symptoms. Test with known patterns through the actual output card, LUT box, and monitor path."
},
{
"question": "Where should we record which LUT, monitor preset, and output format were used for a review or approval pass?",
"answer": "Put that information with the cut, not only in an email or room notebook. Aspect can store review context, versions, and custom fields, so teams can track details like Rec.709 Gamma 2.4, PQ 1000 nit, LUT name, output card format, and monitor preset as part of the project’s custom metadata."
}
],
}
The rule is simple: make the reference display the truth, then configure every upstream device to feed it the exact signal it expects. Start with the monitor target: SDR or HDR, Rec.709 or P3/Rec.2020, 1080 or UHD, 23.976 or 24 or 25 or 29.97, video levels or data levels, single-link 12G-SDI or something else. Once you fix that target, the output card and LUT box choices become much easier.
A clean monitoring chain usually looks like this:
```text
Workstation or grading system
→ video output card
→ SDI cable
→ LUT box or color management device
→ SDI cable
→ reference display
```
That chain is boring on purpose because the viewer GUI on your computer display isn't the reference path, and the operating system, GPU ICC profiles, desktop scaling, browser color management, and UI overlays all get in the way. A dedicated video output card gives your NLE or grading system a proper video signal, separate from the desktop. The LUT box applies the viewing transform or calibration transform in real time, and the reference monitor shows the result under known conditions.
## Start with the monitoring target
Before buying or wiring anything, define the signal you need to monitor. The same hardware can behave very differently depending on format, frame rate, levels, and color pipeline.
For a standard SDR editorial or finishing room, the usual target is:
- Rec.709
- Gamma 2.4 for a dim grading environment
- 100 nit reference white
- 10-bit video signal where possible
- Legal/video levels unless the whole chain is explicitly built around full/data levels
- Native project frame rate, not a convenient converted rate
- 1920x1080 or UHD, depending on the room and deliverable
For HDR, the target gets more specific:
- PQ or HLG
- Rec.2020 container, often with P3-limited mastering inside it
- Defined peak luminance, such as 600, 1000, or 4000 nits depending on the display and deliverable
- Correct HDR metadata behavior if any device in the chain depends on it
- 12G-SDI, quad-link SDI, or HDMI 2.x depending on resolution and frame rate
- A monitor that can actually display the required luminance and gamut, not just accept the signal
The takeaway is that “4K HDR capable” isn't a setup plan. A 2160p23.976 PQ signal over 12G-SDI is a different problem from 2160p59.94 SDR, and both are different from 1080p24 Rec.709. Write the target down in the workflow memo or room documentation so the assistant editor, colorist, engineer, and post supervisor aren't guessing from device menus.
## Choose the output card based on signal
[Blackmagic DeckLink and UltraStudio devices](https://kb.pomfort.com/livegrade/reference/device-integrations/setting-up-blackmagic-devices/), [AJA Kona](https://www.aja.com/assets/support/files/8346/en/AJA_Manual_KONA-Series_v16.1.pdf) and Io devices, and similar video I/O hardware all solve the same core problem: they output a dedicated video signal from the workstation to the monitoring chain. The right choice depends on what you need to carry.
The main decision points are:
- Support for the SDI format you need, including 3G, 6G, 12G, quad-link, or dual-link
- The maximum raster and frame rate, such as HD, UHD, 4K DCI, or 50p/60p
- The required color sampling and bit depth, including 4:2:2 10-bit, 4:4:4, RGB, or 12-bit where required
- The connection type to the computer, such as PCIe, Thunderbolt, or external chassis
- Driver support for the software you actually use
- Enough outputs for client, scopes, recorder, or separate clean feeds
- Sync input if the room needs house reference or genlock
- Embedded audio support, especially if monitoring audio through SDI
For many editorial rooms, a single-output 3G-SDI card is enough for 1080p Rec.709 monitoring. For UHD SDR or HDR at higher frame rates, you quickly get into 12G-SDI or multi-link territory. If you need simultaneous output to a reference monitor, client display, and recorder, pick hardware with enough outputs or plan for a proper SDI distribution amplifier or router.
PCIe cards are usually the cleanest choice for fixed rooms because they're stable, low clutter, and can support high bandwidth. Thunderbolt boxes are useful for laptops, carts, and rooms that change often. The tradeoff is that the whole Thunderbolt chain matters: dock quality, cable length, OS permissions, and bus sharing can all affect reliability.
Confirm the exact format support from the card, the software, the LUT box, and the monitor together. A card that can output UHD 60p doesn't help if the LUT box only supports that mode in 4:2:2 and the monitor input is expecting a different mapping.
## Keep the signal path SDI when you can
For professional monitoring, SDI is usually the least annoying path. It locks well, carries embedded audio, supports long cable runs, and behaves predictably in machine rooms and grading suites. HDMI can work, especially for small rooms or consumer client displays, but it adds more ambiguity around levels, color space flags, HDCP, EDID negotiation, and range handling.
A solid SDI path looks like this:
```text
DeckLink / AJA output
→ SDI out
→ LUT box SDI in
→ LUT box SDI out
→ reference monitor SDI in
```
If you need to feed multiple displays, avoid random splitters. Use a proper SDI distribution amplifier or router that supports the signal rate. Put the LUT box before the split only if every downstream display should see the same transformed image. Put the LUT box only in the reference path if the client display should receive a different transform or a simpler display conversion.
Cable rating matters more than people want it to. A short 3G-SDI cable that behaved for years may fail with 12G-SDI. Symptoms can look like random sparkles, intermittent black frames, failure to lock, or weird format negotiation. If the room is moving to UHD or HDR, budget for 12G-rated cabling and patch panels rather than treating cables as an afterthought.
## Decide where the LUT should live
You can apply a LUT in several places: in the software, in the output card path, in an external LUT box, inside the monitor, or sometimes in the camera for on-set viewing. For a post monitoring chain, an external LUT box is useful because it separates the monitoring transform from the creative application timeline.
That separation matters because you usually don't want to bake a display LUT into editorial exports, dailies, or online renders by accident. You want the LUT to affect the monitor path while the media, timeline, and render pipeline remain controlled by the project’s color management plan.
External LUT boxes and color management devices apply 1D and/or 3D LUTs to a live SDI signal. Common uses include:
- Log-to-Rec.709 viewing transforms
- Show LUT preview
- Display calibration LUTs
- SDR/HDR monitoring transforms
- Matching multiple monitors in a controlled pipeline
Devices vary a lot. Some simple boxes offer one SDI input and one SDI output with a loaded LUT. More advanced devices support multiple channels, 12G-SDI, HDR and wide color gamut workflows, 33-point 3D LUT processing, and direct control from look management software. [Flanders Scientific BoxIO](https://flandersscientific.com/support/BoxIOUserManual.pdf), [AJA ColorBox](https://www.aja.com/assets/support/files/9835/en/AJA_ColorBox_Manual_v3.0.pdf), [Blackmagic HDLink-era devices](https://documents.blackmagicdesign.com/UserManuals/HDLinkManual.pdf?_v=1300604403000), and similar tools all sit in this broad category, but they don't all support the same formats or transforms.
The key question is: “can it process the exact signal I'm sending, at the bit depth and frame rate I need, without changing the parts of the signal I need preserved?”
## Use the LUT box for the right transform
There are two common LUT box patterns in post rooms, and mixing them up causes a lot of confusion.
The first pattern is a display calibration LUT. In this setup, the grading application is already outputting the intended display color space, such as Rec.709 Gamma 2.4. The LUT box applies a calibration correction so the monitor conforms more accurately to that target. Your team should create this LUT through a proper calibration process for that specific monitor, input, luminance, and viewing condition.
The second pattern is a viewing or show LUT. In this setup, the system may be outputting log, camera color, ACES, DaVinci Wide Gamut, or another working/rendering space, and the LUT box converts that signal into a display-referred image for the monitor. This is more common on set and in look development, but it also appears in post pipelines that want a hardware viewing transform.
The danger is double-transforming. For example, if Resolve is already outputting Rec.709 Gamma 2.4 and the LUT box also has a log-to-709 LUT loaded, the image will be wrong. If the monitor also has an internal calibration LUT or color space conversion enabled on top of that, it can be wrong in a subtler way.
A sane setup names each transform by role:
- Project color management describes how source media is interpreted and transformed in the software
- The output transform defines what the application sends to the video output card
- The LUT box transform handles calibration, show look, or viewing conversion
- The monitor mode sets the display’s target color space, EOTF, range, and luminance
When something looks off, this naming makes troubleshooting much faster. You're asking which stage is responsible for which transform.
| Stage | Job in the chain | Typical setting or content | Common mistake |
|---|---|---|---|
| Project color management | Interprets source media and defines the working or rendering space | ACES, DaVinci Wide Gamut, camera color management, scene-referred workflow | Assuming it is the same thing as monitor calibration |
| Application output transform | Defines the signal sent from the software to the video output card | Rec.709 Gamma 2.4, PQ Rec.2020, HLG, or a deliberate log feed | Leaving an unchecked preset active or sending the wrong display target |
| LUT box | Applies the assigned hardware transform in the SDI path | Display calibration LUT, show LUT, log-to-709 viewing LUT, HDR-to-SDR transform | Applying a second viewing transform or stacking calibration LUTs unintentionally |
| Reference display mode | Sets how the monitor interprets and displays the incoming signal | Rec.709 Gamma 2.4 at 100 nits, PQ Rec.2020 at target peak, correct input range | Using auto modes, dynamic processing, wrong gamut, or wrong range |
## Configure the software output deliberately
In your NLE or grading system, choose the dedicated video device as the monitoring output. Don't judge color from the program viewer on the computer display unless that's explicitly your workflow and you understand the compromise.
In Resolve, Premiere Pro, Media Composer, Baselight, Flame, and other systems, the details differ, but the intent is the same. The application needs to know:
- Which video I/O device to use
- Output raster and frame rate
- Whether to follow timeline format or force a monitoring format
- Data levels or video levels behavior
- Output color space or display transform
- Whether external video scopes, clean feed, or HDR metadata are active
- Whether the application is applying a video monitoring LUT
For SDR Rec.709 finishing, many rooms output Rec.709 Gamma 2.4 from the application, then use the LUT box only for display calibration. In [Resolve color managed workflows](https://www.youtube.com/watch?v=CTAzjAReZvs), for example, Rec.709 Gamma 2.4 is a common SDR output target. If you're using ACES or DaVinci Wide Gamut, make sure you set the output transform intentionally rather than inherit it from a preset no one checked.
Editorial rooms often get tripped up because teams treat the timeline, proxy media, and monitoring output as one thing. They aren't. You might cut with 1080p proxies, maintain a UHD sequence, and monitor 1080p Rec.709 because that's what the room can reliably display. That can be fine, but everyone should know that the reference monitor is showing a downconverted monitoring signal, not a native UHD master.
Aspect gives the whole team one shared cloud filespace, so editorial, finishing, and review can point at the same media. That reduces duplicate proxy folders and handoff drives when you're testing what the monitoring chain is actually showing.
## Match levels across the whole chain
[Video levels versus data levels](https://mixinglight.com/color-grading-tutorials/is-your-reference-display-input-set-to-data-or-video-levels/) is one of the easiest ways to make a calibrated display look “uncalibrated.” The image might look washed out, crushed, too contrasty, or slightly wrong in the shadows and highlights. People will start adjusting the monitor, the grade, or the LUT, when the real issue is range mapping.
In simple terms:
- Video/legal levels use the traditional limited video range
- Data/full levels use the full code value range
- Some software uses “auto” logic based on codec, format, or output path
- Some monitors expect a fixed range on certain inputs
- Some LUT boxes pass levels transparently, while others can be configured to scale or process them
The safest approach is to choose one expected range for the monitoring chain and set every device accordingly. In many broadcast and post environments, teams configure SDI monitoring for legal/video levels. If your facility uses full range for a specific workflow, document it and test it with known patterns.
Use a pluge pattern, grayscale ramp, and range chart through the actual output card, LUT box, and monitor input. Don't test from a still you opened on the desktop unless the desktop path is the thing you're calibrating. You want to see how the reference chain handles code values, not how macOS or Windows displays an image.
## Set the LUT box as a networked device
You often control modern LUT boxes over [Ethernet or USB](https://kb.pomfort.com/livegrade/hands-on/setting-up-livegrade/building-a-livegrade-setup/) with calibration software, live grading software, or vendor utilities. Treat that control path as part of the room design. Label the device, assign a stable IP if needed, and keep the utility software available on the machine that will manage it.
A typical managed setup includes:
- Workstation running the grading or calibration software
- Video output card sending SDI
- LUT box on SDI for image processing
- Ethernet or USB control connection to the LUT box
- Reference monitor receiving processed SDI
- Saved presets for SDR, HDR, calibration bypass, and show LUT modes
The bypass preset is especially useful. You need a fast way to compare processed and unprocessed signal without unloading LUTs by hand. If the LUT box supports multiple slots or pipelines, name them clearly. “709_cal_2026_02” is better than “LUT_3_final_final.”
Also watch for firmware and LUT format compatibility. Some devices expect cube files with specific sizes. Some support 17-point, 33-point, or 65-point 3D LUTs. Some need separate 1D shaper LUTs for best results. Loading a LUT successfully doesn't mean it's the right transform for that device or signal.
## Configure the reference display last, then stop touching it
Set the monitor to the target mode for the room. For SDR Rec.709, that usually means the Rec.709 color space, Gamma 2.4, correct luminance, correct input range, and disable any internal processing unless it's part of the calibration plan. For HDR, select the correct EOTF, gamut/container, peak luminance behavior, and input format.
Monitor menus can be dangerous because they contain many settings that look helpful but break reference behavior. Don't keep dynamic contrast, auto color modes, noise reduction, motion smoothing, super white expansion, or extra processing features active on a reference path. If the display has internal LUT support, decide whether calibration lives inside the monitor or in the external LUT box. Avoid stacking both unless the calibration plan explicitly calls for it.
After calibration, lock the monitor settings if the display supports it. At minimum, write them down and save them as named presets. A room can lose half a day because someone changed an input range setting while trying to make a client monitor look nicer.
## Common failure modes and how to read them
Most monitoring problems show up as a visual complaint, but the cause is usually a signal mismatch, so these symptoms are useful because they point to the likely stage.
Common patterns include:
- A washed-out image usually points to a full-range signal interpreted as video range, wrong gamma, or double display transform
- Highlights clipping early usually points to a range mismatch, HDR-to-SDR mistake, or LUT built for a different peak luminance
- Colors that are too saturated usually point to a gamut mismatch, P3/Rec.2020 content viewed as Rec.709, or wrong monitor mode
- No signal usually points to an unsupported raster/frame rate, bad cable, wrong SDI link mode, or output card not selected
- Missing audio usually points to embedded audio disabled, wrong SDI output, or monitor not set to the expected audio pair
Don't troubleshoot by changing five things at once. Bypass the LUT box, confirm the output card signal, then reinsert the LUT box with processing disabled, then enable the transform. That isolates whether the problem is format, processing, or display configuration.
## Build presets for the work you actually do
A monitoring chain is only useful if the next person can recall it, and most facilities and teams need a small set of known-good modes.
Useful preset families might include:
- An SDR editorial preset with 1080p, Rec.709 Gamma 2.4, and video levels
- An SDR finishing preset with UHD or HD, Rec.709 Gamma 2.4, and a calibrated reference path
- An HDR review preset with UHD, PQ, Rec.2020 container, and a defined nit target
- A show LUT preview preset with a camera/log input transform plus show look to display target
- A calibration bypass preset with the same signal format and LUT processing disabled
- A client display feed preset with separate conversion if the client display isn't reference accurate
Presets should include software settings, output card format, LUT box slot, monitor input, monitor mode, and cabling route. If the room has a router, include the route name. If the setup lives on a cart, include the physical port labels.
Aspect stacks every version on one asset, so the current cut, older exports, and notes stay together. That helps the team compare monitoring presets against the right revision instead of chasing mismatched files from different review rounds.
This is where post supervisors and assistant editors can save the color team real pain. A simple monitoring note in the project workflow documentation prevents “it looked different in editorial” conversations later. Include the monitoring target, LUT names, where your team applies transforms, and any known compromises such as HD monitoring for a UHD finish.
## The setup that works most of the time
For a reliable SDR post room, a strong baseline is:
```text
Workstation running the NLE or grading system
→ Blackmagic or AJA video output card
→ 3G/12G-SDI depending on raster and frame rate
→ LUT box with display calibration LUT
→ SDI reference monitor set to Rec.709 Gamma 2.4
```
Set the software to output the same display target you calibrated the monitor for. Keep creative LUTs inside the project only when they're part of the grade or dailies pipeline. Keep display calibration in the LUT box or monitor, not both casually. Use video levels unless your workflow has a clear reason not to. Test with patterns through the real chain.
For HDR or on-set-style look management, the same structure applies, but the LUT box becomes more than a calibration device. It may be handling color space conversion, show LUTs, HDR/SDR trims, or live look updates from control software. In that case, choose hardware with enough processing precision, format support, and control integration for the job.
The best monitoring setup is the one where every device has a clear job, every transform has one home, and the reference display receives the signal you calibrated it to show.