#9221 closed task (invalid)
How to set yuv to full range in a mpeg2video?
| Reported by: | Jefferson Villasan Josol | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | avfilter |
| Version: | git-master | Keywords: | Full range |
| Cc: | mirh | Blocked By: | |
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
I've found out that YUV420P has a limited range based on MediaInfo
How can I set that into Full range using ffmpeg? Does anyone know how to set it into Full?
I'm currently using mpeg2video -q:v 0 because it has an acceptable quality and small file sizes compared to x264 -crf 0
Thanks in advance for those who can help me!
Change History (4)
follow-up: 2 comment:1 by , 3 years ago
comment:2 by , 3 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
yuvj420p is full range, where j means full range and p means planar. But I recommend to use modern and not deprecated -vf scale=out_range=pc -color_range pc file.mp4
can I use BT.2020 on 1080p video?
Yes, both SDR and as part of BT.2100, i.e. HDR.
x264 -crf 0
Is mathematically lossless. mpeg2video is not. Seriously?
Also please stop asking such questions on a bugtracker. I agree those options (and their defaults and their strange behaviour) is confusing as hell.
comment:3 by , 2 years ago
x264 -crf 0
Is not lossless, I was wrong. Both x264 and ffmepg require -qp 0 instead.
comment:4 by , 2 years ago
| Cc: | added |
|---|
I would guess a bug report to track the stupid JPEG pixel format related behaviours is due.
Putting even aside their eventual removal, it's kinda pathetic that ffmpeg will trigger random warnings by itself just because you are extracting/converting yuv420p to/from jpeg.
Another question, can I use BT.2020 on 1080p video?