<div dir="ltr"><div class="gmail_default" style="font-size:small">Tarantas, thank you very much for working through a solution for this issue and providing the "real world" example. Andrea, thank you for the Latex version for the manual which has been checked into GIT and will appear in the September 30th manual. As usual, I changed a few trivial things; for example "loose" to "lose".<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 30, 2024 at 4:39 PM Tarantas via Cin <<a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, 29 Aug 2024 22:12:38 +0000<br>
Andrea paz <<a href="mailto:gamberucci.andrea@gmail.com" target="_blank">gamberucci.andrea@gmail.com</a>> wrote:<br>
<br>
> I don't think YT skips color compression if set directly as YT wants<br>
> it. Anyway it's a complicated and interesting topic and if you do<br>
> tests and find an optimal solution please let me know and I'll put it<br>
> in the manual.<br>
<br>
Well, here's my draft if I would write such a manual.<br>
<br>
"""<br>
Title: [the subject of this thread actually]<br>
<br>
For a historical reasons, almost every piece of video software uses<br>
limited range [...]<br>
<br>
But, sometimes you have to deal with files encoded utilizing the full<br>
range. For example, some video cameras encode full range files. The<br>
simplest way to deal with them is just to re-encode in limited range:<br>
<br>
ffmpeg -i input.mp4 -c:v libx264 -preset fast -crf 19 -c:a copy \<br>
-pix_fmt yuv420p output.mp4<br>
<br>
But, this is not an option for you if you're either a perfectionist or<br>
trying to fight color banding.<br>
<br>
Color banding is a video artifact that could be visible in smooth areas<br>
of the video.<br>
Here's an example: <a href="https://youtu.be/KL8CIZej19o" rel="noreferrer" target="_blank">https://youtu.be/KL8CIZej19o</a><br>
If you don't see the ugly background, then you don't need to worry<br>
about the whole issue.<br>
<br>
Color banding is different from compression artifacts. You can't fight<br>
it just by increasing the bitrate of your video.<br>
<br>
Color banding comes from color correction performed too much or in<br>
inaccurate way. And it stacks, so if you faced it, then you should get<br>
rid of dynamic range compression at every step it happens.<br>
<br>
Cinelerra has a native full color range support, and you can enable it<br>
via:<br>
Settings -> Preferences -> Appearance -> YUV color range: JPEG<br>
Note how everything will loose contrast and become grey-ish.<br>
<br>
But, in this mode, Cinelerra will also render full range video files.<br>
There are two reasons why it could be a bad thing:<br>
- some video players don't understand what full range is and will play<br>
these resulting videos with the increased contrast;<br>
- some image processing software (like YouTube) will re-encode full<br>
range videos into limited range by compressing the dynamic range and<br>
making the color banding issue even worse.<br>
<br>
That's why you should make a couple of hacks.<br>
First, after your project is done, apply F_colorspace filter at the end<br>
(bottom) of the stack with these options:<br>
- range: 1<br>
- irange: 2<br>
Second, in File -> Render -> Video, place this line at the end of big<br>
textfield:<br>
color_range=mpeg<br>
<br>
Since you're already fighting color banding, the good thing is to<br>
32-bit colors in Settings -> Format -> Color model: RGB(A)-FLOAT.<br>
Note this could slow down your playback and rendering.<br>
"""<br>
<br>
By the way, if anyone is wondering "why is this guy so obsessed with<br>
such a rare issue" - well, I shoot blurry asphalt, usually misexposed:<br>
<a href="https://www.youtube.com/watch?v=B6QukURw_Og" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=B6QukURw_Og</a><br>
This was the good example where I was clever and minimized the damage.<br>
I have worse and don't want to look at them.<br>
<br>
By the way^2 - I just notice the cinelerra manual is the first result<br>
for googling "mpeg color range". Cool!<br>
<br>
> However, this is a different matter from what you were asking. You<br>
> could try using ffmpeg from the command line using the option:<br>
> -vf "scale=in_range=jpeg:out_range=mpeg" -pix_fmt yuv420p<br>
> and compare with the result obtained in CinGG to see if there are any<br>
> differences.<br>
> <br>
> Question: In CinGG, what format and preset do you use for the<br>
> rendering to export to YT?<br>
<br>
Nothing fancy really.<br>
<br>
File -> Render:<br>
File format: FFMPEG mp4<br>
Audio:<br>
bitrate 0,<br>
quality 5 (an overkill really, produces ~450 kbit/s AAC, but it's<br>
still noting compared to video)<br>
Video:<br>
bitrate 0,<br>
quality -1,<br>
pixels yuv420p,<br>
in a big field for options:<br>
crf=25 (for a 4K, must be lower for 1080p)<br>
preset=fast<br>
<br>
This provides a nice gently compressed video for long-time storing and<br>
uploading to YouTube.<br>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" target="_blank">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div>