Re: [FFmpeg-devel] FFmpeg 3.2

On 10/26/2016 10:45 PM, Michael Niedermayer wrote: applied you are maintainer of that file, you can send me your public ssh key to get git write access, that would simplify your work maintaining that file as you can push changes yourself For something that would/will be so rarely changed and

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Wed, Oct 26, 2016 at 3:54 PM, Michael Niedermayer wrote: > On Tue, Oct 25, 2016 at 12:00:01AM +0200, Hendrik Leppkes wrote: >> On Mon, Oct 24, 2016 at 10:31 PM, Ronald S. Bultje >> wrote: >> > Hi, >> > >> > On Mon, Oct 24, 2016 at 4:26 PM, Henrik

Re: [FFmpeg-devel] FFmpeg 3.2

2016-10-26 1:32 GMT+02:00 Michael Niedermayer : > On Wed, Sep 28, 2016 at 05:11:23PM +0200, Carl Eugen Hoyos wrote: >> 2016-09-27 15:30 GMT+02:00 Michael Niedermayer : >> >> > Its long since FFmpeg 3.1, so its time to make 3.2 >> >> The configure

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Wed, Oct 26, 2016 at 04:21:14PM +0200, Hendrik Leppkes wrote: > On Wed, Oct 26, 2016 at 3:54 PM, Michael Niedermayer > wrote: > > On Tue, Oct 25, 2016 at 12:00:01AM +0200, Hendrik Leppkes wrote: > >> On Mon, Oct 24, 2016 at 10:31 PM, Ronald S. Bultje

Re: [FFmpeg-devel] [PATCH 1/2] img2: added support for %t output pattern

On Tue, Oct 25, 2016 at 06:38:12PM -0600, Roger Pack wrote: > On 10/25/16, Michael Niedermayer wrote: > > On Mon, Oct 24, 2016 at 03:20:14PM -0600, Roger Pack wrote: > >> On 10/16/16, Michael Niedermayer wrote: > >> > On Mon, Oct 10, 2016 at

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Wed, Oct 26, 2016 at 05:08:56PM +0200, Hendrik Leppkes wrote: > > One of the highly appreciated virtues of ffmpeg is its efficiency, > > this makes hardware much more useful. Please do not cut off the low > > end systems when possible. > Its not about low-end, its about 15+ years old hardware.

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Wed, 26 Oct 2016 18:04:24 +0200 u-9...@aetey.se wrote: > On Wed, Oct 26, 2016 at 05:08:56PM +0200, Hendrik Leppkes wrote: > > > One of the highly appreciated virtues of ffmpeg is its efficiency, > > > this makes hardware much more useful. Please do not cut off the low > > > end systems when

Re: [FFmpeg-devel] [PATCH] lavfi/vf_overlay: support NV12 and NV21

On Tue, Oct 25, 2016 at 09:58:43PM -0500, Rodger Combs wrote: > --- > libavfilter/vf_overlay.c| 22 +- > tests/fate/filter-video.mak | 10 ++ > tests/filtergraphs/overlay_nv12 | 5 + > tests/filtergraphs/overlay_nv21 | 5 + > 4 files changed, 37

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Wed, Oct 26, 2016 at 04:21:14PM +0200, Hendrik Leppkes wrote: > You can add "not caring about first-gen sse2 CPUs" to the list as > well, if you want. Those are way old as well. > There is going to be a performance loss either way, except that emms > slows it down everywhere, while using sse2

Re: [FFmpeg-devel] [PATCH] lavf/mov.c: Use the first sidx for tracks without sidx.

On Tue, Oct 25, 2016 at 11:07:58PM -0700, Sasi Inguva wrote: > According to spec ISO_IEC_15444_12 "For any media stream for which no segment > index is present, referred to as non‐indexed stream, the media stream > associated with the first Segment Index box in the segment serves as a >

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Wed, Oct 26, 2016 at 4:52 PM, wrote: > On Wed, Oct 26, 2016 at 04:21:14PM +0200, Hendrik Leppkes wrote: >> You can add "not caring about first-gen sse2 CPUs" to the list as >> well, if you want. Those are way old as well. >> There is going to be a performance loss either way,

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

