Re: [FFmpeg-devel] [PATCH] lavf/avisynth: fix compilation, remove bundled headers

On Wed, Mar 25, 2015 at 7:50 PM, Michael Niedermayer michae...@gmx.at wrote: On Wed, Mar 25, 2015 at 01:59:18PM -0400, Stephen Hutchinson wrote: On Wed, Mar 25, 2015 at 12:49 PM, Michael Niedermayer michae...@gmx.at wrote: ive applied patch 4 from the patchset too, does that fix it ?

Re: [FFmpeg-devel] [PATCH 2/4] avisynth: drop support of AviSynth 2.5

On Tue, Mar 24, 2015 at 7:33 PM, Hendrik Leppkes h.lepp...@gmail.com wrote: On Tue, Mar 24, 2015 at 8:23 PM, Stephen Hutchinson qyo...@gmail.com wrote: If the user attempts to use AviSynth 2.5, an error message will now tell them they need to upgrade. Just had avisynth.c fail to compile

Re: [FFmpeg-devel] [PATCH] lavf/avisynth: fix compilation, remove bundled headers

On Wed, Mar 25, 2015 at 7:50 PM, Michael Niedermayer michae...@gmx.at wrote: On Wed, Mar 25, 2015 at 01:59:18PM -0400, Stephen Hutchinson wrote: On Wed, Mar 25, 2015 at 12:49 PM, Michael Niedermayer michae...@gmx.at wrote: ive applied patch 4 from the patchset too, does that fix it ?

Re: [FFmpeg-devel] [PATCH 0/4] more accurate constants

On Fri, Nov 13, 2015 at 4:42 PM, Ganesh Ajjanagadde wrote: > > 4/4 is a "best effort" patch that maximizes accuracy on all platforms for > avcodec/faandct. It results in concrete accuracy benefits on the "default" > x86-64 > GNU/Linux platform. > > Patches tested with

Re: [FFmpeg-devel] [PATCH 0/4] more accurate constants

On Thu, Nov 26, 2015 at 1:26 PM, Ganesh Ajjanagadde wrote: >> Does removing the L fix it? > Read up a bit and suspect it should, and more generally long double is > a can of worms on ppc with bugs on some compilers: > https://gcc.gnu.org/wiki/Ieee128PowerPC, ABI in transition,

[FFmpeg-devel] Avid DNxHR / UK DPP

Tomorrow I'm attending an event run by the Digital Production Partnership, a body that has brought together mainstream digital television delivery and workflow standards for UK broadcasters. My production company is a member, and we assisted a little in the development of their UHD workflow

Re: [FFmpeg-devel] Avid DNxHR / UK DPP

On 25 Jan 2016 23:04, "Kieran Kunhya" wrote: > > If they are considering VC-5 (Cineform) basically point them to this: > https://medium.com/@kierank_/reverse-engineering-the-gopro-cineform-codec-7411312bfe1c > > tl;dr The VC-5 document isn't enough to implement things in

Re: [FFmpeg-devel] Avid DNxHR / UK DPP

Gentlemen, I'm at DPP conference, in the room. Start of UHD delivery standards for UK just announced. Now on website, we are told. H.264 codec, AS-11 encapsulation for MXF, HLG and SMPTE 2084 both supported for HDR, WCG framework supported, Long-GOP in H.264. But I-frame only option for

Re: [FFmpeg-devel] [PATCH] lavc/hevc_parse: Don't take a HEVCContext

Is it possible that this patch, particularly to libavcodec/hevc.h, is causing my compilation error today, cross-compiling using mingw-w64 and gcc-5.3.0 from GNU/Linux to Windows 64-bit? libavcodec/qsvenc_hevc.c: In function 'generate_fake_vps': libavcodec/qsvenc_hevc.c:71:38: warning: passing

Re: [FFmpeg-devel] order T-shirts

On Sun, Sep 4, 2016 at 10:34 PM, Thomas Volkert wrote: > Hi, > > Some guys at the VDD asked for FFmpeg T-shirts. > I'd like to do a new T-shirt order. The shirts could be given to > multimedia devs who stop at one of our next booths. > > ​I'd *buy* one. XL. Wear it at the lectures

Re: [FFmpeg-devel] [PATCH] lavfi/af_ebur128: update filter to use new ebur128 API

On Thu, Nov 17, 2016 at 5:04 PM, Kyle Swanson wrote: > Hi, > > Here's a couple of patches which update the ebur128 filter to use the > recently added ebur128 API. This updated filter allows fine-tuned > control over which EBU R128 parameters are measured, and provides > modest speed

[FFmpeg-devel] Patch: filter af_amix inputs

f-stream.", OFFSET(duration_mode), AV_OPT_TYPE_INT, { .i64 = DURATION_LONGEST }, 0, 2, A|F, "duration" }, { "longest", "Duration of longest input.", 0, AV_OPT_TYPE_CONST, { .i64 = DURATION_LONGEST }, INT_MIN, INT_MAX, A|F, "duration" }, -

Re: [FFmpeg-devel] Patch: filter af_amix inputs

On Fri, Apr 7, 2017 at 10:25 AM, Michael Niedermayer <mich...@niedermayer.cc> wrote: > > this patch is corrupted by linebreaks I'm sorry about that. It's attached to this email, from a file made by git format-patch. J -- John Warburton Tonmeister, Director, Associate Lecturer

Re: [FFmpeg-devel] [PATCHv2 1/2] avdevice/decklink_dec: add support for decoding teletext from 10bit ancillary data

(.rdata$.refptr.ff_reverse[.refptr.ff_reverse]+0x0): undefined reference to `ff_reverse' collect2: error: ld returned 1 exit status ffbuild/library.mak:101: recipe for target 'libavdevice/avdevice-57.dll' failed make: *** [libavdevice/avdevice-57.dll] Error 1 Build

Re: [FFmpeg-devel] [PATCH 7/7] lavfi/vf_stack: move to activate design.

On Mon, Aug 7, 2017 at 10:08 AM, Nicolas George wrote: > > This issue seems fixed by these changes: > > https://ffmpeg.org/pipermail/ffmpeg-devel/2017-July/214306.html > ... > Also, it would help deciding stuff if you, as a user, told us: if you > had to write

Re: [FFmpeg-devel] [PATCH 7/7] lavfi/vf_stack: move to activate design.

On Sun, Aug 6, 2017 at 4:39 PM, Gyan wrote: > Is ticket #6566 also related? This test case on ticket #6566 indeed freezes during the overlay on my patched FFmpeg with the alteration to libav/vf_stack.c taken out. I have not been able to test it in another way yet. Kind

Re: [FFmpeg-devel] [PATCH 7/7] lavfi/vf_stack: move to activate design.

On Mon, Jul 17, 2017 at 3:19 PM, Nicolas George wrote: > > Signed-off-by: Nicolas George > --- > libavfilter/Makefile | 4 ++-- > libavfilter/vf_stack.c | 32 +--- > 2 files changed, 15 insertions(+), 21 deletions(-) > > > Works

Re: [FFmpeg-devel] [PATCH 7/7] lavfi/vf_stack: move to activate design.

On Mon, Aug 7, 2017 at 10:08 AM, Nicolas George wrote: > > This issue seems fixed by these changes: > > https://ffmpeg.org/pipermail/ffmpeg-devel/2017-July/214306.html > > I thought it could only be triggered with the specific configuration > caused by dualinput, but you

Re: [FFmpeg-devel] [PATCH] doc/filters: document the unstability of the shorthand options notation.

On Mon, Aug 7, 2017 at 10:03 AM, Nicolas George wrote: >> >Lets take a step back and look at this >> > >> >There are some rarely used options in multi input filters like >> >overlay which break. >> >Noone even noticed except me ... > Now, to all that stated a negative opinion

Re: [FFmpeg-devel] [DECISION] scaletempo filter

On Sat, May 4, 2019 at 2:41 PM Nicolas George wrote: > Paul B Mahol (12019-05-04): > > I open votes for 7 days. Voting is about inclusion of scaletempo > > filter (IMHO it is better than atempo) in FFmpeg. > > > > Thanks for voting. > > Voting for what? This mail does not look remotely like the

Re: [FFmpeg-devel] [DECISION] scaletempo filter

On Sat, May 4, 2019 at 3:34 PM Nicolas George wrote: > John Warburton (12019-05-04): > > > Is there a patch I can use to test scaletempo to compare it against > atempo? > > It'll be no trouble to do that with the normal audio that is > time-adjusted > > on that rad