9/10/2023 0 Comments Lut range for lutcalc![]() ![]() Feeding some F55 XAVC footage in, plus some 12-bit C300mkII RGB footage, I found that it doesn't seem to be keen on disabling the 'auto' range (as was Sony's recommended workflow). Looking at it now, I see that Resolve seems to be rather stricter with the 'auto' range setting than in the past (and ditched the word 'data'). Personally I'm more of a CC person than a Resolve one, so I haven't been playing around with 12.5 as much as I probably should have. As such, LUT Range settings for Resolve are dependent upon what 'auto' decides unless you manually set clip ranges in Resolve (Sony has a workflow paper which explicitly recommends setting Sony log clips to 'data' in Resolve the Sony looks included in Resolve under 3D LUTs expect that). Consequently, the 1023 at the top may refer to 10-bit 1023 in the recording, or 100% IRE (10-bit 940). Depending upon setup 0 can mean 10-bit 0 or 0% IRE (i.e. The 0-1023 scale on the side of the Resolve waveform is just a guide and can actually be misleading if thought of as 10-bit recording values. Resolve has always been a bit of a headache to me. You can probably leave this post at that, but diving into the deep end. The input and output ranges should also match the recording, for the same reason. That's why the preview window (and vectorscope) show an effect, but trying to generate a LUT with 'Gamut Limiter' causes a hissy fit.Īlready fixed in my computer, I'll have that in an update as soon as I can.Īs Nick says, for a straight colour space conversion, the gamma settings need to match each other and the original recording, for the correct linearisation before conversion. It's a variable name typo in the output code which doesn't get used for the preview. Thanks for spotting that! No idea how I managed to include this bug without spotting it. This is just to point out that the new option doesn't appear to be working for me.Ībout the 'Gamut limter' bug. Maybe I should open a different issue for the difference in color space conversion. ![]() Since you introduced the Gamut Limiter for these purposes in 2.90 (I'm running the Chrome App 2.91 on Windows), I wanted to give it a go.Īs soon as I set the checkbox though, clicking "Generate LUT" doesn't open the popup to save the file anymore. trying to convert S-Gamut3.cine to Rec709, especially comparing it to results that Davinci Resolve would produce, I get clipped colors (especially in orange tones). I've been trying to use LutCalc for the purpose of just converting gamuts without touching the gamma at all (I use a Sony a6300 and sometimes I just shoot in Cine4 which isn't currently supported in LUTCalc as a Rec Gamma).įor these purposes, I simply set the Rec Gamma to the same as the Out Gamma (which in my understanding shouldn't touch the luminance or adjust the gamma in any way) as a workaround. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |