That is what I do too. On the computer which I need for work I have upgraded to High Sierra only a few months ago. Result: Everything works just fine, no problems at all, right from the beginning. Why should I be a Beta-tester for Apple if I do not have to.
Whenever Apple moves on the next OS - the one after Catalina - I will upgrade to Mojave.
Catalina is a major step forward.
Away from legacy. Towards clean 64 bit and user integrity.
Apple have warned about this for many years and it’s not a surprise for anyone that this is not an update. It’s pretty much a new world.
I’m keeping 10.13 on a couple of macs as they are production units.
10.14 runs on another and 10.15 on my personal.
Yes I had to throw a couple apps away as they haven’t been updated in many years but those were not any important ones anyway.
I updated a few others but otherwise I’m pretty safe.
If you are on a T2 chip enabled Mac, be careful about upgrading for fun as the options to downgrade is not a simple task.
I’ve been using Carbon Copy Cloner for years and it has helped me in many cases. I can recommend the product (I get nothing from writing this here)
Installing Catalina does two things that will possibly not amuse you:
Disables running 32 bit applications
Introducing a partition scheme that separates system and user data into two separate volumes. While this is a sensible step from a security point-of-view, it can crash applications that are not ready for Catalina yet.
Good news! We have just updated PhotoLab 2 to have a tool that will repair the issue that was created by the upgrade to Catalina, so that everything goes back to normal.
At startup, if you were in one of the cases where you could have issues, you will see a dialog that will perform the repair. Everything should be quite clear in the dialog, and if you have more questions, you can also check this FAQ (that will be updated very shortly) to get more details about those: https://support.dxo.com/hc/en-us/articles/360034657752
The same update will follow very closely for PhotoLab 3 (with version 3.0.1), so that the repair dialog is proposed for users who migrated to our latest major version already. This version should be released early next week.
Note that PhotoLab 2.3.3 also fixes two other issues with Catalina: the zoom control that was not working properly, and also navigating in the Photos library from within PhotoLab.
I recently installed CatalinaI and have issues with finding images. I tried upgrading to DXO 3, but DXO3 can’t find photos. The Photos Library shows, but there’s nothing in it. Depressing.
Another related issue, if I select Edit with DXO in Mac Photos, it will bring the image into DXO, but it shows as a TIFF rather than RAW. This makes DXO unusable now.
m-photo
( Marc (macOS Sonoma on MBP16" Intel))
56
Hi Arthur,
Do not depress.
Things will be working soon I am sure.
(Un)fortunately I did not upgrade to Catalina yet so I can not help you but you are in good hands on this forum.
Try to see if your problem is already listed, maybe you only need a new update to fix this, else contact DxO support to get official help.
People using Catalina and PL3 will read your post. Keep faith
I recently installed CatalinaI and have issues with finding images. I tried upgrading to DXO 3, but DXO3 can’t find photos. The Photos Library shows, but there’s nothing in it. Depressing.
As was said above, the issue of showing photos from within the Photo Library is fixed on PL2, and will very soon be fixed on PL3 as well.
Another related issue, if I select Edit with DXO in Mac Photos, it will bring the image into DXO, but it shows as a TIFF rather than RAW. This makes DXO unusable now.
As for Photos sending TIFFs to PhotoLab, there’s unfortunately not much we can do about that, we have absolutely no control over what Photos is sending us, so that would be a feature request for Apple.
About showing Photos from the Photos Library: What is the expected behavior? I tried on MacOS 10.14 with PL 3.0.1, but couldn’t figure out how to access the Photos Library. I assume you don’t mean to open the bundle directory directly and start working in the inner data structures of Apple Photos?
I assume you don’t mean to open the bundle directory directly and start working in the inner data structures of Apple Photos?
That’s actually one way to do it, even though it’s neither practical, nor really ‘clean’.
The best way I could recommend would be to use “Edit With” in Photos to open the photo in PhotoLab, but even then, it will still generate a picture in a temporary folder within the Photos library bundle, so we still need to get inside there.
When that happens, either way, it should prompt you the first time for permission to access Photos. If you don’t get that prompt, you’ll have to go into System Preferences > Security > Privacy > Photos, and there you can enable PhotoLab to allow the access.
Yes, then it is in an ExternalEditSessions subfolder. And if I export to the same folder without a suffix in JPG or TIFF then Photos picks up the edit. Nice, I wasn’t aware of that.
Still, usefulness is limited because Photos will not supply the RAW file, but a TIFF instead, as mentioned elsewhere.
Still, usefulness is limited because Photos will not supply the RAW file, but a TIFF instead, as mentioned elsewhere.
Yes, we don’t have much say on that, unfortunately… In the case of a Photos extension, there’s a criteria that the photo needs not have any correction applied in Photos to have the RAW passed along. Maybe it’s the same with the Edit With, so that might be worth a try… but I wouldn’t hold my breath either!
