Mark:
On 2024-02-19 17:31, Mark Filipak wrote:
On 19/02/2024 18.49, Jim DeLaHunt wrote:
On 2024-02-19 15:04, Mark Filipak wrote:
If I recall correctly, each of the two segments was a couple hundred
bytes. The two sources total 27 GB and are copyrighted.
If the sources are 27GB, then that is
вт, 20 февр. 2024 г., 05:02 amindfv--- via ffmpeg-user <
ffmpeg-user@ffmpeg.org>:
> On Mon, Feb 19, 2024 at 08:49:14PM +0100, Paul B Mahol wrote:
>
> > Best to create minimal reproducible usecase with all required files to
> reproduce it
>
> By the way, this isn't just for reporting on Trac. For
On Mon, Feb 19, 2024 at 08:49:14PM +0100, Paul B Mahol wrote:
> Best to create minimal reproducible usecase with all required files to
> reproduce it
By the way, this isn't just for reporting on Trac. For most recipients of these
messages (i.e. the people subscribed here) to get anything out
Mark:
On 2024-02-19 15:04, Mark Filipak wrote:
On 19/02/2024 16.45, Jim DeLaHunt wrote:
Mark:
On 2024-02-19 13:23, Mark Filipak wrote:
Best to create minimal reproducible usecase with all required files to
reproduce it, upload it somewhere and link it on ffmpeg trac site.
I did that. It
Mark:
On 2024-02-19 13:23, Mark Filipak wrote:
Best to create minimal reproducible usecase with all required files to
reproduce it, upload it somewhere and link it on ffmpeg trac site.
I did that. It didn't get any interest.
Really, you "did that"? I do not recall that you have created a
On Mon, Feb 19, 2024 at 6:47 PM Mark Filipak
wrote:
> On 19/02/2024 01.16, Greg Oliver wrote:
> > I usually do not chime in on your emails where people flame you for
> writing
> > a book or being a troll because I usually learn something from the
> > discussions.
>
> Hi Greg. I'm not writing a
> On 19 Feb 2024, at 19:23, Reindl Harald wrote:
>
>
>
> Am 19.02.24 um 19:20 schrieb Bouke / edit 'B:
>> My most sincere apologies to the list.
>> I have a mental condition that forces me to indulge in these kind of
>> discussions, while it is clearly pointless.
>> Sorry for the waste of
Am 19.02.24 um 19:20 schrieb Bouke / edit 'B:
My most sincere apologies to the list.
I have a mental condition that forces me to indulge in these kind of
discussions, while it is clearly pointless.
Sorry for the waste of bandwidth / your attention.
I’ll make a message rule filtering out the
>
> On 19 Feb 2024, at 19:14, Mark Filipak wrote:
>
> On 19/02/2024 13.11, Bouke / edit 'B wrote:
>>> On 19 Feb 2024, at 19:04, Mark Filipak wrote:
>>>
>>> On 19/02/2024 12.59, Bouke / edit 'B wrote:
>
> On 19 Feb 2024, at 18:47, Mark Filipak wrote:
>
> I'm not writing a
> On 19 Feb 2024, at 19:04, Mark Filipak wrote:
>
> On 19/02/2024 12.59, Bouke / edit 'B wrote:
>>>
>>> On 19 Feb 2024, at 18:47, Mark Filipak wrote:
>>>
>>> I'm not writing a book.
>>> That's something someone made up.
>> Yes, the ’someone' was you. Search the archives.
>
> No, that was
>
> On 19 Feb 2024, at 18:47, Mark Filipak wrote:
>
> I'm not writing a book.
> That's something someone made up.
Yes, the ’someone' was you. Search the archives.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
When trimming packets and later concatenating packets, ensure that no
packets that are not trimmed from stream of packets and thus are still part
of final file depend on any frame from any dropped/removed stream of
packets for correct glitch-free decoding.
Also ensure that there is no dangling
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
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
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.
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.
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
17 matches
Mail list logo
