On 2022-01-31 03:38, Michael Koch wrote:
Am 31.01.2022 um 05:03 schrieb Mark Filipak (ffmpeg):
During the past year, I've developed a set of true stream primitives that are object oriented
(frames, pictures, ...), plus a notation to describe encodings and "mechanical" manipula
During the past year, I've developed a set of true stream primitives that are object oriented
(frames, pictures, ...), plus a notation to describe encodings and "mechanical" manipulations that
are useful and that are fairly easy to read and understand. Can the notation be used as a frontend
t
On 2021-04-12 18:02, Carl Eugen Hoyos wrote:
Am Mo., 12. Apr. 2021 um 23:52 Uhr schrieb Carl Zwanzig :
On 4/12/2021 2:42 PM, Carl Eugen Hoyos wrote:
and since Matthew didn't mention "interlaced"
Video (ORIGINAL)
Scan type: Interlaced
Scan order
On 2021-04-12 17:19, Carl Eugen Hoyos wrote:
Am Mo., 12. Apr. 2021 um 10:42 Uhr schrieb Jim DeLaHunt
:
3. Use the current version of ffmpeg to reproduce your problem. Your
output says, "ffmpeg version n3.0.1", but the current numbered version
is 4.4.
To make this as clear as possible:
The onl
On 2021-04-12 06:40, Matthew Yang wrote:
Hello all
I was trying to extract a 5-minute segment of a video, keeping the same
settings using the following command
ffmpeg -ss 00:00:00 -i "input.mxf" -c copy -t 00:05:00 output.mxf
However the 'resolution' and 'scan type' of the output differs from
On 2021-04-08 04:56, Nicolas George wrote:
Adrian Cable (12021-04-08):
Mark – yes – you’re understanding exactly right! I was thinking
specifically of the encoder ‘throttle’ being a frame rate control, but
other forms of quality control that could be self-adjusted by the
encoder to keep up with
On 2021-04-07 22:33, Adrian Cable wrote:
Mark – yes – you’re understanding exactly right! I was thinking specifically of
the encoder ‘throttle’ being a frame rate control, but other forms of quality
control that could be self-adjusted by the encoder to keep up with the input
would also work fo
On 2021-04-07 21:51, Adrian Cable wrote:
Mark,
Sorry, I thought XXX referred to the output -- -vf fps=fps=XXX is *output*
frame rate. To the best
of my knowledge, the input frame rate of VFR video can't be specified.
I’m referring to XXX as the maximum *output* frame rate that the pipeline c
t be independent of the input frame rate, because decoding the input
frames consumes CPU and memory bandwidth, which leaves less available for the
re-encoding part. If the input frame rate is 60 fps, for example, XXX will be
lower than if the input frame rate were 5 fps.
-Adrian
From: ffmpeg
On 2021-04-05 21:02, Adrian Cable wrote:
Hi,
I have a question that I thought should have an ‘easy’ answer – I have spent a
lot of time searching and I cannot find it, so thought I would ask here.
My application sounds simple. I have an input RTSP stream, which I need to
transcode and output a
As shown below, the mix filter appears to be failing and I don't know why. Can
you help, please?
ffmpeg -i SOURCE -vf "showinfo,split=2[1][2],[1][2]mix=inputs=2:weights=5
5,showinfo" ...
The 'showinfo' information includes:
[Parsed_showinfo_0 ...] n: 0 pts: 0 pts_time:0 pos: 5
On 2021-04-01 13:40, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
What I'm trying to do is make a 12/1001fps cfr in which each frame is
a proportionally weighted
pixel mix of the 24 picture-per-second original:
A B AAABB AABBB A.
I'm sure it would be way better than standar
On 2021-04-01 13:40, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
What I'm trying to do is make a 12/1001fps cfr in which each frame is
a proportionally weighted
pixel mix of the 24 picture-per-second original:
A B AAABB AABBB A.
I'm sure it would be way better than standar
On 2021-04-01 13:06, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
On 2021-04-01 11:41, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
On 2021-04-01 07:13, Mark Filipak (ffmpeg) wrote:
The source is MKV. MKV has a 1/1000 TB, so any PTS variance should be
less than 0.1%.
The filter complex is thinned
On 2021-04-01 11:41, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
On 2021-04-01 07:13, Mark Filipak (ffmpeg) wrote:
The source is MKV. MKV has a 1/1000 TB, so any PTS variance should be
less than 0.1%.
The filter complex is thinned down to just this: settb=1/72,showinfo
Here is selected lines
On 2021-04-01 07:13, Mark Filipak (ffmpeg) wrote:
The source is MKV. MKV has a 1/1000 TB, so any PTS variance should be less than
0.1%.
The filter complex is thinned down to just this: settb=1/72,showinfo
Here is selected lines from the showinfo report (with ...comments
The source is MKV. MKV has a 1/1000 TB, so any PTS variance should be less than
0.1%.
The filter complex is thinned down to just this: settb=1/72,showinfo
Here is selected lines from the showinfo report (with ...comments):
[Parsed_showinfo_1 @ 0247d719ef00] config in time_base: 1/720
Oh! Returning to my editor from replying to your last message, I suddenly saw
what I'm doing wrong.
The fix: I need to create a 2-frame sliding window that ping-pongs between this:
PTS=0 30030
: :
[a
On 2021-03-30 08:40, Bruce Roberts wrote:
Sorry to keep contradicting myself Mark Filipak, but I'm still wondering if
perhaps there is something wrong in your shuffle/mix/interleave command
because to me, having looked once again, ...
"Looked"? Have you run that filter_complex_script? I don't k
Addition: I'm also not receiving Phil's posts (and perhaps others).
On 2021-03-29 18:19, Nicolas George wrote:
Phil Rhodes via ffmpeg-user (12021-03-29):
Are you contending that there is no such thing as video at 24000/1001 fps?
Are you capable of understanding a simple phrase made of less
On 2021-03-29 18:19, Nicolas George wrote:
Phil Rhodes via ffmpeg-user (12021-03-29):
Are you contending that there is no such thing as video at 24000/1001 fps?
Are you capable of understanding a simple phrase made of less ten words?
I believe that Nicolas is correct, Phil. I know that 24p
On 2021-03-29 07:11, Bruce Roberts wrote:
Yes, my apologies - I don't get the luminance bands either when I don't try
to deinterlace the progressive source or if I do deinterlace and
reinterlace interlaced inputs so it seems there was no problem with the
framerate filter after all.
I would still
On 2021-03-26 10:02, Bruce Roberts wrote:
Hello,
I'm looking for advice on the best ways to convert 23.976fps and 29.97fps
AVC-I 100Mbps content to 25fps (also interlaced AVC-I 100Mbps).
Hello Bruce,
I think we may be treading parallel paths, you: from the west to east (FILM & NTSC to 50fps),
On 2021-03-24 07:23, Gyan Doshi wrote:
On 2021-03-24 16:29, Moritz Barsnick wrote:
On Wed, Mar 24, 2021 at 10:18:55 +0100, Peter White wrote:
[AVFilterGraph @ 025772b53dc0] Error initializing filter 'mix' with args
'nb_inputs=2:weights=3 2'
Error initializing complex filters.
Option not fo
On 2021-03-24 05:18, Peter White wrote:
On Wed, Mar 24, 2021 at 05:00:09AM -0400, Mark Filipak (ffmpeg) wrote:
...contrary to https://ffmpeg.org/ffmpeg-filters.html#mix
[Parsed_mix_29 @ 025771c709c0] Option 'nb_inputs' *not found*
[AVFilterGraph @ 025772b53dc0] Error in
...contrary to https://ffmpeg.org/ffmpeg-filters.html#mix
[Parsed_mix_29 @ 025771c709c0] Option 'nb_inputs' *not found*
[AVFilterGraph @ 025772b53dc0] Error initializing filter 'mix' with args
'nb_inputs=2:weights=3 2'
Error initializing complex filters.
Option not found
On 2021-03-22 02:48, Jim DeLaHunt wrote:
On 2021-03-21 22:40, Mark Filipak (ffmpeg) wrote:
Hi All,
A little help, please.
Using the latest git source, using '-filter_complex_script', I get a mystery
error.
I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt,
On 2021-03-22 03:28, Paul B Mahol wrote:
On Mon, Mar 22, 2021 at 8:17 AM Mark Filipak (ffmpeg)
wrote:
On 2021-03-22 03:00, Paul B Mahol wrote:
On Mon, Mar 22, 2021 at 6:43 AM Mark Filipak (ffmpeg) <
markfili...@bog.us>
wrote:
Hi All,
A little help, please.
Using the latest git
On 2021-03-22 03:00, Paul B Mahol wrote:
On Mon, Mar 22, 2021 at 6:43 AM Mark Filipak (ffmpeg)
wrote:
Hi All,
A little help, please.
Using the latest git source, using '-filter_complex_script', I get a
mystery error.
I have checked the filter_complex_script: 23fps.ffmpeg.filte
Hi All,
A little help, please.
Using the latest git source, using '-filter_complex_script', I get a mystery
error.
I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for errors. Especially I've
checked that every input pad (especially [AA1]) has one and only one matching outpu
On 2021-03-21 19:01, Carl Eugen Hoyos wrote:
Am So., 21. März 2021 um 23:55 Uhr schrieb Mark Filipak (ffmpeg)
:
On 2021-03-21 18:36, Carl Eugen Hoyos wrote:
Am So., 21. März 2021 um 23:31 Uhr schrieb Mark Filipak (ffmpeg)
:
On 2021-03-21 17:50, Carl Eugen Hoyos wrote:
Am So., 21. März 2021
On 2021-03-21 05:04, Er Win wrote:
Hey ffmpeg-user,
when ffmpeg reports errors it looks like this:
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 01d8c0fe9cc0] Invalid NAL unit size (0 > 7208).
[h264 @ 01d8c0fe9cc0] Error splitting the input into NAL
On 2021-03-21 18:36, Carl Eugen Hoyos wrote:
Am So., 21. März 2021 um 23:31 Uhr schrieb Mark Filipak (ffmpeg)
:
On 2021-03-21 17:50, Carl Eugen Hoyos wrote:
Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg)
:
I think '-framerate 60' may not be needed at all.
On 2021-03-21 17:50, Carl Eugen Hoyos wrote:
Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg)
:
I think '-framerate 60' may not be needed at all.
It is only needed if 60fps recording is wanted.
As said before, setpts should generally be avoided and
this is even mor
Is the format of a filter script file documented anywhere? I can't find any.
Working command is:
ffmpeg -i source.mkv -filter_script:v test.filter_script -map 0 -codec:v libx265 -codec:a copy
-codec:s copy -dn test.mkv
If the test.filter_script file contains this:
settb=expr=1/72,setpts=
g a video from a desktop that is playing at 60 FPS. My frame rate
for capturing is also set at 60 FPS. Is it likely that a frame of video
appears on LCD and the ffmpeg captures it at a delta of almost a full
frame, i.e., ~16. mec ? If so, then isn't recording a 60 FPS video with
-framerate 60
Synopsis: I present the 'mix' filter (in compact format) followed by criticism followed by my
rewrite followed by remaining questions.
Tip: Before responding, I suggest you save time and effort by reading below the divider (=). If
I have it right, then kindly say so; otherwise, let me know
On 2021-03-19 03:56, tai truong wrote:
Hi every one,
Sorry for my first naive question. As googling, I found some talk about fpga
hevc encode plugin for ffmpeg from Xilinx. Is there anyone have work on it?
Some result/benchmark on performance either for suggestions and views. Thank
you ver
On 2021-03-18 01:55, pdr0 wrote:
https://www.mediafire.com/file/m46kc4p1uvt7ae3/cadence_tests.zip/file
Thanks again. I haven't tested my filters on cadence.mp4 yet to see if they
work as expected.
How did you make cadence.mp4? Did you use ffmpeg to make it? Or did you use
something else?
I
On 2021-03-18 01:55, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
I hoped that "marked as interlaced" [1] meant that
'select=expr=not(eq(interlace_type\,TOPFIRST)+eq(interlace_type\,BOTTOMFIRST))'
[2]
would work. However, the 'select' doesn't work. I'm
Addendum:
Key: 'p' : progressive frame | 'c' : combed frame | 'r' : repeated frame
Sorry, I deleted some stuff without realizing the stuff included the key.
On 2021-03-17 20:27, Mark Filipak (ffmpeg) wrote:
Does something like this scheme already ex
Does something like this scheme already exist? No? Can it be implemented?
Implementation example:
streampatterns=span=20:patterns=p c ccppp ccprp,
split=5[p][c][ccppp][ccprp][else],
[p]select=eq(STREAM_PATTERN,p), ... progressive stream ...[prog],
[c]select=eq(STREAM_PATTERN,c), ... scan-interla
On 2021-03-15 06:43, Paul B Mahol wrote:
On Sun, Mar 14, 2021 at 11:18 PM Mark Filipak (ffmpeg) wrote:
On 2021-03-14 10:47, Mark Filipak (ffmpeg) wrote:
I hoped that "marked as interlaced" [1] meant that
'select=expr=not(eq(interlace_type\,TOPFIRST)+eq(interlace_type\,BO
On 2021-03-15 13:43, Hassan wrote:
Hello,
I am using ffmpeg on a Windows 10 machine and I want to record the desktop
at a high frame rate while appending accurate timestamps to each frame.
I am recording my desktop using the following command:
ffmpeg -f gdigrab -framerate 60 -i desktop -vf "set
On 2021-03-14 10:47, Mark Filipak (ffmpeg) wrote:
I hoped that "marked as interlaced" [1] meant that
'select=expr=not(eq(interlace_type\,TOPFIRST)+eq(interlace_type\,BOTTOMFIRST))'
[2]
Have I made myself understood? Do you see the problem?
...progressive.&.
I hoped that "marked as interlaced" [1] meant that
'select=expr=not(eq(interlace_type\,TOPFIRST)+eq(interlace_type\,BOTTOMFIRST))'
[2]
would work. However, the 'select' doesn't work. I'm counting on the 'select' working -- not working
is a complete show stopper.
Is there some other species o
On 2021-03-11 18:37, Reino Wijnsma wrote:
On 2021-03-09T20:43:21+0100, Mark Filipak (ffmpeg) wrote:
On 2021-03-09 03:58, Michael Koch wrote:
These links might help:
https://stackoverflow.com/questions/2017843/fetch-frame-count-with-ffmpeg
https://superuser.com/questions/1512575/why-total
On 2021-03-10 21:30, Barry Smith wrote:
-snip-
these are questions that i need answered before I csn even execute any
of the 4 tools included in the build in the bin/ folder.
Hello, Barry,
I can tell you're upset. May I recommend Handbrake for your recodes? It will give you all the power
you
I'm reposting this after realizing that the subject line was a bit misleading. Hopefully, I'll get
some responses...
I'm looking for a way to separate telecined sequences from the rest of a video (via split &
selects). The following is one idea.
The 'fieldmatch' filter has a telecine detector
On 2021-03-09 03:58, Michael Koch wrote:
Am 09.03.2021 um 09:46 schrieb Ulf Zibis:
Am 09.03.21 um 09:26 schrieb Peter White:
On Tue, Mar 09, 2021 at 09:13:14AM +0100, Ulf Zibis wrote:
Hi,,
can one please tell me, how I can get the total number of frames of a video?
ffmpeg -i input -an -sn -
I'm looking for a way to separate telecined sequences from the rest of a video. The following is one
idea.
The 'fieldmatch' filter favors telecined sequences [1]. I want it to drop telecined sequences and
pass the remaining frames (i.e. that are not telecined).
Is there any way to do that?
T
I'm well on my way to creating a single, non-cosmetic, filter complex that will transcode any video
found on DVDs & BDs with excellent results and with zero combing & zero judder. The filters are
purely mechanical -- no blend, no blur, no yadif -- and with results that are far better than
Handbr
On 2021-03-05 21:31, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
On 2021-03-05 11:13, James Darnley wrote:
On 05/03/2021, Mark Filipak (ffmpeg) wrote:
I seek a fields-to-frames filter that does not add cosmetics. In my
pursuit,
I look for such a
filter every time I peruse the filter docs for
On 2021-03-05 11:13, James Darnley wrote:
On 05/03/2021, Mark Filipak (ffmpeg) wrote:
I seek a fields-to-frames filter that does not add cosmetics. In my pursuit,
I look for such a
filter every time I peruse the filter docs for anything. I've yet to find
such a filter.
Do you know of a f
On 2021-03-05 10:35, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
'yadif=mode=send_field' is one way to convert fields to frames at the same
frame size and twice the
FR. It does it by repeating fields, but it also adds cosmetics -- it is,
after all, a motion
interpolation filter.
I seek a
Please, enlighten this poor bastard.
matroska.h is here:
http://patches.ffmpeg.org/doxygen/0.5/matroska_8h-source.html
So, what is this:
http://patches.ffmpeg.org/doxygen/0.5/matroska_8h.html
and why does it exist?
--
In U.S. History: The House Un-American Activities Committee was a committee
Hi All,
'yadif=mode=send_field' is one way to convert fields to frames at the same frame size and twice the
FR. It does it by repeating fields, but it also adds cosmetics -- it is, after all, a motion
interpolation filter.
I seek a fields-to-frames filter that does not add cosmetics. In my pu
On 2021-03-02 13:31, Carl Eugen Hoyos wrote:
Am Di., 2. März 2021 um 17:50 Uhr schrieb Mark Filipak (ffmpeg)
:
I've searched the docs one-by-one. I seek a simpler way to repeat a frame.
Increase the frame rate, either with the fps filter or the ffmpeg option "-r".
They
On 2021-03-04 09:26, Moritz Barsnick wrote:
On Thu, Mar 04, 2021 at 03:57:38 -0500, Mark Filipak (ffmpeg) wrote:
Well, per rational.h, 'num' & 'den' are both integers.
Now, I don't know how '72' is stored. Is it stored as an int64?
They are
On 2021-03-04 11:02, Peter White wrote:
On 03.03.21 23:57, Mark Filipak (ffmpeg) wrote:
On 2021-03-03 11:30, Mark Filipak (ffmpeg) wrote:
I've tried transcoding a 2:21:19 movie via this script:
SET codecs=-codec:v libx265 -x265-params crf=16:qcomp=1.00 -codec:a copy
-codec:s copy -dn
On 2021-03-04 09:36, Michael Koch wrote:
Am 03.03.2021 um 23:57 schrieb Mark Filipak (ffmpeg):
I've tried transcoding a 2:21:19 movie via this script:
SET prep23=settb=expr=1/72,setpts=N*30030
SET cfr23=setpts=N*1001/24000/TB,fps=24000/1001
SET codecs=-codec:v libx265 -x265-params c
On 2021-03-04 01:05, Jim DeLaHunt wrote:
On 2021-03-03 14:57, Mark Filipak (ffmpeg) wrote:
With TB = 1/(72 ticks/s), for a 24.976fps output,
deltaPTS = (1001/24000 frames/s)/(1/(72 ticks/s)) = 30030 ticks/frame
If working time_base (from the AVRational) has an effective resolution of
On 2021-03-03 11:30, Mark Filipak (ffmpeg) wrote:
On 2021-03-03 05:58, Moritz Barsnick wrote:
On Tue, Mar 02, 2021 at 17:32:42 -0500, Mark Filipak (ffmpeg) wrote:
Thank you, Jim. To the best of my knowledge, rational is not a 'C' datatype.
No, but it is an ffmpeg data type, AVRa
On 2021-03-03 05:58, Moritz Barsnick wrote:
On Tue, Mar 02, 2021 at 17:32:42 -0500, Mark Filipak (ffmpeg) wrote:
Thank you, Jim. To the best of my knowledge, rational is not a 'C' datatype.
No, but it is an ffmpeg data type, AVRational, as defined in
libavutil/rational.h, along with
On 2021-03-02 16:34, Jim DeLaHunt wrote:
On 2021-03-02 13:13, Mark Filipak (ffmpeg) wrote:
On 2021-03-02 15:18, Carl Eugen Hoyos wrote:
…timebase is not 64bit, I believe this was already mentioned.
No, it has not been mentioned.
Mark, I can point to three times it has been mentioned, in
On 2021-03-02 15:18, Carl Eugen Hoyos wrote:
Am Di., 2. März 2021 um 20:51 Uhr schrieb Mark Filipak (ffmpeg)
:
On 2021-03-02 13:31, Carl Eugen Hoyos wrote:
Am Di., 2. März 2021 um 17:50 Uhr schrieb Mark Filipak (ffmpeg)
:
I've searched the docs one-by-one. I seek a simpler way to rep
On 2021-03-02 13:31, Carl Eugen Hoyos wrote:
Am Di., 2. März 2021 um 17:50 Uhr schrieb Mark Filipak (ffmpeg)
:
I've searched the docs one-by-one. I seek a simpler way to repeat a frame.
Increase the frame rate, either with the fps filter or the ffmpeg option "-r".
They
On 2021-03-02 11:53, Paul B Mahol wrote:
On Tue, Mar 2, 2021 at 5:50 PM Mark Filipak (ffmpeg)
wrote:
I've searched the docs one-by-one. I seek a simpler way to repeat a frame.
This:
split[1][2],[1]setpts=(N+floor(N/4))/FR/TB[3],[2]select=eq(mod(n\,4)\,3),setpts=(N*5+4)/FR/TB[4],
I've searched the docs one-by-one. I seek a simpler way to repeat a frame.
This:
split[1][2],[1]setpts=(N+floor(N/4))/FR/TB[3],[2]select=eq(mod(n\,4)\,3),setpts=(N*5+4)/FR/TB[4],[3][4]interleave
works, but perhaps there's an easier way that I'm just not seeing.
Suggestions are welcome. Thanks!
The ffmpeg filter pipeline assigns a 'PTS' to each frame, frame by frame. Is
*that* 'PTS' an int64_t?
Things I have found.
https://ffmpeg.org/ffmpeg-filters.html#fps-1
"...trim any frames with a negative PTS."
That implies that PTS can be negative (ergo, is a signed integer).
http://svn.ffmp
On 2021-02-27 11:46, Jim DeLaHunt wrote:
On 2021-02-27 01:45, Mark Filipak (ffmpeg) wrote:
I thought that 'fps' just changes the 'frame_rate_code' metadata.
Not at all. Read [1] for part of the story of what the `fps` video filter actually does: "Convert
the vi
On 2021-02-27 04:33, Carl Eugen Hoyos wrote:
Am Sa., 27. Feb. 2021 um 10:26 Uhr schrieb Mark Filipak (ffmpeg)
:
I will try 'settb=expr=1/36,setpts=N*1001/3*36,fps=3/1001'.
From all that was written in this mailing list thread I believe this fps
expression can be e
On 2021-02-27 03:52, Jim DeLaHunt wrote:
On 2021-02-27 00:23, Mark Filipak (ffmpeg) wrote:
On 2021-02-27 02:57, list+ffmpeg-u...@jdlh.com wrote:
On 2021-02-26 23:20, Mark Filipak (ffmpeg) wrote:
showinfo reports 11880, 24120, 36000 because that's what ffmpeg has calculated based on ro
On 2021-02-27 03:29, Carl Eugen Hoyos wrote:
Am Sa., 27. Feb. 2021 um 06:34 Uhr schrieb Mark Filipak (ffmpeg)
:
Question: Why would testsrc.mpg have been created with non-zero timestamp for
frame 0?
Nothing in the MPEG specification requires the first frame to have
a timestamp of 0, so
On 2021-02-27 02:57, list+ffmpeg-u...@jdlh.com wrote:
On 2021-02-26 23:20, Mark Filipak (ffmpeg) wrote:
On 2021-02-27 01:37, Jim DeLaHunt wrote:
-snip-
showinfo reports 11880, 24120, 36000 because that's what ffmpeg has calculated based on rounded ms
(milliseconds).
No, showinfo re
On 2021-02-27 01:37, Jim DeLaHunt wrote:
On 2021-02-26 22:08, Mark Filipak (ffmpeg) wrote:
On 2021-02-27 00:55, Jim DeLaHunt wrote:
On 2021-02-26 18:36, Mark Filipak (ffmpeg) wrote:
That's exactly the point. It is not constant because ffmpeg calculates frame times in integer
millise
On 2021-02-27 00:55, Jim DeLaHunt wrote:
On 2021-02-26 18:36, Mark Filipak (ffmpeg) wrote:
On 2021-02-26 20:42, Jim DeLaHunt wrote:
On 2021-02-26 17:24, Mark Filipak (ffmpeg) wrote:
'ffmpeg -i input.mkv -vf "showinfo" -codec:a copy -codec:s copy -dn output.mkv'
On 2021-02-26 22:53, Carl Zwanzig wrote:
On 2/26/2021 5:55 PM, Mark Filipak (ffmpeg) wrote:
The source video is a 5 second MKV clip from a commercial DVD.
Instead of using unknown data*, I suggest making your own test video so you're absolutely sure of
all the parameters. You could do
On 2021-02-26 22:53, Carl Zwanzig wrote:
On 2/26/2021 5:55 PM, Mark Filipak (ffmpeg) wrote:
The source video is a 5 second MKV clip from a commercial DVD.
Instead of using unknown data*, I suggest making your own test video so you're absolutely sure of
all the parameters. You could do
On 2021-02-26 21:29, Paul B Mahol wrote:
You are living proof that universe is finite and human stupidity/ignorance
is not.
Paul, I know you're a smart guy and can keep 'N' balls in the air at the same
time.
How do *you* explain this:
'ffmpeg -i input.mkv -vf "settb=expr=1/36,showinfo" -
On 2021-02-26 21:28, Jim DeLaHunt wrote:
On 2021-02-26 17:53, Mark Filipak (ffmpeg) wrote:
… I'm concerned with the internal time base in the filter pipeline that's used to resolve frame
ordering, both video and audio.…
That is the timebase which FFmpeg stores as a rational number,
On 2021-02-26 20:42, Jim DeLaHunt wrote:
On 2021-02-26 17:24, Mark Filipak (ffmpeg) wrote:
On 2021-02-26 20:05, Jim DeLaHunt wrote:
Does input1.mkv in fact have a constant frame rate of 24/1.001 frames/second?
No, it has a constant frame rate of 30/1.001 frames/second.
Sorry, my mistake
On 2021-02-26 20:35, Phil Rhodes via ffmpeg-user wrote:
On Saturday, 27 February 2021, 01:27:22 GMT, Mark Filipak (ffmpeg)
wrote:
No, it has a constant frame rate of 30/1.001 frames/second.
I'm not really following this, but one question which may be worth asking is
wher
On 2021-02-26 20:32, Jim DeLaHunt wrote:
On 2021-02-26 16:53, Mark Filipak (ffmpeg) wrote:
…What I'm suggesting is that ffmpeg convert to a single, 36Hz time base for all videos, for
all time. Then, rounding errors would be *zero*. PTSs would be exact. …
As I told you back
On 2021-02-26 20:05, Jim DeLaHunt wrote:
On 2021-02-26 15:40, Mark Filipak (ffmpeg) wrote:
'ffmpeg -i input.mkv -vf "settb=expr=1/36,showinfo" -codec:a copy -codec:s
copy -dn output.mkv'
partial output shown below.
input.mkv is 30.1.001fps constant frame rate. I exp
Let's wipe the screen between us.
What I'm suggesting is that ffmpeg convert to a single, 36Hz time base for all videos, for all
time. Then, rounding errors would be *zero*. PTSs would be exact.
FFmpeg is superior because, instead of frame numbers, ffmpeg uses PTSs. That decision was very
On 2021-02-26 19:06, Paul B Mahol wrote:
On Sat, Feb 27, 2021 at 1:01 AM Mark Filipak (ffmpeg)
wrote:
On 2021-02-26 18:49, Paul B Mahol wrote:
This is math question, and does not belong here.
Yes, it's a math question. I'm questioning how ffmpeg is doing math.
By converting TB
On 2021-02-26 18:49, Paul B Mahol wrote:
This is math question, and does not belong here.
Yes, it's a math question. I'm questioning how ffmpeg is doing math.
By converting TB to periods with millisecond resolution, it limits temporal resolution to 1 part in
1000 parts no matter what the time
On 2021-02-26 15:51, Paul B Mahol wrote:
Ever looked at (a)settb filter
Thank you, Paul.
'ffmpeg -i input.mkv -vf "settb=expr=1/36,showinfo" -codec:a copy -codec:s
copy -dn output.mkv'
partial output shown below.
input.mkv is 30.1.001fps constant frame rate. I expected deltaPTS to be 1201
How can I force ffmpeg to use a 360kHz time base? (I spent 1/2 day searching.)
Thanks!
Mark.
With a 1kHz time base:
65535 = largest 16-bit integer.
0:01:05.535 = longest running time for 16-bit integer with 1kHz time base..
Conclusion: FFmpeg cannot be using 16-bit integers.
16777215 = largest
On 2021-02-23 13:56, Carl Eugen Hoyos wrote:
Am Di., 23. Feb. 2021 um 06:39 Uhr schrieb Mark Filipak (ffmpeg)
:
at least out of the encoder, ffmpeg encodes frames with PTS resolution = 1ms.
(Since people may be reading this)
To quote Wolfgang Pauli, above is not even wrong.
I'
On 2021-02-23 14:06, list+ffmpeg-u...@jdlh.com wrote:
On 2021-02-23 09:51, Mark Filipak (ffmpeg) wrote:
…Except in "THE MATRIX", the timebase is 90KHz ±0.1.85%. Changing the timebase to something
else is a programming construct and is not real.…
Mark, I think your original qu
On 2021-02-23 13:17, Rob Hallam wrote:
On Tue, 23 Feb 2021 at 17:55, Mark Filipak (ffmpeg)
wrote:
[ information on PTS ]
Interesting information, thank you for sharing those insights.
Without wanting to cast aspersions, does this mean that ffmpeg does
something different with regards to
On 2021-02-23 03:58, Jim DeLaHunt wrote:
On 2021-02-22 21:35, Mark Filipak (ffmpeg) wrote:
On 2021-02-23 00:01, Jim DeLaHunt wrote:
The Presentation Time Stamp (PTS) value which FFmpeg associates with video frames and audio data
is a 64-bit integer. There is an associated time base attribute
Attached are manual parses of sectors 1 & 2 of the DVD "RUNNING ON EMPTY". I'm attaching them
because there's 6200 characters in some of the lines.
I've gathered together the work of other people (cited within) and made some
corrections.
480t24 RUNNING ON EMPTY, 085391184324, VTS_01_1.VOB, sect
On 2021-02-23 02:46, Gyan Doshi wrote:
On 23-02-2021 12:40 pm, Mark Filipak (ffmpeg) wrote:
On 2021-02-23 01:38, Carl Zwanzig wrote:
You missed mentioning the program clock reference (PCR) of the -ts. -And- many references to PTS
directly say that it's contained in a -ts (which if th
On 2021-02-23 01:38, Carl Zwanzig wrote:
You missed mentioning the program clock reference (PCR) of the -ts. -And- many references to PTS
directly say that it's contained in a -ts (which if the -ts contains a -ps, is correct).
The answers are in a GIF illustration (not text) in the H.262 spec
On 2021-02-23 01:08, Mark Filipak (ffmpeg) wrote:
On 2021-02-23 00:41, Carl Zwanzig wrote:
-snip-
... 'Presentation time stamps have a resolution of 90kHz", so at 29.97fps the PTSs should be
3003.003... apart. Since they're whole numbers, that would be 3003, 6006, etc with an
On 2021-02-23 00:41, Carl Zwanzig wrote:
-snip-
If you're starting with mpeg-ps or -ts, ...
There's no such thing as PTS in mpeg-ts. The transport stream sets the SCR (System Clock Reference)
(aka TB) but the PTSs are in the presentation stream, stored as integer ticks of the SCR.
I've been
On 2021-02-23 00:01, Jim DeLaHunt wrote:
On 2021-02-22 18:53, Mark Filipak (ffmpeg) wrote:
Are these correct?
ffmpeg PTS resolution is 1ms.…
This at least is not correct AFAIK.
Thanks, Jim. I certainly didn't expect such a lengthy response. I'll respond
more verbosely.
The Pr
1 - 100 of 321 matches
Mail list logo
