[FFmpeg-user] Need info on ATSC3 stream capture going wrong

Carl Zwanzig cpz at tuunq.com
Sun Apr 14 18:42:19 EEST 2019

On 4/14/2019 7:14 AM, Deron wrote:
> What appears to happen is some audio timestamp drift error is noticed, 
> compensation is applied that perhaps has a math sign error, a whole lot of 
> silence is inserted, the incoming data is ignored because of that silence, 
> and the input buffer is overflowed.

I wonder, and this is just a WAG, if that stream has enough uncorrected bit 
errors spread around that the demux/decoder can't figure out where the data 
blocks start and then picks a likely spot that's wrong. Can you pick out the 
error stats for different channels and compare them?


More information about the ffmpeg-user mailing list