[FFmpeg-devel] New active mailing list maintainer needed

Would any developer like to volunteer to take care of the mailing lists? I'm retiring from it. Here are the usual tasks: * Clear the ffmpeg-devel moderation ideally on a daily basis. It isn't time consuming but involves approving legit messages/patches (first check to see if it is not a

Re: [FFmpeg-devel] Blackfin optimizations

On Wed, Feb 27, 2019, at 10:03 AM, Michael Noel wrote: > Hello, > > Can you pls. send me more details about the Blackfin optimizisations for > the ffmpeg? > > Thanks > Miki Blackfin optimization was removed from the ffmpeg years ago:

Re: [FFmpeg-devel] [PATCH] doc: add missing hyphen prefix

On Fri, Feb 22, 2019, at 4:57 AM, Nicolas George wrote: > > That would be an argument for using something way more specific than a > dash. Like what? Do you have an example? > Anyway, that kind of marking would belong in the definition of the macro > @option, not in the body of the

Re: [FFmpeg-devel] [PATCH] doc: add missing hyphen prefix

On Fri, Feb 22, 2019, at 4:21 AM, Nicolas George wrote: > > There are other users than API and command-line. Think of a GUI that > presents all options as editable fields. That seems like an empty argument. Which GUI? Do you have an example? I don't see how some unnamed third-party GUI should

Re: [FFmpeg-devel] [PATCH] doc: add missing hyphen prefix

On Fri, Feb 22, 2019, at 2:29 AM, Nicolas George wrote: > > I do not think this is correct: the dash is not part of the option name, > it is part of the Unix command-line tradition. For consistency, it > should be removed when it is there, possibly replaced by the word > "option" if necessary. I

Re: [FFmpeg-devel] dav1d support

On Wed, Feb 20, 2019, at 3:39 PM, Patel, Dhaval R wrote: > > Does anyone aware about targeted dates for Release 4.2 ? No, but if it follows the trend of the last 5 releases it will be about 6 months from the last release, so my guess is in May or June.

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

On Wed, Feb 6, 2019, at 11:48 AM, Werner Robitza wrote: > > I propose that FFmpeg maintains its own ffmpeg formula under its > GitHub organization at github.com/ffmpeg/homebrew-ffmpeg (or similar). > This will ensure that there's one formula users will discover when > they look for an alternative

Re: [FFmpeg-devel] [PATCH 1/4] doc/formats: add reference to ffmpeg(1) stream specifiers as that docs is more complete

On Sun, Feb 17, 2019, at 10:58 AM, Marton Balint wrote: > Signed-off-by: Marton Balint > --- > doc/formats.texi | 24 ++-- LGTM ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [Patch] lavf/mpeg: fix indent

On Sun, Feb 17, 2019, at 4:56 PM, Morris Stock wrote: > > Ah, yes, but seems no one else use short name, see new attachment, thanks. You can use whatever name or alias you want. We only want consistency, so future patches from the same address should ideally have the same author name.

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: Lo

[FFmpeg-devel] [PATCH] web/generate-doc: replace yasm with x86asm

Signed-off-by: Lou Logan --- generate-doc.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/generate-doc.sh b/generate-doc.sh index d8d01d3..4555a35 100755 --- a/generate-doc.sh +++ b/generate-doc.sh @@ -34,9 +34,9 @@ export FA_ICONS=true rm -rf build-doc mkdir build

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

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 --- src/documentation | 3 --- 1 file changed, 3 deletions(-) diff --git a/src

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

On Fri, Feb 8, 2019, at 11:27 AM, Jean-Baptiste Kempf wrote: > > Also, the AUR recipe does not push for non-free packages. The proposed homebrew formulae will not push for non-free packages. It will simply provide the options for the user to enable two non-free components (openssh and fdk-aac

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

On Fri, Feb 8, 2019, at 12:03 AM, Jean-Baptiste Kempf wrote: > > Helping people to build non-free distributions of FFmpeg is a very weird > and dubious goal. > This is just helping other people violate the FFmpeg license. You could say the same thing for other build scripts such as the AUR for

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

On Thu, Feb 7, 2019, at 12:49 PM, Carl Eugen Hoyos wrote: > > This sounds like a strong reason not to add it to an FFmpeg > repository: It was claimed in the past that I am the only one > not supporting releases but the same was now repeated by > other developers. We can simply provide a note

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

On Thu, Feb 7, 2019, at 8:28 AM, Derek Buitenhuis wrote: > > I haven't seen anyone object to hosting it as a separate repo on our infra, > but I also didn't see anyone who maintains our infra reply... maybe Michael > has opinions. I'm not against it. Seems like it will be helpful to users and I'm

Re: [FFmpeg-devel] [PATCH] doc: fix various typos

On Thu, Jan 31, 2019, at 2:23 PM, Moritz Barsnick wrote: > Found with the help of codespell-1.14.0. > > Signed-off-by: Moritz Barsnick > --- > doc/bitstream_filters.texi | 2 +- > doc/codecs.texi| 2 +- > doc/filters.texi | 24 > doc/formats.texi

Re: [FFmpeg-devel] [PATCH] Fix Markdown formatting

On Thu, 31 Jan 2019 11:46:49 -0500 Justin Bull wrote: > --- > INSTALL.md | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/INSTALL.md b/INSTALL.md > index 5db912231c..3b220bc6ff 100644 > --- a/INSTALL.md > +++ b/INSTALL.md > @@ -1,4 +1,4 @@ > -#Installing FFmpeg: > +##

Re: [FFmpeg-devel] [PATCH] web/consulting: add myself

On Thu, 31 Jan 2019 21:57:38 +0530 Gyan wrote: > From a03e88da9deb21b800714b695b4d99edb54397ff Mon Sep 17 00:00:00 2001 > From: Gyan Doshi > Date: Thu, 31 Jan 2019 21:44:19 +0530 > Subject: [PATCH] web/consulting: add myself > > Signed-off-by: Gyan Doshi > --- > src/consulting | 13

Re: [FFmpeg-devel] [PATCH] img2enc: mention -frames:v in error message

On Tue, Jan 15, 2019, at 10:54 PM, Kieran O Leary wrote: > > Looks good to me. Thanks. Pushed with fixed subject prefix. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] img2enc: mention -frames:v in error message

Signed-off-by: Lou Logan --- libavformat/img2enc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/libavformat/img2enc.c b/libavformat/img2enc.c index a09cc8ec50..bec4bf81dd 100644 --- a/libavformat/img2enc.c +++ b/libavformat/img2enc.c @@ -110,7 +110,8 @@ static int

Re: [FFmpeg-devel] [PATCH] doc/developer: require transparency about sponshorships.

On Fri, Jan 11, 2019, at 9:21 AM, Nicolas George wrote: > > Signed-off-by: Nicolas George > --- > doc/developer.texi | 10 ++ > 1 file changed, 10 insertions(+) I am against this and completely agree with Derek and Kyle. ___ ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 01/11] doc/indevs: fix upto typo

