Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 7,1 MacOS Catalina 10.15.5 - Improvements or new nightmares?
- Thread starter MarciaFunebre
- Start date
- Sort by reaction score
Thanks for sharing this... the threads around issues have been putting me off at the moment and that gives some confidence back. 16 core / w5700x is the exact configuration im planning on (with third party RAM upgrade to 192GB most likely).
How is performance editing/exporting 4K video? I'm looking to use it for multicam but for now that will mostly mean two stream max and mostly SDR at this time. Hoping that a single w5700x would be totally enough for now and even leave plenty of headroom for more streams/effects in the future (plus potential to add a second card if really needed). Is that a realistic expectation from the w5700x?
Here's a review comparing it to the Vega II and other 2019 cards.
"WHAT DID WE LEARN?
At $1000 USD, the Pro W5700X is not cheap, but its cost/performance ratio beats the $2800 USD Pro Vega II. Ditto for third party GPUs like the RX 5700 XT (@$400 USD) and the VII (@$700 USD)."
"WHAT DID WE LEARN?
At $1000 USD, the Pro W5700X is not cheap, but its cost/performance ratio beats the $2800 USD Pro Vega II. Ditto for third party GPUs like the RX 5700 XT (@$400 USD) and the VII (@$700 USD)."
Pro W5700X versus other 2019 Mac Pro GPUs
real world speed test results for performance minded Macintosh users
barefeats.com
For those using Carbon Copy Cloner or generally interested in backups, cloning volumes etc - according to Bomich there is a new APFS file system bug introduced in 10.15.5:
& now a 10.15.5 'supplemental update' ....
Early last week we discovered an APFS filesystem bug in a beta of macOS 10.15.5 ... the short version is that we're no longer able to use our own file copier to establish an initial bootable backup of a macOS Catalina System volume.
The chflags() system call can no longer set the SF_FIRMLINK flag on a folder on an APFS volume. Rather than fail with an error code that we would have detected, it fails silently – it exits with a success exit status, but silently fails to set the special flag. That's a bug in the APFS filesystem implementation of chflags – if a system call doesn't do what you ask it to do, it's supposed to return an error code, not success. That's a fairly nasty bug too. Apple preaches that you should always check your error codes, and we do – religiously. This bug slipped past us for who knows how long because the system call exits with a success error code.
We don't need to set many of these flags, nor set them frequently – just on the first backup of the macOS system volume. It happens to be essential to the functionality of an APFS volume group, though, so the failure to set these flags means that new full-system backups created on 10.15.5 and later won't be bootable, and it will appear as if none of your data is on the destination (to be clear, though, all of the data is backed up). Kind of the opposite of what we're trying to do here. It's hard to find kind words to express my feelings towards Apple right now. Suffice it to say, though, I'm extremely disappointed that Apple would introduce this kind of bug in a dot-release OS update. We've seen 5 major updates to Catalina now, we should expect to see higher quality than this from an operating system
[automerge]1591051869[/automerge]& now a 10.15.5 'supplemental update' ....
Last edited:
I wonder why you are posting early findings as opposed to latest current information.
There have been 2 updates to CCC since the discovery of this change. The only current limitation to CCC is that the option to create disk image backups is turned off until a solution is found.
Initial and subsequent Full system backups (including bootable) work perfectly. That has been addressed and presents no problem. It’s only the disk imaging option that’s been turned off in Catalina (for now).
Last edited:
All the three OSes have their benefits and downsides as we know well. Linux is very fast and stable but has flaky bugs here and there especially in apps. Windows is very fast and very compatible with the most apps. macOS is user friendly but the slowest.
I think that most people's complains with macOS comes from the fact that it is mostly tested on laptops and mobile chips and internal laptop displays. How can devs and engineers develop an OS and apps that competes with the fastest Linux and Windows desktops if macOS is being mostly tested on weak hardware with weak cooling with less choice of peripherals and upgrades? They need desktop computers to do that and iMac/Mac Pro came too late and it's still a very closed up system with weak options.
I no longer respect Apple. I am here because I still have my iMac. I paid for it and I will use it until it dies. And, oh, how uncanny. Just now in the past 15 minutes I had a kernel panic. This in the long line of recent problems. My keyboard won't connect via bluetooth but works when hard-wire connected. My mouse works with bluetooth... after 2 reboots.
Wow, on a 3-year old iMac. So much for Apple quality... really gone down hill.
Yes, Linux is a toy. And I hate the Linux zealots as much as the others. But at least I'm not being ravaged financially while Apple laughs all the way to the bank, er, I mean to the sweat shops in China and then to the bank. Apple, Google, yeah, "do the right thing." Ha ha ha....
I must admit, it’s getting difficult to determine where 10.15 issues end and Hackintosh ones begin.
My 8700K build started with an RX580 on 10.13, got it to 10.14.6 no problem, and it was pretty much rock solid.
Decided to upgrade to a 5700XT and therefore had to upgrade to Catalina and it’s never been the same.
My Mac Pro is due in a little over a week, hoping it’s better than the system I cobbled together on a budget 2.5 years ago!
Having both a Hackintosh (9900k, 5700XT) and a Mac Pro (12 core, W5700X) the experience with Navi has been far better on the Mac Pro than the Hack. The early problems with the 5700XT AFAICT had to do with immaturity in WEG and the driver. The framebuffer support for the 5700XT was really sketchy at the start, and WhateverGreen didn't support it OOB despite the drivers being present (you had to add a special boot flag)
Vega was also fairly terrible on my Hackintosh (I had a Vega FE and a VII previously) and had a bunch of weird, random issues in Mojave and Catalina. This is also the case when I use my VII in an eGPU on my MBP.
RX580 always provided the best experience on my Hackintosh, yes, but that is perhaps because the GCN drivers had like half a decade to mature. Additionally I unfortunately expect the Vega drivers to suck forever. I consider 10.15.5 to be the actual start of support for Navi, with the previous Catalina patches being just kinda "supported"
Vega was also fairly terrible on my Hackintosh (I had a Vega FE and a VII previously) and had a bunch of weird, random issues in Mojave and Catalina. This is also the case when I use my VII in an eGPU on my MBP.
RX580 always provided the best experience on my Hackintosh, yes, but that is perhaps because the GCN drivers had like half a decade to mature. Additionally I unfortunately expect the Vega drivers to suck forever. I consider 10.15.5 to be the actual start of support for Navi, with the previous Catalina patches being just kinda "supported"
Just a friendly reminder that this thread was meant to be a place to collect experiences with the latest Catalina versions in conjunctions with the Mac Pro 7,1. Hackintoshes, iMacs etc. should have their own thread.
That said, has anyone being able to feel out what 10.15.6 beta? Are there any noticeable changes or fixes? (Kernel Panics, HDMI handshake problems, Multiple screen mess etc.)?
That said, has anyone being able to feel out what 10.15.6 beta? Are there any noticeable changes or fixes? (Kernel Panics, HDMI handshake problems, Multiple screen mess etc.)?
10.15.6 Beta 1 was rough. I had two kernel panics in a week, whereas with the last two betas of .5 and the gold release I had none. Beta 2 came out a day or two ago. No panics yet. The last KP I had with Beta 1 was actually caused by an Adobe extension.
This is wrong. The Navi bugs are purely driver related. WEG has nothing to do with it. Not using WEG doesn't change anything. Plus it already has been proven that Macs are affected by those bugs as well. That includes the MacBook Pro 16 as well as the W5700X of the Mac Pro. Graphical glitches, Final Cut crashes, wake from sleep freezes / kernel panics - they all have it.