feat: add protected transcoding device capability registry - #9
Merged
Merged
Conversation
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.
Summary
Security and compatibility
UnknownVerifierlaunches no runtime command or child process/device-info, and/hwaccel-profilerbehavior remains unchangedRelease notes
Adds the protected hardware-device and codec-capability inventory foundation for future hardware-accelerated HLS and casting. This release does not yet route playback through the GPU and does not add user-facing hardware settings.
Verification
enginefsandserveracross all librqbit targetsExact head:
4cde60b0cc50ad666813a2c5cf28d5ac3cdd68ccFollow-up
Hardware recipe qualification, persistent HLS/casting sessions, device preferences, telemetry, and actual GPU execution remain separate later PRs.