From: Tobias Rapp <t.rapp@noa-archive.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] libavutil/log: Support for logging timestamps in the log
Date: Thu, 19 Jan 2023 09:24:15 +0100
Message-ID: <ff1bb7ac-7954-082d-d133-dc32a1f501bd@noa-archive.com> (raw)
In-Reply-To: <CAB1hn_x0db77L9_Kd_1WPV8kDLbhMxdwry8iShreGHY-XNEfcA@mail.gmail.com>
On 19/01/2023 00:20, Prakash wrote:
> The problem with int milliseconds is you lose the microseconds precision.
> Sometimes there are multiple log lines within the same millisecond.
If you want to do performance profiling like comparing between assembler
and C versions of a routine in my opinion there are better ways to do
that than using log timestamps. But I also have nothing against adding
more positions after the decimal point, if you prefer that.
The usecase I see for log timestamps is more to find out whether a
warning message appeared at the begin, middle, or end of the transcoding
process.
> I can
> definitely move the timestamp as the first field of the log line. Let me
> fix the patch file.
>
> -Prakash.
>
Regards, Tobias
_______________________________________________
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-01-19 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 21:52 Prakash
2023-01-18 8:51 ` Tobias Rapp
2023-01-18 23:20 ` Prakash
2023-01-19 8:24 ` Tobias Rapp [this message]
2023-02-17 0:16 ` Prakash
2023-02-17 11:07 ` Anton Khirnov
2023-02-17 11:49 ` Lynne
2023-02-17 18:55 ` Prakash
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=ff1bb7ac-7954-082d-d133-dc32a1f501bd@noa-archive.com \
--to=t.rapp@noa-archive.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