Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: ffmpegagent <ffmpegagent-at-gmail.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: softworkz <softworkz@hotmail.com>
Subject: [FFmpeg-devel] [PATCH v2 0/6] avformat/segment: Various segment muxer improvements
Date: Sat, 14 Jun 2025 00:59:06 +0000
Message-ID: <pull.96.v2.ffstaging.FFmpeg.1749862752.ffmpegagent@gmail.com> (raw)
In-Reply-To: <pull.96.ffstaging.FFmpeg.1749794066.ffmpegagent@gmail.com>

Includes

 * Two new options
   * segment_write_temp
     Allows to write segments as temp files (.tmp) which are renamed on
     completion
   * segment_limit Stop after n segments have been written
 * some minor changes (option contraints and formatting fixes)


Versions
========


V2
==

 * merge the documentation patch with the feature patch
 * segment_write_temp: use av_asprintf() directly instead of strlcatf() +
   av_strdup()
   (as per review by Marton - thanks!)
 * removed logging patch

.

softworkz (6):
  avformat/segment: Add segment_write_temp option
  avformat/segment: Add segment_limit option
  avformat/segment: Remove non-negative constraint from
    segment_time_delta
  avformat/segment: Don't allow negative segment duration
  avformat/segment: Fix typo
  avformat/segment: Indent and whitespace fixes

 doc/muxers.texi       | 12 ++++++
 libavformat/segment.c | 95 +++++++++++++++++++++++++++++--------------
 2 files changed, 76 insertions(+), 31 deletions(-)


base-commit: f3bf5356966b4ad9334034e720fa224c2d9464a6
Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-96%2Fsoftworkz%2Fsubmit_segment_muxer-v2
Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-96/softworkz/submit_segment_muxer-v2
Pull-Request: https://github.com/ffstaging/FFmpeg/pull/96

Range-diff vs v1:

  1:  0132f3f933 !  1:  79b4f63573 avformat/segment: Add segment_write_temp option
     @@ Commit message
      
          Signed-off-by: softworkz <softworkz@hotmail.com>
      
     + ## doc/muxers.texi ##
     +@@ doc/muxers.texi: argument must be a time duration specification, and defaults to 0.
     + If enabled, write an empty segment if there are no packets during the period a
     + segment would usually span. Otherwise, the segment will be filled with the next
     + packet written. Defaults to @code{0}.
     ++
     ++@item segment_write_temp @var{1|0}
     ++Write segments to files with a .tmp extension. Each file is renamed to its 
     ++actual name on completion. This can help to prevent segment files from 
     ++being accessed before they are complete. Disabled by default (@code{0}).
     + @end table
     + 
     + Make sure to require a closed GOP when encoding and to set the GOP
     +
       ## libavformat/segment.c ##
      @@ libavformat/segment.c: typedef struct SegmentContext {
           int   break_non_keyframes;
     @@ libavformat/segment.c: static int set_segment_filename(AVFormatContext *s)
       
      +    // Write segment as a temp file and rename on completion
      +    if(seg->segment_write_temp) {
     -+        av_strlcatf(buf, sizeof(buf), ".tmp");
     -+        char *temp_name = av_strdup(buf);
     ++        char *temp_name = av_asprintf("%s%s", buf, ".tmp");
      +        if (!temp_name)
      +            return AVERROR(ENOMEM);
      +        ff_format_set_url(oc, temp_name);
  2:  2bad7a3acc <  -:  ---------- doc/muxers: Add documentation for segment_write_temp option
  3:  6a76e43900 <  -:  ---------- avformat/segment: Log more detailed information about written segments
  4:  4f05a7d2e9 !  2:  10b1c22439 avformat/segment: Add segment_limit option
     @@ Commit message
      
          Signed-off-by: softworkz <softworkz@hotmail.com>
      
     + ## doc/muxers.texi ##
     +@@ doc/muxers.texi: packet written. Defaults to @code{0}.
     + Write segments to files with a .tmp extension. Each file is renamed to its 
     + actual name on completion. This can help to prevent segment files from 
     + being accessed before they are complete. Disabled by default (@code{0}).
     ++
     ++@item segment_limit @var{number}
     ++Stops after the specified number of segments has been generated.
     ++This can be helpful to fill gaps in a range of already generated segments,
     ++which is difficult to achieve otherwise as it would either cause the last 
     ++segment to be incomplete or to overwrite an existing segment with a partial
     ++data. Default is @code{0} - no limit.
     + @end table
     + 
     + Make sure to require a closed GOP when encoding and to set the GOP
     +
       ## libavformat/segment.c ##
      @@ libavformat/segment.c: typedef struct SegmentContext {
           int   break_non_keyframes;
  5:  53b693320f <  -:  ---------- doc/muxers: Add documentation for segment_limit option
  6:  ddf37a882b <  -:  ---------- avformat/segment: Fix invalid codecpar extradata_size after copying
  7:  d5def15604 =  3:  a855134dc7 avformat/segment: Remove non-negative constraint from segment_time_delta
  8:  16cb8ea92b =  4:  33139f28c8 avformat/segment: Don't allow negative segment duration
  9:  1348b1b42c =  5:  64451d004a avformat/segment: Fix typo
 10:  88a8dc7875 =  6:  cb3267591d avformat/segment: Indent and whitespace fixes

-- 
ffmpeg-codebot
_______________________________________________
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".

  parent reply	other threads:[~2025-06-14  0:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13  5:54 [FFmpeg-devel] [PATCH 00/10] " ffmpegagent
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 01/10] avformat/segment: Add segment_write_temp option softworkz
2025-06-13 20:37   ` Marton Balint
2025-06-13 21:43     ` softworkz .
2025-06-13 22:07       ` Marton Balint
2025-06-13 22:26         ` softworkz .
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 02/10] doc/muxers: Add documentation for " softworkz
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 03/10] avformat/segment: Log more detailed information about written segments softworkz
2025-06-13 13:42   ` Derek Buitenhuis
2025-06-13 14:03     ` softworkz .
2025-06-13 20:44   ` Marton Balint
2025-06-13 23:53     ` softworkz .
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 04/10] avformat/segment: Add segment_limit option softworkz
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 05/10] doc/muxers: Add documentation for " softworkz
2025-06-13 20:25   ` Marton Balint
2025-06-13 21:33     ` softworkz .
2025-06-13 21:59       ` Marton Balint
2025-06-13 22:49         ` softworkz .
2025-06-14 15:59           ` Marton Balint
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 06/10] avformat/segment: Fix invalid codecpar extradata_size after copying softworkz
2025-06-13  6:03   ` softworkz .
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 07/10] avformat/segment: Remove non-negative constraint from segment_time_delta softworkz
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 08/10] avformat/segment: Don't allow negative segment duration softworkz
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 09/10] avformat/segment: Fix typo softworkz
2025-06-13  5:54 ` [FFmpeg-devel] [PATCH 10/10] avformat/segment: Indent and whitespace fixes softworkz
2025-06-14  0:59 ` ffmpegagent [this message]
2025-06-14  0:59   ` [FFmpeg-devel] [PATCH v2 1/6] avformat/segment: Add segment_write_temp option softworkz
2025-06-14  0:59   ` [FFmpeg-devel] [PATCH v2 2/6] avformat/segment: Add segment_limit option softworkz
2025-06-14  0:59   ` [FFmpeg-devel] [PATCH v2 3/6] avformat/segment: Remove non-negative constraint from segment_time_delta softworkz
2025-06-14  0:59   ` [FFmpeg-devel] [PATCH v2 4/6] avformat/segment: Don't allow negative segment duration softworkz
2025-06-14 20:40     ` Michael Niedermayer
2025-06-14  0:59   ` [FFmpeg-devel] [PATCH v2 5/6] avformat/segment: Fix typo softworkz
2025-06-14  0:59   ` [FFmpeg-devel] [PATCH v2 6/6] avformat/segment: Indent and whitespace fixes softworkz

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=pull.96.v2.ffstaging.FFmpeg.1749862752.ffmpegagent@gmail.com \
    --to=ffmpegagent-at-gmail.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=softworkz@hotmail.com \
    /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