Question / Help Unable to broadcast in 1080p - 720p fine.

T

Tallsquall

New Member
I updated my NVIDIA drivers and I claim it has broken something in my .dll files for OBS but just for 1080p, Still fine for 720p. and didn't want to go poking around and mess with something that breaks it for 720p as well

I reinstalled OBS saving my scenes and profiles hoping the fresh install would correct it, but still not working

Here is what I claim is the relevant information in the log, but here is the link as well.

11:46:32.648: video settings reset:
11:46:32.648: base resolution: 1920x1080
11:46:32.648: output resolution: 1920x1080
11:46:32.648: downscale filter: Bilinear
11:46:32.648: fps: 60/1
11:46:32.648: format: NV12
11:46:32.658: Audio monitoring device:
11:46:32.658: name: Default
11:46:32.658: id: default
11:46:32.658: ---------------------------------
11:46:32.660: Required module function 'obs_module_load' in module '../../obs-plugins/32bit/chrome_elf.dll' not found, loading of module failed
11:46:32.667: [CoreAudio encoder]: Adding CoreAudio AAC encoder
11:46:32.669: [AMF] Encountered Exception during AMF initialization: Unable to load 'amfrt32.dll', error code 126.
11:46:32.669: Failed to initialize module 'enc-amf.dll'
11:46:32.678: Required module function 'obs_module_load' in module '../../obs-plugins/32bit/libcef.dll' not found, loading of module failed
11:46:32.678: Required module function 'obs_module_load' in module '../../obs-plugins/32bit/libEGL.dll' not found, loading of module failed
11:46:32.679: Required module function 'obs_module_load' in module '../../obs-plugins/32bit/libGLESv2.dll' not found, loading of module failed
11:46:32.680: Failed to load 'en-US' text for module: 'obs-browser.dll'
11:46:32.680: [browser_source: 'Version: 1.29.0']
11:46:32.684: NVENC supported
11:46:32.760: Couldn't find VLC installation, VLC video source disabled
11:46:32.766: No blackmagic support

https://gist.github.com/anonymous/1b5c29e274efca155cf26b97f0490cb6

Thanks!
 
c3r1c3

c3r1c3

Member
1. That log is incomplete (i.e. it doesn't have any profiler info or shows the result of you streaming).
2. A 4-core system that's gaming and streaming will almost never be able to do 1920x1080@60p.
3. Use a 2nd PC (and the NDI plugin) or buy a 6-core+ System.
4. Using a slower-sounding preset will use more CPU.
5. Why did you mess with the buffer size?
 
T

Tallsquall

New Member
1) I don't get an error it acts like it is streaming but there is no output, I have to hard exit the program. I guess it might eventually crash,I could give that a try.

2) I stream D&D so I am just capturing Zoom (video conference) and Roll20 (online game table)

3) above

4) showing CPU at 16% - 18% at 720p

5) reccomemded size I found for my type of stream.

The big thing it it literally all worked a day before. I can try to screen cap what I am seeing
 
c3r1c3

c3r1c3

Member
Please post a link to a clean log with profiler information. First restart OBS, then start your stream/recording for ~30 seconds and stop it again. Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc. When you're done, close OBS, Open OBS, and select Help > Log Files > Upload Last Log File. Copy the URL and paste it here.
 
c3r1c3

c3r1c3

Member
Okay, then let's try something:
1. Set the x264 preset to ultrafast.
2. Make sure the recording format is MKV
3. Set the resolution-fps to 1920x1080@60p.
4. Make sure that the recording setting is set to "Same as stream"

Now do a test record and see what happens.
 
T

Tallsquall

New Member
So don't know if this helps in diagnosis:

Bottom left hand corner "stream health" LIVE: counts up like normal REC: Counts like normal CPU: 3.3%-3.5% 60.00 fps

but no colored square and kb/s: stays at 0
 
S

sam686

Member
Try using 64 bit OBS-studio.

Log shows: [x264 encoder: 'streaming_h264'] encode failed. This can happen when it ran out of memory, which can easily happen in 32 bit program.

Log also shows: (NOTE: 32bit programs cannot use more than 3gb), but it is actually limited to 2 GB because obs32.exe LAA (Large Address Aware) flag is disabled. If LAA was enabled, 32-bit program can go up to 4 GB on 64 bit windows. There is some third party program that can view LLA and enable LAA flag, but ideally should have been enabled at compile time.

Fast preset at 1920x1080 in 8-thread CPU requires 1.3 GB 145 MB or lots of RAM. (1920x1080*1.5(4:2:0 colorspace)*(12(threads) + 30(rc-lookahead) + 3(bframes))
If you need use 32 bit OBS-studio for any reason, to reduce memory usage, just switch to SuperFast preset as your CPU probably cannot handle 1080p 60fps anyway, or you can use custom x264 rc-lookahead=0.

Detailed x264 differences of presets, https://www.google.com/search?q=x264+preset+reference
 
Last edited:
S

sam686

Member
Tallsquall said:
https://gist.github.com/c17f25dab1e2b6acaed90ed836bda509
Click to expand...
Your most recent log now shows: OBS 20.0.1 (64bit, windows), unlike your previous logs. With 64 bit, fewer out of memory errors. Lots of sources is probably why 64 bit OBS-studio is needed. It isn't showing any dropped frames in this log so it might be fine as it is.

I miscalculated how much total memory encoder might use, but its nice to see 64 bit OBS fixed your x264 1080p encoder problem.
 
You must log in or register to reply here.
Top