> On 22 Dec 2017, at 15:04, Karthick J wrote:
>
> From: Karthick Jeyapal
>
> Currently http end of chunk is called implicitly in hlsenc_io_open().
> This mean playlists http writes would have to wait upto a segment duration to
> signal end of chunk causing delays.
> This patch will fix that p
From: Karthick Jeyapal
---
libavformat/http.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/libavformat/http.c b/libavformat/http.c
index cf86adc..4635a9a 100644
--- a/libavformat/http.c
+++ b/libavformat/http.c
@@ -307,9 +307,11 @@ int ff_http_do_new_request(URLCon
From: Karthick Jeyapal
Currently http end of chunk is signalled implicitly in hlsenc_io_open().
This mean playlists http writes would have to wait upto a segment duration to
signal end of chunk causing delays.
This patch will fix that problem and improve performance.
---
libavformat/hlsenc.c |
On 12/22/17, 1:13 PM, "wm4" wrote:
>
>On Fri, 22 Dec 2017 12:34:41 +0530
>Karthick J wrote:
>
>> From: Karthick Jeyapal
>>
>> Right now there is no explicit way to signal end of chunk, when
>> http_multiple is set.
>> ff_http_do_new_request() function implicitly signals end of chunk. But tha
>On 12/22/17, 2:06 PM, "刘歧" wrote:
>
>> On 22 Dec 2017, at 15:04, Karthick J wrote:
>>
>> From: Karthick Jeyapal
>>
>> Currently http end of chunk is called implicitly in hlsenc_io_open().
>> This mean playlists http writes would have to wait upto a segment duration
>> to signal end of chun
Signed-off-by: Paul B Mahol
---
libavfilter/vf_lut.c | 6 +-
tests/ref/fate/filter-pixfmts-lut | 5 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/libavfilter/vf_lut.c b/libavfilter/vf_lut.c
index 11c039ead7..26f2945c84 100644
--- a/libavfilter/vf_lut.c
+++
On 12/19/17 11:53 AM, 刘歧 wrote:
> On 19 Dec 2017, at 14:09, vdi...@akamai.com wrote:
>> From: Vishwanath Dixit
>>
>> ---
>> doc/muxers.texi | 12 +
>> libavformat/dashenc.c | 3 ++-
>> libavformat/hlsenc.c | 64
>> ---
>> libavf
> On 22 Dec 2017, at 19:05, Dixit, Vishwanath wrote:
>
> On 12/19/17 11:53 AM, 刘歧 wrote:
>> On 19 Dec 2017, at 14:09, vdi...@akamai.com wrote:
>>> From: Vishwanath Dixit
>>>
>>> ---
>>> doc/muxers.texi | 12 +
>>> libavformat/dashenc.c | 3 ++-
>>> libavformat/hlsenc.c
On 2017-12-22 10:57, Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/vf_lut.c | 6 +-
> tests/ref/fate/filter-pixfmts-lut | 5 +
> 2 files changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/libavfilter/vf_lut.c b/libavfilter/vf_lut.c
> index 11c0
Hello Michael,
I fixed the things you mentioned. New patch attached.
Felix
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, 21 Dec 2017 10:32:50 -0900, Lou Logan wrote:
> On Thu, Dec 21, 2017, at 4:07 AM, Carl Eugen Hoyos wrote:
> > Where was this agreed upon?
> >
> > Carl Eugen
>
> I did not assume further discussion was required for this subject, but I am
> confident that the vast majority of developers w
From: Misty De Meo
Most of the constants in libavcodec/oma aren't specific to
libavformat; moving them into libavcodec makes them available to
libavcodec as well as keeping them compatible with libavformat.
ff_oma_codec_tags uses a libavformat-specific type, so it has been
left in libavformat.
-
From: Misty De Meo
MPS files are MPEG files used on PSP Video discs. They lack
the PSMF header used by .pms files, and so the special casing
in the original patch fails to support their audio. This patch
fixes this by unconditionally reading a new byte for the startcode
for PRIVATE_STREAM_1 secti
From: Misty De Meo
---
libavformat/mpeg.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat/mpeg.c b/libavformat/mpeg.c
index a366ece0ed..210424faf3 100644
--- a/libavformat/mpeg.c
+++ b/libavformat/mpeg.c
@@ -547,8 +547,8 @@ redo:
len--;
for (
From: Misty De Meo
This is based on Maxim Poliakovski's patch from this 2014 email:
https://ffmpeg.org/pipermail/ffmpeg-devel/2014-December/166169.html
This patchset is updated based on Michael Niedermayer's feedback. I've
also included an improvement which ensures support for Sony .MPS MPEG
fil
From: Maxim Poliakovski
---
libavcodec/Makefile| 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/atrac3plus_parser.c | 153 +
libavformat/mpeg.c | 27 +++-
4 files changed, 181 insertions(+), 1 deletion(-)
create mod
On Fri, Dec 22, 2017, at 10:34 AM, Felix Matouschek wrote:
> Hello Michael,
>
> I fixed the things you mentioned. New patch attached.
>
> Felix
I think you forgot to attach the patch.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.
From: Misty De Meo
---
libavcodec/Makefile| 2 +-
libavcodec/atrac3plus_parser.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/Makefile b/libavcodec/Makefile
index e0e3f1ebac..0e1c6d53ea 100644
--- a/libavcodec/Makefile
+++ b/libavcodec/Makefile
@@
On Fri, 22 Dec 2017 22:35:08 +0800
mi...@brew.sh wrote:
> From: Misty De Meo
>
> Most of the constants in libavcodec/oma aren't specific to
> libavformat; moving them into libavcodec makes them available to
> libavcodec as well as keeping them compatible with libavformat.
>
> ff_oma_codec_tags
Am 22.12.2017 20:50, schrieb Lou Logan:
I think you forgot to attach the patch.
Sorry, flaky mail client... attached it again.From ba2ccca1200a55b0f1c0331ebd6d26324941fb2e Mon Sep 17 00:00:00 2001
From: Felix Matouschek
Date: Fri, 22 Dec 2017 20:10:41 +0100
Subject: [PATCH] avdevice: add andr
On Fri, 22 Dec 2017 14:39:40 -0500, Compn wrote:
> carl if you have a suggestion for better wording, please send patch ?
also as the other ml admin, i agree with lou's commit and
community agreed upon policy change.
what discussions do you want to have on -cvslog that would not be
better heard
This removes the XP compatibility code, and switches entirely to SWR
locks, which are available starting at Windows Vista.
This removes CRITICAL_SECTION use, which allows us to add
PTHREAD_MUTEX_INITIALIZER, which will be useful later.
Windows XP is hereby not a supported build target anymore. It
On Fri, 22 Dec 2017 23:17:21 +0100
wm4 wrote:
> This removes the XP compatibility code, and switches entirely to SWR
> locks, which are available starting at Windows Vista.
>
> This removes CRITICAL_SECTION use, which allows us to add
> PTHREAD_MUTEX_INITIALIZER, which will be useful later.
>
>
On Wed, Dec 20, 2017 at 11:36 AM, Aman Gupta wrote:
>
>
> On Sun, Dec 17, 2017 at 1:13 PM, Anssi Hannula
> wrote:
>
>> Aman Gupta kirjoitti 2017-12-17 22:41:
>>
>>> On Sun, Dec 17, 2017 at 12:34 PM Anssi Hannula
>>> wrote:
>>>
>>> Hi!
Aman Gupta kirjoitti 2017-12-13 02:35:
> From
From: Aman Gupta
---
libavformat/internal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/internal.h b/libavformat/internal.h
index 36a57214ce..aac566aace 100644
--- a/libavformat/internal.h
+++ b/libavformat/internal.h
@@ -542,7 +542,7 @@ static inline int ff_r
just use lrint(lrint(duration * 10.0) / 10.0)
fix ticket: 6915
Suggested-by: beloko
Signed-off-by: Steven Liu
---
libavformat/dashenc.c | 2 +-
libavformat/hlsenc.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavformat/dashenc.c b/libavformat/dashenc.c
index 5368a23
On Fri, 22 Dec 2017 15:17:33 -0800
Aman Gupta wrote:
> From: Aman Gupta
>
> ---
> libavformat/internal.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/internal.h b/libavformat/internal.h
> index 36a57214ce..aac566aace 100644
> --- a/libavformat/internal.
On Thu, 15 Jun 2017 15:50:31 -0400
"Ronald S. Bultje" wrote:
> From: Anton Mitrofanov
>
> Use the correct ctxIdxInc calculation for coded_block_flag.
> Keep old behavior for old versions of x264 for backward compatibility.
>
> Signed-off-by: Ronald S. Bultje
> ---
> libavcodec/h264_cabac.c |
On Thu, Dec 21, 2017 at 11:22:21PM +0100, wm4 wrote:
> Use static mutexes instead of requiring a lock manager. The behavior
> should be roughly the same before and after this change for API users
> which did not set the lock manager at all (except that a minor memory
> leak disappears).
> ---
> do
On Sat, 23 Dec 2017 02:25:11 +0100
Michael Niedermayer wrote:
> On Thu, Dec 21, 2017 at 11:22:21PM +0100, wm4 wrote:
> > Use static mutexes instead of requiring a lock manager. The behavior
> > should be roughly the same before and after this change for API users
> > which did not set the lock ma
On 12/22/2017 10:25 PM, Michael Niedermayer wrote:
> On Thu, Dec 21, 2017 at 11:22:21PM +0100, wm4 wrote:
>> Use static mutexes instead of requiring a lock manager. The behavior
>> should be roughly the same before and after this change for API users
>> which did not set the lock manager at all (ex
On Fri, Dec 22, 2017 at 3:37 PM, wm4 wrote:
> On Fri, 22 Dec 2017 15:17:33 -0800
> Aman Gupta wrote:
>
> > From: Aman Gupta
> >
> > ---
> > libavformat/internal.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libavformat/internal.h b/libavformat/internal.h
> >
This provides a generic way to the API user to deal with files that
either lack this SEI, or which have the SEI only in packets not passed
to the decoder (such as the common case of the SEI being in the very
firsat video packet, but decoding is started somewhere in the middle of
the file). Bugs lik
From: Misty De Meo
Most of the constants in libavcodec/oma aren't specific to
libavformat; moving them into libavcodec makes them available to
libavcodec as well as keeping them compatible with libavformat.
ff_oma_codec_tags uses a libavformat-specific type, so it has been
left in libavformat.
-
From: Misty De Meo
Thanks for the feedback! I checked in with #ffmpeg-devel on IRC, and
they suggested simply making them static consts in the headers since
they're small enough. Updated patch is included.
Misty De Meo (1):
oma: move some constants into libavcodec
Changelog
2017-12-22 19:30 GMT+08:00 刘歧 :
>
>
>> On 22 Dec 2017, at 19:05, Dixit, Vishwanath wrote:
>>
>> On 12/19/17 11:53 AM, 刘歧 wrote:
>>> On 19 Dec 2017, at 14:09, vdi...@akamai.com wrote:
From: Vishwanath Dixit
---
doc/muxers.texi | 12 +
libavformat/dashenc.c
36 matches
Mail list logo
