Hello,
this patch is ffmpeg can now use the x265 multi-library interface to make a
run-time selection between a number of libx265 libraries (perhaps 8bpp and
16bpp).
I have attached the patch with this mail,
0001-avcodec-libx265-use-x265-Multi-library-Interface-to-.patch
Description: Binary
On Sun, May 03, 2015 at 04:11:04AM +0200, Michael Niedermayer wrote:
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/avcodec.h |2 ++
libavcodec/avpacket.c | 23 +++
2 files changed, 25 insertions(+)
applied
[...]
--
Michael GnuPG
AV_PIX_FMT_GRAY8/16 are considered YUV formats, and the color_range is
not set - so the API user will have to assume limitted range. (Unless
the API user adds a special-case for the PNG decoder.)
Just export the correct range - full range.
---
libavcodec/pngdec.c | 2 ++
1 file changed, 2
wm4 nfxjfg at googlemail.com writes:
AV_PIX_FMT_GRAY8/16 are considered YUV formats,
and the color_range is not set - so the API user
will have to assume limitted range. (Unless the
API user adds a special-case for the PNG decoder.)
I believe this is slightly misleading: gray8 and
gray16
On 05/07/2015 03:43 AM, Michael Niedermayer wrote:
On Thu, May 07, 2015 at 01:29:11AM +0530, Anshul wrote:
On 05/06/2015 01:21 AM, Michael Niedermayer wrote:
On Tue, May 05, 2015 at 08:33:42PM +0530, Anshul wrote:
[...]
and here is shorter file then previous one.
---
libavcodec/vp9dsp_template.c | 112 +--
1 file changed, 98 insertions(+), 14 deletions(-)
diff --git a/libavcodec/vp9dsp_template.c b/libavcodec/vp9dsp_template.c
index 18b14e8..8f10ccf 100644
--- a/libavcodec/vp9dsp_template.c
+++
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/x86/vp9dsp_init.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/libavcodec/x86/vp9dsp_init.c b/libavcodec/x86/vp9dsp_init.c
index f2ac6e8..979bd93 100644
--- a/libavcodec/x86/vp9dsp_init.c
+++
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/vp9dsp.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavcodec/vp9dsp.c b/libavcodec/vp9dsp.c
index d78c453..5ff18b4 100644
--- a/libavcodec/vp9dsp.c
+++ b/libavcodec/vp9dsp.c
@@ -21,6 +21,7 @@
*
On Thu, May 07, 2015 at 08:14:14AM -0400, Ronald S. Bultje wrote:
Hi,
On Thu, May 7, 2015 at 8:08 AM, Michael Niedermayer michae...@gmx.at
wrote:
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/x86/vp9dsp_init.c |5 +++--
1 file changed, 3 insertions(+), 2
On Thu, May 07, 2015 at 08:13:46AM -0400, Ronald S. Bultje wrote:
Hi,
On Thu, May 7, 2015 at 8:08 AM, Michael Niedermayer michae...@gmx.at
wrote:
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/vp9dsp.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Michael Niedermayer michaelni at gmx.at writes:
Attached patch allows decoding of the qdraw files I found.
Please comment, Carl Eugen
if that works, i guess its an improvment and should be ok
The patch that works for several public samples was
merged by Michael.
Thank you, Carl Eugen
Carl Eugen Hoyos cehoyos at ag.or.at writes:
Attached patch allows the autodetection of qdraw images
as decoded by libavcodec.
A variant of this was merged.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Thu, 7 May 2015 22:00:32 + (UTC)
Carl Eugen Hoyos ceho...@ag.or.at wrote:
wm4 nfxjfg at googlemail.com writes:
I believe this is slightly misleading: gray8 and
gray16 are interpreted as full-range by default
since years.
Really? Where?
In the software scaler.
Doesn't
On Thu, May 07, 2015 at 11:37:18PM +0200, wm4 wrote:
AV_PIX_FMT_GRAY8/16 are considered YUV formats, and the color_range is
not set - so the API user will have to assume limitted range. (Unless
the API user adds a special-case for the PNG decoder.)
Just export the correct range - full range.
wm4 nfxjfg at googlemail.com writes:
I believe this is slightly misleading: gray8 and
gray16 are interpreted as full-range by default
since years.
Really? Where?
In the software scaler.
Carl Eugen
___
ffmpeg-devel mailing list
On Thu, May 07, 2015 at 09:21:46PM +0100, Tom Butterworth wrote:
Fix alpha position error for edge blocks of odd-dimensioned frames
---
libavcodec/s3tc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
patch applied
thanks
[...]
--
Michael GnuPG fingerprint:
Ashamed to discover I omitted to progress the alpha position for edge
blocks 4 pixels, patch to follow.
The problem can be seen on the right edge of decodes of my previous
sample http://files.kriss.cx/387x249DXT3.txd
Profound apologies for the noise/extra patch.
On 7 May 2015 at 18:09, Michael
On Thu, May 07, 2015 at 11:56:36PM +0200, wm4 wrote:
APIC tags always have a description. Tag writers obviously leave it
empty if there is no description. In this case, libavformat would export
as title. Do not set the title instead.
---
Somewhat questionable. Take it or leave it.
---
Fix alpha position error for edge blocks of odd-dimensioned frames
---
libavcodec/s3tc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavcodec/s3tc.c b/libavcodec/s3tc.c
index 9886b1d..a422874 100644
--- a/libavcodec/s3tc.c
+++ b/libavcodec/s3tc.c
@@ -71,8 +71,10 @@
APIC tags always have a description. Tag writers obviously leave it
empty if there is no description. In this case, libavformat would export
as title. Do not set the title instead.
---
Somewhat questionable. Take it or leave it.
---
libavformat/id3v2.c | 3 ++-
1 file changed, 2 insertions(+), 1
The APIC description must be unique, and some ID3v2 tag writers add
spaces to write several APIC entries with the same description. The
trailing spaces simply serve as a way to disambiguate the description.
Do this so that API users do not have to special-case mp3 to fix this
cosmetic issue.
---
On Tue, May 05, 2015 at 09:16:44PM +0200, Andreas Cadhalpun wrote:
On 23.04.2015 17:50, Claudio Freire wrote:
On Thu, Apr 23, 2015 at 12:43 PM, Michael Niedermayer michae...@gmx.at
wrote:
ok, so is the patch the correct solution or are the fields already
invalid before this loop and
On Thu, May 07, 2015 at 12:27:48PM +, Nedeljko Babic wrote:
LGTM
applied
thanks
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
it is not once nor twice but times without number that the same ideas make
their appearance in the world. -- Aristotle
I took variables bx and by to be shorthand for block x and block y, so I
renamed them because they now refer to pixel and not block positions -
would you rather they remain bx, by?
Examples at
http://files.kriss.cx/387x249DXT1.txd
http://files.kriss.cx/387x249DXT3.txd
On Thu, May 7, 2015 at
On Thu, May 07, 2015 at 01:58:50AM -0300, James Almer wrote:
This allows the removal of a few branches.
Before:
lavu RIPEMD-160 size: 1048576 runs: 1024 time:7.052 +- 0.010
After:
lavu RIPEMD-160 size: 1048576 runs: 1024 time:6.865 +- 0.015
Hi,
On Thu, May 7, 2015 at 8:08 AM, Michael Niedermayer michae...@gmx.at
wrote:
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/x86/vp9dsp_init.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/libavcodec/x86/vp9dsp_init.c
LGTM
Thanks,
Nedeljko
Od: ffmpeg-devel-boun...@ffmpeg.org [ffmpeg-devel-boun...@ffmpeg.org] u ime
korisnika Shivraj Patil
Poslato: 4. maj 2015 14:21
Za: ffmpeg-devel@ffmpeg.org
Cc: Rob Isherwood; Shivraj Patil
Tema: [FFmpeg-devel] [PATCH] avcodec/mips:
On Wed, 6 May 2015 17:40:20 + (UTC)
Carl Eugen Hoyos ceho...@ag.or.at wrote:
Ronald S. Bultje rsbultje at gmail.com writes:
+static void vert_4x4_c(uint8_t *_dst, ptrdiff_t stride,
+ const uint8_t *left, const uint8_t *_top)
Once upon a time, it was claimed
Hi,
On Thu, May 7, 2015 at 8:08 AM, Michael Niedermayer michae...@gmx.at
wrote:
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/vp9dsp.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavcodec/vp9dsp.c b/libavcodec/vp9dsp.c
index
29 matches
Mail list logo
