Add dual-octet VP8 picture ID to payload descriptor #4660
Merged
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.
Plan for VP8 Dual-Octet Picture ID Implementation
Based on PR #4515, I have applied the following minimal changes:
Reference: #4659 (formerly #4515)
Changes Made:
vpx_packetizer.c:
unsigned int picture_idfield topjmedia_vpx_packetizerstructvpx.c:
Review Comments Addressed:
(pktz->cfg.fmt_id == PJMEDIA_FORMAT_VP8? 4: 1)Validation Results:
The implementation follows RFC 7741 section 4.2 for the dual-octet PictureID format.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.