Media (Intel® oneAPI Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools from Intel. This includes Intel® oneAPI Video Processing Library and Intel® Media SDK.
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
2904 Discussions

H264 encoder gives invalid DecodeTimeStamp on old hardware

CyberDemon
Beginner
104 Views

Tested with 3 systems:

2100 (Windows 10, HD Graphics, mfxVer=1.4), 2500K (Windows 8.1, HD Graphics 3000, mfxVer=1.4), 3570K (Windows 10, HD Graphics 4000, mfxVer=1.7).

Test 1:
mfx.InfoMFX.GopRefDist = 1

All three systems give IPPP... sequence, output mfxBitstream->TimeStamp is correct (increasing for every next frame according input data) but DecodeTimeStamp is correct only on 3570 CPU (and equals to TimeStamp). Both 2100 and 2500 CPUs give DecodeTimeStamp == 0.

Ok, This can be fixed by checking DecodeTimeStamp and ignoring it.

But what can I do if GopRefDist is greater than "1"? In this case I get B-frames and again DecodeTimeStamp is Zero. Frames are not coming in input order so I cannot fix this during runtime.

What's wrong? Hardware, drivers, my hands? :)

0 Kudos
1 Solution
Harshdeep_B_Intel
104 Views

Hi Eduard, 

2100 (Windows 10, HD Graphics, mfxVer=1.4), 2500K (Windows 8.1, HD Graphics 3000, mfxVer=1.4) ->These systems a 2nd generation generation machine are VERY VERY old. Please take a look at MediaSDK release notes on minimum hardware requirements. 

3570K (Windows 10, HD Graphics 4000, mfxVer=1.7) -> This is 3rd generation machine which also old, and no longer actively driver bug fixes effort for this platform. So, I suggest upgrading your hardware to any latest 6th/5th/4th generation machine and trying out on latest machine. Let us know if issue is still observable on latest hardware. 

Thanks,

 

View solution in original post

2 Replies
Harshdeep_B_Intel
105 Views

Hi Eduard, 

2100 (Windows 10, HD Graphics, mfxVer=1.4), 2500K (Windows 8.1, HD Graphics 3000, mfxVer=1.4) ->These systems a 2nd generation generation machine are VERY VERY old. Please take a look at MediaSDK release notes on minimum hardware requirements. 

3570K (Windows 10, HD Graphics 4000, mfxVer=1.7) -> This is 3rd generation machine which also old, and no longer actively driver bug fixes effort for this platform. So, I suggest upgrading your hardware to any latest 6th/5th/4th generation machine and trying out on latest machine. Let us know if issue is still observable on latest hardware. 

Thanks,

 

View solution in original post

CyberDemon
Beginner
104 Views

Harsh Jain (Intel) wrote:

2100 (Windows 10, HD Graphics, mfxVer=1.4), 2500K (Windows 8.1, HD Graphics 3000, mfxVer=1.4) ->These systems a 2nd generation generation machine are VERY VERY old. Please take a look at MediaSDK release notes on minimum hardware requirements. 

3570K (Windows 10, HD Graphics 4000, mfxVer=1.7) -> This is 3rd generation machine which also old, and no longer actively driver bug fixes effort for this platform. So, I suggest upgrading your hardware to any latest 6th/5th/4th generation machine and trying out on latest machine. Let us know if issue is still observable on latest hardware. 

As I wrote before, it works fine on 3570, the question was only about "very very" old CPUs and they're installed in customers PCs so we cannot upgrade them :)

Anyway, "upgrading hardware" is suitable answer in my case. Thanks!

 

Reply