Carsten Sellberg wrote:But there is still something I don't understand. Is the hardware decoding/encoding done in the nVideas Graphics Card or in the Intel CPU?
I'll try and give you a short answer.
The CPU decodes and encodes your video clips. The GPU works the grades, timeline effects, et al. Resolve emphasizes the GPU for obvious reasons.
Given Resolve is scalable, your own needs dictate a lot. An older CPU can handle proxies ("optimized media") efficiently, while your resolution needs are obviously a factor with the GPU.
You don't need the latest everything to run Resolve. Speaking of which, you'll want to read
this test.
Carsten Sellberg wrote:And is the codecs and number of bits the same for hardware decoding/encoding in Resolve Studio for Windows, Linux or Hackintosh?
Number of bits is the same on all ports, I wager.
Codecs the same, nope. Here's a
list of supported codecs for 12.5. BMD have since implemented on HEVC (h265) support in v14. Also, Nvidia GPUs can now decode h264/hevc on all platforms (Mac Lite, Studio for Win/Linux).
The Linux stand-alone is the pickiest, but even that is manageable. Two ports of Resolve can co-exist on the same workstation and share databases / projects / proxies. This helps with MIDI support (only BMD panels on Linux) and import/export, but also stipulates dualboot. Up to you. Our workflow uses certain features that are out of bounds for the Linux stand-alone, which is why we utilize the Mac port on the side.
Hackintosh is a good all-around solution. You get most of what Resolve has to offer in terms of codecs and other things. As said, your CPU/GPU come largely down to what sort of projects you intend on doing.
Resolve is scalable and flexible. Determine what you need from the video resolution, codecs and your user experience and go with that. You have a lot of options to build the affordable workstation for the job you need.
Linux Mint 19.3 | DaVinci Resolve Studio 17.1 | 2700x 32gb Radeon VII | macOS Mojave