Re: [FFmpeg-devel] [PATCH] lavf/os_support: Add safe win32 dlopen/dlclose/dlsym functions.

On 31 October 2016 at 05:30, James Almer wrote: > On 10/30/2016 8:31 AM, Matt Oliver wrote: > > From 1dc1f59158cfb12d9160ee47342f5742d67ad864 Mon Sep 17 00:00:00 2001 > > From: Matt Oliver > > Date: Sun, 30 Oct 2016 15:13:47 +1100 > > Subject: [PATCH]

Re: [FFmpeg-devel] [PATCH] news: add final report for summer of code 2016

Thanks for the comments and corrections. Fixed the typos and pushed as: commit f06598a8e1fcccef8c38a657162db309773d1515 Author: Reynaldo H. Verdejo Pinochet Date: Sun Oct 30 01:37:26 2016 -0700 news: add final report for summer of code 2016 Bests, -- Reynaldo

Re: [FFmpeg-devel] [PATCH] news: add final report for summer of code 2016

On Sun, Oct 30, 2016 at 01:57:58AM -0700, reyna...@osg.samsung.com wrote: > From: "Reynaldo H. Verdejo Pinochet" > > Signed-off-by: Reynaldo H. Verdejo Pinochet > --- > src/index | 34 ++ > 1 file changed, 34

Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer

On 10/30/2016 8:23 PM, Lukasz Marek wrote: > On 27.10.2016 20:26, Michael Niedermayer wrote: >> On Thu, Oct 27, 2016 at 11:03:07AM -0700, Reynaldo H. Verdejo Pinochet wrote: >> I agree with moving the apps to a seperate repo hosted within >> the same infra and keeping ffserver. >> I will help with

Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer

On 27.10.2016 20:26, Michael Niedermayer wrote: On Thu, Oct 27, 2016 at 11:03:07AM -0700, Reynaldo H. Verdejo Pinochet wrote: I agree with moving the apps to a seperate repo hosted within the same infra and keeping ffserver. I will help with ffserver as my time & todo list permits I don't

Re: [FFmpeg-devel] [PATCH] interplayacm: check for too large b

On 30.10.2016 22:16, Paul B Mahol wrote: > On 10/30/16, Andreas Cadhalpun wrote: >> This fixes out-of-bounds reads. >> >> Signed-off-by: Andreas Cadhalpun >> --- >> libavcodec/interplayacm.c | 12 >> 1 file

Re: [FFmpeg-devel] [PATCH] interplayacm: validate number of channels

On 30.10.2016 22:15, Paul B Mahol wrote: > On 10/30/16, Andreas Cadhalpun wrote: >> The number of channels is used as divisor in decode_frame, so it must >> not be zero to avoid SIGFPE crashes. >> >> Signed-off-by: Andreas Cadhalpun

Re: [FFmpeg-devel] [PATCH] interplayacm: increase bitstream buffer size by AV_INPUT_BUFFER_PADDING_SIZE

On 30.10.2016 22:18, Paul B Mahol wrote: > On 10/30/16, Andreas Cadhalpun wrote: >> This fixes out-of-bounds reads by the bitstream reader. >> >> Signed-off-by: Andreas Cadhalpun >> --- >> libavcodec/interplayacm.c | 2 +- >> 1

Re: [FFmpeg-devel] [PATCH] interplayacm: increase bitstream buffer size by AV_INPUT_BUFFER_PADDING_SIZE

On 10/30/16, Andreas Cadhalpun wrote: > This fixes out-of-bounds reads by the bitstream reader. > > Signed-off-by: Andreas Cadhalpun > --- > libavcodec/interplayacm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

Re: [FFmpeg-devel] [PATCH] interplayacm: check for too large b

On 10/30/16, Andreas Cadhalpun wrote: > This fixes out-of-bounds reads. > > Signed-off-by: Andreas Cadhalpun > --- > libavcodec/interplayacm.c | 12 > 1 file changed, 12 insertions(+) > > diff --git

Re: [FFmpeg-devel] [PATCH] interplayacm: validate number of channels

On 10/30/16, Andreas Cadhalpun wrote: > The number of channels is used as divisor in decode_frame, so it must > not be zero to avoid SIGFPE crashes. > > Signed-off-by: Andreas Cadhalpun > --- > libavcodec/interplayacm.c | 5

[FFmpeg-devel] [PATCH] interplayacm: validate number of channels

