At present, the max value for the framerate input in the abitscope filter
is 0. This leads to an error when setting any rate:
"[abitscope @ 04700500] Value 24.00 for parameter 'rate' out of
range [0 - 0]"
Replaced with INT_MAX.
Thanks,
Gyan
0001-Correct-range-for
On Thu, Mar 23, 2017 at 7:17 PM, Gyan <gyando...@gmail.com> wrote:
> At present, the max value for the framerate input in the abitscope filter
> is 0. This leads to an error when setting any rate:
>
> "[abitscope @ 04700500] Value 24.00 for parameter 'rate
On Fri, Jul 21, 2017 at 5:56 PM, Jorge Ramirez-Ortiz <
jorge.ramirez-or...@linaro.org> wrote:
> ffplay always requires user intervention via the GUI to close the
> video at the end of the file.
>
You wish to make -autoexit the default?
___
ffmpeg-devel
On Mon, Aug 7, 2017 at 11:11 PM, John Warburton
wrote:
> if an old FFmpeg script of mine breaks, as they have on a couple of
> occasions, isn't it logical for a user of the command line to go
> straight to the documentation, and the answer (and the fix) always
> seems to
Is ticket #6566 also related?
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Mon, Aug 7, 2017 at 2:38 PM, Nicolas George wrote:
>
> Also, it would help deciding stuff if you, as a user, told us: if you
> had to write "scale=w=1536:h=512" instead of "scale=1536:512" to be
> completely sure that your scripts will not break on upgrade, would you
>
On Tue, Jun 20, 2017 at 11:29 PM, Paul B Mahol wrote:
> On 12/24/16, Nicolas George wrote:
> > Le quartidi 4 nivose, an CCXXV, Michael Niedermayer a ecrit :
> >> theres a change with "-af apad=pad_len=1 -shortest" (no -vframes)
> >> the file is not
On Sat, May 27, 2017 at 9:41 PM, Kevin Mark wrote:
> I wouldn't be comfortable calling this a bug fix (or that ticket being a
> bug/defect) considering the current functionality, while not particularly
> intuitive, is consistent with the documentation.
>
The commit message
On Sat, May 27, 2017 at 7:40 PM, Kevin Mark wrote:
> Variables pertaining to the non-reference video are now available when
> using the scale2ref filter. This allows scaling a video with another
> as a reference point while maintaining the original aspect ratio of
> the
On Sun, May 28, 2017 at 8:06 PM, Kevin Mark wrote:
> Any thoughts on creating shorthand variables? I don't
> see a particular need for them but it would put these new variables in
> line with the others. mw for main_w, mh for main_h. Potentially ma for
> main_a. I don't have
On Tue, May 30, 2017 at 3:27 PM, Kevin Mark wrote:
>
> Sounds good. If my understanding is correct, you would recommend changing
> the
> scale2ref=iw/6:iw/(6*main_a) [main][ref]
> example to
> scale2ref=iw/6:iw/(6*mdar) [main][ref]
> correct?
>
I prefer
a link to SuperUser - the SE forum where FFmpeg CLI
queries are on-topic. It doesn't remove the link to the deprecated forum,
which can be done when that site closes down.
Thanks,
Gyan
0001-Added-link-to-SuperUser-forum.patch
Description: Binary data
On Sun, Jun 4, 2017 at 1:23 PM, Kevin Mark wrote:
>
> If we were to use "iw/4:-1" in place of "iw/4:ow/mdar":
> 640 / 4 = 160. So the new width for [main] would be 160.
> 360 / 4 = 90. So the new height for [main] would be 90.
> 160 / 90 = 16 / 9 so [main] now has the same
On Sat, Jun 3, 2017 at 3:24 PM, Gyan <gyando...@gmail.com> wrote:
> The support forum at
>
> http://ffmpeg.gusari.org/index.php
>
> which is linked to at
>
> http://www.ffmpeg.org/contact.html#Forums
>
> now sports a banner announcing its likely closure. The ban
On Thu, Jun 15, 2017 at 4:59 AM, wm4 wrote:
>
> > av_log(NULL, AV_LOG_WARNING,
> > "No pixel format specified, %s for H.264 encoding
> chosen.\n"
> > "Use -pix_fmt yuv420p for compatibility with
> outdated media
On Thu, Jun 15, 2017 at 4:44 PM, wm4 wrote:
> Forcing the "High" or maybe "Main" profile is enough to ensure
> compatibility.
>
Result of encoding a PNG sequence, forcing High profile, but without
-pix_fmt
-
No pixel format specified, yuv444p for H.264
On Thu, Jun 15, 2017 at 3:04 PM, wm4 wrote:
> It's wrong and dumb because the pixfmt is not enough to tell whether
> the encoder will produce a file with w widely compatible profile.
>
yuv420p is not sufficient to ensure compatibility but !yuv420p is
sufficient to ensure
On Thu, Oct 4, 2018 at 2:33 AM Dave Rice wrote:
>
>
> I attempted to add an error message but am uncertain how to access the
> width and height of the canvas used. Any advice?
>
I believe you need to call SDL_GetCurrentDisplayMode.
See https://wiki.libsdl.org/SDL_GetCurrentDi
now. I'll make any changes later on.
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
+
> +@item matrix, m
> +Set the output colorspace matrix.
> +
> +Possible value are:
> +@table @var
> +@item bt709
> +@item bt2020
> +@end table
> +
> +Default is same as input.
> +
> +@end table
> +
> +@subsection Example
> +
> +@itemize
> +@item
&
f_draw_init(>draw, inlink->format, 0);
> + ff_draw_color(>draw, >color, s->rgba_color);
> +
> +return 0;
> +}
> +
> +static const AVFilterPad tpad_inputs[] = {
> +{
> +.name = "default",
> +.type = AVMEDIA_TYPE_VIDEO,
> +.config_props = config_input,
> +},
> +{ NULL }
> +};
> +
> +static const AVFilterPad tpad_outputs[] = {
> +{
> +.name = "default",
> +.type = AVMEDIA_TYPE_VIDEO,
> +},
> +{ NULL }
> +};
> +
> +AVFilter ff_vf_tpad = {
> +.name = "tpad",
> +.description = NULL_IF_CONFIG_SMALL("Temporarily pad video
> frames."),
> +.priv_size = sizeof(TPadContext),
> +.priv_class= _class,
> +.query_formats = query_formats,
> +.inputs= tpad_inputs,
> +.outputs = tpad_outputs,
> +.activate = activate,
> +};
>
Nice. Thanks.
A couple of suggestions:
1) allow the user to supply duration as well.
2) allow cloning the nearest frame. First frame for start delay and last
frame for end padding.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> +return ret;
> +}
>
Nice filter. One unfortunate side-effect is that unused parts of the
canvas are zero-ed which in YUV formats is a shade of dark green. Users
will generally want black. Would be nice to add a color option which fills
the c
On Wed, Oct 31, 2018 at 6:11 AM Michael Niedermayer
wrote:
> On Wed, Oct 24, 2018 at 10:34:39AM +0530, Gyan wrote:
> > On Wed, Oct 24, 2018 at 3:09 AM Michael Niedermayer
>
> > wrote:
>
>
> > > +Also all needed samples for a commit should be uploaded before th
; +by ":".
> +
> +For example to specify libxavs2 encoding options with
> @option{-xavs2-params}:
> +
> +@example
> +ffmpeg -i input -c:v libxavs2 -xavs2-params preset_level=5 output.avs2
> +@end example
> +@end table
> +
> @section libxvid
>
LGTM.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
eally need to duplicate the text for the generic options? That will
lead to bloat if widely adopted.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Tue, Oct 30, 2018 at 12:00 PM Gyan wrote:
>
>
> On Mon, Oct 29, 2018 at 10:50 AM Ruiling Song
> wrote:
>
>> Signed-off-by: Danil Iashchenko
>> Signed-off-by: Ruiling Song
>> ---
>> Seems like Danil is not working on this recently.
>> So I re-
would
> break older checkouts or releases.
> +Also all needed samples for a commit should be uploaded before the commit
> is
> +pushed. Ideally 24h before.
>
Nit: merge the 2nd sentence into the first.
Also, dependant -> dependent.
Gyan
__
On Mon, Nov 5, 2018 at 9:04 PM Mark Thompson wrote:
> On 05/11/18 15:20, Gyan wrote:
> > On Mon, Nov 5, 2018 at 8:23 PM Mark Thompson wrote:
> >
> >> ---
> >> Updated to add some more explanation of the rate control mode selection.
> &
On Sun, Nov 11, 2018 at 5:00 PM Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/vf_alphamerge.c | 88 ++---
> 1 file changed, 44 insertions(+), 44 deletions(-)
>
Does this fi
el
> contains?
> I don't have a clear answer to it, so I just keep it uninitialized.
The s/w overlay filter does this to produce the output alpha:
main_alpha += (1-main_alpha) * overlay_alpha
Better to keep it consistent, IMHO.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
;,
> OFFSET(duration), AV_OPT_TYPE_DURATION, {.i64 = 0. }, 0, 6000,
> FLAGS },
>
What's the rationale for this non-standard value?
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
ally out-of-canvas
rendering?
For the former case, we may want to print a warning and reposition the
window.
If a partial window is drawable, then negative values can be valid and the
lower range bound should be INT_MIN
Also, the user can't position a wi
nterfaces, where the user can choose
> -which interface to send on by specifying the IP address of that interface.
> +Local IP address of a network interface used for sending packets or
> joining
> +multicast groups.
>
LGTM.
Gyan
___
ffmpeg-
At Michael's suggestion, earlier patch broken into two. This one stops
discarded streams from being processed. A few more checks added.
Gyan
From fef4f27c42058b40547181e45073517abc9a57ea Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Sat, 29 Dec 2018 16:17:05 +0530
Subject: [PATCH 1/2
-vn/-an/-sn/-dn now work for inputs
Gyan.
From b6efe47010cda7b9d53d7464d68f5c63d0df7ff7 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Sat, 29 Dec 2018 16:19:09 +0530
Subject: [PATCH 2/2] ffmpeg: allow disabling streams by type for inputs
-vn/-an/-sn/-dn now works for input. Streams
On 29-12-2018 04:40 PM, Gyan wrote:
-vn/-an/-sn/-dn now work for inputs
Ping.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Ping.
On 31-12-2018 10:33 AM, Gyan wrote:
On 31-12-2018 06:50 AM, Michael Niedermayer wrote:
On Sat, Dec 29, 2018 at 04:39:18PM +0530, Gyan wrote:
At Michael's suggestion, earlier patch broken into two. This one stops
discarded streams from being processed. A few more checks added.
Gyan
On 02-01-2019 10:49 AM, Gyan wrote:
On 29-12-2018 04:40 PM, Gyan wrote:
-vn/-an/-sn/-dn now work for inputs
Ping.
Plan to push tonight if no objections.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman
: Gyan Doshi
Date: Sat, 29 Dec 2018 16:19:09 +0530
Subject: [PATCH 2/2] ffmpeg: allow disabling streams by type for inputs
-vn/-an/-sn/-dn now works for input. Streams are still registered in
input_streams but they can't be automatically selected or mapped or
filtered.
---
fftools/ffmpeg_opt.c | 7
Fixes alpha extraction for sample at
https://08488297638989341201.googlegroups.com/attach/85d30cd6b8095/Circle%20Ink%20Bleed_10.mov
as seen in
ffplay -i in -vf alphaextract
Gyan
From 122f500e09b2741f3865da5c3f612ee04dcd7e21 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Thu, 17 Jan 2019
the error, so looks like a config error rather than the
conversion itself
I don't have time to trace it at present. Only wanted to get the
immediate use-case fixed.
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org
message doesn't leave them any wiser. So, add a short note (or link)
that multiple filters should be specified in a single chain, separated
by commas.
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman
From 1aa1db056e1e9887e6467a0c9e10276be78ff623 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Wed, 23 Jan 2019 13:35:23 +0530
Subject: [PATCH] avfilter/acrossfade: allow skipping fade on inputs
---
doc/filters.texi | 2 ++
libavfilter/af_afade.c | 10 +++---
2 files changed, 9
On 23-01-2019 07:40 PM, Paul B Mahol wrote:
On 1/23/19, Gyan wrote:
On 23-01-2019 03:00 PM, Paul B Mahol wrote:
On 1/23/19, Gyan wrote:
Why? afade needs change too.
If a user doesn't want to apply fade, then they can simply not add afade
filter. This change is meant for users who want
On 23-01-2019 03:00 PM, Paul B Mahol wrote:
On 1/23/19, Gyan wrote:
Why? afade needs change too.
If a user doesn't want to apply fade, then they can simply not add afade
filter. This change is meant for users who want to combine two audio
streams with overlap but don't want to apply
On 11-12-2018 02:18 PM, Gyan wrote:
On 10-12-2018 08:53 PM, Gyan wrote:
Maybe we should set a ffprobe variable in the fate Makefile, like
done for ffmpeg on ln 8.
Gyan
Will push tonight if no objections.
Pushed as 3b825b2f81e74bf9709d376f61fd1bf9a394f6ad
Gyan
On 13-12-2018 12:50 AM, Michael Niedermayer wrote:
On Wed, Dec 12, 2018 at 10:25:46AM +0530, Gyan wrote:
On 12-12-2018 03:40 AM, Michael Niedermayer wrote:
On Mon, Dec 10, 2018 at 08:57:44PM +0530, Gyan wrote:
At Michael's suggestion, this patch lets -vn/-an/-sn/-dn work for input
files
be,
-hls_ts_options movflags=+skip_sidx
This is because mp4 is a child muxer in this context. That hls option
should be renamed.
Line 790 should be patched by adding + before frag_custom
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http
On 12-12-2018 03:40 AM, Michael Niedermayer wrote:
On Mon, Dec 10, 2018 at 08:57:44PM +0530, Gyan wrote:
At Michael's suggestion, this patch lets -vn/-an/-sn/-dn work for input
files. Individual streams can still be let through e.g.
ffmpeg -an -discard:a:1 none -i file ...
will let
On 10-12-2018 08:53 PM, Gyan wrote:
Maybe we should set a ffprobe variable in the fate Makefile, like done
for ffmpeg on ln 8.
Gyan
Will push tonight if no objections.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org
| 14 +
2 files changed, 171 insertions(+), 0 deletions(-)
LGTM.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 09-12-2018 11:32 PM, Michael Niedermayer wrote:
On Sat, Dec 08, 2018 at 06:56:10PM +0530, Gyan Doshi wrote:
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
On 13-01-2019 06:39 PM, Ronald S. Bultje wrote:
Hi,
On Sun, Jan 13, 2019 at 4:39 AM Gyan wrote:
When someone submits a patch, it is implicit, unless stated otherwise,
that it is of their own initiative (and their own work), and thus they
are free to assign copyright. When work is performed
On 31-12-2018 06:50 AM, Michael Niedermayer wrote:
On Sat, Dec 29, 2018 at 04:39:18PM +0530, Gyan wrote:
At Michael's suggestion, earlier patch broken into two. This one stops
discarded streams from being processed. A few more checks added.
Gyan
[...]
diff --git a/fftools/ffmpeg_opt.c b
s there a good reason this is not already added??
>
> For some standards, this would seem to be a better solution than writing a
> different file and using the concat protocol to join the two files into a
> third file.
>
Share an example command line which will use this feature.
G
action you're
considering beyond the deadline.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Maybe we should set a ffprobe variable in the fate Makefile, like done
for ffmpeg on ln 8.
Gyan
From f1cdb3ee993602618bad243df07c0e33263cc211 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Mon, 10 Dec 2018 20:44:33 +0530
Subject: [PATCH] fate: add prog suffix in fate-mov-mp4-with-mov-in24
At Michael's suggestion, this patch lets -vn/-an/-sn/-dn work for input
files. Individual streams can still be let through e.g.
ffmpeg -an -discard:a:1 none -i file ...
will let (only) the 2nd audio stream be seen during stream selection and
filtergraph construction.
Thanks,
Gyan
From
| 14 +
2 files changed, 171 insertions(+), 0 deletions(-)
LGTM.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 26-01-2019 01:17 AM, Carl Eugen Hoyos wrote:
2019-01-25 14:02 GMT+01:00, Gyan :
On 25-01-2019 06:25 PM, Carl Eugen Hoyos wrote:
2019-01-25 13:52 GMT+01:00, Gyan :
On 25-01-2019 06:11 PM, Carl Eugen Hoyos wrote:
2019-01-25 13:35 GMT+01:00, Gyan :
+av_log(s, AV_LOG_WARNING
the log showing this? Locally, Isee that tpad does offset
the PTS of the input. I do see a bug related to the PTS for the
generated frames,
In any case, tpad is meant to be the counterpart to adelay; better to
patch it than add a new filter.
Gyan
On 26-01-2019 06:40 PM, Carl Eugen Hoyos wrote:
2019-01-26 5:42 GMT+01:00, Gyan :
On 26-01-2019 01:17 AM, Carl Eugen Hoyos wrote:
2019-01-25 14:02 GMT+01:00, Gyan :
On 25-01-2019 06:25 PM, Carl Eugen Hoyos wrote:
2019-01-25 13:52 GMT+01:00, Gyan :
On 25-01-2019 06:11 PM, Carl Eugen Hoyos
On 26-01-2019 07:49 PM, Carl Eugen Hoyos wrote:
2019-01-26 15:10 GMT+01:00, Gyan :
Try feeding a few images of different sizes to the crop
filter with reinit disabled
Sorry, not sure if I understand:
The warning you want to add is only shown if the filter reinit
was disabled by the user
On 26-01-2019 08:23 PM, Carl Eugen Hoyos wrote:
2019-01-26 15:42 GMT+01:00, Gyan :
On 26-01-2019 07:49 PM, Carl Eugen Hoyos wrote:
2019-01-26 15:10 GMT+01:00, Gyan :
Try feeding a few images of different sizes to the crop
filter with reinit disabled
Sorry, not sure if I understand
On 27-01-2019 09:57 AM, Gyan wrote:
On 26-01-2019 08:23 PM, Carl Eugen Hoyos wrote:
2019-01-26 15:42 GMT+01:00, Gyan :
On 26-01-2019 07:49 PM, Carl Eugen Hoyos wrote:
2019-01-26 15:10 GMT+01:00, Gyan :
Try feeding a few images of different sizes to the crop
filter with reinit disabled
On 28-01-2019 01:53 PM, Marton Balint wrote:
From bc08c60761df77b37c83a4c285f3ca45e5045979 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Mon, 28 Jan 2019 12:20:02 +0530
Subject: [PATCH] avformat/http: clarify that ffmpeg will attempt to add
missing CRLF
---
libavformat/http.c | 7
From bc08c60761df77b37c83a4c285f3ca45e5045979 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Mon, 28 Jan 2019 12:20:02 +0530
Subject: [PATCH] avformat/http: clarify that ffmpeg will attempt to add
missing CRLF
---
libavformat/http.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions
On 01-04-2019 10:23 AM, Gyan wrote:
On 27-03-2019 08:26 PM, Gyan wrote:
Weird. Attached corrected patch.
Thanks.
Ping.
Plan to push tomorrow evening.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman
On 01-04-2019 02:54 PM, Tomas Härdin wrote:
sön 2019-03-31 klockan 00:11 +0530 skrev Gyan:
Regression since, I believe, 42cb050a05
Sounds like there should be a test case to go along with it so it
doesn't re-regress in the future :)
Turns out there's already a test. But the command
I ran full fate and some tests failed as the ffmpeg binary wasn't found.
Suffixes weren't respected. Fixed.
I can run fate only occasionally. Maybe one of the regular FATE
submitters could set a suffix (and extension) to keep a check on this.
Thanks,
Gyan
From
, enable_global_motion, and intrabc.
Docs update missing.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject
On 02-04-2019 05:38 PM, Hendrik Leppkes wrote:
On Tue, Apr 2, 2019 at 1:27 PM Gyan wrote:
I ran full fate and some tests failed as the ffmpeg binary wasn't found.
Suffixes weren't respected. Fixed.
I can run fate only occasionally. Maybe one of the regular FATE
submitters could set a suffix
On 28-03-2019 11:04 PM, Gyan wrote:
0001-lavf-mov-skip-extradata-check-in-esds-for-MPEG-1-2-a.patch
From 7e10e1c58e69137487ff0da85caf1c350b3262ae Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Thu, 28 Mar 2019 22:59:30 +0530
Subject: [PATCH] lavf/mov: skip extradata check in esds for MPEG
On 27-03-2019 08:26 PM, Gyan wrote:
Weird. Attached corrected patch.
Thanks.
Ping.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg
On 03-04-2019 10:03 AM, Gyan wrote:
On 02-04-2019 04:57 PM, Gyan wrote:
I ran full fate and some tests failed as the ffmpeg binary wasn't
found. Suffixes weren't respected. Fixed.
I can run fate only occasionally. Maybe one of the regular FATE
submitters could set a suffix (and extension
On 02-04-2019 05:31 PM, Gyan wrote:
On 01-04-2019 02:54 PM, Tomas Härdin wrote:
sön 2019-03-31 klockan 00:11 +0530 skrev Gyan:
Regression since, I believe, 42cb050a05
Sounds like there should be a test case to go along with it so it
doesn't re-regress in the future :)
Turns out there's
On 02-04-2019 04:57 PM, Gyan wrote:
I ran full fate and some tests failed as the ffmpeg binary wasn't
found. Suffixes weren't respected. Fixed.
I can run fate only occasionally. Maybe one of the regular FATE
submitters could set a suffix (and extension) to keep a check on this.
Will push
On 03-04-2019 03:12 PM, Tomas Härdin wrote:
ons 2019-04-03 klockan 12:17 +0530 skrev Gyan:
On 02-04-2019 05:31 PM, Gyan wrote:
On 01-04-2019 02:54 PM, Tomas Härdin wrote:
sön 2019-03-31 klockan 00:11 +0530 skrev Gyan:
Regression since, I believe, 42cb050a05
Sounds like there should
Essential in avoiding loss of output streams (audio) for me, when input
has unreliable transport.
Tested with software decoding (h264, aac, mp1, mp2) pipeline.
Gyan
From ca04af063ee4a9406b6f09e12126827728aff875 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Mon, 25 Mar 2019 22:01:07 +0530
Weird. Attached corrected patch.
Thanks.
On 27-03-2019 08:19 PM, Moritz Barsnick wrote:
On Wed, Mar 27, 2019 at 18:05:32 +0530, Gyan wrote:
+@item -drop_deviant_frames (@emph{input,per-stream})
+Allows discarding decoded frames whose parameters differ from initialized
+stream parameters. May
(-)
71a87fe4d8f2efa73a3d2d9845e7aabfb75edce5
0001-ffmpeg-add-drop_deviant_frames-option.patch
From f39e3d44e1cb8108592d2241e2251d8e1506e031 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Mon, 25 Mar 2019 22:01:07 +0530
Subject: [PATCH] ffmpeg: add -drop_deviant_frames option
Decoded frames with changed
tra block prediction. This
mode is
+useful for screen content. The default value is true.
Doc for aq-mode missing.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link ab
On 02-04-2019 09:56 AM, Gyan wrote:
On 01-04-2019 10:23 AM, Gyan wrote:
On 27-03-2019 08:26 PM, Gyan wrote:
Weird. Attached corrected patch.
Thanks.
Ping.
Plan to push tomorrow evening.
Plan to push in ~2 hours.
Gyan
___
ffmpeg-devel
On 28-03-2019 05:19 PM, Stephen Hutchinson wrote:
On 3/28/2019 1:03 AM, Gyan wrote:
On 25-03-2019 01:59 AM, Stephen Hutchinson wrote:
It's been fixed both AviSynth+-side and locally.
---
doc/general.texi | 13 -
1 file changed, 13 deletions(-)
diff --git a/doc/general.texi
-1, 1, VE},
{ "enable-intrabc", "Enable intra block copy prediction mode",
OFFSET(enable_intrabc), AV_OPT_TYPE_BOOL, {.i64 = -1}, 0, 1, VE},
Shouldn't 'enable-intrabc ' follow the same pattern?
And what are the semantics of the user setting row_mt or enable-intrabc
On 30-03-2019 06:09 PM, Moritz Barsnick wrote:
On Sat, Mar 30, 2019 at 16:50:52 +0530, Gyan wrote:
And what are the semantics of the user setting row_mt or enable-intrabc
as -1?
The user doesn't set -1, they set 0 or 1 as bool. -1 helps to indicate
that nothing was set, and - in these cases
Regression since, I believe, 42cb050a05
From 22620ccaae074700c8c470a78daa7682638cecbf Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Sun, 31 Mar 2019 00:00:50 +0530
Subject: [PATCH] lavf/movenc: fix tmcd writing for non-MP4/MOV modes
write_tmcd allows tmcd track to be created with any mode
From 7e10e1c58e69137487ff0da85caf1c350b3262ae Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Thu, 28 Mar 2019 22:59:30 +0530
Subject: [PATCH] lavf/mov: skip extradata check in esds for MPEG-1/2 audio
As per 14496-3 9.D.2.2, it's not defined for these audio object types.
Fixes #7817
the note,
but add a date and revision range for the affected versions.
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org
On 01-04-2019 10:22 AM, Gyan wrote:
On 28-03-2019 11:04 PM, Gyan wrote:
0001-lavf-mov-skip-extradata-check-in-esds-for-MPEG-1-2-a.patch
From 7e10e1c58e69137487ff0da85caf1c350b3262ae Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Thu, 28 Mar 2019 22:59:30 +0530
Subject: [PATCH] lavf/mov
ilter or other in-tree mechanism at present can convey or generate it.
Are there any near-term plans to add some? If not, may I suggest that
you add a private option for supporting encoders, for users to input ROIs?
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 27-02-2019 07:07 PM, Derek Buitenhuis wrote:
On 27/02/2019 10:22, Gyan wrote:
Looks like, at present, the only way to effect ROI is via side data, and
no filter or other in-tree mechanism at present can convey or generate it.
Life exists outside of ffmpeg.c, and it's an extremely useful
On 27-02-2019 10:32 PM, Derek Buitenhuis wrote:
On 27/02/2019 13:48, Gyan wrote:
Huh. I haven't suggested removing anything.
I suggested *adding* a way for this feature to be useful for ffmpeg
users in the near-term. Who knows how long will it take for a decent
per-frame ROI filter, like
From fda793f6fa7678e36b00eeea12343f90da75bfcb Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Sat, 2 Mar 2019 20:49:12 +0530
Subject: [PATCH] configure: select rotation filters for ffmpeg
autorotate is enabled by default in ffmpeg so the rotation filters
are required and will be attempted
On 03-03-2019 03:51 AM, Michael Niedermayer wrote:
On Sat, Mar 02, 2019 at 09:03:18PM +0530, Gyan wrote:
configure |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
4b5163db4a15d9d6caaebb35d11fac16a5c64f37
0001-configure-select-rotation-filters-for-ffmpeg.patch
From
out
that the hyphen represents CLI. GUI users won't be entering the key
string, only the values*, and casual CLI users will immediately
recognize which entries pertain to options.
Gyan
*if custom text is allowed, like in myffmpeg, that's in CLI form
On 22-02-2019 06:12 AM, Lou Logan wrote:
For consistency. Fixes #7740.
Signed-off-by: Lou Logan
---
Does this need to be checked for errant added hypens, like before
entries in a value table?
If not, LGTM.
Gyan
___
ffmpeg-devel mailing list
s the correct one.
+@item hdr
+High dynamic range input. Default is 0 (disable).
"Flags input as having high dynamic range. Default is 0 (disabled)."
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
t had
been a common source of GPL violations.
Do you have citations for these violation*s*? I'm only aware of Newtek's
distribution of ffmpeg in their SDK, as reported in trac #7589. Are
there others?
>+
>+
> November 6th, 2018, FFmpeg 4.1 "al-Khwarizmi"
>
>
The changes in my review don't look to have been made.
http://www.ffmpeg.org/pipermail/ffmpeg-devel/2019-March/240931.html
Gyan
On 20-03-2019 01:14 PM, Jing Sun wrote:
Add docs for libsvt_hevc encoder in encoders.texi and general.texi
Signed-off-by: Jun Zhao
Signed-off-by: Zhengxu Huang
1 - 100 of 1666 matches
Mail list logo