Hi Rohit and Margus, thanks for the interest
Firstly I should clear up something in my previous post, comparing a 2K playback on Resolve with a 4K playback on Scratch.
Scratch did indeed play the 4K (3996×2160) stereo at 24fps realtime. After I posted the first post I manage to run exactly the same test on Resolve with the 4K files.
The same files played at 10fps on Resolve, which is double the data throughput performance of the 2K playback (half as quick, not a quarter, as suggested, as Scratch).
In terms of Disk IO this was about 800MB/s on Resolve and 1.7GB/s on the Scratch.
I only need 400MB/s for the stereo 2K, so Resolve CAN pull enough data through quick enough for the 2K stereo playback, but something is throttling it.
Regarding whether it could be a GPU issue or not. It’s possible, I don’t know enough about DaVinci’s internal workings to say otherwise. But if the GPU was topping out with a stereo 1998×1080 stream then it should have topped out at around 5.5fps with the 3996×2160 files, not 10fps. However, if BMD say that’s the issue then I’ll put one in tomorrow. My feeling is the FX6000 is more than adequate for this throughput test. This playback is without any LUT’s, grade, resizing or image manipulation whatsoever.
In regards to the SDI setup. This was to be a test to see if Resolve worked well on the Globalstor. At the moment it is our Scratch production machine and currently uses the SDI daughter board of the 6000 for the SDI output which Resolve obviously can’t use. If Resolve is proven on the machine then I’ll go buy the Decklink 3D.
So I am monitoring just on the GUI monitor and going by the fps indicator at the top left of frame. Stereo is toggled on, (I am assuming this is reading both frames as the playback speed slows down as opposed to mono where it plays realtime), but I have selected ‘none’ on the stereo viewer setup, so as not to tax any gpu in processing the gui.
If the feeling is that this is the issue then I’ll see if I can put one of my old decklinks (not 3D) and an FX4000 in it tomorrow and see what happens. I’ll also check the Bilinear setting and video optimisation setting and let you know how it goes.
My personal belief is that it’s something in the Disk I/O calls or the size of the chunks of the frames it reads from the disk. There was an issue (now fixed) with an older version of Scratch that if a file’s size, say DPX was not perfectly aligned in 8KB blocks then Scratch would read each file twice necessitating double the IO bandwidth. Maybe there’s something like that in Resolve.
(feature request) It would be nice if Resolve had a popup box with a complete system stats readout somewhere to monitor the cpu/memory/IO/GPU performance of the machine.
Thanks again and sorry for my ramblings
Toby
Colourist | Editor | Post-Production Consultant — 25 years at the post-production coalface, and still loving it.