The number of channels is used as divisor in decode_frame, so it must not be zero to avoid SIGFPE crashes. Signed-off-by: Andreas Cadhalpun --- libavcodec/interplayacm.c | 5 + 1 file changed, 5 insertions(+) diff --git a/libavcodec/interplayacm.c

[FFmpeg-devel] [PATCH] interplayacm: increase bitstream buffer size by AV_INPUT_BUFFER_PADDING_SIZE

This fixes out-of-bounds reads by the bitstream reader. Signed-off-by: Andreas Cadhalpun --- libavcodec/interplayacm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/interplayacm.c b/libavcodec/interplayacm.c index

[FFmpeg-devel] [PATCH] interplayacm: check for too large b

This fixes out-of-bounds reads. Signed-off-by: Andreas Cadhalpun --- libavcodec/interplayacm.c | 12 1 file changed, 12 insertions(+) diff --git a/libavcodec/interplayacm.c b/libavcodec/interplayacm.c index 0fd3501..0486e00 100644 ---

[FFmpeg-devel] [PATCH] mov: only read e_old if there were any old streams

This fixes a heap buffer overflow. Signed-off-by: Andreas Cadhalpun --- libavformat/mov.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavformat/mov.c b/libavformat/mov.c index 357d800..95b546e 100644 --- a/libavformat/mov.c +++

Re: [FFmpeg-devel] [PATCH 3/3] vf_colorspace: Add support for smpte 431/432 (dci/display p3) primaries

Hi Kieran, On Sun, Oct 30, 2016 at 10:06 AM, Kieran O Leary wrote: > Hi, > > On Sun, Oct 30, 2016 at 7:07 AM, Vittorio Giovara < > vittorio.giov...@gmail.com> wrote: > > > Signed-off-by: Vittorio Giovara > > --- > > I couldn't find any

[FFmpeg-devel] [PATCH v2] avformat/tee: Add FATE tests for tee

From: Jan Sebechlebsky This commit also adds new diff option for fate tests allowing do compare multiple tuples of files. Signed-off-by: Jan Sebechlebsky --- Changes since the last version: - fixed out of tree build (previous version

Re: [FFmpeg-devel] [PATCH v2] libavformat/tee: Add fifo support for tee

On 10/17/2016 01:13 PM, sebechlebsky...@gmail.com wrote: From: Jan Sebechlebsky Signed-off-by: Jan Sebechlebsky --- Thanks for noticing, I've fixed the patch (also some minor formatting issues I've noticed). doc/muxers.texi | 20

Re: [FFmpeg-devel] [PATCH v3] ffmpeg: parameters for filter thread counts

On 10/30/2016 12:09 PM, Paul B Mahol wrote: > On 10/30/16, DeHackEd wrote: >> Enables specifying how many threads are available to each filtergraph. >> --- >> v2->v3: >> - Typos in docs fixed >> >> v1->v2: >> - Reworded documentation >> - Removed hunk from ffmpeg_filter.c not

Re: [FFmpeg-devel] [PATCH] lavf/os_support: Add safe win32 dlopen/dlclose/dlsym functions.

On 10/30/2016 8:31 AM, Matt Oliver wrote: > From 1dc1f59158cfb12d9160ee47342f5742d67ad864 Mon Sep 17 00:00:00 2001 > From: Matt Oliver > Date: Sun, 30 Oct 2016 15:13:47 +1100 > Subject: [PATCH] avformat/avisynth.c: Use new safe dlopen code. > > --- > configure

Re: [FFmpeg-devel] [PATCH] lavf/os_support: Add safe win32 dlopen/dlclose/dlsym functions.

On Sun, Oct 30, 2016 at 10:31:16PM +1100, Matt Oliver wrote: > On 30 October 2016 at 20:21, Hendrik Leppkes wrote: > > > On Sun, Oct 30, 2016 at 5:13 AM, Matt Oliver wrote: > > > On 30 October 2016 at 03:41, Stephen Hutchinson > >

Re: [FFmpeg-devel] [PATCH]lavfi/mergeplanes: Fix little endian formats >8 bit.

On 10/30/16, Carl Eugen Hoyos wrote: > > >> Am 30.10.2016 um 00:55 schrieb Paul B Mahol : >> >>> On 10/30/16, Carl Eugen Hoyos wrote: >>> Hi! >>> >>> Attached patch fixes ticket #5916 for (for example) yuv444p9le. >> >> Same as for another

Re: [FFmpeg-devel] [PATCH v3] ffmpeg: parameters for filter thread counts