On Mon, Dec 31, 2018, at 12:03 PM, Michael Niedermayer wrote: > Signed-off-by: Michael Niedermayer > --- > doc/indevs.texi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Ok. Same typo is in compat/avisynth/avisynth_c.h. ___ ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 3/6] avcodec/qsvenc: Fix Unkown typo

On Fri, Dec 28, 2018, at 12:35 PM, Lou Logan wrote: > > OK, of course. Same for patch 2/6. No need to submit patches for simple typos. ...also 1/6. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 3/6] avcodec/qsvenc: Fix Unkown typo

On Fri, Dec 28, 2018, at 12:22 PM, Michael Niedermayer wrote: > Signed-off-by: Michael Niedermayer > --- > libavcodec/qsvenc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavcodec/qsvenc.c b/libavcodec/qsvenc.c > index 70772dc0e2..56a3756357 100644 > ---

Re: [FFmpeg-devel] [PATCH] web/(old)download: Move 3.0 to olddownloads

On Mon, Dec 3, 2018, at 10:19 AM, Lou Logan wrote: > No current downstream appears to be using 3.0: > https://trac.ffmpeg.org/wiki/Downstreams > > Signed-off-by: Lou Logan > --- > src/download| 39 --- >

Re: [FFmpeg-devel] [PATCH] fix infinite retry issue for rtsp when the uri has redirection

On Thu, Dec 13, 2018, at 3:19 PM, tianhu yang wrote: > --- > libavformat/rtsp.c | 1 + > 1 file changed, 1 insertion(+) Thank you for the patch, but it does not apply. Please create patches with "git format-patch" or "git send-email", and provide a commit message.

[FFmpeg-devel] [PATCH] web/(old)download: Move 3.0 to olddownloads

