Ask Your Question
0

Continuity Counter mismatch error when Adaptation Field Control is set to 0x2.

asked 2024-06-24 15:08:51 +0000

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.

edit retag flag offensive close merge delete

Comments

Please update the question with the output of wireshark -v or Help->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.

Chuckc gravatar imageChuckc ( 2024-06-24 15:13:40 +0000 )edit

thanks for your time.I got reply to be precise answer from tHacker from Discord.

dhaksh64 gravatar imagedhaksh64 ( 2024-06-24 15:33:59 +0000 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2024-06-24 20:09:50 +0000

Jaap gravatar image

CC can't just be set to zero, it should contain the last used value.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2024-06-24 15:08:51 +0000

Seen: 79 times

Last updated: Jun 24