On 10/30/16, DeHackEd wrote: > Enables specifying how many threads are available to each filtergraph. > --- > v2->v3: > - Typos in docs fixed > > v1->v2: > - Reworded documentation > - Removed hunk from ffmpeg_filter.c not directly applicable to patch > > doc/ffmpeg.texi | 10

Re: [FFmpeg-devel] [PATCH] avformat/utils: only call h264 decoder private function if h264 decoder is in use

On Sun, Oct 30, 2016 at 12:04:14PM +0100, Timo Rothenpieler wrote: > > has the issue been fixed for all branches an cases or is something > > missing that needs this ? > > (if so this needs a null pointer check i think) > > This was fixed in a diffrent way in

Re: [FFmpeg-devel] [PATCH] add hds demuxer

2016-10-24 16:27 GMT+08:00 Steven Liu : > > > 2016-10-24 15:22 GMT+08:00 wm4 : > >> On Sat, 15 Oct 2016 15:52:48 +0200 >> Nicolas George wrote: >> >> > Le tridi 23 vendémiaire, an CCXXV, wm4 a écrit : >> > > XML is very complex

Re: [FFmpeg-devel] [PATCH] news: add final report for summer of code 2016

On Sun, Oct 30, 2016 at 01:57:58 -0700, reyna...@osg.samsung.com wrote: > +Without further ado, here's the silver-lining for each one of the > projects we sought to complete during this Summer of Code season: > + > + FFv1 (Mentor: Michael Nierdermayer) ^

Re: [FFmpeg-devel] [PATCH 3/3] vf_colorspace: Add support for smpte 431/432 (dci/display p3) primaries

Hi, On Sun, Oct 30, 2016 at 7:07 AM, Vittorio Giovara < vittorio.giov...@gmail.com> wrote: > Signed-off-by: Vittorio Giovara > --- > I couldn't find any reference to the name of the whitepoint used for 431, > so I came up with DCI, since it looks like it is only used

Re: [FFmpeg-devel] [PATCH]lavfi/mergeplanes: Fix little endian formats >8 bit.

> Am 30.10.2016 um 00:55 schrieb Paul B Mahol : > >> On 10/30/16, Carl Eugen Hoyos wrote: >> Hi! >> >> Attached patch fixes ticket #5916 for (for example) yuv444p9le. > > Same as for another mergeplanes patch from you, please explain why > this is correct.

Re: [FFmpeg-devel] [PATCH]lavfi/mergeplanes: Fix >8bit formats

> Am 30.10.2016 um 00:53 schrieb Paul B Mahol : > >> On 10/30/16, Carl Eugen Hoyos wrote: >> Hi! >> >> Attached patch fixes the command line provided in ticket #5916. > > Can you explain why this patch is correct way to fix bug? I don't know if the patch

Re: [FFmpeg-devel] [PATCH 2/3] vf_colorspace: Add support for ycgco color space

Hi, On Sun, Oct 30, 2016 at 3:07 AM, Vittorio Giovara < vittorio.giov...@gmail.com> wrote: > Signed-off-by: Vittorio Giovara > --- > This is a little hackish, not sure how to represent the matrix otherwise. Haha :) I have to admit I hadn't put much thought into

[FFmpeg-devel] [PATCH v3] ffmpeg: parameters for filter thread counts

Enables specifying how many threads are available to each filtergraph. --- v2->v3: - Typos in docs fixed v1->v2: - Reworded documentation - Removed hunk from ffmpeg_filter.c not directly applicable to patch doc/ffmpeg.texi | 10 ++ ffmpeg.h| 3 +++ ffmpeg_filter.c | 7 +++

Re: [FFmpeg-devel] [PATCH] openssl: Allow newer TLS versions than TLSv1

On 29/10/16 22:57, Michael Niedermayer wrote: > On Sat, Oct 29, 2016 at 09:53:30AM +0100, Mark Thompson wrote: >> The use of TLSv1_*_method() disallows newer protocol versions; instead >> use SSLv23_*_method() and then explicitly disable the deprecated >> protocol versions which should not be

Re: [FFmpeg-devel] [PATCH 3/3] vf_colorspace: Add support for smpte 431/432 (dci/display p3) primaries

Hi, On Sun, Oct 30, 2016 at 3:07 AM, Vittorio Giovara < vittorio.giov...@gmail.com> wrote: > Signed-off-by: Vittorio Giovara > --- > I couldn't find any reference to the name of the whitepoint used for 431, > so I came up with DCI, since it looks like it is only used

Re: [FFmpeg-devel] [PATCH 1/3] vf_colorspace: Add support for iec61966-2.4 (xvYCC) transfer

Hi, On Sun, Oct 30, 2016 at 3:07 AM, Vittorio Giovara < vittorio.giov...@gmail.com> wrote: > Signed-off-by: Vittorio Giovara > --- > As described in http://www.color.org/chardata/rgb/xvycc.xalter > Please CC. > Vittorio > > libavfilter/vf_colorspace.c | 3 +++ > 1

Re: [FFmpeg-devel] [PATCH] news: add final report for summer of code 2016

On 10/30/16, reyna...@osg.samsung.com wrote: > From: "Reynaldo H. Verdejo Pinochet" > > Signed-off-by: Reynaldo H. Verdejo Pinochet > --- > src/index | 34 ++ > 1 file changed, 34

Re: [FFmpeg-devel] [PATCH] lavf/os_support: Add safe win32 dlopen/dlclose/dlsym functions.

On 30 October 2016 at 20:21, Hendrik Leppkes wrote: > On Sun, Oct 30, 2016 at 5:13 AM, Matt Oliver wrote: > > On 30 October 2016 at 03:41, Stephen Hutchinson > wrote: > > > >> On 10/29/2016 11:22 AM, Michael Niedermayer wrote: > >> >

Re: [FFmpeg-devel] [PATCH] avformat/utils: only call h264 decoder private function if h264 decoder is in use

> has the issue been fixed for all branches an cases or is something > missing that needs this ? > (if so this needs a null pointer check i think) This was fixed in a diffrent way in 6d9a46e884d090a68069112a3b0436aa8b563967 It forces the h264 decoder to be used, so the assumption it is in use is

Re: [FFmpeg-devel] [PATCH] lavf/os_support: Add safe win32 dlopen/dlclose/dlsym functions.

On Sun, Oct 30, 2016 at 5:13 AM, Matt Oliver wrote: > On 30 October 2016 at 03:41, Stephen Hutchinson wrote: > >> On 10/29/2016 11:22 AM, Michael Niedermayer wrote: >> >>> On Sat, Oct 29, 2016 at 06:35:19PM +1100, Matt Oliver wrote: >>> configure

Re: [FFmpeg-devel] [PATCH]lavfi/mergeplanes: Fix little endian formats >8 bit.

On 10/30/16, Carl Eugen Hoyos wrote: > Hi! > > Attached patch fixes ticket #5916 for (for example) yuv444p9le. > > Please comment, Carl Eugen Same as for another mergeplanes patch from you, please explain why this is correct. Are patches dependend on each other?

Re: [FFmpeg-devel] [PATCH]lavfi/mergeplanes: Fix >8bit formats

On 10/30/16, Carl Eugen Hoyos wrote: > Hi! > > Attached patch fixes the command line provided in ticket #5916. > > Please comment, Carl Eugen Can you explain why this patch is correct way to fix bug? ___ ffmpeg-devel mailing list

[FFmpeg-devel] [PATCH 2/3] vf_colorspace: Add support for ycgco color space

Signed-off-by: Vittorio Giovara --- This is a little hackish, not sure how to represent the matrix otherwise. Please CC. Vittorio libavfilter/vf_colorspace.c | 15 +++ 1 file changed, 15 insertions(+) diff --git a/libavfilter/vf_colorspace.c

[FFmpeg-devel] [PATCH 3/3] vf_colorspace: Add support for smpte 431/432 (dci/display p3) primaries

Signed-off-by: Vittorio Giovara --- I couldn't find any reference to the name of the whitepoint used for 431, so I came up with DCI, since it looks like it is only used there. Please CC. Vittorio libavfilter/vf_colorspace.c | 6 ++ 1 file changed, 6 insertions(+)

[FFmpeg-devel] [PATCH 1/3] vf_colorspace: Add support for iec61966-2.4 (xvYCC) transfer

Signed-off-by: Vittorio Giovara --- As described in http://www.color.org/chardata/rgb/xvycc.xalter Please CC. Vittorio libavfilter/vf_colorspace.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libavfilter/vf_colorspace.c b/libavfilter/vf_colorspace.c index

Re: [FFmpeg-devel] [PATCH] Fix build with LibreSSL

On 10/29/16, Matt Oliver wrote: > This also seems a bit odd, why is libreSSL setting an openssl version > number of 1.1.0 or higher when it doesnt actually conform to the > corresponding openssl version. LibreSSl setting the openssl version number > to 2.0.0 seems to be