[Mp4-tech] Re: PCR Discontinuity Issues

[Song]

Dear Mohit
I don't think that H.222 or ISO13818 can tell us how to process an error stream. It only defines what is a correct stream.
It is up to demux designer to process that according to actual situation.
Sorry I cannot give you more advice about that.
Regards.
Song
Message: 4
Date: Tue, 18 Jul 2023 14:31:48 +0530
From: "Mohit Agarwal" <magarwal NeoMagic.com>
Subject: RE: [Mp4-tech] Re: PCR Discontinuity Issues
To: <mp4-tech lists.mpegif.org>
Message-ID: <000001c6aa48$cf231d30$841fa8c0 pcmagarwal>
Content-Type: text/plain; charset="us-ascii"
Thanks Song,
I have a doubt regarding Continuity Counter(cc).
Consider the following Base case and a variant mentioned at end of mail.
<cc=0> <pcr_flag == 0, discontinuity_indicator = 0> // old system time
<cc=1>   <pcr_flag == 0, discontinuity_indicator = 1> // new system time
begin
<cc=2> <pcr_flag == 1, discontinuity_indicator = 1> //  new PCR set.
<cc=3> <pcr_flag == 0, discontinuity_indicator = 0> 
Acc to 2.4.3.5 of H.222.0 there can be a CC error in Case of PCR_PID Packet
also,but
This err will occur only in packet in which system discontinuity will occur.
What I think this CC error is totally dependent on the Network.If there are
some attenuations in the 
Network then only can a packet be dropped.This CC err can occur in any
packet.
Now consider the case when the Packet containing the new PCR set gets
dropped.Then How will
Demuxer will come to know of the new time base.Will it to wait till next
discontinuity in PCR to occur,then new 
Time base to arrive or there is some way???
<cc=0> <pcr_flag == 0, discontinuity_indicator = 0> // old system time
<cc=1>   <pcr_flag == 0, discontinuity_indicator = 1> // new system time
begin
/////////////<cc=2> packet gets dropped
<cc=3> <pcr_flag == 0, discontinuity_indicator = 0> 
Regards
Mohit