OCP-7182 - H.264 MSDK and QSV decoders fail to link with h264parse in parsebin pipeline, causing "not-linked" errors #326
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
Parsebin auto-plugging selects higher priority decoders (vah264dec, vaapih264dec) instead of the explicitly requested MSDK/QSV decoders due to their rank being none. This causes not-linked errors when testing MSDK/QSV conformance. Use explicit h264parse element instead of parsebin to ensure the correct decoder is used in the pipeline.
rgonzalezfluendo
approved these changes
Dec 16, 2025
mdimopoulos
approved these changes
Dec 16, 2025
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.
Parsebin auto-plugging selects higher-priority decoders (vah264dec, vaapih264dec) instead of the explicitly requested MSDK/QSV decoders because their rank is set to none. This causes not-linked errors when testing MSDK/QSV conformance.