PaulW61

...and amazingly, still not fixed in V 2.0!

Agreed! I have always installed apps under specific folders in Program Files or Program Files (x86). For example, I have all of my business programs including accounting, spreadsheets, word processor and contact manager installed in "c:\Program Files\Business App\...". I have all of my photo editing programs including Land and Sea Scuba, Affinity Photo 1.10, NX Studio, Pixbim, etc. installed in c:\Program Files\Photo Apps\.....". This makes finding my apps simple and well organized. Now that Photo 2.0 doesn't allow me to choose the installation folder as well as making it difficult to find the installation folder, this is going to make my organized PC much less tidy and cumbersome to maintain. Please allow users to select installation locations with your future releases and updates!

Still not fixed over one year later.

I use Capture One or DxO for RAW processing and then Affinity for any editing or further adjustments. I had various friends process the identical RAW file in the varying tools that they used and Capture One and DxO yielded the best results. The resulting files were strictly output from the software with no enhancements or changes of any kind I have attached a TIFF file that contains the outpts of eight of the popular programs if anyone wants to see the results (this file is also available as a much larger file for more critical evaluation). 8 RAW conversions.tiff

🙄

Has this issue been addressed as yet?

When doing batch conversions, Affinity Photo sets the default folder to the source folder and does not warn if photos are about to be overwritten. So if you decide to convert a group of 6000 x 4000 pixel photos to reduced 1500 x 1000 pixel photos, for example, and you do not change the output folder, the conversions will proceed and your original photos will be replaced by lower resolution ones without any warning. So if you do not have a backup, you've lost your originals. Affinity Photo should either warn that this is about to happen or change the default folder to a sub-folder of the source one.

I will set up an account for her and then request a refund for my purchase and, concurrently, buy the software with her email info. Thanks everyone!

I previously purchased a copy of Affinity Photo. If I change the email address in the Account Details page, I assume that all future notices will go to her. I think it may be easier to request a refund for the purchase and then buy them again with correct credentials. Is it difficult to get a refund?

I just purchased Affinity Photo and Affinity Publisher for my wife. The email and product keys have my email address attached to the purchase. How do I change the email address so that she is registered and receives updates? Thanks!

My wife would not be using the program for commercial use. Although we do not have joint accounts, we purchase things from both accounts without concern for whom the items are being bought. These purchases would include computers and software. I just want to be fair, as the low purchase price is really not an issue.

If my wife wants to use Photo on her computer, may I assume that as her computer is not under my control and therefore she needs a separate license, even though I have a licensed copy on my computer?

Since I haven't enabled WARP, I'm hopeful that Windows 10 Pro doesn't enable it automatically.

What is WARP? Explorer integration was disabled in Capture One.

The NEF files are on an external drive, where they've always been.

56fff567-f170-449d-9491-c9749dff4076.dmpa4224a2c-c14f-4c19-b3c1-4ddb79089a8b.dmp28631e33-23ef-42b9-a9e6-255aa04b6c7e.dmp The app simply closes without warning, nor are there any dialogs after the crash. I turned off hardware acceleration and didn't have a crash after editing two NEF files, although all Photo processes seem to be running a lot slower. I hadn't had this issue until a few days ago. I'm curious as to what can cause this sudden problem, as hardware acceleration had been enabled since buying the program years ago.

Windows 10 Pro, 20H2 The program crashes on every importation of any NEF file. If I import a JPG first, I can then import an NEF. But the program crashes when I start to work on the NEF file. I don't have the problem when running the software on my notebook, so there's obviously a conflict with Photo and something on my computer. All other software runs well, so it's not a hard drive issue. I've tried reinstalling the beta and have run a computer and registry cleaner to no avail. Is there an error file created on crashes that I can upload here?

Thanks for the response, Gabe. Here's an NEF file that shows the older Tamron profile on my system as well as a screen shot of the Profile. _NZ64005.NEF

The latest Beta is now showing my Tamron SP 24-70mm f/2.8Di VC USD G2 (A032) lens profile as the older, non-G2 version. Previous Betas were profiling it as a Nikkor 24-70mm, so this is a step in the right direction!

Thanks, 78deluxe, for the excellent explanation! I just bought a copy of C1 Pro for Nikon and am looking forward to seeing what results I can achieve with that software.

OK. I'm going to try Nikon Capture NX-D. 🙂

I was having trouble posting and voting a few minutes ago, but all is well now. :-)

Pardon my ignorance, but when you say that Capture One is the best RAW development software, do you mean that it has more and better adjustment tools within the RAW environment or that it does the best job of extracting the most out of RAW files prior to making any adjustments? I consider myself to be a bit of a novice with photo editing software and likely use no more than 20-25 of Affinity Photo's features. My question is whether by using Affinity I am starting off with a compromised image with which to work? What file format would one use if developing the RAW in C1 and then exporting to Affinity? Is this the best method? https://blog.thomasfitzgeraldphotography.com/blog/2020/3/working-with-capture-one-and-affinity-photo Thanks to everyone for your comments!

Hi David, Thanks for your input. I agree with you about getting differing answers from different people, but in my little test, I was only looking at conversions from Nikon NEF to JPG. I am very comfortable working with the Photo and Develop Personae and understand how to improve my shots using both. However, if I am working with a lower quality RAW conversion to start with, isn't that crippling my ability to match other softwares' results?

I have loved using Affinity Photo for Windows since it was released and used it exclusively to process my RAW files..... until yesterday! I was reading a few posts on DPReview about the results obtained by various software programs for processing RAW files. One poster said that he's tried ON1, DxOMark, Affinity Photo, Capture 1, Luminar, etc. and described the results obtained from each of the programs. His one comment that caught my eye was that he would never use Affinity for this task! I was curious to see if I could determine why this was. So I downloaded trial versions of some of the programs or got friends who were using non-Affinity programs to help me out. I loaded a Nikon RAW file (NEF) into Affinity and exported it to a TIFF RGB 16-bit JPG without making any adjustments and asked the others to do the same thing. It was a simple IN & OUT process. In my opinion, Photo and Luminar had the worst results and DxO had the best. Here are the photos for your comparison. I'd love to hear comments from the pros &/or from those who may think that my "test" was flawed and why. If not, I am hoping that Affinity has plans to improve its RAW processing. Untitled.tiff