Peter Chamberlain
Forum Replies Created
-
The upgrade from 7.1 to 8.0 will take just a couple of minutes so don’t wait, make some money now with your new suite.
-
Hi, it sounds like you have all your r3d clips in the medial pool at the same time, which could be hundreds of clips, and basically you are running out of memory as Resolve needs to keep a referene to everything in the media pool, even if it’s not in the active session. Remember everything in the medial pool becomes part of the master timeline.
Try putting in the material you need for the session you are grading, normally it’s 20-30 min reels. Its also good practice to use half res premuim if you have a red rocket, and hd timeline during the grade, and switch to the render settings you need for the final render of each reel. Resolve will automatically link the color grades, window positions and sizes etc to the new resolution for the render.
Peter -
Are you using 1/2 res premium for the r3d decode?
Do you see the same issue with another 2K or HD source image rendered to Pal? -
Two items to discuss here to answer this great question.
A: This depends how you are decoding the r3d. In Resolve you can set the decode at premium or good debayer, and at different resolutions, 1/2, 1/4 etc. The decoded RGB pixel data is delivered to the Resolve resizing engine and so if your timeline is set to HD, it resizes to HD. If set to SD it resizes to SD. Resolve will use the decoded resolution as you set it for the input to the resize engine. And the Resolve resize engine is the best realtime processor you will find.
B: If you set a creative resize on a clip, to grow the image 20% for example, Resolve calculates the resultant image based on the source available to the resizing engine, not the timeline size. e.g. if you have a SD timeline and HD material, and a 20% increase in size, Resolve resizes the HD material to the correct size. It does not convert to SD, then increase by 20%.
In this manner, the highest quality resize is performed but you need to set a sufficient decode resolution to match your needs. One way to do this is set the r3d project settings to full res premium for the render.
Peter -
Hi all, its all about balance and the work you do. You can put in three GPU’s for fast image processing, but if you have one disk, that’s going to be the limitation. Conversely, one GPU may not give you 10 nodes of 2K but the fibre channel Aurora from Rorke Data will definately will give you the 2K bandwidth with plenty to spare. If you have r3d, use a Red Rocket for full debayer at 2K in real time. Stereo r3d requires two Rockets. If you have a lot of QT files, CPU decoding and encoding speed will benefit from faster and more cores.
For those looking at tuning for high performance, consider one drive array as the source and another as the render destination. In this config, your drive controller can stick to one task. We know of Resolve colorists getting better than 100fps for SD dailies renders and at BMD post we render 2K faster than real time so clearly it’s not an application limitation. It’s just about configuring the system to meet your budget and operational needs.
Peter -
Hi, the basic concept is that the x16 slot that the expander uses shares the bandwidth to the four new slots…. if you assume that a GPU or other cards in those new slots require the full slot bandwidth for 100% of the cards duty cycle then you are correct that this ‘voodoo’ wont work. Fortunately the GPU and other cards need most of the frame duration to do their own internal magic and so the slot use by each card is manageable. That’s not to say there are no limitations, just too many variables to be able to check every single one. Thus the config guide describes known working combinations.
Peter -
Linux still offers greater GPU options (up to 16) and also bigger and better I/O to disk of the large image files. Steroscopic 3D at 2K is real time and 4K on Linux in realtime is a breeze, as is RGB at 10 bit for stereoscopic monitoring, data waveforms on a separate server etc. The Linux also handles more RAM and yes uses IB for expansion, can connect to CXFS file systems as well as StorNext, etc etc. These are balanced by QT and ProRes on Mac, and easy plug and play for external drives. The UI is the same and feature set closer than you can imagine.
The differences are driven by external factors, mainly OS and hardware, as BMD make the application as ‘the same’ as we can but there is no doubt, there is still plenty of reasons for the Linux systems.
Peter
-
If you use SD resolution files performance will be ok for learning the app but as you surmised, you do need a CUDA GPU for the app to run.
Peter -
Our expectation is the slowest GPU will pace the others so keeping them the same is best, similar in performance likely to also be ok.
Peter -
Hi, if you have 7.0.3 use the middle “Autosave” option as this mimics pushing the save command and does an incremental save. The option to backup the project will take longer as Resolve makes a full project backup and them needs to complete some file housecleaning. Some facilities run Autosave during the day and each night do one backup.
Peter