From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Paul B Mahol <onemda@gmail.com>,
Kieran Kunhya <kieran618@googlemail.com>,
Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/h264dec: Remove ff_h264_draw_horiz_band
Date: Tue, 02 Jul 2024 10:12:27 +0200
Message-ID: <171990794755.21847.12078797316079978714@lain.khirnov.net> (raw)
In-Reply-To: <CABGuwE=wWmyuOarV6CJ1NV6dc9YJBwLQkwRMm8mgA6Gm3m0XTw@mail.gmail.com>
Quoting Kieran Kunhya via ffmpeg-devel (2024-06-14 15:27:32)
> On Fri, Jun 14, 2024 at 1:53 PM Paul B Mahol <onemda@gmail.com> wrote:
> >
> >
> >
> > On Fri, Jun 14, 2024 at 2:41 PM Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
> >>
> >> On Sun, Jun 9, 2024 at 2:39 AM Andreas Rheinhardt
> >> <andreas.rheinhardt@outlook.com> wrote:
> >> >
> >> > The H.264 decoder does not support draw_horiz_band (it does not have
> >> > the AV_CODEC_CAP_DRAW_HORIZ_BAND), making ff_h264_draw_horiz_band()
> >> > legally dead. The function here always calls draw_horiz_band
> >> > in coded order, although the default case is display order.
> >>
> >> Why would you want a low latency decode mode with reordering?
> >> I have no idea about hwaccel, but I believe with low latency encoded
> >> video this does work.
> >
> >
> > Since when?
> >
> > See 0da71265d84b587c7159cd82708ca60ad050dd4c from 2003.
> >
> > flag remain commented out from then to this day.
>
> It still worked if you controlled the input.
Do you actually use this, or know anyone who does?
--
Anton Khirnov
_______________________________________________
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".
prev parent reply other threads:[~2024-07-02 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 1:39 Andreas Rheinhardt
2024-06-14 11:01 ` Andreas Rheinhardt
2024-06-14 12:41 ` Kieran Kunhya via ffmpeg-devel
2024-06-14 13:03 ` Paul B Mahol
2024-06-14 13:27 ` Kieran Kunhya via ffmpeg-devel
2024-07-02 8:12 ` Anton Khirnov [this message]
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=171990794755.21847.12078797316079978714@lain.khirnov.net \
--to=anton@khirnov.net \
--cc=andreas.rheinhardt@outlook.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--cc=onemda@gmail.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