Hi,
>But your patch did ;)
Ok, the comments were perhaps slightly misleading -- "invalid" didn't
refer to the stream but to the framing into "items".
>>>How often does the "skipping" message appear? Does it happen while the
>>>file is indexed or when it is exported?
>>
>>
>> It happens wheneve
Hi!
Wolfram Gloger wrote:
> I have found that your "patch #6" (from Aug 6th) disabled an
> "invalidation" of timestamps that prevents the serious "non monotonous
> timestamp" errors with the libavformat muxer (even the one included
> with dvbcut) -- just the hunk in question (*):
>
> --- dvbcut/
I have a 1.1GB mpg file (about 30 minutes) created from a MythTV
capture that I'm trying to cut with DVBCUT. However, at anywhere from
50-70% or so, it ends in a segmentation fault as follows:
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3