Changes between Initial Version and Version 1 of Ticket #1224, comment 31
- Timestamp:
- 04/21/2012 06:36:28 PM (14 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1224, comment 31
initial v1 1 I am afraid that solves it: the only difference between these commands is the speed of the encoding process: the first is very slow ({{{veryslow}}} )is a dead giveaway) and the second is very fast ({{{ultrafast}}} is a clue; the very small resolution helps too).1 I am afraid that solves it: the only difference between these commands is the speed of the encoding process: the first is very slow ({{{veryslow}}} is a dead giveaway) and the second is very fast ({{{ultrafast}}} is a clue; the very small resolution helps too). 2 2 3 3 My conclusion is that the problem is that when the encoding command is too slow, the kernel buffer overflows and causes a read error. Now that I know that, I can reproduce the problem, and I see, using strace, that read on the device fails with EOVERFLOW (shame on the MPEG-TS demuxer not to report it).


