Question / Help What did you do with OBS 25 ? Stutters in Browser forever !

I was very reluctant in upgrading from OBS 22.0.2 to OBS 25. I was sure it would cause me trouble.
Indeed, after several days testing, I noticed it crashes a lot, and I discovered now an unacceptable thing:
The browser function seems that doesn´t work anymore, at least, in two different computers, I tried to point to any Youtube URL
address, and I notice terrible stutters. When I was using version 22.02 it was fluid, so I made a video for you to see the result
of this comparison. What could be happening ? Look :

 

Narcogen

Active Member

Open OBS. Start an output session (streaming or recording). Observe your issue. Stop the output session. Upload the Current log without quitting OBS.

Any particular reason you avoided 23 and 24 and are now upgrading to 25?
 

Open OBS. Start an output session (streaming or recording). Observe your issue. Stop the output session. Upload the Current log without quitting OBS.

Any particular reason you avoided 23 and 24 and are now upgrading to 25?

Here´s the LOG:

 

Narcogen

Active Member
I doubt anybody is testing new builds of OBS on Windows 7.

That said, you could be using NVENC instead of x264, which might help with any performance issues.

From my experience, the dedicated NDI filter is a performance killer-- just running one of those with program and preview NDI feeds off causes more performance problems than running both the usual program and preview outputs. You're running *15* of them.

17:31:51.341: - filter: 'Dedicated NDI™ output' (ndi_filter)

CBR isn't really intended for recording, it's more for streaming. You should probably use CRF or CQP rate control with a quality setting between 14 (very good) and 23 (pretty good) or just try simple mode with the indistinguishable quality, large file size setting.

If you can't upgrade to Windows 10 you can always downgrade to 23 or 24 and see if those give you the same performance as 22.
 
I doubt anybody is testing new builds of OBS on Windows 7.

That said, you could be using NVENC instead of x264, which might help with any performance issues.

From my experience, the dedicated NDI filter is a performance killer-- just running one of those with program and preview NDI feeds off causes more performance problems than running both the usual program and preview outputs. You're running *15* of them.

17:31:51.341: - filter: 'Dedicated NDI™ output' (ndi_filter)

CBR isn't really intended for recording, it's more for streaming. You should probably use CRF or CQP rate control with a quality setting between 14 (very good) and 23 (pretty good) or just try simple mode with the indistinguishable quality, large file size setting.

If you can't upgrade to Windows 10 you can always downgrade to 23 or 24 and see if those give you the same performance as 22.

Thank you, Narcogen, but these stutters happens even when not recording nor streaming, and even CPU consuming only aroun 24%.
Both OBS have the same configuration.
 

Narcogen

Active Member
I don't know. What are you using those for? Each one of them is using your CPU to lightly compress a source and produce a stream on your LAN of about 100Mbps. Are you doing something with them?
 

Narcogen

Active Member
You removed the plugin but not the filters on the sources. I'm surprised that wouldn't crash.

Put the plugin back, remove the filters, then uninstall the plugin.

17:48:22.674: - filter: 'Dedicated NDI™ output' (ndi_filter)
 

Narcogen

Active Member
Log shows a dfiference between frames drawn and frames output, which means I assume some were dropped but the log does not say why.

17:48:55.101: Output 'adv_file_output': stopping
17:48:55.101: Output 'adv_file_output': Total frames output: 257
17:48:55.101: Output 'adv_file_output': Total drawn frames: 284
 

Narcogen

Active Member
That logfile shows similar dropped frames without cause and no other differences.

17:52:54.118: [ffmpeg muxer: 'adv_file_output'] Writing file 'E:/01 - BOLETIM CHAPADA DO ARARIPE/2020-04-08 17-52-54.mp4'...
17:53:03.832: [ffmpeg muxer: 'adv_file_output'] Output of file 'E:/01 - BOLETIM CHAPADA DO ARARIPE/2020-04-08 17-52-54.mp4' stopped
17:53:03.832: Output 'adv_file_output': stopping
17:53:03.832: Output 'adv_file_output': Total frames output: 262
17:53:03.832: Output 'adv_file_output': Total drawn frames: 292


I don't see any identifiable cause, and the effects aren't happening when the recording is rendered or output, it looks like it's happening when the browser source plays the youtube video.

You might try a workaround like using streamlink to play the video in a dedicated player, and then use that as a source. The browser source isn't really intended for video.
 

Narcogen

Active Member
Another idea:

Go to Settings > Advanced, scroll down to the bottom. Is "Enable browser source hardware acceleration" on? If so, try turning it off. If not, try turning it on. I'm guessing though in 25 it's on by default and previous versions did not have this.
 
You removed the plugin but not the filters on the sources. I'm surprised that wouldn't crash.

Put the plugin back, remove the filters, then uninstall the plugin.

17:48:22.674: - filter: 'Dedicated NDI™ output' (ndi_filter)

I put the Obs-ndi.dll back and went to the control panel and removed everything related to NDI, but it continues to appear on OBS. I noticed that the file obs-ndi.dll continues there...
 

Narcogen

Active Member
You need to remove the dedicated filter you've added to each of the 15 sources. Right click them in the Sources pane, choose Filters from the dropdown, and in the bar on the left click on the "Dedicated NDI Output" and click the '-' key to delete the filter from the source. Do this for each source that in your log lists a Dedicated NDI Output filter.

The problem is that without the plugin and NDI runtime properly installed, it's possible that when you open the Filters page for these sources, OBS might crash. Maybe, maybe not.
 
Another idea:

Go to Settings > Advanced, scroll down to the bottom. Is "Enable browser source hardware acceleration" on? If so, try turning it off. If not, try turning it on. I'm guessing though in 25 it's on by default and previous versions did not have this.

Browser hardware acceleration was disabled by default. I enabled, then, the display went black on the browser. I disabled again.
 
Is the performance the same if you turn off hardware acceleration in chrome itself and capture a window instead of a browser source?

When I capture through window capture, it´s excellent, but I want to capture using browser. Using window capture, I need one more monitor to capture at 1080p and route audio.
 
You need to remove the dedicated filter you've added to each of the 15 sources. Right click them in the Sources pane, choose Filters from the dropdown, and in the bar on the left click on the "Dedicated NDI Output" and click the '-' key to delete the filter from the source. Do this for each source that in your log lists a Dedicated NDI Output filter.

The problem is that without the plugin and NDI runtime properly installed, it's possible that when you open the Filters page for these sources, OBS might crash. Maybe, maybe not.

Now that you said, I think I messed all things, because I uninstalled on the control panel, and now I removed the sources I discovered that were using NDI, but I couldn´t find 15. Perhaps, I´ll have to reinstall in order to uninstall properly, no ?
 
Top