From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Stefano Sabatini <stefasab@gmail.com> Subject: [FFmpeg-devel] [PATCH] doc/muxers/image2: add mention to image2pipe Date: Fri, 29 Mar 2024 14:03:54 +0100 Message-ID: <20240329130354.36725-1-stefasab@gmail.com> (raw) Clarify the difference with regards to the image2 muxer. --- doc/muxers.texi | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/muxers.texi b/doc/muxers.texi index 05a0c302cf..5cce26a43f 100644 --- a/doc/muxers.texi +++ b/doc/muxers.texi @@ -2569,10 +2569,10 @@ Internet Low Bitrate Codec (iLBC) raw muxer. It accepts a single @samp{ilbc} audio stream. @anchor{image2} -@section image2 +@section image2, image2pipe Image file muxer. -The image file muxer writes video frames to image files. +The @samp{image2} muxer writes video frames to image files. The output filenames are specified by a pattern, which can be used to produce sequentially numbered series of files. @@ -2603,6 +2603,10 @@ each of the YUV420P components. To read or write this image file format, specify the name of the '.Y' file. The muxer will automatically open the '.U' and '.V' files as required. +The @samp{image2pipe} muxer accepts the same options as the @samp{image2} muxer, +but ignores the pattern verification and expansion, as it is supposed to write +to the command output rather than to an actual stored file. + @subsection Options @table @option @item frame_pts @var{bool} -- 2.34.1 _______________________________________________ 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:[~2024-03-29 13:04 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240329130354.36725-1-stefasab@gmail.com \ --to=stefasab@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