#2909: Make dvbsubs more compliant among stb's
-------------------------------------+-----------------------------------
Reporter: Tommy2d | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Component: avcodec
Version: 1.2.2 | Resolution:
Keywords: dvbsub | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-----------------------------------
Comment (by waider):
It looks like the reserved bits can be 1 or 0 depending on where they are.
The current spec
(https://www.etsi.org/deliver/etsi_en/300700_300799/300743/01.06.01_60/en_300743v010601p.pdf)
says:
> reserved: When used in a clause defining the coded bit stream, this
field indicates that the value may be used for extensions in the future.
Unless specified otherwise within the present document, all "reserved"
bits are expected to be set to "1".
> reserved_zero_future_use: When used in clauses defining the coded bit
stream, this field indicates that the value may be used in future
revisions for ETSI-defined extensions. All "reserved_zero_future_use" bits
are expected to be set to "0".
(Yes, adding an note to a 12-year-old bug report. I happened to be poking
in the spec for something else.)
--
Ticket URL: <https://trac.ffmpeg.org/ticket/2909#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
