Opened 10 years ago Closed 10 years ago #1355 closed defect (fixed)CAVLC encoder decoder mismatch
Description
Read, never written:
Written, never read:
Change History (7)comment:1 Changed 10 years ago by DefaultCC Plugin
comment:2 in reply to: ↑ description Changed 10 years ago by ksuehringcomment:3 Changed 10 years ago by tung.nguyen
You are comparing different parts of T(Enc/Dec)CAVLC.
TEncCAVLC @ 284:
TDecCAVLC @ 363:
comment:4 Changed 10 years ago by kolya
Yes you're right.
Me set the tag incorrectly.
My comment is about HM-dev, revision 4243. There is no reading of that kind there. comment:5 follow-up: ↓ 6 Changed 10 years ago by karlsharman
In HM-dev, revision 4243, the line numbers for the two highlighted sections are practically the same:
comment:6 in reply to: ↑ 5 Changed 10 years ago by kolya
Agreed again. This is due to stupid automatic parser, who cannot treat "cb_qp_adjustnemt" and "cb_qp_adjustment" as the same %)
Replying to karlsharman:
comment:7 Changed 10 years ago by karlsharman
Fixed spelling mistake in debug trace string in r4244. Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber, Participant
|
This is an extension mechanism, which is already used in the multi-layer extensions (syntax element name in the spec: slice_segment_header_extension_data_byte).
We don't have meaningful semantics defined for profiles specified in Annex A, so there is no point in writing data into this section (except if you want to test that a decoder properly ignores the content according to the spec). But such a test should be a conformance bitstream, not a common HM functionality.