I found the problem. FFmpeg is corrupting the last B-frame at the end of cuts. It shows up during
subsequent concatenation. Why it's happening is unknown of course.
There is no workaround that I can conceive of.
--Mark.
000 PTS video 1 video 2
< 504197456 504204
I don't know how "DTS" became "000". Sorry. It's 3AM and I'm a little punchy.
I found the problem. FFmpeg is corrupting the last B-frame at the end of cuts. It shows up during
subsequent concatenation. Why it's happening is unknown of course.
There is no workaround that I can conceive of.
--M
On 2024-02-18 01:52 pm, Mark Filipak wrote:
I don't know how "DTS" became "000". Sorry. It's 3AM and I'm a little
punchy.
I found the problem. FFmpeg is corrupting the last B-frame at the end
of cuts. It shows up during subsequent concatenation. Why it's
happening is unknown of course.
Th
On 2024-02-18 09:59 pm, Mark Filipak wrote:
On 18/02/2024 05.09, Gyan Doshi wrote:
Add -mpegts_flags +initial_discontinuity to get rid of the corrupt
packet messages. This may or may not get rid of the glitches.
Regards,
Gyan
Hey, Gyan,
No effect whatsoever. Same message, same glitches
Hi,
I have to record lectures to preserve quality (i.e. legibility of letters)
and reduce file size, both to maximum possible extent.
In our lectures, only 2 things happen - either tutor is full screen or the
slides are fullscreen. Obviously, there is no time pattern when slides come
and when tea
On Sun, Feb 18, 2024, 11:04 AM Mark Filipak
wrote:
> On 18/02/2024 11.53, Gyan Doshi via ffmpeg-user wrote:
> > On 2024-02-18 09:59 pm, Mark Filipak wrote:
> >> On 18/02/2024 05.09, Gyan Doshi wrote:
> >>>
> >>> Add -mpegts_flags +initial_discontinuity to get rid of the corrupt
> packet messages.
