Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] H.261 patch to detect Iframe in H.261 decoder
Date: Mon, 10 Feb 2025 17:04:58 +0100
Message-ID: <AS8P250MB0744A0189A679FA3160294E08FF22@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CADzfgVdZL=Zyrz6sHUvHTTNBBaR4Nfq6twqJrbwyWxJPopiM4A@mail.gmail.com>

Jerome GORIN:
> -    skip_bits1(&s->gb); /* freeze picture release off */
> +    intra_flag = get_bits1(&s->gb); /* Intra 1 = I-frame, 0 = P-frame */
>  
> +    if (intra_flag){
> +        s->pict_type = AV_PICTURE_TYPE_I;
> +    }else{
> +        s->pict_type = AV_PICTURE_TYPE_P;
> +    }
> +    
>      format = get_bits1(&s->gb);
>  
>      // only 2 formats possible
> @@ -498,10 +504,8 @@ static int h261_decode_picture_header(H261DecContext *h)
>      if (skip_1stop_8data_bits(&s->gb) < 0)
>          return AVERROR_INVALIDDATA;
>  
> -    /* H.261 has no I-frames, but if we pass AV_PICTURE_TYPE_I for the first
> -     * frame, the codec crashes if it does not contain all I-blocks
> -     * (e.g. when a packet is lost). */
> -    s->pict_type = AV_PICTURE_TYPE_P;
> +
> +    

H.261 does not guarantee that a picture with the freeze picture release
bit set is an actual keyframe; the macroblocks can nevertheless be inter
coded (such a bitstream could cause a segfault with your patch because
it tries to access references that aren't there).

- Andreas

_______________________________________________
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".

      reply	other threads:[~2025-02-10 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 10:09 Jerome GORIN
2025-02-10 16:04 ` Andreas Rheinhardt [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=AS8P250MB0744A0189A679FA3160294E08FF22@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.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