Gargamel314
I do think the i9 is overkill for my purposes, it would be nice, but beyond my needs.
This assessment is an accurate one. My 8700K is overclocked to 29% and it has only ever pegged when being benchmarked, and the reality is that much of that extra umph is wasted. Almost all of its life has been below 50% (I actually cannot recall it ever breaking 50% yet other than on benchmarks and video rendering, TBH).
The other things to consider are these:
- RAM - 8GB is the bare minimum, 32GB has been overkill for me. 16GB is a nice medium (again, I am usually running less than 50%) and you can add more later if needed (if you get 2 8GB sticks initially, then you would still be able to use them if you get 2 more to save on upgrade cost).
- Motherboard - I have become a fan of ASUS, but even for these CPUs, there are many to choose from. If you research, much of the differences are splitting hairs (and some folks have done nice reviews of differences). The easiest way to sort them is by the features you want with the board (ASUS has a nice search feature here, start on the left edge filters if you want to look at them).
- GPU - you will definitely want a dedicatated GPU if working with video to remove some of the strain off the CPU. Again, you can get into hairsplitting here, so performance/price point is a good way to decide on all three of these items (and even the CPU).
- If not hard-pressed for a new machine NOW, CyberPowerPC is a good resource to monitor and sign up for emails from. They run specials on components, so you can get upgrades cheaply. When I got this machine I Goolged for a coupon that actually took at checkout (10% off). They also have a massive warehouse, so I escaped the GPU price-spike which was lucky, but I am not sure what the market looks like now.
Lastly, this is rarely mentioned but important, is workflow. For those of us who grew up on limited-resource machines, we have learned the art of judicious resource management. That translates well into this day-in-age when developers assume users have excess resources available and get sloppy with developing. I think that many issues people see is the "fear of commitment," where they will let numerous VSTs run each and every time the transport does "just because." Something simple like noise removal I will always render out; it is silly to assume I might want that noise back. Rendering/baking just adds another wav file to the audio folder, and with good naming conventions (projects, tracks, and clips) it is easy to find things even years into the future. I just wanted to mention this since even with a high-end machine, you can get it to choke by being a "sloppy user."