[FFmpeg-devel] [PATCH 1/4] mxfenc: explicitly truncate continuity count.

Michael Niedermayer michaelni at gmx.at
Tue Oct 16 03:02:46 CEST 2012


On Mon, Oct 15, 2012 at 05:59:27PM +0200, Tomas Härdin wrote:
> On Mon, 2012-10-15 at 16:07 +0200, Michael Niedermayer wrote:
> > The field is intended to overflow and have only its low 16bits stored.
> > This commit avoids the implicit truncation and clarifies that its
> > intended and not a bug
> > 
> > Approved-by: Tjoppen
> 
> For completeness and posterity I'll quote the relevant spec, S326m
> section 7.6 ("Continuity count"):
> 
> > The continuity count word consists of 2 bytes allow-
> > ing a number to be created by a modulo 65536
> > counter (bits C15 to C0 in figure 7). The continuity
> > count shall increment by 1 for each newly transmit-
> > ted content package with the same SDTI source and
> > destination addresses. The continuity count may
> > be used to detect whether the content package
> > sequence has been broken by an operation such as
> > a routing switch.

added
patch 1/4 applied

thanks

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20121016/eacccbe1/attachment.asc>


More information about the ffmpeg-devel mailing list