How to build your own iMac Pro [Successful Build/Extended Guide]

[RuleBreaker01]

If you can, I'd love for you to try the following:

7). Once it is in the queue (right side of Davinci Resolve Window), push "Start Render" to begin the h.264 encoding. Once it is done, report pack with the time it took for the render.
View attachment 316375 View attachment 316376

I always get an error "Recording failed with Error: Failed to encode the video frame"

Okay, so it's because I had the SMBIOS set to MacPro,6 (I like my 5K screen to work at 5K, this is more useful to me)
I get the above error with the SMBIOS set to MacPro,6
with SMBIOS set to iMacPro,1 encoding completes to the end.
encoding the 3984x2327 37s quicktime recording (11.44fps) took 18s with the Vega 64.
Edit: I re-did it with a 2560x1440 screen recording, 60fps. it took 15s

 

[RuleBreaker01]

Everyday some new conspiracy theories right here... Please stop it.

@macjai
The Vega works perfectly I don't know what you guys are doing...

What conspiracy are you talking about?
I'm only stating what I'm experiencing.
With SMBIOS set to iMacPro,1 ; I can't hotplug screens and my 5K screen only gets 2560x1440 resolution. But I get hardware encoding/decoding. Screen is seen as a 10 bits HDR (ARGB2101010)
With SMBIOS set to MacPro,6 ; I can hotplug screen, 5K screens work at native resolution, but not hardware encoding/decoding (just like the real mac pro 2013). Screen is seen as 8 bits only (ARGB8888)

You haven't answered my question: can you plug a 2nd screen once the system has booted: does the layout reconfigure itself, same when you disconnect the screen, does the layout reset itself to the remaining screen.
Just like what you would expect from a "perfectly working" graphic card.

I'd love to get it working properly with iMacPro,1 ... not for the lack of trying...

 

[eiriasemrys]

Anybody here use Davinci Resolve 14 in High Sierra? Exporting any video file to Pro Res 422 1080p/4K works fine and CPU is fully utilized, demolishing the performance of an iMac Pro (I would know, as I have the base model sitting right next to me for comparison).

However, exporting to h.264 is a different story, where the iMac Pro takes the lead by a huge margin. On my 7900x rig, exporting to h.264 (at any resolution or bitrate) starts off fast, but drops in speed tremendously after a few seconds (for example, from 80 frames per second to 20 frames per second). The iMac pro will stay constant at about 60 frames per second.

I've tried using CUDA on my 1080ti and OpenCL/Metal on an RX580. Same results. RX580 seems to be functioning normally in FCPX, as my Bruce X time is 14 seconds. I'm wondering if it has anything to do with power delivery, because I can hear my GPU coil whine in 1.5 second intervals - almost like it's struggling to ramp up to optimal frequencies. CPU also ramps up and down in power consumption in that same 1.5 second interval pattern.

Also, we'd normally say the that h.264 export is accelerated by quick sync, giving the regular iMac a clear advantage; however, the iMac Pro doesn't have a iGPU with quick sync, yet it is way faster. My Macbook Pro 13 inch is also much faster, with the RX580 attached as an eGPU in Davinci Resolve.

Any ideas?

Thanks.

I am a colorist on Resolve 14 and I can confirm the same behavior. On some long form project I have exported prores and done the h264 through another system just to free up my main rig quicker. Seems to be an issue regardless of destination read-write speed.

Just conjecturing some conspiracy, but I would say it seems as though hardware encoding h264 in Resolve with these processors is being throttled by some unknown process/setting/etc.

 

[kgp]

I am a colorist on Resolve 14 and I can confirm the same behavior. On some long form project I have exported prores and done the h264 through another system just to free up my main rig quicker. Seems to be an issue regardless of destination read-write speed.

Just conjecturing some conspiracy, but I would say it seems as though hardware encoding h264 in Resolve with these processors is being throttled by some unknown process/setting/etc.

Buy a Vega..

Else come up with facts and try to find the source of your problem..

The statement that "the encoding with these processors is throttled" is wrong. It is definitely not the Skylake-X hardware encoding that throttles the h264 encoding process on your system. Try to find the source for the observed throttle and report back with facts instead of spreading wild imprecise speculations and conspiracies that confuse all other users.

@DSM2, do you use a NVMe drive? If so, which NVMe drive do you use? Do you think that the latter can introduce some performance loss during encoding due to thermal throttle?

Thanks for your comprehension and good luck,

KGP

 

[kgp]

I always get an error "Recording failed with Error: Failed to encode the video frame"

Okay, so it's because I had the SMBIOS set to MacPro,6 (I like my 5K screen to work at 5K, this is more useful to me)
I get the above error with the SMBIOS set to MacPro,6
with SMBIOS set to iMacPro,1 encoding completes to the end.
encoding the 3984x2327 37s quicktime recording (11.44fps) took 18s with the Vega 64.
Edit: I re-did it with a 2560x1440 screen recording, 60fps. it took 15s

Who told you to use SMBIOS MacPro6,1 with iMac Pro special build 10.13.3 SA (17D2102)?

By the way, pete1959, your statement that correct "SSDT patches make the system unstable" is wrong and pure nonsense, sorry. Also your conspiracy that the i9-7980XE might need some patching is misleading and totally wrong. Please don't discuss things you do not sufficiently control or understand and avoid wrong respective recommendations and conclusions.