No current downstream appears to be using 3.0: https://trac.ffmpeg.org/wiki/Downstreams Signed-off-by: Lou Logan --- src/download| 39 --- src/olddownload | 37 + 2 files changed, 37 insertions(+), 39 deletions(-) diff

Re: [FFmpeg-devel] [PATCH 3/4] doc/filters: add tonemap_opencl document.

On Mon, Oct 29, 2018, at 9:31 PM, Gyan wrote: > > LGTM. Pushed. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/4] doc/filters: add document for opencl filters

On Sat, Nov 3, 2018, at 8:31 AM, Lou Logan wrote: > On Thu, Nov 1, 2018, at 9:13 PM, Gyan wrote: > > Sure, but I may not get to it until Monday. Pushed. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listin

Re: [FFmpeg-devel] [PATCH 1/4] doc/filters: add document for opencl filters

On Thu, Nov 1, 2018, at 9:13 PM, Gyan wrote: > > Lou, can you push this? Won't have my comp with the repo credentials for > some time. Sure, but I may not get to it until Monday. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH v2] web/documentation: add new book about FFmpeg in China

On Wed, Oct 17, 2018, at 3:40 PM, Steven Liu wrote: > Signed-off-by: Steven Liu > --- > src/documentation | 2 ++ > 1 file changed, 2 insertions(+) Pushed. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] avfilter: add (a)graphmonitor filter(s)

On Tue, Oct 30, 2018, at 12:30 PM, Paul B Mahol wrote: > > Will apply soon. Are you going to add any documentation? ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] doc/hls: fix grammar for HLS options

On Tue, 30 Oct 2018 21:07:16 +0100 Werner Robitza wrote: > From 7da20791b3d146e49855f975c8b5102e8cbfd9f2 Mon Sep 17 00:00:00 2001 > From: Werner Robitza > Date: Tue, 30 Oct 2018 20:22:55 +0100 > Subject: [PATCH] doc/hls: fix grammar for HLS options > > This fixes the grammar of two HLS option

Re: [FFmpeg-devel] [PATCH] avfilter: add xstack filter

On Wed, Oct 24, 2018, at 11:04 AM, Paul B Mahol wrote: > Signed-off-by: Paul B Mahol > --- > doc/filters.texi | 45 > libavfilter/Makefile | 1 + > libavfilter/allfilters.c | 1 + > libavfilter/vf_stack.c | 151 --- > 4 files

Re: [FFmpeg-devel] [PATCH] download: change OS X to macOS

On Tue, Oct 16, 2018, at 4:33 PM, Helmut K. C. Tessarek wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > I've changed the commit message as James suggested. > > Do I have to do anything else to get someone to commit it? I can push this in about a week unless someone else does first.

Re: [FFmpeg-devel] FFmpeg 4.1

On Tue, Sep 25, 2018, at 10:50 AM, Lou Logan wrote: > > The users on Twitter have been asked for their suggestions. Please let > me know a little while before you want to make the release and I'll > post the results here. Results. Number of likes are in parentheses. Multiple sugg

Re: [FFmpeg-devel] FFmpeg 4.1

On Thu, Sep 13, 2018, at 5:22 PM, Michael Niedermayer wrote: > > Are there any suggestions for a name ? The users on Twitter have been asked for their suggestions. Please let me know a little while before you want to make the release and I'll post the results here.

Re: [FFmpeg-devel] h264 decoding question

On Mon, Sep 24, 2018, at 8:43 AM, Jimmy Bhaktha wrote: > Hi > > I am working on an application based on FFMPEG version 3.4.2 where the RTSP > packets from the camera are captured and store using python. The decoder > application is run later. The application receives a byte array which is > the

Re: [FFmpeg-devel] [RFC] Make the user help mailing lists subscription only

On Tue, Jul 17, 2018, at 2:43 PM, Lou Logan wrote: > I'm considering changing the ffmpeg-user and libav-user mailing lists to > only accept messages from subscribed users. Implemented. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.or

Re: [FFmpeg-devel] [RFC] Make the user help mailing lists subscription only

On Wed, Jul 18, 2018, at 3:32 AM, Gyan Doshi wrote: > > What's the volume of messages from non-subscribers relative to subscribers? I'm not sure. I never did keep a running tally. I may be able to figure it out via the logs if I were motivated enough. However, I can provide some limited info

[FFmpeg-devel] [RFC] Make the user help mailing lists subscription only

