[FFmpeg-devel] Lossy GIF encoding

Hello! I'm working on implementing lossy gif encoding, and I'd like to hear your opinion on how to best integrate it with ffmpeg in a way that would be acceptable for inclusion in the project. Lossy encoding is done by making LZW use approximate matching, and with the right input it can halve

[FFmpeg-devel] [PATCH v5] Improved the performance of 1 decode + N filter graphs and adaptive bitrate.

It enabled multiple filter graph concurrency, which bring above about 4%~20% improvement in some 1:N scenarios by CPU or GPU acceleration Below are some test cases and comparison as reference. (Hardware platform: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz) (Software: Intel iHD driver - 16.9.00100,

Re: [FFmpeg-devel] [PATCH] avcodec/mips: [loongson] optimizetheora?decoding with mmi.

On Fri, Feb 15, 2019 at 09:24:10AM +0800, guxiwei-hf wrote: > >On Fri, Feb 15, 2019 at 12:13:43AM +0100, Michael Niedermayer wrote: > > > On Wed, Feb 13, 2019 at 05:56:50PM +0800, Shiyou Yin wrote: > > > > >-Original Message- > > > > >From: ffmpeg-devel-boun...@ffmpeg.org > > > >

[FFmpeg-devel] [PATCH] avformat/http: Do not try to make a new request when seeking past the end of the file

From: Justin Ruggles This avoids making invalid HTTP Range requests for a byte range past the known end of the file during a seek. Those requests generally return a HTTP response of 416 Range Not Satisfiable, which causes an error response. Reference: https://tools.ietf.org/html/rfc7233

[FFmpeg-devel] [PATCH, RFC] lavf/deinterlace_qsv: set TFF or BFF together with progressive

Currently, BFF or TFF will not be set if the frame is progressive. This will break the Input PicStruct check in MSDK because of absence of the specific PicStruct check for: MFX_PICSTRUCT_PROGRESSIVE | MFX_PICSTRUCT_FIELD_REPEATED Set PicStruct to MFX_PICSTRUCT_FIELD_TFF or MFX_PICSTRUCT_FIELD_BFF

Re: [FFmpeg-devel] Lossy GIF encoding

On 2/15/19, Kornel wrote: > >>> Alternatively, would it be OK to create a separate codec just for >>> lossy compression? I would create a new GIF codec, define it under a >>> new name, and declare it always takes AV_PIX_FMT_RGB24 or >>> AV_PIX_FMT_RGBA. Is that a good approach? >> >> This sounds

Re: [FFmpeg-devel] Lossy GIF encoding

>> Alternatively, would it be OK to create a separate codec just for >> lossy compression? I would create a new GIF codec, define it under a >> new name, and declare it always takes AV_PIX_FMT_RGB24 or >> AV_PIX_FMT_RGBA. Is that a good approach? > > This sounds more like something that belongs

Re: [FFmpeg-devel] Lossy GIF encoding

fre 2019-02-15 klockan 09:01 + skrev Kornel: > Hello! > > I'm working on implementing lossy gif encoding, and I'd like to hear > your opinion on how to best integrate it with ffmpeg in a way that > would be acceptable for inclusion in the project. > > Lossy encoding is done by making LZW use

Re: [FFmpeg-devel] [PATCH, RFC] lavf/deinterlace_qsv: set TFF or BFF together with progressive

2019-02-15 20:50 GMT+01:00, Linjie Fu : > Currently, BFF or TFF will not be set if the frame is progressive. > This will break the Input PicStruct check in MSDK Was this always documented? If not - given that this is completely counterintuitive - this should be fixed in the driver. Carl Eugen

Re: [FFmpeg-devel] [PATCH] web/docs: remove ffserver links

On Wed, Feb 13, 2019, at 3:25 PM, Lou Logan wrote: > ffserver documentation and sample configuration file has been moved to > the wiki: > https://trac.ffmpeg.org/wiki/ffserver > > The files unlinked by this patch will be removed from the server. > > Signed-off-by: Lou Logan > --- >

Re: [FFmpeg-devel] [PATCH] avformat/http: Do not try to make a new request when seeking past the end of the file

On Fri, Feb 15, 2019 at 11:34:43AM -0500, Vittorio Giovara wrote: > From: Justin Ruggles > > This avoids making invalid HTTP Range requests for a byte range past the > known end of the file during a seek. Those requests generally return a HTTP > response of 416 Range Not Satisfiable, which

Re: [FFmpeg-devel] Lossy GIF encoding

On 2019-02-15 10:01, Kornel wrote: > libavcodec/gif.c in ff_gif_encoder.pix_fmts seems to passively declare types > of pixel formats it accepts. If you want to experiment you can change that so it accepts rgb (also or only). Then you can implement and test what you want, then you can ask about

Re: [FFmpeg-devel] [PATCH] avformat/oggparseogm: sync avctx w/ codecpar

On Mon, Feb 11, 2019 at 1:55 PM Chris Cunningham wrote: > On Fri, Feb 8, 2019 at 2:37 PM Michael Niedermayer > wrote: > >> ogg allows chaining streams when they have differing serial numbers >> https://xiph.org/ogg/doc/oggstream.html >> >> i think ive seen actual files doing this >> >>

Re: [FFmpeg-devel] [PATCH v5] Improved the performance of 1 decode + N filter graphs and adaptive bitrate.

On Fri, Feb 15, 2019 at 04:54:23PM -0500, Shaofei Wang wrote: > It enabled multiple filter graph concurrency, which bring above about > 4%~20% improvement in some 1:N scenarios by CPU or GPU acceleration > > Below are some test cases and comparison as reference. > (Hardware platform: Intel(R)

Re: [FFmpeg-devel] Lossy GIF encoding

On Fri, Feb 15, 2019 at 09:01:40 +, Kornel wrote: > The main problem I have now is that the existing GIF codec receives > frames already converted to AV_PIX_FMT_RGB8 or similar 8-bit format. > When working with 8bpp heavily-dithered input, the lossy compression > struggles to find runs of

Re: [FFmpeg-devel] [PATCH v7] mpeg12enc: Use Closed Captions if available

On 2/14/19 10:01 PM, Michael Niedermayer wrote: > if someone checks it against some spec and or tests it against some > decoders, probably yes, The relevant part of the spec is section 6.2.3 in , and I have indeed tested this

Re: [FFmpeg-devel] [PATCH] avcodec/mpeg4videodec: Clear interlaced_dct for studio profile

ok On Fri, 15 Feb 2019 at 00:58 Michael Niedermayer wrote: > Fixes: Out of array access > Fixes: > 13090/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MPEG4_fuzzer-5408668986638336 > > Found-by: continuous fuzzing process > https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg >