Capture Card Fit

Professional I/O

Compare AJA Corvid capture boards by signal path and host

The Corvid family includes current and earlier developer-oriented PCIe boards, not one interchangeable capture card. This guide compares the observed models by connector direction, channel layout, documented timing and host evidence. Some AJA product pages and NTV2 SDK records describe older software paths; they are not proof that an arbitrary application or used-card package works on every current system.

Current Corvid 88: eight configurable 3G-SDI connections

The current AJA Corvid 88 assessment covers an eight-port developer I/O board with bidirectional 3G-SDI DIN 1.0/2.3 connectors. AJA lists grouped-link 4K/UltraHD modes and up to dual 4K 50/60p, but that does not turn the card into a one-cable 12G board or promise eight maximum-rate sources. The exact app must allocate its ports, compatible timing and any independent SDI output.

There is a host-document discrepancy worth resolving against the exact card: AJA's current Corvid 88 product page/spec sheet say PCIe 3.0 x4, while its Corvid comparison and published NTV2 17.1.3 device page still say PCIe 2.0 x8. The review retains both source statements and does not infer a revision boundary. AJA's Corvid matrix names OBS for this model on Windows and macOS, but the conservative OBS plan is one SDI source at 1080p60; OBS's own plugin notes call for more testing of 4K SDI transport. Do not transfer the Corvid 88 OS/app plan to earlier Corvid boards.

Start with the input connector and its direction

Corvid 1 and Corvid 3G are single-channel SDI boards with a distinct input/output pair. Corvid 22 has two SDI inputs and two outputs. Corvid 24 has four connectors whose directions are configured by software, with a hardware bypass relay/watchdog behavior that depends on setup. Those SDI output connectors are not automatically a consumer monitor-passthrough path. They belong to a professional signal-chain design and the application must configure the device.

Corvid HB-R is the easy one to misread from a connector photo: its RJ-45 is an HDBaseT input carrying an HDMI signal from a compatible camera/transmitter. It is not Ethernet and it is not an HDMI socket on the card. Its bracket also has an active HDMI loop output, but that does not make the upstream input a direct HDMI connection. The documented loop follows the negotiated input timing; AJA excludes HDCP, describes no EDID interface and limits 4K60 to 8-bit 4:2:0. A conventional HDMI source needs a separately verified HDBaseT transmitter, not just a passive cable.

Corvid HEVC is a separate developer encoder board with four 3G-SDI inputs and an auxiliary-power requirement. Its product summary and NTV2 SDK describe a 4K-capable HEVC workflow, but the detailed AJA timing table distinguishes 59.94 A/B entries from a general phrase that says “4Kp60.” The reviewed finder plan therefore does not map this card to the exact 4K60 choice. Its documented one-source 1080p60 SDI plan is more conservative and does not claim that four inputs can all encode their maximum formats at once.

Compare the observed Corvid boards by practical boundary

  • Corvid / Corvid 1: an earlier single-channel SDI capture/playout board for SD and HD work. The exact table reaches 720p60 but tops out at 1080p30. AJA’s 2018 end-of-life notice gives separate short- and tall-bracket OEM codes and names KONA 1 as its successor. Check the bracket and legacy SDK requirements before considering a used example.
  • Corvid 3G: a different one-input/one-output SDI board with 3G-format capability, including a documented 1080p60 timing. It is not the fiber model and should not inherit Corvid 1’s lower ceiling or Corvid 22’s two-channel layout. Its legacy Mac SDK support is not a current macOS compatibility promise.
  • Corvid 22: two independent SDI input/output channels on a Gen 1 x4 PCIe board. AJA documents HD and 2K formats, including a one-feed 1080p60 plan. The board reached end of life in 2024 and was superseded by Corvid 44; used listings need the correct OEM configuration and working SDK/application path.
  • Corvid 24: four configurable 3G-SDI connectors, Gen 2 x4 PCIe, and bypass-relay/watchdog behavior. One input at 1080p60 is a narrower assessment than using four links for a 4K/UHD arrangement; the latter has different timing limits, including a 25p ceiling in the reviewed table. Confirm direction, software configuration, jumper state and whether the chosen mode uses a relay path.
  • Corvid HB-R: one HDBaseT camera input carried over RJ-45 plus an active HDMI loop output. This is for an installed camera/link workflow with a compatible transmitter, not a direct HDMI gaming-card replacement. Plan around the 4K60 8-bit 4:2:0 limit, lack of HDCP/EDID and historical Linux/V4L2 integration rather than assuming an HDMI 2.1 feature set.
  • Corvid HEVC: four SDI inputs feeding a developer-oriented encoding workflow on an x8 Gen 2 PCIe board with auxiliary power. The capture card is only one part of the system: validate the AJA SDK version, encoder application, PCIe lane/power arrangement and exact per-input format table. Do not substitute the product page’s broad 4K summary for the precise timing rows.
  • Corvid 88: a current eight-port 3G-SDI card with compact DIN 1.0/2.3 connectors and grouped-link 4K/UltraHD modes. The present AJA product page/spec sheet state PCIe 3.0 x4, while the published comparison and NTV2 17.1.3 device reference state PCIe 2.0 x8; verify the exact board revision. Its OBS plan here is one 1080p60 source, not 4K.

