- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From this test and analysis "Quick Sync H.264 Encoding Performance and Quality Test" (which uses q264.exe) here: http://www.tetrachromesoftware.com/q264Test1Analysis/q264test_5.html
The PSNR (quality) vs bitrate trajectory falls off for 1080p above about 4000 Kbps, meaning that increasing the bitrate doesn't increase the quality like one would expect. Lower resolutions don't show this trajectory fall-off. This looks to me like something fundamental, but is there some setting q264.exe could be messing up to cause this?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One thing to keep in mind, is I believe how this works is dramatically different between Haswell and Ivy Bridge, Sandy Bridge.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, thanks, page 4 of the analysis compares those three generations and shows the same trajectory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ryan,
can you please provide the specific encoder configuration you are using for the encode workload where you see observe the quality degradation. You can use the Media SDK tracer tool to fetch the configuration details.
Regards,
Petter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the details Ryan.
We are investigating this and will get back to you shortly.
Regards,
Petter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi again Ryan,
We have studied the behavior for the encoder configuration you provided in further detail.
For configurations with high number of B frames (in your case 4) the HW encoder is known to have limitations with regards to quality on high bit rates. So, in essence this behavior is expected.
You should be getting better results using for instance 2 B-frames. You may also explore other rate control modes than AVBR to see if it produced better results.
Regards,
Petter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
q264 uses the normal GopPicSize, GopRefDist, and IdrInterval parameters in mfxInfoMFX to determine encoded frame types.
Can you clarify what you mean when you say "2 B frames"? Do you mean the number of consecutive B frames? Do you mean reduce the number of consecutive B-frames by setting GopRefDist?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ryan,
Right. The number of B-frames following a P frame can be controlled by the GopRefDist parameter. If you set GopRefDist to 3 you will generate two consecutive B-frames, such as the following pattern IPBBPBBPBBPBB...
BTW. GopRefDist = 1 means no B-frames.
Regards,
Petter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay, thanks. I tried other bitrate control methods and GOP params (including GopRefDist) and saw slight changes in PSNR, but no significant differences.
Ryan
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page