Hi, On Wed, Oct 26, 2016 at 12:04 PM, wrote: > On Wed, Oct 26, 2016 at 05:08:56PM +0200, Hendrik Leppkes wrote: > > you just have to replace this stuff. > > For $100 you can buy a system at least 10 times as fast then those. > > Heck even a RPi might rival those for $20 or so.

Re: [FFmpeg-devel] FFmpeg 3.2

On Wed, Oct 26, 2016 at 06:12:22PM -0400, Stephen Hutchinson wrote: > On 10/26/2016 3:29 PM, Michael Niedermayer wrote: > >On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote: > >>Hi all > >> > >>Its long since FFmpeg 3.1, so its time to make 3.2 > >>ill branch release/3.2 off

[FFmpeg-devel] [PATCH] lavf/mov.c: Use the first sidx for tracks without sidx.

According to spec ISO_IEC_15444_12 "For any media stream for which no segment index is present, referred to as non‐indexed stream, the media stream associated with the first Segment Index box in the segment serves as a reference stream in a sense that it also describes the subsegments for any

Re: [FFmpeg-devel] [PATCH] avcodec/dvdsubdec: Fix off by 1 error

On Wed, Oct 26, 2016 at 12:31:06AM +0200, Michael Niedermayer wrote: > Fixes out of array read > > Found-by: Thomas Garnier using libFuzzer > Signed-off-by: Michael Niedermayer > --- > libavcodec/dvdsubdec.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Wed, Oct 26, 2016 at 06:17:27PM +0200, wm4 wrote: > > With all respect, I find such an argument hardly appropriate for two > > reasons: > > it is formally incorrect (see below), > > it shifts the attention from the functionality/usability to emotionally > > charged aspects like age. > > It's

Re: [FFmpeg-devel] [PATCH] removing comma at final enumeration items to fix pedantic warnings

On Fri, Oct 21, 2016 at 10:32:58AM +0200, Michael Behrisch wrote: > Am 20.10.2016 um 10:00 schrieb Clément Bœsch: > > On Thu, Oct 20, 2016 at 09:55:17AM +0200, Nicolas George wrote: > >> Le nonidi 29 vendémiaire, an CCXXV, Clement Boesch a écrit : > >>> it's really a trivial and harmless patch. >

[FFmpeg-devel] [PATCH] lavf/mov.c: Use the first sidx for tracks without sidx.

According to spec ISO_IEC_15444_12 "For any media stream for which no segment index is present, referred to as non‐indexed stream, the media stream associated with the first Segment Index box in the segment serves as a reference stream in a sense that it also describes the subsegments for any

Re: [FFmpeg-devel] [PATCH] avformat/isom: Fix old API regression with exporting max bitrate

On Mon, Oct 10, 2016 at 02:36:37AM +0200, Michael Niedermayer wrote: > Signed-off-by: Michael Niedermayer > --- > libavformat/isom.c | 11 --- > 1 file changed, 8 insertions(+), 3 deletions(-) applied [...] -- Michael GnuPG fingerprint:

Re: [FFmpeg-devel] FFmpeg 3.2

On Wed, Oct 26, 2016 at 05:07:44PM +0200, Carl Eugen Hoyos wrote: > 2016-10-26 1:32 GMT+02:00 Michael Niedermayer : > > On Wed, Sep 28, 2016 at 05:11:23PM +0200, Carl Eugen Hoyos wrote: > >> 2016-09-27 15:30 GMT+02:00 Michael Niedermayer : > >> > >>

Re: [FFmpeg-devel] [PATCH 01/12] adxdec: validate sample_rate

On 10/25/16, Michael Niedermayer wrote: > On Tue, Oct 25, 2016 at 07:45:25PM +0200, Andreas Cadhalpun wrote: >> On 25.10.2016 12:58, Paul B Mahol wrote: >> > patch(es)have good intent, but better fix is doing/checking it in single >> > place. >> >> I don't agree. >> In

Re: [FFmpeg-devel] [PATCH] avformat/utils: Discard huge timestamps which would cause overflows if used in basic computations

On Sun, Sep 25, 2016 at 11:54:00PM +0200, Michael Niedermayer wrote: > Allowing larger timestamps makes it impossible to calculate basic things like > the > difference of 2 timestamps or their sum without checking each individual > computation for > overflow. > This should avoid a significant

Re: [FFmpeg-devel] [PATCH] doc/patchwork: Document the patchwork states

