Chris Martin
Forum Replies Created
-
If you are giving a file sequence such as dpx or tif (usually the case for vfx) the 23.98 / 24 flag does not matter really as long as they are set to 24 workspace on their end. If you’re sending a wrapped file like QT different story.
-
This sounds like a case of working with and rendering files that are not 709 themselves. So even though you are grading to a 709 environment there is nothing about your files that are 709, this using any 709 to XYZ transform is not going to work unless you first bake down your graded/rendered files to 709.
Example: If you were working with full range RGB DPX frames but colored out to YUV 709 (head range) monitor then rendered full range tif a 709 transform really would only apply to what your seeing on your 709 SDI output.
-
Peter,
The problem in Quicktime viewer. We run into this all the time when clients use it and are viewing different flavors of quicktimes.
It’s just not a stable way to view and compare. Bring them back in Resolve or in an NLE to judge them.
-
Definitely don’t use quicktime viewer to judge anything!
-
Even if you accept the limits of what can be passed in a LUT or CDL you’re dealing with a lot of numbers being written and read and a lot room for variance with LUT writing and reading. For CDL unless you have systems supporting Open Color io you are going to have variances as well.
-
If you use your nodes efficiently knowing you may do this you can add nodes and then take the key mix from 1.0 to .50 and mix the node in. Versions with totally different looks and node structures not as easily done.
-
Yes we usually work in reels for long form and tried doing an hour show recently all in one timeline and Resolve ran much slower.
If you work in reels and want to final a continuous quicktime or file sequence one thing we do is after rendering the reels we’ll create a session to compile the reels and then render out from there. This is also nice if you have been working with larger resolution source files but finishing in HD as the render will go fast.
-
Unchecking that would bypass any fcp repo being recreating if you had checked use resize info during the loading of xml.
Have you brought any of the files into a new session in Resolve without the use of xml? I’d eliminate the xml from the equation. If it’s still doing it it has to be a setting for bow the image is being fit into a timeline setting.
-
If you don’t have to worry about recreating a lot of image repos then I’d bag the xml and use and edl per layer. Enable using clip name during conform in project settings and you you bypass the problem.
-
Did you carry across image repositions with the xml? If so go into color menu and uncheck use xml sizing in timeline menu. That will confirm or eliminate xml as the issue.