From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 2/2] lavf: add prores bitstream demuxer and muxer
Date: Thu, 27 Jul 2023 14:02:17 +0100
Message-ID: <2f18a33f-ce60-ea16-89c8-cbe17e439398@gmail.com> (raw)
In-Reply-To: <PH7PR11MB74300F5806524E3C275EC811C401A@PH7PR11MB7430.namprd11.prod.outlook.com>
On 7/27/2023 9:16 AM, hung kuishing wrote:
> Let me briefly describe what I needed at that time:
> I have another prores encoder and another mov muxer, what I need to do are:
> 1. use "another mov muxer" to encapsulate prores bitstream generated by ffmpeg.
> 2. use ffmpeg to encapsulate prores bitstream generated by "another prores encoder" .
>
> I know I can implement them by calling the ffmpeg api, but how can I implement them by ffmpeg tool?
> So, I developed these patches.
So this format was created as a weird hack to enable the ffmpeg CLI to be jammed
into such a workflow.
My NAK remains.
- 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".
next prev parent reply other threads:[~2023-07-27 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 9:28 hung kuishing
2023-07-26 12:54 ` Derek Buitenhuis
2023-07-26 14:59 ` hung kuishing
2023-07-26 17:10 ` Andreas Rheinhardt
2023-07-27 8:16 ` hung kuishing
2023-07-27 13:02 ` Derek Buitenhuis [this message]
2023-07-26 17:08 ` Kieran Kunhya
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=2f18a33f-ce60-ea16-89c8-cbe17e439398@gmail.com \
--to=derek.buitenhuis@gmail.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