This schema allows reliably restoring the OS drive WITHOUT clobbering work you’ve done on documents, etc, etc.Īnd no, I didn’t completely uninstall. So, I have OneDrive mapped to Drive D, while all the apps remain installed normally on Drive C. For me, that’s also about 40Gb, and I DON’T want it on the drive I make OS IMAGE backups of (Macrium Reflect). That way, the Gb+++ of device backups are on Drive E, not cluttering up Drive C, and can be themselves backed up separately.Ĭase in point 2: Microsoft stores OneDrive in the users’s Drive C area. So I wrote a batch script that aliases a different drive’s folder to the default Apple backup folder when I run iTunes, and disconnects it when I quit. But the files on which the software operates are stored elsewhere so you DON’T overwrite newer versions of them created since the OS drive image backup.Ĭase in point 1: On Windows, Apple iTunes backs up your devices to a user folder on Drive C and gives you no option to move them elsewhere (unlike the music library). It’s a simple and reliable principle: that if you have to restore (an image of) your primary drive for any reason (I’ve had to do it three times in the past year), you get the ENTIRE suite of installed apps in known working order as at the backup date. Thanks for the suggestion, Alan, but no, I don’t want to install APPS on anything but drive C. I continue to highly recommend the old products to colleagues, and I’ll continue to recommend they AVOID this product. This is not even Beta software: it’s the quality of Alpha software and doesn’t belong in paid user-land, especially for those of us who haven’t signed up to beta test this product. Please improve your entire software release process. So, you’ve “proudly” released a major update that makes an awful stuff-up of the first image I opened, and crashed on the second? You gotta be kidding. Opened image 2 (ordinary JPG): After loading the image, the app crashed off the screen while attempting its first auto-compute.

I did nothing but turn various auto switches off and on to see results, and mask in the text area. Opened image 1 (ordinary JPG): Auto text sharpen did a nice job on some selected text in the image, auto color was meh, but auto lighting made the whole image HORRIBLY dark. I would not use it in a professional context. PhotoAI 2, like 1 before it, is immature, gives inconsistent results, and is essentially play-with-it software. They give entirely predictable and repeatable results in a really busy professional workflow, and are a real pleasure to use (including via Lightroom). They are old and reliable and marvellous. This PhotoAI release reminds me why I continue to rely on the old apps: GigapixelAI, SharpenAI, DenoiseAI. If your product release processes were as good as the restoration capabilities of the software, you’d get 9.9/10. Sorry to sound cross, but these problems keep appearing again and again because there is obviously an inadequate pre-release checklist. I’ve complained about this MULTIPLE times in the past. In the meantime, please improve your pre-release processes. VERY HIGH PRIORITY → Stop your app hogging the primary monitor when full screen, and allow the Task Bar to appear.Īt some stage I will try out the model improvements. Please add to your pre-release checklist testing that your app does NOT take over the primary screen and prevent normal OS behaviour. I’ve complained about this in various Topaz apps MULTIPLE TIMES in the past. When PhotoAI is full screen on the primary monitor, it prevents Windows’ (10 Pro) Task Bar from popping up.

YOU’VE TAKEN OVER THE PRIMARY MONITOR – AGAIN VERY HIGH PRIORITY → Put model flie location support in Prefs. Give a bit of consideration for people using other stuff and managing their own systems, please. This is another example of Devs presuming their bit of software is the centre of the universe and client computers should and can be bent to the Devs will.

They also clutter Gb of my multiple Drive C image backups, which is totally unnecessary as they are downloadable after all. I do NOT want the model files on Drive C. Gigapixel, VideoAI) I have the models located on a different (high but not extreme performance) drive via the main bus. This is a VERY expensive EXTREME performance drive connected directly to the CPU. Your installer, without asking, downloaded and installed all the PhotoAI models onto my drive C. Here are the first two things I noticed when just installing and launching the app.

Macrium reflect restore image mac os