Of course that's the best outcome. But after discuss from other Hackintosh users, I only have less than 50% confidence that I can build a 100% trouble free Hackintosh. I don't expect to face any serious problem (if I pick the parts correctly). However, I do expect some minor annoying issues from Handoff, Message, Sound driver...
I had some annoyances with iMessage back in the day—as I said before that was really the only thing I really spent time on. I ended up using the hardware ID of my oldest MBP when they switched up how the service ran. From what I've heard, it's gone back to being easy again. My stuff works so I don't want to mess with it, but I have considered looking into it and switching to an ID not attached to an actual system.
My studio mate also runs a hackintosh and our render farm is comprised of his older hacks, so if something happens we can work things out together. Our systems are similar, but present different issues sometimes. Right now I'm on the latest and greatest OS and he's back a version.
I haven't dealt with handoff much. I don't really use it. I've seen it work before on this machine but it might be spotty, I don't know. It's not really work-related for me so I can't totally attest to that. I can message and take calls out of this machine. Sound is simple. I originally had a setup through Chameleon and Multibeast. Now that I'm on Clover, I baked in a lot of the changes I had to add with upgrades (like Trim support). But I always had to use Multibeast to get audio back up when I needed the other ports (like my front audio port that we soldered to the original). So I ended up going through the Multibeast app package, and grabbed out audio and ethernet installers so I didn't have to bother remembering which ones worked. Usually ethernet is completely fine. The only one that get's overwritten so much is audio, maybe the FakePCIID kexts. So I usually just use the machine and if something is amiss, I install those over. Honestly the PCIID kexts I usually only have to install for major versions and even then I think it's only out of precautions. You can put them right into your Clover setup too I believe. I just haven't. And installing them is a matter of opening up Kext Utility and dragging them onto it and waiting a minute. It's all really no big deal. It sounds way worse than it is.
Honestly, if you want to be super solid, get a USB audio solution. They tend to work right out of the box. I've been doing some tutorials for AE and I use a blue Nessie, and it works for my headphones too (because I used the original port on my hack for a clean appearance rather than swapping it there's a phase issue with the sensing on that port IIRC so I don't use it much because of how you have to have the audio set). I haven't brought my 5.1 system out since switching to this setup, but I might just get a USB breakout for that.
When I upgraded to Sierra, I couldn't get the install to work on my older Clover version, so I upgraded that. It then worked fine. I had to install ethernet and audio (double clicking an installer package) when it booted and I dragged the kexts onto Kext Utility for good measure. I had to reinstall the nVidia web drivers and got a black screen issue on restart. On a whim, I booted up off of my backup drive's clover, back into the new drive's Sierra, so I could mess with configuration of Clover (basically ticking a checkbox that would've likely solved the problem) but I noticed there was a newer OS update, so I figured I might as well upgrade all the way if I might have to roll back. When it rebooted, ethernet and everything still worked (usually point upgrades are super easy) there was a new nVidia web driver so I installed, booted back off of the main drive and everything has been completely fine since. It sounds like a long time and a lot of work when you read it, but including the OS install and updating Clover, it probably took me an hour. Maybe even less. And that's probably the second hardest update I've had. I didn't even solicit help from my studio mate.
So while YMMV, it's really not that difficult. In the past, granted it was more than a decade ago, I've had to tinker more with supported Windows hardware.
No matter what road you take, good luck to you.
[doublepost=1477668115][/doublepost]
I completely understand most of your points, and they do make sense. Cutting/editing alone does not require much. But, at least it seems like, most people who have the Mac Pro are closer to one-man bands. Or they at least want the ability to learn new things. Because you're right in what it takes to edit, and if you bought a Mac Pro just for cutting footage, you wasted your money. There are so many cheaper, simpler options for editing video. But in modern video, it's becoming almost a requirement to understand at least basic grading. The 2015 MBP falls short horribly in grading and 3D rendering (even 1080p), as does the iMac with its incredibly poor mobile graphics.
If people were just editing on a Mac Pro, you'd be right 100%. There's no need for any new ones. Even a 2008 will edit perfectly fine. But if you grade and do any sort of 3D project, the need is becoming more substantiated to upgrade from an old machine and have support for the latest cards.
Totally! I just feel like I've seen a lot of Editors with a capital E complaining about it. Editors that were fine with FCP 7 with all of its bugs. If you could deal with and love that old pile, you can deal with a few seconds longer transcodes, haha. Maybe I'm wrong about that. Maybe they were more one-man-bands.
But yes, my MBP doesn't like Davinci, although more recent versions seemed ok but I've mostly only used it on this hackintosh recently. But I can definitely attest to that. I've done C4D on it, but it's not super enjoyable. AE is ok for simple stuff. It's odd what it has trouble with, but that's also the nature of AE. Things that seem simple take forever, and things that are complex are sometimes fast.
Anyway, yes, my comment was to specifically people that are doing 90% of their work in an NLE.