I'm considering changing the ffmpeg-user and libav-user mailing lists to only accept messages from subscribed users. ffmpeg-devel would be excluded from this due to the higher familiarity of mailing lists with that audience. Currently anyone can send a message to the *-user mailing lists.

Re: [FFmpeg-devel] [GSOC] [PATCH] ESPCN super-resolution

On Tue, Jul 17, 2018, at 11:29 AM, Pedro Arthur wrote: > > It seems gmail just delivered your second patch email from 06/28 today > (delivered after 1670067 seconds), that's why already pushed the first > one and fixed the warnings. It was stuck in the ffmpeg-devel moderation queue due to its

Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg: add option to hide vsync warnings

On Wed, Jun 27, 2018, at 10:00 AM, Marton Balint wrote: > > If we don't know why it spams the console or nobody is willing to fix it, > then decrease loglevel to verbose. I am strongly against adding a command > line option for this. I was just about to give the same suggestion.

Re: [FFmpeg-devel] [PATCH] avdevice/v4l2enc: add video4linux2 name alias

On Thu, Jun 14, 2018, at 1:39 PM, Lou Logan wrote: > Makes v4l2 outdev name consistent with the v4l2 indev. > > Signed-off-by: Lou Logan > --- > libavdevice/v4l2enc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Pushed. __

Re: [FFmpeg-devel] [PATCH] avdevice/v4l2enc: add video4linux2 name alias

On Sun, Jun 17, 2018, at 8:25 AM, Carl Eugen Hoyos wrote: > > Wouldn't it make more sense to remove the extremely > long name at the next bump if consistency is needed > here? I don't think it matters too much to also have the alias video4linux2, or at least I can't think of any good reasons to

Re: [FFmpeg-devel] [PATCH] avdevice/v4l2enc: add video4linux2 name alias

On Thu, Jun 14, 2018, at 1:39 PM, Lou Logan wrote: > Makes v4l2 indev name consistent with the v4l2 indev. Should say: Makes v4l2 outdev name consistent with the v4l2 indev. I changed this locally before sending, but forgot to re-make the updated pa

[FFmpeg-devel] [PATCH] avdevice/v4l2enc: add video4linux2 name alias

Makes v4l2 indev name consistent with the v4l2 indev. Signed-off-by: Lou Logan --- libavdevice/v4l2enc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavdevice/v4l2enc.c b/libavdevice/v4l2enc.c index 85200d0a36..1c36f81f90 100644 --- a/libavdevice/v4l2enc.c +++ b

Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg_opt: Add -toeof option to stop writing relative to EOF

On Mon, Jun 11, 2018, at 1:00 PM, Morten With wrote: > > Also, was this the correct way to send in a revised patch? I'm completely > new to this. Yes, that is acceptable. We are not too picky about that. It can be helpful to rename the subject, such as [PATCH v2], if desired: especially if

Re: [FFmpeg-devel] Atempo limits

On Mon, Jun 4, 2018, at 10:09 AM, Ronak wrote: > > We are looking to use the atempo filter for our audio files. However, > the limit between 0.5 - 2x is too restrictive for us. We would like to > expand the limit to 0.5x - 3x. Consider using the rubberband filter instead if atempo is too simple

Re: [FFmpeg-devel] [PATCH] doc/ffmpeg - rewrite Stream Selection chapter

On Wed, May 30, 2018, at 9:56 PM, Gyan Doshi wrote: > > Can you run this on the server to check if subsubheadings are rendered? I'm fairly confident it will since @subheading also works online for developer.html, but not locally. However, this shouldn't be blocking your patch since it is an

Re: [FFmpeg-devel] [PATCH] doc/ffmpeg - rewrite Stream Selection chapter

On Tue, May 29, 2018, at 9:43 PM, Gyan Doshi wrote: > > They do here. Which version of makeinfo do you have? 6.5 Works when "--init-file=doc/t2h.pm" is omitted. Didn't investigate further. > More importantly, which version is on the project server? 5.2

Re: [FFmpeg-devel] [PATCH] doc/ffmpeg - rewrite Stream Selection chapter

On Sun, 27 May 2018 09:46:46 +0530 Gyan Doshi wrote: > I was talking about the vertical margins appled to the 'code' element. That's ugly too. I removed the margin for the code element. > From 60ed76348e70f1b0a25eadde8d886d47be3fca69 Mon Sep 17 00:00:00 2001 > From: Gyan Doshi > Date: Thu, 24