Separate the video timing from host and software evidence

These boards are internal PCIe devices, but “PCIe” by itself is insufficient. Record lane width and generation, physical slot length and electrical lanes, auxiliary power, chassis airflow, bracket height and the workstation OS. A board can fit a connector and still fail its required link or cooling assumptions. AJA’s historical SDK compatibility statements should be treated as versioned evidence: recheck the exact SDK, operating system, firmware and application integration before purchase. AJA's current matrix names OBS for Corvid 88 and the four Corvid 44 models; this guide does not extend that evidence to Corvid 1, 3G, 22, 24, HB-R or HEVC.

Likewise, a single supported input mode does not prove all channels operate concurrently at that rate. For two or four inputs, check the selected timing on each input, shared reference/clock-family requirements, memory/DMA constraints and application support. The numbers in a per-channel table should not be converted into a guarantee of peak throughput across all connectors.

Used-market checks for a developer board

Before evaluating a listing, ask for a clear photo of the actual board label and connector bracket, not a generic family image. Match the full model name and OEM part number to the intended host, identify any required breakout or HDBaseT transmitter, and confirm that the included power lead and bracket match the exact SKU. Request the seller’s return terms and test status without assuming a used listing has current drivers, a transferable license, a supported firmware revision or warranty coverage. The manufacturer pages here identify model configurations; they do not establish present stock or the condition of any offer.

For system planning, write down four separate lines: the physical source connector; the intended capture format; the host bus, OS and app; and any independent output/display requirement. The earlier-model control changes whether historical product assessments are included, not whether their old support paths have become current. The examples below keep those choices visible and link to the exact finder request instead of silently substituting a similar board.

Windows SDI at 1080p60 on PCIe

Three Corvid arrangements fit this exact reviewed plan

Thirty-six earlier-inclusive assessments match SDI capture at 1080p60 on PCIe with Windows. Within the Corvid set, the Corvid 22, Corvid 24 and Corvid HEVC have reviewed one-source arrangements; the current Corvid 88 adds an OBS 1080p60 plan on Windows, while 4K needs a different developer-app route. The AJA KONA 3G and KONA LHi each add a separate digital SDI/1080p60 plan; standalone KONA 5 is a current PCIe Gen 3 x8 alternative with separate 6-pin ATX power and its own Control Room/OBS limits. The four current Corvid 44 variants also have distinct Windows plans: DIN 1.0/2.3 3G, full-size-BNC 3G, HD-BNC 12G and full-size-BNC 12G. Corvid 1 stops at 1080p30, the reviewed Corvid 3G plan is Mac SDK evidence rather than a Windows plan, and HB-R takes HDBaseT rather than SDI. Find this same earlier-inclusive Windows/SDI/1080p60/PCIe request.

macOS SDI at 1080p60 on PCIe

Keep the earlier Corvid 1 ceiling separate

