The "-deinterlace" option was removed in
481575d255195c6c2f32e04686b94de984ae78d4,
over five years ago. Refer to deinterlacing filters instead.
Signed-off-by: Moritz Barsnick
---
doc/ffmpeg.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ffmpeg.texi b/doc/ffmpeg
The option still exists and is effective. See current line 3528 of
fftool/ffmpeg_opt.c and the block at line 822 of fftool/ffmpeg_filter.c
On 17-07-2018 03:06 PM, Moritz Barsnick wrote:
The "-deinterlace" option was removed in
481575d255195c6c2f32e04686b94de984ae78d4,
over five years ago. Re
On Tue, Jul 17, 2018 at 16:00:33 +0530, Gyan Doshi wrote:
>
> The option still exists and is effective. See current line 3528 of
> fftool/ffmpeg_opt.c and the block at line 822 of fftool/ffmpeg_filter.c
>
> On 17-07-2018 03:06 PM, Moritz Barsnick wrote:
> > The "-deinterlace" option was removed
V2: - update performance data
- hold on minterpolate filter improvement (need to more talk for
minterpolate improvement)
Jun Zhao (2):
lavutil/pixelutils: add sad_32x32 in pixelutils API.
avutil/pixelutils: sad_32x32 sse2/avx2 optimizations.
libavutil/pixelutils.c |2 +
li
add ff_pixelutils_sad_32x32_sse2, ff_pixelutils_sad_{a,u}_32x32_sse2,
ff_pixelutils_sad_32x32_avx22, ff_pixelutils_sad_{a,u}_32x32_avx2
use perf record/report profiling, get instructions:u for avx2 sad_32x32:
72.05% pixelutils pixelutils [.] block_sad_32x32_c
18.50% pixelutils pixelut
add sad_32x32 in pixelutils API, and update the fate.
Signed-off-by: Jun Zhao
---
libavutil/pixelutils.c |2 ++
libavutil/tests/pixelutils.c |2 +-
tests/ref/fate/pixelutils| 12
3 files changed, 15 insertions(+), 1 deletions(-)
diff --git a/libavutil/pixelutils
Hi Michael,
Of course we should not check in a change that is incorrect. So thank you
for your thorough review.
However, could you help me understand which part exactly of the below do
you think is incorrect?
Before:
int nb_in = av_get_channel_layout_nb_channels(s->in_ch_layout);
This is clear
Ah yeah that makes a lot of sense, Devin. I will keep that in mind for the ntv2
avdevice I created for use with our Kona4.
I basically copied the exact structure of the decklink libavdevice as my
starting point anyway. It isn’t nearly as flexible and focuses exclusively on
capture (demuxing), b
On 17-07-2018 04:52 PM, Moritz Barsnick wrote:
I guess it was undeprecated by making it work properly again, which is
fair enough, as far as I'm concerned. Still, is it preferred to use a
filter?
Yes, the CLI option is global, so applies to all video streams. Most
invocations I've seen of i
From: Archer Chang
Some QNAP surveillance system will only change audio type id
WAVE_FORMAT_RAW_AAC1
to 0x0AAC but not audio track itself.
---
libavformat/riffdec.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavformat/riffdec.c b/libavformat/riffdec.c
index b448f91..fe22610 100644
0001-add-missing-padding-to-nearest-WORD-boundary-AVI.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hi,
2018-06-28 7:20 GMT-03:00 Sergey Lavrushkin :
>
> Here is the patch with fixed warnings.
I already pushed the previous patch and fixed the compiler warnings.
If there is any change besides the warnings could you send a new patch
against latest git HEAD?
Thanks!
___
2018-07-17 16:21 GMT-03:00 Pedro Arthur :
> Hi,
>
> 2018-06-28 7:20 GMT-03:00 Sergey Lavrushkin :
>>
>> Here is the patch with fixed warnings.
>
> I already pushed the previous patch and fixed the compiler warnings.
> If there is any change besides the warnings could you send a new patch
> against
On Tue, Jul 17, 2018 at 8:15 PM wrote:
>
> From: Archer Chang
>
> Some QNAP surveillance system will only change audio type id
> WAVE_FORMAT_RAW_AAC1
> to 0x0AAC but not audio track itself.
> ---
> libavformat/riffdec.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavformat/riff
YUV410P requires that sizes are divisible by 4. There seem to be
some encoders that ignore that and encode a different value in
the bitstream itself. Handle that case by exporting the relative
cropping information.
---
Alternatively it is possible to always enforce mod4 sizes and call
it a day.
Vit
YUV410P requires that sizes are divisible by 4. There are some encoders
(including ffmpeg's) that ignore this constraint and encode a different
value in the bitstream itself. Handle that case by exporting the relative
cropping information.
---
Alternatively it is possible to always enforce mod4 siz
On Tue, Jul 17, 2018, at 11:29 AM, Pedro Arthur wrote:
>
> It seems gmail just delivered your second patch email from 06/28 today
> (delivered after 1670067 seconds), that's why already pushed the first
> one and fixed the warnings.
It was stuck in the ffmpeg-devel moderation queue due to its size
2018-07-17 21:39 GMT+02:00, Vittorio Giovara :
> YUV410P requires that sizes are divisible by 4. There seem to be
> some encoders that ignore that and encode a different value in
> the bitstream itself. Handle that case by exporting the relative
> cropping information.
Can you provide a sample?
T
From d7bd55c3d280c10b990577003a985296f10a2b59 Mon Sep 17 00:00:00 2001
From: Fredrik Hubinette
Date: Tue, 17 Jul 2018 14:35:55 -0700
Subject: [PATCH] Avoid undefined behavior when start_time_text is -1<<63
---
libavformat/utils.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
2018-07-12 14:39 GMT+02:00, archer.ch...@gmail.com :
> From: Archer Chang
>
> Some QNAP surveillance system will only change audio type id
> WAVE_FORMAT_RAW_AAC1
> to 0x0AAC but not audio track itself.
Please provide a sample.
Thank you, Carl Eugen
___
2018-07-17 21:39 GMT+02:00, Vittorio Giovara :
> YUV410P requires that sizes are divisible by 4.
Do you mean that AV_PIX_FMT_YUV410P requires it?
Where is this documented?
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.or
On Tue, Jul 17, 2018 at 11:54 PM Carl Eugen Hoyos wrote:
>
> 2018-07-17 21:39 GMT+02:00, Vittorio Giovara :
> > YUV410P requires that sizes are divisible by 4.
>
> Do you mean that AV_PIX_FMT_YUV410P requires it?
> Where is this documented?
>
Its a consequence of the subsampling factor. 4:1:0 is
2018-07-17 23:58 GMT+02:00, Hendrik Leppkes :
> On Tue, Jul 17, 2018 at 11:54 PM Carl Eugen Hoyos
> wrote:
>>
>> 2018-07-17 21:39 GMT+02:00, Vittorio Giovara :
>> > YUV410P requires that sizes are divisible by 4.
>>
>> Do you mean that AV_PIX_FMT_YUV410P requires it?
>> Where is this documented?
>
2018-07-10 20:06 GMT+02:00, stefan.becker...@gmx.de :
Please provide a sample.
Thank you, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, Jul 18, 2018 at 12:13 AM Carl Eugen Hoyos wrote:
>
> 2018-07-17 23:58 GMT+02:00, Hendrik Leppkes :
> > On Tue, Jul 17, 2018 at 11:54 PM Carl Eugen Hoyos
> > wrote:
> >>
> >> 2018-07-17 21:39 GMT+02:00, Vittorio Giovara :
> >> > YUV410P requires that sizes are divisible by 4.
> >>
> >> Do
2018-07-18 0:22 GMT+02:00, Hendrik Leppkes :
> On Wed, Jul 18, 2018 at 12:13 AM Carl Eugen Hoyos
> wrote:
>>
>> 2018-07-17 23:58 GMT+02:00, Hendrik Leppkes :
>> > On Tue, Jul 17, 2018 at 11:54 PM Carl Eugen Hoyos
>> > wrote:
>> >>
>> >> 2018-07-17 21:39 GMT+02:00, Vittorio Giovara
>> >> :
>> >> >
I'm considering changing the ffmpeg-user and libav-user mailing lists to only
accept messages from subscribed users. ffmpeg-devel would be excluded from this
due to the higher familiarity of mailing lists with that audience. Currently
anyone can send a message to the *-user mailing lists. Althou
On Wed, Jul 18, 2018 at 12:37 AM Carl Eugen Hoyos wrote:
> > This doesn't change how the format is stored, just when cropping is applied.
>
> Then I wonder what exactly this patch fixes (if nothing is changed).
>
"Change when cropping is applied" is nothing? Thats everything this
patch is about,
On Mon, Jul 16, 2018 at 01:03:53PM +0200, James Darnley wrote:
> From: James Darnley
>
> ---
> Michael, can you test this for the same failure you saw last time?
seems to work in all cases i tested
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The worst form
On Wed, Jul 18, 2018 at 12:22:21AM +0200, Hendrik Leppkes wrote:
> On Wed, Jul 18, 2018 at 12:13 AM Carl Eugen Hoyos wrote:
> >
> > 2018-07-17 23:58 GMT+02:00, Hendrik Leppkes :
> > > On Tue, Jul 17, 2018 at 11:54 PM Carl Eugen Hoyos
> > > wrote:
> > >>
> > >> 2018-07-17 21:39 GMT+02:00, Vittorio
On Tue, Jul 17, 2018 at 11:58:06PM +0200, Hendrik Leppkes wrote:
> On Tue, Jul 17, 2018 at 11:54 PM Carl Eugen Hoyos wrote:
> >
> > 2018-07-17 21:39 GMT+02:00, Vittorio Giovara :
> > > YUV410P requires that sizes are divisible by 4.
> >
> > Do you mean that AV_PIX_FMT_YUV410P requires it?
> > Wher
31 matches
Mail list logo
