Kdenlive/Manual/Full Luma: Difference between revisions
mNo edit summary |
(Marked this version for translation) |
||
(3 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
<translate> | <translate> | ||
== | ===== Full Luma ===== <!--T:13--> | ||
====== Advance Clip Property - Full Luma Range ====== <!--T:1--> | |||
<!--T:2--> | |||
A clip can have its full luma flag set from the [[Special:myLanguage/Kdenlive/Manual/Projects_and_Files/Clips#Advanced_Properties|Clip -> Advanced properties]] | A clip can have its full luma flag set from the [[Special:myLanguage/Kdenlive/Manual/Projects_and_Files/Clips#Advanced_Properties|Clip -> Advanced properties]] | ||
<!--T:3--> | |||
From [http://www.kdenlive.org/forum/what-does-full-luma-exactly-do#comment-18298 this] forum post by Yellow | From [http://www.kdenlive.org/forum/what-does-full-luma-exactly-do#comment-18298 this] forum post by Yellow | ||
<!--T:4--> | |||
:The full luma option refers to video sources with luma recorded outside of the typical 'broadcast', 'restricted' 16 - 235 8bit range. | :The full luma option refers to video sources with luma recorded outside of the typical 'broadcast', 'restricted' 16 - 235 8bit range. | ||
:This option fixes problems round tripping video files with luma outside of the 16 - 235 8bit range. By default when we import a video it is handled | <!--T:5--> | ||
:This option fixes problems round tripping video files with luma outside of the 16 - 235 8bit range. By default when we import a video it is handled and displayed based on the 16 - 235 range, levels below ie: 0 to 15 and those above 235 to 255 are compressed to 0 and 255, so shadows get overly dark and highlights saturated, in the preview within '''Kdenlive''' for camera sources that are full range. | |||
<!--T:6--> | |||
:Then when we render out, those levels remain in the final video, compressed shadows and saturated highlights, so there is a mismatch between the levels in the video we import compared to that exported. '''This only really matters for round tripping to an external application'''. | :Then when we render out, those levels remain in the final video, compressed shadows and saturated highlights, so there is a mismatch between the levels in the video we import compared to that exported. '''This only really matters for round tripping to an external application'''. | ||
<!--T:7--> | |||
:For any playback on DVD's, bluray and including the web like Vimeo or Youtube our video levels in the final rendered output should be in the 16 - 235 range, otherwise we see so called 'gamma shifts', 'washed out' or saturated playback depending on playback handling. | :For any playback on DVD's, bluray and including the web like Vimeo or Youtube our video levels in the final rendered output should be in the 16 - 235 range, otherwise we see so called 'gamma shifts', 'washed out' or saturated playback depending on playback handling. | ||
<!--T:8--> | |||
:However really we want to have control of the levels adjustment in '''Kdenlive''' i.e.: 0 - 255 into 16 - 235 so full luma option changes the handling of the files and preview / scopes are based on an alternative YCbCr to RGB calculation. | :However really we want to have control of the levels adjustment in '''Kdenlive''' i.e.: 0 - 255 into 16 - 235 so full luma option changes the handling of the files and preview / scopes are based on an alternative YCbCr to RGB calculation. | ||
<!--T:9--> | |||
:By setting the full luma on, which should only be done for camera sources known to be full range 0 - 255 or even 16 - 255 such as FS100, Nex5, HV20, HV30 and probably many more consumer cameras. Canon and Nikon DSLR's too but a little more complicated, we can export video with the levels as imported, BUT and it's a big but, that is without doing any RGB operations in '''Kdenlive''', so no effects, color correction etc. If any effects are added then the output will be restricted range again. | :By setting the full luma on, which should only be done for camera sources known to be full range 0 - 255 or even 16 - 255 such as FS100, Nex5, HV20, HV30 and probably many more consumer cameras. Canon and Nikon DSLR's too but a little more complicated, we can export video with the levels as imported, BUT and it's a big but, that is without doing any RGB operations in '''Kdenlive''', so no effects, color correction etc. If any effects are added then the output will be restricted range again. | ||
<!--T:10--> | |||
:For me I use full luma all the time, it allows roundtripping a video edit and maintaining levels for grading in an external application that offers 32bit float precision. When it's necessary to otherwise happy with '''Kdenlive's''' SOP/SAT and scopes. | :For me I use full luma all the time, it allows roundtripping a video edit and maintaining levels for grading in an external application that offers 32bit float precision. When it's necessary to otherwise happy with '''Kdenlive's''' SOP/SAT and scopes. | ||
<!--T:11--> | |||
{{Prevnext2 | {{Prevnext2 | ||
| prevpage=Special:MyLanguage/Kdenlive/Manual/Projects_and_Files/Clips | | prevpage=Special:MyLanguage/Kdenlive/Manual/Projects_and_Files/Clips | ||
Line 28: | Line 40: | ||
}} | }} | ||
<!--T:12--> | |||
[[Category:Kdenlive]] | [[Category:Kdenlive]] | ||
</translate> | </translate> |
Latest revision as of 13:53, 25 February 2013
Full Luma
Advance Clip Property - Full Luma Range
A clip can have its full luma flag set from the Clip -> Advanced properties
From this forum post by Yellow
- The full luma option refers to video sources with luma recorded outside of the typical 'broadcast', 'restricted' 16 - 235 8bit range.
- This option fixes problems round tripping video files with luma outside of the 16 - 235 8bit range. By default when we import a video it is handled and displayed based on the 16 - 235 range, levels below ie: 0 to 15 and those above 235 to 255 are compressed to 0 and 255, so shadows get overly dark and highlights saturated, in the preview within Kdenlive for camera sources that are full range.
- Then when we render out, those levels remain in the final video, compressed shadows and saturated highlights, so there is a mismatch between the levels in the video we import compared to that exported. This only really matters for round tripping to an external application.
- For any playback on DVD's, bluray and including the web like Vimeo or Youtube our video levels in the final rendered output should be in the 16 - 235 range, otherwise we see so called 'gamma shifts', 'washed out' or saturated playback depending on playback handling.
- However really we want to have control of the levels adjustment in Kdenlive i.e.: 0 - 255 into 16 - 235 so full luma option changes the handling of the files and preview / scopes are based on an alternative YCbCr to RGB calculation.
- By setting the full luma on, which should only be done for camera sources known to be full range 0 - 255 or even 16 - 255 such as FS100, Nex5, HV20, HV30 and probably many more consumer cameras. Canon and Nikon DSLR's too but a little more complicated, we can export video with the levels as imported, BUT and it's a big but, that is without doing any RGB operations in Kdenlive, so no effects, color correction etc. If any effects are added then the output will be restricted range again.
- For me I use full luma all the time, it allows roundtripping a video edit and maintaining levels for grading in an external application that offers 32bit float precision. When it's necessary to otherwise happy with Kdenlive's SOP/SAT and scopes.