On Sat, Oct 22, 2016 at 09:20:20PM +0200, Michael Niedermayer wrote: > On Sat, Oct 22, 2016 at 10:41:29AM -0800, Lou Logan wrote: > > On Sat, Oct 22, 2016, at 09:49 AM, Bodecs Bela wrote: > > > > > > under review: someone marked it because he/she investigate this patch. > > > So the patch

[FFmpeg-devel] [PATCH] lavf/mov.c: Set duration to zero if the duration is UINT_MAX

Fixes some MP4F files which have duration in mdhd set to UINT_MAX instead of zero. Signed-off-by: Sasi Inguva --- libavformat/mov.c | 5 + 1 file changed, 5 insertions(+) diff --git a/libavformat/mov.c b/libavformat/mov.c index 357d800..245e424 100644 ---

[FFmpeg-devel] [PATCH 05/10] crystalhd: We don't need the track the last picture number anymore

This was needed to detect an interlaced failure case that doesn't happen with the new decode api. Signed-off-by: Philip Langdale --- libavcodec/crystalhd.c | 40 1 file changed, 40 deletions(-) diff --git a/libavcodec/crystalhd.c

[FFmpeg-devel] [PATCH 4/4] qsv: Merge libav implementation

Merged as-at libav 398f015, and therefore includes outstanding skipped merges 04b17ff and 130e1f1. All features not in libav are preserved, and no options change. --- v3. Changes from v2: - Profile seems to be required by the decoder in some cases; always pass in the correct value. - Fix

Re: [FFmpeg-devel] [PATCH 01/12] adxdec: validate sample_rate

On 26.10.2016 20:15, Paul B Mahol wrote: > On 10/25/16, Michael Niedermayer wrote: >> On Tue, Oct 25, 2016 at 07:45:25PM +0200, Andreas Cadhalpun wrote: >>> On 25.10.2016 12:58, Paul B Mahol wrote: patch(es)have good intent, but better fix is doing/checking it in

[FFmpeg-devel] [PATCH 06/10] crystalhd: Remove h.264 parser

Now that we don't need to do ridiculous things to work out if a frame is interlaced or not, we don't need an extra h.264 parser. Signed-off-by: Philip Langdale --- libavcodec/crystalhd.c | 55 -- 1 file changed, 4 insertions(+),

[FFmpeg-devel] [PATCH 2/4] hevc: Return stream format information from parser

--- libavcodec/hevc_parser.c | 8 1 file changed, 8 insertions(+) diff --git a/libavcodec/hevc_parser.c b/libavcodec/hevc_parser.c index d93586b..508f22f 100644 --- a/libavcodec/hevc_parser.c +++ b/libavcodec/hevc_parser.c @@ -312,6 +312,14 @@ static inline int

[FFmpeg-devel] [PATCH 10/10] crystalhd: Update high level description

We don't need to document the horrible hacks that we removed. Signed-off-by: Philip Langdale --- libavcodec/crystalhd.c | 38 +- 1 file changed, 5 insertions(+), 33 deletions(-) diff --git a/libavcodec/crystalhd.c b/libavcodec/crystalhd.c

[FFmpeg-devel] [PATCH 00/10] crystalhd: Move to new decode API

The CrystalHD hardware decoder is an excellent example of something that was ill-suited to the old 1:1 decode API. I had to put in a ton of fragile heuristics and sleep()s to make it mostly work. By switching to the new m:n decode API, all that crap can get tossed out, and things actually look

[FFmpeg-devel] [PATCH 3/4] mpeg2video: Return correct coded frame sizes from parser

--- libavcodec/mpegvideo_parser.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/libavcodec/mpegvideo_parser.c b/libavcodec/mpegvideo_parser.c index 206f268..de70cd5 100644 --- a/libavcodec/mpegvideo_parser.c +++ b/libavcodec/mpegvideo_parser.c @@ -168,8 +168,10 @@

Re: [FFmpeg-devel] [OPW] OPW Project Proposal

I mean deciding a timeline for the opw project. Which is to be mentioned in application On Wed, Oct 26, 2016 at 6:01 PM, Michael Niedermayer wrote: > Hi > > On Mon, Oct 17, 2016 at 02:06:26PM +0530, Pallavi Kumari wrote: > > Hi Michael, > > > > I figured out the use of

Re: [FFmpeg-devel] [PATCH] avformat: close parser if codec changed

