Stig Olsen
Forum Replies Created
-
What you need to understand about Avid import is this:
– If you check RGB when importing, you tell Avid that you are importing a RGB file. It then remap the RGB file to 709 (16-235) that is what Avid prefers.
Some think that it works the opposite way – that Avid will import the file and remap to or keep it RGB, but that is wrong.– If you check 709/601 you tell Avid that the file is 709 and it will NOT remap. It will eat it as it is (if it is 709)
Stig
-
If you finish in a NLE you can monitor normal range in Davinci, but output full range. When you import the files into your NLE you choose RGB when importing the clips and it will automatically remap the full range signal to normal range. No need for a LUT.
Since the NLE is working internally with levels between 16-235 you need to export with RGB checked to see what you see on your computer screen in Davinci.
If you finish in Smoke or Flame you can still monitor normal range, and export full Range in Davinci. Smoke and Flame also work full range internally and you can the same way set the output monitoring to normal range.
Stig
-
William, what is your finishing tool?
-
Thank you guys. I will try that. Packshot is the “product shot”, often the last seconds of a commercial.
-
Yes.
-
Ok thank you. I will check that out!
-
Ok. I thought the probes only work for calibrating the monitors and computer screens. In this case Im using the same monitor and computer screens on both Macs, linked with Cubix. Stig
-
OS is not adjusted, i didnt think that it was possible.
Full range is selected in Resolve and “preserve RGB” is also selected in AE.
It is the exact same DPX. On the Mac with AE I have also tried the DPX in other programs and it also looks exactly as dark as in AE.Could it be the graphic cards?
Stig
-
I mean same computer screens, but not the same machine – as they are linked with a cubix box that let me switch between those two.
Both are Mac and the DPX is the same.If it is not the color management system in AE, is it possible that it could be a different contrast in OS?
Stig
-
It did work by doing this:
– Create a corrector node after the LUT to have a clean key
– Create a parallel node, but change the input to a node prior to the LUT
– Feed the key into the parallel node
– Invert the key or add an outside node to adjust.This way it will give a clean key (made from after the LUT) and all the corrections will affect the data prior to the LUT but feed it back later in the chain.
Stig