It looks like early CUVID did not support Extended_SAR. Your file displays fine in my system with 2053 and latest drivers. It also displays fine using 2052 with latest drivers, which tends to confirm the theory. Here is the info log for the sample:
Code: Select all
Stream Type: Transport [188]
Video Type: AVC
Profile: Main
Level: 3
Coded Size: 864x480
SAR: 1280:1281
Display Size: 863x480
Frame Rate: 25.000000 fps
Colorimetry: Unknown [2]
Frame Structure:
Frame Type:
Coded Number: 360
Playback Number: 360
Frame Repeats: 0
Field Repeats: 0
Bitrate:
Bitrate (Avg):
Bitrate (Max):
Audio Stream: 101: AAC Audio
Elapsed: 0:00:00
Remain: 0:00:00
FPS:
Info: Finished!
257: C:\Users\Don\Downloads\ad PID 101 DELAY 66665380ms.aac
The SAR of 1280:1281 is not a standard one and is rather unusual. It can be specified using the Extended_SAR syntax element. You can look at your other working files and see if any specify this extended SAR of 1280:1281. I suspect you won't find any. It's probably academic though, because if the theory is borne out, there's nothing you can do about it without upgrading your card, which will allow you to run the latest driver.