Erik Lindahl
Forum Replies Created
-
Titel and / or action safe will vary by region, destination and format.
-
With out specific answers in general..
1) Resolve should run fine to great on the new machines. Do mind they are laptops
2) Since Resolve really benifits from GPU(s), yes, defiantly. Also the enhance media engines will help.
3) Probably a bit yes. I can’t however see where you would drive more than 2 displays + BMD video out.
-
Erik Lindahl
January 29, 2021 at 1:57 pm in reply to: New Mac Pro Problem with H 265 Codec / Footage from EOS R5Problem is if you shoot the 4:2:2 codec variants with the se new cameras from Canon and Sony, few computers have hardware decode for this. This includes Mac and PCs. Apples M1 Macs are pretty much the only ones (aside from iPads / iPhones).
The solution is to shoot a different codec or transcode before editing.
-
Sorry for the late reply.
We got the OWC-SSD, 4TB and 8TB versions. I haven’t tested all configs but…
– a single drive gets around 3GB/s read and write across the drive.
– a 3 drive raid 0 get slightly above 6 GB/s read and write across the drive.The above goes for both 1TB or 2TB versions.
With “only” 6 TB/s r/w one could probably put the blades in a 8X slot instead of the recommended 16X slot. That said, in theory you could probably tax 2X raid 0’s quite heavily in parallel. Not sure you’d get the full 2×6000 MB/s though but probably / possibly more than 3-4 drives in raid 0 if you read / write to the respective drives.
I can also confirm doing some tests in Resolve today the importance of fast storage. One project – be that almost 6K ProRes 4444 – was heavily limited by the drive I had it on, and external USB-C drive running at up to 550 MB/s. Transferring the media to the internal OWC-drive saw real world read speeds of up to 1850 MB/s.
——
F-ing hell the forum removed 90% of my reply. Will try to add it again
-
Regarding NVMe support on the new MacPro there are quite a few options.
– OWC (up to 6 GB/s)
– Sonnet (up to 10 GB/s, BYOD)
– HighPoint (up to 14 GB/s, BYOD)They all have their pros / cons. We went with 4TB and 8TB OWC as they are “ready to go” and built with a fanless design.
You can even raid two HighPoint cards for a total of 8 SSD’s peaking at over 25 GB/s.
-
The Vega II’s are miles better than the 580’s. The latter are roughly 2016 tech.
-
12-core with Vega II vs 16-core with R580X is very work-depending.
In general if I had to choose I’d go 12-Core Vega II.
On the other hand you could use an off-the-shelf 5700X for 1/5 of the Vega II price in the R580X machine. I’d there recommend using the 5700X as your main display, really making the R580X a glorified Thunderbolt 3 controller.
One downside is the consumer cards have very little VRAM relatively speaking. I’d like 12GB minimum.
TBH I think the coming X5700 Pro from Apple will be best features / price / performance. With 16 GB of VRAM that’s also relatively future proof.
-
One note is most apps don’t use additional cards than the one connected to your display. Some outlier are there – Resolve for example or Premiere when rendering (but not during playback oddly enough). It’s also in general best practice to match cards. As and example someone on LGG used a Radeon VII Duo + a W7100 or something for Resolve where the W-card was used for GUI and the VII’s for compute. Removing the W-card and using one of the VII’s for both GUI and compute actually improved performance in Resolve.
-
Erik Lindahl
February 2, 2020 at 12:11 pm in reply to: A warning about Catalina and the 2019 Mac ProFirst reading this I figured the MacPro 2019 was “broken” in some way but really it’s, sadly, a case of how Apples – or rather any hardware and software works in this day and age.
You can’t ever down-grade a minimum system required for a given hardware. One could chime this as poor design but that’s always been the case. I’d never expect to be able to fall back to an older system or software version with a new machine. It sucks for sure but it’s a fact of our current world.
The fact that a lot of apps would break with macOS 10.15 I also figured was a given. If it ain’t 64-bit and really officially supported by system X, one shouldn’t expect it to work. Again, I just take this for granted – test before you update or upgrade.
It’s ironic that a lot of people moving to the Mac Pro 2019 says “it’s worth the cost since the system is up and running in a matter of hours” where clearly this isn’t the case for everyone (including the person who started this thread). That’s harsh for the people caught in situations where app X or Y won’t work anymore or where hardware Z just isn’t updated for the new guy in town. Sadly this has more or less always been the case.
For me the transition to the Mac Pro 2019 will be a clean install and a re-evaluation or all the software including plugins I use. The nMP 2013 will be frozen in time on the system it’s currently on as I know what works and doesn’t on it. Moving to the new hopefully only takes a day or two but I will most defiantly keep “the old” until I feel 100% confident in the new hardware and software.
One huge “gotcha” also seems to be the T2 chip and that you should disable most of its security features for doing things “like you have” (booting from external HDDs for example).
-
For future hardware HEVC support the Navi-based systems are your best bet. These currently include the 16” MacBooks and soon the Mac Pro 2019. When Apple will fully use these chips however is a software question mark. Could be an 10.15.x release in conjunction with a new FCPX release. Could be you’ll have to wait longer.
For the non-Navi based systems I think you’re out of luck sadly. I guess you could also try brute-forcing the codec with a 28-core Mac Pro…