birdfeather wrote:Jim Simon wrote:Can you share a clip for testing?
Sure. See 17 sec singing cuckoo here:
https://we.tl/t-zTxuSZX9TO
That clip is 5728 x 3024, 10-bit, 4:2:0, 59.94 fps, 290 megabit/sec, HEVC, profile = 6.1@High.
I tried it using Resolve Studio and FCP on four different Macs, all top spec configurations.
Summary: FCP 10.5.4 and Resolve 17.3.1 were unusably slow on the 2017 iMac with i7-7700K ("Kaby Lake") running Catalina 10.5.7. VLC 3.0.7.1 would play it at 1x but no faster. Quicktime Player would play it at 2x.
On the 2019 MacBook Pro with i9-9900KH ("Coffee Lake"), running Monterey 12.5.1. FCP 10.6.4 and Resolve 18.0.1 Studio were improved but still somewhat laggy, esp if using JKL commands. It would play at 2x speed in VLC and Quicktime Player.
On the M1 Max MacBook Pro 16 it was smooth and likewise the M1 Ultra Mac Studio. Both of those were on Monterey 12.5.1, FCP 10.6.4 and Resolve Studio 18.0.1.
The issue with VLC performance is really irrelevant since it's very unlikely the NLE will be changed in a timeframe useful to your task at hand.
Your i7-9700 CPU is "Coffee Lake" or 8th-generation. I don't think it has hardware decoding for your codec. In theory the RTX-2070 does for 10-bit 4:2:0 HEVC but I don't know if it supports that HEVC profile, resolution and frame rate. Hardware decoders are very narrow and finicky about what they support. E.g, they may support 10-bit 4:2:0 but not 4:2:2 or they might support 10-bit 4:2:0 for DCI 4k and UHD 4k at 23.98 but not at 59.94, or they might support that but not odd frame sizes like 5728 x 3024. What they support is so poorly documented that Puget Systems had to run their own tests to determine this:
https://www.pugetsystems.com/labs/artic ... udio-2122/