Media (Intel® Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools like Intel® oneAPI Video Processing Library and Intel® Media SDK
The Intel Media SDK project is no longer active. For continued support and access to new features, Intel Media SDK users are encouraged to read the transition guide on upgrading from Intel® Media SDK to Intel® Video Processing Library (VPL), and to move to VPL as soon as possible.
For more information, see the VPL website.
3044 Discussions

Inconsistency in the use of PicTimingSEI coding option



I'm using the Media SDK's H264 Software and QSV encoding capabilities.

My problem is has follows:

When I encoded a .mov file using the QSV encoder, Quicktime wasn't able to playback the file, showing a green image for the entire file length. The same settings using the SW encoder generated a file that was perfeclty played back in Quicktime.

After a couple of tests and debugging I found out that the culprit was the mfxExtCodingOption's PicTimingSEI option:

When I disable this option, QSV encoding shows green in Quicktime and when I enable it, everything plays fine (even if I do not encode any picture timing). With the SW encoder, everything works fine, regardless of the value of PicTimingSEI.

Why do I have to enable this option so that the encoded footage using QSV can be played back in Quicktime? Is this a bug?


0 Kudos
2 Replies

Hi Daniel,

Quicktime is known to be very sensitive including, timestamps, SEI and profiles. Based on that it may be hard to locate the root cause.

Can you please share the details about your Media SDK encoder configuration and also the method you use for muxing the stream into the mov container?


0 Kudos

Hi Petter,

Thanks for your answer.

My concern is that I don't understand what could be the differences between encoding in SW and encoding in QSV (since it's only in QSV that I see the bug).

I've attached an mp4 files enocded using QSV. I've also attached the logs using the media SDK tracer.

It will be nice to have some input one what I might be doing wrong.


0 Kudos