Bug Report [Now tested with 0.12.0] x264 failed to load - 32bit version

C

chrisw10

New Member
Hi guys,

How do I fix this? I've got a big Wii-U stream (well, big for me) starting in about 13 hours and I really would like to have this fixed beforehand if at all possible. Why does this error appear on the 32-bit version but not the 64-bit version? I must use the 32-bit version since the Wii-U only works through my Elgato Gamecapture HD on the 32-bit version.

I've attached several logs. In the meantime I'll continue to troubleshoot.
 

Attachments

  • logs.zip
    13.5 KB · Views: 23
C

chrisw10

New Member
I've narrowed it down to the Elgato being used as a video capture source. It completely fails when I add it as a source. OBS streams fine in 32-bit when it's not used as a source in any scene whatsoever.
 

Attachments

  • 2015-09-11 22-58-11.txt
    27.7 KB · Views: 20
D

DoAGoldeneye

Member
It's been a while since I've used my Elgato (Avermedia LGX ftw! :p), but I remember it was finnicky about how I was using the audio input. I always handled audio and video capturing separately, so for me, disabling the audio captured was a workaround for that. I then routed the audio from my HDMI TV into my PC's Line In and recorded from there.

Seeing as you're in a pinch: If all else fails, you can do a (VERY) basic stream from the Elgato's own software :)
 
C

chrisw10

New Member
Do you see anything in the logs that indicates it's the audio input from the Elgato causing the crash?

