On 6/25/2024 11:20 AM, Mark Filipak wrote:
What are you arguing about, z!?
Do you not believe that VLC plays Track_11055.m2ts?
Sigh, read it again. You asserted without foundation that VLC does "do
not depend on ffmpeg" and I pointed out that it does. Nothing more,
nothing less.
You also as
On 26/06/2024 00:10, MacFH - C E Macfarlane - News wrote:
On 25/06/2024 20:17, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 7:55 PM MacFH - C E Macfarlane - News <
n...@macfh.co.uk> wrote:
On 25/06/2024 18:28, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 6:57 PM Mark Filipak
VirusTotal repor
On Tue, Jun 25, 2024 at 9:23 PM Mark Filipak
wrote:
> On 25/06/2024 15.17, Paul B Mahol wrote:
> > On Tue, Jun 25, 2024 at 7:55 PM MacFH - C E Macfarlane - News <
> > n...@macfh.co.uk> wrote:
> >
> >> On 25/06/2024 18:28, Paul B Mahol wrote:
> >>>
> >>> On Tue, Jun 25, 2024 at 6:57 PM Mark Filipa
On 25/06/2024 15.17, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 7:55 PM MacFH - C E Macfarlane - News <
n...@macfh.co.uk> wrote:
On 25/06/2024 18:28, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 6:57 PM Mark Filipak
VirusTotal reports that Google, Sophos, and Ikarus all say that the MSI
con
On Tue, Jun 25, 2024 at 7:55 PM MacFH - C E Macfarlane - News <
n...@macfh.co.uk> wrote:
> On 25/06/2024 18:28, Paul B Mahol wrote:
> >
> > On Tue, Jun 25, 2024 at 6:57 PM Mark Filipak >
> >>
> >> VirusTotal reports that Google, Sophos, and Ikarus all say that the MSI
> >> contains a virus trojan
On 25/06/2024 14.57, Richard Bartczak via ffmpeg-user wrote:
Someone was asked, by the gods.
"One wish, you have for free, what do you like?"
"I want the laughs on my side."
"The gods were rolling with laughter."
"You will get it"
Gloster
Hey, Gloster,
You need to get together with Jim De
Someone was asked, by the gods.
"One wish, you have for free, what do you like?"
"I want the laughs on my side."
"The gods were rolling with laughter."
"You will get it"
Gloster
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscri
Correction: "Ticket_11055.m2ts" was "Track_11055.m2ts".
On 25/06/2024 13.56, Carl Zwanzig wrote:
On 6/25/2024 10:39 AM, Mark Filipak wrote:
VLC and PowerDVD.
VLC? Right in their credits they list ffmpeg (along with many other OS
projects).
What are you arguing about, z!?
Do you not believ
On 25/06/2024 13.56, Carl Zwanzig wrote:
On 6/25/2024 10:39 AM, Mark Filipak wrote:
VLC and PowerDVD.
VLC? Right in their credits they list ffmpeg (along with many other OS
projects).
What are you arguing about, z!?
Do you not believe that VLC plays Track_11055.m2ts?
On 25/06/2024 13.56, Carl Zwanzig wrote:
On 6/25/2024 10:39 AM, Mark Filipak wrote:
VLC and PowerDVD.
VLC? Right in their credits they list ffmpeg (along with many other OS
projects).
It's at the top of the trac page, in the "Summary of the bug". Do you see it,
z!?
Did you put it in the
On 25/06/2024 13.56, Carl Zwanzig wrote:
On 6/25/2024 10:39 AM, Mark Filipak wrote:
VLC and PowerDVD.
VLC? Right in their credits they list ffmpeg (along with many other OS
projects).
It's at the top of the trac page, in the "Summary of the bug". Do you see it,
z!?
Did you put it in the
On 6/25/2024 10:39 AM, Mark Filipak wrote:
VLC and PowerDVD.
VLC? Right in their credits they list ffmpeg (along with many other OS
projects).
It's at the top of the trac page, in the "Summary of
the bug". Do you see it, z!?
Did you put it in the email that I was quoting? No. In the trac
On 25/06/2024 18:28, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 6:57 PM Mark Filipak
VirusTotal reports that Google, Sophos, and Ikarus all say that the MSI
contains a virus trojan. The
other virus scanners _may_ be reporting on the payload, _not_ the MSI.
Its not virus, its just their sil
On 25/06/2024 13.28, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 6:57 PM Mark Filipak
wrote:
On 25/06/2024 12.03, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 5:49 PM Mark Filipak
On 20/06/2024 03.30, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol
wrote:
https://www.jo
On 25/06/2024 13.04, Carl Zwanzig wrote:
On 6/25/2024 9:53 AM, Mark Filipak wrote:
On 25/06/2024 12.28, Carl Zwanzig wrote:
On 6/25/2024 8:51 AM, Mark Filipak wrote:
https://trac.ffmpeg.org/ticket/11055#comment:173
Ticket_11055.m2ts plays correctly and completely by two players that do not
On Tue, Jun 25, 2024 at 6:57 PM Mark Filipak
wrote:
> On 25/06/2024 12.03, Paul B Mahol wrote:
> > On Tue, Jun 25, 2024 at 5:49 PM Mark Filipak >
> > wrote:
> >
> >> On 20/06/2024 03.30, Paul B Mahol wrote:
> >>> On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol
> wrote:
>
> https://www.j
On 6/25/2024 9:53 AM, Mark Filipak wrote:
On 25/06/2024 12.28, Carl Zwanzig wrote:
On 6/25/2024 8:51 AM, Mark Filipak wrote:
https://trac.ffmpeg.org/ticket/11055#comment:173
Ticket_11055.m2ts plays correctly and completely by two players
that do not depend on FFmpeg.
Which ones? That's p
On 25/06/2024 12.28, Carl Zwanzig wrote:
On 6/25/2024 8:51 AM, Mark Filipak wrote:
https://trac.ffmpeg.org/ticket/11055#comment:173
Ticket_11055.m2ts plays correctly and completely by two players that do not
depend on FFmpeg.
Which ones? That's part of traceability (and proper bug reporti
On 25/06/2024 12.03, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 5:49 PM Mark Filipak
wrote:
On 20/06/2024 03.30, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol wrote:
https://www.jongbel.com/automated-validation/mpeg-2-video-validation/
Mark, did you tried this one or
On 6/25/2024 8:51 AM, Mark Filipak wrote:
https://trac.ffmpeg.org/ticket/11055#comment:173
Ticket_11055.m2ts plays correctly and completely by two players that
do not depend on FFmpeg.
Which ones? That's part of traceability (and proper bug reporting).
When are we going to get on with
On 25/06/2024 17:03, Paul B Mahol wrote:
On Tue, Jun 25, 2024 at 5:49 PM Mark Filipak
wrote:
On 20/06/2024 03.30, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol wrote:
https://www.jongbel.com/automated-validation/mpeg-2-video-validation/
The above URL is too vague to b
On Tue, Jun 25, 2024 at 5:49 PM Mark Filipak
wrote:
> On 20/06/2024 03.30, Paul B Mahol wrote:
> > On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol wrote:
> >>
> >> https://www.jongbel.com/automated-validation/mpeg-2-video-validation/
> >
> > Mark, did you tried this one or any alternative one to m
On Tue, Jun 25, 2024 at 5:52 PM Mark Filipak
wrote:
> https://trac.ffmpeg.org/ticket/11055#comment:173
>
>Ticket_11055.m2ts plays correctly and completely by two players that do
> not depend on FFmpeg.
>
>Ticket_11055.m2ts has 99 frames. All frames are listed correctly by
> framecrc.
>
>
https://trac.ffmpeg.org/ticket/11055#comment:173
Ticket_11055.m2ts plays correctly and completely by two players that do not
depend on FFmpeg.
Ticket_11055.m2ts has 99 frames. All frames are listed correctly by framecrc.
Ticket_11055.m2ts has 99 frames. All frames are listed correctly by
On 20/06/2024 03.30, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol wrote:
https://www.jongbel.com/automated-validation/mpeg-2-video-validation/
Mark, did you tried this one or any alternative one to move forward with
this subject?
Will you validate Ticket_11055.m2ts, Pa
On 20/06/2024 03.30, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 10:43 PM Mark Filipak wrote:
On 19/06/2024 15.48, Jim DeLaHunt wrote:
On 2024-06-19 10:25, Paul B Mahol wrote:
It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts s
On Wed, Jun 19, 2024 at 11:25 PM Paul B Mahol wrote:
>
>
> On Wed, Jun 19, 2024 at 10:43 PM Mark Filipak
> wrote:
>
>> On 19/06/2024 15.48, Jim DeLaHunt wrote:
>> > On 2024-06-19 10:25, Paul B Mahol wrote:
>> >
>> >> It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
>> >> insp
Am 20.06.24 um 01:16 schrieb Bouke / Videotoolshed:
Harald, I was not talking to you, nor do I have any interest in what you have
to say.
I am also totally not interested in the reason why you feel to respond, and I
think the rest of the list isn’t either, so, please do all of us a favour, dr
Harald, I was not talking to you, nor do I have any interest in what you have
to say.
I am also totally not interested in the reason why you feel to respond, and I
think the rest of the list isn’t either, so, please do all of us a favour, drop
it.
> On 20 Jun 2024, at 01:06, Reindl Harald wro
Am 20.06.24 um 00:51 schrieb Bouke / Videotoolshed:
Do you have many friends?
when you pretend that you have more than 10 friedns yiou confuse
Faceboook with reality - quality matters - and now take your meds
___
ffmpeg-user mailing list
ffmpeg-u
On 19/06/2024 18.49, Phil Rhodes via ffmpeg-user wrote:
Oh, dear. TBird has found a way to thread these in regardless...
Look, Paul is fine. He just has a different sense of humor. You have to work
with him.
Jim DeLaHunt is fine. He just likes to preach and sing Kumbaya without actually
cont
> On 20 Jun 2024, at 00:48, MacFH - C E Macfarlane - News
> wrote:
>
> On 19/06/2024 23:40, Bouke / Videotoolshed wrote:
>>
>>> On 20 Jun 2024, at 00:31, MacFH - C E Macfarlane - News
>>> wrote:
>>>
>>> I've been following this list for a very long time, at least a decade I
>>> think. AFA
On 19/06/2024 23:38, Mark Filipak wrote:
On 19/06/2024 16.58, MacFH - C E Macfarlane - News wrote:
Apologies to Jim DeLaHunt for initially replying to him directly rather
than to the list as I had intended to do ...
On 19/06/2024 20:48, Jim DeLaHunt wrote:
On 2024-06-19 10:25, Paul B Mahol wr
On Wednesday 19 June 2024 at 21:58:51 BST, MacFH - C E Macfarlane - News
wrote:
Exactly! I've seen Paul's type before, trolling someone who comessearching for
help on a genuine problem and when asked for actual advicejust drops vague
hints rather than saying anything definite that mightturn
On 19/06/2024 23:40, Bouke / Videotoolshed wrote:
On 20 Jun 2024, at 00:31, MacFH - C E Macfarlane - News
wrote:
I've been following this list for a very long time, at least a decade I
think. AFAICR, I have posted in the past, but not for a quite a while
as I've been busy with a huge projec
On 19/06/2024 16.58, MacFH - C E Macfarlane - News wrote:
Apologies to Jim DeLaHunt for initially replying to him directly rather
than to the list as I had intended to do ...
On 19/06/2024 20:48, Jim DeLaHunt wrote:
On 2024-06-19 10:25, Paul B Mahol wrote:
It could be ffmpeg libavformat m2ts
On 19/06/2024 23:13, Bouke / Videotoolshed wrote:
Well Charles, please introduce yourself, and explain why I never ever have
heard from you before.
(I’ll take your advise under…)
I've been following this list for a very long time, at least a decade I
think. AFAICR, I have posted in the past,
Am 20.06.24 um 00:13 schrieb Bouke / Videotoolshed:
Well Charles, please introduce yourself, and explain why I never ever have
heard from you before.
(I’ll take your advise under…)
after our offlist-communication months ago the only question remains:
are you again out of drugs? take your me
What am I doing, feeding the trolls myself….
So sorry, weak moment.
Mea Culpa!
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org
Well Charles, please introduce yourself, and explain why I never ever have
heard from you before.
(I’ll take your advise under…)
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit
On 19/06/2024 23:02, Bouke / edit 'B wrote:
May I suggest that MacFH - C E Macfarlane - News
Is in fact Mark Fillipak with an alternative e-mail address?
I could be wrong of course, but please, proof me wrong.
How to klll a troll?
No, I am not, but feel free to kill yourself by any means
May I suggest that MacFH - C E Macfarlane - News
Is in fact Mark Fillipak with an alternative e-mail address?
I could be wrong of course, but please, proof me wrong.
How to klll a troll?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://f
On 19/06/2024 22:19, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 10:59 PM MacFH - C E Macfarlane - News <
n...@macfh.co.uk> wrote:
Apologies to Jim DeLaHunt for initially replying to him directly rather
than to the list as I had intended to do ...
On 19/06/2024 20:48, Jim DeLaHunt wrote:
On
> On 19 Jun 2024, at 23:19, Paul B Mahol wrote:
>
> Also derailing
After hundreds of (mostly) useless messages, initiated by somewone who promised
not to post not more than 8 messages per year, how can this be other than a
derailing trolling thread?
Am I the only one who is fed up with thi
On Wed, Jun 19, 2024 at 10:43 PM Mark Filipak
wrote:
> On 19/06/2024 15.48, Jim DeLaHunt wrote:
> > On 2024-06-19 10:25, Paul B Mahol wrote:
> >
> >> It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
> >> inspector tool to confirm.
> >
> > Paul, could you please specify which "
On Wed, Jun 19, 2024 at 10:59 PM MacFH - C E Macfarlane - News <
n...@macfh.co.uk> wrote:
> Apologies to Jim DeLaHunt for initially replying to him directly rather
> than to the list as I had intended to do ...
>
> On 19/06/2024 20:48, Jim DeLaHunt wrote:
> >
> > On 2024-06-19 10:25, Paul B Mahol
Apologies to Jim DeLaHunt for initially replying to him directly rather
than to the list as I had intended to do ...
On 19/06/2024 20:48, Jim DeLaHunt wrote:
On 2024-06-19 10:25, Paul B Mahol wrote:
It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
inspector tool to confirm
On 19/06/2024 15.48, Jim DeLaHunt wrote:
On 2024-06-19 10:25, Paul B Mahol wrote:
It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
inspector tool to confirm.
Paul, could you please specify which "m2ts stream inspector tool" you are
referring to?
From a web search for "m
On 19/06/2024 15.41, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 9:22 PM Mark Filipak
wrote:
On 19/06/2024 14.48, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 7:43 PM Mark Filipak
On 19/06/2024 13.25, Paul B Mahol wrote:
-snip-
It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts st
On 2024-06-19 10:25, Paul B Mahol wrote:
It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
inspector tool to confirm.
Paul, could you please specify which "m2ts stream inspector tool" you
are referring to?
From a web search for "m2ts stream inspector tool", I found:
* T
On Wed, Jun 19, 2024 at 9:22 PM Mark Filipak
wrote:
> On 19/06/2024 14.48, Paul B Mahol wrote:
> > On Wed, Jun 19, 2024 at 7:43 PM Mark Filipak >
> > wrote:
> >
> >> On 19/06/2024 13.25, Paul B Mahol wrote:
> >> -snip-
> >>> It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
>
On 19/06/2024 14.48, Paul B Mahol wrote:
On Wed, Jun 19, 2024 at 7:43 PM Mark Filipak
wrote:
On 19/06/2024 13.25, Paul B Mahol wrote:
-snip-
It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
inspector tool to confirm.
Thank you, Paul.
I searched "m2ts" & "inspector":
htt
On 19/06/2024 14.55, Carl Zwanzig wrote:
On 6/19/2024 11:19 AM, Mark Filipak wrote:
From the sound of it, this _is_ a normal/medium (or even "low") severity bug in that it doesn't
affect the vast majority of ffmpeg use.
How do you know that, Carl?
Address me as I sign my email and no other
On 6/19/2024 11:19 AM, Mark Filipak wrote:
From the sound of it, this _is_ a normal/medium (or even "low")
severity bug in that it doesn't affect the vast majority of ffmpeg use.
How do you know that, Carl?
Address me as I sign my email and no other way; that's why it's there.
How to I kno
On Wed, Jun 19, 2024 at 7:43 PM Mark Filipak
wrote:
> On 19/06/2024 13.25, Paul B Mahol wrote:
> -snip-
> > It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
> > inspector tool to confirm.
>
> Thank you, Paul.
>
> I searched "m2ts" & "inspector":
> https://ffmpeg.org/ffmpeg-all
On 19/06/2024 11.57, Carl Zwanzig wrote:
On 6/19/2024 6:22 AM, Mark Filipak wrote:
MasterQuestionable has downgraded the timestamp bug from 'important' to
'normal'.
Yes, and???
From the sound of it, this _is_ a normal/medium (or even "low") severity bug in that it doesn't
affect the vast m
On 19/06/2024 13.25, Paul B Mahol wrote:
-snip-
It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream
inspector tool to confirm.
Thank you, Paul.
I searched "m2ts" & "inspector":
https://ffmpeg.org/ffmpeg-all.html
https://ffmpeg.org/ffmpeg.html
https://ffmpeg.org/ffmpeg-utils.ht
On Wed, Jun 19, 2024 at 7:12 PM Mark Filipak
wrote:
> On 19/06/2024 13.07, Mark Filipak wrote:
> > Correction of first file name, sorry, copy goof.
> >
> > On 19/06/2024 12.45, Paul B Mahol wrote:
> >> ffmpeg -i Ticket_11055.m2ts -an -c copy -f framecrc broken.video.txt
> >
> > Thank you, Paul. I
On 19/06/2024 13.07, Mark Filipak wrote:
Correction of first file name, sorry, copy goof.
On 19/06/2024 12.45, Paul B Mahol wrote:
ffmpeg -i Ticket_11055.m2ts -an -c copy -f framecrc broken.video.txt
Thank you, Paul. I have two _different_ outputs. One from this:
ffmpeg -i g:\Ticket_11055.m2t
On 6/19/2024 9:51 AM, Mark Filipak wrote:
Thank you for the 'guide' but neither 'important' nor 'normal' are in
that guide.
The interpolate using normal English!
I can only say that if you take all the timestamp bug reports (which may
all be from the same cause) and total them together, it's
Correction of first file name, sorry, copy goof.
On 19/06/2024 12.45, Paul B Mahol wrote:
ffmpeg -i Ticket_11055.m2ts -an -c copy -f framecrc broken.video.txt
Thank you, Paul. I have two _different_ outputs. One from this:
ffmpeg -i g:\Ticket_11055.m2ts -an -c copy -f framecrc c:\broken.video.
On 19/06/2024 12.45, Paul B Mahol wrote:
ffmpeg -i Ticket_11055.m2ts -an -c copy -f framecrc broken.video.txt
Thank you, Paul. I have two _different_ outputs. One from this:
ffmpeg -i g:\Ticket_11055.m2ts -an -c copy -f framecrc c:\broken.video.txt
and one from this:
ffmpeg -copyts -i g:\Ticket
On 19/06/2024 11.57, Carl Zwanzig wrote:
On 6/19/2024 6:22 AM, Mark Filipak wrote:
MasterQuestionable has downgraded the timestamp bug from 'important' to
'normal'.
Yes, and???
From the sound of it, this _is_ a normal/medium (or even "low") severity bug in that it doesn't
affect the vast m
On 19/06/2024 12.29, Rob Hallam wrote:
On Wed, 19 Jun 2024 at 17:21, Mark Filipak wrote:
On 19/06/2024 12.02, Rob Hallam wrote:
-snip-
I can confirm I see a pause at "23%", though mpv reports it as
00:00:00 and then a seeming jump or fast increment through
percentages. I would probably have t
On Wed, Jun 19, 2024 at 6:27 PM Mark Filipak
wrote:
> On 19/06/2024 12.02, Rob Hallam wrote:
> -snip-
> > I can confirm I see a pause at "23%", though mpv reports it as
> > 00:00:00 and then a seeming jump or fast increment through
> > percentages. I would probably have to record the screen or so
On Wed, 19 Jun 2024 at 17:21, Mark Filipak wrote:
>
> On 19/06/2024 12.02, Rob Hallam wrote:
> -snip-
> > I can confirm I see a pause at "23%", though mpv reports it as
> > 00:00:00 and then a seeming jump or fast increment through
> > percentages. I would probably have to record the screen or som
On 19/06/2024 12.02, Rob Hallam wrote:
-snip-
I can confirm I see a pause at "23%", though mpv reports it as
00:00:00 and then a seeming jump or fast increment through
percentages. I would probably have to record the screen or something
to see exactly what happened, unless there's a way to get mp
On Wed, 19 Jun 2024 at 16:55, Mark Filipak wrote:
>
> I'm sorry, Rob, press [Shift][L] to loop MPV.
No worries, I found another way :)
Cheers,
Rob
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To u
On Wed, 19 Jun 2024 at 16:17, Mark Filipak wrote:
> MPV is more powerful and I think you'll like it. When it loads, quickly press
> the [L] key
> (unshifted) to loop,
As an aside, I couldn't get mpv to loop by pressing 'L', though it
reported A-B loop; instead I created an mpv.conf file with con
On 6/19/2024 6:22 AM, Mark Filipak wrote:
MasterQuestionable has downgraded the timestamp bug from 'important' to
'normal'.
Yes, and???
From the sound of it, this _is_ a normal/medium (or even "low")
severity bug in that it doesn't affect the vast majority of ffmpeg use.
There is often a giv
I'm sorry, Rob, press [Shift][L] to loop MPV.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
I've seen un explainable '-ss' (i.e., seek) problems.
I've seen trivial changes to FFmpeg commands produce a flood of un explainable "non-monotonous DTS"
errors when the trivial change had nothing to do with anything that would change DTS. (And I find it
tragic-funny that FFmpeg 'fixes' the bogu
On Wed, Jun 19, 2024 at 5:22 PM Mark Filipak
wrote:
> On 19/06/2024 10.01, Rob Hallam wrote:
> > On Wed, 19 Jun 2024 at 14:23, Mark Filipak
> wrote:
> >
> >> I think this may be a far ranging bug that affects '-ss' and that
> provokes many of the
> >> "non-monotonous DTS" error messages that see
On 19/06/2024 10.01, Rob Hallam wrote:
On Wed, 19 Jun 2024 at 14:23, Mark Filipak wrote:
I think this may be a far ranging bug that affects '-ss' and that provokes many
of the
"non-monotonous DTS" error messages that seem to appear out of nowhere when a
trivial, non-timing,
non-timestamp cha
On Wed, 19 Jun 2024 at 14:23, Mark Filipak wrote:
> I think this may be a far ranging bug that affects '-ss' and that provokes
> many of the
> "non-monotonous DTS" error messages that seem to appear out of nowhere when a
> trivial, non-timing,
> non-timestamp change is made to a transcode or to
MasterQuestionable has downgraded the timestamp bug from 'important' to 'normal'. I'm copying my
response here because trac is in a different account and that account's email-'cc's are rejected by
ffmpeg-user. --Mark.
https://trac.ffmpeg.org/ticket/11055
https://streams.videolan.org/ffmpeg/inco
On 17/06/2024 18.05, Paul B Mahol wrote:
On Tue, Jun 18, 2024 at 12:00 AM Mark Filipak
wrote:
On 17/06/2024 17.18, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 8:29 PM Mark Filipak
On 17/06/2024 13.50, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 5:35 PM Mark Filipak <
markfilipak.i...@gmail
On Tue, Jun 18, 2024 at 12:00 AM Mark Filipak
wrote:
> On 17/06/2024 17.18, Paul B Mahol wrote:
> > On Mon, Jun 17, 2024 at 8:29 PM Mark Filipak >
> > wrote:
> >
> >> On 17/06/2024 13.50, Paul B Mahol wrote:
> >>> On Mon, Jun 17, 2024 at 5:35 PM Mark Filipak <
> markfilipak.i...@gmail.com
> >>>
Paul, I misunderstood your question. (see at end)
On 17/06/2024 17.59, Mark Filipak wrote:
On 17/06/2024 17.18, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 8:29 PM Mark Filipak
wrote:
On 17/06/2024 13.50, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 5:35 PM Mark Filipak
On 17/06/2024 03.16,
On 17/06/2024 17.18, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 8:29 PM Mark Filipak
wrote:
On 17/06/2024 13.50, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 5:35 PM Mark Filipak
On 17/06/2024 03.16, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 3:16 AM Mark Filipak <
markfilipak.i...@gmail.
On Mon, Jun 17, 2024 at 8:29 PM Mark Filipak
wrote:
> On 17/06/2024 13.50, Paul B Mahol wrote:
> > On Mon, Jun 17, 2024 at 5:35 PM Mark Filipak >
> > wrote:
> >
> >> On 17/06/2024 03.16, Paul B Mahol wrote:
> >>> On Mon, Jun 17, 2024 at 3:16 AM Mark Filipak <
> markfilipak.i...@gmail.com
> >>>
>
On 17/06/2024 13.50, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 5:35 PM Mark Filipak
wrote:
On 17/06/2024 03.16, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 3:16 AM Mark Filipak
To expand on my idea:
The video is this:
I P B B P B B P B B I P B B..
I want to change it to this:
I B B P B B
On Mon, Jun 17, 2024 at 5:35 PM Mark Filipak
wrote:
> On 17/06/2024 03.16, Paul B Mahol wrote:
> > On Mon, Jun 17, 2024 at 3:16 AM Mark Filipak >
> > wrote:
> >
> >> To expand on my idea:
> >>
> >> The video is this:
> >> I P B B P B B P B B I P B B..
> >> I want to change it to this:
> >> I B B
On 17/06/2024 03.16, Paul B Mahol wrote:
On Mon, Jun 17, 2024 at 3:16 AM Mark Filipak
wrote:
To expand on my idea:
The video is this:
I P B B P B B P B B I P B B..
I want to change it to this:
I B B P B B P B B P I B B P..
If this is what I think it is, your are wasting your time.
It is
On Mon, Jun 17, 2024 at 3:16 AM Mark Filipak
wrote:
> To expand on my idea:
>
> The video is this:
> I P B B P B B P B B I P B B..
> I want to change it to this:
> I B B P B B P B B P I B B P..
>
If this is what I think it is, your are wasting your time.
Its nonsense to change order of encoded
To expand on my idea:
The video is this:
I P B B P B B P B B I P B B..
I want to change it to this:
I B B P B B P B B P I B B P..
To do that, I reckon I need to,
1, move the packets that contain P-frames,
2, insert revised 'program_clock_reference_base's and 'program_clock_reference_extension's
I had a brainwave...
The 4 second video is in DTS-order. That's unusual, but that's what Criterion
gave us.
What if I could rearrange the packets to PTS-order?
If showinfo and show_frames then agreed with framecrc, that would tell the
whole story, wouldn't it?
Is that possible? Is it possible t
On 16/06/2024 19.25, Jim DeLaHunt wrote:
On 2024-06-16 01:19, Mark Filipak wrote:
On 16/06/2024 03.51, Jim DeLaHunt wrote:
On 2024-06-15 23:04, Mark Filipak wrote:
On 15/06/2024 23.39, Jim DeLaHunt wrote:
On 2024-06-15 19:27, Mark Filipak wrote:
It would be nice if folks from here went here
On 2024-06-16 01:19, Mark Filipak wrote:
On 16/06/2024 03.51, Jim DeLaHunt wrote:
On 2024-06-15 23:04, Mark Filipak wrote:
On 15/06/2024 23.39, Jim DeLaHunt wrote:
On 2024-06-15 19:27, Mark Filipak wrote:
It would be nice if folks from here went here:
https://trac.ffmpeg.org/ticket/11055
and
On Sun, Jun 16, 2024 at 8:03 PM Bouke / Videotoolshed <
bo...@videotoolshed.com> wrote:
> Hi Harald,
> As a professional, my time is worth something.
> How much does it cost never to be bothered by you again?
> It is not helpfull, nor joy, nor constructive, only a major PITA.
> So, please, name yo
Hi Harald,
As a professional, my time is worth something.
How much does it cost never to be bothered by you again?
It is not helpfull, nor joy, nor constructive, only a major PITA.
So, please, name your price!
Bouke
videotoolshed.com
Van Oldenbarneveltstraat 33
6512 AS Nijmegen, the Netherlands
Am 16.06.24 um 15:54 schrieb Phil Rhodes via ffmpeg-user:
On Sunday 16 June 2024 at 13:56:33 BST, Paul B Mahol wrote:
Do it professionally instead, hire developers! (But I think most of
developers listed on ffmpeg page have job already.)
Isn't that a statement which fundamentally under
Yes, I'm fully aware - it's just a bit much to gleefully point out that
they're all otherwise engaged!
P
On Sunday 16 June 2024 at 15:01:49 BST, Carl Zwanzig
wrote:
On 6/16/2024 6:54 AM, Phil Rhodes via ffmpeg-user wrote:
> Isn't that a statement which fundamentally undermines the enti
On 6/16/2024 6:54 AM, Phil Rhodes via ffmpeg-user wrote:
Isn't that a statement which fundamentally undermines the entire concept
of ffmpeg as an open source project with willing developers...
More than a few OS projects have professional (and paid, they're not the
same thing) developers. No
On Sunday 16 June 2024 at 13:56:33 BST, Paul B Mahol wrote:
> Do it professionally instead, hire developers! (But I think most of
> developers listed on ffmpeg page have job already.)
Isn't that a statement which fundamentally undermines the entire concept of
ffmpeg as an open source project w
On Sun, Jun 16, 2024 at 1:51 PM Reindl Harald
wrote:
>
>
> Am 16.06.24 um 11:33 schrieb Binarus:
> > Yes, I am also impatient sometimes. And yes, I also have been very
> > disappointed by the FFMPEG community support; sometimes, I wasn't able
> > to get even the simplest explanations for question
Am 16.06.24 um 11:33 schrieb Binarus:
Yes, I am also impatient sometimes. And yes, I also have been very
disappointed by the FFMPEG community support; sometimes, I wasn't able
to get even the simplest explanations for questions that a developer
should be able to answer with no effort.
you
On Sun, Jun 16, 2024 at 11:33 AM Binarus wrote:
> I really have to kick in here, although I have no clue regarding the
> internals of FFMPEG, and although 90% of it are a mystery to me, and
> although I have to admit that I didn't get yet how to use it properly (and
> probably never will get that
I really have to kick in here, although I have no clue regarding the internals
of FFMPEG, and although 90% of it are a mystery to me, and although I have to
admit that I didn't get yet how to use it properly (and probably never will get
that). That is, I can't contribute anything to solve your
On Sun, Jun 16, 2024 at 10:19 AM Mark Filipak
wrote:
> On 16/06/2024 03.51, Jim DeLaHunt wrote:
> > On 2024-06-15 23:04, Mark Filipak wrote:
> >
> >> On 15/06/2024 23.39, Jim DeLaHunt wrote:
> >>> On 2024-06-15 19:27, Mark Filipak wrote:
> >>>
> It would be nice if folks from here went here:
1 - 100 of 126 matches
Mail list logo
