Keep codec decoding separate from GPU compute
A runtime that recognises a GPU does not establish that an editor can decode a particular clip. Before changing a system, describe the media and the exact application environment. This is an evidence collection procedure; no Resolve or GPU benchmark was run for it.

1. Record the application version, edition, operating system, driver and runtime independently. Keep a vendor support statement distinct from a community configuration or a successful local launch.
2. Identify one source clip: container, video codec, profile, bit depth, chroma subsampling, resolution, frame rate and audio codec. The filename extension alone is insufficient.
3. Check the codec list for that exact application version, operating system and edition. A decode restriction is not resolved merely by passing a compute-library example.
4. If you can lawfully test the environment, keep the original clip unchanged and record import, playback and export separately. Without that test, leave every performance field “not measured”.

Media identity — fictional record: MOV container; H.264 video; 10-bit; 4:2:2; 3840 × 2160; 25 fps. These are example fields, not a supported-format claim.
Decode question: Does this Resolve version and edition on this OS support this codec/profile combination? Save the matching vendor document and its date.
Compute question: Which GPU and runtime does the application actually use for effects? Record its own diagnostic, not another program’s GPU detection.
Separate observations: Import __; playback __; effects __; export __. Current result for this worksheet: not measured.
Next useful request: Send the environment card and a permitted, non-sensitive sample to the relevant support channel; do not publish private source footage.

Media identity — fictional record: ____________________
Decode question: ____________________
Compute question: ____________________
Separate observations: ____________________
Next useful request: ____________________
This record prevents a codec problem from being reported as proven GPU incompatibility, or a working compute sample from being reported as proven video acceleration.

Blackmagic Design — official support and versioned documents — https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion
AMD — ROCm compatibility documentation — https://rocm.docs.amd.com/en/latest/compatibility/compatibility-matrix.html