OBS and chrome>50 HW accelerated incompatibility
Reported by
szof...@gmail.com,
Aug 30 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Install OBS studio on windows 10 with DX3D11: https://obsproject.com/ 2. add a "window capture" to a scene, select the GPU accelerated chrome window 3. be amazed that only an empty black screen occurs. What is the expected behavior? OBS should be able to capture the GPU accelerated chrome window. What went wrong? coming from https://productforums.google.com/forum/#!topic/chrome/hVMQX0S599I it seems that chrome uses DX3D11 in a wrong way so that OBS can't capture its window contents. many people are complaining because of this. I've ran a round with OBS, they pointed fingers at chrome. Then I created the productforum topic, I was pointed at NVIDIA (I have a GTX1018, look at the product forum topic please). Then, NVIDIA people pointed back at OBS/chrome. Please get this right, we can't use OBS to stream this way. My setup is a desktop machine, installed with windows 10, a Palit GTX 1080 (NVIDIA Pascal architecture), and the latest versions of all the involved software installed. Did this work before? Yes people say it worked before chrome 50, supposedly when GPU acceleration arrived. tested it with chrome 49, it works indeed. Chrome version: 52.0.2743.116 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 please have a look at the product forum link I provided. all the necessary information can be found there.
,
Sep 5 2016
bump
,
Sep 19 2016
bump
,
Sep 29 2016
buppity bump
,
Nov 17 2016
Bump-diggity... Still experiencing this issue with Version 54.0.2840.99 m
,
Apr 7 2017
Bump Need this to be fixed.
,
May 3 2017
Still having to do the chrome restart every single time I want to record in OBS: Just tested version 58.0.3029.96 and black screen unless I turn off acceleration.
,
May 4 2017
I too wish for this bug to be fixed.
,
May 17 2017
szoftos@, Could you please confirm this still exists on latest stable-58.0.3029.110 on Windows 10? Thanks..!!
,
May 17 2017
@jmukthavaram just tested, can confirm it still exists on Chrome 58.0.3029.110, OBS 18.0.2. I have an Nvidia GTX 1080 with Game Ready Driver 382.05, and with the latest win10 updates.
,
May 17 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 18 2017
,
May 27 2017
Can confirm this issue still exists for the newest version of OBS. Chrome: 58.0.3029.110 (64-bit) Windows: 10 (64-bit) OBS: 19.0.2
,
Jun 27 2017
From a fresh install of updated Windows 10 64-bit, Chrome (Version 59.0.3071.115 (Official Build) (64-bit)) and OBS Studio 19.0.3 64-bit, the problem is still here.
,
Mar 2 2018
bump please FIX
,
Mar 24 2018
Problem persists with Chrome Version 65.0.3325.181 (official build) (64-Bit) on Windows 10 64bit with Nvidia GeForce GTX 970 using GeForce Game Ready Driver v391.24. BTW: OBS can capture Firefox 59.0.1 with and without HA with zero problems. WebGL performance is about 6 FPS with HA disabled and 16 FPS with HA enabled using the Aquarium demo at 30,000 fish on my machine: http://webglsamples.org/aquarium/aquarium.html The browser source (embedded Chromium) in OBS with --enable-gpu flag to turn on HA (and WebGL) can be used to capture the content, and achieves 12 FPS.
,
Aug 3
Chrome Version 68.0.3440.84 (Official Build) (64-bit) and the issue still persists. I can also confirm that it works on Firefox with hardware acceleration turned on. I personally am also curious what exactly got changed from Chrome 49 to 50 that suddenly made hardware acceleration behave in a completely different way?
,
Aug 4
Alright small update from my side. I've stumbled upon a flag called `--use-angle` that, when I set it to `gl`, causes Chrome to use the OpenGL rendered instead of the default (?) DirectX renderer. With this flag enabled, I am actually able to use the Window capture in OBS. `--use-angle=gl` is the full text you have to put after the target path in the Chrome shortcut.
,
Oct 7
The issue persists in version 69.0.3497.100 (Official Build) (64-bit).
,
Oct 30
The issue still persists in version 70.0.3538.77 (Official Build) (64-bit). I doubt anyone has looked into it yet, have they?
,
Oct 31
Could some one from MTV team please take a look into it as the specified drivers in C#10 are not available with india team. Thanks in advance!
,
Oct 31
,
Oct 31
lordmau5ooo@ could you please provide us with chrome://gpu information. Lopping to Mo as well for inputs.
,
Oct 31
Sure can - I've posted it to Pastebin here: https://pastebin.com/TN6NHrav
,
Nov 2
,
Nov 2
If it helps, here's my chrome://gpu: https://pastebin.com/ef5KksR2
,
Nov 2
,
Nov 16
Hello! I am a developer at Amazon/Twitch and we're running into this same issue with Google Chrome & newer NVIDIA graphics cards (680 or newer). We can successfully capture windows with Firefox. Please help us resolve! Our preferred browser is Google Chrome but we will be forced to recommend alternate browsers for an upcoming product. :( We have successfully captured windows with Chromium but unable to capture with Chrome Beta 71 and Chrome Canary 72.
,
Dec 16
It's been around a month and this problem still occurs even on Version 71.0.3578.98 (Official Build) (64-bit). As stated on this issue, using `--disable-direct-composition` fixes it, but I'm not sure what the side-effects of that would be (if any) https://bugs.chromium.org/p/angleproject/issues/detail?id=1460 |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by szof...@gmail.com
, Aug 30 2016