Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: hung kuishing <hungkuishing@outlook.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 1/2] lavc: add prores bitstream parser
Date: Wed, 26 Jul 2023 14:55:48 +0000
Message-ID: <PH7PR11MB7430CEEEB1E7512B60695B63C400A@PH7PR11MB7430.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAPYw7P4=1u0QNUVeXhhRVRVfiz2wCG4aaHyG+Ma4RVmXM5pHUw@mail.gmail.com>

> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Paul B Mahol
> Sent: Wednesday, July 26, 2023 9:02 PM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v3 1/2] lavc: add prores bitstream
> parser
> 
> On Wed, Jul 26, 2023 at 11:27 AM hung kuishing
> <hungkuishing@outlook.com>
> wrote:
> 
> > Signed-off-by: clarkh <hungkuishing@outlook.com>
> > ---
> >  libavcodec/Makefile        |   1 +
> >  libavcodec/parsers.c       |   1 +
> >  libavcodec/prores_parser.c | 107
> > +++++++++++++++++++++++++++++++++++++
> >  3 files changed, 109 insertions(+)
> >  create mode 100644 libavcodec/prores_parser.c
> >
> 
> What is usage for this?
> Which streams/files need this?

This patch originated from a need in my work to wrap the ProRes bitstream generated by ffmpeg into another mov wrapper. 
If it doesn't add value to the community, just ignore it with ease.

> Have parser be tested rigorously with random noise data?

I tested with some random data, ffmpeg can handle them correctly.
_______________________________________________
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:[~2023-07-26 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26  9:27 hung kuishing
2023-07-26 13:01 ` Paul B Mahol
2023-07-26 14:55   ` hung kuishing [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=PH7PR11MB7430CEEEB1E7512B60695B63C400A@PH7PR11MB7430.namprd11.prod.outlook.com \
    --to=hungkuishing@outlook.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