Height of canvas produced by drawtext varies depending on symbols in
text, so add example for printing separate texts aligned horizontally.
Wording suggested by Lou Logan
Signed-off-by: Andrey Utkin
---
Changes in v2:
* Taken the wording of example and description Lou proposed
* Added
On Tue, Nov 29, 2016 at 10:19:04AM -0900, l...@lrcd.com wrote:
> On Tue, Nov 29, 2016, at 09:55 AM, Andrey Utkin wrote:
> >
> > The point is that with more naive approach to printing parts of text,
> > using just same vertical offset (code given below), it will look fine i
On Tue, Nov 29, 2016 at 09:31:08AM -0900, l...@lrcd.com wrote:
> On Mon, Nov 28, 2016, at 07:29 AM, Andrey Utkin wrote:
> > Dimensions of canvas drawtext produces vary depending on symbols in
> > text, so add example for printing multiple texts aligned horizontally.
>
> I do
Dimensions of canvas drawtext produces vary depending on symbols in
text, so add example for printing multiple texts aligned horizontally.
Signed-off-by: Andrey Utkin
---
doc/filters.texi | 16
1 file changed, 16 insertions(+)
diff --git a/doc/filters.texi b/doc/filters.texi
On Sun, Sep 04, 2016 at 06:24:37PM +0200, Stefano Sabatini wrote:
> +A well-formed file will consists of an initial @samp{FORMAT} section,
I guess either "file will consist" or "file consists" goes here.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.
On Thu, Jul 14, 2016 at 05:27:08PM +, Carl Eugen Hoyos wrote:
> Andrey Utkin fastmail.com> writes:
>
> > It is impossible to pass "aspect" parameter to encoder from ffmpeg
> > CLI because option from lavc/options_table.h is eclipsed by option
> > with
It is impossible to pass "aspect" parameter to encoder from ffmpeg CLI
because option from lavc/options_table.h is eclipsed by option with same
name in ffmpeg_opt.c, which has different meaning (DAR, not SAR).
---
v3: added doc update
doc/codecs.texi | 3 +++
libavcodec/opti
On Wed, May 04, 2016 at 05:07:10AM +0200, Michael Niedermayer wrote:
> doesnt this require an update to teh docs ?
Indeed, thanks for commenting.
But I wonder how should I format reference to "aspect" correctly and pretty.
Now I have come up with this, which I think is not perfect. Any help is v
It is impossible to pass "aspect" parameter to encoder from ffmpeg CLI
because option from lavc/options_table.h is eclipsed by option with same
name in ffmpeg_opt.c, which has different meaning (DAR, not SAR).
---
v2: Updated tests reference results as suggested by Michael Niedermayer.
libavcode
It is impossible to pass "aspect" parameter to encoder from ffmpeg CLI
because option from lavc/options_table.h is eclipsed by option with same
name in ffmpeg_opt.c, which has different meaning (DAR, not SAR).
---
libavcodec/options_table.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/libav
On Tue, Apr 26, 2016 at 10:44:06AM +0200, Nicolas George wrote:
> I can not reproduce this with my patches. Or more precisely, I can reproduce
> it with only the second patch applied. Are you sure you tested with both
> patches applied?
Sorry, I didn't notice that both of your patches must be appl
On Mon, Apr 25, 2016 at 04:35:03PM +0200, Nicolas George wrote:
> Thanks for sending it again. I find my version is simpler, and it is
> probably closer to what it will look like when migrating to the new API. If
> that is fine with you, I would like to push it.
Your patch breaks a particular usec
This is my patch which has stuck waiting for premoderation.
- Forwarded message from Andrey Utkin -
From: Andrey Utkin
To: ffmpeg-devel@ffmpeg.org
CC: andrey_ut...@fastmail.com, Carl Eugen Hoyos , Andrey
Utkin
Date: Sun, 24 Apr 2016 16:28:38 +0300
Subject: [PATCH] concatdec: Fix
On Mon, Apr 25, 2016 at 08:58:40AM +0200, Nicolas George wrote:
> Le sextidi 6 floréal, an CCXXIV, Andrey Utkin a écrit :
> > Please look at my email in ffmpeg-devel
> > '[PATCH] concatdec: Fix handling of H.264 in MP4 in case of "-auto_convert
> > 0"&
On Sun, Apr 24, 2016 at 05:26:33PM +0200, Nicolas George wrote:
> Le sextidi 6 floréal, an CCXXIV, Derek Buitenhuis a écrit :
> > Removing this causes failures when concatdec is used to concat two H.264
> > streams from an MP4 source, when remuxed, IIRC.
> >
> > Example: https://trac.ffmpeg.org/ra
On Sun, Apr 24, 2016 at 04:28:38PM +0300, Andrey Utkin wrote:
> Bug ticket: http://trac.ffmpeg.org/ticket/5461
> This fix enables back the ability to concat appropriately encoded
> (with "-x264opts stitchable=1") MP4 files in less time, without conversion to
> mpegts and back
ering bitrace, setting "-aac_coder fast" don't
help.
You can check this yourself with this script (it is also inlined below):
https://gist.github.com/andrey-utkin/c60cd4070eb962d58075
On my workstation, the old version finishes the transcoding in 2.5s,
the new one in 6.6s.
Is ther
On Mon, 22 Feb 2016 22:11:37 +0100
Andrea Lazzarotto wrote:
> 2016-02-22 22:02 GMT+01:00 Andrey Utkin :
>
> > In yet other words, it is about defining bounds on which the
> > temporal piece of H.264 video can be cut out and correctly
> > decoded/played without any additi
On Mon, 22 Feb 2016 21:56:05 +0100
Andrea Lazzarotto wrote:
> 2016-02-22 18:23 GMT+01:00 Carl Eugen Hoyos :
>
> > Do I understand correctly that your issue is that FFmpeg
> > doesn't tell you if an I-frame in an H264 stream is an
> > IDR frame or not?
> >
>
> Is this related to the fact that
On Mon, 22 Feb 2016 20:22:30 + (UTC)
Carl Eugen Hoyos wrote:
> Andrey Utkin fastmail.com> writes:
>
> >
> > On Mon, 22 Feb 2016 17:23:06 + (UTC)
> > Carl Eugen Hoyos ag.or.at> wrote:
> >
> > > Andrey Utkin fastmail.com> write
On Mon, 22 Feb 2016 20:04:31 +0200
Andrey Utkin wrote:
> On Mon, 22 Feb 2016 17:23:06 + (UTC)
> Carl Eugen Hoyos wrote:
> > Do I understand correctly that your issue is that FFmpeg
> > doesn't tell you if an I-frame in an H264 stream is an
> > IDR frame
On Mon, 22 Feb 2016 17:23:06 + (UTC)
Carl Eugen Hoyos wrote:
> Andrey Utkin fastmail.com> writes:
>
> > As it was discussed today on #ffmpeg and #ffmpeg-devel,
> > only IDR frames are considered safe seek points by design
> > of H.264.
>
> Since va
As it was discussed today on #ffmpeg and #ffmpeg-devel, only IDR frames
are considered safe seek points by design of H.264. H.264 has two
kinds of pictures which are mapped to AV_PICTURE_TYPE_I: NAL_IDR_SLICE
and some other NAL_SLICE. H.264 referencing is arbitrary and GOP concept
is not strict, as
On Mon, 15 Feb 2016 11:40:33 +0100
Paul B Mahol wrote:
> Hi,
>
> patch attached.
I am not keen on raw data planes handling, so I could ignore something
important. Also I haven't tested this patch in runtime. Otherwise the
patch looks good.
___
ffmpeg-
doc/examples/transcoding is not able to reencode with libx264.
Please help to teach it to do so.
This script reproduces the issue in automated fashion:
https://gist.github.com/andrey-utkin/925ce227b2b530d1e808
(ffmpeg.issue.sh attached).
The script applies one patch to the example program. The
On Fri, Dec 11, 2015 at 3:02 PM, Andrey Utkin
wrote:
> On Wed, Dec 9, 2015 at 2:07 AM, Andrey Utkin
> wrote:
>> Hi! Could please anybody look at MJPEG RTP encoder issue with yuvj422p
>> https://trac.ffmpeg.org/ticket/3823#comment:17 ? This pixel format
>> becomes popular
On Wed, Dec 9, 2015 at 2:07 AM, Andrey Utkin
wrote:
> Hi! Could please anybody look at MJPEG RTP encoder issue with yuvj422p
> https://trac.ffmpeg.org/ticket/3823#comment:17 ? This pixel format
> becomes popular for IP cameras having no RTSP, and there are
> constantly issues with RT
On Wed, Dec 9, 2015 at 4:26 PM, Carl Eugen Hoyos wrote:
> On Tuesday 08 December 2015 01:10:30 pm Andrey Utkin wrote:
>> RFCs for JPEG over RTP don't support dimensions larger than pixels,
>> but it is possible to work around if we stick with information from SDP.
>
>
Hi! Could please anybody look at MJPEG RTP encoder issue with yuvj422p
https://trac.ffmpeg.org/ticket/3823#comment:17 ? This pixel format
becomes popular for IP cameras having no RTSP, and there are
constantly issues with RTPizing it. I consider donation for fixing
this.
Thanks.
--
Bluecherry de
This enables us to process pics larger than 2040 pixels in dimensions,
overcoming the limitation of RFC 2435.
Signed-off-by: Andrey Utkin
---
libavformat/rtpdec_jpeg.c | 46 +++---
1 file changed, 43 insertions(+), 3 deletions(-)
diff --git a/libavformat
Signed-off-by: Andrey Utkin
---
libavformat/rtsp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/rtsp.c b/libavformat/rtsp.c
index 39539e9..4c0a057 100644
--- a/libavformat/rtsp.c
+++ b/libavformat/rtsp.c
@@ -567,7 +567,7 @@ static void sdp_parse_line
Signed-off-by: Andrey Utkin
---
libavformat/sdp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavformat/sdp.c b/libavformat/sdp.c
index 2ab37a8..27112ef 100644
--- a/libavformat/sdp.c
+++ b/libavformat/sdp.c
@@ -657,6 +657,8 @@ static char *sdp_write_media_attributes(char *buff, int
RFCs for JPEG over RTP don't support dimensions larger than 2040 pixels, but it
is possible to work around if we stick with information from SDP.
Andrey Utkin (3):
sdp: print a=framesize for MJPEG
rtpdec_jpeg: use framesize from SDP if present
Don't forget to run SDP parsing ca
Signed-off-by: Andrey Utkin
---
doc/filters.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index fc71a99..06686bd 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -5605,7 +5605,7 @@ within the parameter list.
@item
Show the
This fixes access to Grandstream cameras, which return 401 to ffmpeg
otherwise.
VLC sends Authorization: header with spaces between parameters, and it
is known to work with Grandstream devices and broad range of other HTTP
and RTSP servers, so author considers switching to such behaviour safe.
Just
I'm working on Linux kernel driver for multimedia grabber and H264
encoder based on Techwell/Intersil 5864 chip. Of course it will be
open and pushed into upstream kernel.
The device produces H264 encoded data, but it lacks any headers. The
reference driver generates headers and glues frames toget
I'm working on Linux kernel driver for multimedia grabber and H264
encoder based on Techwell/Intersil 5864 chip. Of course it will be
open and pushed into upstream kernel repo.
The device produces H264 encoded data, but it lacks any headers. The
reference driver generates headers and glues frames
2015-04-11 0:47 GMT+03:00 Michael Niedermayer :
> can be simplified with FF_CEIL_RSHIFT
Thanks.
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
If width or height doesn't divide by 8, there are non-full blocks with
the remaining of pixels; but before this commit, RTP encoding procedure
assumed there's just w/8 by h/8 blocks.
Signed-off-by: Andrey Utkin
---
libavformat/rtpenc_jpeg.c | 4 ++--
1 file changed, 2 insertions(+), 2
If width or height doesn't divide by 8, there are non-full blocks with
the remaining of pixels; but before this commit, RTP encoding procedure
assumed there's just w/8 by h/8 blocks.
Signed-off-by: Andrey Utkin
---
libavformat/rtpenc_jpeg.c | 4 ++--
1 file changed, 2 insertions(+), 2
If width or height doesn't divide by 8, there are non-full blocks with
the remaining of pixels; but before this commit, RTP encoding procedure
assumed there's just w/8 by h/8 blocks.
Signed-off-by: Andrey Utkin
---
libavformat/rtpenc_jpeg.c | 4 ++--
1 file changed, 2 insertions(+), 2
---
libavdevice/v4l2-common.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavdevice/v4l2-common.c b/libavdevice/v4l2-common.c
index 966b9a1..196c09b 100644
--- a/libavdevice/v4l2-common.c
+++ b/libavdevice/v4l2-common.c
@@ -46,6 +46,9 @@ const struct fmt_map ff_fmt_conversion_table[]
2014-10-25 2:28 GMT+04:00 Timothy Gu :
> Those URLs are very explicit, while `/dev/` can mean anything,
> including `/dev/stdin`.
Could you elaborate what this practically means? BTW there's no "/dev"
in my patch, but "/dev
libavformat/rtsp.c-return AVPROBE_SCORE_MAX;
libavformat/rtsp.c-return 0;
libavformat/rtsp.c-}
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
---
libavdevice/v4l2.c | 8
1 file changed, 8 insertions(+)
diff --git a/libavdevice/v4l2.c b/libavdevice/v4l2.c
index cf7a92c..ebc50bb 100644
--- a/libavdevice/v4l2.c
+++ b/libavdevice/v4l2.c
@@ -806,6 +806,13 @@ static int device_try_init(AVFormatContext *ctx,
return ret;
}
+st
On Thu, Oct 23, 2014 at 10:23 PM, Michael Niedermayer wrote:
> why doesnt this write into err directly without ret ?
ffurl_open() returns >= 0 in case of success.
Positive value of err can be confusing and can lead to unexpected
behaviour, also at future changes (the modified function is quite
la
Previously, AVERROR(EIO) was returned. Now the value is passed from
lower level, thus it is possible to distinguish ECONNREFUSED, ETIMEDOUT,
ENETUNREACH etc.
---
libavformat/rtsp.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/libavformat/rtsp.c b/libavformat/rtsp.c
in
Previously, AVERROR(EIO) was returned on failure of
http_open_cnx_internal(). Now the value is passed to upper level, thus
it is possible to distinguish ECONNREFUSED, ETIMEDOUT, ENETUNREACH etc.
---
libavformat/http.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavformat/http.c b/libav
On Sat, Oct 18, 2014 at 5:16 PM, wm4 wrote:
> Why not just store the error code as separate field?
I don't think it's a good idea. Introduces special behaviour,
duplicates the objective of return codes.
--
Bluecherry developer.
___
ffmpeg-devel mailin
On Sat, Oct 18, 2014 at 1:19 AM, Carl Eugen Hoyos wrote:
> Andrey Utkin corp.bluecherry.net> writes:
>
>> Any comments and testing are appreciated. I
>> have made a little amount of testing, but RTSP,
>> HTTP and HTTPS 401 and 404 work as expected.
>
> Is the
---
libavformat/http.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/libavformat/http.c b/libavformat/http.c
index 1958a1b..d12dcaa 100644
--- a/libavformat/http.c
+++ b/libavformat/http.c
@@ -250,7 +250,7 @@ redo:
fail:
if (s->hd)
ffurl_closep(&s->hd);
-
Currently this is another name for ff_http_averror()
---
libavformat/rtspcodes.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/libavformat/rtspcodes.h b/libavformat/rtspcodes.h
index d4ae0a8..0ae490a 100644
--- a/libavformat/rtspcodes.h
+++ b/libavformat/rtspcodes.h
@@ -25,6 +25,7 @@
---
libavformat/rtsp.c| 4 ++--
libavformat/rtspdec.c | 27 ++-
libavformat/rtspenc.c | 4 ++--
3 files changed, 18 insertions(+), 17 deletions(-)
diff --git a/libavformat/rtsp.c b/libavformat/rtsp.c
index 77f03ba..1682db8 100644
--- a/libavformat/rtsp.c
+++ b/libavf
int ff_http_averror(int status_code, int default_averror)
This helper function returns AVERROR_ value from 3-digit HTTP status
code.
Second argument, default_averror, is used if no specific AVERROR_ is
available. It is introduced because in different places of code
different return codes are used
---
libavutil/error.c | 6 ++
libavutil/error.h | 7 +++
2 files changed, 13 insertions(+)
diff --git a/libavutil/error.c b/libavutil/error.c
index 9be78bc..d2868ac 100644
--- a/libavutil/error.c
+++ b/libavutil/error.c
@@ -53,6 +53,12 @@ static const struct error_entry error_entries[] =
Any comments and testing are appreciated. I have made a little amount of
testing, but RTSP, HTTP and HTTPS 401 and 404 work as expected.
Andrey Utkin (5):
Introduce new error codes for 4XX and 5XX replies from remote servers
Introduce ff_http_averror()
Use ff_http_averror()
Introduce
2014-09-29 21:06 GMT+04:00 Nicolas George :
> L'octidi 8 vendémiaire, an CCXXIII, Andrey Utkin a écrit :
>> At last I got back to this issue.
>> First I thought of adding such new error codes:
>
>> What do you think about it? Which would you prefer?
>
> I am sor
e), 5xx error
Then i had an idea that
AVERROR(EACCES) could replace AVERROR_ACCESS_DENIED, and
AVERROR(ENOENT) could replace AVERROR_RESOURCE_NOT_FOUND. The downside
of such way is inconsistence of representation of HTTP/RTSP status
codes sets.
What do you think about it? Which would you prefer?
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Thank you for your feedback.
Any more comments/advices?
Are patch submissions on this topic welcome?
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
everything, including 404 Not
Found by RTSP.
I propose to introduce more specific error codes, like
- "resource not found",
- "auth failed"
and so on.
Please let me know what you think about this.
For now, is there a reference table for possible reasons of currently
used
Konstantin, Kieran - could you please give some examples? This would
be beneficial at least for justification in commit message.
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
posed to
happen.
P. S. In my opinion the issue #2748 is not a bug. The produced stream
is perfectly OK and shouldn't break anything, probably except some
oversimplified artisanal software.
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Example of non-mappable file is /dev/stdin. Previously passing it as
graph_file value returned error.
---
libavdevice/lavfi.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/libavdevice/lavfi.c b/libavdevice/lavfi.c
index d1904dd..f1c88ac 100644
---
libavformat/avio.h| 9 +
libavformat/aviobuf.c | 18 ++
2 files changed, 27 insertions(+)
diff --git a/libavformat/avio.h b/libavformat/avio.h
index 4004b6f..9b16843 100644
--- a/libavformat/avio.h
+++ b/libavformat/avio.h
@@ -31,6 +31,7 @@
#include "libavutil/co
Thanks for comments, going to resubmit on Monday.
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2014-07-18 1:05 GMT+03:00 Nicolas George :
> Le decadi 30 messidor, an CCXXII, Andrey Utkin a écrit :
>> ---
>> doc/filters.texi | 2 +-
>> libavfilter/vf_drawtext.c | 3 ++-
>> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> IMHO, since the function
---
doc/filters.texi | 2 +-
libavfilter/vf_drawtext.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/filters.texi b/doc/filters.texi
index 8cde277..a7919a3 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@ -3916,7 +3916,7 @@ example the text size is not
Damn, was just going to resubmit :( However, the only change was to
add more comprehensive alias "expr_int_format". Do you think it's
worth to submit such addition?
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
ht
This is a replacement for previously proposed API
av_bprint_fd_contents().
Side-effect: lavfi input device now accepts any URL as "graph_file"
option value.
---
libavdevice/lavfi.c | 30 +++---
libavformat/avio.h| 8
libavformat/aviobuf.c | 16 ++
2014-07-15 21:39 GMT+03:00 Andrey Utkin :
> 2014-07-15 19:16 GMT+03:00 Nicolas George :
>> Le septidi 27 messidor, an CCXXII, Andrey Utkin a écrit :
>>> Thanks, with this change streaming HTTP MJPEG stream into browsers
>>> work (with inserting boundaries, which is eas
2014-07-15 19:16 GMT+03:00 Nicolas George :
> Le septidi 27 messidor, an CCXXII, Andrey Utkin a écrit :
>> Thanks, with this change streaming HTTP MJPEG stream into browsers
>> work (with inserting boundaries, which is easy for scripting).
>
> Can you share your test procedu
Thanks, with this change streaming HTTP MJPEG stream into browsers
work (with inserting boundaries, which is easy for scripting).
--
Andrey Utkin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
r can be up to 4 bytes in UTF-8 */
Comment not indented.
I have tested this patch, both with "--enable-libfribidi" and without.
Compiles without warnings and works as expected.
LGTM. Especially I like the fact that it handles both cases
(left-to-right and right-to-left) by itself, with
73 matches
Mail list logo
