2017-02-09 19:10 GMT+08:00 Steven Liu :
> When user use the hls_wrap, there have many problem:
> 1. some platform refersh the old but usefull segment
> 2. CDN(Content Delivery Network) Deliver HLS not friendly
>
> The hls_wrap is used to wrap segments for use little space,
>
2017-02-11 11:14 GMT+08:00 Michael Niedermayer :
> On Fri, Feb 10, 2017 at 04:43:17PM -0300, James Almer wrote:
> > On 2/10/2017 4:03 PM, Michael Niedermayer wrote:
> > > Hi community
> > >
> > > what do you prefer about the ffmpeg-security alias ?
> > > in no particular
On Fri, Feb 10, 2017 at 04:43:17PM -0300, James Almer wrote:
> On 2/10/2017 4:03 PM, Michael Niedermayer wrote:
> > Hi community
> >
> > what do you prefer about the ffmpeg-security alias ?
> > in no particular order
> >
> > Should everyone on the alias be listed in MAINTAINERs under a
> >
On 2/10/2017 10:18 PM, Michael Niedermayer wrote:
> On Fri, Feb 10, 2017 at 07:52:11PM -0300, James Almer wrote:
>> Signed-off-by: James Almer
>> ---
>> tests/fate/avformat.mak | 1 +
>> tests/lavf-regression.sh | 4
>> tests/ref/lavf/wv| 3 +++
>> 3 files
On Fri, Feb 10, 2017 at 05:21:00PM -0500, Vittorio Giovara wrote:
> In particular cases, it is possible to initialize top_field_first
> but not interlaced_frame. Make sure to correctly tag a frame
> as interlaced when this happens.
>
> Signed-off-by: Vittorio Giovara
On 11 February 2017 at 01:22, James Almer wrote:
> On 2/10/2017 9:25 PM, Rostislav Pehlivanov wrote:
> > Handles strides (needed for Opus transients), does pre-reindexing and
> folding
> > without needing a copy.
> >
> > Signed-off-by: Rostislav Pehlivanov
On 11 February 2017 at 01:26, Rostislav Pehlivanov
wrote:
>
>
> On 11 February 2017 at 01:22, James Almer wrote:
>
>> On 2/10/2017 9:25 PM, Rostislav Pehlivanov wrote:
>> > Handles strides (needed for Opus transients), does pre-reindexing and
>> folding
On Fri, Feb 10, 2017 at 05:16:52PM +0530, Mulvya V wrote:
> Hi,
>
> Attached patch will document the options to list demuxers and muxers
>
> Regards,
> Mulvya
> demuxers.texi|5 +++--
> ffmpeg.texi |2 +-
> fftools-common-opts.texi |6 ++
> muxers.texi
On 2/10/2017 9:25 PM, Rostislav Pehlivanov wrote:
> Handles strides (needed for Opus transients), does pre-reindexing and folding
> without needing a copy.
>
> Signed-off-by: Rostislav Pehlivanov
> ---
> configure| 6 +-
> libavcodec/Makefile
On Fri, Feb 10, 2017 at 07:52:11PM -0300, James Almer wrote:
> Signed-off-by: James Almer
> ---
> tests/fate/avformat.mak | 1 +
> tests/lavf-regression.sh | 4
> tests/ref/lavf/wv| 3 +++
> 3 files changed, 8 insertions(+)
> create mode 100644 tests/ref/lavf/wv
This is meant to be applied on top of my previous patch which
split PVQ into celt_pvq.c and made opus_celt.h
Essentially nothing has been changed other than renaming CeltFrame
to CeltBlock (CeltFrame had absolutely nothing at all to do with
a frame) and CeltContext to CeltFrame.
3 variables have
A huge amount can be reused by the encoder, as the only thing
which needs to be done would be to add a 10 line celt_icwrsi,
a wrapper around it (celt_alg_quant) and templating the
ff_celt_decode_band to replace entropy decoding functions
with entropy encoding.
There is no performance loss but in
Handles strides (needed for Opus transients), does pre-reindexing and folding
without needing a copy.
Signed-off-by: Rostislav Pehlivanov
---
configure| 6 +-
libavcodec/Makefile | 2 +-
libavcodec/aac.h | 4 +-
Mostly used the RFC document, the decoding functions and
the reference encoder's implmenentation as a reference.
Signed-off-by: Rostislav Pehlivanov
---
libavcodec/opus_rc.c | 182 ++-
libavcodec/opus_rc.h | 35 --
2
This series of commits implements a native Opus encoder.
This is v2 of the patchset, the changes are:
- The forward MDCT doesn't need a third buffer and can handle
the full set of sizes the init function allows
- The encoder has a new faster than libopus and more accurate
PVQ
This marks the first time anyone has written an Opus encoder without
using any libopus code. The aim of the encoder is to prove how far
the format can go by writing the craziest encoder for it.
Right now the encoder's basic, it only supports CBR encoding, however
internally every single feature
On Fri, Feb 10, 2017 at 04:11:43PM -0500, Vittorio Giovara wrote:
> Signed-off-by: Vittorio Giovara
> ---
> This should help not losing details over muxing and allows
> callers to get additional information in a clean manner.
>
> Please keep me in CC.
> Vittorio
>
>
This enables having multiple tracks of the same type which would
be treated as different things by the media server (as opposed to
different bit rate versions of the same track). According to the
smooth streaming specification, just setting the systemLanguage
tag is not enough to note that a track
Signed-off-by: James Almer
---
tests/fate/avformat.mak | 1 +
tests/lavf-regression.sh | 4
tests/ref/lavf/wv| 3 +++
3 files changed, 8 insertions(+)
create mode 100644 tests/ref/lavf/wv
diff --git a/tests/fate/avformat.mak b/tests/fate/avformat.mak
index
In particular cases, it is possible to initialize top_field_first
but not interlaced_frame. Make sure to correctly tag a frame
as interlaced when this happens.
Signed-off-by: Vittorio Giovara
---
Please CC.
Vittorio
libavcodec/h264_slice.c | 13 -
1 file
On Fri, Feb 10, 2017 at 01:35:34PM +0100, wm4 wrote:
> From: Anton Khirnov
>
> This will be useful in the following commit, after which the muxer
> timebase is not always available when encoding.
>
> This merges Libav commit 3e265ca. It was previously skipped.
>
> There is a
---
Although quite math-heavy, I saw little value in having a single parsing
function, and since it requires stream or demuxer specific information
I preferred to keep the two separate.
Please keep me in CC.
Vittorio
libavformat/matroskadec.c | 34 +-
1 file
On 2/10/2017 6:24 PM, Paul B Mahol wrote:
> On 2/10/17, James Almer wrote:
>> This way it's clear the size field accounts for the footer length plus every
>> tag entry, but not the header.
>>
>> Signed-off-by: James Almer
>> ---
>> libavformat/apetag.c | 12
On 2/10/2017 6:23 PM, Paul B Mahol wrote:
> On 2/10/17, James Almer wrote:
>> The size field in the header/footer accounts for the entire APE tag
>> structure except the 32 bytes from header, for compatibility with
>> APEv1.
>>
>> Signed-off-by: James Almer
On 2/10/2017 6:20 PM, Paul B Mahol wrote:
> On 2/10/17, James Almer wrote:
>> According to the spec[1], a value of 0 means the footer is present and a
>> value
>> of 1 means it's absent, the exact opposite of header presence flag where 1
>> means present and 0 absent.
>> The
On 2/10/17, James Almer wrote:
> This way it's clear the size field accounts for the footer length plus every
> tag entry, but not the header.
>
> Signed-off-by: James Almer
> ---
> libavformat/apetag.c | 12 ++--
> 1 file changed, 6 insertions(+),
On 2/10/17, James Almer wrote:
> The size field in the header/footer accounts for the entire APE tag
> structure except the 32 bytes from header, for compatibility with
> APEv1.
>
> Signed-off-by: James Almer
> ---
> libavformat/apetag.c | 6 +-
>
On 2/10/17, James Almer wrote:
> According to the spec[1], a value of 0 means the footer is present and a
> value
> of 1 means it's absent, the exact opposite of header presence flag where 1
> means present and 0 absent.
> The reason for this is compatibility with APEv1 tags,
Update the fate test as needed.
---
Please keep me in CC.
Vittorio
libavformat/mov.c | 46 ++-
tests/ref/fate/mov-spherical-mono | 8 +--
2 files changed, 51 insertions(+), 3 deletions(-)
diff --git a/libavformat/mov.c b/libavformat/mov.c
Signed-off-by: Vittorio Giovara
---
This should help not losing details over muxing and allows
callers to get additional information in a clean manner.
Please keep me in CC.
Vittorio
doc/APIchanges| 5 +
ffprobe.c | 11 --
This way it's clear the size field accounts for the footer length plus every
tag entry, but not the header.
Signed-off-by: James Almer
---
libavformat/apetag.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/libavformat/apetag.c
According to the spec[1], a value of 0 means the footer is present and a value
of 1 means it's absent, the exact opposite of header presence flag where 1
means present and 0 absent.
The reason for this is compatibility with APEv1 tags, where there's no header,
footer presence was mandatory for all
Iam listing the reason for each, this is mostly my oppinion and i didnt ask most
if they agree with the listed reason to be listed with their name, so its largly
my oppinion. Which is why i will remove the reasons before pushing i just added
them
to be transparent on this but as said its mostly
On 2/10/2017 4:03 PM, Michael Niedermayer wrote:
> Hi community
>
> what do you prefer about the ffmpeg-security alias ?
> in no particular order
>
> Should everyone on the alias be listed in MAINTAINERs under a
> ffmpeg-security point?
I'd say yes. From a transparency PoV, people should know
Hi community
what do you prefer about the ffmpeg-security alias ?
in no particular order
Should everyone on the alias be listed in MAINTAINERs under a
ffmpeg-security point?
Should for everyone who is on the alias a reason be listed in
MAINTAINERs why (s)he is on the alias ?
Should everyone on
Hi all,
The attached patch allows libavcodec/opus to decode ambisonics with
non-diegetic stereo stream in an ogg/opus container, as is being added in
this IETF standards draft [1].
Please let me know if there are any concerns.
Thanks,
Felicia
[1]
According to the spec[1], a value of 0 means the footer is present and a value
of 1 means it's absent, the exact opposite of header presence flag where 1
means present and 0 absent.
The reason for this is compatibility with APEv1 tags, where there's no header,
footer presence was mandatory for all
The size field in the header/footer accounts for the entire APE tag
structure except the 32 bytes from header, for compatibility with
APEv1.
Signed-off-by: James Almer
---
libavformat/apetag.c | 6 +-
libavformat/apetag.h | 1 +
2 files changed, 6 insertions(+), 1
On Fri, 10 Feb 2017 15:48:55 +
Saverio Blasi wrote:
> > You probably shouldn't update options_buffer_size before the reallocation
> > actually succeeded. (Probably doesn't matter with the current code, but for
> > robustness...)
> This is now addressed.
>
> >
On Fri, 10 Feb 2017 15:37:09 +
Saverio Blasi wrote:
> - This patch contains the changes to interface the Turing codec
> (http://turingcodec.org/) with ffmpeg. The patch was modified to address the
> comments in the review as follows:
> - Added a pkg-config file
On 2/10/17, Carl Eugen Hoyos wrote:
> 2017-02-10 16:14 GMT+01:00 Paul B Mahol :
>
>> +case 32: avctx->pix_fmt = AV_PIX_FMT_BGRA; break;
>
> Do you have a 32bit sample?
> I would have expected that screen capture codecs do not
> support alpha.
It
2017-02-10 16:14 GMT+01:00 Paul B Mahol :
> +case 32: avctx->pix_fmt = AV_PIX_FMT_BGRA; break;
Do you have a 32bit sample?
I would have expected that screen capture codecs do not
support alpha.
Carl Eugen
___
ffmpeg-devel
On 2/10/17, Saverio Blasi wrote:
> - This patch contains the changes to interface the Turing codec
> (http://turingcodec.org/) with ffmpeg. The patch was modified to address the
> comments in the review as follows:
> - Added a pkg-config file to list all dependencies
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) with ffmpeg. The patch was modified to address the
comments in the review as follows:
- Added a pkg-config file to list all dependencies required by libturing.
This should address the issue pointed out
> 'U' < 'W' (the ones above in configure get the order right).
This is now fixed.
> It's now 2017.
This is now fixed.
> What is float.h being included for here?
This redundant include is now removed.
> Would it be possible to add a few more of the standard options here to avoid
> some normal
Signed-off-by: Paul B Mahol
---
libavcodec/Makefile | 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/avcodec.h| 1 +
libavcodec/codec_desc.c | 7 +
libavcodec/fmvc.c | 629
libavformat/riff.c | 1 +
6
On Fri, Feb 10, 2017 at 03:22:28PM +0100, Michael Niedermayer wrote:
> On Fri, Feb 10, 2017 at 03:15:29PM +0100, Michael Niedermayer wrote:
> > On Fri, Feb 10, 2017 at 01:35:32PM +0100, wm4 wrote:
> > > These patches merge the previously skipped Libav commits, which made
> > > avconv lazily
On Fri, Feb 10, 2017 at 03:15:29PM +0100, Michael Niedermayer wrote:
> On Fri, Feb 10, 2017 at 01:35:32PM +0100, wm4 wrote:
> > These patches merge the previously skipped Libav commits, which made
> > avconv lazily initialize libavfilter graphs. This means the filters
> > are initialized with the
On Fri, Feb 10, 2017 at 01:35:32PM +0100, wm4 wrote:
> These patches merge the previously skipped Libav commits, which made
> avconv lazily initialize libavfilter graphs. This means the filters
> are initialized with the actual output format, instead of whatever
> libavformat reports.
>
> It's a
On Fri, 10 Feb 2017 13:55:39 +0100
Timo Rothenpieler wrote:
> Am 10.02.2017 um 13:35 schrieb wm4:
> > These patches merge the previously skipped Libav commits, which made
> > avconv lazily initialize libavfilter graphs. This means the filters
> > are initialized with the
Am 10.02.2017 um 13:35 schrieb wm4:
> These patches merge the previously skipped Libav commits, which made
> avconv lazily initialize libavfilter graphs. This means the filters
> are initialized with the actual output format, instead of whatever
> libavformat reports.
>
> It's a prerequisite to
From: Timo Rothenpieler
---
libavcodec/cuvid.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/libavcodec/cuvid.c b/libavcodec/cuvid.c
index 6091d81d3b..463c0dbf49 100644
--- a/libavcodec/cuvid.c
+++ b/libavcodec/cuvid.c
@@ -136,6 +136,19 @@ static int
From: Timo Rothenpieler
---
libavcodec/cuvid.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavcodec/cuvid.c b/libavcodec/cuvid.c
index 9b35476f2a..6091d81d3b 100644
--- a/libavcodec/cuvid.c
+++ b/libavcodec/cuvid.c
@@ -193,6 +193,11 @@ static int CUDAAPI
Broken by the previous Libav commit (even in Libav, thus a separate
commit).
Signed-off-by: wm4
---
ffmpeg_filter.c | 44 +---
1 file changed, 21 insertions(+), 23 deletions(-)
diff --git a/ffmpeg_filter.c b/ffmpeg_filter.c
index
From: Anton Khirnov
This is a more appropriate place for it, and will also be useful in the
following commit.
This merges Libav commit d2e56cf. It was previously skipped.
Signed-off-by: wm4
---
ffmpeg.c| 11 ---
ffmpeg_filter.c | 11
From: Anton Khirnov
Be more careful when an input stream encounters EOF when its filtergraph
has not been configured yet. The current code would immediately mark the
corresponding output streams as finished, while there may still be
buffered frames waiting for frames to appear
From: Anton Khirnov
This makes sure the actual stream parameters are used, which is
important mainly for hardware decoding+filtering cases, which would
previously require various weird workarounds to handle the fact that a
fake software graph has to be constructed, but never
From: Timo Rothenpieler
---
ffmpeg.c | 13 --
ffmpeg.h | 1 -
ffmpeg_cuvid.c | 141 -
3 files changed, 30 insertions(+), 125 deletions(-)
diff --git a/ffmpeg.c b/ffmpeg.c
index
From: Anton Khirnov
This will be useful in the following commit, after which the muxer
timebase is not always available when encoding.
This merges Libav commit 3e265ca. It was previously skipped.
There is a minor change with setting the mux_timebase field only after
the
Some callers (like do_subtitle_out()) call this with an AVPacket that is
not refcounted. This can cause undefined behavior.
Calling av_packet_move_ref() does not make a packet refcounted if it
isn't yet. (And it can't be made to, because it always succeeds,
and can't return ENOMEM.)
Call
These patches merge the previously skipped Libav commits, which made
avconv lazily initialize libavfilter graphs. This means the filters
are initialized with the actual output format, instead of whatever
libavformat reports.
It's a prerequisite to making hardware decoding support saner, as
Hi,
Attached patch will document the options to list demuxers and muxers
Regards,
Mulvya
0001-Add-muxers-demuxers-list-option.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Thu, Feb 09, 2017 at 04:03:57PM -0800, Matthew Wolenetz wrote:
> I've separated and updated the mov_read_{senc,saiz}() patch, attached.
> It avoids allocation wraps in those two functions.
applied
thanks
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The
On Wed, Feb 08, 2017 at 03:48:19PM -0800, Matthew Wolenetz wrote:
> I've separated and updated the mov_read_udta_string() patch, attached.
> It prevents accessing MOVContext.meta_keys[0] in that method. That array is
> 1-based.
applied
thx
[...]
--
Michael GnuPG fingerprint:
64 matches
Mail list logo