Hardware video frames: verify the CPU filter transfer boundary

Inspect capabilities and the actual processing path

Retain the authorized source and record codec, bit depth and intended filtering. ffmpeg -hwaccels lists compiled acceleration methods, not proof that every corresponding device or driver works. Check the installed decoder and selected device in the actual command’s result. An encoder’s hardware support is also separate from whether the source can be decoded into that device representation.

Inspect ffmpeg -h filter=hwdownload and the applicable upload or hardware-filter documentation. Decide whether processing remains on the device or crosses to a CPU filter. A supported hardware scale filter and an ordinary scale filter can require different inputs. Do not assume one generic format option supplies every device’s transfer representation.

Choose a supported, bounded transfer test

For an actually supported QSV decoding path with an eight-bit NV12 transfer, an illustrative diagnostic derivative is ffmpeg -n -hwaccel qsv -hwaccel_output_format qsv -t 5 -i source.mp4 -map 0:v:0 -vf "hwdownload, format=nv12, scale=640: -2" -an -c:v libx264 review-transfer.mp4. It is conditional on the actual decoder, device and transfer format, and writes a selected video-only software-encoded test.

This is not a universal command for ten-bit input, every operating system or every acceleration API. A hardware upload instead moves a supported software representation toward a configured device, with its own context requirements. If the requested transfer fails, preserve the error stage and review the supported formats or a suitable software path rather than substituting an incompatible format and claiming successful acceleration.

Verify output interpretation and resource behavior

Open the saved derivative and compare meaningful scenes against the retained parent. Inspect dimensions, bit depth and color interpretation and check movement and duration. A successful transfer does not prove that the chosen conversion retained every precision or color property. The explicit scaling and encoding in the example are derivative changes, not an unchanged master copy.

Record the FFmpeg build, actual device path and accepted transfer format. Keep tests bounded and preserve normal resource protections; do not expose an entire hardware device or disable security merely to make an optional accelerator available. SocialVidDownloader does not promise this QSV transfer graph or universal GPU acceleration. Its working utilities retain their actual implementation and limits. An unavailable device is a reported local path limitation, not proof that the source recording is corrupt or that a fabricated output may be returned.

Worked example

Example: a software scale filter receives device frames and fails at the transfer boundary. The operator identifies the supported download format and makes a short checked derivative, or uses a valid software path. Merely listing QSV in compiled capabilities is never reported as evidence that the actual device processed the file.

Related guidance

• FFmpeg filter outputs: map the intended branch explicitly
• Video color fields: primaries, transfer and matrix interpretation

Sources and verification

• FFmpeg hardware methods and device options
• FFmpeg hardware upload and download filters

Reviewed 2026-10-13. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.