Hauppauge HD PVR USB H.264 video capture devices
A USB 2.0 capture box from Hauppauge that takes component, composite, or S-Video input from devices like the Xbox 360, PlayStation 3, and cable or satellite set-top boxes and encodes it in hardware as H.264 at up to 1080i. It was popular with gamers and home-theater hobbyists in the late 2000s and early 2010s, before HDMI capture and the HD PVR 2 superseded it.
recommendation
Worth keeping but documenting its niche, because the original HD PVR is no longer in Hauppauge's current lineup yet still receives genuine upstream attention, including a 2022 bug fix and a 2026 endpoint-lookup refactor. Some users still run these boxes for legacy console and set-top capture, so removal would be premature even though deployments are low.
repository signals
sources
- lore.kernel.org
The driver still receives upstream maintenance in 2026; this patch refactors endpoint lookup in hdpvr-core.c rather than proposing removal.
- lore.kernel.org
The driver also saw a bug-fix patch in 2022, indicating nonzero ongoing maintenance over the last five years.
- hauppauge.com
Hauppauge's current game-recorder lineup lists newer products such as HD PVR 2 and HD PVR 60, but not the original HD PVR/HD PVR Gaming Edition.
- hauppauge.com
The supported hardware is the original Hauppauge HD PVR family: a USB 2.0 H.264 encoder for Xbox 360/PS3, cable/satellite set-top boxes, and component/composite/S-Video capture up to 1080i.
codex reasoning notes (technical)
Local `rg` over drivers/media/usb/hdpvr shows Kconfig/MODULE_DESCRIPTION naming the device as the Hauppauge HD PVR USB driver. `lore_file_timeline(path=drivers/media/usb/hdpvr/hdpvr-core.c)` produced the two cited lore URLs and showed recent 2026 maintenance, with no removal signal in the returned events. Hauppauge URLs were obtained via web search and then opened; the current product-list page omits the original HD PVR while the old HD PVR page remains available and clearly targets Xbox 360/PS3/component-video-era workflows. That points to legacy but still occasionally deployed capture hardware, so `keep-annotate` fits better than deprecate/remove.