From: Tobias Rapp via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
Carl Hetherington <cth@carlh.net>, Niklas Haas <ffmpeg@haasn.xyz>,
Tobias Rapp <t.rapp@noa-archive.com>
Subject: [FFmpeg-devel] Re: [PATCH] libavfilter: Fix incorrect ebur128 peak calculation.
Date: Tue, 18 Nov 2025 09:04:58 +0100
Message-ID: <c93aff13-d5b7-4099-87b8-112c99de4e4e@noa-archive.com> (raw)
In-Reply-To: <176339171541.8.12636206057646773265.1011234232@haasn.xyz>
On 17/11/2025 16:01, Niklas Haas wrote:
> On Monday, November 17th, 2025 at 3:48 PM, Tobias Rapp via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
>>
>> On 11/11/2025 03:33, Michael Niedermayer via ffmpeg-devel wrote:
>>
>>> Hi
>>>
>>> adding niklas to the CC so its not missed
>>> but i agree the patch LGTM
>>>
>>> On Tue, Nov 04, 2025 at 08:52:36PM +0100, Nicolas George via ffmpeg-devel wrote:
>>>
>>>> Carl Hetherington via ffmpeg-devel (HE12025-11-03):
>>>>
>>>>> Since 3b26b782eeded9b9ab7fac013cd1a83a30d68206 it would only look at the
>>>>> first channel.
>>>>>
>>>>> Signed-off-by: cth@carlh.net
>>>>> ---
>>>>> libavfilter/f_ebur128.c | 2 +-
>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>> Hi. Thanks for the patch. I suspect the issue has been here for a longer
>>>>> time, if only on one branch of the conditional build:
>>>> #if CONFIG_SWRESAMPLE
>>>> …
>>>> const double sample = fabs(swr_samples[i * nb_channels]);
>>>> #endif
>>>>
>>>> versus
>>>>
>>>> const double *restrict samples_ch = &samples[ch];
>>>> …
>>>> const double sample = fabs(samples_ch[nb_channels * i]);
>>>>
>>>> Anyway, the fix looks good to me.
>>>>
>>>> Niklas, it has become mostly your code, what do you make of it?
>>
>> Now that n8.0.1 will be tagged soonish it would be great if this fix
>> could be included.
>>
>> Regards, Tobias
> Hi Tobias,
>
> Sorry for the delay in responding. I agree that this seems to be a bug that has been around for quite a while, and that your fix seems correct.
>
> I also don't suspect the performance will be impacted as a result, unless the compiler is really very clever to eliminate the common subcalculation by reassociating the FFMAX calls.
>
> Thanks,
> Niklas
>
> P.s. In the future, it's probably faster if you submit patches directly on https://code.ffmpeg.org/
I'm not the author of the patch, just a random person that did a ping :-)
Have added you as a reviewed-by to the commit message and pushed the
patch to master and release/8.0. Thanks Carl for the patch, and thanks
to Nicolas, Michael and Niklas for taking a look.
Regards, Tobias
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-11-18 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 20:38 [FFmpeg-devel] " Carl Hetherington via ffmpeg-devel
2025-11-04 19:52 ` [FFmpeg-devel] " Nicolas George via ffmpeg-devel
2025-11-04 21:34 ` Carl Hetherington via ffmpeg-devel
2025-11-11 2:33 ` Michael Niedermayer via ffmpeg-devel
2025-11-17 14:47 ` Tobias Rapp via ffmpeg-devel
2025-11-17 15:01 ` Niklas Haas via ffmpeg-devel
2025-11-18 8:04 ` Tobias Rapp 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=c93aff13-d5b7-4099-87b8-112c99de4e4e@noa-archive.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=cth@carlh.net \
--cc=ffmpeg@haasn.xyz \
--cc=michael@niedermayer.cc \
--cc=t.rapp@noa-archive.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