- Dec 15, 2015
- MSI Z270 M7
- GTX 1070
- Mobile Phone
I agree with you, since I disabled my iGPU (3770k) and use imac pro 1.1 SMBIOS, everything is way faster. On top of that, preview in finder works, I do not need NoVPAJpeg anymoreFWIW I have never gotten good FCPX performance on my i7-3770K/R9 280X system when the onboard Intel HD 4000 GPU was enabled and injected. I've followed all the guides and advice and different Clover boxes ticked and every time I enable Intel graphics alongside my AMD 280X, FCPX exports slow to a crawl. I can see in Activity Monitor that the Intel GPU is handling the FCPX export, but it takes about 3-4 times as long as if I don't disable the Intel graphics and just run the system with only the AMD GPU. Then all FCPX exports pin the 280X in Activity Monitor and finish very quickly.
Just another data point for the discussion. I don't think this is all so well understood as the mods believe. If it was, enabling my HD 4000 would speed up my FCPX exports instead of slow it to a snail's pace, even though the Intel GPU was running full steam. I am certainly open to suggestions here but for now I'm leaving Intel graphics off and letting my 280X run as the sole GPU. Mojave seems to understand this and everything works better this way, on my machine at least.
A few more observations: it seems to be a thing now to use apps like Videoproc to assess whether GPU hardware encoding/decoding is in play or not, but it’s my experience that every app is different, and some make full use of GPU hardware encoding/decoding even if, say, Videoproc shows it’s not enabled. What Videopro tells you is whether or not GPU hardware encoding/decoding is enabled for Videoproc. Not every app. Do yourself a favor and fire up Activity Monitor and look at GPU History as you encode/decode video with your various apps. Even if Videoproc indicates no hardware acceleration is possible, you’ll see your discrete GPU is handling the full processing task while your CPU idles.
It’s also important to understand that Intel Quick Sync was designed for real-time video telephony, not high quality video encoding. What’s impressive for Skype is not good enough for a Final Cut master. I see so much attention here about IQS and how enabling it is important, but nobody talks about its visual quality vs. standard encoding. Speed is not the only metric, especially if you’re doing pro work. Clients tend not to be impressed by quick turnarounds if the video looks just okay and they paid for excellent.
I would be delighted if my onboard Intel graphics delivered faster encodes with higher quality. It doesn’t work that way. Intel Quick Sync is treated here as some kind of free lunch but it does have a cost, and it is video quality.