From 24b8e1c70fd4bf4eb76404fd9e2020fe3bbd90cb Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Tue, 24 Oct 2017 13:25:21 +0800
Subject: [PATCH V2] lavc/vaapi_encode_h264: correct VUI
max_dec_frame_buffering setting.
vseq.max_num_ref_frames not init before the VUI
max_dec_frame_buffering setting, s
>On 10/22/17, 1:28 PM, "Liu Steven" wrote:
>Two patches should be ok, add FATE cases please :)
I am not familiar with FATE and I could not find any sample hlsenc FATE cases
in ffmpeg workspace. Could you please help me with this? If some basic hlsenc
tests are available, I can extend them furthe
On 2017/10/24 13:42, Jun Zhao wrote:
The commit comment is wrong, will re-submit V2 to fix the typo.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
From db142742fa9adb74dea2b376db618075c86a5731 Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Tue, 24 Oct 2017 13:25:21 +0800
Subject: [PATCH] lavc/vaapi_encode_h264: correct VUI max_dec_frame_buffering
setting.
vseq.max_num_ref_frames not init before the VUI
max_dec_frame_buffering setting, so u
Hi,
Am 24.10.17 um 02:43 schrieb Lou Logan:
> On Sat, Oct 21, 2017, at 07:53 AM, Lou Logan wrote:
>> I'll attach the SVG file when I get back home on Monday or Tuesday.
>
> SVG attached. Let me know if you need changes or if the printer needs a
> different format.
then we are talking about a com
This prevents potential ABI issues with GetByteContext.
Signed-off-by: James Almer
---
libavcodec/exif.c | 16 +---
libavcodec/exif.h | 6 --
libavcodec/mjpegdec.c | 2 +-
libavcodec/webp.c | 2 +-
libavformat/avidec.c | 4 ++--
5 files changed, 21 insertions(+),
On 10/23/2017 10:24 PM, Michael Niedermayer wrote:
> On Tue, Oct 24, 2017 at 01:39:03AM +0100, Mark Thompson wrote:
>> On 24/10/17 00:52, Michael Niedermayer wrote:
>>> Hi
>>>
>>> On Mon, Oct 23, 2017 at 04:43:19PM +0100, Mark Thompson wrote:
On 23/10/17 03:56, Michael Niedermayer wrote:
>
On Tue, Oct 24, 2017 at 01:39:03AM +0100, Mark Thompson wrote:
> On 24/10/17 00:52, Michael Niedermayer wrote:
> > Hi
> >
> > On Mon, Oct 23, 2017 at 04:43:19PM +0100, Mark Thompson wrote:
> >> On 23/10/17 03:56, Michael Niedermayer wrote:
> >>> the initialization should be thread safe as it never
On Sat, Oct 21, 2017, at 07:53 AM, Lou Logan wrote:
> I'll attach the SVG file when I get back home on Monday or Tuesday.
SVG attached. Let me know if you need changes or if the printer needs a
different format.
These shirts will be silk screened, right? If so, the green is intended
to be "PMS 35
On 24/10/17 00:52, Michael Niedermayer wrote:
> Hi
>
> On Mon, Oct 23, 2017 at 04:43:19PM +0100, Mark Thompson wrote:
>> On 23/10/17 03:56, Michael Niedermayer wrote:
>>> the initialization should be thread safe as it never writes a different
>>> value in the same spot
>>
>> This is not true; plea
On Sun, Oct 22, 2017 at 05:11:21PM +0200, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> tests/ffserver.regression.ref | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
will apply
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787
On Mon, Oct 23, 2017 at 10:44:07AM +0200, Clément Bœsch wrote:
> On Mon, Oct 23, 2017 at 10:42:53AM +0200, Clément Bœsch wrote:
> [...]
> > how about changing the whole chunk with (untested):
> >
> > prog = av_strdup(my_program_name);
> > dirname = av_dirname(prog);
> > pathname = *dir
Hi!
Trying to encode 256-colour subtitles to dvbsub currently fails in the
"region" section, a hunk of Joolz' patch was not committed six years
ago.
Attached patch has two hunks: The forgotten hunk from the original
patch and further up a fix that I created now (to be committed
separately):
The li
2017-10-24 1:43 GMT+02:00 Niki Bowe :
> On Thu, Oct 19, 2017 at 3:39 PM, Carl Eugen Hoyos
> wrote:
>> Does the patch have a measurable speed impact?
>>
> Is there a standard set of benchmarks I can run?
>
> For typical videos the speed impact is small, due to NALU fitting in cache,
> but for vide
Hi
On Mon, Oct 23, 2017 at 04:43:19PM +0100, Mark Thompson wrote:
> On 23/10/17 03:56, Michael Niedermayer wrote:
> > the initialization should be thread safe as it never writes a different
> > value in the same spot
>
> This is not true; please be very careful with assumptions like this.
>
> Th
On Thu, Oct 19, 2017 at 3:39 PM, Carl Eugen Hoyos
wrote:
> 2017-10-19 20:46 GMT+02:00 Nikolas Bowe :
> > Found via fuzzing.
> > /tmp/poc is a 1 MB mpegts file generated via fuzzing, where 1 packet has
> many NALUs
> > Before this change:
> > $ /usr/bin/time -f "\t%M Max Resident Set Size (Kb)"
On Fri, Oct 20, 2017 at 4:26 PM, Michael Niedermayer wrote:
> On Wed, Oct 18, 2017 at 08:12:50PM -0700, Sasi Inguva wrote:
> > Signed-off-by: Sasi Inguva
> > ---
> > libavformat/mov.c | 16 +++-
> > tests/fate/mov.mak | 6 ++-
> > tests/re
Signed-off-by: Sasi Inguva
---
libavformat/mov.c | 15 +++-
tests/fate/mov.mak | 4 ++
tests/ref/fate/mov-invalid-elst-entry-count | 57 +
3 files changed, 75 insertions(+), 1 deletion(-)
create mode 100644 tests
On Sat, Oct 21, 2017 at 4:00 PM, Clément Bœsch wrote:
> On Sat, Oct 21, 2017 at 09:47:47PM +0200, Carl Eugen Hoyos wrote:
> > 2017-10-21 21:43 GMT+02:00 Clément Bœsch :
> > > On Sat, Oct 21, 2017 at 09:37:06PM +0200, Carl Eugen Hoyos wrote:
> > >> 2017-10-21 18:40 GMT+02:00 Clément Bœsch :
> > >>
This patch enables paletteuse to identify the transparency in incoming
video and tag transparent pixels on outgoing video with the correct
index from the palette.
This requires tracking the transparency index in the palette,
establishing an alpha threshold below which a pixel is considered
transpa
Any update on this patch? We've been carrying it in Chrome for a while.
- dale
On Fri, Apr 7, 2017 at 11:14 AM, Felicia Lim
wrote:
> Hi,
>
> Just wanted to follow up and check if there any changes I should add to
> this patch?
>
> Thanks for taking a look.
>
> Felicia
>
> On Mon, Mar 27, 2017 a
On 9/14/17, Richard Ling wrote:
> Hi,
>
> This patch adds a filter to normalize (contrast stretch) RGB video.
> Comments welcome.
>
> R.
>
> From f08f132ecd79718d0ce6fb07f99c84ab5dd52ee4 Mon Sep 17 00:00:00 2001
> From: Richard Ling
> Date: Thu, 14 Sep 2017 13:18:50 +1000
> Subject: [PATCH] avfil
On Fri, Oct 06, 2017 at 05:33:22PM +0200, Mateusz wrote:
> Fixed DITHER_COPY macro (only C code), updated FATE tests.
>
> PSNR in tests that needed update goes from 50 to 999.99 -- the quality is
> there.
>
> Please review.
>
> Mateusz
>
> libswscale/swscale_unscaled.c | 73
>
Am 20.10.17 um 17:16 schrieb Thilo Borgmann:
> Hi,
>
>>> Some guys at the VDD asked for FFmpeg T-shirts.
>>> I'd like to do a new T-shirt order. The shirts could be given to
>>> multimedia devs who stop at one of our next booths.
>>>
>>> My idea is to order 25 shirts:
>>>
>>> 1*S
>>> 5*M
>>> 10*L
On 10/23/17, James Almer wrote:
> Replaces the now dropped global option.
>
> Addresses ticket #6771.
>
> Signed-off-by: James Almer
> ---
> libavcodec/libx264.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
> index b11ede6198..b5e04d674d 10
Replaces the now dropped global option.
Addresses ticket #6771.
Signed-off-by: James Almer
---
libavcodec/libx264.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
index b11ede6198..b5e04d674d 100644
--- a/libavcodec/libx264.c
+++ b/libavcodec/lib
The fields can be accessed directly, so these are not needed anymore.
Signed-off-by: James Almer
---
libavformat/avformat.h | 30 +-
libavformat/utils.c| 4
libavformat/version.h | 3 +++
3 files changed, 36 insertions(+), 1 deletion(-)
diff --git a/libav
Remove the silly second notice.
Signed-off-by: James Almer
---
libavformat/avformat.h | 65 ++
1 file changed, 28 insertions(+), 37 deletions(-)
diff --git a/libavformat/avformat.h b/libavformat/avformat.h
index ece1b179f3..7594277f06 100644
--- a
On 23/10/17 03:56, Michael Niedermayer wrote:
> the initialization should be thread safe as it never writes a different
> value in the same spot
This is not true; please be very careful with assumptions like this.
The C standard calls this a data race and it is undefined behaviour.
It is not jus
On 10/23/2017 03:24 AM, Michael Niedermayer wrote:
> On Thu, Oct 12, 2017 at 10:59:23AM -0700, John Stebbins wrote:
>> When keyframe intervals of dash segments are not perfectly aligned,
>> fragments in the stream can overlap in time. The previous sorting by
>> timestamp causes packets to be read o
On 10/23/2017 3:56 AM, Michael Niedermayer wrote:
> the initialization should be thread safe as it never writes a different
> value in the same spot
> This would avoid the need to alwas hardcode the tables
Still no reason to *not* put it under ff_thread_once, though,
to minimize work done.
- Dere
The fields can be accessed directly, so these are not needed anymore.
Signed-off-by: James Almer
---
libavutil/frame.c | 2 ++
libavutil/frame.h | 26 ++
libavutil/version.h | 3 +++
3 files changed, 31 insertions(+)
diff --git a/libavutil/frame.c b/libavutil/frame
On Mon, Oct 23, 2017 at 3:22 PM, James Almer wrote:
> On 10/23/2017 5:25 AM, Daniel Kučera wrote:
>> 2017-10-21 13:36 GMT+02:00 Jan Ekstrom :
>>>
>>> This seems to have broken seeking and files ending. FLAC was
>>> experienced yesterday but it seems like it's more general. This was
>>> reported on
On 10/23/2017 5:25 AM, Daniel Kučera wrote:
> 2017-10-21 13:36 GMT+02:00 Jan Ekstrom :
>>
>> This seems to have broken seeking and files ending. FLAC was
>> experienced yesterday but it seems like it's more general. This was
>> reported on the mpv users' channel by sfan5, but I feel like this
>> mi
On 10/23/2017 5:09 AM, Carl Eugen Hoyos wrote:
> 2017-10-23 5:22 GMT+02:00 James Almer :
>> On 10/21/2017 9:31 PM, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> Attached patch silences the many warnings shown when decoding streams
>>> with DolbyVision content.
>>>
>>> Please comment, Carl Eugen
>>>
>>>
>
On Sun, 22 Oct 2017 21:29:52 +0200, Thilo Borgmann
wrote:
> >> So what do others think about colors? Shall I make a 3-color-sample first?
> >> We might do more than one version.
> >> They open again Tuesday...
> >>
> >
> > I personally don't think it's a big deal either way, but green logo would
Hi,
On Mon, Oct 23, 2017 at 4:27 AM, Clément Bœsch wrote:
> On Sun, Oct 22, 2017 at 12:09:04PM -0400, Ronald S. Bultje wrote:
> [...]
> > > > The replacement will never be written if:
> > > > a) nobody cares; AND
> > > > b) we keep delaying the removal
> > > >
> > > > I'm considering veto'ing th
2017-10-23 13:07 GMT+02:00 Carl Eugen Hoyos :
> 2017-10-23 12:31 GMT+02:00 :
>> This patch fixes the MXF format write. This is required for
>> Sony XDCAM Station and Sony Content Browser compatibility.
>> +mxf_write_local_tag(pb, 4, 0x3308);
>> +if (st->codec->pix_fmt == AV_PIX_FMT_YUV420
2017-10-23 12:31 GMT+02:00 :
> This patch fixes the MXF format write. This is required for
> Sony XDCAM Station and Sony Content Browser compatibility.
The patch contains trailing whitespace and tabs, both cannot
be committed to the FFmpeg repository.
You can use tools/patcheck to find the issues
This patch fixes the MXF format write. This is required for Sony XDCAM
Station and Sony Content Browser compatibility.
Axel Technology development team.
0001-Sony-XDCAM-Fix.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ff
On Sun, Oct 22, 2017 at 01:41:57AM +0200, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> fftools/ffmpeg.h | 1 +
> fftools/ffmpeg_opt.c | 16
> 2 files changed, 17 insertions(+)
applied with documentation
[...]
--
Michael GnuPG fingerprint: 9F
On Thu, Oct 12, 2017 at 10:59:23AM -0700, John Stebbins wrote:
> When keyframe intervals of dash segments are not perfectly aligned,
> fragments in the stream can overlap in time. The previous sorting by
> timestamp causes packets to be read out of decode order and results
> in decode errors.
>
>
On 10/23/2017 01:47 AM, Mark Thompson wrote:
so let's make this work then and fix the SIGSEGV present in master asap (btw
this RFC also seg-fault when the above is applied)
Where does that version segfault? (It doesn't for me.)
the patch will segfault if the changes below are applied to the
On Fri, Sep 29, 2017 at 06:59:56PM -0300, James Almer wrote:
[...]
> Then IMO we should wait until the major bump (Which is not too far
> away). Leaving a stub object for the symbols and configure clutter
> should be avoided.
Patch applied.
Thanks
--
Clément B.
signature.asc
Description: PGP
2017-10-23 11:30 GMT+02:00 Michael Niedermayer :
> On Sun, Oct 22, 2017 at 01:15:27AM +0200, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> On redirection to https, FFmpeg only shows "protocol missing" without
>> a hint to what is missing.
>>
>> Please comment, Carl Eugen
>
>> avio.c |2 +-
>> 1 file ch
On Sun, Oct 22, 2017 at 01:15:27AM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> On redirection to https, FFmpeg only shows "protocol missing" without
> a hint to what is missing.
>
> Please comment, Carl Eugen
> avio.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> e7b346c9ce0c4f07004
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: Monday, October 23, 2017 4:53 PM
> To: FFmpeg development discussions and patches
>
> Subject: Re: [FFmpeg-devel] [PATCH V3 2/2] hwaccel_mpeg: check reference
> pictur
W dniu 2017-10-20 o 20:07, Jan Ekstrom pisze:
> On Fri, Oct 20, 2017 at 10:26 AM, Mateusz wrote:
>> W dniu 2017-10-06 o 17:33, Mateusz pisze:
>>> Fixed DITHER_COPY macro (only C code), updated FATE tests.
>>>
>>> PSNR in tests that needed update goes from 50 to 999.99 -- the quality is
>>> there.
2017-10-23 10:49 GMT+02:00 Li, Zhong :
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of Carl Eugen Hoyos
>> Sent: Friday, October 13, 2017 4:34 AM
>> To: FFmpeg development discussions and patches
>>
>> Subject: Re: [FFmpeg-devel] [PATCH
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: Friday, October 13, 2017 4:34 AM
> To: FFmpeg development discussions and patches
>
> Subject: Re: [FFmpeg-devel] [PATCH V3 2/2] hwaccel_mpeg: check reference
> pictur
On Mon, Oct 23, 2017 at 10:42:53AM +0200, Clément Bœsch wrote:
[...]
> how about changing the whole chunk with (untested):
>
> prog = av_strdup(my_program_name);
> dirname = av_dirname(prog);
> pathname = *dirname ? av_asprintf("%s/%s", dirname, "ffmpeg")
> : av
On Sun, Oct 22, 2017 at 05:11:20PM +0200, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> fftools/ffserver.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fftools/ffserver.c b/fftools/ffserver.c
> index d4885dfa0e..51f31bc704 100644
> --- a/
2017-10-21 13:36 GMT+02:00 Jan Ekstrom :
>
> This seems to have broken seeking and files ending. FLAC was
> experienced yesterday but it seems like it's more general. This was
> reported on the mpv users' channel by sfan5, but I feel like this
> might be more general than related to just mpv. At fi
On Sun, Oct 22, 2017 at 12:09:04PM -0400, Ronald S. Bultje wrote:
[...]
> > > The replacement will never be written if:
> > > a) nobody cares; AND
> > > b) we keep delaying the removal
> > >
> > > I'm considering veto'ing this patch.
> >
> > Personally I'm with Clement in this. The deprecation was
2017-10-23 5:22 GMT+02:00 James Almer :
> On 10/21/2017 9:31 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch silences the many warnings shown when decoding streams
>> with DolbyVision content.
>>
>> Please comment, Carl Eugen
>>
>>
>> 0001-lavc-hevcdec-Silence-warnings-when-decoding-DolbyVi
On Mon, Oct 23, 2017 at 5:22 AM, James Almer wrote:
> On 10/21/2017 9:31 PM, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> Attached patch silences the many warnings shown when decoding streams
>> with DolbyVision content.
>>
>> Please comment, Carl Eugen
>>
>>
>> 0001-lavc-hevcdec-Silence-warnings-when-dec
Though this patch to fix ticket #6668, I belive it
is unnecessary to set SLICE_FLAG_ALLOW_FIELD flag to other
hwaccels(dxva, vdpau, etc). Please also refer the orginal comment
of 9cb150c9ab520eba5636bbcf925db6a70e67f3e5
Signed-off-by: Zhong Li
---
libavcodec/mpeg12dec.c | 3 +--
1 file changed,
some reference pictures are not existed but valid surface_ids are set,
(for example, the second field of the first key frame can be
P_Picture_Type but there is no preivous frame.)
then may cause some driver problems (e.g, segment fault on mesa/AMD driver).
Signed-off-by: Zhong Li
---
libavcodec
Signed-off-by: Zhong Li
---
tests/fate/video.mak| 3 +++
tests/ref/fate/mpeg2-ticket6677 | 12
2 files changed, 15 insertions(+)
create mode 100644 tests/ref/fate/mpeg2-ticket6677
diff --git a/tests/fate/video.mak b/tests/fate/video.mak
index 6f76365165..51678078a3 100
59 matches
Mail list logo
