- Thread starter
- #181
But I'm not 100% sure if it is really needed. Probably it is better not to flush since it would cause much bigger wholes in the timeline (all queued data in decoders and renderers would be dropped).
My feeling too - the cure would be worse than the problem. I can think of a better workaround which might help.
What comes to discontinuity handling, the old TsReader has worked with short discontinues at least. I have one .ts file that is having hundreds of different types of dropped data gaps - audio renderer is passing that "reference" without any issues. So the assumption about short gaps causing the renderer queue to behave badly is probably wrong. It must be something else.
A log with the sample timestamps would reduce the quessing a lot
OK - question for Wouter1971 - if you use the standard MP 1.2.1/1.2.2 TsReader.ax + MP AudioRenderer, does the A/V sync problem happen ?
Tourettes - can I download the corruption test file from somewhere ?
Tony