On Tue, Feb 27, 2018 at 5:47 AM, wm4 wrote:
> On Mon, 26 Feb 2018 17:15:26 -0500
> Bjorn Roche wrote:
>
> > Okay, thanks Nicolas.
> >
> > I already submitted a patch to the mailing list a few months ago, I was
> > just hoping for an easier way to keep it
On 2/27/18, Bjorn Roche wrote:
> On Tue, Feb 27, 2018 at 10:34 AM, Paul B Mahol wrote:
>
>> On 2/27/18, Bjorn Roche wrote:
>> > On Tue, Feb 27, 2018 at 5:47 AM, wm4 wrote:
>> >
>> >> On Mon, 26 Feb 2018 17:15:26 -0500
Bjorn Roche (2018-02-27):
> According to Carl Eugen Hoyos: "This is Clément's code, he has to review
> your patch."
Then reply to Carl Eugen's mail to say "Clément does not seem to care
these days", to re-start the discussion.
Regards,
--
Nicolas George
signature.asc
Description: Digital
On 2/27/2018 1:28 PM, Bjorn Roche wrote:
> On Tue, Feb 27, 2018 at 10:34 AM, wm4 wrote:
>
>> On Tue, 27 Feb 2018 10:25:17 -0500
>> Bjorn Roche wrote:
>>
>>> On Tue, Feb 27, 2018 at 5:47 AM, wm4 wrote:
>>>
On Mon, 26 Feb 2018
On Tue, Feb 27, 2018 at 08:49:19AM +0100, Tobias Rapp wrote:
> On 27.02.2018 01:12, Michael Niedermayer wrote:
> >On Mon, Feb 26, 2018 at 05:09:04PM +0100, Tobias Rapp wrote:
> >>Move time string formatting into inline function. Also fixes out_time
> >>sign prefix for progress report.
> >>
>
On Tue, Feb 27, 2018 at 10:34 AM, Paul B Mahol wrote:
> On 2/27/18, Bjorn Roche wrote:
> > On Tue, Feb 27, 2018 at 5:47 AM, wm4 wrote:
> >
> >> On Mon, 26 Feb 2018 17:15:26 -0500
> >> Bjorn Roche wrote:
> >>
> >> >
Timo Rothenpieler (2018-02-27):
> compat: remove in-tree NVidia headers
Unless I was mistaken, there was no consensus for that yet.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
+cuda_deps="ffnvcodec"> cuda_deps_any="libdl LoadLibrary"
cuvid_deps="cuda"
d3d11va_deps="dxva_h ID3D11VideoDecoder ID3D11VideoContext"
@@ -5811,6 +5812,9 @@ check_type "va/va.h va/va_enc_vp9.h"
"VAEncPictureParameterBufferVP9"
check_type "vdpau/vdpau.h" "VdpPictureInfoHEVC"
On 2/27/18, Bjorn Roche wrote:
> On Tue, Feb 27, 2018 at 5:47 AM, wm4 wrote:
>
>> On Mon, 26 Feb 2018 17:15:26 -0500
>> Bjorn Roche wrote:
>>
>> > Okay, thanks Nicolas.
>> >
>> > I already submitted a patch to the mailing list a few
Tobias Rapp (2018-02-26):
> Signed-off-by: Tobias Rapp
> ---
> fftools/ffmpeg.c | 44
> 1 file changed, 20 insertions(+), 24 deletions(-)
LGTM.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
On Tue, 27 Feb 2018 10:25:17 -0500
Bjorn Roche wrote:
> On Tue, Feb 27, 2018 at 5:47 AM, wm4 wrote:
>
> > On Mon, 26 Feb 2018 17:15:26 -0500
> > Bjorn Roche wrote:
> >
> > > Okay, thanks Nicolas.
> > >
> > > I already submitted a
On Tue, Feb 27, 2018 at 4:24 PM, Nicolas George wrote:
> Timo Rothenpieler (2018-02-27):
>> compat: remove in-tree NVidia headers
>
> Unless I was mistaken, there was no consensus for that yet.
>
The issue holding up the patch was fixed, so who was still objecting?
- Hendrik
Fixes: Timeout
Fixes:
6297/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_NUV_fuzzer-4882404863901696
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/nuv.c | 11
Fixes: Timeout
Fixes:
6297/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_NUV_fuzzer-4882404863901696
Found-by: continuous fuzzing process
https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by: Michael Niedermayer
---
libavcodec/nuv.c | 3 +++
On Tue, Feb 27, 2018 at 10:34 AM, wm4 wrote:
> On Tue, 27 Feb 2018 10:25:17 -0500
> Bjorn Roche wrote:
>
> > On Tue, Feb 27, 2018 at 5:47 AM, wm4 wrote:
> >
> > > On Mon, 26 Feb 2018 17:15:26 -0500
> > > Bjorn Roche
Am 27.02.2018 um 16:24 schrieb Nicolas George:
Timo Rothenpieler (2018-02-27):
compat: remove in-tree NVidia headers
Unless I was mistaken, there was no consensus for that yet.
From how I understood the discussion the only issue people had was that
it was still not pushed, with MSVC
Hendrik Leppkes (2018-02-27):
> The issue holding up the patch was fixed, so who was still objecting?
You were still objecting. The fact that is was resolved had not been
made public when I posted my message.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
---
libavformat/dashenc.c | 28 +---
1 file changed, 25 insertions(+), 3 deletions(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index 83e0cff728..66f12d8d49 100644
--- a/libavformat/dashenc.c
+++ b/libavformat/dashenc.c
@@ -1131,6 +1131,28 @@ static int
On 2/27/2018 9:58 PM, Hendrik Leppkes wrote:
> On Tue, Feb 27, 2018 at 9:35 PM, David Murmann
wrote:
>> Quantization scaling seems to be a slight bottleneck,
>> this change allows the compiler to more easily vectorize
>> the loop. This improves total encoding performance
Hi, and welcome back.
Stephan Holljes (2018-02-26):
> seeing that people are already applying for projects, I think I should as
> well.
>
> My name is Stephan Holljes, on IRC I go by klaxa. Some may remember me
> from GSoC 2015 where I implemented the (how I later found out
> controversly
On Thu, Feb 22, 2018 at 04:35:50AM +0100, Michael Niedermayer wrote:
> Fixes: OOM
> Fixes:
> 6216/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_G2M_fuzzer-4983807968018432
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
>
On Wed, Feb 21, 2018 at 04:29:44AM +0100, Michael Niedermayer wrote:
> Fixes: 6154/clusterfuzz-testcase-minimized-5762231061970944
> Fixes: runtime error: shift exponent 63 is too large for 32-bit type 'int'
>
> Found-by: continuous fuzzing process
>
Quantization scaling seems to be a slight bottleneck,
this change allows the compiler to more easily vectorize
the loop. This improves total encoding performance in my
tests by about 10-20%.
Signed-off-by: David Murmann
---
libavcodec/proresenc_anatoliy.c | 12
1
On Tue, Feb 27, 2018 at 11:55 AM, James Almer wrote:
> On 2/27/2018 1:28 PM, Bjorn Roche wrote:
> > On Tue, Feb 27, 2018 at 10:34 AM, wm4 wrote:
> >
> > According to Carl Eugen Hoyos: "This is Clément's code, he has to review
> > your patch."
>
> He's
On Tue, Feb 27, 2018 at 9:35 PM, David Murmann wrote:
> Quantization scaling seems to be a slight bottleneck,
> this change allows the compiler to more easily vectorize
> the loop. This improves total encoding performance in my
> tests by about 10-20%.
>
> Signed-off-by:
Sure. Updated!
On Tue, Feb 27, 2018 at 2:38 AM, Michael Niedermayer wrote:
> On Mon, Feb 26, 2018 at 10:37:51AM -0800, Xiaohan Wang (王消寒) wrote:
> > Thanks! Updated the patch. Please take a look again.
> >
> > On Sat, Feb 24, 2018 at 7:04 PM, Michael Niedermayer
>
On Mon, Feb 26, 2018 at 11:00:28PM +0100, Michael Niedermayer wrote:
> Fixes: Timeout
> Fixes:
> 6276/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_WMV1_fuzzer-5881196690014208
>
> Found-by: continuous fuzzing process
> https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
>
Hi everybody,
My name is Swastik Haldar. I am a third year undergrad at the Indian
Institute of Technology, Kharagpur. I would like to apply for image Super
Resolution Filter development for FFMPEG in GSoC '18.
I am currently working on the qualification task for this project. This
is my
2018-02-27 9:26 GMT+01:00 Maxton :
> I looked at the code in avcodec/wmaprodec.c and noticed that
> the maximum number of channels was set to 8, but I think this
> is a mistake as the number of channels should logically be
>
> XMA_MAX_STREAMS * XMA_MAX_CHANNELS_STREAM
On Tue, 27 Feb 2018 12:27:10 +0100
Hendrik Leppkes wrote:
> On Tue, Feb 27, 2018 at 12:13 PM, Nicolas George wrote:
> > Hendrik Leppkes (2018-02-27):
> >> Something works today, you want to refactor it, you get to keep it
> >> working. Its a simple rule.
On 2/25/2018 9:20 PM, Marton Balint wrote:
> From: Timo Rothenpieler
>
> External headers are no longer welcome in the ffmpeg codebase because they
> increase the maintenance burden. However, in the NVidia case the vanilla
> headers need some modifications to be usable in
On Mon, 26 Feb 2018 17:15:26 -0500
Bjorn Roche wrote:
> Okay, thanks Nicolas.
>
> I already submitted a patch to the mailing list a few months ago, I was
> just hoping for an easier way to keep it fresh since it's gone stale, and I
> had some more fixes for it.
Just ping it a
On Tue, Feb 27, 2018 at 11:45 AM, wm4 wrote:
> On Mon, 26 Feb 2018 22:15:04 +0100 (CET)
> Marton Balint wrote:
>
>> On Mon, 26 Feb 2018, Timo Rothenpieler wrote:
>>
>> > The reason I haven't pushed this yet is because it breaks the build on
>> > MSVC, and I
On Tue, Feb 27, 2018 at 12:13 PM, Nicolas George wrote:
> Hendrik Leppkes (2018-02-27):
>> Something works today, you want to refactor it, you get to keep it
>> working. Its a simple rule.
>
> It is a simple rule, but not one that must be followed blindly. Please
> do not be
On Mon, Feb 26, 2018 at 10:37:51AM -0800, Xiaohan Wang (王消寒) wrote:
> Thanks! Updated the patch. Please take a look again.
>
> On Sat, Feb 24, 2018 at 7:04 PM, Michael Niedermayer > wrote:
>
> > On Fri, Feb 23, 2018 at 05:12:05PM -0800, Xiaohan Wang (王消寒) wrote:
> > >
On Tue, 27 Feb 2018 11:49:25 +0100
Hendrik Leppkes wrote:
> On Tue, Feb 27, 2018 at 11:45 AM, wm4 wrote:
> > On Mon, 26 Feb 2018 22:15:04 +0100 (CET)
> > Marton Balint wrote:
> >
> >> On Mon, 26 Feb 2018, Timo Rothenpieler wrote:
>
On Tue, Feb 27, 2018 at 11:59 AM, wm4 wrote:
> On Tue, 27 Feb 2018 11:49:25 +0100
> Hendrik Leppkes wrote:
>
>> On Tue, Feb 27, 2018 at 11:45 AM, wm4 wrote:
>> > On Mon, 26 Feb 2018 22:15:04 +0100 (CET)
>> > Marton Balint
Hendrik Leppkes (2018-02-27):
> Something works today, you want to refactor it, you get to keep it
> working. Its a simple rule.
It is a simple rule, but not one that must be followed blindly. Please
do not be dogmatic.
Sometimes, we have to "break" an obscure case in order to make progress.
We
On Mon, Feb 26, 2018 at 03:29:46AM +0100, Michael Niedermayer wrote:
> Fixes: Timeout
> Fixes:
> 6266/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_RSCC_fuzzer-5692431816196096
>
> Its not known if nb_tiles is allowed so it is not treated as an error
>
> Found-by: continuous fuzzing process
Hendrik Leppkes (2018-02-27):
> I know you Linux people don't want to hear it, but Windows is not an
> "obscure" platform.
Maybe. But I have to emphasize that you refused to give comment to the
practical part of my message. Does it means you do not have an
objection?
We can go ahead, then.
Hendrik Leppkes (2018-02-27):
> Your entire approach revolves around it being an obscure feature that
> noone is going to miss, so you can take that as an objection.
>
> The original author never submitted his patch because he didn't finish
> it yet. Someone else finds it somewhere and sends it
On Mon, 26 Feb 2018 22:15:04 +0100 (CET)
Marton Balint wrote:
> On Mon, 26 Feb 2018, Timo Rothenpieler wrote:
>
> > The reason I haven't pushed this yet is because it breaks the build on
> > MSVC, and I haven't gotten around to figuring out pkg-config for it.
>
> Right. I
On Tue, 27 Feb 2018 12:01:48 +0100
Hendrik Leppkes wrote:
> On Tue, Feb 27, 2018 at 11:59 AM, wm4 wrote:
> > On Tue, 27 Feb 2018 11:49:25 +0100
> > Hendrik Leppkes wrote:
> >
> >> On Tue, Feb 27, 2018 at 11:45 AM, wm4
On Tue, Feb 27, 2018 at 12:29 PM, Nicolas George wrote:
> Hendrik Leppkes (2018-02-27):
>> I know you Linux people don't want to hear it, but Windows is not an
>> "obscure" platform.
>
> Maybe. But I have to emphasize that you refused to give comment to the
> practical part of my
Hi All,
i tried transcoding sample application shared with examples. As i'm new to
video codecs didnot understand fully , how to scale a resolution of video
i.e if input of 720p trancode to 240p without changing video codec.
i tried to enhance transcoding sample with sws_scale(); i.e scaling
tis 2018-02-27 klockan 19:55 +0530 skrev Vittalprasad:
> Hi All,
>
> i tried transcoding sample application shared with examples. As i'm
> new to
> video codecs didnot understand fully , how to scale a resolution of
> video
> i.e if input of 720p trancode to 240p without changing video codec.
>
On Tue, Feb 27, 2018 at 8:13 PM, Nicolas George wrote:
> Hi, and welcome back.
Thanks you, and thanks for the feedback.
>
> Stephan Holljes (2018-02-26):
>> seeing that people are already applying for projects, I think I should as
>> well.
>>
>> My name is Stephan Holljes, on
On 27 February 2018 at 21:22, David Murmann wrote:
>
> On 2/27/2018 9:58 PM, Hendrik Leppkes wrote:
> > On Tue, Feb 27, 2018 at 9:35 PM, David Murmann
> wrote:
> >> Quantization scaling seems to be a slight bottleneck,
> >> this change allows the
fix ticket: #7044
Get the first video stream to reference for split segment
when there have more than one video stream
Signed-off-by: Steven Liu
---
libavformat/hlsenc.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/libavformat/hlsenc.c
On 2/28/18 10:18 AM, Steven Liu wrote:
> fix ticket: #7044
> Get the first video stream to reference for split segment
> when there have more than one video stream
>
> Signed-off-by: Steven Liu
> ---
> libavformat/hlsenc.c | 8 +++-
> 1 file changed, 7 insertions(+),
2018-02-28 11:32 GMT+08:00 Jeyapal, Karthick :
>
>
> On 2/27/18 11:09 AM, Steven Liu wrote:
>> fix ticket: #7044
>> Get the first video stream to reference for split segment
>> when there have more than one video stream
>>
>> Signed-off-by: Steven Liu
>>
On Sat, Feb 24, 2018 at 09:31:30PM +, Rostislav Pehlivanov wrote:
> On 24 February 2018 at 12:01, Aurelien Jacobs wrote:
>
> > On Thu, Feb 22, 2018 at 06:18:48PM +, Rostislav Pehlivanov wrote:
> > > On 21 February 2018 at 22:37, Aurelien Jacobs wrote:
On Mon, Feb 19, 2018 at 02:39:25AM +0100, Michael Niedermayer wrote:
> No currently maintained distro or app uses 3.1 on
> https://trac.ffmpeg.org/wiki/Downstreams
> so it would help noone if we continue maintaining 3.1.*
> ---
> src/download| 39 ---
>
This commit replaces the huge and impractical LUT which converted coeffs
and a quantizer to bits to encode and instead uses a standard multiplication
and a shift to replace the division and then codes the values using the
regular golomb coding functions.
I was unable to see a performance
ping
On 2018/2/23 15:12, Jun Zhao wrote:
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, 22 Feb 2018, Paul B Mahol wrote:
On 2/22/18, Tomas Haerdin wrote:
ons 2018-02-21 klockan 23:06 +0100 skrev Marton Balint:
On Wed, 21 Feb 2018, Tomas Haerdin wrote:
> loer 2018-02-17 klockan 22:45 +0100 skrev Marton Balint:
> > The reference point for a KAG is
On 27 February 2018 at 23:56, Aurelien Jacobs wrote:
>
> So I've updated the patch with only a msbc and a delay option and
> I've added some sane parameters decisions, mainly based on the following
> study :
> https://pdfs.semanticscholar.org/1f19/561d03bc88b67728375566c95bbf77
On 2/27/18 11:09 AM, Steven Liu wrote:
> fix ticket: #7044
> Get the first video stream to reference for split segment
> when there have more than one video stream
>
> Signed-off-by: Steven Liu
> ---
> libavformat/hlsenc.c | 12 ++--
> 1 file changed, 10
On 2/27/18 2:48 PM, Serhii Marchuk wrote:
> ---
> libavformat/dashenc.c | 28 +---
> 1 file changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
> index 83e0cff728..66f12d8d49 100644
> --- a/libavformat/dashenc.c
> +++
59 matches
Mail list logo