how to force HW video decoding?

33 views
Skip to first unread message

Denys Khanzhyiev

unread,
Sep 23, 2013, 3:58:23 AM9/23/13
to node-...@googlegroups.com
It looks like nw.exe does not use hardware video decoding on my system while chrome does.
I get 20-25% cpu load in nw.exe vs 3-7% in chrome on same test file.
I use ffmpegsumo.dll trick.
tested in 0.7.1 and 0.6.3 with corresponding ffmpegsumo versions.

seen chromium flags - there is no flag to force hw video decoding - only disabling available

Denys Khanzhyiev

unread,
Sep 23, 2013, 5:00:07 AM9/23/13
to node-...@googlegroups.com
I also have tested chromium from here
https://download-chromium.appspot.com/
with ffmpegsumo trick. It is the same as chrome 0.29 - video decoding takes less than 10% cpu.

Denys Khanzhyiev

unread,
Sep 25, 2013, 5:47:01 AM9/25/13
to node-...@googlegroups.com

Ok I have discovered it further.
In chrome we have chrome://gpu page to see Graphic feature status.
In node-webkit this page is broken but information could be extracted through devtools:
1. open chrome://gpu in nw
2. open devtools
3. enter in console
var browserBridge = { onGpuInfoUpdate:function(arg){console.log(JSON.stringify(arg,null,1));}};
4. then
chrome.send('browserBridgeInitialized');
5. Tada! You have JSON object describing graphic features of nw.
Same works in chrome.

 here is what I get from nw:
http://pastebin.com/QtLAvJQz
as you see
...
{    "name": "video_decode",    "status": "enabled"   },
...

so flags are ok.

but when I compare it to chrome output
http://pastebin.com/7hAwCMXU
problems array is empty in chrome while in nw

...
"problems": [ { "crBugs": [], "description": "Force compositing mode is off, either disabled at the command line or not supported by the current system.", "webkitBugs": [] } ],
...

any thoughts?

May it cause CPU load difference?

Denys Khanzhyiev

unread,
Sep 25, 2013, 6:27:41 AM9/25/13
to node-...@googlegroups.com
I also have created a gist to see the difference:

https://gist.github.com/xdenser/6697525/revisions

so there are slightly different library verisons
and composition mode as said


2013/9/25 Denys Khanzhyiev <xde...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "node-webkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Denys Khanzhyiev

unread,
Sep 25, 2013, 6:36:26 AM9/25/13
to node-...@googlegroups.com
This is not force compositing mode flag:
I have entered "chromium-args" : "--force-compositing-mode" in manifest and problems array is empty, but CPU load difference with chrome have not gone.


2013/9/25 Denys Khanzhyiev <xde...@gmail.com>
Reply all
Reply to author
Forward
0 new messages