On Tue, Feb 16, 2021 at 1:23 PM Mark Filipak (ffmpeg)
wrote:
>
> On 02/15/2021 08:54 PM, Chris Angelico wrote:
> > On Tue, Feb 16, 2021 at 12:45 PM Mark Filipak (ffmpeg)
> > wrote:
> -bigsnip-
> >> The rest of 'C' syntax, and precedent, and operators, etc. I know. It's
> >> just pointers that
On 02/15/2021 08:54 PM, Chris Angelico wrote:
On Tue, Feb 16, 2021 at 12:45 PM Mark Filipak (ffmpeg)
wrote:
-bigsnip-
The rest of 'C' syntax, and precedent, and operators, etc. I know. It's just
pointers that mystify
me. Now I understand what a struct actually is but pointers?... not so
On Tue, Feb 16, 2021 at 12:45 PM Mark Filipak (ffmpeg)
wrote:
>
> On 02/15/2021 06:47 PM, Chris Angelico wrote:
> > On Tue, Feb 16, 2021 at 8:44 AM Mark Filipak (ffmpeg)
> > wrote:
> >>
> >> On 02/15/2021 04:32 PM, Carl Zwanzig wrote:
> >>> On 2/15/2021 1:26 PM, Mark Filipak (ffmpeg) wrote:
>
On 02/15/2021 06:47 PM, Chris Angelico wrote:
On Tue, Feb 16, 2021 at 8:44 AM Mark Filipak (ffmpeg)
wrote:
On 02/15/2021 04:32 PM, Carl Zwanzig wrote:
On 2/15/2021 1:26 PM, Mark Filipak (ffmpeg) wrote:
Yes, I'm aware of C++. It's sort of a 'C' language architecture hack, isn't it?
More
On Tue, Feb 16, 2021 at 8:44 AM Mark Filipak (ffmpeg)
wrote:
>
> On 02/15/2021 04:32 PM, Carl Zwanzig wrote:
> > On 2/15/2021 1:26 PM, Mark Filipak (ffmpeg) wrote:
> >> Yes, I'm aware of C++. It's sort of a 'C' language architecture hack,
> >> isn't it?
> > More like butchery ...
>
> O...
On Tue, Feb 16, 2021 at 8:29 AM Mark Filipak (ffmpeg)
wrote:
>
> On 02/15/2021 06:38 AM, Chris Angelico wrote:
> > On Mon, Feb 15, 2021 at 9:21 PM Mark Filipak (ffmpeg)
> > wrote:
> >> On 02/15/2021 01:56 AM, Chris Angelico wrote:
> >>> On Mon, Feb 15, 2021 at 5:32 PM Mark Filipak (ffmpeg)
> >>>
On 02/15/2021 04:32 PM, Carl Zwanzig wrote:
On 2/15/2021 1:26 PM, Mark Filipak (ffmpeg) wrote:
Yes, I'm aware of C++. It's sort of a 'C' language architecture hack, isn't it?
More like butchery ...
O... that's harsh. :-)
Glad it's making more sense now.
z!
Thanks for the
On 2/15/2021 1:26 PM, Mark Filipak (ffmpeg) wrote:
Yes, I'm aware of C++. It's sort of a 'C' language architecture hack, isn't it?
More like butchery than hack, but yes.
Glad it's making more sense now.
z!
___
ffmpeg-user mailing list
On 02/15/2021 06:38 AM, Chris Angelico wrote:
On Mon, Feb 15, 2021 at 9:21 PM Mark Filipak (ffmpeg)
wrote:
On 02/15/2021 01:56 AM, Chris Angelico wrote:
On Mon, Feb 15, 2021 at 5:32 PM Mark Filipak (ffmpeg)
wrote:
frame->pts = (
(s->start_time == AV_NOPTS_VALUE) ? 0 : s->start_time)
On Mon, 15 Feb 2021 at 14:48, Phil Rhodes via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
>> On Monday, 15 February 2021, 13:58:30 GMT, Michael Koch <
astroelectro...@t-online.de> wrote:
>> A few developers (not all!) are actively fighting against any changes
in the documentation. It seems
>>
On Monday, 15 February 2021, 13:58:30 GMT, Michael Koch
wrote:
> A few developers (not all!)
> are actively fighting against any changes in the documentation. It seems>
> they are really convinced that the documentation is perfect as it is.
Agreed. I think it's an extension of a situation
Jim,
I am in the camp that believes that the measure of adequate FFmpeg
documentation is that it describes what an FFmpeg user needs to know
about the behaviour of that filter, in all respects, without having to
read the source code. By that measure, I believe that FFmpeg's
documentation for
On Monday, 15 February 2021, 11:39:05 GMT, Chris Angelico
wrote:
> > and then 'frame' would be a pointer to an in-memory structure of that
> > type. When you refer to 'frame->pts', that means 'look at the spot in
> > memory three words in from where frame points, and assign to that'.
>
On Mon, Feb 15, 2021 at 9:21 PM Mark Filipak (ffmpeg)
wrote:
>
> On 02/15/2021 01:56 AM, Chris Angelico wrote:
> > On Mon, Feb 15, 2021 at 5:32 PM Mark Filipak (ffmpeg)
> > wrote:
> >>> frame->pts = (
> >>>(s->start_time == AV_NOPTS_VALUE) ? 0 : s->start_time) +
> >>>
On 02/15/2021 01:56 AM, Chris Angelico wrote:
On Mon, Feb 15, 2021 at 5:32 PM Mark Filipak (ffmpeg)
wrote:
frame->pts = (
(s->start_time == AV_NOPTS_VALUE) ? 0 : s->start_time) +
av_rescale(outlink->frame_count_in, s->ts_unit.num, s->ts_unit.den);
I don't know what this:
On Mon, Feb 15, 2021 at 5:32 PM Mark Filipak (ffmpeg)
wrote:
> > frame->pts = (
> > (s->start_time == AV_NOPTS_VALUE) ? 0 : s->start_time) +
> > av_rescale(outlink->frame_count_in, s->ts_unit.num, s->ts_unit.den);
>
> I don't know what this: 'frame->pts', means. I have written a ton
On 02/15/2021 12:35 AM, Carl Zwanzig wrote:
On 2/14/2021 5:54 PM, Mark Filipak (ffmpeg) wrote:
On 02/14/2021 08:44 PM, Paul B Mahol wrote:
See source code of telecine filter. ...
I can't read 'C'.
You really ought to learn, it's not that hard to _read_ although the context and the data
On 2/14/2021 5:54 PM, Mark Filipak (ffmpeg) wrote:
On 02/14/2021 08:44 PM, Paul B Mahol wrote:
See source code of telecine filter. ...
I can't read 'C'.
You really ought to learn, it's not that hard to _read_ although the context
and the data names matter a lot. And there are details
On 02/14/2021 08:44 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 2:39 AM Mark Filipak (ffmpeg)
wrote:
On 02/14/2021 08:28 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 2:23 AM Mark Filipak (ffmpeg) <
markfili...@bog.us>
wrote:
On 02/14/2021 08:13 PM, Paul B Mahol wrote:
On Mon, Feb
On Mon, Feb 15, 2021 at 2:39 AM Mark Filipak (ffmpeg)
wrote:
> On 02/14/2021 08:28 PM, Paul B Mahol wrote:
> > On Mon, Feb 15, 2021 at 2:23 AM Mark Filipak (ffmpeg) <
> markfili...@bog.us>
> > wrote:
> >
> >> On 02/14/2021 08:13 PM, Paul B Mahol wrote:
> >>> On Mon, Feb 15, 2021 at 1:46 AM Mark
On 02/14/2021 08:28 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 2:23 AM Mark Filipak (ffmpeg)
wrote:
On 02/14/2021 08:13 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 1:46 AM Mark Filipak (ffmpeg) <
markfili...@bog.us>
wrote:
On 02/14/2021 07:34 PM, Paul B Mahol wrote:
On Mon, Feb
On Mon, Feb 15, 2021 at 2:23 AM Mark Filipak (ffmpeg)
wrote:
> On 02/14/2021 08:13 PM, Paul B Mahol wrote:
> > On Mon, Feb 15, 2021 at 1:46 AM Mark Filipak (ffmpeg) <
> markfili...@bog.us>
> > wrote:
> >
> >> On 02/14/2021 07:34 PM, Paul B Mahol wrote:
> >>> On Mon, Feb 15, 2021 at 12:50 AM Mark
On 02/14/2021 08:19 PM, Phil Rhodes via ffmpeg-user wrote:
How does all this interact with files from cameras with very stable timing,
such as broadcast and cinema cameras? ...
What is the antecedent of "this"? We've received no information yet, so how can you refer
to "this"?
Is there
On 02/14/2021 08:13 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 1:46 AM Mark Filipak (ffmpeg)
wrote:
On 02/14/2021 07:34 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 12:50 AM Mark Filipak (ffmpeg) <
markfili...@bog.us>
wrote:
Disclosure: Everything that follows may be wrong.
I
On Mon, Feb 15, 2021 at 2:19 AM Phil Rhodes via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> How does all this interact with files from cameras with very stable
> timing, such as broadcast and cinema cameras?
> Is there not a risk of long-term rounding errors?
>
PTS and TB (timebase) are used
How does all this interact with files from cameras with very stable timing,
such as broadcast and cinema cameras?
Is there not a risk of long-term rounding errors?
P
On Monday, 15 February 2021, 01:13:37 GMT, Paul B Mahol
wrote:
On Mon, Feb 15, 2021 at 1:46 AM Mark Filipak (ffmpeg)
On Mon, Feb 15, 2021 at 1:46 AM Mark Filipak (ffmpeg)
wrote:
> On 02/14/2021 07:34 PM, Paul B Mahol wrote:
> > On Mon, Feb 15, 2021 at 12:50 AM Mark Filipak (ffmpeg) <
> markfili...@bog.us>
> > wrote:
> >
> >> Disclosure: Everything that follows may be wrong.
> >>
> >> I reckon that, except for
On 2/14/2021 4:34 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 12:50 AM Mark Filipak (ffmpeg)
wrote:
If so, wouldn't it be helpful if filter documentation included how it
generates PTSs?
PTS are not generated.
-Something- generates the PTS, although maybe not the filter. OTOH if an
On 02/14/2021 07:34 PM, Paul B Mahol wrote:
On Mon, Feb 15, 2021 at 12:50 AM Mark Filipak (ffmpeg)
wrote:
Disclosure: Everything that follows may be wrong.
I reckon that, except for a few filters, the important metric is PTS, not
the frame #s assigned at a
filter's input node nor its
On Mon, Feb 15, 2021 at 12:50 AM Mark Filipak (ffmpeg)
wrote:
> Disclosure: Everything that follows may be wrong.
>
> I reckon that, except for a few filters, the important metric is PTS, not
> the frame #s assigned at a
> filter's input node nor its wall-clock arrival time at a filter's input
>
On 2021-02-14 15:47, Mark Filipak (ffmpeg) wrote:
…wouldn't it be helpful if filter documentation included how it
generates PTSs?
Filter documentation should include:
…[List of desired items omitted]…
I am in the camp that believes that the measure of adequate FFmpeg
documentation is that
Am Mo., 15. Feb. 2021 um 00:50 Uhr schrieb Mark Filipak (ffmpeg)
:
> Perhaps someday we will be allowed to contribute.
This is probably the most insulting comment I have ever seen here.
Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
32 matches
Mail list logo