Twenty-three earlier-inclusive assessments match SDI capture at 1080p60 on PCIe with macOS. The earlier Corvid matches are Corvid 3G, Corvid 22 and Corvid 24; the current Corvid 88 also has a model-specific OBS 1080p60 path on macOS, distinct from its 4K developer plan. KONA 3G, KONA LHi and standalone KONA 5 have separate one-source SDI plans; the KONA 5 card needs a 6-pin ATX feed. The four current Corvid 44 routes are separate: 3G DIN 1.0/2.3, 3G full-size BNC, 12G HD-BNC and 12G full-size BNC; the current v18 Mac route requires Apple silicon/macOS 14 or later. The original Corvid 1 is excluded at this boundary because its exact maximum is 1080p30; the Windows-oriented HEVC plan and HDBaseT-only HB-R plan do not meet this Mac SDI request. Find this same earlier-inclusive Mac/SDI/1080p60/PCIe request.

Corvid 1 without imposing the 1080p60 boundary

A legacy Mac SDK route for SDI through 1080p30

Thirty-five earlier-inclusive assessments match SDI and PCIe on macOS when no capture-rate minimum is selected; the Corvid 1 remains a 1080p30 model. Current Corvid 88 has separately documented 1080p60 OBS and grouped-link 4K developer plans, while the Corvid 44, Corvid 44 BNC, Corvid 44 12G and Corvid 44 12G BNC add distinct Apple-silicon PCIe plans; Intel Macs need a separate older-driver check. The standalone KONA 5 is another current SDI/PCIe route and is distinct from its Io Xpand bundle. AJA Io Express, KONA 3G and KONA LHi also match at their documented conditions; do not infer that the older Io Express handles 1080p60. The Corvid 1's 720p60 row does not make it a 1080p60 card. Find this same earlier-inclusive Mac SDI/PCIe request.

The same host and input, with 1080p60 required

Adding a 1080p60 capture requirement removes Corvid 1 from that Mac SDI/PCIe plan; Corvid 3G, Corvid 88, standalone KONA 5 and the four current Corvid 44 variants join the exact 1080p60 set under their separately supported Mac plans. Compare the Corvid 1, Corvid 3G, Corvid 88, Corvid 44, Corvid 44 BNC, Corvid 44 12G and Corvid 44 12G BNC reviews rather than treating the model names as interchangeable revisions. Find this same earlier-inclusive Mac SDI/1080p60/PCIe request.

HDBaseT camera input with 4K60 loop output

Do not relabel HDBaseT as direct HDMI

Eleven earlier-inclusive PCIe assessments match a 4K60 capture and 4K60 passthrough/monitor requirement, including the distinct MK.2; the Elgato 4K60 route is Windows/OBS SDR. They use different signal families: the original Elgato 4K60 Pro is one Windows-only HDMI/SDR route, while the separate 4K60 Pro MK.2 adds a Windows utility HDR-recording path; the Corvid HB-R is the HDBaseT loop case. Current Corvid 44 12G and Corvid 44 12G BNC plus standalone KONA 5 match separate SDI capture-and-monitor arrangements. The 3G Corvid 44 and Corvid 44 BNC do not because their four-link 4K ports are used for input or output, not both. HB-R's camera signal enters over HDBaseT on RJ-45; its loop is limited to 8-bit 4:2:0 at 4K60, without HDCP or EDID. The answer does not select an OS, so verify that requirement before comparing the Windows-only Elgato plans. Find this same earlier-inclusive 4K60-capture/4K60-monitor/PCIe request.

Direct HDMI with a 4K60 display path is a different request

Nine earlier-inclusive PCIe assessments match direct HDMI with 4K60 passthrough, including the distinct MK.2; its Windows/PCIe HDR-recording path is separate from this open capture target. The original Windows-only Elgato 4K60 Pro is another direct input model, while the separate MK.2 is not the original card. None is Corvid HB-R because its input is HDBaseT, not a direct HDMI connector. A direct-input candidate such as AVerMedia GC575 has its own model-specific path. The OS and capture target are left open in this answer, so check the exact input mode and Windows-only restriction before choosing any candidate. Find this same earlier-inclusive direct-HDMI/4K60-passthrough/PCIe request.

