Peter Chamberlain
Forum Replies Created
-
Hello all, the RED SDK offers adjustments to a number of the decoder metadata settings. The r3d’s are played from disk, decoded by the SDK, or Red Rocket, and then presented to the Resolve as RGB values per pixel. I understand that this is the same for all third party vendors. The decoding must be done prior to the main application, its how the SDK works and its why the settings don’t appear in the node graph.
Resolve offers RED default, project, camera or clip based metadata control of these adjustments and you can modify one or many parameters for one or many clips. This is performed in the red decode settings window which is found in the configuration, source screen, the Media Pool, and also the main color screen.
With 8.0, due for June release, these controls are also available on the DaVinci Resolve control surface so while they are adjusting the decode pre the Resolve node graph, they practically are accessible just like all the other grading parameters on the Resolve panels.
Peter
-
Hi all, when we release 8.0 in June we will have an updated config guide and a number of these questions will be clearer then.
OpenCL is GPU based, not cpu, and in the iMac and Macbook Pro configs we demonstrated at NAB we used the one on-board ATI GPU. If you are building a MacPro, you can continue to use the ATI cards BMD have previously identified for the UI GPU, but for image processing the Nvidia Quadro 4000 with CUDA is still the performance GPU for image processing.
The NR is only available on CUDA so its likely users will want at least one CUDA GPU for the image processing to get this amazing feature.
Peter -
Resolve only makes dpx on ingest.
Peter -
DaVinci Resolve 8.0 supports Open CL so you can now use the latest quad core i7 iMac and the latest MacBook Pro with Thunderbolt and our new UltraStudio 3D. There is no noise reduction available on the OpenCL and for real time playback use 720p.
For performance applications the Nvidia CUDA GPUs that you all use today are still suitable in the same MacPro systems you use today. No one will be required to change their hardware for this upgrade, however with the addition of full multi layer timelines there will be greater bandwidth demand on the disk storage systems and GPU count to play more tracks in real time. If your system was able to offer five nodes at HD with one track, adding a second track with two nodes for a transitions may impact playback for the duration of the transition. Just use the ‘render cache dissolve’ to make that real time.
At NAB we are using 2010 MacPros with two Quadro 4000 GPU’s and the Cubix expander and feedback from the show has been that performance is exceptional. We also have Red Rockets in the systems to play the Epic 5K material.
8.0 also supports multi layer AAF import and ALE export so Avid round trip has also improved in this release.
Peter -
It was wonderful to meet so many from the Resolve community today. Thank you for taking the time to visit BMD, SL220 @ NAB.
Just FYI, the Open CL is working well on the iMac and MacBook Pro up to HD resolution. At this time the real time noise reduction is only available on the Nvidia CUDA graphics cards and CUDA should still be considered for performance application where more you need more than the one GPU card limit that exists on Open CL.
We also demoed today, Cinema DNG RAW file support with our new BMD designed high quality debayer, Epic 5K, multiple layer AAF import from Avid and ALe export, and one of my favorites, Canon 5D conform via XML from FCP where every clip starts at :00 timecode, yet they all conform to the right spot on the timeline.
For those FCP users, after grading and XML export to FCP, you can import the sequence and amend the edit, as we know everyone needs to, and then in FCP export a new XML. Resolve will import the XML into the previous graded session and then automatically color trace all the previous shots, leaving just the changed shots to grade and send back to FCP, so constant edit changes are handled easily.
More news tomorrow.
Peter
-
DaVinci Resolve 8.0 is a no charge upgrade for existing customers. Enjoy.
-
Update: Nvidia have released a new Quadro 4000 driver for MacOSX 10.6.7
https://www.nvidia.com/object/quadro-macosx-256.01.00f03v7-driver.html
You are required however to remove the 4000 GPU before installing the update and the driver.
After the update and driver installation is complete, power down and install the 4000.
We tested the update here successfully.
The issue only affects Nvidia Quadro 4000.
Peter
-
Hi, experience from the numbers of colorists moving to Resolve indicates a fast learning curve. “The DaVinci Resolve UI is clean and uncluttered.” “The pictorial nature of the UI makes it very easy to see where you are on every clip and every node in a quick glance.” “Its like having version 10 of the application without the bloat.” These are not my words, but those who have made switch.
Give yourself a couple of client free days, then easy into the first job. I’m pretty sure that within a week you will feel comfortable, even if you have never used a DaVinci grader before.
As for the auto tracker, try making the window smaller and then in interactive mode remove the computer selected marks to leave just the ones you want.
Peter
-
On the Config screen, project settings, there is a check box you can use for interlace processing. It will influence your real time playback node count. If you are not resizing, changing the resolution, using defocus or sharpen you may not need this checkbox for your interlace material. If you have just a few shots that need resizing, consider rendering those to DPX first with the checkbox enabled then complete the project with it disabled, i.e. normal mode.
-
Charlie is correct, you can make a 2K proxy on Resolve and because our the optical quality resizing its suitable for grading and output. Use the proxy manager to make a 2K proxy; grade with the proxy button ‘on’ then when you wish to render turn the proxy off and preview full res.
While ProRes 4K may be only 100MB on disk, Resolve needs RGB for every pixel for every frame so internally you are trying to decode the 4K ProRes and process. Tough ask on the Mac with the current OS.
Are you starting with ProRes4K or r3d as this changes the situation too.
Ultimately, if its node limits you have, add another GPU. For ProRes material you can use two for image processing.
Peter