On 22.10.2016 01:16, Andreas Cadhalpun wrote: > From 9de87a4fb2c6c6311a11a2da5de8554a71adfa66 Mon Sep 17 00:00:00 2001 > From: Andreas Cadhalpun > Date: Mon, 17 Oct 2016 20:26:51 +0200 > Subject: [PATCH] avformat: close parser if codec changed > > The parser

Re: [FFmpeg-devel] FFmpeg 3.2

On 2016-10-26 15:29, Michael Niedermayer wrote: > release/3.2 branched > > ill make the 3.2 release tomorrow from release/3.2 > so if anyone wants to backport something, you have till then ffserver is still in that branch. I thought it would be removed from the repo and the configure script. Or

Re: [FFmpeg-devel] [PATCH] configure: make sure LTO does not optimize out the test functions

On 26.10.2016 10:52, Carl Eugen Hoyos wrote: > 2016-10-26 1:16 GMT+02:00 Andreas Cadhalpun > : >> I'm under the impression that __attribute__((used)) is not available >> for all compilers, > Yes, but __attribute__((foo_bar)) does not break compilation here.

[FFmpeg-devel] [PATCH 1/4] vc1: Return stream format information from parser

--- libavcodec/vc1_parser.c | 8 1 file changed, 8 insertions(+) diff --git a/libavcodec/vc1_parser.c b/libavcodec/vc1_parser.c index 9ca6154..bb54947 100644 --- a/libavcodec/vc1_parser.c +++ b/libavcodec/vc1_parser.c @@ -115,6 +115,14 @@ static void

[FFmpeg-devel] [PATCH 02/10] crystalhd: Switch to new decode API and remove the insanity

The new decode API allows for m:n decode patterns, which is what you need to use this hardware in a sane way. There are so many situations where 1:1 doesn't happen naturally that it's a miracle I got it working as well as I did. With this change, we can throw all of the crazy heuristics and

[FFmpeg-devel] [PATCH 01/10] crystalhd: Fix up the missing first sample

Why on earth the hardware returns garbage for the first sample of a decoded picture is anyone's guess. The simplest reasonable way to patch it up is to copy the first sample of the second line. This should result in the correct chroma values (because the data was original 4:2:0 upsampled to 4:2:2)

[FFmpeg-devel] [PATCH 09/10] crystalhd: Simplify output frame handling

The old code had to retain a partial frame across two calls in the case of separate interlaced fields. Now, we know that we'll get both fields within the same receive_frame call, and so we don't need to manage the frame as private state any more. Signed-off-by: Philip Langdale

[FFmpeg-devel] [PATCH 04/10] crystalhd: Remove trust_interlaced heuristic

It seems that without all the other 1:1 heuristics, we don't have a fundamental problem trusting the interlaced flag on output pictures. That's a relief. Signed-off-by: Philip Langdale --- libavcodec/crystalhd.c | 37 - 1 file changed, 4

[FFmpeg-devel] [PATCH 08/10] crystalhd: Loop for a frame internally where possible.

It's not possible to return EAGAIN when we've passed input EOF and are in draining mode. If do return EAGAIN, we're saying there's no way to get any more output - which isn't true in many cases. So let's handled these cases in an internal loop as best we can. Signed-off-by: Philip Langdale

[FFmpeg-devel] [PATCH 03/10] crystalhd: Revert back to letting hardware handle packed b-frames

I'm not sure why, but the mpeg4_unpack_bframes bsf is not interacting well with seeking. Looking at the code, it should be ok, with possibly one warning shown, but I see it getting stuck for an extended period of time after a seek where a packed frame is cached to be shown later. So, I gave up on

Re: [FFmpeg-devel] [PATCH] avformat/matroskaenc: fix cue relative position values when CRC32 is enabled

On 10/25/2016 12:38 PM, James Almer wrote: > The dynamic buffer does not contain the CRC32 element so calls to avio_tell() > don't take it into account. This resulted in CueRelativePosition values being > six bytes short. > This is a regression since 6724525a1576ca334d2ffdc085620bb44aea7394

[FFmpeg-devel] [PATCH 07/10] crystalhd: Keep NOPTS_VALUE so we know it's not there.

