You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AnduinOS - Appimage build Missing Encoders linux ffmpeg_vaapi_tex, obs_qsv11_v2 #1720
Thanks for the report and the screenshot! That dialog means your imported profile uses two encoders that this OBS didn't register at startup. They're missing for different reasons:
Intel QSV (obs_qsv11_v2): this one is expected for now. The AppImage doesn't include the QSV plugin yet, because we haven't been able to test it on Intel hardware. Until it's added, pick another encoder for the setting that used QSV (Settings → Output): x264 always works, and VA-API will too once it shows up (see below).
VA-API (ffmpeg_vaapi_tex): this should work. The AppImage includes VA-API and uses your system's own VA-API driver, so OBS only offers it when that driver can encode H.264. We checked the released AppImage on Ubuntu 24.04 with a working driver, and the encoder shows up there. So something on your system is probably missing or not set up. Could you check these?
Run vainfo in a terminal (it's in the vainfo package) and paste the output. Look for VAProfileH264...: VAEntrypointEncSlice lines. If there are none, the driver can't encode H.264.
On an Intel GPU, the driver is usually intel-media-va-driver (or intel-media-va-driver-non-free). On AMD it's mesa-va-drivers.
Tell us your GPU model, and whether your previous OBS was the Flatpak, the PPA or something else. The Flatpak brings its own VA-API drivers, so VA-API could have worked there even without them on your system.
Attach the OBS log: Help → Log Files → Show Log Files opens the folder; drag the newest file into a comment here. The lines starting with hostlib: and VAAPI: show what OBS found.
We're also working on making the Missing Encoders dialog so it gives the actual reason ("Module obs-qsv11 not loaded", or "No VA-API device that can encode this format was found") instead of "Unknown".
Thanks, that output explains it. VA-API isn't working on your system itself, not just in OBS: vainfo finds both Intel drivers (iHD and i965) but neither can start (va_openDriver() returns -1), so every program that uses VA-API will fail the same way. OBS then has no VA-API encoder to offer, which is why the profile's ffmpeg_vaapi_tex encoder shows as missing.
Two quick checks will tell us why:
Which GPU is in use, and which kernel driver it has:
lspci -k | grep -EA3 'VGA|3D|Display'
If it's Intel, whether the media driver package is the full one:
apt list --installed 2>/dev/null | grep -E 'intel-media-va-driver|i965-va-driver'
What to do depends on the result:
NVIDIA GPU: VA-API encoding isn't available there. Use the NVENC encoder in Settings → Output instead.
AMD GPU: install mesa-va-drivers. VA-API should then show VAEntrypointEncSlice in vainfo, and the encoder will appear in OBS.
Intel GPU (Kernel driver in use: i915 or xe): install intel-media-va-driver-non-free, then run vainfo again. If it still fails, LIBVA_DRIVER_NAME=iHD vainfo (or =i965 on older chips, roughly before 2016) shows which one your chip needs.
Once vainfo lists VAProfileH264...: VAEntrypointEncSlice, restart OBS and the VA-API encoder should be there. QSV (obs_qsv11_v2) will still be missing in the AppImage for now, as mentioned before. In the meantime, x264 works for both streaming and recording.
Claiming: #1720 for the Missing Encoders dialog change (it names why each encoder is missing instead of "Unknown"). The QSV and VA-API availability themselves are separate.
Here is my screenshot the driver my iGPU uses on my Mini Intel PC Shows i915.
But i do use QuickSync as that works a lot better for my Streaming Performance, but didn't OBS-Rust also use QuickSync or was that removed after this Project was started?
Also the commands You told me earlier don't work idk How but would this screenshot help.
Thanks, the screenshot helps a lot: an Intel HD Graphics 530 (Skylake) on the i915 driver is supported by both Intel VA-API drivers, so vainfo should work there.
QuickSync: it wasn't removed. The AppImage has simply never included the QSV plugin, because we haven't been able to test it on Intel hardware yet. The QuickSync encoder in your screenshot is most likely from your other OBS install (the Flatpak, for example), which brings its own Intel drivers. That's also why VA-API works for that OBS but not for vainfo on your system. Your setup is exactly the hardware we'd need to test QSV in the AppImage, so I've noted it.
VA-API: one command that shows why the driver doesn't start. Paste it into a terminal and post what it prints:
LIBVA_MESSAGING_LEVEL=2 LIBVA_DRIVER_NAME=iHD vainfo 2>&1 | head -20
(If the earlier commands printed "command not found" or nothing at all, tell us what they printed. That's useful too.)
Separately, the Missing Encoders dialog no longer says "Unknown": from the next release it says why each encoder is missing (QSV module not loaded, or no VA-API driver that can encode the format).
I Took another screenshot the command you provided worked but idk whats different with this vainfo and the one from earlier, But here is the output i received.
Thanks, that narrows it down. The iHD driver is found but refuses to start, and libva gives no reason. On an HD 530 that usually means it can't open the GPU's render device. Two more commands, posting what they print:
ls -l /dev/dri/ ; groups
vainfo --display drm --device /dev/dri/renderD128
The first shows whether your user can access the render device; the device should belong to the render (or video) group, and that group should appear in your groups line. The second tries VA-API without going through Wayland.
If render isn't in your groups, sudo usermod -aG render $USER, then log out and back in, should fix it.
If the second command works but plain vainfo doesn't, it's the Wayland path, and OBS will still be able to use VA-API.
That's it: your user isn't in the render or video group (groups shows only your own group and sudo), and /dev/dri/renderD128 belongs to render. So the VA-API driver can't open the GPU and gives up with that unhelpful -1. (The + on those device files means a desktop login can sometimes get access anyway; an SSH session never does.)
To fix it:
sudo usermod -aG render,video $USER
Then log out and back in (or reboot) so the new groups take effect, and run vainfo again. It should list VAProfileH264...: VAEntrypointEncSlice lines. After that, start the OBS AppImage again: the VA-API encoder (ffmpeg_vaapi_tex) should be available, and you can pick it in Settings → Output instead of QuickSync.
QSV in the AppImage is still separate; your HD 530 would be a good machine to test it on once we have a build with it.
Thanks for trying that. The groups were part of it but not all of it: your user can reach the GPU now, yet both drivers still refuse to start. That points at the driver files themselves, either a library they depend on is missing, or they don't match your libva version (1.23). This shows which:
If the first part prints any "not found" lines, those libraries are missing (often libigdgmm12). Installing them, or reinstalling intel-media-va-driver-non-free, should fix it.
The second part lists the installed versions, so we can see whether the Intel driver and libva are from the same release.
Either way, keep the render/video groups. They're needed once the driver starts.
So the remaining work is entirely #1863, which is hardware-gated. Linking it as a dependency so this issue stops showing up as a free ready unit; it can close when #1863 lands.
Closing this as resolved for the reporter's support case: the VA-API half was a host driver/render-group problem that the reporter fixed on their machine, and the QSV half needs the AppImage to ship obs-qsv11, which is tracked, not a defect in this report.
The dialog improvements that came out of this report (naming the cause and the fix for a missing VA-API/QSV encoder) landed in #1841/#1862. Nothing in this issue is an open worker unit.
Activity
rdoupe commentedon Oct 22, 2026
Thanks for the report and the screenshot! That dialog means your imported profile uses two encoders that this OBS didn't register at startup. They're missing for different reasons:
Intel QSV (
obs_qsv11_v2): this one is expected for now. The AppImage doesn't include the QSV plugin yet, because we haven't been able to test it on Intel hardware. Until it's added, pick another encoder for the setting that used QSV (Settings → Output): x264 always works, and VA-API will too once it shows up (see below).VA-API (
ffmpeg_vaapi_tex): this should work. The AppImage includes VA-API and uses your system's own VA-API driver, so OBS only offers it when that driver can encode H.264. We checked the released AppImage on Ubuntu 24.04 with a working driver, and the encoder shows up there. So something on your system is probably missing or not set up. Could you check these?vainfoin a terminal (it's in thevainfopackage) and paste the output. Look forVAProfileH264...: VAEntrypointEncSlicelines. If there are none, the driver can't encode H.264.intel-media-va-driver(orintel-media-va-driver-non-free). On AMD it'smesa-va-drivers.hostlib:andVAAPI:show what OBS found.We're also working on making the Missing Encoders dialog so it gives the actual reason ("Module obs-qsv11 not loaded", or "No VA-API device that can encode this format was found") instead of "Unknown".
tinyplayerss commentedon Oct 22, 2026
Here are my Outputs:
rdoupe commentedon Oct 22, 2026
Thanks, that output explains it. VA-API isn't working on your system itself, not just in OBS:
vainfofinds both Intel drivers (iHDandi965) but neither can start (va_openDriver() returns -1), so every program that uses VA-API will fail the same way. OBS then has no VA-API encoder to offer, which is why the profile'sffmpeg_vaapi_texencoder shows as missing.Two quick checks will tell us why:
What to do depends on the result:
mesa-va-drivers. VA-API should then showVAEntrypointEncSliceinvainfo, and the encoder will appear in OBS.Kernel driver in use: i915orxe): installintel-media-va-driver-non-free, then runvainfoagain. If it still fails,LIBVA_DRIVER_NAME=iHD vainfo(or=i965on older chips, roughly before 2016) shows which one your chip needs.Once
vainfolistsVAProfileH264...: VAEntrypointEncSlice, restart OBS and the VA-API encoder should be there. QSV (obs_qsv11_v2) will still be missing in the AppImage for now, as mentioned before. In the meantime, x264 works for both streaming and recording.rdoupe commentedon Oct 22, 2026
Claiming: #1720 for the Missing Encoders dialog change (it names why each encoder is missing instead of "Unknown"). The QSV and VA-API availability themselves are separate.
frontend: Say why a VA-API or QSV encoder from a profile is missing
frontend: Say why a VA-API or QSV encoder from a profile is missing (o…
tinyplayerss commentedon Oct 22, 2026
Here is my screenshot the driver my iGPU uses on my Mini Intel PC Shows i915.
But i do use QuickSync as that works a lot better for my Streaming Performance, but didn't OBS-Rust also use QuickSync or was that removed after this Project was started?
Also the commands You told me earlier don't work idk How but would this screenshot help.
rdoupe commentedon Oct 22, 2026
Thanks, the screenshot helps a lot: an Intel HD Graphics 530 (Skylake) on the
i915driver is supported by both Intel VA-API drivers, sovainfoshould work there.QuickSync: it wasn't removed. The AppImage has simply never included the QSV plugin, because we haven't been able to test it on Intel hardware yet. The QuickSync encoder in your screenshot is most likely from your other OBS install (the Flatpak, for example), which brings its own Intel drivers. That's also why VA-API works for that OBS but not for
vainfoon your system. Your setup is exactly the hardware we'd need to test QSV in the AppImage, so I've noted it.VA-API: one command that shows why the driver doesn't start. Paste it into a terminal and post what it prints:
(If the earlier commands printed "command not found" or nothing at all, tell us what they printed. That's useful too.)
Separately, the Missing Encoders dialog no longer says "Unknown": from the next release it says why each encoder is missing (QSV module not loaded, or no VA-API driver that can encode the format).
tinyplayerss commentedon Oct 22, 2026
I Took another screenshot the command you provided worked but idk whats different with this vainfo and the one from earlier, But here is the output i received.
rdoupe commentedon Oct 22, 2026
Thanks, that narrows it down. The iHD driver is found but refuses to start, and libva gives no reason. On an HD 530 that usually means it can't open the GPU's render device. Two more commands, posting what they print:
The first shows whether your user can access the render device; the device should belong to the
render(orvideo) group, and that group should appear in yourgroupsline. The second tries VA-API without going through Wayland.renderisn't in your groups,sudo usermod -aG render $USER, then log out and back in, should fix it.vainfodoesn't, it's the Wayland path, and OBS will still be able to use VA-API.tinyplayerss commentedon Oct 22, 2026
Heres another output i add both commands so its one screenshot. And i SSHed into my Linux machine to make the process easier
rdoupe commentedon Oct 22, 2026
That's it: your user isn't in the
renderorvideogroup (groupsshows only your own group andsudo), and/dev/dri/renderD128belongs torender. So the VA-API driver can't open the GPU and gives up with that unhelpful-1. (The+on those device files means a desktop login can sometimes get access anyway; an SSH session never does.)To fix it:
Then log out and back in (or reboot) so the new groups take effect, and run
vainfoagain. It should listVAProfileH264...: VAEntrypointEncSlicelines. After that, start the OBS AppImage again: the VA-API encoder (ffmpeg_vaapi_tex) should be available, and you can pick it in Settings → Output instead of QuickSync.QSV in the AppImage is still separate; your HD 530 would be a good machine to test it on once we have a build with it.
tinyplayerss commentedon Oct 22, 2026
Ok i rebooted and logged back in ran the Same two commands again from earlier so this means it should now Work without the errors right?
rdoupe commentedon Oct 22, 2026
Thanks for trying that. The groups were part of it but not all of it: your user can reach the GPU now, yet both drivers still refuse to start. That points at the driver files themselves, either a library they depend on is missing, or they don't match your libva version (1.23). This shows which:
libigdgmm12). Installing them, or reinstallingintel-media-va-driver-non-free, should fix it.Either way, keep the
render/videogroups. They're needed once the driver starts.17 remaining items
zackees commentedon Oct 28, 2026
Tick: the two missing-encoder halves are already tracked elsewhere
Checked this issue against master and the follow-up chain; nothing here is a free worker unit.
ffmpeg_vaapi_tex): landed asEncoderMissing.VAAPI.NotSupportedin frontend: Say why a VA-API or QSV encoder from a profile is missing #1841 and the host-cause dialog in frontend, appimage: Tell the user how to fix a missing VA-API encoder (driver not installed, no render group, no encode entrypoint) #1862 (closed).obs_qsv11_v2): the AppImage leavesobs-qsv11out on purpose (build-aux/appimage/README.md: the host libvpl probe cannot run in CI), so shipping it is appimage: Investigate and ship Intel QSV, validated once on real hardware and pinned by a recorded fixture #1863 (--qsv true, the hostlib/oneVPL path, and a recorded fixture from real Intel hardware).So the remaining work is entirely #1863, which is hardware-gated. Linking it as a dependency so this issue stops showing up as a free
readyunit; it can close when #1863 lands.Verified on master at
cb2dcd16(2026-10-28).zackees commentedon Oct 29, 2026
Closing this as resolved for the reporter's support case: the VA-API half was a host driver/
render-group problem that the reporter fixed on their machine, and the QSV half needs the AppImage to shipobs-qsv11, which is tracked, not a defect in this report.Follow-ups that carry the remaining work:
The dialog improvements that came out of this report (naming the cause and the fix for a missing VA-API/QSV encoder) landed in #1841/#1862. Nothing in this issue is an open worker unit.