Re: Question: How to enable FFmpeg logging in Chromium?

[Dale Curtis]

@media-dev 

Hi Mingzhe,

In developer builds you can control the amount of logs by changing the log level value here:

* https://source.chromium.org/chromium/chromium/src/+/main:media/base/media.cc;l=46;drc=dc1d5a68d4e3cabecd33e1258d5902f7d9fc78dd

E.g., AV_LOG_LEVEL_TRACE. See all enums here:

* https://source.chromium.org/chromium/chromium/src/+/main:third_party/ffmpeg/libavutil/log.h;l=189;drc=e63596721df61bbc199c38c4a102597ad81ad154

Good luck!

- dale

On Thu, Feb 5, 2026 at 10:56 PM Mingzhe Yue <yuem...@gmail.com> wrote:

Hi Dale, 

I noticed you committed the CHROMIUM_NO_LOGGING switch for FFmpeg in Chromium a few years ago. 

I'm currently debugging some audio decoding issues and found the error was happening inside the ffmpeg module (avcodec_send_packet failed: -1094995529 (Invalid data found when processing input)) and would like to view FFmpeg's internal logs.
I tried setting is_official_build=false and couldn't get the log. I'm not sure if that's the correct approach or if there's a simpler way to enable FFmpeg logging.

Could you point me to the recommended way to enable FFmpeg logs in Chromium?

Thanks!