Thanks again for your help, I started again "from scratch" as best I could by: However, is there an "Aperture App" in your applications folder ? If there is then you should be able to download and run Retroactive. 'open' might not work with an unmodified Aperture. It is the running of Retroactive that modifies the Aperture installation such that it will run under Catalina. You mention "restore`, 'update' and download - but do not mention applying Retroactive. I have not yet checked Console logs to see what the nature of the error might be. Then did the App Store "install" of Aperture 3.6 via the "cloud download" and got the Open button - this was also a new procedure for me - but Open seemed to produce no activity, and obviously Aperture did not open. After I did the restore it appeared that the Security Update 2022-005 had NOT been applied so I ran that on top of the restore. That's a process I'm not too savvy about - previously I've only done individual files or complete machine restores from Time Machine backups - so I didn't know exactly which version of 10.15.7 I was getting. Yes I restored 10.15.7 from the Recovery partition (restart, CMD-R). If your images are stored in your Aperture library make sure you have a couple of copies of your library backed up externally to your Mac - you should be able to reconnect the library to Aperture (if you can get Aperture to install - good luck). However - took a while to import all my images again which reminds me that all my images were referenced. I did a Catalina Mac OS Recovery which retained all my data and apps - downloaded Aperture from the App Store - ran retroactive 1.9 (with the right options set) and have Aperture 3.6 running fine on my MacBook Pro. I know it's not much help to be told "works for me" - but that's the truth of it. If you restored using any other mechanism then you cannot guarantee the version you are restoring from does not have the remains of the faulty update that caused all these problems in the first place. That makes me wonder if you did indeed restore using the Mac OS Recovery option (Restart your Mac and hold down the Command and R keys to boot into Recovery Mode.). But if you restored Catalina from the version that is called by the Mac OS Recovery option then it should have been a fully updated copy. If you purchased Aperture from the App Store then it should still be available to download/install - unless you purchased it in a box with a physical DVD from an Apple shop.Īnyway, you say you restored 10.15.7 and then applied an update. I merely click on the download cloud next to the Aperture entry in my App Store account. I don't have an "installer" - by which I assume you mean a dmg file. Different graphics cards ? Or am I doing something wrong ? walterdavis states he is on a 2013 Mac Pro - I am trying to work with a MacBook Pro 16 2019. Which is it ? The implication is that there is an underlying hardware issue - different machines responding differently. I have seen several comments on line claiming that Aperture unboxed works fine under Big Sur, and several that it does not. Second issue, despite my seeing somewhere that the latest version of Retroactive allows import from an external drive and allows full access to referenced files - I cannot get files on an external drive to appear available for import (and thus I cannot import, obviously). The tally at the bottom of the thumbnail display reads the correct number of files loaded - so it's not a file access problem, just a display problem. Further scrolling up and down makes no difference, only some of the blocks are displayed and no more blank blocks get populated. After a moment, the blank block gets populated with thumbnails - but then on scrolling back up the screen, the first block is now blank and does NOT get populated. Opened Aperture and although it appeared to work, when I open a folder with several hundred images in thumbnail view and then scroll down the display, it appears that only the first 100 or so are displayed - the next "block" is blank. However, tried walterdavis solution and did a full clean install of Big Sur from scratch. I could upgrade to Big Sur but I'm afraid that would pushing it on my late 2013 MBP. Until then, that page says "the quick fix is to tell Core Image not use the software renderer." How is that done? I know nothing about this stuff.įYI, a comment from 5/5 on says the OpenCL break is "fixed in macOS Catalina Security Update Developer Beta 2021-003." But this discussion lists other issues with this beta update. The page he links to lists several other issues with this update, but I don't know if Apple, in fixing those, will fix this. So I suspect it's the OpenCL issue walterdavis cites above. I have the same issue, and it started very recently, probably with the 10.15.7 security update, which I installed on 5/4, not the update, which I installed on 12/8/20 or the supplemental update installed on 4/2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |