View Single Post
Old 10-04-2018, 06:29 PM   #87
Senior Member
Join Date: Oct 2008
Location: Bucharest, Romania
Posts: 507

Peter, OK. Here are my thoughts and experiences.

I built a new Win7 Pro computer just over 3 years ago, with an i7-5820K CPU and 32GB RAM. The Graphics card is an NVIDIA NVS 510 with just 2GB. At the time it was quite expensive, so I expect to still get another year or so out of this machine. It has been perfect for editing 1920x1080 HD in EDIUS v7. In 2016 I upgraded to Workgroup v8, and continued editing 1920x1080 HD.

Now I am about to upgrade to 38402160 UHD, but as I said, I will continue with my existing computer for around 18 months. It is tempting to upgrade to a faster CPU but I am going to wait.

The next big job I do will contain a lot of material filmed on a Mavic 2 Pro. So I have been doing some tests. I am setting up the drone to film HEVC H.265 10-bit MP4 38402160 UHD @ 25p DLog-M.

So how does 38402160 UHD in H.265 work on my EDIUS PC running Workgroup v8.53b3262 ???

Well, my C-Drive is a Samsung SSD 850 PRO. I have copied the original Mavic 2 Pro media onto a striped pair of conventional hard drives.

I have setup an EDIUS v8 project as follows...
Frame Size: 38402160
Frame Rate: 25p
Quantization Bit Rate: 10Bit

After loading the media onto the timeline it plays fine. But try to scrub, and the situation is hopeless. Reduce the preview quality to even 1/4, and it is impossible to scrub properly. Any editing will be utterly frustrating. And this is before I apply any PCC using the DJI Dlog-M to Rec709 LUT. [BTW in the PCC window, I and others feel the Source and Destination/LUT fields are the wrong way around. Any thoughts on that?].

If I change the project settings to 1920x1080 the results are very similar, even at 1/4 preview quality.

So what to do?

David Harry has demonstrated the clear advantage of rendering 4K material to HQX. And of course it works fine. In fact it is a terrific format and plays faultlessly - perfect for editing. But for me, it's only useful for medium to small jobs, since I generally work with long-form documentaries of between 40 to 60 minutes, which are edited from as much as 24hrs of original camera footage filmed over 6 months.

Here's the problem. One of my typical files, 44secs of UHD, is 544MB. In actual fact H.265 files are 50% smaller that H.264. So if I acquire 24hrs of this resolution I will need storage for just over 1TB of video. Which is easily manageable.

If I bump this up to Superfine HQX, what happens? Well the 44secs of UHD, which was 544MB, now becomes 6605MB. That is 12 times larger. In which case my 24hrs of material in HQX will require an extra 12TB.

However, if I keep the project at 38402160 and create "large" proxies (which are 1920x1080), my original 44sec file reduces from 544MB to just 64MB - that is 9 times smaller. And the 24hrs of proxies will only require an extra 100GB.

Having done the test, I can honestly say the proxies look great, and are ideal for editing. They run beautifully, just as 1920x1080 has always done on my computer. And when I add PCC with the DJI Dlog-M to Rec709 LUT the images come alive and there is no degradation in the operations on the timeline - scrubbing to and fro is as smooth as you like.

What more can I say?
EDIUS WG 9.50.5351 Tower > Win10 Pro 64-bit on 512GB Samsung 850 Pro SSD, Nanoxia Deep Silence Case, Asus X99-S Mobo, Intel i7-5820K Haswell-E @ 3.30GHz O/C to 4GHz, 32GB Crucial DDR4 @ 2133MHz, NVIDIA GeForce 980 Ti 6GB + dual 1920x1080 monitors, BM Intensity Pro 4K + 3840x2160 monitor, LG Blu-Ray writer, Storage: 16TB WD RED RAID0. EDIUS WG 9.50.5351 Field Laptop > Acer P645-M, 14" 1920x1080, 256GB SSD, Win7 Pro 64-bit, Intel dual-core i7-4500U Haswell @ 1.8GHz, 8GB DDR3.

Last edited by spurfilm; 10-04-2018 at 09:27 PM. Reason: typo
spurfilm is offline   Reply With Quote