From: Niklas Haas <ffmpeg@haasn.xyz> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] ebur128 bounty Date: Thu, 12 Jun 2025 16:59:44 +0200 Message-ID: <20250612165944.GB113284@haasn.xyz> (raw) In-Reply-To: <9892DC78-8E65-4DE5-9491-6F3D9C2E3153@spectre-music.com> On Thu, 12 Jun 2025 16:49:34 +0200 Guillaume Khayat <gkhayat@spectre-music.com> wrote: > Hello, > > The small company I work at uses ebur128 filter. > > I’m offering a bounty to improve the filter’s performance on x86 machines. > > I’m offering 800 EUR per 10% gain from current baseline, up to 50%/4000 EUR. > > I’m aware of 2 recent, promising initiatives to improve performance: > - our own incomplete attempt using SIMD instructions (-17%): https://ffmpeg.org/pipermail/ffmpeg-devel/2025-April/342383.html > - Paul Mahol’s recent work in his fork (-20-25%) > > Notes: > - Solution should of course remain EBU R128 compliant (see EBU Loudness Test Set [1], EBU 3341 [2] and EBU 3342 [3] specs) > - Solution can use FMA, AVX, AVX2 but not AVX512. > - Evaluation should be done w/ true peak detection disabled (e.g. "ffmpeg -i ~/test.wav -af ebur128=peak=none:framelog=quiet -f null -“) > - I can offer a down payment at start of work of 800 EUR as a gesture of good will. Rest of payment on patch merge into ffmpeg + invoice > > I tried doing this myself but I lack the skills and proper time to learn them on the job. Always happy to sponsor some OSS work though! Hi, I'm happy to take a look at this. To be clear, you are fine with me taking your existing SIMD code as a starting point? Out of curiousity, did you try the "loudnorm" filter as well? > > Best, > > Guillaume > > [1]: https://tech.ebu.ch/publications/ebu_loudness_test_set > [2]: https://tech.ebu.ch/files/live/sites/tech/files/shared/tech/tech3341.pdf > [3]: https://tech.ebu.ch/files/live/sites/tech/files/shared/tech/tech3342.pdf > _______________________________________________ > 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".
next prev parent reply other threads:[~2025-06-12 14:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-12 14:49 Guillaume Khayat 2025-06-12 14:59 ` Niklas Haas [this message] 2025-06-12 15:09 ` Guillaume Khayat 2025-06-12 20:18 ` Niklas Haas 2025-06-13 7:45 ` Guillaume Khayat
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=20250612165944.GB113284@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --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