Re: [FFmpeg-devel] [PATCH] doc/ffmpeg - rewrite Stream Selection chapter

On Sat, May 26, 2018, at 12:33 AM, Gyan Doshi wrote: > > Part of the ugliness is due to how the code fragments are rendered: with > vertical margins, creating uneven line spacing. Do you mind if I reduce > or eliminate those margins? Which file sets those margins? The ugly justified text in the

Re: [FFmpeg-devel] [PATCH] doc/ffmpeg - rewrite Stream Selection chapter

On Thu, 24 May 2018 19:18:50 +0530 Gyan Doshi wrote: > From a7ff32bdac54a1f257482526a507ab7823cafb41 Mon Sep 17 00:00:00 2001 > From: Gyan Doshi > Date: Thu, 24 May 2018 19:11:00 +0530 > Subject: [PATCH] doc/ffmpeg - rewrite Stream Selection chapter Nit:

Re: [FFmpeg-devel] github

On Thu, Apr 26, 2018, at 2:50 PM, wm4 wrote: > > That would mostly get rid of the centralization argument. But I've > heard bad things from someone who wanted to setup a private instance of > it. Apparently it has a large number of dependencies, is extremely hard > to deploy (unless you use their

Re: [FFmpeg-devel] github

On Thu, Apr 26, 2018, at 4:40 AM, wm4 wrote: > > To be fair, I'd prefer the github issue tracker over TRAC any day. At least it isn't Bugzilla. What are some of the problems with trac? Is there a self-hostable bug tracker you prefer? ___ ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add myself to documentation section

On Wed, 11 Apr 2018 21:53:25 +0530 Gyan Doshi wrote: > rom b18cb5bfb7c8df130892f9ec9552287edac2b17a Mon Sep 17 00:00:00 2001 > From: Gyan Doshi > Date: Wed, 11 Apr 2018 21:46:03 +0530 > Subject: [PATCH] MAINTAINERS: add myself to documentation section > >

Re: [FFmpeg-devel] [PATCH v3] doc: update loglevel option documentation

On Tue, Apr 10, 2018, at 11:11 PM, Tobias Rapp wrote: > > BTW: Is there some documentation on the generic flags syntax used in > FFmpeg for options like "-fflags" or "-cpuflags" and how to combine the > tokens with "+" or "-"? I couldn't find something on a quick scan. Doesn't appear to be

Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add myself to documentation section

On Wed, Apr 11, 2018, at 8:23 AM, Gyan Doshi wrote: > As suggested by Lou Logan, this patch adds myself as a docs maintainer. I suggested this because the documentation can always use more improvements, we need more active documentation maintainers, and he has previously shown inter

Re: [FFmpeg-devel] [PATCH] avcodec/dpx: Support for RGB 12-bit packed decoding

On Tue, Apr 10, 2018, at 2:05 PM, Michael Niedermayer wrote: > > what do you mean by "Git and me are not good friends" ? > If git hates you and sometimes does things that you didnt intend at all then > that would be a problem with direct pushes as theres no way to undo. > But maybe i

Re: [FFmpeg-devel] [PATCH v2] doc: update loglevel option documentation

On Mon, Apr 9, 2018, at 10:59 PM, Tobias Rapp wrote: > > +For example to enable repeated log output and set @var{loglevel} to > +@code{verbose}: > +@example > +ffmpeg -loglevel repeat+verbose -i input output > +@end example Just to show all current flags and the loglevel I prefer: For example to

Re: [FFmpeg-devel] Add IRC nicknames to MAINTAINERS?

On Sun, Apr 8, 2018, at 3:05 AM, Tomas Härdin wrote: > > Good suggestion > > /Tomas Patch LGTM with the suggestion from James. Although I'm not on IRC very often lately you can add mine too if you feel like it: llogan. ___ ffmpeg-devel mailing list

Re: [FFmpeg-devel] [PATCH] doc/developer: remove merge request method of contributing

On Thu, Apr 5, 2018, at 10:17 AM, Lou Logan wrote: > This seems to confuse Github users into thinking that we may accept pull > requests. We do not accept pull requests. > > Sending patches to the ffmpeg-devel mailing list is our preferred method > for users to contribute code.

Re: [FFmpeg-devel] [PATCH] doc/filters: some more details and modified example to, zmq/azmq

On Thu, Apr 5, 2018, at 12:04 PM, Lou Logan wrote: > > It needs some minor work. I will plan to fix and apply later today. Pushed after some meddling. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] doc/filters: some more details and modified example to, zmq/azmq

