Annoying mpegts logs about "Packet Corrupt" when playing back out segments
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 283
- Forks
- 72
- Avg merge
- 27m
- Merged PRs (30d)
- 1
Description
While playing back some of the [transcoded renditions](https://livepeerworkspace.slack.com/files/U012ZT0KRPX/F01GUN85URX/3ppin.tar), the mpegts demuxer complains a lot -
`[mpegts @ 0x7f6e88005bc0] Packet corrupt (stream = 0, dts = 813902940).`
Even though the player has no issues playing it back.
**Todo**
Figure out root cause or mitigation of the logs if it's not a real issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing playback with the transcoded renditions in the linked 3ppin.tar archive and observe the mpegts demuxer output. Investigate whether the repeated "Packet corrupt" messages correspond to a real playback problem; done means identifying the root cause or defining a mitigation for the misleading logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100