Please find attached a patch for setting key frames.
"-force_key_frames" can then use this option.
Thanks,
Yogender
---
This email message is for the sole use of the intended recipient(s) and may
contain
confidentia
> On 17 Jan 2018, at 11:00, Colin NG wrote:
>
> - Add function 'resolve_content_path' to propagate the baseURL from upper
> level nodes.
> * if no baseURL is available, the path of mpd file will be set as the baseURL.
> - Remove checking for newly established connection.
> - Establish the commu
---
libavformat/dashdec.c | 88 +--
1 file changed, 58 insertions(+), 30 deletions(-)
diff --git a/libavformat/dashdec.c b/libavformat/dashdec.c
index 1d520d4..9d5986d 100644
--- a/libavformat/dashdec.c
+++ b/libavformat/dashdec.c
@@ -147,6 +147,7 @
- Add function 'resolve_content_path' to propagate the baseURL from upper level
nodes.
* if no baseURL is available, the path of mpd file will be set as the baseURL.
- Remove checking for newly established connection.
- Establish the communication protocol in each connection rather than applying
---
libavformat/dashdec.c | 36 ++--
1 file changed, 30 insertions(+), 6 deletions(-)
diff --git a/libavformat/dashdec.c b/libavformat/dashdec.c
index 2492f1d..67a92d6 100644
--- a/libavformat/dashdec.c
+++ b/libavformat/dashdec.c
@@ -550,6 +550,23 @@ static enum A
From df08f000b58a362dadb412bdf55a36f1c8f1c82b Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Mon, 8 Jan 2018 16:07:38 +0800
Subject: [PATCH V2 3/5] lavfi: use common VPP infrastructure for
vf_deinterlace_vaapi.
Use the common VPP infrastructure re-work vf_deinterlace_vaapi.
Signed-off-by: Jun Z
From 415c5da45adfb09b7f083e0d912be7033bd44876 Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Mon, 8 Jan 2018 16:02:35 +0800
Subject: [PATCH V2 2/5] lavfi: use common VPP infrastructure for
vf_scale_vaapi.
Use the common VPP infrastructure re-work vf_scale_vaapi.
Signed-off-by: Jun Zhao
---
li
From 0a7f0aa4a108faad5ed84c285d5431ca6c9d9fdd Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Mon, 8 Jan 2018 16:19:17 +0800
Subject: [PATCH V2 5/5] lavfi: add misc(denoise/sharpness) VPP video filter.
add misc(denoise/sharpness) VPP video filter.
Signed-off-by: Yun Zhou
Signed-off-by: Jun Zha
From 5749acdcc5a7607221c29473d52a674922c7e8e0 Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Mon, 8 Jan 2018 16:12:41 +0800
Subject: [PATCH V2 4/5] lavfi: add ProcAmp(color balance) vaapi video filter.
add ProcAmp(color balance) vaapi video filter, use the option
like -vf "procamp_vaapi=b=10:h=12
V2: - Fix the resource leak in procamp/misc VPP filter.
- Re-work the common VAAPIVPPContext and specific VPP context part
like VAAPIVPPContext+ScaleVAAPIContext, borrowing the idea from
vaapi_encode.
- misc vpp part need to refactoring, and I don't have good idea
about the file name for vf
> On 17 Jan 2018, at 06:52, Colin NG wrote:
>
> O. I forgot to include on other patches the ticket 6856 fix depended on.
did you have try that patch, can that patch fix the 6856?
>
>
> Colin
>
>
> PS: the depended patches are
>
> 0001-libavformat-dashdec-Fix-for-ticket-6658-Dash-demuxer.pat
On Tue, Jan 16, 2018 at 05:52:52PM +0530, Gyan Doshi wrote:
>
>
> On 1/16/2018 5:19 PM, Michael Niedermayer wrote:
> >On Thu, Jan 11, 2018 at 12:15:00PM +0530, Gyan Doshi wrote:
> >>
> >>On 1/11/2018 6:16 AM, Michael Niedermayer wrote:
> >>
> >>Georg, do you want to maintain vf_vidstabtra
On Mon, Jan 15, 2018 at 08:08:33PM -0200, Pedro Arthur wrote:
> Added an entry in the ideas page for the super resolution project. I'd like
> to know if any one could be co-mentor with me? just in case my studies
> conflicts with mentoring as gsoc overlaps with half of my phd period.
If noone else
From af8982bddc1e5b430ba12fc155676ee71f598c0a Mon Sep 17 00:00:00 2001
From: Jun Zhao
Date: Tue, 16 Jan 2018 22:44:02 +0800
Subject: [PATCH] lavfi/deinterlace_vaapi: fix can't show full option
information.
use ffmpeg -h filter=deinterlace_vaapi can't get full help information,
the root cause is
O. I forgot to include on other patches the ticket 6856 fix depended on.
Colin
PS: the depended patches are
0001-libavformat-dashdec-Fix-for-ticket-6658-Dash-demuxer.patch
0001-Download-dash-content-with-byte-range-info.patch (not necessary for
compilation but needed for the complete solutio
2018-01-16 23:00 GMT+01:00 James Darnley :
> On 2018-01-16 22:26, Martin Vignali wrote:
> > diff --git a/libavutil/x86/x86util.asm b/libavutil/x86/x86util.asm
> > index d7cd996842..9db2d90e57 100644
> > --- a/libavutil/x86/x86util.asm
> > +++ b/libavutil/x86/x86util.asm
> > @@ -335,7 +335,7 @@
> >
2018-01-16 19:40 GMT+01:00 Bjorn Roche :
> I'm just reviewing this and noticing that the patch is stale
> and no longer compiles. I am happy to update, but is
> there someone to review it if I do so?
This is Clément's code, he has to review your patch.
In any case, please update the patch.
Sorr
On 2018-01-16 22:26, Martin Vignali wrote:
> diff --git a/libavutil/x86/x86util.asm b/libavutil/x86/x86util.asm
> index d7cd996842..9db2d90e57 100644
> --- a/libavutil/x86/x86util.asm
> +++ b/libavutil/x86/x86util.asm
> @@ -335,7 +335,7 @@
> %endmacro
>
> %macro ABS2 4
> -%if cpuflag(ssse3)
> +
Hello,
following Henrik Gramner comments (in discussion "avfilter/x86/vf_blend :
add avx2 version for 8b func (WIP)")
in attach new patch to add AVX2 version for each 8b func (except divide)
001 : avutil : add ABS2 for avx2
002 : avfilter : add AVX2 version
for most of the func, the AVX2 is a si
Hey all,
I'm just reviewing this and noticing that the patch is stale and no longer
compiles. I am happy to update, but is there someone to review it if I do
so? I'd love to get this patch in. Thanks,
bjorn
On Thu, Dec 7, 2017 at 5:56 PM, Bjorn Roche wrote:
> Hey all,
>
> Just wondering what
On Tue, 16 Jan 2018 17:47:14 +0100
Steve Lhomme wrote:
> Le 16/01/2018 à 17:42, wm4 a écrit :
> > On Tue, 16 Jan 2018 14:08:37 +0100
> > wm4 wrote:
> >
> >> D3D11 has rather fine grained per texture format capabilities for
> >> different uses that can be queried at runtime. Since we don't know
Le 16/01/2018 à 17:42, wm4 a écrit :
On Tue, 16 Jan 2018 14:08:37 +0100
wm4 wrote:
D3D11 has rather fine grained per texture format capabilities for
different uses that can be queried at runtime. Since we don't know at
the time av_hwdevice_get_hwframe_constraints() is called what the user
want
On Tue, 16 Jan 2018 14:08:37 +0100
wm4 wrote:
> D3D11 has rather fine grained per texture format capabilities for
> different uses that can be queried at runtime. Since we don't know at
> the time av_hwdevice_get_hwframe_constraints() is called what the user
> wants to do with this, we simply ret
D3D11 has rather fine grained per texture format capabilities for
different uses that can be queried at runtime. Since we don't know at
the time av_hwdevice_get_hwframe_constraints() is called what the user
wants to do with this, we simply return all formats that have the most
basic support.
---
l
On Tue, Jan 16, 2018 at 10:46:54AM +0800, Jun Zhao wrote:
>
> snow_dwt.h |2 ++
> 1 file changed, 2 insertions(+)
> 189c300f91a062974bb658acbf56d1169f9aa2bc
> 0001-lavc-snow_dwt-add-struct-MpegEncContext-to-fix-heade.patch
> From 998717188707f5bda66267202c492328092e3831 Mon Sep 17 00:00:00
On 1/16/2018 5:19 PM, Michael Niedermayer wrote:
On Thu, Jan 11, 2018 at 12:15:00PM +0530, Gyan Doshi wrote:
On 1/11/2018 6:16 AM, Michael Niedermayer wrote:
Georg, do you want to maintain vf_vidstabtransform.c ?
If not, who wants to maintain vf_vidstabtransform.c ?
If noone then iam not
On Thu, 4 Jan 2018 17:02:41 +0100
wm4 wrote:
> It was sort of optional before - if you didn't call it, networking was
> initialized on demand, and an ugly warning was logged. Also, the doxygen
> comments threatened that it would be made strictly required one day.
>
> Make it explicitly optional
On Mon, 15 Jan 2018 11:29:20 -0300
James Almer wrote:
> On 1/15/2018 9:11 AM, wm4 wrote:
> > ---
> > doc/APIchanges | 4
> > libavformat/avformat.h | 2 ++
> > libavformat/utils.c| 8
> > libavformat/version.h | 5 -
> > 4 files changed, 18 insertions(+), 1 deletio
On Thu, Jan 11, 2018 at 12:15:00PM +0530, Gyan Doshi wrote:
>
> On 1/11/2018 6:16 AM, Michael Niedermayer wrote:
>
> Georg, do you want to maintain vf_vidstabtransform.c ?
>
> If not, who wants to maintain vf_vidstabtransform.c ?
>
> If noone then iam not sure who will t
29 matches
Mail list logo
