Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 03/10] avformat/segment: Log more detailed information about written segments
Date: Fri, 13 Jun 2025 22:44:49 +0200 (CEST)
Message-ID: <93a5c9ec-aade-0c81-7177-d0e2ac17314c@passwd.hu> (raw)
In-Reply-To: <6a76e43900f1ac469a138bc2f5163a46d4a1dfb5.1749794067.git.ffmpegagent@gmail.com>



On Fri, 13 Jun 2025, softworkz wrote:

> From: softworkz <softworkz@hotmail.com>
>
> Also moves point of log writing to after rename of temp files
> and changes log level to INFO. The completion of a segment is
> important enough to justify logging at INFO level.
>
> Signed-off-by: softworkz <softworkz@hotmail.com>
> ---
> libavformat/segment.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/libavformat/segment.c b/libavformat/segment.c
> index 04e973a198..608cad0ba4 100644
> --- a/libavformat/segment.c
> +++ b/libavformat/segment.c
> @@ -417,8 +417,6 @@ static int segment_end(AVFormatContext *s, int write_trailer, int is_last)
>         }
>     }
>
> -    av_log(s, AV_LOG_VERBOSE, "segment:'%s' count:%d ended\n",
> -           seg->avf->url, seg->segment_count);
>     seg->segment_count++;
>
>     if (seg->increment_tc) {
> @@ -471,6 +469,12 @@ static int segment_end(AVFormatContext *s, int write_trailer, int is_last)
>         av_free(final_filename);
>     }
>
> +    av_log(s, AV_LOG_INFO, "SegmentComplete=%s:%d Index=%d Start=%f End=%f Duration=%f offset_pts=%s start_pts=%s Frames=%d filename=%s\n",
> +           av_get_media_type_string(s->streams[seg->reference_stream_index]->codecpar->codec_type),
> +           seg->reference_stream_index, seg->segment_idx, seg->cur_entry.start_time, seg->cur_entry.end_time,
> +           seg->cur_entry.end_time - seg->cur_entry.start_time, av_ts2str(seg->cur_entry.offset_pts), av_ts2str(seg->cur_entry.start_pts),
> +           seg->segment_frame_count, seg->cur_entry.filename);

No CamelCase please, follow snake_case as the other similar messages. And 
yes, VERBOSE is the proper loglevel for this.

> +
>     return ret;
>
> fail:
> @@ -994,6 +998,8 @@ calc_times:
>     if (pkt->dts != AV_NOPTS_VALUE)
>         pkt->dts += offset;
>
> +    seg->cur_entry.offset_pts = av_rescale_q(offset, st->time_base, AV_TIME_BASE_Q);
> +

This line does not belong to this patch, or the patch description is 
incomplete.

Thanks,
Marton

>     av_log(s, AV_LOG_DEBUG, " -> pts:%s pts_time:%s dts:%s dts_time:%s\n",
>            av_ts2str(pkt->pts), av_ts2timestr(pkt->pts, &st->time_base),
>            av_ts2str(pkt->dts), av_ts2timestr(pkt->dts, &st->time_base));
> -- 
> 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".
>
_______________________________________________
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-13 20:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13  5:54 [FFmpeg-devel] [PATCH 00/10] avformat/segment: Various segment muxer improvements 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 [this message]
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 ` [FFmpeg-devel] [PATCH v2 0/6] avformat/segment: Various segment muxer improvements ffmpegagent
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=93a5c9ec-aade-0c81-7177-d0e2ac17314c@passwd.hu \
    --to=cus@passwd.hu \
    --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