[FFmpeg-devel] [PATCH] ffmpeg-opt: mark stream disable options as output-only

2018-12-08 Thread Gyan Doshi
I see users with these options set in front of input. Stream disabling for input requires -discard though one packet tends to get smuggled across. But that's for another patch. Gyan From f0e78555d6ea5510922e2d543c9b69dff7d480b5 Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Sat, 8 Dec 2018

Re: [FFmpeg-devel] [PATCH V3 1/2] lavc/svt_hevc: add libsvt hevc encoder wrapper.

2018-12-07 Thread Gyan Doshi
On 07-12-2018 05:26 PM, Jun Zhao wrote: +{"perset", "Encoding preset [0, 12] (e,g, for subjective quality tuning mode and >=4k resolution), [0, 10] (for >= 1080p resolution), [0, 9] (for all resolution and modes)", preset --> preset +static const AVCodecDefault eb_enc_defaults[] = { +

Re: [FFmpeg-devel] [PATCH V3 2/2] doc: Add libsvt_hevc encoder docs

2018-12-07 Thread Gyan Doshi
You'll need to rebase as I just rearranged entries (and style, a bit) in doc/general On 07-12-2018 05:26 PM, Jun Zhao wrote: Signed-off-by: Jun Zhao Signed-off-by: Huang, Zhengxu Signed-off-by: hassene --- doc/encoders.texi | 98 +

Re: [FFmpeg-devel] Patch to add avcintra-flavor option from x264

2018-12-06 Thread Gyan Doshi
On 06-12-2018 02:26 PM, Steinar Apalnes wrote: This patch adds the new "avcintra-flavor" to the -x264opts. The avcintra-flavor option in x264 adds the possibility to create the Sony XAVC flavor of avcintra. Default is Panasonic. Tested OK. -steinar Why is this needed? All key=value pairs

Re: [FFmpeg-devel] [FFmpeg-cvslog] doc: chromaprint

2018-12-04 Thread Gyan Doshi
On 04-12-2018 09:28 PM, Carl Eugen Hoyos wrote: 2018-12-04 16:51 GMT+01:00, Gyan Doshi : On 04-12-2018 08:44 PM, Carl Eugen Hoyos wrote: 2018-12-04 15:52 GMT+01:00, Gyan Doshi : On 04-12-2018 08:05 PM, Carl Eugen Hoyos wrote: 2018-12-04 14:53 GMT+01:00, Gyan Doshi : My commits simply

Re: [FFmpeg-devel] [FFmpeg-cvslog] doc: chromaprint

2018-12-04 Thread Gyan Doshi
On 04-12-2018 08:05 PM, Carl Eugen Hoyos wrote: 2018-12-04 14:53 GMT+01:00, Gyan Doshi : My commits simply convey that into the docs - it doesn't create a new judgement or make one where none existed. It claims something (that may or may not be correct) instead of leaving the responsibility

Re: [FFmpeg-devel] [FFmpeg-cvslog] doc: chromaprint

2018-12-04 Thread Gyan Doshi
On 04-12-2018 07:10 PM, Carl Eugen Hoyos wrote: 2018-12-04 14:32 GMT+01:00, Gyan Doshi : On 04-12-2018 06:38 PM, Carl Eugen Hoyos wrote: 2018-12-04 13:53 GMT+01:00, Gyan Doshi : On 04-12-2018 06:15 PM, Carl Eugen Hoyos wrote: 2018-12-04 12:10 GMT+01:00, Gyan Doshi : +@section Chromaprint

Re: [FFmpeg-devel] [FFmpeg-cvslog] doc: chromaprint

2018-12-04 Thread Gyan Doshi
On 04-12-2018 06:38 PM, Carl Eugen Hoyos wrote: 2018-12-04 13:53 GMT+01:00, Gyan Doshi : On 04-12-2018 06:15 PM, Carl Eugen Hoyos wrote: 2018-12-04 12:10 GMT+01:00, Gyan Doshi : +@section Chromaprint + +FFmpeg can make use of the Chromaprint library for generating audio fingerprints

Re: [FFmpeg-devel] [FFmpeg-cvslog] doc: chromaprint

2018-12-04 Thread Gyan Doshi
On 04-12-2018 06:15 PM, Carl Eugen Hoyos wrote: 2018-12-04 12:10 GMT+01:00, Gyan Doshi : +@section Chromaprint + +FFmpeg can make use of the Chromaprint library for generating audio fingerprints. +It is licensed under LGPL version 2.1. No other library is described like this. Why are you

Re: [FFmpeg-devel] [PATCH 1/2] avformat/movenc: Added an option to disable SIDX atom

2018-12-04 Thread Gyan Doshi
On 04-12-2018 02:11 PM, Karthick J wrote: diff --git a/doc/muxers.texi b/doc/muxers.texi index f1cc6f5fee..6ca27b04a3 100644 --- a/doc/muxers.texi +++ b/doc/muxers.texi @@ -1325,6 +1325,8 @@ more efficient), but with this option set, the muxer writes one moof/mdat pair for each track, making

Re: [FFmpeg-devel] [PATCH]lavd: Remove libndi newtek

2018-12-03 Thread Gyan Doshi
On 03-12-2018 09:49 PM, Carl Eugen Hoyos wrote: 2018-12-03 17:16 GMT+01:00, Gyan Doshi : What's the link to the blog post? Also, is anyone from Newtek on the ML - if not, is there someone we can invite for input? What kind of input would seem useful to you in this case? Insight

Re: [FFmpeg-devel] [PATCH]lavd: Remove libndi newtek

2018-12-03 Thread Gyan Doshi
On 03-12-2018 09:35 PM, Carl Eugen Hoyos wrote: Hi! It appears to me that NewTek abused our willingness to add an optional external nonfree library, I don't see many better options. See Ticket #7589 and a blog post by a NewTek engineer confirming the issue. What's the link to the blog post?

Re: [FFmpeg-devel] [PATCH V1 0/2] Add libsvt HEVC encoder wrapper.

2018-12-01 Thread Gyan Doshi
On 02-12-2018 11:08 AM, Jun Zhao wrote: The Scalable Video Technology for HEVC Encoder (SVT-HEVC Encoder) is an HEVC-compliant encoder library core that achieves excellent density-quality tradeoffs, and is highly optimized for Intel® Xeon™ Scalable Processor and Xeon™ D processors. Intel

Re: [FFmpeg-devel] [PATCH 2/2] avformat/mpegenc: extend muxing PCM-DVD to other depths

2018-11-29 Thread Gyan Doshi
On 29-11-2018 05:09 PM, Paul B Mahol wrote: Fixes #6783. Signed-off-by: Paul B Mahol --- libavformat/mpegenc.c | 27 +-- 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/libavformat/mpegenc.c b/libavformat/mpegenc.c index 4c6fa67fb8..1389288b7f 100644

Re: [FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-09-17 Thread Gyan Doshi
On 07-09-2018 12:21 AM, Gyan Doshi wrote: On 05-09-2018 06:06 AM, Michael Niedermayer wrote: On Mon, Sep 03, 2018 at 10:48:45AM +0530, Gyan Doshi wrote: On 31-08-2018 10:26 AM, Gyan Doshi wrote: On 31-08-2018 09:57 AM, Gyan Doshi wrote: On 31-08-2018 04:28 AM, Marton Balint wrote

Re: [FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-09-06 Thread Gyan Doshi
On 05-09-2018 06:06 AM, Michael Niedermayer wrote: On Mon, Sep 03, 2018 at 10:48:45AM +0530, Gyan Doshi wrote: On 31-08-2018 10:26 AM, Gyan Doshi wrote: On 31-08-2018 09:57 AM, Gyan Doshi wrote: On 31-08-2018 04:28 AM, Marton Balint wrote: Is there any real use case when same source

Re: [FFmpeg-devel] [PATCH] ffplay: add option to allow custom jump interval

2018-09-05 Thread Gyan Doshi
On 05-09-2018 09:52 PM, Marton Balint wrote: On Wed, 5 Sep 2018, Gyan Doshi wrote: Ping. LGTM, thanks. Pushed as 1a4a8df249426c85ba6c96ef5ab022afaaf4dc8f Thanks, Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org

Re: [FFmpeg-devel] [PATCH] ffplay: add option to allow custom jump interval

2018-09-05 Thread Gyan Doshi
On 03-09-2018 11:03 AM, Gyan Doshi wrote: On 02-09-2018 02:57 PM, Marton Balint wrote: I don't think the guards are necessary, it might make sense for somebody to reverse the meaning of left and right keys, therefore use a negative value. v3: option renamed; sign guard removed. Gyan

Re: [FFmpeg-devel] [PATCH 1/2] docs/filters: add documentation to all existing OpenCL filters

2018-09-05 Thread Gyan Doshi
Hi Danil, On 18-08-2018 02:06 PM, Gyan Doshi wrote: Hi Danil, Except overlay and the topic of format requirements, rest LGTM. This patch appears to be abandoned. These filters need to be documented, but the format constraints should be clarified first, as asked in the parent post. Also

Re: [FFmpeg-devel] [PATCH] ffplay: add option to allow custom jump interval

2018-09-02 Thread Gyan Doshi
< 0) I don't think the guards are necessary, it might make sense for somebody to reverse the meaning of left and right keys, therefore use a negative value. v3: option renamed; sign guard removed. Gyan From 94424f1b9501e0550a2d395381f15d89e00a52f9 Mon Sep 17 00:00:00 2001 From: Gyan Do

Re: [FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-09-02 Thread Gyan Doshi
On 31-08-2018 10:26 AM, Gyan Doshi wrote: On 31-08-2018 09:57 AM, Gyan Doshi wrote: On 31-08-2018 04:28 AM, Marton Balint wrote: Is there any real use case when same source and destination works, so the option can be used? If not, then just make ffmpeg fail, like the cp command fails

Re: [FFmpeg-devel] [PATCH] ffplay: add option to allow custom jump interval

2018-09-01 Thread Gyan Doshi
nged 'jump' to 'seek' throughout. Haven't changed code much, kept basic protection against invalid input (val < 0) Gyan From abd6b2616ec2caf115dcdf05fba6be0a3c80a17a Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Sat, 1 Sep 2018 11:33:17 +0530 Subject: [PATCH v2] ffplay: add option to allo

[FFmpeg-devel] [PATCH] ffplay: add option to allow custom jump interval

2018-09-01 Thread Gyan Doshi
From aab52de703302d26d0bd83fb28eb1a033fa57d14 Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Sat, 1 Sep 2018 11:33:17 +0530 Subject: [PATCH] ffplay: add option to allow custom jump interval At present, left and right keys are hardcoded to jump by 10 seconds. Added option allows users to set

Re: [FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-08-30 Thread Gyan Doshi
On 31-08-2018 09:57 AM, Gyan Doshi wrote: On 31-08-2018 04:28 AM, Marton Balint wrote: Is there any real use case when same source and destination works, so the option can be used? If not, then just make ffmpeg fail, like the cp command fails for same source and destination. I am against

Re: [FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-08-30 Thread Gyan Doshi
On 31-08-2018 04:28 AM, Marton Balint wrote: Is there any real use case when same source and destination works, so the option can be used? If not, then just make ffmpeg fail, like the cp command fails for same source and destination. I am against adding an option if it has no known use.

Re: [FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-08-30 Thread Gyan Doshi
On 29-08-2018 09:48 AM, Gyan Doshi wrote: On 29-08-2018 02:43 AM, Michael Niedermayer wrote: On Tue, Aug 28, 2018 at 08:31:51AM +0200, Marton Balint wrote: Instead of this, maybe we should add support to write lock the files when opening them for reading. Then ffmpeg can request

Re: [FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-08-28 Thread Gyan Doshi
On 29-08-2018 02:43 AM, Michael Niedermayer wrote: On Tue, Aug 28, 2018 at 08:31:51AM +0200, Marton Balint wrote: Instead of this, maybe we should add support to write lock the files when opening them for reading. Then ffmpeg can request this. That would be an useful option, and not just for

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-27 Thread Gyan Doshi
On 28-08-2018 01:29 AM, Michael Niedermayer wrote: LGTM thanks PS: these fields seem not documented anywhere, neither the new nor the old or iam looking at the wrong places Will add documentation. This patch pushed as 26dc76324564fc572689509c2efb7f1cb8f41a45 Thanks, Gyan

[FFmpeg-devel] [PATCH] ffmpeg: block output == input for files

2018-08-27 Thread Gyan Doshi
/sinks are exempt i.e. http, pipes, devices..etc. This patch doesn't affect the semantics of '-y' and adds the check after it. Thanks, Gyan From deb97d9b5dd1f50a7e6b560c77b81b9cd707b7c1 Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Sun, 26 Aug 2018 11:22:50 +0530 Subject: [PATCH] ffmpeg: block

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-27 Thread Gyan Doshi
On 26-08-2018 11:53 AM, Gyan Doshi wrote: On 09-08-2018 10:09 AM, Gyan Doshi wrote: On 08-08-2018 12:47 AM, Nicolas George wrote: Gyan Doshi (2018-08-08): That will just defer the breaking change. That will leave people time to notice the change and allow old and new scripts to work

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-26 Thread Gyan Doshi
On 09-08-2018 10:09 AM, Gyan Doshi wrote: On 08-08-2018 12:47 AM, Nicolas George wrote: Gyan Doshi (2018-08-08): That will just defer the breaking change. That will leave people time to notice the change and allow old and new scripts to work during the transition. Will do it this way

Re: [FFmpeg-devel] [PATCH] avdevice/decklink_enc: print preroll and buffer size

2018-08-23 Thread Gyan Doshi
On 24-08-2018 12:12 AM, Marton Balint wrote: On Thu, 23 Aug 2018, Gyan Doshi wrote: Plan to push tomorrow. Ok, LGTM. Thanks. Pushed as d0b48a960448cc8eb0e2c86e0804b14bdcb3e751 Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http

Re: [FFmpeg-devel] [PATCH] avdevice/decklink_enc: print preroll and buffer size

2018-08-23 Thread Gyan Doshi
Plan to push tomorrow. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] avdevice/decklink_enc: print preroll and buffer size

2018-08-22 Thread Gyan Doshi
From f496d970d319ec3916a55e05b925f6b43763ebfa Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Wed, 22 Aug 2018 16:23:58 +0530 Subject: [PATCH] avdevice/decklink_enc: print preroll and buffer size Helpful in diagnosing latency issues. --- libavdevice/decklink_enc.cpp | 3 +++ 1 file changed, 3

Re: [FFmpeg-devel] [PATCH v3] doc/filters: Add double-pass example for loudnorm

2018-08-22 Thread Gyan Doshi
On 22-08-2018 04:01 PM, Marvin Scholz wrote: Guessed Channel Layout for Input Stream #0.0 : stereo ...     Stream #0:0(ger): Audio: wmav2 (a[1][0][0] / 0x0161), 48000 Hz, stereo, fltp, 192 kb/s [Parsed_aresample_1 @ 0x7fb7c540d500] Cannot select channel layout for the link between filters

Re: [FFmpeg-devel] [PATCH v3] doc/filters: Add double-pass example for loudnorm

2018-08-22 Thread Gyan Doshi
On 22-08-2018 02:38 PM, Marvin Scholz wrote: On 22 Aug 2018, at 6:40, Gyan Doshi wrote: On 22-08-2018 04:43 AM, Marvin Scholz wrote: +@example +ffmpeg -i input -af loudnorm=I=-23:TP=-1:measured_I=-9.0:measured_TP=1.5:measured_LRA=9.4:measured_thresh=-19.5:print_format=summary output

Re: [FFmpeg-devel] [PATCH v3] doc/filters: Add double-pass example for loudnorm

2018-08-21 Thread Gyan Doshi
On 22-08-2018 04:43 AM, Marvin Scholz wrote: +@example +ffmpeg -i input -af loudnorm=I=-23:TP=-1:measured_I=-9.0:measured_TP=1.5:measured_LRA=9.4:measured_thresh=-19.5:print_format=summary output Since your input LRA is 9.4, and output LRA is 7 (default), the filter will upsample to 192

Re: [FFmpeg-devel] [PATCH 2/2] libavfilter: Removes stored DNN models. Adds support for native backend model file format in tf backend.

2018-08-21 Thread Gyan Doshi
On 22-08-2018 01:32 AM, Pedro Arthur wrote: 2018-08-21 16:40 GMT-03:00 Gyan Doshi : Agreed. Can't the filter upscale the chroma planes internally? That's exactly what the filter were doing before, but for some reason doing it this way is not 'good code'. Well, the rule hasn't been

Re: [FFmpeg-devel] [PATCH 2/2] libavfilter: Removes stored DNN models. Adds support for native backend model file format in tf backend.

2018-08-21 Thread Gyan Doshi
On 21-08-2018 10:27 PM, Pedro Arthur wrote: Something like, ffmpeg -i in.bmp -filter_complex 'format=yuvj444p,extractplanes=y+u+v[y][u][v]; [y]sr=dnn_backend=tensorflow:model=espcn.model[y-sr]; [u]scale=iw*2:-1[u2x];[v]scale=iw*2:-1[v2x];

Re: [FFmpeg-devel] [PATCH v3] doc/filters: Add double-pass example for loudnorm

2018-08-20 Thread Gyan Doshi
On 21-08-2018 03:18 AM, Marvin Scholz wrote: +@example +ffmpeg -i input -af loudnorm=I=-23:TP=-1:measured_I=-9.0:measured_TP=1.5:measured_LRA=9.4:measured_thresh=-19.5:print_format=summary output Since your input LRA is 9.4, and output LRA is 7 (default), the filter will upsample to 192

Re: [FFmpeg-devel] [PATCH 2/2] libavfilter: Removes stored DNN models. Adds support for native backend model file format in tf backend.

2018-08-20 Thread Gyan Doshi
On 20-08-2018 11:52 PM, Sergey Lavrushkin wrote: But there are some issues. First, to use this filter for formats with chroma channels I do: ffmpeg -i in.bmp -filter_complex 'extractplanes=y+u+v[y][u][v]' -map '[y]' y.bmp -map '[u]' u.bmp -map '[v]' v.bmp ffmpeg -i y.bmp -vf

Re: [FFmpeg-devel] [PATCH v2] doc/filters: Add double-pass example for loudnorm

2018-08-19 Thread Gyan Doshi
On 20-08-2018 03:27 AM, Marvin Scholz wrote: +@example +$ ffmpeg -i input -map 0:a -af loudnorm=I=-23:TP=-1:print_format=summary -f null - + +[...] +Input Integrated: -9.0 LUFS +Input True Peak: +1.5 dBTP +Input LRA: 9.4 LU +Input Threshold: -19.5 LUFS +@end example +

Re: [FFmpeg-devel] [PATCH] lavfi/vf_libvmaf: update to use libvmaf v1.3.9

2018-08-19 Thread Gyan Doshi
On 20-08-2018 03:17 AM, Carl Eugen Hoyos wrote: I believe that if a general option exists (as in this case), it is a bad idea to have a specifically targeted option that has to be used instead. The user may not want the thread pool to be available for any other threaded filters in the graph.

Re: [FFmpeg-devel] [PATCH 1/2] docs/filters: add documentation to all existing OpenCL filters

2018-08-18 Thread Gyan Doshi
Hi Danil, Except overlay and the topic of format requirements, rest LGTM. On 15-08-2018 05:30 PM, Danil Iashchenko wrote: docs/filters: add documentation to all existing OpenCL filters Added general instruction for format conversion in the start of overall section and separatly for

Re: [FFmpeg-devel] [PATCH] lavfi/vf_libvmaf: update to use libvmaf v1.3.9

2018-08-17 Thread Gyan Doshi
On 17-08-2018 06:12 PM, Carl Eugen Hoyos wrote: 2018-08-14 9:57 GMT+02:00, Gyan Doshi : filter_threads applies to all simple filtergraphs. The private option is specifically targeted. Isn't that better? I believe the opposite is true. Which - preference for private option

Re: [FFmpeg-devel] [PATCH 1/2] doc/filters.texi: Adds documentation for sr filter.

2018-08-15 Thread Gyan Doshi
On 15-08-2018 11:37 PM, James Almer wrote: Should have been the second patch in the set, in that case. If a change is split into two patches, one for code and one for documentation, then the former goes first. Gyan should have paid more attention to it as well, to be fair. I assumed he made

Re: [FFmpeg-devel] [PATCH 1/2] doc/filters.texi: Adds documentation for sr filter.

2018-08-15 Thread Gyan Doshi
On 15-08-2018 11:28 PM, Sergey Lavrushkin wrote: 2018-08-15 19:59 GMT+03:00 Gyan Doshi : LGTM. Will apply with some small changes. I've merged the docs entry in the 2nd part, so remove it from there. This entry corresponds to changes made in the second patch. Without these changes

Re: [FFmpeg-devel] [PATCH 1/2] doc/filters.texi: Adds documentation for sr filter.

2018-08-15 Thread Gyan Doshi
On 15-08-2018 10:05 PM, Sergey Lavrushkin wrote: Resending patch with documentation for sr filter. LGTM. Will apply with some small changes. I've merged the docs entry in the 2nd part, so remove it from there. Thanks, Gyan ___ ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/2] docs/filters: add documentation to all existing OpenCL filters

2018-08-14 Thread Gyan Doshi
Danil, On 04-08-2018 12:43 AM, Gyan Doshi wrote: On 03-08-2018 08:46 PM, Danil Iashchenko wrote: +For most general-purpose filters, no conversion is required. + +In case a file contains an alpha channel supported by the format, then explicit conversion is a requirement. This is unclear

Re: [FFmpeg-devel] [PATCH] avformat: correct fdebug loglevel

2018-08-14 Thread Gyan Doshi
On 14-08-2018 12:58 PM, Gyan Doshi wrote: On 13-08-2018 12:52 PM, Gyan Doshi wrote: 3e4b5e68c1 intended for fdebug to be usable without -v and cmdutils sets v to DEBUG but most fdebug logs are at TRACE. Changed. Plan to push tonight. Pushed as 02741853d74d214540aca4cd456877348d4f8953

Re: [FFmpeg-devel] [PATCH] lavfi/vf_libvmaf: update to use libvmaf v1.3.9

2018-08-14 Thread Gyan Doshi
On 14-08-2018 01:20 PM, Paul B Mahol wrote: On 8/14/18, Gyan Doshi wrote: On 14-08-2018 03:24 AM, Carl Eugen Hoyos wrote: Why does this not use -filter_threads? Didn't know it was an option. I can certainly change the code to use it. Please do it if it works. filter_threads

Re: [FFmpeg-devel] [PATCH] avformat: correct fdebug loglevel

2018-08-14 Thread Gyan Doshi
On 13-08-2018 12:52 PM, Gyan Doshi wrote: 3e4b5e68c1 intended for fdebug to be usable without -v and cmdutils sets v to DEBUG but most fdebug logs are at TRACE. Changed. Plan to push tonight. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] lavfi/vf_libvmaf: update to use libvmaf v1.3.9

2018-08-13 Thread Gyan Doshi
On 14-08-2018 03:24 AM, Carl Eugen Hoyos wrote: Why does this not use -filter_threads? Didn't know it was an option. I can certainly change the code to use it. Please do it if it works. filter_threads applies to all simple filtergraphs. The private option is specifically targeted.

[FFmpeg-devel] [PATCH] avformat: correct fdebug loglevel

2018-08-13 Thread Gyan Doshi
3e4b5e68c1 intended for fdebug to be usable without -v and cmdutils sets v to DEBUG but most fdebug logs are at TRACE. Changed. From 0b349a958d6af8ce09ef7d36a34e3f0d3f6b0692 Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Mon, 13 Aug 2018 12:32:41 +0530 Subject: [PATCH] avformat: correct fdebug

Re: [FFmpeg-devel] [PATCH] lavfi: update xbr filter url

2018-08-08 Thread Gyan Doshi
On 09-08-2018 10:31 AM, Gyan Doshi wrote: On 09-08-2018 01:19 AM, Mina wrote: This patch update the existing url with the newly found one. Will apply. Thanks, Gyan Pushed as e0539f0349e945793c11cd88c468d9a2f3fedce9 with modified/shortened commit msg. Gyan

Re: [FFmpeg-devel] [PATCH] lavfi: update xbr filter url

2018-08-08 Thread Gyan Doshi
On 09-08-2018 01:19 AM, Mina wrote: This patch update the existing url with the newly found one. Will apply. Thanks, Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-08 Thread Gyan Doshi
On 08-08-2018 12:47 AM, Nicolas George wrote: Gyan Doshi (2018-08-08): That will just defer the breaking change. That will leave people time to notice the change and allow old and new scripts to work during the transition. Will do it this way. Gyan

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-07 Thread Gyan Doshi
On 06-08-2018 08:00 PM, Nicolas George wrote: Not really. I suppose you could add the field with the correct name and remove the bogus one later. But your thoughts on this are probably better than mine. That will just defer the breaking change. The options, as I see it, are wontfix, or

Re: [FFmpeg-devel] [PATCH] avs2: correct avs2 description

2018-08-07 Thread Gyan Doshi
On 08-08-2018 12:08 AM, Gyan Doshi wrote: Will push. Thanks, Gyan Pushed as f563e7868fb9540e1c8a589558fba2beaaba01e0 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] avs2: correct avs2 description

2018-08-07 Thread Gyan Doshi
On 08-08-2018 12:05 AM, James Almer wrote: Should be ok. Will push. Thanks, Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/7] libavfilter: Adds on the fly generation of default DNN models for tensorflow backend instead of storing binary model.

2018-08-06 Thread Gyan Doshi
On 06-08-2018 08:23 PM, Pedro Arthur wrote: I may push the patch with proposed changes by tomorrow. Please add an entry in docs/filter as well as one in docs/general for tf backend as applicable. Thanks, Gyan ___ ffmpeg-devel mailing list

Re: [FFmpeg-devel] [PATCH] avs2: Correct expression error and simplify log

2018-08-06 Thread Gyan Doshi
On 06-08-2018 07:13 PM, hwren wrote: -.long_name = NULL_IF_CONFIG_SMALL("Decoder for AVS2/IEEE 1857.4"), +.long_name = NULL_IF_CONFIG_SMALL("Decoder for AVS2-P2/IEEE1857.4"), "Decoder for" is not needed. The flag indicates its role in `ffmpeg -codecs`. Rest docs LGTM

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-05 Thread Gyan Doshi
On 05-08-2018 02:28 PM, Gyan Doshi wrote: Ah yes, Sorry, this is used for parsing. What protocol do you suggest for correcting this? Any thoughts on this? I see that there were two changes made to value fields of the progress report earlier this year - a194e9c4159 and 1322b00060 Regards

Re: [FFmpeg-devel] [PATCH] avcodec/libaomenc: correct range for cpu-used

2018-08-05 Thread Gyan Doshi
On 05-08-2018 02:12 PM, Gyan Doshi wrote: Will push soon, if nothing else. Pushed as 076b19660e7c9466d2d78ff9ae66b97ff2b6aa1e Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [RFC] Maintain documentation for all components?

2018-08-05 Thread Gyan Doshi
Our documentation for demuxers/muxers/decoders/encoders is incomplete and only feature a few. I propose we cover all or, at least, many more of them. Thoughts? Thanks, Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-05 Thread Gyan Doshi
On 05-08-2018 02:17 PM, Nicolas George wrote: Gyan Doshi (2018-08-05): Will push soon, if nothing else. Have you considered you may be breaking some user's scripts? Ah yes, Sorry, this is used for parsing. What protocol do you suggest for correcting this? Regards, Gyan

Re: [FFmpeg-devel] [PATCH] avcodec/libaomenc: correct range for cpu-used

2018-08-05 Thread Gyan Doshi
On 05-08-2018 01:49 PM, Carl Eugen Hoyos wrote: Am 05.08.2018 um 08:09 schrieb Gyan Doshi : Don't know if micro bump is needed. You may (should) always bump micro when the behaviour changes, if this counts as a change is up to you (the options you remove didn’t work before afaiu

Re: [FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-05 Thread Gyan Doshi
On 05-08-2018 01:46 PM, Carl Eugen Hoyos wrote: av_bprintf(_script, "out_time_ms=N/A\n"); If the patch is a good idea you should also change this line. Fixed locally. Will push soon, if nothing else. Thanks, Gyan ___ ffmpeg-devel mailing

[FFmpeg-devel] [PATCH] ffmpeg: correct units for raw pts in -progress report

2018-08-05 Thread Gyan Doshi
From a45b0ade691816d8037c846f2b773d0ddab74cbe Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Sun, 5 Aug 2018 12:34:21 +0530 Subject: [PATCH] ffmpeg: correct units for raw pts in -progress report PTS is in microseconds. Fixes #7345 --- fftools/ffmpeg.c | 2 +- 1 file changed, 1 insertion(+), 1

[FFmpeg-devel] [PATCH] avcodec/libaomenc: correct range for cpu-used

2018-08-05 Thread Gyan Doshi
Don't know if micro bump is needed. From 4078eb3627999632234eb84cb132ddc4c7c96583 Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Sun, 5 Aug 2018 11:33:45 +0530 Subject: [PATCH] avcodec/libaomenc: correct range for cpu-used Valid range is [0,8] as stated in aom.git:aom/aomcx.h Fixes #7343

Re: [FFmpeg-devel] [PATCH 1/2] docs/filters: add documentation to all existing OpenCL filters

2018-08-03 Thread Gyan Doshi
On 03-08-2018 08:46 PM, Danil Iashchenko wrote: +For most general-purpose filters, no conversion is required. + +In case a file contains an alpha channel supported by the format, then explicit conversion is a requirement. This is unclear. So, if the input's pixel format has alpha, we

Re: [FFmpeg-devel] [PATCH] avformat/avs: add descriptive name and url

2018-08-02 Thread Gyan Doshi
Pushed as c9118d4d64a661fddd431a7437994c31eafb32c6 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/2] docs/filters: add documentation to all existing OpenCL filters

2018-08-02 Thread Gyan Doshi
On 31-07-2018 08:44 PM, Danil Iashchenko wrote: This hinders overall progress on the documentation and filter implementation of my GSoC project and there is not much time left. I suggest putting it on the backburner for the moment and leaving it out until the next patch. OK. +@item

[FFmpeg-devel] [PATCH] avformat/avs: add descriptive name and url

2018-08-01 Thread Gyan Doshi
From c9118d4d64a661fddd431a7437994c31eafb32c6 Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Thu, 2 Aug 2018 10:47:10 +0530 Subject: [PATCH] avformat/avs: add descriptive name and url AVS now more commonly refers to the Chinese AVS format. This demuxer processes video files for Creature Shock

Re: [FFmpeg-devel] [PATCH] doc/formats: Add documentation for skip_estimate_duration_from_pts

2018-07-29 Thread Gyan Doshi
On 30-07-2018 04:37 AM, Michael Niedermayer wrote: I'll modify and push this tomorrow. sure, thx Pushed as 67fb9c75efec9f069fc57b3ed211a35c63c686e5 Thanks, Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] doc/formats: Add documentation for skip_estimate_duration_from_pts

2018-07-29 Thread Gyan Doshi
On 26-07-2018 11:38 AM, Gyan Doshi wrote: On 26-07-2018 03:37 AM, Michael Niedermayer wrote: what do people prefer ? I have no real oppinion on where to put it as long as it is documented somewhere in the docs ... ... We can leave the possible shifting for later on, but let's add

Re: [FFmpeg-devel] [PATCH] qt-faststart: Add mode for probing faststart-ness

2018-07-27 Thread Gyan Doshi
On 28-07-2018 03:33 AM, Tomas Härdin wrote: woot! I didn't know the mov demuxer dumped such things. It is quite slow however, since it will scan through every leaf atom in the file. For example, running time ffmpeg -i input.mov -v 56 2>&1 | wc on a 1.5 GiB MP4 on an SSD takes: Use the

Re: [FFmpeg-devel] [PATCH] qt-faststart: Add mode for probing faststart-ness

2018-07-27 Thread Gyan Doshi
On 27-07-2018 07:36 PM, Tomas Härdin wrote: This is something the PeerTube guys need, and this seemed a straightforward enough approach. Feedback appreciated Not a patch review, just a note that one can do this with ffmpeg/ffprobe and basic *nix tools. To check for moof, ffmpeg -i

Re: [FFmpeg-devel] [PATCH] doc/formats: Add documentation for skip_estimate_duration_from_pts

2018-07-26 Thread Gyan Doshi
On 26-07-2018 03:37 AM, Michael Niedermayer wrote: On Wed, Jul 25, 2018 at 10:13:58AM +0530, Gyan Doshi wrote: Wouldn't it be better to move this as a private option for those two demuxers? iam not sure, it could be used by others in the future too what do people prefer ? I have no real

Re: [FFmpeg-devel] [PATCH] doc/formats: Add documentation for skip_estimate_duration_from_pts

2018-07-24 Thread Gyan Doshi
On 25-07-2018 04:19 AM, Michael Niedermayer wrote: + +@item skip_estimate_duration_from_pts @var{bool} (@emph{input}) +skip duration calculation from pts. The function this is in is only called for MPEG-PS or seekable MPEG-TS. We should note that. The comment above the function says it's

[FFmpeg-devel] [PATCH] download: remove dead link for Mac binaries

2018-07-23 Thread Gyan Doshi
From f57cec086a22300dbc12f6e998b2cf53d7a8e103 Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Mon, 23 Jul 2018 19:33:57 +0530 Subject: [PATCH] download: remove dead link for Mac binaries ffmpegmac.net now leads to a parked page. --- src/download | 3 --- 1 file changed, 3 deletions(-) diff

Re: [FFmpeg-devel] [PATCH 1/2] docs/filters: add documentation to all existing OpenCL filters

2018-07-23 Thread Gyan Doshi
On 20-07-2018 10:01 PM, Danil Iashchenko wrote: +@section avgblur_opencl + +Apply average blur filter. + +The filter accepts the following options: + +@table @option +@item sizeX +Set horizontal radius size. By default value is @code{1}. State range as well for all options, e.g. Range

Re: [FFmpeg-devel] [PATCH] doc/filters: update info about avgblur filter to make it more understandable

2018-07-21 Thread Gyan Doshi
On 20-07-2018 10:01 PM, Danil Iashchenko wrote: doc/filters: update info about avgblur filter to make it more understandable --- doc/filters.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/filters.texi b/doc/filters.texi index 705d48e..e3005c3 100644 ---

Re: [FFmpeg-devel] [PATCH 1/2] docs/filters: add documentation to all existing OpenCL filters

2018-07-21 Thread Gyan Doshi
I'll review this within a couple of days. Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

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

2018-07-18 Thread Gyan Doshi
On 18-07-2018 04:13 AM, Lou Logan wrote: 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. What's the volume of

Re: [FFmpeg-devel] [PATCH] doc/ffmpeg: remove reference to non-existent option

2018-07-17 Thread Gyan Doshi
On 17-07-2018 04:52 PM, Moritz Barsnick wrote: I guess it was undeprecated by making it work properly again, which is fair enough, as far as I'm concerned. Still, is it preferred to use a filter? Yes, the CLI option is global, so applies to all video streams. Most invocations I've seen of

Re: [FFmpeg-devel] [PATCH] doc/ffmpeg: remove reference to non-existent option

2018-07-17 Thread Gyan Doshi
The option still exists and is effective. See current line 3528 of fftool/ffmpeg_opt.c and the block at line 822 of fftool/ffmpeg_filter.c On 17-07-2018 03:06 PM, Moritz Barsnick wrote: The "-deinterlace" option was removed in 481575d255195c6c2f32e04686b94de984ae78d4, over five years ago.

Re: [FFmpeg-devel] [PATCH] ffmpeg.c: allow ffmpeg to output stats for each video stream

2018-07-16 Thread Gyan Doshi
On 17-07-2018 02:38 AM, Wang Cao wrote: I was thinking to output stats for each video/audio stream one line by another. It seems this would be a huge change to users who are not aware. Keeping the old file bitrate looks good to me. Can I extend this to output file bitrate for each output

Re: [FFmpeg-devel] [PATCH] avformat/mov: only set handler_name from mdia->hdlr

2018-07-16 Thread Gyan Doshi
On 16-07-2018 03:34 PM, Gyan Doshi wrote: Plan to push tonight. On 14-07-2018 02:15 PM, Gyan Doshi wrote: Date: Sat, 14 Jul 2018 13:59:51 +0530 Subject: [PATCH] avformat/mov: only set handler_name from mdia->hdlr 6 FATE references updated. Fixes #7104 Pus

Re: [FFmpeg-devel] [PATCH v2] fate: add more vc2 encoder tests

2018-07-16 Thread Gyan Doshi
I'll likely be pushing a change to the MOV demuxer tonight which will change a tag, so you'll probably need to re-gen your refs. Regards, Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] avformat/mov: only set handler_name from mdia->hdlr

2018-07-16 Thread Gyan Doshi
Plan to push tonight. On 14-07-2018 02:15 PM, Gyan Doshi wrote: Date: Sat, 14 Jul 2018 13:59:51 +0530 Subject: [PATCH] avformat/mov: only set handler_name from mdia->hdlr 6 FATE references updated. Fixes #7104 ___ ffmpeg-devel mailing list ffm

Re: [FFmpeg-devel] [PATCH v2][GSOC] avfilter: added colorconstancy

2018-07-14 Thread Gyan Doshi
On 15-07-2018 07:50 AM, Mina wrote: +A variation color constancy that estimates scene illumination via grey edge algorithm +and corrects the scene colors accordingly. "A variation color constancy filter which estimates ..." Maybe add a link to the algo paper in the next line: "Grey Edge

Re: [FFmpeg-devel] [PATCH] avformat/movenc: write track data in minf->hdlr for MOV

2018-07-14 Thread Gyan Doshi
On 10-07-2018 10:40 PM, Gyan Doshi wrote: Plan to push in a day if no objections. I checked some MOVs generated by Apple s/w like FCP or QT and saw that they don't set stream-specific handlers in minf. Correct way to convey handler name from input MOV to output MOV is by not updating

[FFmpeg-devel] [PATCH] avformat/mov: only set handler_name from mdia->hdlr

2018-07-14 Thread Gyan Doshi
From 125c35cb08ece825dade33b9dc7bf7babe1fc46d Mon Sep 17 00:00:00 2001 From: Gyan Doshi Date: Sat, 14 Jul 2018 13:59:51 +0530 Subject: [PATCH] avformat/mov: only set handler_name from mdia->hdlr 6 FATE references updated. Fixes #7104 --- libavformat/mo

Re: [FFmpeg-devel] [PATCH][GSOC] avfilter: added colorconstancy

2018-07-13 Thread Gyan Doshi
On 13-07-2018 02:44 PM, Mina wrote:   This patch introduces Grey-Edge algorithm as part of the Color Constancy Filter project in GSOC. Docs missing. Regards, Gyan ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] avfilter/drawtext: fix box sizing

2018-07-12 Thread Gyan Doshi
On 10-07-2018 03:31 PM, Gyan Doshi wrote: Test command: ffplay -f lavfi -i "color,\ drawtext=fontfile='arial.ttf':fontcolor=white:fontsize=H/5:\ text='A string of characters':\ box=1:boxcolor=green:boxborderw=5:\ x='w-w*t/5':y=-th+h*t/10" Pushed as 1a31c2b5df1179fdc1b8e84c8fa89d

Re: [FFmpeg-devel] mistake in patch "Add lensfun filter"

2018-07-12 Thread Gyan Doshi
On 12-07-2018 03:59 PM, Stephen Seo wrote: Yes, because it also uses a lanczos resampling implementation based on the one that exists in Lenstool, which is in the Lensfun repository and that is GPL3 while Lensfun itself is LGPL3. Correct me if I'm wrong, but I think that because of this the

Re: [FFmpeg-devel] mistake in patch "Add lensfun filter"

2018-07-12 Thread Gyan Doshi
On 12-07-2018 02:45 PM, Stephen Seo wrote: I have already added some lines in configure to not compile the filter unless --enable-version3 is also specified to configure, but thanks for checking. Just to be clear - the library is LGPL3 and your filter is meant to be GPL3. Regards, Gyan

Re: [FFmpeg-devel] [PATCH] doc/filters: add documentation to all existing OpenCL filters, except tonemap filter

2018-07-11 Thread Gyan Doshi
On 12-07-2018 04:33 AM, Mark Thompson wrote: I'm not sure I'm completely in favour of that change, anyway? The section feels more coherent to me as "OpenCL versions of other filters" rather than "all filters using OpenCL" - program_opencl/openclsrc do something really quite different.

Re: [FFmpeg-devel] [PATCH] avformat/movenc: write track data in minf->hdlr for MOV

2018-07-10 Thread Gyan Doshi
Plan to push in a day if no objections. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

  1   2   3   4   >