Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marvin Scholz <epirat07@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat: Fix AV1 RTP wrong log condition
Date: Thu, 03 Apr 2025 16:37:14 +0200
Message-ID: <7C4777AD-17A8-4318-A500-B057231C8EA7@gmail.com> (raw)
In-Reply-To: <e07c659e-6e35-422a-b345-6d17528169ee@axis.com>

On 1 Apr 2025, at 11:26, Chris Hodges wrote:

> Fixed warning about OBU count being wrong, which can only be
> determined when the number of OBUs in the header is non-zero,
> not the other way round.
>
> Signed-off-by: Chris Hodges <chris.hodges@axis.com>
> ---
>  libavformat/rtpdec_av1.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/rtpdec_av1.c b/libavformat/rtpdec_av1.c
> index af3f9e0f09..7cfc83b03c 100644
> --- a/libavformat/rtpdec_av1.c
> +++ b/libavformat/rtpdec_av1.c
> @@ -373,7 +373,7 @@ static int av1_handle_packet(AVFormatContext *ctx, PayloadContext *data,
>          }
>          is_frag_cont = 0;
>
> -        if (!rem_pkt_size && !num_obus && (num_obus != obu_cnt)) {
> +        if (!rem_pkt_size && num_obus && (num_obus != obu_cnt)) {
>              av_log(ctx, AV_LOG_WARNING, "AV1 aggregation header indicated %u OBU elements, was %u\n",
>                     num_obus, obu_cnt);
>          }
> -- 
> 2.39.5

Thanks, LGTM, will apply.

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

      reply	other threads:[~2025-04-03 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  9:26 Chris Hodges
2025-04-03 14:37 ` Marvin Scholz [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=7C4777AD-17A8-4318-A500-B057231C8EA7@gmail.com \
    --to=epirat07@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