Hi
Please find attached the patch, it enables ffnvcodec and nvenc, nvdec, cuvid
for PPC64 architecture.
PPC64 support requires Video Codec SDK 9.
Thanks
Ruta
---
This email message is for the sole use of the
Hi
Please find the attached patch, it rectifies the definition of cuda device
pointer for PPC64 architecture.
PPC64 support is present from Video Codec SDK 9.
Thanks
Ruta
---
This email message is for the sole use
I just searched my inbox again but failed to find that email of question you
mentioned.
Could you please elaborate your request? What is the preservation for and how
is it expected to work?
Regards,
SUN, Jing
From: Vittorio Giovara [mailto:vittorio.giov...@gmail.com]
Sent: Saturday, March 9,
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Carl
Eugen Hoyos
Sent: Saturday, March 9, 2019 5:07 AM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] [PATCH v7 1/2] lavc/svt_hevc: add libsvt hevc
encoder wrapper.
ping.
On Thu, Mar 7, 2019 at 11:55 AM Jun Li wrote:
> From: jun
>
> Calculate bitrate based on fragment size, only applied when
> bitrate is not set, for example rtsp source.
>
> Signed-off-by: Jun Li
> ---
> libavformat/smoothstreamingenc.c | 30 +-
> 1 file
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Guo, Yejun
> Sent: Tuesday, March 05, 2019 8:46 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 2/5] libx264: Update ROI behaviour
> 在 2019年3月11日，上午10:34，James Almer 写道：
>
> On 2/21/2019 4:16 AM, Steven Liu wrote:
>> Signed-off-by: Steven Liu
>> ---
>> libavformat/avformat.h | 7 +++
>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
>> index
Signed-off-by: Steven Liu
---
libavformat/avformat.h | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/libavformat/avformat.h b/libavformat/avformat.h
index fdaffa5bf4..3fec074373 100644
--- a/libavformat/avformat.h
+++ b/libavformat/avformat.h
@@ -36,17 +36,15 @@
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of myp...@gmail.com
> Sent: Monday, March 11, 2019 11:05 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Jun Zhao
> Subject: Re: [FFmpeg-devel] [PATCH V2]
On Mon, Mar 11, 2019 at 10:51 AM Guo, Yejun wrote:
>
>
>
> > -Original Message-
> > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> > Of Jun Zhao
> > Sent: Sunday, March 10, 2019 9:17 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Cc: Jun Zhao
> > Subject: [FFmpeg-devel]
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Jun Zhao
> Sent: Sunday, March 10, 2019 9:17 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Jun Zhao
> Subject: [FFmpeg-devel] [PATCH V2] lavfi/showinfo: support regions of
> interest sidedata
>
>
On 2/21/2019 4:16 AM, Steven Liu wrote:
> Signed-off-by: Steven Liu
> ---
> libavformat/avformat.h | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
> index fdaffa5bf4..12cc8387ed 100644
> --- a/libavformat/avformat.h
> 在 2019年2月21日，下午3:16，Steven Liu 写道：
>
> Signed-off-by: Steven Liu
> ---
> libavformat/avformat.h | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
> index fdaffa5bf4..12cc8387ed 100644
> ---
From: Mark Reid
This patch restores the ability to add user comments for the opatom_mxf muxer.
The ability seems to have been disabled in d9726893f31.
---
doc/muxers.texi | 2 +-
libavformat/mxfenc.c | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/doc/muxers.texi
2019-02-25 21:41 GMT+01:00, Yufei He :
> Please review this one.
The library needs non-free in configure and please
use dynamic linking, not loading at run-time.
Please find out what top-posting means and avoid it here, Carl Eugen
___
ffmpeg-devel
Fixes: Timeout 13149 (5sec -> 3sec), 13166 (11sec -> 7sec), 13430 (5sec -> 3sec)
Fixes:
13149/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_PGM_fuzzer-5760833622114304
Fixes:
13166/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_PGMYUV_fuzzer-5763216322330624
Fixes:
Fixes: Timeout (11sec -> 3sec)
Fixes:
13218/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_DFA_fuzzer-5661074316066816
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/dfa.c | 2 ++
1 file
Michael Niedermayer:
> On Fri, Mar 08, 2019 at 10:25:59AM +0100, Andreas Rheinhardt wrote:
>> When the new incremental parser was introduced, the old parser was
>> kept, because the new parser was unable to handle the way SSA packets
>> are put into Matroska. But since 2014 (since
>>
Maksym Veremeyenko (12019-03-10):
> removal code authors should find the core of their hates: either NDI
> technology or NewTek company
Please control your wording. Hate is a toxic irrational emotion.
Fighting companies that produce non-Libre software and want to profit
from the efforts of the
On 10.03.2019 19:04, Martin Vignali wrote:
[...]
The interest of sending a patch to this project is to benefit of the entire
infrastructure around the ffmpeg project.
Not the pleasure to read this mailing list.
Taking time to have a feature/enhancement integrate inside this project,
are
Andrey Semashev (12019-03-10):
> Yes. It doesn't make it less true, IMO.
It makes it neither true nor false but subject to personal judgements.
> I'm pointing out that there seem to be no technical reason for the removal,
> but instead there is a political one.
Indeed.
>
Martin Vignali (12019-03-10):
> It's about the lack of consistency on this topic, and the lack of a clear
> definition (documented at the project level, to avoid precisely this kind
> of situation)
As I said: if there is support for removing ALL non-free stuff, I am
behind it too. Is it clear
On 3/10/19 9:39 PM, Nicolas George wrote:
Andrey Semashev (12019-03-10):
But I think decisions like this should be based exclusively on
technical grounds. Political or populist arguments are not valid for
technical decisions, regardless how "good" or aligned with your personal
views
Le dim. 10 mars 2019 à 18:55, Nicolas George a écrit :
> Martin Vignali (12019-03-10):
> > Le dim. 10 mars 2019 à 17:03, Nicolas George a écrit :
> > > It's just ruining his effort to integrate this feature inside the
> project.
>
> Please do not attribute your sentences to me.
>
> > This
Andrey Semashev (12019-03-10):
> But I think decisions like this should be based exclusively on
> technical grounds. Political or populist arguments are not valid for
> technical decisions, regardless how "good" or aligned with your personal
> views they might seem.
Do you realize that
On 3/10/19 8:28 PM, Jean-Baptiste Kempf wrote:
On Sun, 10 Mar 2019, at 18:04, Martin Vignali wrote:
This discussion just send bad message to contributors.
You're just encourage them to keep code improvement in their own version of
ffmpeg.
Maintaining an FFmpeg is hard and costly.
This gives
Martin Vignali (12019-03-10):
> Le dim. 10 mars 2019 à 17:03, Nicolas George a écrit :
> > It's just ruining his effort to integrate this feature inside the project.
Please do not attribute your sentences to me.
> This discussion just send bad message to contributors.
If you consider "we do
Hi,
On Sun, Mar 10, 2019 at 1:04 PM Martin Vignali
wrote:
> But if this is the project policy...
>
Yes, I would like to propose to make this project policy.
Ronald
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Sun, 10 Mar 2019, at 18:04, Martin Vignali wrote:
> This discussion just send bad message to contributors.
> You're just encourage them to keep code improvement in their own version of
> ffmpeg.
Maintaining an FFmpeg is hard and costly.
This gives those people incentives to use open source
Le dim. 10 mars 2019 à 17:03, Nicolas George a écrit :
> Maksym Veremeyenko (12019-03-10):
> > code you going to remove was not made by you nor NewTek company.
> >
> > if you have a problem with NewTek company - do a step to solve it - dont
> > ruin a code.
>
> Nobody is ruining any code. Just
On Sun, Mar 10, 2019 at 09:15:40AM +0100, Paul B Mahol wrote:
> On 3/10/19, Michael Niedermayer wrote:
> > Fixes: Out of array access
> > Fixes:
> > 13552/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_IMM4_fuzzer-5767949648920576
> >
> > Found-by: continuous fuzzing process
> >
Maksym Veremeyenko (12019-03-10):
> code you going to remove was not made by you nor NewTek company.
>
> if you have a problem with NewTek company - do a step to solve it - dont
> ruin a code.
Nobody is ruining any code. Just removing it from a prominent
distribution and development platform.
On 09.03.2019 22:12, Kieran Kunhya wrote:
They have not responded to any communications:
https://trac.ffmpeg.org/ticket/7589
code you going to remove was not made by you nor NewTek company.
if you have a problem with NewTek company - do a step to solve it - dont
ruin a code.
--
Maksym
From: Jun Zhao
support regions of interest sidedata
Signed-off-by: Jun Zhao
---
libavfilter/vf_showinfo.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/libavfilter/vf_showinfo.c b/libavfilter/vf_showinfo.c
index e41c330..d0e140f
On Sun, 10 Mar 2019, Jean-Baptiste Kempf wrote:
On Sat, 9 Mar 2019, at 21:58, Marton Balint wrote:
On Sat, 9 Mar 2019, Dennis Mungai wrote:
> On Sat, 9 Mar 2019 at 23:19, Carl Eugen Hoyos wrote:
>> 2019-03-09 21:16 GMT+01:00, Carl Eugen Hoyos :
>> > 2019-03-09 21:12 GMT+01:00, Kieran Kunhya
Marton Balint (12019-03-09):
> You are not removing ndi because of the license violation, you are removing
> it because you don't like it.
Let us assume, for the rice wine of the argument, that you are right:
that we want to remove it because we do not like them. But ask yourself:
why do we not
Ronald S. Bultje (12019-03-09):
> I would not be against removing all closed-source support.
I would get behind that.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Sat, 9 Mar 2019, at 23:58, Ronald S. Bultje wrote:
> On Sat, Mar 9, 2019 at 4:02 PM Martin Vignali
> I would not be against removing all closed-source support. I have voiced
> this before in the realvideo discussion:
>
On Sat, 9 Mar 2019, at 21:58, Marton Balint wrote:
> On Sat, 9 Mar 2019, Dennis Mungai wrote:
> > On Sat, 9 Mar 2019 at 23:19, Carl Eugen Hoyos wrote:
> >> 2019-03-09 21:16 GMT+01:00, Carl Eugen Hoyos :
> >> > 2019-03-09 21:12 GMT+01:00, Kieran Kunhya :
> >> >> They have not responded to any
On 3/10/19, Michael Niedermayer wrote:
> Fixes: Out of array access
> Fixes:
> 13552/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_IMM4_fuzzer-5767949648920576
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> Signed-off-by: Michael
40 matches
Mail list logo
