Continuity Counter mismatch error when Adaptation Field Control is set to 0x2.
Currently I am working with MPEGTS-Muxer,Specifically, I'm focusing on the behavior of the continuity counter (CC) with PCR packets. According to the MPEGTS standard, when the adaptation field control (AFC) is set to "adaptation field only, no payload" (as is the case with PCR packets), the continuity counter doesn't need to be incremented. In my current setup, I'm transmitting PCR packets with the CC set to zero, reflecting this understanding. However, when I inspect the captured traffic in Wireshark, the expert information indicates nine missing TS frames. This seems to suggest that Wireshark expects the CC of the PCR packet to be incremented as well. My question is: Can this Wireshark warning be safely ignored, or is my understanding of the CC behavior with PCR packets incorrect? I have attached the screenshot for the reference. Please let me know if I can provide addtional information. Video PID and PCR_PID are same- 0x64.
Comments
Please update the question with the output of
wireshark -vorHelp->About Wireshark:Wireshark.If you can provide a sample capture, place it on a public file share (Dropbox, Google, Microsoft, ...) and update the question with a link to it.
thanks for your time.I got reply to be precise answer from tHacker from Discord.
https://discord.com/channels/88921418...