We are working to reduce similar delays in the future. BC5 has taken longer to finish than we expected, and macOS has required more development resources than expected. We agree that the delay between the M-series launch and BC's native support for it has been too long. We're aiming to have a publicly available Technical Test or Alpha early next year. As we're able to open it up to more users, it's one of our early resources for expanding our tester base. I also try to mention subscribing to the News and Announcements sub-forum for email notifications. I've been gathering almost every email and forum post to form a list. We're in the early stages of sending out private invites for a Technical Test we're not ready to label it as an Alpha yet and why we've been hesitent on releasing a timetable. BC4 is performing pretty simple transfer commands, but Apple's translation for those commands to ARM support is likely very complex and removing Rosetta as a factor would greatly help us troubleshoot BC bugs. We are *really* eager to have some users help us test a native arm build of BC5. The comment you are quoting is specific to the M1 Max chip, which I had recently noticed a pattern of users reporting greater than expected stability issues on that specific hardware that we don't have on our in-office M-series hardware. To clarify, we are mostly on M-series hardware in-house, but still use older Intel hardware to test all of the currently supported macOS releases. Sorry, this thread has gotten a bit difficult to parse and some of my generic comments are targetted replies to specific User posts within the thread. Should we just seek out another solution and abandon BC, since Scooter doesn't want to announce a BC5 release date?
I have invested in other solutions, so version 4 will only continue as long, as my Intel gear sees any use (the 2015 model is only existing as a spare in case of trouble on an Intel platform). It's not that they haven't shown extraordinary patience in this matter. You are of course free, to decide to ignore your customers reasonable requests for a tentative timeline.
#Beyond compare mac m1 pro
It works on Intel Macs, but mine are on the way out (one is from 2015, the other from 2018) and day-to-day work happens on M1 (2021) or M1 Pro (2021), where BC 4 never survives for long without crashing the systems completely (panic followed by reboot).
#Beyond compare mac m1 update
We are planning on pushing out a technical test before a full release roll-out.Maybe, that is because - for instance - I cannot be bothered to send endless crash reports on a well known issue, when a new version 4 update is released. Since a lot of it is interconnected, we have a few things we really need to hammer out before we're able to announce an alpha or beta, but will as soon as we're able. I would not recommend multiple concurrent tasks, given that's usually the easiest way to trigger the issue.Īs for existing customers, we certainly understand the frustration and really want to get something out. I think with some troubleshooting, we could get it to be a bit more stable and useful for you. Are you performing many small but concurrent actions? My suggestion isn't to reduce your workflow until it is a single, tiny operation, but to start smaller and single task to test the stability, then slowly ratchet it back up to find the largest single task you can perform successfully and repeatedly. We're generally not seeing that level of instability. I had to hard restart five times in just one day this week and still didn't get everything synced. I would suggest subscribing to the News and Announcements sub-forum for email notifications to get a ping when we have something concrete to share.Aaron, this is an understandable approach for those contemplating new purchases, but what about for folks who have an unusable BC because of the massive memory leak leading to a system freeze issue on M1? Syncing small data sets doesn't help, as the system still completely freezes after ~10 minutes, even with doing multiple small syncs. I understand the frustration of not having a roadmap, but we want to be sure any purchases now are for the current release and feature set.
#Beyond compare mac m1 upgrade
Because of a combination of our upgrade policy and licensing, we've had experiences in the past where announcements have led to purchasing decisions for the future version rather than what was currently available. It's something we are actively working on, but are holding off on announcing a timetable until we have something closer to a deliverable.
0 kommentar(er)
