From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] doc/muxers: extend documentation for MOV muxers
Date: Sun, 7 Jan 2024 09:54:11 -0600
Message-ID: <CA+28BfDxu0qMmGFoinnEZXL0=ZE6gGPy9kjiRLd=kL4Z6-RX9Q@mail.gmail.com> (raw)
In-Reply-To: <ZZq9pbXYrTFQX3tV@mariano>
Update to that paragraph LGTM. Thanks!
On Sun, Jan 7, 2024 at 9:05 AM Stefano Sabatini <stefasab@gmail.com> wrote:
> On date Saturday 2024-01-06 14:43:47 -0600, Marth64 wrote:
> > +This section covers formats belonging to the QuickTime / MOV family,
> > +also named after the MPEG-4 Part 14 format, also named after the ISO
> > +base media file format (ISOBMFF).
> > +
> > +The MOV format was originally developed for the Apple QuickTime
> > +container format. Then it was later used as basis for the MPEG MPEG-4
> > +Part 1 (later Part 14) format, also named after ISO/IEC 14496-1.
> > +
> > +The format was later generalized into the ISO base media file format,
> > +also named MPEG-4 Part 12 format or ISO/IEC 14496-12 or ISO/IEC
> > +15444-12.
> > +
> >
> > The word "also" is very prominent in this part (and a duplicate MPEG). I
> > admit it feels confusing to read. Maybe something like this?
> >
> > This section covers formats belonging to the QuickTime / MOV family,
> > including the MPEG-4 Part 14 format. These formats share a common
> structure
> > based on the ISO base media file format (ISOBMFF). ISOBMFF is also known
> as
> > MPEG-4 Part 12, ISO/IEC 14496-12, or ISO/IEC 15444-12.
> >
> > The MOV format was originally developed for use with Apple QuickTime.
> > It was later used as the basis for MPEG-4 Part 1 (later Part 14), also
> > known as
> > ISO/IEC 14496-1. That format was then generalized into ISOBMFF.
>
> Thanks, shortened and updated with some of the suggested changes.
> _______________________________________________
> 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".
prev parent reply other threads:[~2024-01-07 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 16:52 Stefano Sabatini
2024-01-06 20:43 ` Marth64
2024-01-07 15:05 ` Stefano Sabatini
2024-01-07 15:54 ` Marth64 [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='CA+28BfDxu0qMmGFoinnEZXL0=ZE6gGPy9kjiRLd=kL4Z6-RX9Q@mail.gmail.com' \
--to=marth64@proxyid.net \
--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