obsproject / obsproject/obs-studio
Custom Output (FFMPEG) vaapi encoder crashes on init FFMPEG 4.4
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
Operating System Info
Other
Other OS
Fedora 35
OBS Studio Version
27.1.3
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/cf95rQ7oRBI3w8up
OBS Studio Crash Log URL
No response
Expected Behavior
To be able to record with hardware acceleration while selecting Custom output(FFmpeg).
Current Behavior
I am trying to set up hardware accelerated encoding via vaapi and trying to pass vaapi_device=/dev/dri/renderD128 to ffmpeg but when i start recording OBS it will crash. In logs there will be Failed to set vaapi_device=/dev/dri/renderD128
I tried to write it to muxer setting or video setting but it crash in both cases. As far i understand vaapi_device is not video encoder /muxer settings. And there is no other option to pass variable.
Steps to Reproduce
- Settings from screenshot
- Start recording and crash OBS

Anything else we should know?
I found different https://github.com/obsproject/obs-studio/issues/2296#issuecomment-840957925 that this is not possible, but issue was closed anyway. Yes i saw last comment but it's not working as you can see from my settings
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash using OBS Studio 27.1.3 on Fedora 35 with Custom Output (FFmpeg) and vaapi_device=/dev/dri/renderD128, then inspect the linked OBS log for the failure. Compare behavior when the setting is supplied as a muxer or video setting. Done means recording no longer crashes and the supported vaapi configuration behaves as documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100