AJA Corvid HEVC review

Corvid HEVC is a discontinued developer-oriented PCIe capture and hardware-encoding board, not a simple consumer capture dongle. AJA’s SDK reference calls out four 3G-SDI inputs and real-time, low-latency HEVC encoding; its detailed format page says independent formats may be used when they share a clock family. AJA also marks the board end-of-life and records the feature set as complete in SDK 15.1. This is a specialist reference for an existing production system, not a current availability recommendation.

Four SDI inputs and an onboard HEVC encoder

The board has four 3G-SDI BNC inputs, an LTC/reference input, and four audio systems. AJA lists 16 embedded audio channels per system. Its exact input table covers SD/HD, 2K and 4K/UHD; the detailed 4K list extends through 59.94 A/B, while the separate 1080p list includes 50, 59.94 and 60. The SDK summary describes support up to 4Kp60, but because the detailed raster table does not list integer 60 for those 4K modes, this assessment does not equate the broader phrase with an exact 4K60 match. The 4K file-based encoding modes are also not the same thing as an SDI input timing; AJA labels several film formats as file-based only.

The encoder supports HEVC Main/Main 10, 8- or 10-bit depth, 4:2:2 or 4:2:0 chroma and CBR/VBR rate control; the sheet lists 3–128 Mbps for 4K. Those are encode-format options, not evidence that every four-input combination can be encoded at the maximum. AJA allows multiple independent input formats only when they share a clock family. The board does not provide an HDMI input or a consumer display passthrough connector. It is the wrong path for a protected console source or a direct monitor loop.

Host integration is part of the system

Corvid HEVC uses eight lanes of PCIe Gen 2 and requires either bus power from a graphics slot or an ATX 6-pin power connection. Check the slot wiring and power lead in the target workstation; a card that fits physically may still be missing the lane or power arrangement needed for its documented operation. AJA’s specification describes developer partners integrating its SDK directly into Windows and Linux applications. That is not a claim that a standard consumer app has a ready-made profile, or that OBS Studio can encode these formats through the hardware automatically.

The board is feature-complete in SDK 15.1, and AJA calls it end-of-life. That means an installed system depends on a specific historic driver/API and a software integration that may be costly to recreate. The source documents are useful for identifying the hardware and its original role, but they do not establish compatibility with a current Windows or Linux release, an arbitrary PCIe host, or any particular seller’s used card. No exact price, stock, warranty or customer experience is inferred here.

When the product makes sense

Consider this model only when a project specifically needs multiple SDI inputs and hardware HEVC encoding inside a supported developer-controlled application. The four inputs, clock-family caveat, file-based-only timing exceptions, power lead and SDK integration all need to be reviewed together. If the requirement is one SDI source captured into a familiar editing or streaming program, a simpler currently supported card may be a more practical route. If you need a direct HDMI monitor loop, compare products whose own mode matrix documents it rather than treating this board’s SDI I/O as passthrough.

Compared with Corvid 24, the HEVC model is an eight-lane four-input encoder card rather than a four-connector 3G-SDI I/O card with bypass relays. Compared with the HB-R, it trades a specialized HDBaseT camera path and HDMI loop for SDI ingest and HEVC encoding. Verify the exact board, host power, PCIe slot, AJA SDK version and application integration before considering a specific offer.