You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ffmpeg.exe -hide_banner -loglevel quiet -i "10-bit-input.mkv" -an -pix_fmt yuv420p10le -strict -1 -f yuv4mpegpipe - | rav1e-ch.exe - --speed 4 --quantizer 120 --primaries bt2020 --transfer smpte2084 --mastering-display G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(1,10000000) --content-light (0,0) -y --output "10-bit-input.ivf"
! Chromaticity coordinates will be trimmed to the range 0.0 to 1.0 (see AV1 spec sec. 6.7.4).
thread 'main' panicked at 'Cannot parse the content light option: ScanError("parse::u16")', src\bin\common.rs:634:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Full command line without --content-light works and produces correct output - well, the color information is interpreted correctly by my player at least:
Versions:
rav1e 0.6.3 (v0.6.3) (release)
ffmpeg version 6.0-full_build-www.gyan.dev.
Windows 11 21h2 (though that does not matter here)
I am not sure whether this is actually me using the option wrong or whether rav1e is at fault here.
1 second source video to reproduce and test: https://joumxyzptlk.de/tmp/10-bit-input.mkv
Full command line which failes:
Full command line without --content-light works and produces correct output - well, the color information is interpreted correctly by my player at least:
ffmpeg.exe -hide_banner -loglevel quiet -i "10-bit-input.mkv" -an -pix_fmt yuv420p10le -strict -1 -f yuv4mpegpipe - | rav1e-ch.exe - --speed 4 --quantizer 120 --primaries bt2020 --transfer smpte2084 --mastering-display G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(1,10000000) -y --output "10-bit-input.ivf"
With trace:
The text was updated successfully, but these errors were encountered: