From: "Wujian(Chin)" <wujian2@huawei.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "zhangxiong \(A\)" <zhangxiong3@huawei.com>,
Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] 答复: [PATCH] fftools/ffprobe.c: Add new Function: The peak bit rate of video streams can be queried
Date: Mon, 27 Jun 2022 08:28:56 +0000
Message-ID: <00efa174fe5846f9b9f6724c96e871dd@huawei.com> (raw)
In-Reply-To: <MR1P264MB2483DE1AF12A599B6090DB409BB99@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM>
>>Code Process
>>- Calculate the frame rate first
>>- Obtain the maximum value of the total bytes of all packets according
>>to the number of frames per second
>Nicolas George already answered you the 23th about required documentation.
>In my opinion, there is today a commonplace definition of max bitrate that involves computation over a sliding window of 1s. This is reinforced by ISO/MP4 (14496-12), but even in the broadcast industry with the MXF file format, this is currently how a max bitrate is understood.
>I fear that introducing another method of computation will raise some confusion for many end users.
>Nicolas
thks,I got it.
Wujian(Chin)
_______________________________________________
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".
next prev parent reply other threads:[~2022-06-27 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 3:01 [FFmpeg-devel] " Wujian(Chin)
2022-06-27 8:01 ` Nicolas Gaullier
2022-06-27 8:28 ` Wujian(Chin) [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 13:45 Wujian(Chin)
2022-06-23 14:33 ` Nicolas George
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=00efa174fe5846f9b9f6724c96e871dd@huawei.com \
--to=wujian2@huawei.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=george@nsup.org \
--cc=zhangxiong3@huawei.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