HandBrake

Depends on the input video. I have seen much better results with ICQ in two videos and a much worse result in one video with QSTranscode at the same bitrate. For the worse video I had to use ICQ 28 whilst the other two I could use ICQ 21 to achieve the same bitrate of 5000 Kbps.

API 1.8 itself should be final. I have a slightly older WHQL driver with API 1.8 from some OEM. The QuickSyncOptions wiki isn't updated it seems, I don't know what to do in the new nightly.

Intel released a new driver which supports API 1.8.


https://downloadcenter.intel.com/Detail ... ldID=23644
https://communities.intel.com/message/226042#226042

I think so too, h264 should have priority. HEVC could be interesting nervertheless for quality comparisons with h264. I guess we won't see hardware support before Skylake. ICQ means intelligent constant quality algorithm...can be combined with LookAhead.

What is the Intel Media SDK? The Intel® Media Software Development Kit (Intel® Media SDK) is a cross-platform application programming interface (API) for developing consumer and professional media applications, including video editing and processing, media conversion, streaming and playback, and vi...

@gmb: this is not helping. It is irrelevant if this is a QS Hardware or not. It makes a huge difference if it is based on Intels Quicksync or based on some crappy third party vendor solutions and as you can see this is causing issues in Handbrake. And even when it works it surely makes a huge diffe...

They recommended fps=GopPicSize? What is the reason behind this exactly? Do they think it gives better quality? Intel official GopPicSize is 256. For better understanding it would be important to know why one or some people from Intel doesn't follow Intels own Media SDK default GopPicSize. I mean th...

[17:50:42] Intel Quick Sync Video support: yes [17:50:42] - Intel Media SDK hardware: API 1.8 (minimum: 1.3) [17:50:42] - Intel Media SDK software: API 1.7 (minimum: 1.3) API 1.8 driver already found here: http://www.station-drivers.com/index.php/articles/713-intel-hd-iris-graphics-version-15-36-0-3...

i am sure it is using Hardware Encoder. all the specs say it too, this SoC has a 1080p HW Encoder (http://www.intel.com/content/www/us/en/processors/atom/atom-z2760-consumer-tablets-brief.html), it is not named Quicksync per se (maybe due to licence problems), but it is working using the _Default_ ...

Once again default settings are broken. Best quality gives fps=GopPicSize.

Once again, Z2760 does not support Quicksync. No GenX graphics and no dedicated Intel h264 encoder is included. Definitely not in hardware. Bay Trail-T Atom is the first with Quicksync support and Gen7 graphics unit.

Atom Z2760 does not support Quicksync. There is no Intel graphics in it, just a PowerVR graphics. First Atom with Intel graphics and Quicksync support is Bay Trail Z3xxx.

What CPU? His 3570k goes up to 1150 Mhz in default state. I had a 3570k before I switched to Haswell, way below 1 Ghz is abnormal. Occasionally spikes below 1 Ghz are possible, I assumed we talk about an average frequency. A 5 sec interval is meaningless though, not accurate enough. With disabled Qu...

He was doing QSV encode, but *software* decode. High CPU usage would be expected in this scenario. He hasn't posted an activity log for his latest attempts, so there is no point in speculating what might be happening with those encodes. He told 90% CPU usage while doing a Quicksync encode+decode. 8...

Such a high CPU is not normal for Quicksync Hardware. In several hundreds of videos I never saw 90% CPU load. Is there a video sample I can try?

Here... HandBrake svn5912 (Nightly Build) - 64bit Version OS: Microsoft Windows NT 6.1.7601 Service Pack 1 CPU: Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz Ram: 8082 MB, GPU Information: Intel(R) HD Graphics 4600 - 10.18.10.3355 NVIDIA GeForce GTX 660 Ti - 9.18.13.3193 Screen: 1920x1080 Temp Dir: C:\Use...

The new Handbrake version hangs with LA depth over 45, no automatically downgrade anymore.

Surely depends on their implementation, without SDK impossible to say but I assume there must be some advantage. Video+audio encode/decode from one manufacturer looks appealing to me but let's wait for more infos. Hopefully the new SDK comes in January.

Intel told in the forum that AAC encode/decode isn't hardware related, it is supported in the upcoming 2014 SDK through the API. Means it should work on my Haswell which is good news.

Yes but I wonder if it requires Hardware support. Broadwell seems to come with some new Audio stuff onboard, maybe this is somehow related: http://vr-zone.com/articles/meet-intels-hardware-level-siri-killer/60323.html?utm_source=rss&utm_medium=rss&utm_campaign=meet-intels-hardware-level-siri...

AAC Encode and decode is a new Feature in 2014 according to this. Is that purely Media SDK related and works on Haswell or does it need new hardware-->Broadwell? Currently AAC is processed by the CPU afaik.

Ok understand. I just wonder if open gop can help on some videos where Intel suffer from a bad gop behavior. This is Intels main issue imo.

Found it! I cant' believe I have missed it this entire time! Drop down box under video codec. /facepalm its what I get for working on this after being awake for to long cruising along at 130~ fps now Try balanced preset, you should get around 200 fps then. On driver 3257 with CQP bitrate mode TU4 a...

Is it still on your TO-DO list?

maxim_d33 wrote:not answering the question but I would clarify that : SDK,driver and Handbrake might have a different opinions on the settings, including default ones.

You have a different opinion? Why?