I hope to avoid doing a basic stream since I just spent a couple weeks retooling my stream layout to include full motion video and all the things. It would suck to do the stream without them. :(
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
In the future, please do not zip logs - just attach the logs themselves if possible. Also, if you need fast (though not necessarily guaranteed) response, we have a chat.

I'm actually totally confused as to what's going on here. You add the elgato source, and then encoding no longer works for some reason? It would have to be some sort of memory issue. That just completely baffles me.
 
C

chrisw10

New Member
Sure thing, Jim. I wanted to include multiple logs in case there was some weird variance in the cause going on there, so that's why I zipped them. I'll check the chat out if I need an urgent response in the future! Thanks for the tip.

Just to clarify, you're saying it sounds like it's an issue with my hardware and not a software bug?
 
C

chrisw10

New Member
Well, I did a system reinstall (keeping apps and personal files) of Windows 10 and RAM doesn't read as faulty according to Memtest.

One additional detail: OBS doesn't crash completely. There is still a process listed in the Details tab that I have to manually close in order to reopen OBS.

I browsed around the forum today and found a similar issue reported on 9/3 that I hadn't seen when I searched for this issue last weekend. see https://obsproject.com/forum/threads/obs-crashes-entirely-upon-launch.36033/

I too renamed the obs-studio folder to obs-studio-old and allowed OBS to generate a new folder. I added the Elgato as a source and began a test recording and it worked. I'll recreate my original layout and settings and test it again later and will post again if I find any more info. But here, I've attached the logs from today (both before and after) in case there's anything to compare.

Chris
 

Attachments

  • 2015-09-14 20-20-16.txt
    10.9 KB · Views: 17
  • 2015-09-14 20-32-41.txt
    11 KB · Views: 25
C

chrisw10

New Member
Jim said:
In the future, please do not zip logs - just attach the logs themselves if possible. Also, if you need fast (though not necessarily guaranteed) response, we have a chat.

I'm actually totally confused as to what's going on here. You add the elgato source, and then encoding no longer works for some reason? It would have to be some sort of memory issue. That just completely baffles me.
Click to expand...

Hi Jim,

I readded my layout and the same issue arose. So I did some more tests, and I think this is a multi-causal problem created by the interplay of a media source, the Elgato, and the BrowserSource plugin. I also tested using text, but it doesn't seem to be a factor from what I can tell.

I used two scenes. A pre-roll scene that uses multiple instances of Browser Source, text, still images, and a media source (a 776MB 18-minute long h.264-encoded .mp4 video set to loop and to use hardware decoding when available.) I then transitioned to the second scene, which includes the same Browser Source and text instances, then some other still images, a webcam Video Capture Device, and the Elgato GameCapture HD Video Capture Device. When OBS crashes, it crashes upon loading the second scene unless otherwise specified.

Here's the tests I performed. Maybe you can make something of it?

  • When Browser Source, Text, and video are removed as Sources in both scenes, Elgato works. OBS does NOT crash.
  • When Browser Source and video are removed, but not text, Elgato works. OBS does NOT crash.
  • When Browser Source and text are removed, but not video, Elgato does not work. OBS crashes.
  • When Text and video are removed, but not Browser Source, Elgato works. OBS does NOT crash.

  • When Video only is removed, but not text and Browser Source, Elgato does not work. OBS crashes.
  • When Browser Source is removed, but not text and video, Elgato does not work. OBS crashes.
  • When text is removed, but not Browser Source or video, Elgato works and OBS does NOT crash when transitioning from Scene 1 to Scene 2, but crashes when transitioning back to Scene 1.

  • When there is NO BrowserSource Plugin installed, but with all other sources existing, Elgato works. OBS does not crash.

These tests were carried out in OBS 0.11.3. Any thoughts as to what may be going on?
 
Last edited:
D

DoAGoldeneye

Member
Knee-jerk reaction here is: Why not 0.11.4 ? There will always be tiny bugfixes/improvements done between versions which may end up.being significant.
 
C

chrisw10

New Member
The problem exists in 0.11.4 as well. I downgraded initially because of this to see if the problem solved itself. It did not.
 
C

chrisw10

New Member
I re-did the test with a new, simpler layout in 0.12.0, and here's the following to report:

Scene 1 Sources:
Media Source: a 776MB 18-minute long h.264-encoded .mp4 video set to loop

Scene 2 Sources:
Webcam Frame: (PNG w/ transparency)
Webcam Video Capture Device with Image/Mask Blend Filter, which is a black and white PNG file
Bottom Bar: (PNG w/ transparency)
Elgato GameCapture HD Video Capture Device
Background Image (solid PNG)

Here's the results. These tests were carried out while streaming:

Test1:
Without the BrowserSource Plugin, OBS did NOT crash.

Test2: Added BrowserSource Plugin
With the BrowserSource Plugin, OBS crashes, but the process remains running in the background.

Test3: Removed Webcam from Scene 2
OBS does NOT crash. Added Webcam back to scene. Switched to Scene 1. Switched back to Scene 2. OBS crashes, but process remains running in the background.

Test 4: Removed Elgato but preserved Webcam.
OBS does NOT crash. Added Elgato back to scene. Switched to Scene 1. Switched back to Scene 2. OBS crashes, but process remains running in the background.

Test 5: Removed Webcam Image Mask from the Webcam source's filter section.
OBS does NOT crash. Added image mask back to Webcam source's filter section. OBS crashes upon pressing OK to close the Webcam Properties Window , but process remains running in the background.

Test 6: Reconfirm Test 5
Webcam Image Mask from the Webcam source's filter section as still removed, so I did not have to remove it. Re-ran the test. OBS does NOT crash. Added image mask back to Webcam source's filter section. A few seconds pass after pressing OK to close the Webcam Properties Window, THEN OBS crashes, but process remains running in the background.

Test 7: Reconfirm Test 5
Removed Webcam Image Mask from the Webcam source's filter section.
Re-ran the test. OBS does NOT crash. Added image mask back to Webcam source's filter section. A few seconds pass after pressing OK to close the Webcam Properties Window, THEN OBS crashes, but process remains running in the background.

Test 8: Added Image/Mask Blend to static Background Image
OBS crashes, but process remains running in the background.

Hypothesis: It appears that Browser Source does not like the Image/Mask Blend filter.

Attached are logs from Tests 5, 6, and 8. Each one reporting a crash ends with a series of these error messages, which are different from those encountered in my very first report a couple weeks ago.

9:02:14 PM.692: error: get_buffer() failed
9:02:14 PM.692: error: thread_get_buffer() failed
 

Attachments

  • 2015-09-23 20-59-30_test5.txt
    11.8 KB · Views: 26
  • 2015-09-23 21-03-13_test6.txt
    11.5 KB · Views: 31
  • 2015-09-23 21-11-30_test8.txt
    12.4 KB · Views: 32
Last edited:
C

chrisw10

New Member
Thinking I had the error figured out, I removed the image/mask filters and started adding sources again. However, the issue was not solved.

Followup:
Set up layout with the following sources in this order:
Background image (static PNG)
Elgato Video Capture Device
Bottom Bar (PNG with transparency)
Webcam Video Capture Device (this time with NO image/mask blend)
Webcam Frame (PNG with transparency)
Donation - Monthly (Local Text File) with a Crop Filter
Donation - Today (Local Text File) with a Crop Filter
Newest Follow (Browser Source) -- Visibility turned off
Donation - Recents (Local Text File)
Tnotifier (Browser Source)

OBS Crashed during setting up the Tnotifier Browser Source, right when I set the dimensions to 1920x1080.

Test 9: Re-add Tnotifier without massive dimensions. Modified dimensions to 1920x200. OBS did NOT crash. Went to Scene 1. Then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 10: Test scene transitions without adding Tnotifier.
Started streaming from scene 2. OBS did not crash. Transitioned to Scene 1, then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 11: Remove Crop Filters from Text Files
Started streaming from scene 2. OBS did not crash. Transitioned to Scene 1, then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 12: Remove Newest Follow Browser Source, even though it is disabled.
Started streaming from scene 2. OBS did not crash. Transitioned to Scene 1, then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 13: Remove Text Files one at a time until OBS stops crashing
Removed 'Donation - Recents'. Started streaming from scene 2. Transitioned to Scene 1, then back to Scene 2. OBS did NOT crash. Moved 'Donations - Monthly' partway off-screen. Transitioned to Scene 1, then back to Scene 2. OBS did NOT crash. Re-added 'Donation - Recents'. Transitioned to Scene 1, then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 14: Remove another text file other than 'Donation - Recents'
Removed 'Donation - Today'. Started streaming from scene 2. Transitioned to Scene 1, then back to Scene 2. OBS did NOT crash. Re-added 'Donation - Today'. Transitioned to Scene 1, then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 15: Moved text files to my SSD C: Drive
Transitioned to Scene 1, then back to Scene 2. OBS did NOT crash with all three text files present. Added Tnotifier source. Transitioned to Scene 1, then back to Scene 2. OBS did NOT crash. Restarted OBS. Streamed from Scene 2. Transitioned to Scene 1, then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 16: Move all assets to SSD C: Drive and progressively test until OBS crashes.
Started streaming from scene 2. OBS did not crash. Transitioned to Scene 1, then back to Scene 2. OBS crashed, but remained running as a process in the background.

Test 17: Increase Audio and Video Buffers on Scene 1 Video to 30 frames each
Started streaming from scene 2. OBS did not crash. Transitioned to Scene 1, then back to Scene 2. OBS did NOT crash.

Test 18: Added my final source, another BrowserSource for my notifications from beam.pro.
OBS failed to stream, resulting in the original x264 failed to load error. OBS crashes while attempting to stream, but remains running as a process in the background. Increasing Audio and Video buffers to 60 seconds each did not solve the issue.

I'm including logs from Test 9 and Test 16. Two different funky things happened there. The others were pretty similar to the others in that they end with something like these two lines: 9:02:14 PM.692: error: get_buffer() failed; 9:02:14 PM.692: error: thread_get_buffer() failed.

TLDR:
No freakin clue what's going on anymore. Hypothesis is that maybe it IS a memory/file access speed issue and OBS still can't handle everything I'm throwing at it. Xsplit doesn't have this issue, but it does run more slowly. What I do know is that when the Elgato OR BrowserSource is not present, OBS is able to stomach it. But when both are present, it is unable to do so. It can also manage it with both the Elgato and only one Browser Source installed, but only when the video file has higher audio/video buffers and the assets are loaded from an SSD.

Oh and this happens sometimes when I try to modify or add sources: https://gyazo.com/5c75bf3400ac3e87b4c8cef64e66a206
 

Attachments

  • 2015-09-23 22-13-08_test9.txt
    12.3 KB · Views: 32
  • 2015-09-23 23-17-52_test16.txt
    18.1 KB · Views: 28
Last edited:
You must log in or register to reply here.
Top