Corvid 88 SDI 4K60 requires the right software plan

Separate the card's grouped-link ceiling from OBS and Control Room

Fifteen current-reference products match SDI input, 4K60 capture, PCIe and Windows when no capture-software requirement is selected. KONA X and the distinct KONA XM join KONA 4 and KONA 5 with single-source Control Room 4K60 routes; KONA 4 uses four linked 3G-SDI inputs, KONA 5 one 12G-SDI input, and KONA XM one SDI source with a 10-bit 4:2:2 60p ceiling. Corvid 88's own 4K plan instead uses grouped 3G-SDI and a compatible NTV2 developer application. Compare the Corvid 88 assessment with the 3G Corvid 44, Corvid 44 12G, Corvid 44 12G BNC, DeckLink 8K Pro G2 and Pro Capture SDI 4K Plus reviews; these are not the same link or application arrangement. Find this same SDI/4K60/PCIe/Windows request without a required app.

Adding OBS Studio narrows that SDI/4K60/PCIe/Windows set to seven documented model plans and excludes Corvid 88; standalone KONA 4 joins through its documented four-link SDI OBS path, while KONA X and KONA 5 remain excluded because their reviewed OBS plans are limited here to 1080p60, not 4K60. Corvid 88's OBS plan is likewise one SDI source at 1080p60, while its 4K plan requires a compatible developer application. The remaining set still needs its own card/app checks; OBS's AJA plugin notes caution that 4K SDI transports need more testing. Compare the DeckLink 8K Pro G2 and Pro Capture SDI 4K Plus reviews rather than assuming their plans are interchangeable. Read the Corvid 88 assessment and find the same SDI/4K60/PCIe/Windows/OBS request.

Four reviewed models match SDI input, 4K60 capture, PCIe, Windows and AJA Control Room: KONA 4 uses four linked 3G-SDI inputs, KONA 5 uses one 12G-SDI input, KONA X has a one-source SDI path with separate monitoring, and KONA XM adds a 12G-SDI source at its 10-bit 4:2:2 60p ceiling; its 12-bit RGB mode stops at 30p. Corvid 88's reviewed 4K plan instead requires a compatible NTV2 developer application and does not qualify for Control Room. This is specific to the current reviewed library, not a claim about every product elsewhere. Check the Corvid 88 application boundary and find this same SDI/4K60/PCIe/Windows/Control Room request.

Earlier AJA PCIe paths by operating system

For an earlier-inclusive Windows PC with SDI input, PCIe and 1080p60 capture, KONA XM has a one-source AJA Control Room route. The separate KONA X is another one-source SDI card, while KONA 4 uses four linked inputs for its distinct 4K routing. Read the KONA XM review and KONA 4 assessment, then find this same earlier-inclusive Windows/SDI/1080p60/PCIe request.

For the same SDI/PCIe/1080p60 request on Mac, KONA X has a documented Control Room route. Its v18 Mac installer requires Apple silicon with macOS 14 or later; Intel Macs need the supported v17.6 branch. KONA 4 is a separate PCIe configuration with its own routing limits. Read the KONA X review and KONA 4 assessment, then find this same earlier-inclusive Mac/SDI/1080p60/PCIe request.

With no capture-rate minimum, earlier-inclusive Mac SDI/PCIe options still need model-specific rate checks. KONA LHe Plus has one SDI source through AJA Control Room; its v18 manual covers Intel and Apple silicon, but does not guarantee a particular frame rate for an open-rate request. KONA X is another PCIe option, while KONA XM is not listed for Mac. Compare KONA 4 for its different four-link 4K routing. Find this same earlier-inclusive Mac SDI/PCIe request.

Adding a 1080p60 capture minimum excludes Corvid 1 because its exact documented ceiling is 1080p30. KONA X remains one documented Control Room option; standalone KONA 4 is a distinct PCIe card with separate four-link 4K routing. Read the Corvid 1 assessment, KONA X assessment and KONA 4 assessment, then find this same earlier-inclusive Mac/SDI/1080p60/PCIe request.

Model references

Turn your setup details into a shortlist

Build my shortlist →