From: Nuo Mi <nuomi2021@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] 回复: [PATCH v1 17/19] avcodec/vvc: support fields
Date: Wed, 23 Apr 2025 21:54:46 +0800
Message-ID: <CAFXK13cYMUaQPUTqAuP4nS1rJKJtHK+6pZi1QWBjWiVP--+RhQ@mail.gmail.com> (raw)
In-Reply-To: <OS3PR01MB994463507E28C84BFC5C91B1CAAC2@OS3PR01MB9944.jpnprd01.prod.outlook.com>
Hi Andreas,
Thank you for the review.
Hi Jianhua,
Thank you for the patches. I will merge this weekend if there are no
objections.
On Wed, Apr 2, 2025 at 2:11 AM Wu Jianhua <toqsxw@outlook.com> wrote:
> Andreas Rheinhardt <andreas.rheinhardt@outlook.com>:
> > toqsxw@gmail.com:
> >> From: Wu Jianhua <toqsxw@outlook.com>
> >>
> >> passed files:
> >> FIELD_A_Panasonic_4.bit
> >> FIELD_B_Panasonic_2.bit
> >>
> >> Signed-off-by: Wu Jianhua <toqsxw@outlook.com>
> >> ---
> >> libavcodec/vvc/refs.c | 8 ++++++++
> >> 1 file changed, 8 insertions(+)
> >>
> >> diff --git a/libavcodec/vvc/refs.c b/libavcodec/vvc/refs.c
> >> index cfbc2977c0..79967b77d3 100644
> >> --- a/libavcodec/vvc/refs.c
> >> +++ b/libavcodec/vvc/refs.c
> >> @@ -160,6 +160,14 @@ static VVCFrame *alloc_frame(VVCContext *s,
> VVCFrameContext *fc)
> >> frame->ref_width = pps->r->pps_pic_width_in_luma_samples -
> win->left_offset - win->right_offset;
> >> frame->ref_height = pps->r->pps_pic_height_in_luma_samples -
> win->bottom_offset - win->top_offset;
> >>
> >> + if (fc->sei.frame_field_info.present) {
> >> + if (fc->sei.frame_field_info.picture_struct ==
> AV_PICTURE_STRUCTURE_TOP_FIELD)
> >> + frame->frame->flags |= AV_FRAME_FLAG_TOP_FIELD_FIRST;
> >> + if (fc->sei.frame_field_info.picture_struct ==
> AV_PICTURE_STRUCTURE_TOP_FIELD ||
> >> + fc->sei.frame_field_info.picture_struct ==
> AV_PICTURE_STRUCTURE_BOTTOM_FIELD)
> >> + frame->frame->flags |= AV_FRAME_FLAG_INTERLACED;
> >> + }
> >> +
> >> frame->progress = alloc_progress();
> >> if (!frame->progress)
> >> goto fail;
> >
> > Does this output the fields separately? Normally, FFmpeg/libavcodec only
> > outputs actual frames and marks these with the AV_FRAME_FLAG_INTERLACED
> > flag if the content is interlaced. AV_FRAME_FLAG_INTERLACED does not
> > mean that it is a single field.
> >
> >- Andreas
>
> The vvc decoder will output the each single fields and need to use the
> filter 'tinterlace' to output the actual frames,
> so I don't need to mark it with AV_FRAME_FLAG_INTERLACED flag, right?
>
> Jianhua
> _______________________________________________
> 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:[~2025-04-23 13:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 17:15 [FFmpeg-devel] [PATCH v1 01/19] avcodec/cbs_sei_syntax_template: add sei message film_grain_characteristics toqsxw
2025-04-01 17:15 ` [FFmpeg-devel] [PATCH v1 02/19] avcodec/vvc: support decoding prefix and suffix nal units toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 03/19] avcodec/vvc/sei: add decode_film_grain_characteristics toqsxw
2025-04-25 22:11 ` Andreas Rheinhardt
2025-04-26 10:56 ` [FFmpeg-devel] 回复: " Wu Jianhua
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 04/19] avcodec/vvc/dec: export sei to the frame when the frame starts toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 05/19] avcodec/vvc/dec: support applying film grain by the decoder toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 06/19] avcodec/vvc/dec: support removing film grain params from side data toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 07/19] avcodec/h274: add H274SEIPictureHash struct toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 08/19] avcodec/vvc/sei: add decode_decoded_picture_hash toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 09/19] avcodec/h274: add ff_h274_hash functions toqsxw
2025-04-25 22:01 ` Andreas Rheinhardt
2025-05-08 18:36 ` [FFmpeg-devel] 回复: " Wu Jianhua
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 10/19] avcodec/vvcdec: verify picture hash toqsxw
2025-04-25 22:02 ` Andreas Rheinhardt
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 11/19] avcodec/cbs_sei_syntax_template: add sei message sei_display_orientation toqsxw
2025-04-25 22:05 ` Andreas Rheinhardt
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 12/19] avcodec/vvc/sei: add decode_display_orientation toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 13/19] avcodec/vvc/sei: add decode_content_light_level_info toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 14/19] avcodec/cbs_sei_syntax_template: add sei message frame_field_information toqsxw
2025-04-25 22:08 ` Andreas Rheinhardt
2025-04-25 22:12 ` James Almer
2025-04-25 22:55 ` Andreas Rheinhardt
2025-04-25 22:58 ` James Almer
2025-04-25 23:02 ` Andreas Rheinhardt
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 15/19] avcodec/h274: add H274SEIFrameFieldInfo struct toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 16/19] avcodec/vvc/sei: add decode_frame_field_info toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 17/19] avcodec/vvc: support fields toqsxw
2025-04-01 17:35 ` Andreas Rheinhardt
2025-04-01 18:11 ` [FFmpeg-devel] 回复: " Wu Jianhua
2025-04-23 13:54 ` Nuo Mi [this message]
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 18/19] avcodec/vvc/sei: add decode_ambient_viewing_environment toqsxw
2025-04-01 17:16 ` [FFmpeg-devel] [PATCH v1 19/19] avcodec/vvc/sei: add decode_mastering_display_colour_volume toqsxw
2025-04-25 21:37 ` [FFmpeg-devel] [PATCH v1 01/19] avcodec/cbs_sei_syntax_template: add sei message film_grain_characteristics Andreas Rheinhardt
2025-04-26 11:37 ` [FFmpeg-devel] 回复: " Wu Jianhua
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=CAFXK13cYMUaQPUTqAuP4nS1rJKJtHK+6pZi1QWBjWiVP--+RhQ@mail.gmail.com \
--to=nuomi2021@gmail.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