fix: skip GL compositor when only Mesa software rendering is available#482
Merged
fix: skip GL compositor when only Mesa software rendering is available#482
Conversation
Auto-selection checked if glvideomixerelement existed in the GStreamer registry, but Mesa makes it always available via llvmpipe. This caused auto mode to pick the GL path even without a real GPU, which is slower than the CPU compositor due to GL API overhead on software rendering. Add gpu::has_hardware_gl() that checks the GL renderer string probed at startup and rejects llvmpipe/softpipe/swrast. Both vision mixer and compositor block auto-selection now require a hardware GL renderer before choosing glvideomixerelement. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
glvideomixerelementexisted in the GStreamer registry, but Mesa makes it always available via llvmpipe software renderingcompositordue to GL API overhead on software renderinggpu::has_hardware_gl()that checks the GL renderer string probed at startup and rejects llvmpipe/softpipe/swrast — both vision mixer and compositor block now require a hardware GL renderer before choosingglvideomixerelementTest plan
"gpu"preference still forces GL even on Mesa (no behavior change for explicit selection)🤖 Generated with Claude Code