On Thu, Apr 5, 2018, at 12:02 PM, Paul B Mahol wrote: > > anybody, please apply this. It needs some minor work. I will plan to fix and apply later today. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] doc: update loglevel option documentation

On Tue, Apr 3, 2018, at 12:30 AM, Tobias Rapp wrote: > Updates documentation after the changes to loglevel flag prefix parsing > in 4b736bc921ed96ad6d312ce0cbe0de29b9e3fe81. > > Signed-off-by: Tobias Rapp > --- > doc/fftools-common-opts.texi | 26

Re: [FFmpeg-devel] [PATCH] avcodec/openh264enc.c: generate IDR frame in response to I frame pict_type

On Sun, Mar 25, 2018, at 10:51 PM, Valery Kot wrote: > > Just wondering: is there an active maintainer for avcodec/libopenh264? Doesn't appear to be so. > If yes - can he or she please review my patch. If no - how does > maintenance works for "orphaned" modules? Any developer simply decides to

[FFmpeg-devel] [PATCH] doc/developer: remove merge request method of contributing

This seems to confuse Github users into thinking that we may accept pull requests. We do not accept pull requests. Sending patches to the ffmpeg-devel mailing list is our preferred method for users to contribute code. Signed-off-by: Lou Logan <l...@lrcd.com> --- doc/developer.texi | 6 ++-

Re: [FFmpeg-devel] [PATCH] doc/encoders - list missing options for x265

On Fri, 30 Mar 2018 19:22:29 +0530 Gyan Doshi wrote: > From dafcf437cf6ef407b95b63ac21589137c0e78c9b Mon Sep 17 00:00:00 2001 > From: Gyan Doshi > Date: Fri, 30 Mar 2018 19:19:09 +0530 > Subject: [PATCH] doc/encoders - list missing options for x265 > >

Re: [FFmpeg-devel] [PATCH] avfilter: add hrtfm filter

On Tue, Mar 20, 2018, at 1:20 AM, Paul B Mahol wrote: > Signed-off-by: Paul B Mahol > --- > doc/filters.texi | 66 ++ > libavfilter/Makefile | 1 + > libavfilter/af_hrtfm.c | 557 > +++ > libavfilter/allfilters.c

Re: [FFmpeg-devel] [PATCH] avfilter: add hrtfm filter

On Fri, Mar 16, 2018, at 11:44 AM, Paul B Mahol wrote: > Signed-off-by: Paul B Mahol > --- > doc/filters.texi | 60 ++ > libavfilter/Makefile | 1 + > libavfilter/af_hrtfm.c | 486 > +++> libavfilter/allfilters.c

Re: [FFmpeg-devel] [PATCH] avfilter: add hrtfm filter

