Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kyle Swanson <k@ylo.ph>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter: merge loudnorm filter functionality into f_ebur128.c
Date: Tue, 21 Nov 2023 10:53:10 -0800
Message-ID: <CALbjROJerAVHdLk25ck1a6emGS3RQnWF81+CP4ofgqKsYaVqLQ@mail.gmail.com> (raw)
In-Reply-To: <CAPYw7P4JMu6J6dWMo=fy4S95=46m_j1SO_aKMzTh1CzQj3E0Sw@mail.gmail.com>

Hi,

On Sun, Nov 19, 2023 at 3:48 AM Paul B Mahol <onemda@gmail.com> wrote:
>
> On Fri, Nov 17, 2023 at 7:38 AM Kyle Swanson <k@ylo.ph> wrote:
>
> > Hi,
> >
> > On Wed, Nov 15, 2023 at 12:39 PM Paul B Mahol <onemda@gmail.com> wrote:
> > >
> > > Attached.
> >
> > Only had a few minutes to look at this. Seems like more than just
> > merging two filters, I see a bunch of new filter options for example.
> > Can you explain?
> >
>
> The linear mode and scanning, both input to filter and filter output itself
> should give similar results.
> The dynamic mode now actually can be configured how aggressively it will
> expand / compress audio.
> Because current state of filter have numerous issues:
>
>  - using unmaintained old libebur128 module, when same functionality is
> already available in existing filter.
>  - code duplication and functionality duplication due the above
>  - buggy limiter - causing clipped samples randomly
>  - buggy first and final frame filtering
>  - over-complicated flow path for dynamic code in filter
>  - excessive compressing of audio dynamic range, causing extreme smaller
> LRU from output audio
>  - and probably more that I forgot
>
> Some options from this patch can be probably removed, like attack/release
> options, and just use defaults as currently in patch.
>
>
> > Thanks,
> > Kyle

OK. Give me some time to review this. Unfortunately, I can't be quick
since it is a Holiday week here and the diff is pretty hard to read.
I'm hoping this still gives exact/equivalent loudnorm output, since
this is a pretty widely used filter. My first reaction is combining
the filters like this might make things more complicated, but I will
keep an open mind while reviewing.

Thanks,
Kyle
_______________________________________________
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".

  parent reply	other threads:[~2023-11-21 18:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 21:46 Paul B Mahol
2023-11-15 20:46 ` Paul B Mahol
2023-11-17  6:38   ` Kyle Swanson
2023-11-19 11:56     ` Paul B Mahol
2023-11-19 21:55       ` Marton Balint
2023-11-19 23:37         ` Paul B Mahol
2023-11-21 18:53       ` Kyle Swanson [this message]
2023-11-28 16:51   ` Paul B Mahol
2023-11-30 11:43     ` Anton Khirnov
2023-11-30 12:48       ` Paul B Mahol
2023-11-30 13:47         ` Anton Khirnov
2023-11-30 14:01           ` Paul B Mahol
2023-11-30 13:57             ` Anton Khirnov
2023-11-30 14:20               ` Paul B Mahol
2023-11-30 18:34                 ` Kyle Swanson
2023-11-30 21:44                   ` Paul B Mahol
2023-11-30 22:19                     ` Kyle Swanson
2023-11-30 22:51                       ` Paul B Mahol
2023-11-30 23:29                         ` Kyle Swanson
2023-12-01 10:45                           ` Paul B Mahol
2023-12-01 21:12                             ` Kyle Swanson
2023-12-01 21:27                               ` Paul B Mahol

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=CALbjROJerAVHdLk25ck1a6emGS3RQnWF81+CP4ofgqKsYaVqLQ@mail.gmail.com \
    --to=k@ylo.ph \
    --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