Signed-off-by: Philip Langdale --- libavcodec/crystalhd.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/libavcodec/crystalhd.c b/libavcodec/crystalhd.c index b68701a..4ac138c 100644 --- a/libavcodec/crystalhd.c +++ b/libavcodec/crystalhd.c @@ -848,8

Re: [FFmpeg-devel] [PATCH] configure: make sure LTO does not optimize out the test functions

2016-10-26 1:16 GMT+02:00 Andreas Cadhalpun : > On 25.10.2016 23:34, Carl Eugen Hoyos wrote: >> 2016-10-25 19:19 GMT+02:00 Andreas Cadhalpun >> : >> >>> +# LTO could optimize out the test functions without this >>> +

Re: [FFmpeg-devel] [PATCH] configure: make sure LTO does not optimize out the test functions

2016-10-26 1:35 GMT+02:00 Andreas Cadhalpun : > I forgot to include stdint.h. Fixed patch attached. Why don't you cast to (int)? Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] libavcodec/tests: Added test for libavcodec/avpacket.c

On Wed, Oct 26, 2016 at 02:00:46PM +0200, wm4 wrote: > On Sat, 22 Oct 2016 23:40:42 -0700 > Thomas Turner wrote: > > > Function(s) Tested: av_packet_clone(). > > > > This test checks if av_packet_clone() can successfully make a copy of an > > AVPacket. > > Compares

Re: [FFmpeg-devel] [PATCH] libavcodec/tests: Added test for libavcodec/avpacket.c

On Wed, 26 Oct 2016 14:56:01 +0200 Michael Niedermayer wrote: > On Wed, Oct 26, 2016 at 02:00:46PM +0200, wm4 wrote: > > On Sat, 22 Oct 2016 23:40:42 -0700 > > Thomas Turner wrote: > > > > > Function(s) Tested: av_packet_clone(). > > > > > >

Re: [FFmpeg-devel] [PATCH] libavcodec/tests: Added test for libavcodec/avpacket.c

On Sat, 22 Oct 2016 23:40:42 -0700 Thomas Turner wrote: > Function(s) Tested: av_packet_clone(). > > This test checks if av_packet_clone() can successfully make a copy of an > AVPacket. > Compares all data members in AVPacket EXCEPT for "buf" because "buf" is >

Re: [FFmpeg-devel] FFmpeg 3.2

On 10/26/2016 5:44 PM, d...@dericed.com wrote: > >> On Oct 26, 2016, at 3:29 PM, Michael Niedermayer >> wrote: >> >> On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote: >>> Hi all >>> >>> Its long since FFmpeg 3.1, so its time to make 3.2 >>> ill branch

Re: [FFmpeg-devel] FFmpeg 3.2

> On Oct 26, 2016, at 4:44 PM, d...@dericed.com wrote: > > >> On Oct 26, 2016, at 3:29 PM, Michael Niedermayer > > wrote: >> >> On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote: >>> Hi all >>> >>> Its long since

Re: [FFmpeg-devel] [PATCH] lavf: add ffprobe demuxer

On Wed, 26 Oct 2016 01:46:35 +0200 Michael Niedermayer wrote: > On Tue, Oct 25, 2016 at 05:07:34PM +0200, Stefano Sabatini wrote: > > On date Tuesday 2016-10-18 16:06:47 +0200, Michael Niedermayer encoded: > > > On Tue, Oct 18, 2016 at 01:33:27PM +0200, Stefano Sabatini

Re: [FFmpeg-devel] [OPW] OPW Project Proposal

Hi On Mon, Oct 17, 2016 at 02:06:26PM +0530, Pallavi Kumari wrote: > Hi Michael, > > I figured out the use of fft. Help me with the time line setting. Thanks I dont understand the question, if its about AVFILTER_FLAG_SUPPORT_TIMELINE*, please ignore this for now, its not needed [...] --

Re: [FFmpeg-devel] [PATCH] configure: make sure LTO does not optimize out the test functions

On Wed, Oct 26, 2016 at 10:57 PM, Carl Eugen Hoyos wrote: > 2016-10-26 21:36 GMT+02:00 Andreas Cadhalpun > : >> On 26.10.2016 10:52, Carl Eugen Hoyos wrote: >>> 2016-10-26 1:16 GMT+02:00 Andreas Cadhalpun >>>

Re: [FFmpeg-devel] FFmpeg 3.2

