Hi,
the webp lossless doc was unclear regarding palette index falling out of
range.
See issue #206 [1] for the bug report.
The solution retained was to treat out-of-range index as color 0x,
so we could keep the speed-up in libwebp (we use fake extra entries in the
cmap to handle out-of-bou
Yes, I think you're right. Thanks for help!
2014-09-18 11:46 GMT+08:00 Timothy Gu :
> On Sep 17, 2014 7:58 PM, "Lynn Yu" wrote:
> >
> > I think you misunderstand what I mean. Of course I know how each lib
> works.
> > I want to know, if I 'ar' the libavformat.a libavcodec.a into one
> > libffmpe
On Sep 17, 2014 8:02 PM, "Michael Niedermayer" wrote:
>
> On Wed, Sep 17, 2014 at 07:16:30PM -0700, Daniel Verkamp wrote:
> > On Wed, Sep 17, 2014 at 12:59 PM, Michael Niedermayer
wrote:
> > > On Wed, Sep 17, 2014 at 11:33:32AM -0700, Daniel Verkamp wrote:
> > >> Hi FFmpeg web folks,
> > >>
> > >
On Sep 17, 2014 7:58 PM, "Lynn Yu" wrote:
>
> I think you misunderstand what I mean. Of course I know how each lib
works.
> I want to know, if I 'ar' the libavformat.a libavcodec.a into one
> libffmpeg.a, how can I retain their function symbols in the new
libffmpeg.a.
There won't be any symbol cl
On Wed, Sep 17, 2014 at 07:16:30PM -0700, Daniel Verkamp wrote:
> On Wed, Sep 17, 2014 at 12:59 PM, Michael Niedermayer
> wrote:
> > On Wed, Sep 17, 2014 at 11:33:32AM -0700, Daniel Verkamp wrote:
> >> Hi FFmpeg web folks,
> >>
> >> When visiting http://fate.ffmpeg.org/ using a browser that enfor
I think you misunderstand what I mean. Of course I know how each lib works.
I want to know, if I 'ar' the libavformat.a libavcodec.a into one
libffmpeg.a, how can I retain their function symbols in the new libffmpeg.a.
2014-09-18 4:21 GMT+08:00 Marcus Johnson :
> No, it won't work because the li
On 17/09/14 11:44 PM, Michael Niedermayer wrote:
> On Wed, Sep 17, 2014 at 10:15:30PM -0300, James Almer wrote:
>> No point in having the sad8 functions separate now that the loop is no
>> longer unrolled.
>>
>> Signed-off-by: James Almer
>> ---
>> libavcodec/x86/me_cmp.asm | 221
>> +++
On Wed, Sep 17, 2014 at 10:15:30PM -0300, James Almer wrote:
> No point in having the sad8 functions separate now that the loop is no
> longer unrolled.
>
> Signed-off-by: James Almer
> ---
> libavcodec/x86/me_cmp.asm | 221
> +++---
> 1 file changed, 93
On Wed, Sep 17, 2014 at 12:59 PM, Michael Niedermayer wrote:
> On Wed, Sep 17, 2014 at 11:33:32AM -0700, Daniel Verkamp wrote:
>> Hi FFmpeg web folks,
>>
>> When visiting http://fate.ffmpeg.org/ using a browser that enforces
>> CORS[1], loading the FontAwesome icon font causes this error:
>>
>>
No point in having the sad8 functions separate now that the loop is no
longer unrolled.
Signed-off-by: James Almer
---
libavcodec/x86/me_cmp.asm | 221 +++---
1 file changed, 93 insertions(+), 128 deletions(-)
diff --git a/libavcodec/x86/me_cmp.asm b/lib
On Thu, Aug 28, 2014 at 12:14:48AM -0300, James Almer wrote:
> On 27/08/14 11:53 PM, Wei Gao wrote:
> > 2014-08-13 9:45 GMT+08:00 Timothy Gu :
> >
> >> On Aug 12, 2014 6:43 PM, "highgod0401" wrote:
> >>
> >>> Hi
> >>>
> >>> Warning is OK for me.
> >>
> >> Do you plan to change the API?
> >>
> >
On Thu, Jul 24, 2014 at 12:14:14AM +0200, Michael Niedermayer wrote:
> Avoid warning that its not set
>
> Signed-off-by: Michael Niedermayer
> ---
> libavformat/rtpenc_chain.c |2 ++
> 1 file changed, 2 insertions(+)
a variant of this was applied by martin and merged by me
[...]
--
Michae
On Thu, Sep 18, 2014 at 12:16:42AM +0200, Andreas Cadhalpun wrote:
> Hi,
>
> FFmpeg failed to build in Debian on powerpc/ppc64el with the
> following error:
> libavfilter/deshake.h:51:24: warning: declaration does not declare anything
> MotionVector vector; ///< Motion vector
>
On Wed, Sep 17, 2014 at 10:55:52PM +0200, Vitor Sessak wrote:
> On Wed, Sep 17, 2014 at 10:31 PM, Michael Niedermayer
> wrote:
> > On Wed, Sep 17, 2014 at 09:21:08PM +0200, Vitor Sessak wrote:
> >> Hi!
> >>
> >> I'm not sure we can count on registers been preserved across ASM
> >> blocks. Moreove
On 18.09.2014 00:33, Carl Eugen Hoyos wrote:
Andreas Cadhalpun googlemail.com> writes:
FFmpeg failed to build in Debian on powerpc/ppc64el
with the following error:
Out of curiosity:
How can I reproduce this? I believe I tested on ppc64
Linux last week...
If you have a Debian jessie/sid in
Andreas Cadhalpun googlemail.com> writes:
> FFmpeg failed to build in Debian on powerpc/ppc64el
> with the following error:
Out of curiosity:
How can I reproduce this? I believe I tested on ppc64
Linux last week...
In any case: No objections here, Carl Eugen
_
Hi,
FFmpeg failed to build in Debian on powerpc/ppc64el with the following
error:
libavfilter/deshake.h:51:24: warning: declaration does not declare anything
MotionVector vector; ///< Motion vector
^
libavfilter/vf_deshake.c: In function 'find_motion':
libavfilter/
On Wed, Sep 17, 2014 at 10:31 PM, Michael Niedermayer wrote:
> On Wed, Sep 17, 2014 at 09:21:08PM +0200, Vitor Sessak wrote:
>> Hi!
>>
>> I'm not sure we can count on registers been preserved across ASM
>> blocks. Moreover, this causes problems with utils that instrument the
>> code by inserting f
On Wed, Sep 17, 2014 at 09:21:08PM +0200, Vitor Sessak wrote:
> Hi!
>
> I'm not sure we can count on registers been preserved across ASM
> blocks. Moreover, this causes problems with utils that instrument the
> code by inserting function calls between lines (like ThreadSanitizer).
>
> The attache
On Wed, 17 Sep 2014 22:56:27 +0300
Andrey Utkin wrote:
> I have got many complaints about FFmpeg error codes being too
> abstract. Not helpful for quick resolution, in a lot of such cases
> real issue with application must be investigated manually (by
> reviewing log with debug loglevel and/or sn
On Wed, 17 Sep 2014, Michael Niedermayer wrote:
On Wed, Sep 17, 2014 at 03:47:09AM +0200, Michael Niedermayer wrote:
On Wed, Sep 17, 2014 at 12:19:49AM +0200, Marton Balint wrote:
On Sat, 6 Sep 2014, Marton Balint wrote:
Create a generic frame and a frame queue struct to handle video pictu
No, it won't work because the libraries are for different purposes.
as per your example, 4xm in the libavcodec directory is for decoding the
file, it implements the actual algorithm. 4xm in the libavformat directory
is for demuxing the codec from the 4xm container, you need both for it to
work.
O
On Wed, Sep 17, 2014 at 11:33:32AM -0700, Daniel Verkamp wrote:
> Hi FFmpeg web folks,
>
> When visiting http://fate.ffmpeg.org/ using a browser that enforces
> CORS[1], loading the FontAwesome icon font causes this error:
>
> Font from origin 'https://ffmpeg.org' has been blocked from loading
I have got many complaints about FFmpeg error codes being too
abstract. Not helpful for quick resolution, in a lot of such cases
real issue with application must be investigated manually (by
reviewing log with debug loglevel and/or sniffing traffic).
E.g., "Invalid data" may mean almost everything,
Hi!
I'm not sure we can count on registers been preserved across ASM
blocks. Moreover, this causes problems with utils that instrument the
code by inserting function calls between lines (like ThreadSanitizer).
The attached patch fix one instance of this problem in swscale.
-Vitor
0001-swscale-
Hi FFmpeg web folks,
When visiting http://fate.ffmpeg.org/ using a browser that enforces
CORS[1], loading the FontAwesome icon font causes this error:
Font from origin 'https://ffmpeg.org' has been blocked from loading
by Cross-Origin Resource Sharing policy: No
'Access-Control-Allow-Origin' he
On 17/09/14 4:40 AM, Paul B Mahol wrote:
> On 9/15/14, James Almer wrote:
>> Signed-off-by: James Almer
>> ---
>> libavfilter/avcodec.c | 20
>> libavfilter/avcodec.h | 41 -
>> libavfilter/version.h | 3 ---
>> 3 files changed, 64 de
> On Tuesday, September 16, 2014 1:34 PM, Nicholas Robbins
> wrote:
> > Ok, I seem to have a partial solution.
>
> I thought that the place to put this would be in the dvdsubenc.c. So I made
> the
> following changes (sorry for inline patch)
>
> So, it seems like what I am doing produc
On Wed, Sep 17, 2014 at 01:14:33PM -0300, James Almer wrote:
> On 17/09/14 9:07 AM, Michael Niedermayer wrote:
> > On Wed, Sep 17, 2014 at 01:18:12PM +0200, Clément Bœsch wrote:
> >> On Wed, Sep 17, 2014 at 11:41:32AM +0200, James Almer wrote:
> >>> ffmpeg | branch: master | James Almer | Tue Sep
Gorilla Maguila gmail.com> writes:
> http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2014-February/154612.html
>
> I attach a new patch with improvements:
I wanted to write an answer with a few minor remarks
but just saw that several issues from the original
review are still valid:
http://thre
After contacting the original author of the the patch posted in:
http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2014-February/154612.html
I attach a new patch with improvements:
- Better codec detection in amfmetata
- Better live streams handling (Get current segment, calculate next
segment..etc
On 17/09/14 9:07 AM, Michael Niedermayer wrote:
> On Wed, Sep 17, 2014 at 01:18:12PM +0200, Clément Bœsch wrote:
>> On Wed, Sep 17, 2014 at 11:41:32AM +0200, James Almer wrote:
>>> ffmpeg | branch: master | James Almer | Tue Sep 16
>>> 21:41:47 2014 -0300| [0456d169c469a79e305813d14c873fe698c8c57
I've build ffmpeg static libraries, and all necessary objs (*.o) generated
in their source directory.
I use 'ar' to archive all these objs into one libffmpeg.a.
command: *ar rc libffmpeg.a *.o*
I notice that, there are some objs have same name in different dirs, for
example *libavformat/4xm.o a
On Wed, Sep 17, 2014 at 01:18:12PM +0200, Clément Bœsch wrote:
> On Wed, Sep 17, 2014 at 11:41:32AM +0200, James Almer wrote:
> > ffmpeg | branch: master | James Almer | Tue Sep 16
> > 21:41:47 2014 -0300| [0456d169c469a79e305813d14c873fe698c8c572] |
> > committer: Michael Niedermayer
> >
> > x
Hi,
On Wed, Sep 17, 2014 at 4:08 AM, Michael Niedermayer
wrote:
> On Sun, Sep 14, 2014 at 01:01:45AM +0200, Mikulas Patocka wrote:
>
> In the program, you can easily determine what -march was passed to the
> > compiler and react to it - if one of __i686__, __athlon__, __SSE__ is
> > defined, you
On Wed, Sep 17, 2014 at 11:41:32AM +0200, James Almer wrote:
> ffmpeg | branch: master | James Almer | Tue Sep 16
> 21:41:47 2014 -0300| [0456d169c469a79e305813d14c873fe698c8c572] | committer:
> Michael Niedermayer
>
> x86/me_cmp: port mmxext and sse2 sad functions to yasm
>
> Also add a missi
On Sun, Sep 14, 2014 at 01:01:45AM +0200, Mikulas Patocka wrote:
> > > Hi
> > >
> > > Here I'm sending two patches to fix portability for 586-class machines
> > > (Pentium, K6, etc.)
> > >
> > >
> > > If the CPU is generic, 386, 486 or pentium, we must not use cmov in inline
> > > assembler.
> > >
On Mon, Sep 15, 2014 at 11:19 AM, Amnon Israely wrote:
> It's work already more than 24h
>
> Maybe it's not a big problem but in some scenario may do some problem
>
> Input #0, decklink, from 'DeckLink SDI (3)@3':
> Duration: N/A, start: 0.00, bitrate: 172032 kb/s
> Stream #0:0: Audio:
On Tue, Sep 16, 2014 at 09:41:47PM -0300, James Almer wrote:
> Also add a missing c->pix_abs[0][0] initialization, and sse2 versions of
> sad16_x2, sad16_y2 and sad16_xy2 (%15 to %20 faster than mmxext).
> Since the _xy2 versions are not bitexact, they are accordingly marked as
> approximate.
>
>
On 9/15/14, James Almer wrote:
> Signed-off-by: James Almer
> ---
> libavfilter/avcodec.c | 20
> libavfilter/avcodec.h | 41 -
> libavfilter/version.h | 3 ---
> 3 files changed, 64 deletions(-)
>
> diff --git a/libavfilter/avcodec.c
On 16.09.2014, at 22:35, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch allows using libopenjpeg 2.x (tested with 2.1) here.
Doesn't it make sense to prefer the newest version, i.e. we should check for
this first and not last?
___
ffmpeg-devel maili
41 matches
Mail list logo
