Chris Martin
Forum Replies Created
-
Resolve reads image repos from Premiere just fine. More than likely your issue is that your Resolve and Premiere project settings regarding scaling source files into sequence timeline resolutions are not consistent. Very important that you aspect ratios between both systems stay consistent.
Since you are working from R3D files in Premiere I would make sure your sequence setting resolution is set to what you will have in Resolve. Premiere also is limited to scaling to fit option whereas Resolve can scale/fit as well as scale/crop. Make sure you have scale to sequence frame size selected in Premiere and then scale/fit for Resolve.
Do these things right and repos come across fine with an XML.
-
So is it safe to say that currently Titan Black and 780ti cards cannot be used in Resolve until nVidia update drivers?
-
I usually just bring into the media pool the select media which makes it easy to use copy manager to copy media as a backup if needed. For the most part I just backup the project and use edls to retrieve from production drives if the need arises.
-
Until you can do the most basic NLE navigations like use the keyboard to enter timecode destinations on the timeline I’m not going to consider Resolve a viable option.
Of course if you buy the $30k panel you can enter tomecode!
There’s a bunch of other stuff too by the way but it stsrts with timeline navigation.
-
Titan cards can only run on macs with cubix FYI.
-
Andrew, where you place the LUT in the node tree is determining at what point you are making the jump from SLog2/SGamut to 709. By putting the LUT on the last node this means all grading upstream from here is based on looking at SLog2/SGamut. For example, using the contrast/pivot anf offset parameters work very well in the Log space. They may not be the right tools if you are working downstream from your LUT. The LUT also is using a specific color matrix as well, so using curve based secondary work is very different after the LUT than before.
-
Time remapping from premiere’s effects pallette is not read by resolve in xml. I’ve only had luck when speed change is done from within the timine (right click on clip to acess).
Baked DPX a great way to go esp since Premiere can read the R3D and you can scale large raster down to say HD. Agree about redlog gamma. Perfectly fine way to go. Prores 4444 would be acceptable if drive playback a concern.
-
V10 is still in beta so maybe this is not worked out yet. There’s been previous posts regarding similar issues in timeline.
Always best not to”upgrade” from an approved tested version to a beta…
-
Is your file identified with a “.xml” at the end?
-
Hopefully a bug and not a featurechange. That would a big bummer step back