Peter Chamberlain
Forum Replies Created
-
As mentioned on the Basics Forum – Please download and try the 8.2.1 beta 3 as this is needed for users of ATI and Mac OS X 10.7.4
Peter -
Please download and try the 8.2.1 beta 3 as this is needed for users of ATI and Mac OS X 10.7.4
Peter -
Hi, how is the performance with the scopes turned off.
Peter -
Hi Chris. Assumption 1 is incorrect.
Resolve uses CPU for codec transcoding and GPU for all image processing. So files from disk are decoded, if required, passed to the GPU for processing. If they are RAW they are debayered in GPU. The exception to this rule is if you have a Red Rocket as the decompression and debayer is made in the Rocket, if not Rocket the r3d files are decompressed and debayered in CPU as thats what the RED SDK requires. In the render process the graded images are then passed from GPU’s to CPU to package into the codec of your choice, assuming you compress, and then to disk.
So to speed your renders, you need to optimize a number of processes, or at least find the speed bump. It could be the disk speed, raid controller, number of CPU cores for decoding, decompressing, debayer (if r3d). Then the number of nodes, NR, Blur, and GPUs used to process the images. The resolution, image resizing etc, all uses GPU resources. Then back to the CPUs for compressing, the Raid controllers ability to switch from read to write dynamically and then disk speed again.
My guess based on your details above, by setting the Red Rocket for a Full Res Premium decode of the r3d, the RED Rocket is making a 4K image, which then your single Q4000 GPU must resize to HD for the timeline before it applies the corrections. Try a 1/2 res setting on the Rocket and see what difference that makes as this will give more GPU power to be used for the grades instead of resizing.
And yes, 100+ fps render is very possible with a multiple Rocket, GPU system on a fast disk array.
Peter
-
Sorry, which model Mac?
Does it work ok for you with Quicktime or ProRes files?
Peter -
Hi Rob, please tell us what is your system config?
Does the Gemini recorder generate an XML in FCP 7 XML v5 or FCPX XML format?
Please provide details of the files you have tested. Were the Arri from from the BMD support page one of the Quicktimes or do you have .ari from somewhere else? Please specify.Peter
-
The monitor displays RGB. Any 422 source is converted to RGB by Resolve before image processing. At the monitoring stage, you can send 422 single link from Resolve to your monitor, which will then matrix it to RGB, or you can send dual link 444 from Resolve to your monitor which will display the RGB.
So, every source ultimately becomes RGB before the monitor can display it. If you have the ability to use dual link RGB from Resolve, I would use that.
I have not included discussion about full (data) vs video levels here as most users will be in legal video range in their monitoring.
Peter -
Usually this means the still is missing. The thumbnail is saved in the project for reference but you may have changed or deleted the still folder as Resolve can’t locate it where it was stored. If you grab a new still and that displays correctly its leaning toward the black ones being missing.
-
Unlike DPX, EXR files are not designed for efficient disk I/O. There were designed for VFX images where disk speed of a few frames per second was considerably faster than the VFX render speeds. We continue to find ways around the file format limitations to improve I/O for EXR but in the meantime, depending on your workflow, consider the 16 bit floating point dpx files Resolve reads and writes.
Peter -
If you stay with system configurations specified in the DaVinci Resolve config guides you know they will work.
Peter