The VideoLAN Forums

Hello,

I need help with a problem using frame-next. When you use it too many times and then press play, the decoder will skip a bunch of pictures saying "main input debug: Decoder buffering done in 0 ms" and "main decoder warning: early picture skipped". The video will then freeze for 10-15 seconds before resuming. It can also freeze after saying "main input debug: Decoder buffering done in 0 ms", without the early picture skips.

I am running it on Windows 7 pro, with an i5. The video I am playing is a .ts file, mpeg2. It happens sporadically, it can happen after 10 presses of frame-next, or after 100. If you could point me in the right direction, or if you know what I need to change it would be a great help.

Thanks,
Adam


Some output:
....
[02d26100] main input debug: EsOutFrameNext consummed 33 ms
[02d26100] main input warning: buffering, ignoring 'frame next'
[02d26100] main input debug: Stream buffering done (14373 ms in 16734 ms)
[02d26100] main input debug: EsOutFrameNext consummed 33 ms
[02d26100] main input debug: Stream buffering done (14410 ms in 16983 ms)
[02d26100] main input debug: EsOutFrameNext consummed 33 ms
[02d26100] main input warning: buffering, ignoring 'frame next'
[02d26100] main input debug: Stream buffering done (14447 ms in 17232 ms)
[02d26100] main input debug: EsOutFrameNext consummed 33 ms
<-------------------------- PRESSED PLAY ---------------------------->
[02d91c88] direct3d vout display debug: Created 96x96 texture for OSD
[02d26100] main input debug: Stream buffering done (14484 ms in 14352 ms)
[02d26100] main input debug: Decoder buffering done in 0 ms
[02e57510] main decoder warning: early picture skipped
[02e57510] main decoder warning: early picture skipped
[02e57510] main decoder warning: early picture skipped
[02e57510] main decoder warning: early picture skipped
[02e57510] main decoder warning: early picture skipped
[02e57510] main decoder warning: early picture skipped
<-------------------------------Freezes------------------------------->

Yes, known issue. Noone has found the deadlock, since it is quite hard to find.