OBS Studio Fails to Expose Proven VP9 QSV Encoder, Leaving Advanced Users Hamstrung by UI Design
VP9 encoding using Intel iGPUs functions perfectly within OBS Studio; the mechanism is accessible via the 'Custom Output (FFmpeg)' settings using the `vp9_qsv` option.
The core fight isn't about if it works—it absolutely does. The issue is usability. Users are furious that the known, functional `vp9_qsv` encoder is locked away, forcing advanced users through the 'Custom Output' workaround instead of being a first-class encoder option in standard OBS modes. asklemmy zeroes in on this feature gap.
The community consensus is clear: the encoder functionality exists and works, but the software's user interface fails to properly integrate it. The fault line is squarely on OBS Studio's UI design, treating a proven encoder option as a hidden technical trick rather than a core feature.
Key Points
VP9 encoding via Intel iGPUs using `vp9_qsv` is technically functional in OBS Studio.
The existence and functionality of `vp9_qsv` in Custom Output (FFmpeg) is confirmed.
The absence of `vp9_qsv` as a standard, primary encoder option is a critical usability flaw.
asklemmy argues that hiding a working encoder feature in Custom Output creates an unacceptable feature gap.
The technical depth of the discussion points to a UI oversight, not an encoding failure.
The analysis suggests the limitation is an 'UI integration oversight rather than an underlying encoding failure.'
High-effort customization in terminal environments (i3, dotfiles) shows a user base demanding similar deep control in their creative software.
While unrelated, threads citing i3 setups and complex Linux customization (somegeek, innocentz3r0) indicate a user segment that expects deep configuration control.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.