BTW, back to your post, I also clearly outline that my proposed Gigabyte BIOS settings might be very basic, incomplete and need to be optimised in any case, as they originate from quick tests with the Gaming 9 at the very initial step of my guide development. Instead of claiming that "kgp's suggested bios settings for Gigabyte your performance will be way down" you should rather precisely state here what to add or skip in the Gigabyte BIOS settings included in my guide to optimise the performance. This would be a positive contribution, in contrary to your else negative propaganda against my guide and related implementations.

pete1959, I don't like to see people spamming my thread with obscure ideas and invalid conspiracies based on your misleading recommendations and conclusions.

Thanks for your comprehension,

KGP

 

[kgp]

If they use Nvme Drives it’s thermal throttling. I use one by myself but mine is cooled! I use an
Samsung 950 Pro. Best way is to watercool the Nvme drive for long rendering seasons!

@DSM2, what could you recommend for water-cooling the NVMe?

Did somebody order and check out this passive NVMe heatsink solution?

https://www.ekwb.com/shop/ek-m-2-nvme-heatsink-nickel

I just ordered one for testing..

With the onboard ASUS Prime X299 Deluxe NVMe stock heatsink one already notices high idle NVMe Temps in the order of 39 deg C.

When running a Blackmagic NVMe benchmark loop, the NVMe Temps can rise up to 50 deg C, in line with a NVMe performance loss of up to 1000 MB/s.

 

[kgp]

kgp,
if you're going to go hunting in other threads for conspiracy evidence and fuel to make allegations against other members I fear you have finally gone completely mad.
I stay away from your thread unless I can say something relevant. For example I suspected thermal throttling in this post in your thread but he replied that he had tried SSD as well as NVME.
You are quite welcome to copy the gigabyte bios settings from my thread to correct your deficient settings in this thread. You only had to ask.

I must say I am very disappointed that you continue to recklessly endanger your standing here by needlessly provoking the users.
For your info, the builds are now unified and there are no special imac pro builds.

I am not hunting for anything.. your comments are just obvious.. as it is also obvious where the recent user feedback here in this thread comes from ...

Forgive me that I read some of your recent comments in your thread, but they are public to anybody. Thus, I hope I do not need any special permission to do so too.

Your comments about NVMe thermal throttling are welcome and are in agreement with my own observations. This however does not state for several other comments from your side..

Again a necessary correction: The official 10.13.3 SA distribution still consists of a standard and special iMac Pro build. Everybody knows that with the final release of 10.13.4, there will be a Combo Full Package Installer instead. However, 10.13.4 is still under beta testing and has not been officially released. Thus, your comment that "the builds are now unified and there are no special imac pro builds" is only partly true (in terms of 10.13.4 public betas) and else incorrect and misleading at present state (in terms of official releases).

Else I would appreciate if you could avoid affronting comments like "I fear you have finally gone completely mad".. or affronting terms like "deficient settings".. This guide bases on the ASUS Prime X299 Deluxe and not on any Gigabyte board. My Gigabyte settings are some initial residual with clearly indicated warnings ..

Cheers,

KGP

 

[kgp]

That's a much more civilized post. Thank you.
I had already established that Rulebreaker01 was using beta 10.13.4, so the imac pro special builds were no longer in play.
The mac pro 6,1 fixes certain Vega flaws, for me it allows me to use DP on multiple screens. So it's not a conspiracy or an opportunity for you to attack, it's a tested practice.

You're welcome to read my thread, but please don't select individual posts and use them to make personal attacks on this thread.

Please don't confuse my defense with your repetitive attacks and derogatory comments against me, my guide and related implementations. There are many more of your attacks and derogatory comments spread over different threads and even different forums. I try not to take them personal or too serious anyway.

Your recommendation for using SMBIOS MacPro6,1 with iMac Pro special builds appears simply weird to me. Even when using future combo full package installers you don't know about other restrictions, implications or limitations when following your advice for using SMBIOS MacPro6,1 instead of SMBIOS iMacPro1,1..

Anyway.. nothing for bad.. have a great day..

KGP

 

[kgp]

I'll ignore the completely false bit at the beginning...
Of course using SMBIOS 6,1 seems weird to you, you have no knowledge of using a gigabyte board with a Vega GPU.
We're finding that the later 10.13s are changing things. We're finding that the imac Pro 1,1 isn't perfect for us. Lets keep open minds about what can work better and keep looking at ways to improve our hackintosh experience rather than putting down anyone who tries something different shall we.

I should try to improve my Hackintosh experience? .. To become as experienced as you?

Perfect man!

Just do what ever you want as long it does not affect my thread and guide here, o.k.?

I never commented on your thread or discredited it in any way. In contrary, you permanently question or discredit my Hackintosh experience, guide, thread, work and implementations in public...

Make people reading your thread and EFI-Folder without the need for permanently discrediting or questioning the work of others and try to develop a reasonable and sophisticated Skylake-X/X299 desktop guide, if you think that the latter is still deemed necessary..

I do not have a Gigabyte board and Vega, but @DSM2 does. That's more than sufficient for me. He is sufficiently skilled and experienced to blindly believe in his feedback, contributions and recommendations..

No further comments from my side.. This discussion is already again out of control .. let's stop at this place.

Cheers,

KGP

 

[RuleBreaker01]

Buy a Vega..
If so, which NVMe drive do you use? Do you think that the latter can introduce some performance loss during encoding due to thermal throttle?
KGP

In my test I was using a 960 Pro nvme drive, temperature of the drive shows at a steady 42C... encoding seems fine. Though it's only a 20ish seconds task, maybe not enough to cause issue.