djbclark
commented
7 years ago These links look possibly apropos:
- (Update: I think this one actually isn't useful because it shows a stream copy, but loudnorm needs to analyze the entire file according to this.) "You can use one filtergraph to rule them all" answer at ffmpeg error : -vf/-af/-filter and -filter_complex cannot be used together (StackExchange)
- https://github.com/rg3/youtube-dl/issues/13511#issuecomment-311552547
- Dual-pass mode documented here.
Dual-pass mode requires two calls to the loudnorm filter, the first of which is for measurement. This command will print loudness stats to stderr as JSON, and create no output file. Of course, dual-pass normalization can be easily scripted.
ffmpeg -i in.wav -af loudnorm=I=-16:TP=-1.5:LRA=11:print_format=json -f null -
{
"input_i" : "-27.61",
"input_tp" : "-4.47",
"input_lra" : "18.06",
"input_thresh" : "-39.20",
"output_i" : "-16.58",
"output_tp" : "-1.50",
"output_lra" : "14.78",
"output_thresh" : "-27.71",
"normalization_type" : "dynamic",
"target_offset" : "0.58"
}We can then use these stats to call FFmpeg for a second time. Supplying the filter with these stats allow it to make more intelligent normalization decisions, as well as normalize linearly if possible. This second pass creates the loudness normalized output file, and prints a human-readable stats summary to stderr.
ffmpeg -i in.wav -af loudnorm=I=-16:TP=-1.5:LRA=11:measured_I=-27.61:measured_LRA=18.06:measured_TP=-4.47:measured_thresh=-39.20:offset=0.58:linear=true:print_format=summary -ar 48k out.wav
Input Integrated: -27.5 LUFS
Input True Peak: -4.5 dBTP
Input LRA: 18.1 LU
Input Threshold: -39.2 LUFS
Output Integrated: -16.0 LUFS
Output True Peak: -1.5 dBTP
Output LRA: 14.6 LU
Output Threshold: -27.2 LUFS
Normalization Type: Dynamic
Target Offset: +0.0 LU
FallingSnow
Using Bleeding edge 0.5.0 2017-08-23 4:49pm EDT installed via
npm install FallingSnow/h265ize --globalUsing sample media files from https://github.com/mediaelement/mediaelement-files
$ h265ize --normalize-level 4 --debug big_buck_bunny.mp4The h265ize.log.txt doesn't look to have anything useful. The console output error is:
However I think that is also not useful, just complaining that a file it was expecting didn't exist because of ffmpeg failing. However if you manually run the ffmpeg command from the log
There seems to be one or two problems; if the logging is to be believed it looks like maybe there is a typo and it is running "ffmpeg" instead of "nice" with the error you'd expect from this mistake:
However stripping off the "ffmpeg -n 10" still leaves an error:
I've tried with both HEAD ffmpeg compiled from source and a ffmpeg static snapshot build, both separately and from within h265ize using:
export FFMPEG_PATH="/Applications/ffmpeg-static"with the same results.Also
h265ize --versionseems to be broken, gives:But looking at it manually shows the latest 0.5.0 git seems to be installed: