Useful when encoding in batch or with aberrant inputs.
---
doc/ffmpeg.texi | 7 +++
fftools/ffmpeg.c | 7 ++-
fftools/ffmpeg.h | 3 +++
fftools/ffmpeg_opt.c | 24 +---
4 files changed, 37 insertions(+), 4 deletions(-)
Forgot to nullify rmax with r set.
Plan to push this in a day.
On 01-02-2021 06:52 pm, Gyan Doshi wrote:
Useful when encoding in batch or with aberrant inputs.
---
doc/ffmpeg.texi | 7 +++
fftools/ffmpeg.c | 7 ++-
fftools/ffmpeg.h | 3 +++
fftools/ffmpeg_opt.c | 24 +---
4 files
On 03-02-2021 01:41 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2021-02-01 14:22:27)
Useful when encoding in batch or with aberrant inputs.
---
doc/ffmpeg.texi | 7 +++
fftools/ffmpeg.c | 7 ++-
fftools/ffmpeg.h | 3 +++
fftools/ffmpeg_opt.c | 24
On 03-02-2021 03:20 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2021-02-03 09:15:35)
On 03-02-2021 01:41 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2021-02-01 14:22:27)
Useful when encoding in batch or with aberrant inputs.
---
doc/ffmpeg.texi | 7 +++
fftools/ffmpeg.c
Useful when encoding in batch or with aberrant inputs.
---
doc/ffmpeg.texi | 7 +++
fftools/ffmpeg.c | 7 ++-
fftools/ffmpeg.h | 3 +++
fftools/ffmpeg_opt.c | 23 ---
4 files changed, 36 insertions(+), 4 deletions(-)
diff --git a/doc/ffmpeg.texi b/doc/f
On 02-07-2020 12:33 am, Joe Ratterman wrote:
Ping.
First time contributing to this project, so I'm not sure if I missed
something?
Will apply.
Thanks,
Gyan
On Thu, May 28, 2020 at 10:32 AM Joe Ratterman wrote:
This is the only use of 'FontName' with that capitalization, as both
source
On 02-07-2020 12:49 am, Gyan Doshi wrote:
On 02-07-2020 12:33 am, Joe Ratterman wrote:
Ping.
First time contributing to this project, so I'm not sure if I missed
something?
Will apply.
Pushed as c367d14d0a5d4ce1c007f636ba85681915fd5f79
On 05-07-2020 06:35 pm, Manolis Stamatogiannakis wrote:
Some options are common between subtitles/ass filters.
Rather than mentioning for each option whether it is common or not,
the options are now displayed in two separate tables.
Signed-off-by: Manolis Stamatogiannakis
---
doc/filters.te
On 07-07-2020 04:42 pm, vectronic wrote:
On 11 May 2020, at 16:46, Gyan Doshi wrote:
On 11-05-2020 06:44 pm, vectronic wrote:
On 5 May 2020, at 06:19, Gyan Doshi wrote:
On 05-05-2020 03:16 am, vectronic wrote:
On 4 May 2020, at 17:56, Gyan Doshi wrote:
On 04-05-2020 09:54 pm
Some legacy applications such as AVI2MVE expect raw RGB bitmaps
to be stored bottom-up, whereas our RIFF BITMAPINFOHEADER assumes
they are always stored top-down and thus write a negative value
for height. This can prevent reading of these files.
Option flipped_raw_rgb added to AVI and Matroska mu
On 10-07-2020 04:36 pm, Moritz Barsnick wrote:
On Thu, Jun 25, 2020 at 18:59:58 +0800, myp...@gmail.com wrote:
On Thu, Jun 25, 2020 at 6:46 PM Moritz Barsnick wrote:
One of them can be triggered by https://samples.ffmpeg.org/F4V/H263_NM_f.mp4.
Signed-off-by: Moritz Barsnick
---
libavform
On 10-07-2020 04:40 pm, Gyan Doshi wrote:
On 10-07-2020 04:36 pm, Moritz Barsnick wrote:
On Thu, Jun 25, 2020 at 18:59:58 +0800, myp...@gmail.com wrote:
On Thu, Jun 25, 2020 at 6:46 PM Moritz Barsnick
wrote:
One of them can be triggered by
https://samples.ffmpeg.org/F4V/H263_NM_f.mp4
Plan to push in 24h.
On 08-07-2020 06:21 pm, Gyan Doshi wrote:
Some legacy applications such as AVI2MVE expect raw RGB bitmaps
to be stored bottom-up, whereas our RIFF BITMAPINFOHEADER assumes
they are always stored top-down and thus write a negative value
for height. This can prevent reading
.
See doc for |biHeight in
https://docs.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-bitmapinfoheader#members
or the end of this page
https://docs.microsoft.com/en-us/windows/win32/directshow/top-down-vs--bottom-up-dibs
Regards,
Gyan
|
On 7/14/20, Gyan Doshi wrote:
Plan to push
On 14-07-2020 05:14 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
Some legacy applications such as AVI2MVE expect raw RGB bitmaps
to be stored bottom-up, whereas our RIFF BITMAPINFOHEADER assumes
they are always stored top-down and thus write a negative value
for height. This can prevent reading
On 14-07-2020 01:29 pm, Gyan Doshi wrote:
Plan to push in 24h.
Pushed as 1ec2b3de5a074ccce555e33d7f2826d963d7
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit
On 18-07-2020 05:26 pm, Jun Zhao wrote:
From: Jun Zhao
remove the timeout option docs part for HTTP protocol and add
auth_type option part.
Signed-off-by: Jun Zhao
---
doc/protocols.texi | 27 ++-
1 file changed, 22 insertions(+), 5 deletions(-)
diff --git a/doc/
In 1ec2b3de5a, the extradata size was affected when the raster was
signaled as flipped due to user-set option rather than via extradata.
This resulted in a wrong header size being written. Fixed.
---
libavformat/riffenc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/
Will push in 12 hours.
On 25-07-2020 10:44 am, Gyan Doshi wrote:
In 1ec2b3de5a, the extradata size was affected when the raster was
signaled as flipped due to user-set option rather than via extradata.
This resulted in a wrong header size being written. Fixed.
---
libavformat/riffenc.c | 8
On 25-07-2020 11:00 pm, Gyan Doshi wrote:
Will push in 12 hours.
Pushed as 93694fe777d12a9432b5ceeb564631da6311ae26
Gyan
On 25-07-2020 10:44 am, Gyan Doshi wrote:
In 1ec2b3de5a, the extradata size was affected when the raster was
signaled as flipped due to user-set option rather than via
On 07-08-2020 07:06 pm, Jun Zhao wrote:
From: tomajsjiang
Update filter buffer/abuffer interface file name, from
libavfilter/{vsrc|asrc_buffer.h} to libavfilter/buffersrc.h
Signed-off-by: Jun Zhao
Signed-off-by: tomajsjiang
---
doc/filters.texi | 4 ++--
1 file changed, 2 insertions(+),
On 07-08-2020 07:06 pm, Jun Zhao wrote:
From: Jun Zhao
document ffmpeg -h protocol=protocol_name
Signed-off-by: Jun Zhao
---
doc/fftools-common-opts.texi | 4
1 file changed, 4 insertions(+)
diff --git a/doc/fftools-common-opts.texi b/doc/fftools-common-opts.texi
index acdaa26..2c9
On 07-08-2020 07:06 pm, Jun Zhao wrote:
From: Jun Zhao
fix typo (name => named)
Signed-off-by: Jun Zhao
---
doc/fftools-common-opts.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/fftools-common-opts.texi b/doc/fftools-common-opts.texi
index f339e0d..acda
On 09-08-2020 11:13 pm, gautamr...@gmail.com wrote:
From: Gautam Ramakrishnan
This patch updates the documentation by adding all options
for JPEG2000 encoder.
---
doc/encoders.texi | 20
1 file changed, 20 insertions(+)
diff --git a/doc/encoders.texi b/doc/encoders.te
Will apply.
On 10-08-2020 10:14 pm, gautamr...@gmail.com wrote:
From: Gautam Ramakrishnan
This patch updates the documentation by adding all options
for JPEG2000 encoder.
---
doc/encoders.texi | 36 +++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff -
On 16-08-2020 09:57 pm, Nicolas George wrote:
Marton Balint (12020-08-16):
Can we find a shorter name for the option? E.g. simply call the option
auto_conversion_filters and the user can use -noauto_conversion_filters to
disable it... In the next patch with the current name you have
-nodisable
On 14-08-2020 11:21 am, Gyan Doshi wrote:
Will apply.
Pushed as 642404f28d39cefb7857c0d77c3a4e5ac98e62c6 with minor changes.
Thanks,
Gyan
On 10-08-2020 10:14 pm, gautamr...@gmail.com wrote:
From: Gautam Ramakrishnan
This patch updates the documentation by adding all options
for
On 20-08-2020 07:08 pm, Harry Mallon wrote:
Signed-off-by: Harry Mallon
---
libavfilter/vf_libvmaf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/vf_libvmaf.c b/libavfilter/vf_libvmaf.c
index 14c3216b3a..4d49127efc 100644
--- a/libavfilter/vf_libvmaf.c
+++
On 20-08-2020 10:09 pm, Harry Mallon wrote:
Signed-off-by: Harry Mallon
---
doc/filters.texi | 2 +-
libavfilter/vf_libvmaf.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Pushed as 412d63fe72d4398d0ffd271a9bd30c6ac9fc0deb
Thanks,
Gyan
On 21-08-2020 06:05 pm, Nicolas George wrote:
1. What would you think about putting the documentation for
libavfilter/vf_foobar.c into libavfilter/doc/vf_foobar.texi instead
of into huge doc/filters.texi (25k lines!)? And same for codecs,
formats, etc.
We can adopt this for new
On 22-08-2020 04:23 pm, Nicolas George wrote:
Signed-off-by: Nicolas George
---
doc/texi2pod.pl | 9 +
1 file changed, 9 insertions(+)
diff --git a/doc/texi2pod.pl b/doc/texi2pod.pl
index 9a9b34fc15..c7f67afe8c 100644
--- a/doc/texi2pod.pl
+++ b/doc/texi2pod.pl
@@ -172,6 +172,9 @@
On 30-08-2020 05:18 am, Jim DeLaHunt wrote:
On 2020-08-29 15:10, Aman Verma wrote:
...As an aside, am I supposed to submit the revised patch in reply to
this
thread or should I submit it as a new thread? This is my first time
contributing to a project that uses mailing lists.
The instructi
On 03-09-2020 04:27 am, Andrei Rybak wrote:
Expressions for parameter fontsize of video filter drawtext have been
supported since commit 6442e4ab3c (avfilter/vf_drawtext: added expr
evaluation to drawtext fontsize, 2017-04-18).
Add an example of using such expressions to documentation.
Revis
In the open ticket 7089, I reported that (terminal) filters with
unlabelled output pads are automatically forwarded to the first output
file and ordered before any expressly mapped streams. There's no warning
issued.
Is this behaviour intended?
In the section on filtergraph syntax @
https
On 5/10/2018 11:17 PM, Marton Balint wrote:
Maybe it is better if we simply get rid of the "probing" part, so the
user would have to explicitly specify the demuxer to use them.
+1
Maybe shift such probes to inside a block and add a new generic lavf
option to set whether such probes are en
On 5/11/2018 3:08 PM, Nicolas George wrote:
Note that the behaviour when explicit -map options are present: when
they are, automatic selection of "best" input streams is disabled, and
it would seem logical that automatic selection of unlabelled filter
outputs would be disabled too. I would not
On 5/14/2018 11:41 AM, Karthick J wrote:
Right now segment file format is chosen to be either mp4 or webm based on the
codec format.
This patch makes that choice configurable by the user, instead of being decided
by the muxer.
Can you update the docs to reflect on the differences between u
From 20a0544d66b5b3b9ebc3e03049a134d13706bda9 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Wed, 16 May 2018 20:18:30 +0530
Subject: [PATCH] cmdutils - don't search for option 'default'
The option 'default' was removed in
af4b1c02acf6923489d30349c4813a0d73b2f114 -
On 5/17/2018 2:19 PM, Michael Niedermayer wrote:
On Wed, May 16, 2018 at 09:21:49PM +0530, Gyan Doshi wrote:
cmdutils.c |2 --
1 file changed, 2 deletions(-)
495ccaae10f8873dc5070858d11c0c3093ce92b4
0001-cmdutils-don-t-search-for-option-default.patch
From
On 5/18/2018 2:08 PM, Hendrik Leppkes wrote:
You can avoid that by using a relative path to the samples. FATE does
not properly quote/escape pathes for windows absolute pathes to work.
That works. 0 fails.
Thanks,
Gyan
___
ffmpeg-devel mailing list
On 5/18/2018 7:04 AM, Michael Niedermayer wrote:
make: *** [fate-mpegts-probe-pmt-merge] Error 1
make: *** [fate-concat-demuxer-simple1-lavf-mxf_d10] Error 1
make: *** [fate-concat-demuxer-extended-lavf-mxf_d10] Error 1
make: *** [fate-concat-demuxer-simple1-lavf-mxf] Error 1
make: *** [fate-c
On 5/18/2018 6:50 PM, Devin Heitmueller wrote:
Is this something anyone is actively looking into? If not, I'll dig into it and see
about respecting program membership in ffmpeg's selection algorithm. My larger concern
is that with MPEG-TS streams, the commonly accepted heuristic is to play
Hi Devin,
On 5/18/2018 9:17 PM, Devin Heitmueller wrote:
Indeed when I dug into the code it became clear that there is added complexity when multiple input files are involved, if for no other reason than it’s not immediately clear which input stream comes from which file and hence it’s difficult
Stream Selection chapter rewritten to be more comprehensive and
illustrative.
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
Flesh out with details and
On 25-05-2018 06:08 AM, Michael Niedermayer wrote:
This is very detailed. I think this could byte us if we want to change some
of the logic.
The current chapter already does. Many askers at SE sites and even on
the User ML show confusion over command line operation, including stream
select
On 24-05-2018 09:58 PM, Carl Eugen Hoyos wrote:
Because of the length of the new description I wonder if the
existing documentation should be kept as a "short version"
or similar.
Parts of the short version which are accurate have been retained; other
parts are incomplete or misleading and
Hi Lou,
Most sectioning and formatting suggestions applied locally.
On 26-05-2018 03:50 AM, Lou Logan wrote:
Examples are often * itemized by convention, but the resulting text
justification such verbose examples makes them hard to read in HTML
format. I would ditch the itemization.
Part of
On 27-05-2018 02:37 AM, Lou Logan wrote:
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
On 27-05-2018 07:59 PM, Moritz Barsnick wrote:
This is incorrect, as it already was before. It doesn't disable
*automatic* stream selection, it rather disables mapping any of these
stream types at all, *even* if explictly mapped. (IOW: "-vn -map 0:v"
never gets you any video stream in the outp
doc/general.texi says this for the FDK AAC library,
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL and is not known to be compatible to the LGPL. Therefore, you
have to pass @code{--enable-nonfree} to configure to use it."
(added 2013 in 6fe419bf73)
LICENSE
On 29-05-2018 03:34 AM, Carl Eugen Hoyos wrote:
Just remove "and is not known...", please don't state that you guarantee
they are compatible.
If we are continuing to permit LGPL compilation, shouldn't it be
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL. Th
On 30-05-2018 04:57 AM, Carl Eugen Hoyos wrote:
2018-05-27 6:16 GMT+02:00, Gyan Doshi :
v2 attached.
+In the absence of any map options for a particular output file, ffmpeg
inspects the output
+format to check which type of streams can be included in it, viz. video, audio
and/or
Sorry
On 30-05-2018 04:39 AM, Lou Logan wrote:
The subject nit still exists.
Fixed locally.
Using an itemized list here will look better in my opinion.
@itemize
@item
for video, it is the stream with the highest resolution,
@item
...
@end itemize
Changed.
+@subsubheading Example: automatic s
On 31-05-2018 04:35 AM, Michael Niedermayer wrote:
If a user consults the relevant parts of the documentation before execution,
they should be able to predict how the program will behave. If they do it
afterwards, they should understand what the program did. Even though FFmpeg
is an open sourc
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL. Therefore, for GPL builds, you have to pass
@code{--enable-nonfree} to configure to use it. To the best of our
knowledge, it is compatible with the LGPL" ?
Will push in a day with above changes.
Gyan
__
On 31-05-2018 02:00 AM, Lou Logan wrote:
On Tue, May 29, 2018, at 9:43 PM, Gyan Doshi wrote:
Works when "--init-file=doc/t2h.pm" is omitted. Didn't investigate further.
make uses the init file here. makeinfo is texi2any 6.3
makeinfo --html -I doc --no-split -D config-
On 31-05-2018 11:57 PM, Lou Logan wrote:
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,
From 525f2422bc2b0544fce59031b8995c4e13fd813c Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Fri, 1 Jun 2018 16:14:02 +0530
Subject: [PATCH] lavc/libx265: allow users to set closed GOP via generic lavc
flag
lavc flag 'cgop' can be used to set closed GOP.
---
libavcodec/lib
On 01-06-2018 06:45 PM, Derek Buitenhuis wrote:
What is the default setting? If it is setting open GOP by default,
I think this is a bad idea.
x265's default setting is open GOP. lavc's default is open as well.
Regards,
Gyan
___
ffmpeg-devel maili
On 01-06-2018 07:08 PM, Derek Buitenhuis wrote:
On Fri, Jun 1, 2018 at 2:25 PM, Gyan Doshi wrote:
x265's default setting is open GOP. lavc's default is open as well.
LGTM then.
- Derek
Thanks. Will push soon.
Gyan
___
ffmpeg-dev
On 01-06-2018 01:16 PM, Gyan Doshi wrote:
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 independent issue.
Ok. Will push in a day or so.
Thanks,
Gyan
Revised
On 06-06-2018 12:05 PM, Roger Pack wrote:
FWIW. It might be compatible with the LGPL.
configure, at present, allows all libraries in the nonfree list to be
built with the LGPL license without having to pass --enable-nonfree. Is
that intended?
Libav's script disables them if the flag isn'
On 31-05-2018 11:03 AM, Gyan Doshi wrote:
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL. Therefore, for GPL builds, you have to pass
@code{--enable-nonfree} to configure to use it. To the best of our
knowledge, it is compatible with the LGPL"
From 91d98675cc85bd78e46971f9e5d3708245345654 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Thu, 7 Jun 2018 23:15:35 +0530
Subject: [PATCH] ffmpeg: sseof is marked as an input-only option
---
doc/ffmpeg.texi | 2 +-
fftools/ffmpeg_opt.c | 2 +-
2 files changed, 2 insertions(+), 2
From 5d3ab077f46fe14eaf5aa1246f975d847cf85e29 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Sun, 10 Jun 2018 20:18:10 +0530
Subject: [PATCH] avformat: remove unused MP4A_LATM flag
A generic lavf option for AAC LATM packetization for the RTP muxer was
added in ef409645f0 and then made inert 20
On 10-06-2018 10:01 PM, morten.w...@gmail.com wrote:
+@item -toeof @var{position} (@emph{input})
+Stop writing the output at @var{position} relative to the "end of file". That
is negative
+values are later in the file, 0 is at EOF.
Should be,
"Stop reading the input at @var{position} rel
On 10-06-2018 11:28 PM, Marton Balint wrote:
end of file is misleading, you are simply using the input duration as
far as I see. So write that in the help text. Also what happens if the
output is generated from multiple inputs?
This is the counterpart to `to` as -sseof is to -ss.
This is
On 10-06-2018 10:01 PM, morten.w...@gmail.com wrote:
+if (o->stop_time_eof != AV_NOPTS_VALUE) {
+if (ic->duration>0) {
+o->recording_time = ic->duration + o->stop_time_eof;
+} else
+av_log(NULL, AV_LOG_WARNING, "Cannot use -toeof, duration of %s no
On 12-06-2018 12:48 AM, Morten With wrote:
commit message to "stop reading"), here is the revised patch attached.
Maybe I missed it, but in the new patch, you don't vet ss against toeof
i.e. for a 10-second file, -ss 7 -toeof -4 should be declared invalid.
Also, this isn't an issue with
Will push tomorrow.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 12-06-2018 01:39 PM, Hendrik Leppkes wrote:
This flag is part of the public API, and eventhough it is entirely
unused, you cannot remove public API without a proper deprecation
period.
Ok, so looking at older flags, I need to
add a define to version.h, something like
#ifndef FF_API_LAVF
On 12-06-2018 11:00 PM, James Almer wrote:
Is that correct?
I assume the other changes can be committed as-is.
Yes, that should do it.
Revised and pushed.
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mail
Default for both parameters in both libs is 0.
Regards,
Gyan
From f875734cc5a1652162156118864db406b192526b Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Wed, 13 Jun 2018 19:01:17 +0530
Subject: [PATCH] avcodec/libx265: apply lavc maxrate and bufsize
CLI options -maxrate and -bufsize are now
On 13-06-2018 07:08 PM, Gyan Doshi wrote:
Default for both parameters in both libs is 0.
Ping.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
The recently added qt-faststart references the tool using $(PROGSSUF).
However, that tool isn't built with the suffix when supplied, and so the
test fails for me. Patch fixes it.
From df8ac19a005524bc152c9fae53b4dddc29dc9257 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Fri, 15 Jun 20
On 16-06-2018 01:11 AM, Michael Niedermayer wrote:
tested with mingw64+wine and qemu-mips, seems to work
thx
Pushed.
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Activates functionality added a few years ago.
Regards,
Gyan
From bead9f22630f2b8efc4a3859568cb0fc46102dd3 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Sat, 16 Jun 2018 15:31:51 +0530
Subject: [PATCH] avformat/movenc: read track title from correct key
da9cc22d5bd allowed the MOV muxer to
On 17-06-2018 01:23 AM, John Stebbins wrote:
On 06/16/2018 03:49 AM, Gyan Doshi wrote:
Activates functionality added a few years ago.
Regards,
Gyan
FYI, HandBrake has been using the "handler" metadata key since 2014 when I
added this code. And it was completely self-consistent
On 15-06-2018 09:50 PM, Gyan Doshi wrote:
On 13-06-2018 07:08 PM, Gyan Doshi wrote:
Default for both parameters in both libs is 0.
Ping.
Will push in a day.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo
: Gyan Doshi
Date: Mon, 18 Jun 2018 12:09:54 +0530
Subject: [PATCH v2] avcodec/libx265: apply lavc maxrate, bufsize &
rc_init_occupancy
CLI options -maxrate, -bufsize and -rc_init_occupancy can now be picked
up by the x265 wrapper. Min. rc init has to be 1001 to avoid x265
setting it to vbv-buf
Fixes #7262.
Requires https://patchwork.ffmpeg.org/patch/9420/ to be applied first.
Regards,
Gyan
From bc208828dc7c9456550c1b27e7540b2b03be817e Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Mon, 18 Jun 2018 19:52:20 +0530
Subject: [PATCH 2/2] avformat/movenc: allow hdlr name field to be
On 17-06-2018 10:07 AM, Gyan Doshi wrote:
Just need to make a note to myself to fix HandBrake when we
update to a version of ffmpeg with the change.
I can just use an if-else to check for both, giving priority to 'handler'.
When I wrote the above, I didn't realize tha
On 18-06-2018 12:13 PM, Gyan Doshi wrote:
On 17-06-2018 09:11 PM, Mark Thompson wrote:
Given you have these two, maybe set vbvBufferInit from
rc_initial_buffer_occupancy as well?
LGTM in either case.
Revised patch attached. Will apply by tonight.
Gyan
Pushed
On 18-06-2018 11:17 PM, John Stebbins wrote:
Will push in a day as-is if there are no objections.
No objections from me. Was only making sure you had full information about the
history of this code.
Pushed.
Regards,
Gyan
___
ffmpeg-devel ma
On 20-06-2018 03:02 AM, Carl Eugen Hoyos wrote:
if (mov->empty_hdlr_name)
descr= "";
Changed locally.
Thanks,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 20-06-2018 01:25 PM, Ibrahim Tachijian wrote:
If the diff is > 1 then I am considering the audio to be out of sync and
restart the process. Is this correct ? Is it not? Why?
Of course the best way is to implement something directly into ffmpeg.
Have you tried inserting the aresample f
On 20-06-2018 10:08 AM, Gyan Doshi wrote:
On 20-06-2018 03:02 AM, Carl Eugen Hoyos wrote:
if (mov->empty_hdlr_name)
descr= "";
Changed locally.
Will push tomorrow.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http
On 20-06-2018 09:54 PM, Gyan Doshi wrote:
Will push tomorrow.
Pushed.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 21-06-2018 09:40 PM, Michael Niedermayer wrote:
how does the user know which is which output ?
also some users may want just one line summarizing all
Agreed. Better if each line is identified.
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg
On 22-06-2018 03:29 AM, Carl Eugen Hoyos wrote:
(musl 32bit is unsupported which we are not allowed to
document
Why is this?
Regards,
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Sorry; ignore this email.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
From 91d98675cc85bd78e46971f9e5d3708245345654 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Thu, 7 Jun 2018 23:15:35 +0530
Subject: [PATCH] ffmpeg: sseof is marked as an input-only option
---
doc/ffmpeg.texi | 2 +-
fftools/ffmpeg_opt.c | 2 +-
2 files changed, 2 insertions(+), 2
From 326e15dcfc3ddb1d9b8fd06a5806807917f56669 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Fri, 22 Jun 2018 22:02:16 +0530
Subject: [PATCH] fftools/ffmpeg: check sseof value and clash with ss
Prioritize -ss
---
fftools/ffmpeg_opt.c | 11 ++-
1 file changed, 10 insertions(+), 1
Added another check and corrected an oversight in a log message.
From f013a502c438ef9940fc131cad9bf870853adb5f Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Fri, 22 Jun 2018 22:02:16 +0530
Subject: [PATCH v2] fftools/ffmpeg: check sseof value and clash with ss
Prioritize -ss
---
fftools
Will push in a day if no comments.
(fixed the missing loglevel locally)
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
n
From ca9d51bca4cb303897bf32ff3900fa36f3cf7074 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Fri, 22 Jun 2018 22:02:16 +0530
Subject: [PATCH v2] fftools/ffmpeg: check sseof value and clash with ss
Prioritize -ss
---
fftools/ffmpeg_opt.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/f
On 25-06-2018 10:07 AM, Gyan Doshi wrote:
Revised. Will push soon.
Thanks,
Gyan
Pushed in a0ac49e38ee1d1011c394d7be67d0f08b2281526
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Many users have queried/complained about the 'Past duration too large'
messages.
Regards,
Gyan
From 9e265308865455c4a61b0cb65840466b4d575670 Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Tue, 26 Jun 2018 15:42:04 +0530
Subject: [PATCH] fftools/ffmpeg: add option to hide vsync warn
On 26-06-2018 04:29 PM, Marton Balint wrote:
Many users have queried/complained about the 'Past duration too large'
messages.
If the message is useless, then why not remove it entirely?
Good question. Don't see the point but Michael added it (4e20e94921) so
may have some use for it that I
On 27-06-2018 06:33 AM, Marton Balint wrote:
Maybe we should disable the message for CFR only?
First question is, who is the message meant for? End-users can't do
anything with it. At most, a one-time message is fine, similar to the
"More than 1000 frames duplicated" message.
Regards,
G
701 - 800 of 1398 matches
Mail list logo
