Question / Help Can't encode webm with Vp9 and vorbis [STILL UNANSWERED]

trooose

New Member
I get this crash error: Unhandled exception: c0000005
I am attempting to record minecraft with game capture with my sample rate at 48k with vorbis vp9 and webm.
Any ideas why this is happening?

The program crashes when I hit Stop Recording.

Also my graphics card is a geforce 150 MX and I use it for the encoding aswell as minecraft.
Any help would be appreciated!
 

trooose

New Member
crash report:
 

Attachments

  • Crash 2018-02-04 11-41-49.txt
    81.2 KB · Views: 32
Last edited:

pkv

Developer
i can confirm the crash.
But it occurs because the encoding is not fast enough for real-time capture with vp9 which is too demanding. You would need a much better proc than what you have. If you use directly ffmpeg you will get the same issue. it's not an obs related issue.
Frankly you should just record in x264.
 

koala

Active Member
Don't use custom output (ffmpeg). Chose Simple Output mode and chose "High Quality, Medium File Size" at Recording Quality, and "Hardware (QSV)" as Encoder. Choose flv or mkv as Recording Format. If you must have your final video as webm+vorbis, recode to that format with an external program after you finished your recording.
 

trooose

New Member
Also is there any way that I can decrease the quality or something so that my system can handle it?
 
What service are you broadcasting to? Most of the services out there now (YouTube, Twitch, Facebook, etc) use x264 as their video. Is there a specific reason you cannot use that? Your question about "codes that dont require a patent fee" interests me, please explain that aspect.
 

trooose

New Member
none, its a recording Also h264 requires a patent when you get a certain amount of subscribers I believe, I may be wrongly informed though.
 

Osiris

Active Member
H264 does not need a patent fee, not sure why you would think that. The creators of the applications doing the h264 encoding and decoding technically need to pay a fee AFAIK.
 

Osiris

Active Member
It's probably not as simple as I stated, but one thing I know for sure, an end user does not need some license to create h264 videos and put them on YT for example.
 

koala

Active Member
There are 2 parties covered in the h264 license: the entity who sells a h264 encoder and the entity who distributes h264-encoded videos to consumer and charges for this.

Noncommercial use of h264 is free. The distribution of h264 encoders within OBS is free, because OBS itself is free and only has free editions. That's why almost all demo versions of commercial software usually have the h264 encoder removed: the companies doesn't want to pay for encoders they deliver in demo versions. But since OBS is completely free, the h264 encoder within is completely free as well.

Recording a h264 video with OBS is free, because you are not distributing it to end users.
Giving h264-encoded videos away for free is free.
Putting h264-encoded videos to Youtube is free, regardless of you monetizing the video or not, because Youtube isn't consuming (watching) the video. All intermediate steps between creating a video and consuming a video are free.

Youtube is using h264 to distribute videos to the people who watch the video and earns money by doing that, so Youtube has to pay a h264 license for this. You, who created the video and uploaded it to Youtube, don't have to pay. Youtube has to pay. And Youtube does pay and doesn't pass these costs to the uploaders.

So, in essence, you don't have to pay h264 license costs by recording h264 content with OBS. Giving away these videos for free also doesn't come with license fees. Selling these videos to end users require license fees. In case of video download portals, the portals are selling/distributing the videos to the end user, not the uploader, so the uploader doesn't have to pay a h264 license - the download portal has.

This is not a legal advice - it's only what I learnt about the h264 license.
 

Ric404

New Member
Solution (worked for me) - OS: Windows
- Install the current version of OBS (nov/2020 : 26.0.2)
- Download the current SHARED library build of ffmpeg (nov/2020 : 4.3.1) (https://www.gyan.dev/ffmpeg/builds/)
- Extract the contents of the ffmpeg zip file
- Navigate to the \bin folder of ffmpeg
- Copy all the .dll files
- Navigate to C:\Program Files\obs-studio\bin\64bit folder (or where ever you have obs installed)
*optional* backup the original .dll files that have the same filename as the ones copied from ffmpeg (Rename and/or move the original .dll files)
- paste the .dll files extracted from the ffmpeg folder
You can delete the ffmpeg folder if you wish.

Now OBS will work with WEBM: VP9 or VP8 + VORBIS (OPUS still not working)
:-)
 
Top