Hello Thibault,
please update the edge264 code for mvc decoding, regarding NAL unit type 24.
NAL unit type 24 should be ignored!
See extract for spec:
NAL unit types 0 and 24..31 may be used as determined by the application. No decoding process for these values of nal_unit_type is specified in this Recommendation | International Standard. Since different applications might use NAL unit types 0 and 24..31 for different purposes, particular care must be exercised in the design of encoders that generate NAL units with nal_unit_type equal to 0 or in the range of 24 to 31, inclusive, and in the design of decoders that interpret the content of NAL units with nal_unit_type equal to 0 or in the range of 24 to 31, inclusive.
I have already samples, where decoding fails, due to nal unit type: 24 # Unkown, see extract from YAML file.
--- # Exodus_Gods_and_Kingsframes120-002.264
- nal_ref_idc: 0
nal_unit_type: 24 # Unknown
nal_res: ENOTSUP
When this issue is solved, I will start with testing of more mvc samples.
Hello Thibault,
please update the edge264 code for mvc decoding, regarding NAL unit type 24.
NAL unit type 24 should be ignored!
See extract for spec:
NAL unit types 0 and 24..31 may be used as determined by the application. No decoding process for these values of nal_unit_type is specified in this Recommendation | International Standard. Since different applications might use NAL unit types 0 and 24..31 for different purposes, particular care must be exercised in the design of encoders that generate NAL units with nal_unit_type equal to 0 or in the range of 24 to 31, inclusive, and in the design of decoders that interpret the content of NAL units with nal_unit_type equal to 0 or in the range of 24 to 31, inclusive.
I have already samples, where decoding fails, due to nal unit type: 24 # Unkown, see extract from YAML file.
--- # Exodus_Gods_and_Kingsframes120-002.264
nal_unit_type: 24 # Unknown
nal_res: ENOTSUP
When this issue is solved, I will start with testing of more mvc samples.