that is my fault and thank you for pointing out the mistake, it should be:
diff --git a/libavcodec/mips/h264qpel_mmi.c b/libavcodec/mips/h264qpel_mmi.c
index d641a51..737c68c 100644
--- a/libavcodec/mips/h264qpel_mmi.c
+++ b/libavcodec/mips/h264qpel_mmi.c
@@ -1901,9 +1901,9 @@ static void
On Mon, 23 May 2016 14:30:54 +0200
Håvard Espeland wrote:
> Currently, we are also developing a version of the same encoder for
> Nvidia TX1 with Cuda/Neon SIMD for supporting multiple high quality
> streams in real time using ffmpeg. I guess there is little interest
On Tue, May 17, 2016 at 07:14:24PM +0800, 周晓勇 wrote:
> avcodec/mips/blockdsp_mmi: Version 2 of the optimizations for loongson mmi
>
> 1. no longer use the register names directly and optimized code format
> 2. to be compatible with O32, specify type of address variable with
>
On Tue, May 17, 2016 at 07:15:46PM +0800, 周晓勇 wrote:
> avcodec/mips/pixblockdsp_mmi: Version 2 of the optimizations for loongson mmi
>
> 1. no longer use the register names directly and optimized code format
> 2. to be compatible with O32, specify type of address variable with
>
On Tue, May 17, 2016 at 07:16:42PM +0800, 周晓勇 wrote:
> avcodec/mips/idctdsp_mmi: Version 2 of the optimizations for loongson mmi
>
> 1. no longer use the register names directly and optimized code format
> 2. to be compatible with O32, specify type of address variable with
> mips_reg
On Mon, May 23, 2016 at 06:41:27PM +0300, foo86 wrote:
> Fixes potential parsing failure when total number of channels indicated
> by EXSS asset descriptor decreases mid-stream and stale embedded downmix
> flags are referenced.
> ---
> libavcodec/dca_exss.c | 6 ++
> 1 file changed, 2
On Tue, May 17, 2016 at 03:08:13PM +0800, 周晓勇 wrote:
> avcodec/mips/h264qpel_mmi: Version 2 of the optimizations for loongson mmi
>
> 1. no longer use the register names directly and optimized code format
> 2. to be compatible with O32, specify type of address variable with
>
On Mon, 23 May 2016 16:18:01 +0530, Venkat Rao wrote:
> Hi ,
>
> This is Venkat, I am new bee working with this open source codec. I need
> help on this libav transcoding.
[...]
Wrong mailing list. ffmpeg-devel is only for patch submissions and
discussions related to the development of FFmpeg.
On Mon, May 23, 2016 at 10:15 PM Davinder Singh wrote:
> On Sun, May 15, 2016 at 1:26 AM Michael Niedermayer
> wrote:
>
>> it would be better if the previous syntax would still work, in addition
>> to any new things
>>
>> bug reports, mailing list
Fixes potential parsing failure when total number of channels indicated
by EXSS asset descriptor decreases mid-stream and stale embedded downmix
flags are referenced.
---
libavcodec/dca_exss.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/libavcodec/dca_exss.c
On Thu, May 19, 2016 at 19:29:40 +0200, Stefano Sabatini wrote:
> > > +ffmpeg -i INPUT -codec copy -map 0 -an -vn data.fftd
BTW, is this possibly the first and only muxer which can actually remux
timed_id3? I have been trying to *extract* timed_id3, but haven't
figured out into which format I can
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Hendrik Leppkes
> Sent: Saturday, May 21, 2016 3:25 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/libopenh264enc: update to
On Mon, May 23, 2016 at 1:59 PM, Michael Niedermayer
wrote:
> On Mon, May 23, 2016 at 07:24:23AM -0400, Ronald S. Bultje wrote:
>> Hi,
>>
>> On Sun, May 22, 2016 at 11:39 PM, Michael Niedermayer <
>> mich...@niedermayer.cc> wrote:
>>
>> > On Sun, May 22, 2016 at 01:51:05AM
>> Have you test your optimizations in the other prores encoder (prores
> kostya) (who i think have more features (interlaced encoding and 444
> versions)) ?
No, we haven’t done this yet. The goal for us was performance without loosing
accuracy. We choose Anatoliy simply because it was faster.
Hi Paul,
> On 23 May 2016, at 13:13, Paul B Mahol wrote:
>
> On 5/23/16, Haavard Espeland wrote:
>> Hi guys,
>>
>> We have been working on Prores Anatoliy optimizations to get the speed up on
>> an embedded x86 platform. Fdct (10bit), scaling and
2016-05-23 13:44 GMT+02:00 Håvard Espeland :
>
> > The SIMD won't be accepted if it's intrinsics. The codeword encoding is
> not
> > SIMD, is it? So that may be worth upstreaming.
>
> All optimizations we’ve done are SIMD so it does not apply. Basically what
> we do
On Mon, May 23, 2016 at 07:24:23AM -0400, Ronald S. Bultje wrote:
> Hi,
>
> On Sun, May 22, 2016 at 11:39 PM, Michael Niedermayer <
> mich...@niedermayer.cc> wrote:
>
> > On Sun, May 22, 2016 at 01:51:05AM +, Davinder Singh wrote:
> > > On Sun, May 22, 2016 at 2:09 AM Michael Niedermayer
> >
On Sun, May 22, 2016 at 01:51:05AM +, Davinder Singh wrote:
[...]
> opencl.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> b3b89a601cc0447677a9f0f375c20f1f63d66f42
> 0005-libavutil-opencl-fixed-uninitialized-var-warning.patch
> From 9259a055b908c12c7ab7c5f08aae95f3cdaacfa8
> The SIMD won't be accepted if it's intrinsics. The codeword encoding is not
> SIMD, is it? So that may be worth upstreaming.
All optimizations we’ve done are SIMD so it does not apply. Basically what we
do for codewords is to process the shifting/masking for eight codewords at a
time. The
Hi,
On Sun, May 22, 2016 at 11:39 PM, Michael Niedermayer <
mich...@niedermayer.cc> wrote:
> On Sun, May 22, 2016 at 01:51:05AM +, Davinder Singh wrote:
> > On Sun, May 22, 2016 at 2:09 AM Michael Niedermayer
>
> > wrote:
> >
> > > On Sat, May 21, 2016 at 02:21:17PM
On 5/23/16, Haavard Espeland wrote:
> Hi guys,
>
> We have been working on Prores Anatoliy optimizations to get the speed up on
> an embedded x86 platform. Fdct (10bit), scaling and encoding of code words
> have been optimized with AVX2 instructions, and the
Hi Havard,
On Mon, May 23, 2016 at 6:36 AM, Håvard Espeland wrote:
> Hi guys,
>
> We have been working on Prores Anatoliy optimizations to get the speed up
> on an embedded x86 platform. Fdct (10bit), scaling and encoding of code
> words have been optimized with
Hi ,
This is Venkat, I am new bee working with this open source codec. I need
help on this libav transcoding.
I need to develop audio Transcoder which takes input as a audio raw file
and and will get information externally like parameters: what type of
codec, bit rate, number of channels etc.
23 matches
Mail list logo