Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Giovanni Mascellani via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Zhao Zhili <quinkblack@foxmail.com>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Cc: Giovanni Mascellani <gmascellani@codeweavers.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/h2645_vui: Interpret a degenerate SAR as unspecified.
Date: Tue, 4 Nov 2025 14:58:39 +0100
Message-ID: <50110314-e8d2-48d9-b229-d4c5faf4a035@codeweavers.com> (raw)
In-Reply-To: <tencent_E60E4E0670582D899A2A40FE9A8B9FC0AB08@qq.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 631 bytes --]

Hi,

Il 04/11/25 14:50, Zhao Zhili ha scritto:
>> The specification says that if either the numerator or the
>> denominator is zero then the SAR is to be intended unspecified.
>> Internally ffmpeg represents an unspecified SAR as 0/1, while
>> fractions with a zero denominator are not handled properly;
> 
> Is there any known issue?

I observed this problem with a bunch of video files provided by game 
OddBallers when executed with Wine/Proton. There is some more backstory 
on my first submission of this patch last year:

   https://ffmpeg.org/pipermail/ffmpeg-devel/2024-July/331835.html

Thanks, Giovanni.

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2025-11-04 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 13:37 [FFmpeg-devel] " Giovanni Mascellani via ffmpeg-devel
2025-11-04 13:50 ` [FFmpeg-devel] " Zhao Zhili via ffmpeg-devel
2025-11-04 13:58   ` Giovanni Mascellani via ffmpeg-devel [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=50110314-e8d2-48d9-b229-d4c5faf4a035@codeweavers.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=gmascellani@codeweavers.com \
    --cc=quinkblack@foxmail.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