Opened 12 years ago Closed 12 years ago #867 closed defect (fixed)Problem with SEI message reading
Description
I am not sure if the problem is in the spec or in the HM9.0rc1 software
First look at line 89 of SEIread.cpp
background: An sei_rbsp can hold more than one sei_message (ref 7.3.2.4)
The software keeps reading sei_messages until the next byte in the stream is equal to 0x80. However, if a sei_message whose payload type, is not the first sei_message in an sei_rbsp, then it would terminate.
There is a sei_message whose payloadType = 128, and that is an sop_description (reference D.1.1)
Feedback would be appreciated.
--James Michener Change History (2)comment:1 Changed 12 years ago by DefaultCC Plugin
comment:2 Changed 12 years ago by davidf
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
|
Yes, that behaviour is problematic. Given that there is only one syndrome as sei_message() is always byte aligned, an additional check for there being one byte remaining is required.
I've committed a fix in r3092