On Thu, 15 Mar 2018 18:54:00 +0100 Paul B Mahol wrote: [...] > diff --git a/libavfilter/af_hrtfm.c b/libavfilter/af_hrtfm.c > new file mode 100644 > index 00..48536edd4b > --- /dev/null > +++ b/libavfilter/af_hrtfm.c [...] > +static const AVOption hrtfm_options[] = { >

Re: [FFmpeg-devel] [PATCH] Correcting spelling mistakes

On Thu, Mar 15, 2018, at 3:00 AM, sanilraut wrote: > Hi, > I found a few spelling mistakes in variable names. Following is the patch. > > --- > libavformat/dashdec.c | 18 +- > 1 file changed, 9 insertions(+), 9 deletions(-) Pushed, thanks.

Re: [FFmpeg-devel] [PATCH] avcodec/openh264enc.c: generate IDR frame in response to I frame pict_type

On Mon, Mar 12, 2018, at 1:46 PM, Valery Kot wrote: > Got it. Do I have to post an updated patch as a reply to this thread? Whatever you prefer, but adding a version to the subject can be helpful for us to keep track. You can do that with the "-v" option in "git format-patch". If you want to

Re: [FFmpeg-devel] [PATCH] avcodec/openh264enc.c: generate IDR frame in response to I frame pict_type

On Mon, 5 Mar 2018 15:01:16 +0100 Valery Kot wrote: > From f95943165c91dac13a644365f775aff3dd9edb11 Mon Sep 17 00:00:00 2001 > From: vkot > Date: Mon, 5 Mar 2018 13:51:51 +0100 > Subject: [PATCH 3/3] avcodec/openh264enc.c: generate IDR frame in

Re: [FFmpeg-devel] [PATCH] avfilter/vf_overlay: add show property/command

On Sun, Mar 11, 2018, at 2:16 PM, Bodecs Bela wrote: > > I have found the info about it. For others who may be curious: https://ffmpeg.org/ffmpeg-filters.html#Timeline-editing See supported filters with: ffmpeg -filters Todo: Mention which filters support timeline in filters.texi.

Re: [FFmpeg-devel] [PATCH]download: Use git.ffmpeg.org to browse repository

On Thu, Mar 8, 2018, at 2:09 PM, wm4 wrote: > I didn't even know about it. Can someone make http://git.ffmpeg.org > redirect to this as well, instead of having it return 403? While we're at it redirecting the http *.ffmpeg.org to https would be nice too.

Re: [FFmpeg-devel] [PATCH]download: Use git.ffmpeg.org to browse repository

On Thu, 8 Mar 2018 23:37:19 +0100 Carl Eugen Hoyos wrote: > Hi! > > Is there a reason why we point users to another website to browse the > FFmpeg repository? My guess is fa2da62: src/download: use a https based link for main "Browse" button But git.ffmpeg.org now has HTTPS

Re: [FFmpeg-devel] [PATCH] compat: remove in-tree NVidia headers

On Mon, Mar 5, 2018, at 11:07 AM, Timo Rothenpieler wrote: > > I tried to do that multiple times already, but trac won't let me login, > it just eventually runs into a Gateway Timeout if I try. Weird. I can't duplicate that issue. Is anyone else experiencing this? If you give me the info I can

Re: [FFmpeg-devel] [PATCH] compat: remove in-tree NVidia headers

On Tue, Feb 27, 2018, at 6:24 AM, Timo Rothenpieler wrote: > > Patch applied. Could you mention the new repo, and perhaps some simple instructions, on HWAccelIntro? I've seen a few confused users. I would but I'm not a HW user and I don't want to add anything incorrect.

Re: [FFmpeg-devel] [PATCH] Revert "Remove battleforthenet widget"

On Sun, Mar 4, 2018, at 10:54 AM, Compn wrote: > > I still have not seen an argument for why politics should not be > involved on ffmpeg. only some strawman argument about kittens on > youtube.

Re: [FFmpeg-devel] [PATCH] Revert "Remove battleforthenet widget"

On Sun, Mar 4, 2018, at 5:45 AM, Ronald S. Bultje wrote: > > I'm so sick of everything being about politics, everything being > politicized, everything being presented about the end of the world, and > everything being pushed in my face and everyone being forced to > continuously pay attention,

Re: [FFmpeg-devel] [PATCH] Revert "Remove battleforthenet widget"

On Wed, Feb 28, 2018, at 11:25 AM, Jan Ekström wrote: > > Looking at how much it got updated the last time when it misbehaved > shows really well how that worked the last time. Sorry if I sound > facetious, but I do use ffmpeg-all.html a lot and it got /really/ > irritating. +1. I object to the

Re: [FFmpeg-devel] Pull requests

On Mon, Feb 26, 2018, at 12:39 PM, Bjorn Roche wrote: > > I have a patch I'd like to submit -- can I submit a PR on GitHub, or no? The main problem with github and such is that all development discussions and reviews occur at one location: the ffmpeg-devel mailing list. PRs are therefore out of

Re: [FFmpeg-devel] h264 and opus in .mp4 container

On Thu, Feb 22, 2018, at 9:00 PM, Vittalprasad wrote: > Hi All, > From below link i saw that mp4 container can have h264 as video codec and > opus as audio codec. so i tried both codecs in to mp4 using ffmpeg, but > external player like mplayer, vlc and kmp are failing to decode voice . i.e >

Re: [FFmpeg-devel] [PATCH] doc/filters: add links to ffmpeg-utils and ffmpeg documentation

On Tue, Feb 20, 2018, at 2:01 AM, Tobias Rapp wrote: > Signed-off-by: Tobias Rapp > --- > doc/filters.texi | 48 ++-- > 1 file changed, 26 insertions(+), 22 deletions(-) [...] > @@ -9322,8 +9323,9 @@ A '|'-separated list of

Re: [FFmpeg-devel] [PATCH] docs/codecs: remove dead codec debug options

On Sat, Feb 17, 2018, at 10:56 AM, Lou Logan wrote: > LGTM. Sorry for the delay. I'll push by Monday unless someone else wants > to do so earlier. Pushed/applied. Thanks. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/m

Re: [FFmpeg-devel] [PATCH] docs/codecs: remove dead codec debug options

On Mon, Jan 15, 2018, at 5:59 AM, Gyan Doshi wrote: > Email had 1 attachment: > + 0001-docs-codecs-remove-dead-codec-debug-options.patch > 2k (text/plain) LGTM. Sorry for the delay. I'll push by Monday unless someone else wants to do so earlier. ___

Re: [FFmpeg-devel] [PATCH]configure: Improve the wording of the license failure

On Fri, Feb 9, 2018, at 1:06 AM, Carl Eugen Hoyos wrote: > Hi! > > It was reported on the user mailing list that "libvmaf is version3 and > --enable-version3 is not specified." is unclear, attached patch tries > to slightly improve the sentence. > > Please comment, Carl Eugen [...] A few

Re: [FFmpeg-devel] ffmpeg.org: snapshots not up-to-date

On Thu, Jan 11, 2018, at 3:25 PM, Michael Niedermayer wrote: > > its not fully automated, never was Ah, I was assuming more complication. I now see the fix was to simply add the links. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] ffmpeg.org: snapshots not up-to-date

