Question / Help Would like to enable Browser Source Hardware Acceleration OBS

[aalan]

It's really weird because I was able to get this working for my StreamElements overlay on older versions of obs, but then I had to do a complete wipe of windows 10 and reconfigure my stuff OBS stuff from scratch.

But when I want to use Browser Source Hardware Acceleration, the browser source doesn't display.

I know that if I disable it, it works. But it'll spike my CPU usage to 25-35% whenever a notification is triggered, I know that when I have Browser Source Hardware Acceleration enabled, I always have a good consistent 10-15% CPU usage no matter what browser source notifications are triggered.

It's also weird because enabling Browser Source Hardware Acceleration works when you open OBS as an administrator, but I'd like to still run it without running it as admin because I use another program called Actual Windows Manager along side OBS to mirror and ghost Chat and Twitch Activity Feed windows on my second monitor, so if I run it as admin, it won't run the program along with it.

yeah... that's it, would absolutely appreciate if I can get some help :)

Great work on 25.0.1!

https://obsproject.com/logs/9yG4SDTMxty2bejm

 

[aalan]

lol I got it to work lol,

for anyone who had the same problem as me, if you're using OBS STUDIO 64 bit, try switching to 32 bit.

haha, I knew I always could do this. I'm just so stupid that i was using OBS 64 the whole time (no offense for those using 64 bit obs)

anyways, bless all of yalls hearts!!!

 

[FerretBomb]

OBS 64-bit is the default, and has been for quite some time now; 32-bit is still there mostly for those with cheap hardware that only provides 32-bit drivers like some chinesium webcams and capture devices. It sounds like you have another, underlying issue that probably should be resolved, but glad you found a workaround in the meantime!

Note: The OBS.Live plugin is well-known to cause issues and is NOT recommended; it replaces several core components (including the Browser Source) with problematic versions. All of the functionality of OBS.Live exists in main-line standard OBS Studio at this point (though some does need to be added as Custom Docks from the View->Docks menu).
Chances are very good that your issue on 64-bit OBS was being caused by having OBS.Live installed.

 

[aalan]

OBS 64-bit is the default, and has been for quite some time now; 32-bit is still there mostly for those with cheap hardware that only provides 32-bit drivers like some chinesium webcams and capture devices. It sounds like you have another, underlying issue that probably should be resolved, but glad you found a workaround in the meantime!

Note: The OBS.Live plugin is well-known to cause issues and is NOT recommended; it replaces several core components (including the Browser Source) with problematic versions. All of the functionality of OBS.Live exists in main-line standard OBS Studio at this point (though some does need to be added as Custom Docks from the View->Docks menu).
Chances are very good that your issue on 64-bit OBS was being caused by having OBS.Live installed.

Oh damn, heyyo, it's weird now. I reinstalled OBS 64 bit and it worked, but when I reopened it; the overlay didn't show up. So then I reinstalled the 32 bit again and it did the same thing when I just reinstalled the 64bit ver.
I was able to get it working in a weird way though,

So to get what I wanted to work, Actual Windows Manager has a thing where you can pause the program,

so what I did is just pause the program, open OBS and wait till all the windows are loaded, then unpause the program.

this way, I can have browser hardware acceleration for my StreamElements overlay on while having Actual Windows Manager running.

I think my problem is like super specific and weird, but I figured if there's anyone else using this Actual Windows Manager along side OBS for mirroring purposes and anything related to Actual Windows Manager. But I'd figure I'd just have this out just in case there's an actual solution to this or for those who are struggling through the same issue as me lol.

At least now, there's some sort of concrete solution for this, it's still a little weird and tedious, but better than nothing :)

if I find a better solution or someone else has one, i'm all ears and i'll let ya'll know.

 

[FerretBomb]

@aalan Most likely "Actual Windows Manager" is a process hook/injector, which absolutely cause conflicts with OBS; generally if more than one program is trying to inject a process hook into a single program, it's not guaranteed to work, and will normally fail. This is why stuff like MSI Afterburner shouldn't be used. There's a known-conflicts list, but it doesn't appear your application is on it yet. Likely it isn't used by too many so hasn't popped up as a problem before.
Still strongly advised to uninstall OBS.Live, in any case.

 

[aalan]

@aalan Most likely "Actual Windows Manager" is a process hook/injector, which absolutely cause conflicts with OBS; generally if more than one program is trying to inject a process hook into a single program, it's not guaranteed to work, and will normally fail. This is why stuff like MSI Afterburner shouldn't be used. There's a known-conflicts list, but it doesn't appear your application is on it yet. Likely it isn't used by too many so hasn't popped up as a problem before.
Still strongly advised to uninstall OBS.Live, in any case.

I probably should've told you this earlier, but I was never using OBS.live in the first place.
The only thing i'm using from StreamElements is the browser source overlay for alerts.

I've tried it before, but then I realized the regular twitch's activity feed from OBS is way better (and more adjustable).
I don't think i'll be using OBS.live for a while anyways.

 

[Paul74]

Try to do this:
follow this guide:

Laptop Troubleshooting

OBS Studio - Free and open source software for live streaming and screen recording - obsproject/obs-studio

obsproject.com

and set everything to use high performance gpu (so not the integrated graphic).
leave enabled Chrome hardware acceleration.
leave enabled OBS browser hardware acceleration in advanced settings.

 

[nathanlejeune]

I am having the same issue and have been digging for over a week to figure it out. Mac Catalina and the browser source freezes when plugged in from SE to OBS. WebM files play fine if dragged and dropped but not if done through SE browser source.

 

[FerretBomb]

I am having the same issue and have been digging for over a week to figure it out. Mac Catalina and the browser source freezes when plugged in from SE to OBS. WebM files play fine if dragged and dropped but not if done through SE browser source.

You'd have better luck asking in the Mac support forum. This is the Windows support forum. Issues may present with similar symptoms, but the causes and fixes are going to be completely different.