Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/3] avformat/mov: skip moof and sidx before found moov
Date: Sat, 25 Dec 2021 10:17:39 +0800
Message-ID: <tencent_04B6AB9C4E5F70242D489AED405B9A709F08@qq.com> (raw)
In-Reply-To: <aff2e578-3fdd-eb09-5b2d-86829fc73abb@gmail.com>



> On Dec 25, 2021, at 3:09 AM, Derek Buitenhuis <derek.buitenhuis@gmail.com> wrote:
> 
> On 12/24/2021 9:58 AM, Zhao Zhili wrote:
>> ---
>> libavformat/mov.c | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
> 
> When do such files exist? They're not valid.

File from Steven, and another one from ticket 8883.
https://trac.ffmpeg.org/ticket/8883

Put moov after moof doesn't make sense, but I’m not sure they are
valid or not. Those files are generated like this:

1. Use hoov as moov to create a fragmented mp4.
2. At last, create a normal moov box.

For demuxer which doesn’t know hoov (maybe don’t know moof neither),
they are normal files. VLC and quicktime player can playback those
samples. FFmpeg only handle the first fragment because it treat
hoov as moov.

gstreamer has a similar strategy but not the same:

> isomp4/mux: add a fragment mode for initial moov with data
> 
> Used by some proprietary software for their fragmented files.
> 
> Adds some support for multi-stream fragmented files
> 
> Flow is as follows.
> 1. The first 'fragment' is written as a self-contained fragmented
>    mdat+moov complete with an edit list and durations, tags, etc.
> 2. Subsequent fragments are written with a mdat+moof and each stream is
>    interleaved as data arrives (currently ignoring the interleave-*
>    properties).  data-offsets in both the traf and the trun ensure
>    data is read from the correct place on demuxing.  Data/chunk offsets
>    are also kept for writing out the final moov.
> 3. On finalisation, the initial moov is invalidated to a hoov and the
>    size of the first mdat is extended to cover the entire file contents.
>    Then a moov is written as regularly would in moov-at-end mode (the
>    default).
> 
> This results in a file that is playable throughout while leaving a
> finalised file on completion for players that do not understand
> fragmented mp4.


https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/merge_requests/643

I’m really interested to know where do those hoov files come from, so
we don’t fix a case and failed for another case.

> 
> - Derek
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2021-12-25  2:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  9:58 Zhao Zhili
2021-12-24 19:09 ` Derek Buitenhuis
2021-12-25  2:17   ` "zhilizhao(赵志立)" [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tencent_04B6AB9C4E5F70242D489AED405B9A709F08@qq.com \
    --to=quinkblack@foxmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git