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 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-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
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
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-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.&.
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-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
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
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
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
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-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
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
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
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=
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
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 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 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
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-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
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 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,
...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-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
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-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-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-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
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-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
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
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
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
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 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 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
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-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
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-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
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-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-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-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 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
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 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
Is the input to the bwdif filter fields or frames?
Since, according to previous threads, ffmpeg decoders solely produce frames,
Based on this:
https://ffmpeg.org/ffprobe-all.html#bwdif
I honestly can't figure out which it is: fields or frames.
Thanks!
Note: I'm experimenting with virtual ident
On 09/14/2020 03:23 PM, Bouke wrote:
Note: I'm experimenting with virtual identities in my Thunderbird email client
because the ffmpeg archives publish email addresses and I wish to spoof in
order to avoid spamming harvesters.
And the fact that you are a troll has nothing to do with it?
Ho
On 09/16/2020 09:58 AM, Mark Himsley wrote:
On Mon, 14 Sep 2020 at 15:42, Mark Filipak (ffmpeg) wrote:
Is the input to the bwdif filter fields or frames?
The input to every filter in a filter chain is a raster of pixels.
That raster may contain one frame or two fields.
The bwdif filter will
On 09/18/2020 03:01 PM, Carl Eugen Hoyos wrote:
Am 16.09.2020 um 15:58 schrieb Mark Himsley :
On Mon, 14 Sep 2020 at 15:42, Mark Filipak (ffmpeg) wrote:
Is the input to the bwdif filter fields or frames?
The input to every filter in a filter chain is a raster of pixels.
That raster may
On 09/20/2020 05:44 PM, Carl Eugen Hoyos wrote:
Am So., 20. Sept. 2020 um 06:59 Uhr schrieb Mark Filipak (ffmpeg)
:
On 09/18/2020 03:01 PM, Carl Eugen Hoyos wrote:
Am 16.09.2020 um 15:58 schrieb Mark Himsley :
On Mon, 14 Sep 2020 at 15:42, Mark Filipak (ffmpeg) wrote:
Is the input to the
On 09/21/2020 03:33 AM, Carl Eugen Hoyos wrote:
Am 21.09.2020 um 01:56 schrieb Mark Filipak (ffmpeg) :
How can it 'deinterlace' a single field?
It can’t and that is what I explained several times in my last two mails.
Here is what you wrote:
"The following makes little se
On 09/21/2020 09:26 AM, Paul B Mahol wrote:
On Mon, Sep 21, 2020 at 08:11:59AM -0400, Mark Filipak (ffmpeg) wrote:
On 09/21/2020 03:33 AM, Carl Eugen Hoyos wrote:
Am 21.09.2020 um 01:56 schrieb Mark Filipak (ffmpeg) :
How can it 'deinterlace' a single field?
It can’t and that
On 09/21/2020 11:24 AM, Edward Park wrote:
Morning,
Hi Ted!
Regarding 'progressive_frame', ffmpeg has 'interlaced_frame' in lieu of 'progressive_frame'.
I think that 'interlaced_frame' = !'progressive_frame' but I'm not sure. Confirming it as a
fact is a side project that I work on only occ
On 09/21/2020 06:07 PM, Carl Eugen Hoyos wrote:
Am Mo., 21. Sept. 2020 um 14:16 Uhr schrieb Mark Filipak (ffmpeg)
:
On 09/21/2020 03:33 AM, Carl Eugen Hoyos wrote:
Am 21.09.2020 um 01:56 schrieb Mark Filipak (ffmpeg) :
How can it 'deinterlace' a single field?
It can’t and that
On 09/21/2020 06:54 PM, Bouke wrote:
On 22 Sep 2020, at 00:44, Mark Filipak (ffmpeg) wrote:
Paul Mahol accused me
He was not the only one.
Go away!
and no, this is not aimed at you, but to the rest of the bunch to NOT FEED THE
TROLL
You calling me a troll doesn't make
On 09/22/2020 05:59 AM, Nicolas George wrote:
Mark Filipak (ffmpeg) (12020-09-21):
No so, Ted. The following two definitions are from the glossary I'm preparing
(and which cites H.262).
Quoting yourself does not prove you right.
You are correct. That's why H.262 is in the defin
On 09/22/2020 04:20 AM, Edward Park wrote:
Not so, Ted. The following two definitions are from the glossary I'm preparing
(and which cites H.262).
Ah okay I thought that was a bit weird, I assume it was a typo but I saw h.242 and
thought two different types of "frames" were being mixed. Befo
On 09/23/2020 12:19 PM, Greg Oliver wrote:
On Tue, Sep 22, 2020 at 1:14 PM Mark Filipak (ffmpeg)
wrote:
-snip-
He has repeatedly posted to either understand or define better
the internals of ffmpeg itself...
Thanks for the kind words.
Yaknow, I'm not special or a wizard. I suffer the
On 09/23/2020 03:53 PM, Carl Eugen Hoyos wrote:
Am Di., 22. Sept. 2020 um 00:47 Uhr schrieb Mark Filipak (ffmpeg)
:
On 09/21/2020 06:07 PM, Carl Eugen Hoyos wrote:
Am Mo., 21. Sept. 2020 um 14:16 Uhr schrieb Mark Filipak (ffmpeg)
:
Here is what you wrote:
"The following makes little
On 09/23/2020 05:27 PM, Paul B Mahol wrote:
On Wed, Sep 23, 2020 at 04:26:27PM -0400, Mark Filipak (ffmpeg) wrote:
On 09/23/2020 03:53 PM, Carl Eugen Hoyos wrote:
Am Di., 22. Sept. 2020 um 00:47 Uhr schrieb Mark Filipak (ffmpeg)
:
On 09/21/2020 06:07 PM, Carl Eugen Hoyos wrote:
Am Mo., 21
On 09/24/2020 12:52 AM, Edward Park wrote:
Hi,
I just realized that the station was public, so I just tried:
% ffplay -nodisp -vn
"https://jrtv-live.ercdn.net/jrradio/englishradiovideo.m3u8”
no issues.
I did try without that buffer flag, but that had no effect. I’m going to try
updating ffpla
On 09/24/2020 09:21 AM, Paul Bourke wrote:
Nice idea, what upscaling methods you use? Do you use swscale by any chance?
Not sure I understand. I don't upscale the movie/image, rather my code
that creates the remap filters just creates the maps 2,3,4 times
bigger than I eventually plan to use.
On 09/26/2020 08:42 AM, Peter wrote:
Hi,
I have a file MPEG-PS, AVC264 with audio code G711u.
It does contain absolute timestamp in each frame i.e I can say when exactly each second of this
video was shot.
I want to do the following:
I'm still exploring/learning the structures in program s
From https://www.ffmpeg.org/doxygen/trunk/frame_8h_source.html#l00309
typedef struct AVFrame {
#define AV_NUM_DATA_POINTERS 8
/**
* pointer to the picture/channel planes.
* This might be different from the first allocated byte
*
* Some decoders access areas outside 0,0 - width,height...
1, Are sa
On 09/27/2020 03:31 PM, James Darnley wrote:
On 27/09/2020, Mark Filipak (ffmpeg) wrote:
From https://www.ffmpeg.org/doxygen/trunk/frame_8h_source.html#l00309
typedef struct AVFrame {
#define AV_NUM_DATA_POINTERS 8
/**
* pointer to the picture/channel planes.
* This might be different from
In frame.h, I think that this line:
352 * but for planar audio with more channels that can fit in data,
should be:
352 * but for planar audio with more channels than can fit in data,
How do I confirm it and make the correction?
Thanks!
--
The U.S. political problem? Amateurs are d
On 09/28/2020 03:49 PM, James Darnley wrote:
On 28/09/2020, Mark Filipak (ffmpeg) wrote:
On 09/27/2020 03:31 PM, James Darnley wrote:
On 27/09/2020, Mark Filipak (ffmpeg) wrote:
2, Are the width & height indexes in bytes or samples? If bytes, how are
8-bit v. 10-bit v. 12-bit
pixel for
I've spent 2 days studying frame.h, pixfmt.h, dpx.c, packet.h, and escape124.c.
I haven't learned a damn thing.
Despite their vagueness and ambiguity, reading and understanding H.222 & H.262 are dead easy by
comparison [1].
I just want to understand the frame structures that ffmpeg creates, an
On 09/29/2020 04:06 AM, Michael Koch wrote:
Am 29.09.2020 um 04:28 schrieb Mark Filipak (ffmpeg):
I just want to understand the frame structures that ffmpeg creates, and that ffmpeg uses in
processing and filtering. Are Y, Cb, Cr separate buffers? That would be logical. Or are the Y, Cb,
Cr
On 09/29/2020 09:37 AM, Michael Koch wrote:
Am 29.09.2020 um 14:58 schrieb Mark Filipak (ffmpeg):
On 09/29/2020 04:06 AM, Michael Koch wrote:
Am 29.09.2020 um 04:28 schrieb Mark Filipak (ffmpeg):
I just want to understand the frame structures that ffmpeg creates, and that ffmpeg uses in
On 09/29/2020 09:20 AM, Devin Heitmueller wrote:
Hi Mark,
Hi Devin. Thanks much!
Your response came in while I was composing my previous message. I see (below) that performance is a
major issue. That absolutely makes sense because, after accuracy, speed is the next most important
objective (
On 09/29/2020 10:46 AM, Michael Koch wrote:
Am 29.09.2020 um 16:26 schrieb Mark Filipak (ffmpeg):
On 09/29/2020 09:37 AM, Michael Koch wrote:
Am 29.09.2020 um 14:58 schrieb Mark Filipak (ffmpeg):
On 09/29/2020 04:06 AM, Michael Koch wrote:
Am 29.09.2020 um 04:28 schrieb Mark Filipak (ffmpeg
On 09/29/2020 11:09 AM, Dave Stevens wrote:
On Tue, 29 Sep 2020 10:48:42 -0400
"Mark Filipak (ffmpeg)" wrote:
Hi Devin. Thanks much!
Your response came in while I was composing my previous message. I
see (below) that performance is a
Because it reverses the normal order of rea
On 09/29/2020 11:44 AM, Devin Heitmueller wrote:
On Tue, Sep 29, 2020 at 11:29 AM Mark Filipak (ffmpeg)
wrote:
Oh, dear, that's what "packed" means? ...very misleading name, eh? How are
fields handled? Are the
pixels assumed to be unfielded (meaning so-called "progressive&
On 09/29/2020 12:57 PM, Devin Heitmueller wrote:
On Tue, Sep 29, 2020 at 12:28 PM Mark Filipak (ffmpeg)
wrote:
-snip-
I would encourage you stop trying to invent new terminology ...
-snip-
With due respect to you, I'm not trying to invent new terminology. I'm trying to creat
I seek your comments regarding the following glossary entries (that have been reformatted to fit
email). Kindly take your time.
-Mark.
DAR (display aspect ratio [1]) [noun]: 1, The intended display's
width-to-height aspect as a minimized, H:V, integer ratio (e.g.
16:9, 4:3) distingushed by
On 09/30/2020 06:08 PM, Jim DeLaHunt wrote:
On 2020-09-30 13:09, Mark Filipak (ffmpeg) wrote:
I seek your comments regarding the following glossary entries (that have been reformatted to fit
email). Kindly take your time.
-Mark.
DAR (display aspect ratio [1]) [noun]: 1, … as a minimized, H:V
Revision: Shorter sentences, better consistency, no extra 'lesson' about how to
minimize ratios.\
Formatted for email, plain text.
DAR (display aspect ratio [1]) [noun]: 1, The width-to-height ratio
(W:H, e.g. 16:9, 4:3) for the intended display. DAR is distingushed
by metadata: 'aspect_rati
Nyquist [adjective]: 1, Reference to the Nyquist–Shannon sampling
theorem. 2, The principle [1] that, to most faithfully reproduce an
image at a given digital display's resolution, the samples must be
made at or above twice the display's resolution, both horizontally &
vertically [2].
[1
Continuing with relatively non controversial entries:
d-NTSC [noun]: 1, The digital equivalent of NTSC distinguished by
binary metadata:
720 samples/row: 'horizontal_size_value' = 0010 1101
'horizontal_size_extension' = 00
480 rows: 'vertical_size_value' = 0001 1110
On 09/30/2020 11:56 PM, Jim DeLaHunt wrote:
On 2020-09-30 20:36, Mark Filipak (ffmpeg) wrote:
Continuing with relatively non controversial entries:
d-NTSC [noun]: 1, The digital equivalent of NTSC distinguished by
binary metadata:
720 samples/row: 'horizontal_size_value' = 0010
On 10/01/2020 01:20 AM, Eduardo Alarcón wrote:
Nyquist is a noun, not an adjective, for Harry Nyquist. ...
Hi Eduardo, Thanks.
Well, technically, a noun used as an adjective: "Nyquist sampling", makes it an adjective, but no
matter.
What if I narrow the scope to solely the sampling theory?
On 10/01/2020 10:38 AM, Eduardo Alarcón wrote:
Mostly the noun/adjective part, the part [1] about SD media and mastering,
seems to be anecdotal information more than a definition of what is the
Nyquist principle, you say that the images are undersampled, but what does
it mean? what is the impact,
On 10/01/2020 11:20 AM, Eduardo Alarcón wrote:
El jue., 1 oct. 2020 a las 12:09, Mark Filipak (ffmpeg) ()
escribió:
On 10/01/2020 10:38 AM, Eduardo Alarcón wrote:
-snip-
Can you suggest better wording? I'd like to see it.
Me too, this is not my native language so i can not suggest a b
On 10/01/2020 12:16 PM, Greg Oliver wrote:
On Wed, Sep 30, 2020 at 6:25 PM Mark Filipak (ffmpeg)
wrote:
-snip-
Mark,
Normally I would absolutely defend your queries as they are technical and
lower level, but I would almost have to side with Bouke from post
(
bwdif filter question
)
You are
On 10/01/2020 01:03 PM, Jim DeLaHunt wrote:
On 2020-10-01 06:27, Mark Filipak (ffmpeg) wrote:
On 09/30/2020 11:56 PM, Jim DeLaHunt wrote:
On 2020-09-30 20:36, Mark Filipak (ffmpeg) wrote:
Continuing with relatively non controversial entries:
d-NTSC [noun]: 1, The digital equivalent of NTSC
On 10/01/2020 02:01 PM, Phil Rhodes via ffmpeg-user wrote:
I don't know who's in charge of this glossary project, but can I please
propose something on the difference between colourspace, subsampling and
luminance encoding. And all the other things people constantly confuse.
No one's in cha
On 10/01/2020 03:21 PM, Jim DeLaHunt wrote:
-snip-
OK, then I think what you have — what you put in your text attachment "d-NTSC & d-PAL .txt" in your
previous message — is two single-line glossary entries, conjoined with entries from a table mapping
H.262 Metadata Values to video types d-NTSC a
On 10/01/2020 05:13 PM, Mark Filipak (ffmpeg) wrote:
On 10/01/2020 03:21 PM, Jim DeLaHunt wrote >> OK, then I think what you have — what you put
in your text attachment "d-NTSC & d-PAL .txt" in
your previous message — is two single-line glossary entries, conjoined with
On 2020-10-01 14:49, Mark Filipak (ffmpeg) wrote:
On 10/01/2020 05:13 PM, Mark Filipak (ffmpeg) wrote:
On 10/01/2020 03:21 PM, Jim DeLaHunt wrote >> OK, then I think what you have — what you put in
your text attachment "d-NTSC & d-PAL .txt" in
your previous message — is two
On 10/01/2020 07:43 PM, Anatoly wrote:
On Wed, 30 Sep 2020 19:21:59 -0400
"Mark Filipak (ffmpeg)" wrote:
Nyquist [adjective]: 1, Reference to the Nyquist-Shannon sampling
theorem. 2, The principle [1] that, to most faithfully reproduce an
image at a given digital display&#x
On 10/02/2020 06:34 AM, Anatoly wrote:
On Thu, 1 Oct 2020 20:25:30 -0400
"Mark Filipak (ffmpeg)" wrote:
On 10/01/2020 07:43 PM, Anatoly wrote:
On Wed, 30 Sep 2020 19:21:59 -0400
"Mark Filipak (ffmpeg)" wrote:
Nyquist [adjective]: 1, Reference to the Nyquist-Shannon s
On 10/02/2020 02:15 PM, Eduardo Alarcón wrote:
El vie., 2 oct. 2020 a las 7:34, Anatoly ()
escribió:
On Thu, 1 Oct 2020 20:25:30 -0400
"Mark Filipak (ffmpeg)" wrote:
When sampling an analog voltage, resolution is the ability to resolve
voltage value within a certain period of
On 10/03/2020 06:41 AM, Anatoly wrote:
On Fri, 2 Oct 2020 20:47:57 -0400
"Mark Filipak (ffmpeg)" wrote:
-snip-
By the way, I've given up trying to make an illustration of
2-dimensional Nyquist sampling. It's too hard.
I think is's easy. Just slale dows to every
On 10/01/2020 10:42 PM, Jim DeLaHunt wrote:
On 2020-10-01 15:37, Mark Filipak (ffmpeg) wrote:
On 2020-10-01 15:30, Jim DeLaHunt wrote:
It is an improvement that you are now stating the context, "MPEG-PS binary metadata values". You
omitted that context before. But you continue to
1 - 100 of 321 matches
Mail list logo
