> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of myp...@gmail.com
> Sent: Friday, September 28, 2018 9:51 AM
> To: FFmpeg development discussions and patches
>
> Cc: l...@chinaffmpeg.org; s...@jkqxz.net
> Subject: Re: [FFmpeg-devel] [PATCH v2] lavc/hevc: Don't parse NAL
2018-09-28 1:21 GMT+02:00, Michael Niedermayer :
> On Thu, Sep 27, 2018 at 11:56:25PM +0200, Carl Eugen Hoyos wrote:
>> 2018-09-27 23:45 GMT+02:00, Michael Niedermayer :
>>
>> > what i use is:
>> > (with gcc) --arch=x86_32 --target-os=linux --extra-cflags=-m32
>> > --extra-ldflags=-m32 --enable-cr
---
libavcodec/libaomenc.c | 60 +-
1 file changed, 54 insertions(+), 6 deletions(-)
diff --git a/libavcodec/libaomenc.c b/libavcodec/libaomenc.c
index 6a79d9b873..481338406c 100644
--- a/libavcodec/libaomenc.c
+++ b/libavcodec/libaomenc.c
@@ -50,6 +50,9 @@
From: Ronald S. Bultje
Originally written by Ronald S. Bultje, with fixes, optimizations and
improvements by James Almer.
Signed-off-by: James Almer
---
Missing Changelog entry and version bump.
configure | 4 +
libavcodec/Makefile| 1 +
libavcodec/allcodecs.c | 1 +
li
Please find my comments inlined below.
On 9/28/18 11:36 AM, Amit Kale wrote:
> If this flag is set, AVERAGE-BANDWIDTH value will be added to a master
> playlist entry. This flag implies peak_segment_bw.
Better to add a code like below to set peak segment bw flag explicitly(with
comments) in hls_i
On 9/28/18 11:33 AM, Amit Kale wrote:
> If this flag is set, BANDWIDTH value in a master playlist entry will be set
> to the peak segment bandwidth. This patch also delays freeing of hls stream
> data, so that it's available for bandwidth calculation.
This is a very useful feature. Thanks for co
Because, the URLContext of the aviocontext is null when custom IO is used,
If keepalive, that will cause the assertion to fail.
Signed-off-by: Lei He
---
libavformat/hls.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/hls.c b/libavformat/hls.c
index 8ad08baaed.
On 9/27/18 6:49 PM, Devin Heitmueller wrote:
> Hi Karthick,
>
>
>>>
>>> Another approch might be to store the wallclock frame time as some kind of
>>> metadata (as it is done for "timecode") and then add the possiblity to
>>> f_select to drop based on this. However the evaluation engine has no
On 9/28/18 2:58 AM, Marton Balint wrote:
>
>
> On Mon, 24 Sep 2018, Karthick J wrote:
>
> > From: Karthick Jeyapal
> >
> > This option is useful for maintaining input synchronization across N
> > different hardware devices deployed for 'N-way' redundancy.
> > The system time of different hardware
From: Karthick Jeyapal
This option is useful for maintaining input synchronization across N
different hardware devices deployed for 'N-way' redundancy.
The system time of different hardware devices should be synchronized
with protocols such as NTP or PTP, before using this option.
---
doc/indevs
10 matches
Mail list logo