On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote: > Hi all > > Its long since FFmpeg 3.1, so its time to make 3.2 > ill branch release/3.2 off master and make 3.2 in maybe about a week or > 2 unless something delays it release/3.2 branched ill make the 3.2 release tomorrow

Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer

On 10/26/2016 6:19 PM, Rostislav Pehlivanov wrote: > Also removes url_feof from libavformat.v which should have been > removed long ago and changed the multipart jpeg boundary tag to > ffmpeg rather than ffserver (it's arbitrary). [...] > diff --git a/libavformat/libavformat.v

Re: [FFmpeg-devel] FFmpeg 3.2

> On Oct 26, 2016, at 3:29 PM, Michael Niedermayer > wrote: > > On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote: >> Hi all >> >> Its long since FFmpeg 3.1, so its time to make 3.2 >> ill branch release/3.2 off master and make 3.2 in maybe about a

Re: [FFmpeg-devel] [PATCH] libavcodec/tests: Added test for libavcodec/avpacket.c

On Wed, Oct 26, 2016 at 03:03:07PM +0200, wm4 wrote: > On Wed, 26 Oct 2016 14:56:01 +0200 > Michael Niedermayer wrote: > > > On Wed, Oct 26, 2016 at 02:00:46PM +0200, wm4 wrote: > > > On Sat, 22 Oct 2016 23:40:42 -0700 > > > Thomas Turner wrote:

Re: [FFmpeg-devel] [PATCH 09/13] avcodec/svq1dec: clear MMX state after MB decode loop

On Tue, Oct 25, 2016 at 12:00:01AM +0200, Hendrik Leppkes wrote: > On Mon, Oct 24, 2016 at 10:31 PM, Ronald S. Bultje wrote: > > Hi, > > > > On Mon, Oct 24, 2016 at 4:26 PM, Henrik Gramner wrote: > > > >> On Mon, Oct 24, 2016 at 9:59 PM, Ronald S. Bultje

Re: [FFmpeg-devel] FFmpeg 3.2

On 10/26/2016 3:29 PM, Michael Niedermayer wrote: On Tue, Sep 27, 2016 at 03:30:03PM +0200, Michael Niedermayer wrote: Hi all Its long since FFmpeg 3.1, so its time to make 3.2 ill branch release/3.2 off master and make 3.2 in maybe about a week or 2 unless something delays it release/3.2

Re: [FFmpeg-devel] [PATCH] configure: make sure LTO does not optimize out the test functions

On 26.10.2016 22:57, Carl Eugen Hoyos wrote: > 2016-10-26 21:36 GMT+02:00 Andreas Cadhalpun > : >> On 26.10.2016 10:52, Carl Eugen Hoyos wrote: >>> 2016-10-26 1:16 GMT+02:00 Andreas Cadhalpun >>> : I'm under the impression

Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer

On 27.10.2016 00:16, Rostislav Pehlivanov wrote: > On 26 October 2016 at 22:48, James Almer wrote: > >> On 10/26/2016 6:19 PM, Rostislav Pehlivanov wrote: >>> Also removes url_feof from libavformat.v which should have been >>> removed long ago and changed the multipart jpeg

Re: [FFmpeg-devel] [OPW] OPW Project Proposal

On Thu, Oct 27, 2016 at 12:40:53AM +0530, Pallavi Kumari wrote: > I mean deciding a timeline for the opw project. Which is to be mentioned in > application its your application, you can choose whatever timeline you feel makes sense. As far as iam concered whats important is to finish the

Re: [FFmpeg-devel] [PATCH] configure: make sure LTO does not optimize out the test functions

2016-10-26 21:36 GMT+02:00 Andreas Cadhalpun : > On 26.10.2016 10:52, Carl Eugen Hoyos wrote: >> 2016-10-26 1:16 GMT+02:00 Andreas Cadhalpun >> : >>> I'm under the impression that __attribute__((used)) is not available >>> for

Re: [FFmpeg-devel] [PATCH] lavf/mov.c: Use the first sidx for tracks without sidx.

sorry. forgot to remove the debug printf. sending the corrected patch. On Wed, Oct 26, 2016 at 7:47 AM, Michael Niedermayer wrote: > On Tue, Oct 25, 2016 at 11:07:58PM -0700, Sasi Inguva wrote: > > According to spec ISO_IEC_15444_12 "For any media stream for which no >