Doom9's Forum - View Single Post - Intel QuickSync Decoder - HW accelerated FFDShow decoder with video processing

nevcairiel · 5th May 2012, 19:53

Hey Eric,

i found a sample with quite an odd behaviour today.

http://files.1f0.de/samples/h264-qs-timestamp-issue.mkv

When i play this file with LAV in QS mode, it plays too fast (should be 24p, plays at 30p), running out of sync.
I checked the timestamps of the file, and they are fine. Plays fine with software or other hardware codecs too.

For some reason, the QS decoder insists on changing the timestamps, even though i turn off the timestamp mangling flag that you expose.

I'm running driver 2696, happens both on my Ivy and Sandy systems.
I just tried 2656, and the problem does not occur anymore.

The driver dependency makes me believe its the MediaSDK itself causing this, and not your code directly.
Can you maybe check if its something you can turn off, or maybe if the problem is just gone in a newer driver which i don't have yet?

Edit:
2712 is also showing the problem.
Either its a bug in the newer MediaSDK libraries which you should forward, or its a feature thats on by accident?

5th May 2012, 19:53	#1163 \| Link
nevcairiel Registered Developer Join Date: Mar 2010 Location: Hamburg/Germany Posts: 10,348	Hey Eric, i found a sample with quite an odd behaviour today. http://files.1f0.de/samples/h264-qs-timestamp-issue.mkv When i play this file with LAV in QS mode, it plays too fast (should be 24p, plays at 30p), running out of sync. I checked the timestamps of the file, and they are fine. Plays fine with software or other hardware codecs too. For some reason, the QS decoder insists on changing the timestamps, even though i turn off the timestamp mangling flag that you expose. I'm running driver 2696, happens both on my Ivy and Sandy systems. I just tried 2656, and the problem does not occur anymore. The driver dependency makes me believe its the MediaSDK itself causing this, and not your code directly. Can you maybe check if its something you can turn off, or maybe if the problem is just gone in a newer driver which i don't have yet? Edit: 2712 is also showing the problem. Either its a bug in the newer MediaSDK libraries which you should forward, or its a feature thats on by accident? __________________ LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 5th May 2012 at 20:13.