On Thu, Jan 11, 2018, at 2:51 PM, Michael Niedermayer wrote: > On Thu, Jan 11, 2018 at 06:57:52PM -0300, James Almer wrote: > > Speaking of doxygen, doxy for branches 3.3 and 3.4 doesn't seem to be > > generated. > > https://ffmpeg.org/documentation.html mentions up to 3.2, and of course > > the

Re: [FFmpeg-devel] GSoC 2018

On Wed, Jan 10, 2018, at 7:31 PM, Carl Eugen Hoyos wrote: > > Were the GSoC rules concerning documentation projects changed? I don't know. I haven't memorized the rules and haven't looked at them for several years. ___ ffmpeg-devel mailing list

Re: [FFmpeg-devel] GSoC 2018

On Wed, Jan 10, 2018, at 3:30 PM, Michael Niedermayer wrote: > > Would there be interrest in a project to write a QR code / barcode > search & decode filter ? I've personally never scanned a QR code, but maybe I'm an outlier. Seems more like an OpenCV project to me. While we are throwing ideas

Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver

On Sat, Jan 6, 2018, at 9:42 AM, Rostislav Pehlivanov wrote: > > Rebased and pushed, thanks for the reviews Would you add a news entry for this? ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] avfilter/vidstab: set bytesPerPixel only for packed formats.

On Thu, Dec 28, 2017, at 11:51 AM, Michael Niedermayer wrote: > > who maintains vf_vidstabtransform.c ? Realistically, nobody. Ideally, should have been Georg Martius who is the original author of the filter and also of vid.stab itself. Consider CCing him at "martius at mis.mpg.de" or

Re: [FFmpeg-devel] Licensing question.

On Wed, 27 Dec 2017 19:48:52 + Lewis Hornsby wrote: > Hey there, I saw on your facebook page that you were giving out this > email address for enquiries regarding FFMPEG licensing. > > I am developing a closed source application in NW.JS. It is a > Wordpress theme

Re: [FFmpeg-devel] Public and private structs and fields (was: lavc: add new API for iterating codecs) and codec parsers

On Sun, Dec 24, 2017, at 6:54 AM, Nicolas George wrote: > > ...or the unbounded consumer society leading to a global ecologic catastrophe. As I work in the multimedia field I am therefore too poor to participate in the consumer society. > Happy days-getting-longer to you all! What about the

Re: [FFmpeg-devel] [PATCH] Add android_capture indev

On Fri, Dec 22, 2017, at 10:34 AM, Felix Matouschek wrote: > Hello Michael, > > I fixed the things you mentioned. New patch attached. > > Felix I think you forgot to attach the patch. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [FFmpeg-cvslog] [ffmpeg-web] branch master updated. 979b3a6 web/contact: note that no discussions occur on cvslog and trac mailing lists

On Thu, Dec 21, 2017, at 4:07 AM, Carl Eugen Hoyos wrote: > Where was this agreed upon? > > Carl Eugen As a mailing list maintainer I made this decision based on the reality of the situation and due to developer feedback in the following three threads: [FFmpeg-devel] [PATCH] Refactor Developer

<    1   2   3   4   5   >