2017-02-25 19:09 GMT+09:00 Martin Storsjö :
> On Fri, 24 Feb 2017, John Stebbins wrote:
>
> On 02/24/2017 03:13 PM, Martin Storsjö wrote:
>>
>>> On Fri, 24 Feb 2017, John Stebbins wrote:
>>>
>>> On 02/24/2017 02:21 PM, Martin Storsjö wrote:
> On Fri, 24 Feb 2017, John
2017-02-20 6:22 GMT+09:00 Martin Storsjö :
> This reduces the need for an edit list; streams that start with
> e.g. dts=-1, pts=0 can be encoded as dts=0, pts=0 (which is valid
> in mov/mp4) by shifting the dts values of all packets forward.
> This avoids the need for edit lists
2017-02-22 6:45 GMT+09:00 Martin Storsjö <mar...@martin.st>:
> Hi Yusuke,
>
>
> On Wed, 22 Feb 2017, Yusuke Nakamura wrote:
>
> 2017-02-20 6:22 GMT+09:00 Martin Storsjö <mar...@martin.st>:
>>
>> In these cases, the CTTS flag is set, but no edit list is ne
2017-02-20 6:22 GMT+09:00 Martin Storsjö :
> In these cases, the CTTS flag is set, but no edit list is necessary.
> ---
> libavformat/movenc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> index
2015-02-21 7:13 GMT+09:00 Martin Storsjö mar...@martin.st:
On Fri, 20 Feb 2015, wm4 wrote:
I suppose in theory the index could be factored into its own API, and
the mov demuxer could use it privately, which would prevent anyone from
tampering with it. (Not that I want to prevent a quick bug
2015-01-27 19:15 GMT+09:00 Yusuke Nakamura muken.the.vfrman...@gmail.com:
CTS-based seek is reasonable since player requests frames in output order
not coded order.
This change fixes seek to a keyframe within consecutive keyframes.
Let's say P[0|-1] and P[1|0], here x and y inside [x|y
2015-02-02 17:26 GMT+09:00 Anton Khirnov an...@khirnov.net:
Quoting Vittorio Giovara (2015-02-01 02:12:53)
From: Hendrik Leppkes h.lepp...@gmail.com
This atom typically is used for a track title. The handler name is stored
as a pascal string in the QT specs (first byte is the length of
CTS-based seek is reasonable since player requests frames in output order
not coded order.
This change fixes seek to a keyframe within consecutive keyframes.
Let's say P[0|-1] and P[1|0], here x and y inside [x|y] are PTS and DTS
respectively, and both two frames are a keyframe. If you try to
2015-01-27 19:27 GMT+09:00 Luca Barbato lu_z...@gentoo.org:
On 27/01/15 11:15, Yusuke Nakamura wrote:
CTS-based seek is reasonable since player requests frames in output order
not coded order.
This change fixes seek to a keyframe within consecutive keyframes.
Let's say P[0|-1] and P[1|0
2014-12-26 0:01 GMT+09:00 Alexandra Hájková alexandra.khirn...@gmail.com:
The old one is result of reverse engeneering and guesswork.
The new one had beem written following the now-available specification.
This work is part of Outreach Program for Women Summer 2014 activities.
---
2014-10-30 16:40 GMT+09:00 Martin Storsjö mar...@martin.st:
ISO/IEC 14496-12:2012/Cor 1:2013 is explicit about how this should be
handled. All zeros doesn't mean that the full file has got a zero
duration, only that the track samples described within the initial moov
have got zero duration.
2014-10-30 16:40 GMT+09:00 Martin Storsjö mar...@martin.st:
We deviate slightly from the iso specs for these files.
---
libavformat/movenc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index d79607b..80a44cf 100644
---
2014-10-30 16:40 GMT+09:00 Martin Storsjö mar...@martin.st:
The tfdt atom shouldn't be needed in those cases, we already
write tfxd atoms for ismv anyway, which is roughly equivalent.
This avoids having to declare the iso6 brand for ismv files.
---
libavformat/movenc.c | 5 +++--
1 file
2014-10-29 19:14 GMT+09:00 Martin Storsjö mar...@martin.st:
Similarly to the omit_tfhd_offset flag added in e7bf085b, this
avoids writing absolute byte positions to the file, making them
more easily streamable.
This is a new feature from 14496-12:2012, so application support
isn't
2014-10-29 22:00 GMT+09:00 Martin Storsjö mar...@martin.st:
On Wed, 29 Oct 2014, Yusuke Nakamura wrote:
2014-10-29 19:14 GMT+09:00 Martin Storsjö mar...@martin.st:
Similarly to the omit_tfhd_offset flag added in e7bf085b, this
avoids writing absolute byte positions to the file, making
2014-10-29 22:54 GMT+09:00 Martin Storsjö mar...@martin.st:
On Wed, 29 Oct 2014, Yusuke Nakamura wrote:
2014-10-29 22:00 GMT+09:00 Martin Storsjö mar...@martin.st:
On Wed, 29 Oct 2014, Yusuke Nakamura wrote:
This patch produces out-of-spec files about the file format
compatibility
2014-10-30 0:09 GMT+09:00 Martin Storsjö mar...@martin.st:
---
libavformat/movenc.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index 30c500e..1470ebf 100644
--- a/libavformat/movenc.c
+++ b/libavformat/movenc.c
@@ -2742,6 +2742,11
2014-10-30 0:09 GMT+09:00 Martin Storsjö mar...@martin.st:
Similarly to the omit_tfhd_offset flag added in e7bf085b, this
avoids writing absolute byte positions to the file, making them
more easily streamable.
This is a new feature from 14496-12:2012, so application support
isn't
2014-10-30 5:57 GMT+09:00 Martin Storsjö mar...@martin.st:
14496-12:2014 Cor.1 is explicit about how this should be handled.
ISO/IEC 14496-12:2012/Cor 1:2013
All zeros doesn't mean that the full file has got a zero duration,
only that the track samples described within the initial moov
2014-10-30 5:57 GMT+09:00 Martin Storsjö mar...@martin.st:
We deviate slightly from the iso specs for these files.
---
libavformat/movenc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index f8b08c1..a8f740c 100644
---
2014-10-30 6:52 GMT+09:00 Martin Storsjö mar...@martin.st:
We deviate slightly from the iso specs for these files.
---
libavformat/movenc.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index 6184101..1459c49 100644
---
2014-10-12 20:18 GMT+09:00 Martin Storsjö mar...@martin.st:
On Sun, 12 Oct 2014, Luca Barbato wrote:
On 12/10/14 12:46, Martin Storsjö wrote:
On Sun, 12 Oct 2014, Luca Barbato wrote:
On 12/10/14 00:32, Martin Storsjö wrote:
From: Michael Niedermayer michae...@gmx.at
This makes sure
2014-07-05 0:21 GMT+09:00 Vittorio Giovara vittorio.giov...@gmail.com:
---
libavutil/frame.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavutil/frame.h b/libavutil/frame.h
index b2159d3..8685fbb 100644
--- a/libavutil/frame.h
+++ b/libavutil/frame.h
@@
default-base-is-moof shall be set to track fragments compatible with DASH
Media Segments. So, this is a fundamental support for ISOBMFF ver. DASH.
This is meaningful only when base-data-offset-present is absent and two or
more track fragments are present in a movie fragment.
---
2014-06-27 2:16 GMT+09:00 Vittorio Giovara vittorio.giov...@gmail.com:
On Wed, Jun 25, 2014 at 8:31 AM, Hendrik Leppkes h.lepp...@gmail.com
wrote:
Setting key frame based on them is the most logical choice, really.
My point was more that it's really hard to tell what key_frame does
since
2014-03-26 2:26 GMT+09:00 Vittorio Giovara vittorio.giov...@gmail.com:
On Tue, Mar 25, 2014 at 3:48 PM, wm4 nfx...@googlemail.com wrote:
On Tue, 25 Mar 2014 15:31:49 +0100
Vittorio Giovara vittorio.giov...@gmail.com wrote:
+/**
+ * Spatial transformation information that should be
2014-03-18 6:43 GMT+09:00 John Stebbins stebb...@jetheaddev.com:
---
libavformat/movenc.c | 5 -
libavformat/movenc.h | 2 ++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index 2ae3475..fedfc3c 100644
---
2014/1/17 Derek Buitenhuis derek.buitenh...@gmail.com
From: Justin Ruggles justin.rugg...@gmail.com
The track duration is often not reliable or is not the duration
represented by the number of frames. In those cases, avg_frame_rate
was reported incorrectly. Removing this code falls back to
2013/11/9 Vittorio Giovara vittorio.giov...@gmail.com
On Mon, Nov 4, 2013 at 1:10 PM, Vittorio Giovara
vittorio.giov...@gmail.com wrote:
---
libavcodec/h264_ps.c |5 +
1 file changed, 5 insertions(+)
diff --git a/libavcodec/h264_ps.c b/libavcodec/h264_ps.c
index
2013/11/4 Vittorio Giovara vittorio.giov...@gmail.com
---
libavcodec/h264_ps.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/libavcodec/h264_ps.c b/libavcodec/h264_ps.c
index 54b735d..819b7ff 100644
--- a/libavcodec/h264_ps.c
+++
2013/11/4 Vittorio Giovara vittorio.giov...@gmail.com
On Mon, Nov 4, 2013 at 2:27 PM, Vittorio Giovara
vittorio.giov...@gmail.com wrote:
On Mon, Nov 4, 2013 at 1:28 PM, Yusuke Nakamura
muken.the.vfrman...@gmail.com wrote:
---
libavcodec/h264_ps.c | 5 -
1 file changed, 4
2013/11/5 Yusuke Nakamura muken.the.vfrman...@gmail.com
And, for 4:2:2, there is no concept of top and left. only left, center and
right.
s/top and left/top and bottom/
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org
---
libavcodec/hevc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/libavcodec/hevc.c b/libavcodec/hevc.c
index ed980e3..e3d306b 100644
--- a/libavcodec/hevc.c
+++ b/libavcodec/hevc.c
@@ -401,6 +401,13 @@ static int set_sps(HEVCContext *s, const HEVCSPS *sps)
---
libavcodec/h264_ps.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libavcodec/h264_ps.c b/libavcodec/h264_ps.c
index 54b735d..422f522 100644
--- a/libavcodec/h264_ps.c
+++ b/libavcodec/h264_ps.c
@@ -178,7 +178,10 @@ static inline int decode_vui_parameters(H264Context
---
libavcodec/hevc.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavcodec/hevc.c b/libavcodec/hevc.c
index 276f3fd..7f5ad60 100644
--- a/libavcodec/hevc.c
+++ b/libavcodec/hevc.c
@@ -401,6 +401,11 @@ static int set_sps(HEVCContext *s, const HEVCSPS *sps)
---
libavcodec/h264_ps.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavcodec/h264_ps.c b/libavcodec/h264_ps.c
index 54b735d..a08ab3b 100644
--- a/libavcodec/h264_ps.c
+++ b/libavcodec/h264_ps.c
@@ -178,7 +178,8 @@ static inline int decode_vui_parameters(H264Context
---
libavcodec/hevc_ps.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavcodec/hevc_ps.c b/libavcodec/hevc_ps.c
index 15f73be..a51784d 100644
--- a/libavcodec/hevc_ps.c
+++ b/libavcodec/hevc_ps.c
@@ -449,6 +449,8 @@ static void decode_vui(HEVCContext *s, HEVCSPS *sps)
2013/11/4 Jan Ekström jee...@gmail.com
Also limit the parsed VUI values to known valid ones.
---
libavcodec/hevc.c| 16
libavcodec/hevc_ps.c |8
2 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/libavcodec/hevc.c b/libavcodec/hevc.c
index
From: Michael Niedermayer michae...@gmx.at
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavcodec/h264_parser.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/h264_parser.c b/libavcodec/h264_parser.c
index a30e2c3..05a40c7 100644
---
---
libavcodec/h264_parser.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/libavcodec/h264_parser.c b/libavcodec/h264_parser.c
index e6e2704..a30e2c3 100644
--- a/libavcodec/h264_parser.c
+++ b/libavcodec/h264_parser.c
@@ -181,11 +181,8 @@ static inline int
---
libavcodec/h264.c| 89 +
libavcodec/h264.h| 2 +
libavcodec/h264_parser.c | 95 +---
3 files changed, 141 insertions(+), 45 deletions(-)
diff --git a/libavcodec/h264.c b/libavcodec/h264.c
The prev_ values were not set after parsing POC.
Increase length of the buffer decoded to parse enough safely.
---
libavcodec/h264_parser.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/libavcodec/h264_parser.c b/libavcodec/h264_parser.c
index
---
libavcodec/h264_parser.c | 148 +--
1 file changed, 142 insertions(+), 6 deletions(-)
diff --git a/libavcodec/h264_parser.c b/libavcodec/h264_parser.c
index 75e09f4..02ef566 100644
--- a/libavcodec/h264_parser.c
+++ b/libavcodec/h264_parser.c
@@
2013/9/6 Vittorio Giovara vittorio.giov...@gmail.com
Il giorno giovedì 5 settembre 2013, Yusuke Nakamura ha scritto:
---
Sorry for parsing wrong output_picture_number since I was under the
impression that the prev_ values are set in ff_init_poc().
This patch decodes up to MMCOs to set
---
libavcodec/h264_parser.c | 148 ++-
1 file changed, 146 insertions(+), 2 deletions(-)
diff --git a/libavcodec/h264_parser.c b/libavcodec/h264_parser.c
index ef5da98..f137260 100644
--- a/libavcodec/h264_parser.c
+++ b/libavcodec/h264_parser.c
@@
---
Sorry for parsing wrong output_picture_number since I was under the impression
that the prev_ values are set in ff_init_poc().
This patch decodes up to MMCOs to set the prev_ values correctly if needed.
libavcodec/h264_parser.c | 142 ++-
1 file
Set output_picture_number in H.264 parser.
---
doc/APIchanges | 3 +++
libavcodec/avcodec.h | 8
libavcodec/h264.c| 3 +--
libavcodec/h264_parser.c | 2 +-
libavcodec/version.h | 2 +-
5 files changed, 14 insertions(+), 4 deletions(-)
diff --git
2013/7/24 Yusuke Nakamura muken.the.vfrman...@gmail.com
2013/7/22 Luca Barbato lu_z...@gentoo.org
On 07/22/2013 12:19 PM, Yusuke Nakamura wrote:
output_picture_number tells us the output or presentation order and
shall
be unique within a sequence.
This corresponds to H.264/H.265
2013/7/22 Luca Barbato lu_z...@gentoo.org
On 07/22/2013 12:19 PM, Yusuke Nakamura wrote:
output_picture_number tells us the output or presentation order and shall
be unique within a sequence.
This corresponds to H.264/H.265 PicOrderCnt and Dirac picture number.
Attached patches support
output_picture_number tells us the output or presentation order and shall
be unique within a sequence.
This corresponds to H.264/H.265 PicOrderCnt and Dirac picture number.
Attached patches support parsing H.264 PicOrderCnt.
0001-avcodec-Add-output-picture-number-to-AVCodecParserCo.patch
ULH0 and ULH2 formats, which indicate BT.709-based colorspace conversion
coefficient, were added at Ut Video ver. 13.0.0.
0001-utvideodec-Support-ULH0-and-ULH2-formats.patch
Description: Binary data
0002-riff-Support-ULH0-and-ULH2-fourccs.patch
Description: Binary data
2013/5/21 Janne Grunau janne-li...@jannau.net
On 2013-05-15 20:57:42 +0900, Yusuke Nakamura wrote:
2013/5/8 Yusuke Nakamura muken.the.vfrman...@gmail.com
From ef78ded8954c3fca0ed138b29ee22dfe5a42fb2a Mon Sep 17 00:00:00 2001
From: Yusuke Nakamura muken.the.vfrman...@gmail.com
Date: Wed
2013/5/24 Diego Biurrun di...@biurrun.de
On Thu, May 23, 2013 at 04:37:24PM +0900, Yusuke Nakamura wrote:
OK. Attached new patches use an enum for picture_structure and take
suggestions on IRC.
--- a/libavcodec/avcodec.h
+++ b/libavcodec/avcodec.h
@@ -3407,6 +3407,13 @@ int
2013/5/8 Yusuke Nakamura muken.the.vfrman...@gmail.com
2013/5/8 Janne Grunau janne-li...@jannau.net
On 2013-04-25 06:58:05 +0900, Yusuke Nakamura wrote:
2013/4/15 Luca Barbato lu_z...@gentoo.org
I got some opinions about the H.264 one by Anton and Janne on IRC, and I
took them in a new
2013/5/8 Janne Grunau janne-li...@jannau.net
On 2013-04-25 06:58:05 +0900, Yusuke Nakamura wrote:
2013/4/15 Luca Barbato lu_z...@gentoo.org
I got some opinions about the H.264 one by Anton and Janne on IRC, and I
took them in a new patch.
From 0013dc39354577b015e8971f6ebacb037914756f
2013/4/25 Yusuke Nakamura muken.the.vfrman...@gmail.com
2013/4/15 Luca Barbato lu_z...@gentoo.org
On 04/11/2013 04:56 PM, Yusuke Nakamura wrote:
2013/4/9 Luca Barbato lu_z...@gentoo.org
On 09/04/13 10:16, Yusuke Nakamura wrote:
Attached patches support setting field order information
2013/4/15 Luca Barbato lu_z...@gentoo.org
On 04/11/2013 04:56 PM, Yusuke Nakamura wrote:
2013/4/9 Luca Barbato lu_z...@gentoo.org
On 09/04/13 10:16, Yusuke Nakamura wrote:
Attached patches support setting field order information for H.264,
VC-1
and MPEG-2 video stream by parsing
2013/4/16 Vittorio Giovara vittorio.giov...@gmail.com
On 15/apr/2013, at 16:43, Yusuke Nakamura muken.the.vfrman...@gmail.com
wrote:
As far as I understand, frame_mbs_only_flag == 1 guarantees that frames
are
progressive, while frame_mbs_only_flag == 0 doesn't guarantee that a
frame
2013/4/11 Yusuke Nakamura muken.the.vfrman...@gmail.com
2013/4/9 Luca Barbato lu_z...@gentoo.org
On 09/04/13 10:16, Yusuke Nakamura wrote:
Attached patches support setting field order information for H.264, VC-1
and MPEG-2 video stream by parsing.
They look ok, the h264 one might
2013/4/15 Vittorio Giovara vittorio.giov...@gmail.com
On Mon, Apr 15, 2013 at 12:42 PM, Luca Barbato lu_z...@gentoo.org wrote:
On 04/11/2013 04:56 PM, Yusuke Nakamura wrote:
2013/4/9 Luca Barbato lu_z...@gentoo.org
On 09/04/13 10:16, Yusuke Nakamura wrote:
Attached patches support
2013/4/9 Luca Barbato lu_z...@gentoo.org
On 09/04/13 10:16, Yusuke Nakamura wrote:
Attached patches support setting field order information for H.264, VC-1
and MPEG-2 video stream by parsing.
They look ok, the h264 one might be reformatted a little since chained
ternaries aren't that nice
Attached patches support setting field order information for H.264, VC-1
and MPEG-2 video stream by parsing.
0001-avcodec-Add-field-order-information-to-AVCodecParser.patch
Description: Binary data
0002-mpegvideo_parser-Set-field_order.patch
Description: Binary data
2013/4/9 Hendrik Leppkes h.lepp...@gmail.com
On Tue, Apr 9, 2013 at 10:16 AM, Yusuke Nakamura
muken.the.vfrman...@gmail.com wrote:
Attached patches support setting field order information for H.264, VC-1
and MPEG-2 video stream by parsing.
AVCodecContext already has a field order
This is a regression in
http://git.libav.org/?p=libav.git;a=commitdiff;h=759001c534287a96dc96d1e274665feb7059145d.
0001-libopencore-amr-Add-the-missing-3rd-argument.patch
Description: Binary data
___
libav-devel mailing list
libav-devel@libav.org
2013/3/8 Yusuke Nakamura muken.the.vfrman...@gmail.com
This is a regression in
http://git.libav.org/?p=libav.git;a=commitdiff;h=759001c534287a96dc96d1e274665feb7059145d.
Oops. obviously, commit message is inappropriate.
libopencore-amr: Add the missing 3rd argument of ff_get_buffer
Attached patch fixes seeking to file offset exceeding 2G when int is
defined as 32bit signed integer.
This patch is similar with
https://github.com/FFmpeg/FFmpeg/commit/d37044647f83f53a1cb711ea4655b944ff4af0e5but
ffmpeg's one doesn't work on MinGW (not MinGW-w64) since MinGW ignores
The newest 14496-12 (4th edition corrected ver.) spec makes the definition
of terms around random access clear.
And the spec adds random access point grouping to signal closed or open
random access points.
14496-15 (AVC file format) spec already says sync sample table describes
only IDR-pictures
2012/6/29 Alex Converse alex.conve...@gmail.com
On Tue, Jun 26, 2012 at 10:07 AM, Anton Khirnov an...@khirnov.net wrote:
---
libavformat/mov.c | 49
+
1 file changed, 49 insertions(+)
Is this documented anywhere. I don't see it in the
2012/4/30 Derek Buitenhuis derek.buitenh...@gmail.com
From: Hendrik Leppkes h.lepp...@gmail.com
This atom typically is used for a track title.
Reviewed-by: Baptiste Coudurier
Signed-off-by: Michael Niedermayer michae...@gmx.at
---
libavformat/mov.c | 13 +
1 file changed,
Skip to parse fields for additional independent substreams and its
associated dependent substreams since libavcodec's eac3 decoder doesn't
support them yet.
0001-mov-Parse-EC3SpecificBox-dec3-atom.patch
Description: Binary data
___
libav-devel mailing
2012年4月26日8:16 Justin Ruggles justin.rugg...@gmail.com:
On 04/25/2012 06:31 PM, Yusuke Nakamura wrote:
+st-codec-channels = ((int[]){2,1,2,3,3,4,4,5})[acmod] + lfeon;
+st-codec-channel_layout = avpriv_ac3_channel_layout_tab[acmod];
+if (lfeon)
+st-codec
2012年4月26日8:47 Justin Ruggles justin.rugg...@gmail.com:
On 04/25/2012 07:38 PM, Yusuke Nakamura wrote:
2012年4月26日8:16 Justin Ruggles justin.rugg...@gmail.com
mailto:justin.rugg...@gmail.com:
On 04/25/2012 06:31 PM, Yusuke Nakamura wrote:
+st-codec-channels = ((int
DTS LBR identifier ('dtse') is not included since libavcodec doesn't
support it yet.
0001-isom-Support-more-DTS-codec-indentifiers.patch
Description: Binary data
___
libav-devel mailing list
libav-devel@libav.org
2012年4月22日8:34 Derek Buitenhuis derek.buitenh...@gmail.com:
On 21/04/2012 7:26 PM, Yusuke Nakamura wrote:
DTS LBR identifier ('dtse') is not included since libavcodec doesn't
support it yet.
This looks pretty harmless. Have you confirmed it works properly
on such files (demux/decode
2012年4月18日1:12 Derek Buitenhuis derek.buitenh...@gmail.com:
On 16/04/2012 10:52 AM, Yusuke Nakamura wrote:
The second patch may deny
http://git.libav.org/?p=libav.git;a=commit;f=libavformat/mov.c;h=26846ba5151b0fe90e21c1a6beb9a3bcb569d1ac,
while this commit denies splitted files
The second patch may deny
http://git.libav.org/?p=libav.git;a=commit;f=libavformat/mov.c;h=26846ba5151b0fe90e21c1a6beb9a3bcb569d1ac,
while this commit denies splitted files with gradual decoder refresh
(not
marked as a sync sample in 14496-15 spec).
So, I prefer the second patch to this commit.
Stss atom without entries doesn't mean every sample is a sync sample.
0001-mov-Fix-detecting-there-is-no-sync-sample.patch
Description: Binary data
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
2012/2/21 Martin Storsjö mar...@martin.st
For video, mark the first sample in a trun which doesn't have the
sample-is-non-sync-sample flag set as a keyframe.
In particular, the sample does not depend on other samples flag
isn't enough to make it a keyframe, since later frames still can
2012/2/19 Martin Storsjö mar...@martin.st
On Sun, 19 Feb 2012, Yusuke Nakamura wrote:
sample_depends_on = 2 doesn't mean random accessible point (e.g. H.264
stream can contain non-RAP I-pictures).
Hmm, the spec says 2: this sample does not depend on others (I picture);
- doesn't
2012/2/17 Martin Storsjö mar...@martin.st
---
Some of these are really long, but making them shorter makes
them a bit ambiguous IMO...
libavformat/isom.h | 10 ++
libavformat/mov.c|2 +-
libavformat/movenc.c |6 --
3 files changed, 15 insertions(+), 3
I encountered the following error.
libavcodec/pthread.c: In function 'frame_thread_free':
libavcodec/pthread.c:654:13: error: used struct type value where scalar is
required
make: *** [libavcodec/pthread.o] Error 1
Attached patch fixes this.
2011/7/30 Alex Converse alex.conve...@gmail.com
On Fri, Jul 29, 2011 at 11:10 AM, Yusuke Nakamura
muken.the.vfrman...@gmail.com wrote:
2011/7/29 Diego Biurrun di...@biurrun.de
---
libavformat/movenc.c | 17 -
1 files changed, 0 insertions(+), 17 deletions
2011/6/18 Måns Rullgård m...@mansr.com
Yusuke Nakamura muken.the.vfrman...@gmail.com writes:
This patch fixes my 10L of following.
http://git.libav.org/?p=libav.git;a=commitdiff;h=5f0bb0baefd506d684adfa1ad4259c65973b455e
From f3c030ebedabc9a17e377c6f91dc417e6578712b Mon Sep 17 00:00:00
2011/6/19 Måns Rullgård m...@mansr.com
Yusuke Nakamura muken.the.vfrman...@gmail.com writes:
2011/6/18 Måns Rullgård m...@mansr.com
Yusuke Nakamura muken.the.vfrman...@gmail.com writes:
This patch fixes my 10L of following.
http://git.libav.org/?p=libav.git;a=commitdiff;h
This patch fixes my 10L of following.
http://git.libav.org/?p=libav.git;a=commitdiff;h=5f0bb0baefd506d684adfa1ad4259c65973b455e
0001-mov-Fix-empty-edit-detection.patch
Description: Binary data
___
libav-devel mailing list
libav-devel@libav.org
Attached patch fixes detecting wrong timestamps on large presentation
indicated by edit list atom.
0001-mov-Support-edit-list-atom-version-1.patch
Description: Binary data
___
libav-devel mailing list
libav-devel@libav.org
2011/4/30 Aℓex Converse aconve...@google.com
On Fri, Apr 29, 2011 at 9:37 AM, Yusuke Nakamura
muken.the.vfrman...@gmail.com wrote:
Sorry, I missed the case that moov atom has any samples and doesn't have
ctts atom.
I attached a new patch.
have you tried running the fate regression
This fixes, for instance, the case that there is a track that has some
samples with composition time offset and has a track run without
sample-composition-time-offsets-present.
---
libavformat/mov.c | 33 ++---
1 files changed, 18 insertions(+), 15 deletions(-)
diff
88 matches
Mail list logo