Fix QSV encoder initialization on Intel systems by using VAAPI backend#21
Draft
Fix QSV encoder initialization on Intel systems by using VAAPI backend#21
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
- QSV on Linux requires VAAPI as backend, not standalone initialization - Updated _check_intel_qsv() to init VAAPI first, then derive QSV from it - Changed QSV init from `-init_hw_device qsv=hw` to `-init_hw_device vaapi=va:/dev/dri/renderD128 -init_hw_device qsv=hw@va` - Store vaapi_device in hw_info when QSV is detected - Updated map_codec_to_hw() to use correct QSV initialization in both code paths - Updated startup_tests.py to pass hw_flags to QSV encoder tests - Should fix "Error while opening enc" on Synology NAS with Intel Celeron J3455 Co-authored-by: JMS1717 <43321848+JMS1717@users.noreply.github.com>
- Added Synology NAS Support section under Intel Arc / Integrated Graphics - Included specific docker-compose device mapping example for Synology - Added troubleshooting steps for QSV on Synology NAS - Documented that QSV now uses VAAPI backend for proper initialization - Added encoder test verification steps Co-authored-by: JMS1717 <43321848+JMS1717@users.noreply.github.com>
- Remove trailing whitespace after comment - Remove unused error handling block - Update comment to reflect QSV is now handled separately Co-authored-by: JMS1717 <43321848+JMS1717@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix hardware acceleration issues on Synology NAS
Fix QSV encoder initialization on Intel systems by using VAAPI backend
Dec 22, 2025
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
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.
Intel QSV encoders on Synology NAS (and other Linux systems) were failing with "Error while opening enc" despite hardware detection passing and
/dev/dridevices being mounted. QSV on Linux requires VAAPI as a backend—the code was using standalone initialization which fails on most Intel systems.Changes
QSV initialization pattern changed:
worker/app/hw_detect.py_check_intel_qsv(): Returns(available, device_path)tuple; initializes VAAPI first then derives QSVdetect_hw_accel(): Storesvaapi_devicein hw_info when QSV is detectedmap_codec_to_hw(): Both explicit and fallback paths now use VAAPI-backed QSV initworker/app/startup_tests.pytest_encoder_init(): QSV encoders now receivehw_flagsfor proper device initializationREADME.mdImpact
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.