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?

z!

_______________________________________________
ffmpeg-user mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".

Reply via email to