I've attached a final version of MPEG-2 Streams. AVC Streams is in the works.
If you see something wrong with MPEG-2 Streams, I'd appreciate an authoritative reference.
Otherwise, please anticipate discussion to resolve controversy. I assure you it will be good discussion.
Thank you
--Mark.
On 20/07/2024 18.11, Vincent Deconinck wrote:
On Sat, Jul 20, 2024 at 9:55 PM Mark Filipak
wrote:
-snip-
GoPro splits videos in chunks of around 4GB (which is about 11 minutes with
my settings). In other words, I have 5 or 7 files to which I should apply
the same shuffling pattern
On 20/07/2024 13.57, Vincent Deconinck wrote
-snip-> But I don't see any such dropped frames in the output.> I reformated the log for the 10
first frames in this spreadsheet:>
https://docs.google.com/spreadsheets/d/1nVWROlUkl2rzENiCpey5Sw1z97WS3tfR52ATjfn_rTU/edit?usp=sharing>
> Do you see
On 18/07/2024 17.56, Vincent Deconinck wrote:
On Thu, Jul 18, 2024 at 12:26 AM Mark Filipak
wrote:
Based on a recent tip, try this command:
ffprobe -flags2 +showall -i ...
You may find that what you think is the first frame is not always the
first frame.
Thanks.
I tried the above command
On 17/07/2024 16.54, Vincent Deconinck wrote:
On Fri, Jul 12, 2024 at 1:04 AM Mark Filipak
wrote:
Try this:
-filter_complex "shuffleframes="
It's worked for me.
Hi Mark and Paul,
Sorry for the delay.
Thanks very much for the "shuffleframes" filter tip, this seems t
On 17/07/2024 15.32, Carl Zwanzig wrote:
On 7/17/2024 5:46 AM, Oliver Fromme wrote:
The typical cinema frame rate (23.976 fps) is the minimum that's
commonly accepted,
In a real film cinema it's an exact 24fps however the shutter is quartered so there are two flashes
per frame; some
On 17/07/2024 14.46, Oliver Fromme wrote:
Mark Filipak wrote:
> On 17/07/2024 13.23, Oliver Fromme wrote:
> > Mark Filipak wrote:
> > > What if there's no such thing as frame in the future? Just think about
it.
> >
> > What are you going to use inste
On 17/07/2024 13.23, Oliver Fromme wrote:
Mark Filipak wrote:
> What if there's no such thing as frame in the future? Just think about it.
What are you going to use instead?
Pels.
You somehow need to organize screen updates -- that is, when the
contents of the screen change. You h
On 17/07/2024 12.30, Oliver Fromme wrote:
Mark Filipak wrote:
> The weighting of Y Cr Cb are still based on CRT phosphors, not reality. HSV
is reality.
No, that's wrong, HSV is not "reality". I'm afraid it's much more
complicated than that.
Oliver, if we continue, you w
I'm sorry my posts are so technical. AVC is technical.
I have 'attacked' my 40 second m2ts with a hex editor because other tools are inadequate. I have not
found any GOPs. I've found GOP-like start codes (0x00 00 01 B8) but the next 4 bytes are not correct
for a GOP header. For example:
00 00
On 17/07/2024 08.46, Oliver Fromme wrote:
I'm not sure this is on-topic for the ffmpeg users list ...
It is, or rather, it will be some day...
Imagine video without frames, imagine how it would work, imagine pixel-by-pixel random access and
you're on your way.
There would be no game play
On 16/07/2024 07.40, Oliver Fromme wrote:
Mark Filipak wrote:
> Since 00305.m2ts is AVC encoded, there are I slices in it but not I frames -- I
P & B frames are
> MPEG-1 & MPEG-2.
That's not completely correct. I suggest you read a bit about
basic concepts and terminology
On 16/07/2024 19.40, MacFH - C E Macfarlane - News wrote:
On 17/07/2024 00:02, Mark Filipak wrote:
To match human persistence of vision, the refresh rate of individual
pels actually needs to be no greater than 10 or 12 refreshes per second.
Only the dots that change need be refreshed
On 16/07/2024 19.34, Reino Wijnsma wrote:
Thank you, Reino. I didn't realize I could suppress like that. That's wonderful! I will use
that, I'll use it a lot.
On 2024-07-06T03:18:31+0200, Mark Filipak wrote:
THE SCRIPT:
[...]
Please don't. Eventhough I'm a Windows user and I understand
I interviewed at NVIDIA when it was a start-up. My interview wound up being an argument over
sprite graphics, which they held in contempt. I did not get the job.
Well, guess what? The so-called "slice prediction" in AVC is sprite graphics. It's real image but
it's sprites. At Atari, we did
When I run this:
ffprobe -sexagesimal -select_streams v -show_frames -of flat -i e:\00305.m2ts
where 00305.m2ts is AVC, it reports such things as this:
frames.frame.0.pict_type="I"?
AVC does not have I-frames (or P-frames or B-frames), so, what does it mean?
Just asking... Anyone know?
I just ran this:
ffprobe -sexagesimal -select_streams v -show_frames -of flat -i e:\00305.m2ts
Since 00305.m2ts is AVC encoded, there are I slices in it but not I frames -- I P & B frames are
MPEG-1 & MPEG-2.
So, what does ffprobe mean when it reports this:
frames.frame.0.pict_type="I"?
Just
Is FFmepg doing anything with the discontinuity_indicator bit in the TS
adaptation_field?
--Mark.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
On 11/07/2024 18.05, Vincent Deconinck wrote:
Hi,
A few months ago, my GoPro randomly started creating some corrupt (or
partly-corrupt) video files, mixing up frames and causing jaggy playback.To
illustrate the case, here is an excerpt I generated with "ffmpeg -c copy"
from a corrupt source
On 11/07/2024 18.05, Vincent Deconinck wrote:
Hi,
A few months ago, my GoPro randomly started creating some corrupt (or
partly-corrupt) video files, mixing up frames and causing jaggy playback.To
illustrate the case, here is an excerpt I generated with "ffmpeg -c copy"
from a corrupt source
On 11/07/2024 00.11, Gyan Doshi wrote:
On 2024-07-11 03:09 am, Paul B Mahol wrote:
On Wed, Jul 10, 2024 at 11:18 PM Mark Filipak
wrote:
On 10/07/2024 13.51, Will Boba wrote:
On 7/10/24 10:26, Mark Filipak wrote:
Three more tried.
ffmpeg -forced-idr 1 -i ... -c:v libx264 -an -sn
On 10/07/2024 13.51, Will Boba wrote:
On 7/10/24 10:26, Mark Filipak wrote:
Three more tried.
ffmpeg -forced-idr 1 -i ... -c:v libx264 -an -sn -start_at_zero -muxdelay 0 ...
[in#0 @ 00542d00] Error opening input: Invalid data found when
processing input
ffmpeg -i ... -forced-idr 1
Three more tried.
ffmpeg -forced-idr 1 -i ... -c:v libx264 -an -sn -start_at_zero -muxdelay 0 ...
[in#0 @ 00542d00] Error opening input: Invalid data found when
processing input
ffmpeg -i ... -forced-idr 1 -c:v libx264 -an -sn -start_at_zero -muxdelay 0 ...
[in#0 @ 00542d00]
Hi All,
Does anyone know how to use 'forced-idr'? Below is what I've tried, plus the
errors. Thanks-- Mark.
ffmpeg -forced-idr -i -c:v libx264 -an -sn -start_at_zero -muxdelay 0
[out#0/mpegts @ 00577400] Output file does not contain any stream
Error opening output file .
ffmpeg
On 05/07/2024 15.41, Mark Filipak wrote:
On 05/07/2024 14.34, Jim DeLaHunt wrote:
On 2024-07-04 15:50, Mark Filipak wrote:
...Here's the interesting terminal output (slightly beautified):
[Parsed_trim_1 @ 00620040]
Media type mismatch between the 'Parsed_trim_1' filter output pad 0
On 04/07/2024 17.11, Paul B Mahol wrote:
On Thu, Jul 4, 2024 at 10:44 PM Mark Filipak
wrote:
On 04/07/2024 14.22, Paul B Mahol wrote:
On Thu, Jul 4, 2024 at 8:05 PM Mark Filipak
wrote:
Is there some secret to the trim filter?
--filter_complex "split=2[i5][i6],
[i5]trim=start_
On 05/07/2024 14.34, Jim DeLaHunt wrote:
On 2024-07-04 15:50, Mark Filipak wrote:
...Here's the interesting terminal output (slightly beautified):
[Parsed_trim_1 @ 00620040]
Media type mismatch between the 'Parsed_trim_1' filter output pad 0 (video) and the
'Parsed_atrim_2' filter
On 05/07/2024 07.54, Paul B Mahol wrote:
On Fri, Jul 5, 2024 at 2:09 AM Mark Filipak
wrote:
On 04/07/2024 17.12, Paul B Mahol wrote:
Its in documentation: asetpts=N/SR/TB, assuming everything starts from 0,
so add it after each atrim.
For both video & audio,
time_base=1/9
On 04/07/2024 23.07, Srikanth Kotagiri wrote:
On Fri, Jul 5, 2024 at 4:49 AM Mark Filipak wrote:
Has anyone figured out how to discern IDR frames v non-IDR frames in either
FFmpeg or FFprobe?
ffprobe -select_streams v -show_frames -print_format json sample.mp4
2>/dev/null | jq '.fra
Has anyone figured out how to discern IDR frames v non-IDR frames in either
FFmpeg or FFprobe?
--Mark.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
On 04/07/2024 17.12, Paul B Mahol wrote:
Its in documentation: asetpts=N/SR/TB, assuming everything starts from 0,
so add it after each atrim.
For both video & audio,
time_base=1/9
start_pts=1048560
So, there are 'silent' audio samples starting with the first video frame. I'm dropping
I meant the "broken non-IDR frame".
On 04/07/2024 17.04, Mark Filipak wrote:
Paul, if I find a way to change only the audio frame's PTSes, what would I
change them to?
Don't I want to simply drop them, instead?
_But_ if I use -noise=drop, I'll drop the video packets, too, and the vid
problem, eh?
--Mark.
On 04/07/2024 16.25, Mark Filipak wrote:
On 04/07/2024 14.22, Paul B Mahol wrote:
On Thu, Jul 4, 2024 at 8:05 PM Mark Filipak
wrote:
Is there some secret to the trim filter?
--filter_complex "split=2[i5][i6],
[i5]trim=start_frame=481:end_frame=134047[o5],
[i6
On 04/07/2024 14.22, Paul B Mahol wrote:
On Thu, Jul 4, 2024 at 8:05 PM Mark Filipak
wrote:
Is there some secret to the trim filter?
--filter_complex "split=2[i5][i6],
[i5]trim=start_frame=481:end_frame=134047[o5],
[i6]trim=start_frame=138745:end_frame=246719[o6],
[o5][o6]conca
Is there some secret to the trim filter?
--filter_complex "split=2[i5][i6],
[i5]trim=start_frame=481:end_frame=134047[o5],
[i6]trim=start_frame=138745:end_frame=246719[o6],
[o5][o6]concat=n=2"
I get "dup=481", instead, and wind up with 20.061708[3..] seconds of black frames preceding the
H.264 appears to have made I- P- & B-frames obsolete.
Everyone's probably seen my DTS-PTS diagrams.
Closed GOP
PTS order I B B P B B P..
/ __/ __/
/ //
DTS order I P B B P B B..
Open GOP
PTS order ..B B I B B P..
On 29/06/2024 14.58, Carl Zwanzig wrote:
On 6/28/2024 4:07 PM, Mark Filipak wrote:
I have to consider Blackmagic DaVinci Resolve to be a virus hub that is probably selling access to
my system through those ports to outside clients.
You're welcome to consider it such, but that doesn't make
On 29/06/2024 23.23, MediaMouth wrote:
On Jun 29, 2024, at 19:07, Mark Filipak wrote:
FWIW Resolve uses a database approach to its projects. (Avid uses files (bins
aka .avb files) as does Premiere. That likely accounts for at least one of the
open ports if not more
If that connects
On 29/06/2024 22.42, Carl Zwanzig wrote:
On 6/29/2024 5:37 PM, Mark Filipak wrote:
The firewall is between them and the OS networking.
The firewall is between your ISP's terminal device ...
What's an "ISP's terminal device"?
... and your PC's network interface ...
What's
On 29/06/2024 20.58, Rob Hallam wrote:
On Sat, 29 Jun 2024 at 23:37, Mark Filipak wrote:
On 29/06/2024 18.19, Rob Hallam wrote:
On Sat, 29 Jun 2024 at 22:35, Mark Filipak wrote:
Only if your router is misconfigured to let all ports through to your
internal network by default. If it does
On 29/06/2024 19.32, Carl Zwanzig wrote:
Mark Filipak wrote in various messages:
Open ports shine on the Internet like stars in the sky. Open ports want to be
found.
How does the world see those ports _inside_ your firewall? Please explain. (You do have an Internet
firewall, don't you
On 29/06/2024 18.30, MediaMouth wrote:
On Jun 29, 2024, at 18:21, MacFH - C E Macfarlane - News
wrote:
On 29/06/2024 22:35, Mark Filipak wrote:
2 - There is a web site that shows your open ports. I can't remember the
name. Sorry. I did tests to prove open ports are readily seen. I did
On 29/06/2024 18.19, Rob Hallam wrote:
On Sat, 29 Jun 2024 at 22:35, Mark Filipak wrote:
Only if your router is misconfigured to let all ports through to your
internal network by default. If it does, then a relatively uncommon
piece of MPEG software will be the least of your problems
On 29/06/2024 17.52, Paul B Mahol wrote:
On Sat, Jun 29, 2024 at 11:42 PM Mark Filipak
wrote:
If you listen only yourself and nobody else, you also are ignorant.
That's logical and illogical at the same time, Paul. If you have no knowledge or experience and you
listen only to yourself
On 29/06/2024 17.18, Oliver Fromme wrote:
Mark Filipak wrote:
> On 29/06/2024 16.28, Carl Zwanzig wrote:
> > On 6/29/2024 12:56 PM, Mark Filipak wrote:
> > > I did. That's why I decided not to use it.
> >
> > Your loss.
> >
> > z!
On 29/06/2024 16.28, Carl Zwanzig wrote:
On 6/29/2024 12:56 PM, Mark Filipak wrote:
I did. That's why I decided not to use it.
Your loss.
z!
No, they're loss. Open ports shine on the Internet like stars in the sky. Open
ports want to be found.
Anyone/anything scanning IP blocks will see
On 29/06/2024 14.58, Carl Zwanzig wrote:
On 6/28/2024 4:07 PM, Mark Filipak wrote:
I have to consider Blackmagic DaVinci Resolve to be a virus hub that is probably selling access to
my system through those ports to outside clients.
You're welcome to consider it such, but that doesn't make
On 28/06/2024 22.57, Richard Bartczak via ffmpeg-user wrote:
Mark an american, stupi.., like possible.
Where a medicine, no.
Gloster
Oh, dear...
Hey, Gloster, do you have the European sickness?
I'm 3rd generation Polish-American. If I was in Poland, I'd be Marek Filipiak. Do you hate me?
On 27/06/2024 19.27, Phil Rhodes via ffmpeg-user wrote:
Mark,
For the purpose of being able to look at frame sequences easily, you can
probably just use something like Resolve.
Thank you, Phil. I tried it on your suggestion. In 48 years of personal computing, that is most
aggressive
On 28/06/2024 14.42, Richard Bartczak via ffmpeg-user wrote:
Hello,
nothing I have found. Neither via ffprobe, nor via ffmpeg, I have found
a solution.
A solution to what, Gloster? What are you trying to solve?
I'll give my latest take on IDR frames: They don't exist, per se. What I think an
On 27/06/2024 19.27, Phil Rhodes via ffmpeg-user wrote:
Mark,
One thing about getting software to analyse what ffmpeg is doing with regard to
cuts and splices - what're you thinking of?
Hey Phil,
I'm doing trimming and splicing of open GOPs.
I trimmed both ends of two m2ts segments and
On 27/06/2024 17.55, Richard Bartczak via ffmpeg-user wrote:
Am 27.06.24 um 22:39 schrieb Mark Filipak:
Hello All,
I'm considering buying professional video software to evaluate and
analyze FFmpeg trims and splices and for troubleshooting. My objective
is to improve my edits, and to improve
Hello All,
I'm considering buying professional video software to evaluate and analyze FFmpeg trims and splices
and for troubleshooting. My objective is to improve my edits, and to improve FFmpeg. I'm retired, I
have plenty of time, I have plenty of money.
From here:
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 t
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
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 arguin
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!?
D
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!?
D
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
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
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
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
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
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,
"Mark Filipak" is my real name. For all time, on all sites except one, I'm "markfilipak". On
forum.videohelp.com I'm "Cuddly Squid". I took that alias to get the attention of the author of
BDInfo, who is "Cinema Squid". "Cuddly Squid" is
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
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
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
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
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
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" &a
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 sig
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
affec
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
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
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
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
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
affec
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 pro
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
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
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
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
On 18/06/2024 12.03, Greg Oliver wrote:
On Tue, Jun 18, 2024 at 10:22 AM Mark Filipak
wrote:
On 18/06/2024 11.16, Greg Oliver wrote:
On Tue, Jun 18, 2024 at 9:45 AM Mark Filipak
MasterQuestionable appears to be the boss of trac. I don't know whether
MasterQuestionable is a
person or a group
On 18/06/2024 11.16, Greg Oliver wrote:
On Tue, Jun 18, 2024 at 9:45 AM Mark Filipak
wrote:
MasterQuestionable appears to be the boss of trac. I don't know whether
MasterQuestionable is a
person or a group. The language from MasterQuestionable is as one would
find in a chat among peers
(i.e
MasterQuestionable appears to be the boss of trac. I don't know whether MasterQuestionable is a
person or a group. The language from MasterQuestionable is as one would find in a chat among peers
(i.e., developers) who come into the chat with a wealth of experience and a common language and a
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 <
markfilipa
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 <
markfilipa
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 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
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
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
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 saw what is going on. It's up to 76
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 saw what is going on. It's up to 76 comments now, so what I ask will take
you a while.
What's going on is a crime.
What's
It would be nice if folks from here went here:
https://trac.ffmpeg.org/ticket/11055
and saw what is going on. It's up to 76 comments now, so what I ask will take
you a while.
What's going on is a crime.
___
ffmpeg-user mailing list
On 15/06/2024 11.18, Paul B Mahol wrote:
On Sat, Jun 15, 2024 at 4:16 PM Carl Zwanzig wrote:
On 6/15/2024 1:30 AM, Paul B Mahol wrote:
What you even mean with above unclear statements?
Perhaps you might read the last 8-10 messages as Jim attempts to
decipher it.
I was explicitly
1 - 100 of 1090 matches
Mail list logo
