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
Thanks a lot. I thought for some reason that bswap is for 16-bit values.
вс, 14 февр. 2021 г. в 22:31, Carl Eugen Hoyos :
>
> Am So., 14. Feb. 2021 um 19:07 Uhr schrieb Vasily Postnicov
> :
> >
> > Hello. I try to add APE decoder support to my own library of audio
> > codecs. Since APE is a
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:58, Carl Eugen Hoyos wrote:
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
Oh, my dear Carl, if you think that is the most
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
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 node. For example,
'interleave' performs frame interleaves based on the
Am So., 14. Feb. 2021 um 22:27 Uhr schrieb Mike Soultanian
:
>
> On 2/14/2021 12:40 PM, Carl Eugen Hoyos wrote:
>
> >> Should ffmpeg be able to capture from any capture card
> > Only video4linux2 is supported, how well it works depends
> > primarily on the kernel driver.
> >
> > You probably want
On 2/14/2021 12:40 PM, Carl Eugen Hoyos wrote:
Should ffmpeg be able to capture from any capture card
Only video4linux2 is supported, how well it works depends
primarily on the kernel driver.
You probably want a card that provides data in a pix_fmt
that your hardware encoder supports.
If
Am So., 14. Feb. 2021 um 20:49 Uhr schrieb Mike Soultanian
:
> Should ffmpeg be able to capture from any capture card
Only video4linux2 is supported, how well it works depends
primarily on the kernel driver.
You probably want a card that provides data in a pix_fmt
that your hardware encoder
On 2/14/2021 8:57 AM, Carl Eugen Hoyos wrote:
Am So., 14. Feb. 2021 um 17:53 Uhr schrieb Mike Soultanian
:
On 2/14/2021 3:27 AM, Carl Eugen Hoyos wrote:
Please provide this command line including complete, uncut console
output to allow us understanding what's going on:
$ ffmpeg -ts abs -i
Am So., 14. Feb. 2021 um 19:07 Uhr schrieb Vasily Postnicov
:
>
> Hello. I try to add APE decoder support to my own library of audio
> codecs. Since APE is a closed format, I use ffmpeg as a reference
> trying to understand how it works.
> I cannot understand how this line works in
Hello. I try to add APE decoder support to my own library of audio
codecs. Since APE is a closed format, I use ffmpeg as a reference
trying to understand how it works.
I cannot understand how this line works in libavcodec/apedec.c:
s->bdsp.bswap_buf((uint32_t *) s->data, (const uint32_t *) buf,
Am So., 14. Feb. 2021 um 17:53 Uhr schrieb Mike Soultanian
:
>
> On 2/14/2021 3:27 AM, Carl Eugen Hoyos wrote:
> > Please provide this command line including complete, uncut console
> > output to allow us understanding what's going on:
> > $ ffmpeg -ts abs -i /dev/video0 -f alsa -ac 2 -i
On 2/14/2021 3:27 AM, Carl Eugen Hoyos wrote:
Please provide this command line including complete, uncut console
output to allow us understanding what's going on:
$ ffmpeg -ts abs -i /dev/video0 -f alsa -ac 2 -i hw:CARD=capture,DEV=0
Sure! Here you go:
*pi@raspberrypi:~ $ ffmpeg -ts abs -i
Am So., 14. Feb. 2021 um 09:49 Uhr schrieb Mike Soultanian
:
> *pi@raspberrypi:~ $ v4l2-ctl --set-fmt-video=width=1280,height=720 *
> *pi@raspberrypi:~ $ ffmpeg -f v4l2 -input_format yuyv422 -framerate 30
> -i /dev/video0 -f alsa -ac 2 -i hw:CARD=capture,DEV=0 -c:v libx264 -vf
> format=yuv420p -y
On Sun, Feb 14, 2021 at 12:01 PM Marco Mircoli wrote:
> Yes, the result Is not leveled to the target loudness value
>
Than that issue should be reported to our issue tracker, as loudnorm bug.
>
> Il Ven 12 Feb 2021, 19:26 Paul B Mahol ha scritto:
>
> > On Fri, Feb 12, 2021 at 7:17 PM Marco
Yes, the result Is not leveled to the target loudness value
Il Ven 12 Feb 2021, 19:26 Paul B Mahol ha scritto:
> On Fri, Feb 12, 2021 at 7:17 PM Marco Mircoli
> wrote:
>
> > Il giorno ven 12 feb 2021 alle ore 10:53 Paul B Mahol
> > ha
> > scritto:
> >
> > > On Fri, Feb 12, 2021 at 12:48 AM
On 2/13/2021 5:36 PM, Carl Eugen Hoyos wrote:
It is not possible to synchronize these two streams due
to the different start times, test the ts option:
https://ffmpeg.org/ffmpeg-devices.html#video4linux2_002c-v4l2
Where do I use the -ts option (audio, video, output, all)? And are
you
32 matches
Mail list logo