From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] liavcodec: add bit-rate support to RoQ video encoder
Date: Mon, 22 Jan 2024 14:05:39 +0100
Message-ID: <36d117194f13247ca865305433f86d5d2851e4fe.camel@haerdin.se> (raw)
In-Reply-To: <f0767f5a-fd79-4002-9a3c-d1da8895d5f7@gmail.com>
mån 2024-01-22 klockan 00:08 +0300 skrev Victor Luchits:
> One can now use the bitrate option (-b) to specify bit rate of the
> video
> stream in the RoQ encoder. The option only becomes effective for
> values
> above 800kbit/s, which is roughly equivalent to bandwidth of a 1x-
> speed
> CD-ROM drive, minus the bandwidth taken up by stereo DPCM stream.
> Values
> below this threshold produce visually inadequate results.
>
> Original patch by Joseph Fenton aka Chilly Willy
>
> Signed-off-by: Victor Luchits <vluchits@gmail.com>
> ---
> Changelog | 1 +
> libavcodec/roqvideo.h | 1 +
> libavcodec/roqvideodec.c | 15 +++++
> libavcodec/roqvideoenc.c | 118 ++++++++++++++++++++++++++++++++++--
> ---
> libavcodec/version.h | 2 +-
> 5 files changed, 123 insertions(+), 14 deletions(-)
Fails to apply with git am on current master
> warning: Patch sent with format=flowed; space at the end of lines
> might be lost.
> Applying: liavcodec: add bit-rate support to RoQ video encoder
> error: corrupt patch at line 20
> Patch failed at 0001 liavcodec: add bit-rate support to RoQ video
> encoder
Typo: liavcodec
> + /* Keyframe when no MOT or FCC codes in frame */
> + if (s->key_frame) {
> + av_log(avctx, AV_LOG_VERBOSE, "\nFound keyframe!\n");
> + rframe->pict_type = AV_PICTURE_TYPE_I;
> + avpkt->flags |= AV_PKT_FLAG_KEY;
Consider resetting framesSinceKeyframe here
> - if (avctx->width > 65535 || avctx->height > 65535) {
The leading space is probably what makes the patch not apply
> - av_log(avctx, AV_LOG_ERROR, "Dimensions are max %d\n", enc-
> >quake3_compat ? 32768 : 65535);
> + if (enc->quake3_compat && ((avctx->width > 32767 || avctx-
> >height > 32767))) {
> + av_log(avctx, AV_LOG_ERROR, "Dimensions are max %d\n",
> 32767);
> + return AVERROR(EINVAL);
> + }
> + else if (avctx->width > 65535 || avctx->height > 65535) {
> + av_log(avctx, AV_LOG_ERROR, "Dimensions are max %d\n",
> 65535);
> return AVERROR(EINVAL);
> }
> - if (((avctx->width)&(avctx->width-1))||((avctx->height)&(avctx-
> >height-1)))
> + if (enc->quake3_compat && ((avctx->width)&(avctx->width-
> 1))||((avctx->height)&(avctx->height-1)))
> av_log(avctx, AV_LOG_ERROR, "Warning: dimensions not power
> of two, this is not supported by quake\n");
These changes appear to be unrelated to bitrate. Consider separating
them into a separate patch.
> - if (frame->quality)
> - enc->lambda = frame->quality - 1;
> - else
> - enc->lambda = 2*ROQ_LAMBDA_SCALE;
> + if (avctx->bit_rate <= ROQ_DEFAULT_MIN_BIT_RATE) {
> + /* no specific bit rate desired, use frame quality */
> + if (frame->quality)
> + enc->lambda = frame->quality - 1;
> + else
> + enc->lambda = 2*ROQ_LAMBDA_SCALE;
> + }
This looks like a bit of a janky way to switch between qscale and
bitrate. Isn't there a way to detect whether an option has been set
explicitly? At the very least this behavior should be documented in
doc/encoders.texi
/Tomas
_______________________________________________
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:[~2024-01-22 13:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 21:08 Victor Luchits
2024-01-22 13:05 ` Tomas Härdin [this message]
2024-01-22 13:38 ` Victor Luchitz
2024-01-22 13:57 ` Tomas Härdin
2024-01-22 13:59 ` Martin Storsjö
2024-01-22 14:19 ` Tomas Härdin
2024-01-22 16:36 ` Victor Luchitz
2024-01-22 16:21 ` Victor Luchitz
2024-01-22 18:32 ` Victor Luchitz
2024-01-22 19:10 ` Tomas Härdin
2024-01-22 19:16 ` Victor Luchitz
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 19:14 Victor Luchits
2024-01-22 21:12 ` Tomas Härdin
2024-01-22 21:40 ` Victor Luchitz
2024-01-22 23:25 ` Tomas Härdin
2024-01-22 22:39 ` epirat07
2024-01-21 20:19 Victor Luchits
2024-01-21 21:02 ` Michael Niedermayer
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=36d117194f13247ca865305433f86d5d2851e4fe.camel@haerdin.se \
--to=git@haerdin.se \
--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