Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Please give us display LUTS!

Rob Ruffo

Well-known member
Joined
Dec 28, 2009
Messages
2,493
Reaction score
0
Points
0
Location
Montreal
Many here use Lightspace to generate display 3D LUTS (which only affect display, not rendered output) for use in DaVinci, for proper calibrated output to external monitors - would be great if these worked in Premiere and After Effects too!
 
LUT buddy only creates LUTs based on grades, it does not only affect external display with a LUT without touching the actual footage or how it is rendered, which is what you would want when calibrating a monitor based a on 3D lut transform created in a software like Lightspace. I don't want to grade my footage with this, I just want to SEE my footage properly on my monitor.

Thanks for the effort though. LutBuddy nonetheless looks like an interesting product for other things.
 
SUre, but then the video output is using 10 bit (or 8 bit, not sure what Premiere outputs to secondary monitor). Internally Premiere is 16 bit, Davinci 32 bit - I'd much rather apply the transforms of my monitor calibration LUT at 16 bit or 32 bit to avoid banding and other issues.
 
SUre, but then the video output is using 10 bit (or 8 bit, not sure what Premiere outputs to secondary monitor). Internally Premiere is 16 bit, Davinci 32 bit - I'd much rather apply the transforms of my monitor calibration LUT at 16 bit or 32 bit to avoid banding and other issues.


3D LUTs generally specify the size of the cube, which only affect the precision of color transforms. Also, internal processing precision usually have no bearing on the output color depth. That is why, for example, Resolve can display 8 and 10 bit images, despite 32 bit internal processing. I'm pretty sure, Resolve uses same 1D display LUTs, as the converters I had mentioned earlier. I'm pretty sure, Resolve applies display LUTs at the very end as well, so the process pretty much identical. May be Peter or Rohit can chime in on this subject. Converters, that I had mentioned are capable of displaying 10 bit images, while using 1D display LUTs, so there is no need to worry about "banding and other issues."
 
3D LUTs generally specify the size of the cube, which only affect the precision of color transforms. Also, internal processing precision usually have no bearing on the output color depth. That is why, for example, Resolve can display 8 and 10 bit images, despite 32 bit internal processing. I'm pretty sure, Resolve uses same 1D display LUTs, as the converters I had mentioned earlier. I'm pretty sure, Resolve applies display LUTs at the very end as well, so the process pretty much identical. May be Peter or Rohit can chime in on this subject. Converters, that I had mentioned are capable of displaying 10 bit images, while using 1D display LUTs, so there is no need to worry about "banding and other issues."

Display LUTs in Resolve work like grades, so they stay in 32 bit space, at least, that's what BM tech support told me. You can use 3D Luts for this, or 1D. Any LUT is like a grade in another sense: if aggressive enough in its curve slope at any point it will cause banding if bitspace of source is too low, just like a sharp slope in a grade. Monitoring and grading are two different things - the only reason monitoring can be 8 bit and look fine is that you are not grading the final signal.
 
Back
Top