> On 13 Dec 2017, at 15:31, Nablet Developer wrote:
>
> The protocol is used by thousands of Haivision customers since 2013,
> in extremely sensitive medical, military and enterprise applications
> with FIPS compliant encryption requirements. Since April 2017, the protocol
> is Open Source and
On 12/19/17 9:23 AM, 刘歧 wrote:
On 18 Dec 2017, at 20:52, vdi...@akamai.com wrote:
From: Vishwanath Dixit
---
doc/muxers.texi | 12 +
libavformat/dashenc.c | 3 ++-
libavformat/hlsenc.c | 62 ---
libavformat/hlsplaylist.c |
> On 19 Dec 2017, at 14:58, Karthick J wrote:
>
> From: Karthick Jeyapal
>
> ---
> libavformat/hlsenc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
> index e3442c3..5ee28ea 100644
> --- a/libavformat/hlsenc.c
> +++ b/libavformat/hlsenc
On Fri, Dec 15, 2017 at 09:16:02AM -0600, Matt Zagrabelny wrote:
> On Thu, Dec 14, 2017 at 8:06 PM, Carl Eugen Hoyos
> wrote:
>
> >
> > You could implement a hack (similar to what the CC code does)
> > that allows processing the subs but it is likely that the patch
> > would be rejected because a
Hi,
On Mon, Dec 18, 2017 at 11:55 PM, James Almer wrote:
> On 12/8/2017 10:35 PM, Ronald S. Bultje wrote:
> > Fixes trac issue #6884 and Netflix/vmaf issue #124.
> > ---
> > libavfilter/vf_libvmaf.c | 28 ++--
> > 1 file changed, 22 insertions(+), 6 deletions(-)
> >
> >
Hi,
Attached patch fixes an issue with the LibreSSL pkg-config check in
configure.
Between the creation of my libtls patchset and the date it was pushed, a
refactor had changed all invocations of use_pkg_config to
require_pkg_config, resulting in pkg-config never working.
From 0afe7b4257f55cc
Last patch had a minor issue, fixed version attached.
From 6f6bcf77ce2aaf6a84858d34112f61128e779fda Mon Sep 17 00:00:00 2001
From: sfan5
Date: Tue, 19 Dec 2017 17:33:26 +0100
Subject: [PATCH] configure: fix pkg-config check for libtls
This was not accounted for during merge and is required due to
On 12/19/2017 2:13 PM, Stefan _ wrote:
> Last patch had a minor issue, fixed version attached.
Applied.
The fallback check for that matter should be removed. It's pointless
since every supported version of the library ships a .pc file, and it's
pretty much guaranteed to not work with static build
On 19.12.2017 at 18:28 James Almer wrote:
> On 12/19/2017 2:13 PM, Stefan _ wrote:
>> Last patch had a minor issue, fixed version attached.
> Applied.
Thanks.
>
> The fallback check for that matter should be removed. It's pointless
> since every supported version of the library ships a .pc file, an
On 07.12.2017 at 20:56 Stefan _ wrote:
> On 07.12.2017 at 17:41 Michael Niedermayer wrote:
>> The move and the functional change should be in seperate patches
>> that keeps changes easy to read and understand
>>
>> [...]
bump
(Previous patch in same series was merged. This one wasn't and hasn't
On 12/19/2017 2:51 PM, Stefan _ wrote:
> On 19.12.2017 at 18:28 James Almer wrote:
>> On 12/19/2017 2:13 PM, Stefan _ wrote:
>>> Last patch had a minor issue, fixed version attached.
>> Applied.
> Thanks.
>>
>> The fallback check for that matter should be removed. It's pointless
>> since every supp
Hi,
Yeah, got mine too! Arrived safely in the USA. Thanks Thilo!
Kyle
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Tue, Dec 19, 2017 at 11:39:24AM +0530, vdi...@akamai.com wrote:
> From: Vishwanath Dixit
>
> ---
> libavcodec/libx264.c | 20 +++-
> 1 file changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
> index e2455e1..0285213 100644
>
Hello Michael,
could you take a look at the patch?
Felix
> Am 30.11.2017 um 18:15 schrieb Michael Niedermayer :
>
> On Thu, Nov 30, 2017 at 10:15:48AM +0100, Felix Matouschek wrote:
>> Sorry, my mail client swallowed the attachment, sent it again.
>>
>
>> Changelog|1
Any chance this could get merged?
> Am 12.12.2017 um 15:53 schrieb Felix Matouschek :
>
> Am 12.12.2017 15:37, schrieb James Almer:
>> No, this is not correct. If anything has to be added here, it would be
>> $libm_extralibs. -lm is not needed/available on some systems.
>
> Ok, changed it.
>
>>
On Mon, Dec 18, 2017 at 09:41:00AM +0800, Jun Zhao wrote:
>
> audiomatch.c |6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
> f7cd009b9c616d48223793eeab8d135329a23f69
> 0001-tests-audiomatch-Add-return-value-check-for-fread.patch
> From a89964e88080d1cc6e01c99bf8640a1020465762
On Mon, Dec 18, 2017 at 09:41:08AM +0800, Jun Zhao wrote:
>
> audiomatch.c | 34 +-
> 1 file changed, 17 insertions(+), 17 deletions(-)
> 731bb5fb6d343903e65d5f1336b6393527bfa780
> 0002-tests-audiomatch-Refine-the-code.patch
> From d2e3ba49180883dc71eb0eb0f5fa
On 12/12/2017 11:53 AM, Felix Matouschek wrote:
> Am 12.12.2017 15:37, schrieb James Almer:
>> No, this is not correct. If anything has to be added here, it would be
>> $libm_extralibs. -lm is not needed/available on some systems.
>
> Ok, changed it.
>
>> Also, you should be using pkg-config. Its
Pushed, using vpermq (faster for me)
and add "%if HAVE_AVX2_EXTERNAL" around INIT YMM...
Thanks
Martin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Am 19.12.2017 um 21:19 schrieb James Almer :
>
> Pushed.
>
> Wouldn't this need to be done for vp8 as well, for that matter?
>
At least on Android using libvpx 1.6.1 it was not needed for vp8, only for vp9.
___
ffmpeg-devel mailing list
ffmpeg-devel@f
>
> LGTM, thanks.
>
Pushed, thanks
Do you think, that the complex low pass filter could also be improved that
> way?
>
>
>
Yes, probably. I will take a look.
Martin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listin
On 12/19/2017 5:16 PM, Martin Vignali wrote:
>>
>> LGTM, thanks.
>>
>
> Pushed, thanks
This broke several interlace fate tests, including the new checkasm one
you added.
http://fate.ffmpeg.org/report.cgi?time=20171219201300&slot=x86_64-archlinux-gcc-threads-2
2017-12-19 21:59 GMT+01:00 James Almer :
> On 12/19/2017 5:16 PM, Martin Vignali wrote:
> >>
> >> LGTM, thanks.
> >>
> >
> > Pushed, thanks
>
> This broke several interlace fate tests, including the new checkasm one
> you added.
>
> Sorry forget to run fate after AVX2 patch (only test with checkas
On 12/19/2017 6:40 PM, Martin Vignali wrote:
> 2017-12-19 21:59 GMT+01:00 James Almer :
>
>> On 12/19/2017 5:16 PM, Martin Vignali wrote:
LGTM, thanks.
>>>
>>> Pushed, thanks
>>
>> This broke several interlace fate tests, including the new checkasm one
>> you added.
>>
>> Sorry forg
> You pretty much did. Side data is an ffmpeg internal concept, and if
> your hypothetical streaming protocol needs special support for side
> data, it's automatically relying on ffmpeg internals.
I thought side data was public data? Doesn't it contain public info
like display info and required d
2017-12-19 22:57 GMT+01:00 James Almer :
> On 12/19/2017 6:40 PM, Martin Vignali wrote:
> > 2017-12-19 21:59 GMT+01:00 James Almer :
> >
> >> On 12/19/2017 5:16 PM, Martin Vignali wrote:
>
> LGTM, thanks.
>
> >>>
> >>> Pushed, thanks
> >>
> >> This broke several interlace fate tests
On 11/28/2017 3:57 PM, Vittorio Giovara wrote:
> Signed-off-by: Vittorio Giovara
> ---
> This version should be more complete.
> Regarding configure changes, this library is not packaged by any distribution
> that I could find, so users will just need to use zimg HEAD or any stable
> snapshot (2.6
On Tue, 19 Dec 2017 14:20:38 -0800
Jacob Trimble wrote:
> > You pretty much did. Side data is an ffmpeg internal concept, and if
> > your hypothetical streaming protocol needs special support for side
> > data, it's automatically relying on ffmpeg internals.
>
> I thought side data was public
On 19/12/17 06:25, Jun Zhao wrote:
> From 8400fa85b7af47c3cff6abd87fdc392ac7891e35 Mon Sep 17 00:00:00 2001
> From: Jun Zhao
> Date: Tue, 19 Dec 2017 14:13:58 +0800
> Subject: [PATCH] lavc/vaapi_encode: give a debug message if attrs unsupported.
>
> Give a debug message when query attribute get V
2017-12-19 18:28 GMT+01:00 James Almer :
> On 12/19/2017 2:13 PM, Stefan _ wrote:
>> Last patch had a minor issue, fixed version attached.
>
> Applied.
>
> The fallback check for that matter should be removed. It's pointless
> since every supported version of the library ships a .pc file
Which is
On 12/19/2017 8:32 PM, Carl Eugen Hoyos wrote:
> 2017-12-19 18:28 GMT+01:00 James Almer :
>> On 12/19/2017 2:13 PM, Stefan _ wrote:
>>> Last patch had a minor issue, fixed version attached.
>>
>> Applied.
>>
>> The fallback check for that matter should be removed. It's pointless
>> since every supp
On Wed, Dec 20, 2017 at 12:32 AM, Carl Eugen Hoyos wrote:
> 2017-12-19 18:28 GMT+01:00 James Almer :
>> On 12/19/2017 2:13 PM, Stefan _ wrote:
>>> Last patch had a minor issue, fixed version attached.
>>
>> Applied.
>>
>> The fallback check for that matter should be removed. It's pointless
>> sinc
2017-12-20 0:49 GMT+01:00 James Almer :
> On 12/19/2017 8:32 PM, Carl Eugen Hoyos wrote:
>> 2017-12-19 18:28 GMT+01:00 James Almer :
>>> On 12/19/2017 2:13 PM, Stefan _ wrote:
Last patch had a minor issue, fixed version attached.
>>>
>>> Applied.
>>>
>>> The fallback check for that matter shou
On 2017/12/20 7:11, Mark Thompson wrote:
> On 19/12/17 06:25, Jun Zhao wrote:
>> From 8400fa85b7af47c3cff6abd87fdc392ac7891e35 Mon Sep 17 00:00:00 2001
>> From: Jun Zhao
>> Date: Tue, 19 Dec 2017 14:13:58 +0800
>> Subject: [PATCH] lavc/vaapi_encode: give a debug message if attrs
>> unsupported.
On 12/16/2017 12:50 PM, Stefan Pöschel wrote:
> Fixes #6918.
> ---
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index d5bbb5b..20ca792 100755
> --- a/configure
> +++ b/configure
> @@ -5853,7 +5853,7 @@ enabled libkvazaar&& re
35 matches
Mail list logo
