affinity photo editor

Hi has anyone used affinity photo editor. My son likes it and it now supports fuji xt2 raw . It costs about £30 in the uk Thanks Ian
Late to this thread but I've been using Affinity Photo on Mac since the beta. It is truly a Photoshop replacement, not a LR replacement. But with Version 1.5x it has added a lot of cool stuff. (focus stacking, pano stitching etc) and the "live filters" are great in that you can go back and change sliders after the fact.

As others have said, the RAW developer is a bit limited but it has gotten better. I use C1 as my DAM/Raw editor and Affinity as a plug-in or external editor to C1 (much like Photoshop is typically used with LR). Affinity is, for my money, faster than photoshop at most things. The content-aware fill option (called "in painting") works really well.

One area lacking is the print module. I have a Canon prograf printer and the canon print tool, which works as a plug-in in Photoshop doesn't do so in Affinity which is too bad. But

As it is, the competitors are really Luminar (new from Macphun, Mac only I think) and On1 Raw. I hope their DAM comes out and works well.
 
I've not had such issues. Hasn't crashed on me once, even when working on RAW files.
Good. The Windows version?

Cadder
Yes the Windows version.
Thanks. It looks too good not to try.

Cadder
It was nice to try, but the system crashes,clearly tied to Affinity, are troubling.

64 bit Windows 10 with latest updates on all drivers and software. Lenovo Thinkpad.
 
Last edited:
Yes I've been using the RAW part of Affinity and think it's pretty good.
 
Another vote here for Affinity Photos...Most if the reviews are excellent. They also apparently have a DAM software in plan for end 2017-2018...

--
Benoit
The raw conversion implementation is limited.
Not IMO
Many things that can be done prior to raw "development" in C1, LR, or SP must be done afterward in Affinity.
Like what, for instance? The Affinity raw module is pretty comprehensive AFAICT.
Try this: Work through the conversion of an RAF file and save your work and close. Re-start Affinity and re-open that RAF file and make a change to the work you previously saved.
You are then working in the pixel based photo editor... where much is possible after you've already "developed" your raw file. The tools available prior to development, however, are limited.
Nah.

The only reason I don't use it for raw is that I like the LR approach of DAM and raw together.

P.S. I use OS X and Affinity Photo is rock solid.
 
How does RAW conversion treat the "worms"?
 
How does RAW conversion treat the "worms"?
Affinity doesn't appear to suffer from "worms" as you say. However it's raw conversion isn't impressive. It fails to remove CA that other converters handle and it does not render fine detail as well as the better converters. Still it has promise.

BUT, HUGE BUT, OMG!! W*F!!! BUT: Affinity's raw conversion is dysfunctional and should be considered unusable. You can't save your work! Any work you do using Affinity's raw converter is discarded the minute you click Develop and commit the conversion. Re-open the raw file and you're right back at square one.
 
I ordered AP for Windows a couple of weeks ago. After using AP during this time, I like what I see. However, AP takes approximately 25 seconds to open a RAW from my X-T2. I also have a high-end spec PC. This will be a deal killer for me if this issue isn't resolved.
 
Last edited:
BUT, HUGE BUT, OMG!! W*F!!! BUT: Affinity's raw conversion is dysfunctional and should be considered unusable. You can't save your work! Any work you do using Affinity's raw converter is discarded the minute you click Develop and commit the conversion. Re-open the raw file and you're right back at square one.
Incorrect. Saves changes to the raw file. Remember to open the .afphoto file you created when you saved your work, not the original raw file which, quite correctly, is left unmodified.
 
BUT, HUGE BUT, OMG!! W*F!!! BUT: Affinity's raw conversion is dysfunctional and should be considered unusable. You can't save your work! Any work you do using Affinity's raw converter is discarded the minute you click Develop and commit the conversion. Re-open the raw file and you're right back at square one.
Incorrect. Saves changes to the raw file. Remember to open the .afphoto file you created when you saved your work, not the original raw file which, quite correctly, is left unmodified.
Incorrect. The afphoto file is the RGB output file that results from the conversion. The work done with the raw conversion tools does not remain re-editable in the afphoto file. The work done with the raw conversion functions is saved by any and all other raw converters but not by Affinity. Do this using Affinity:

Make adjustments using the raw conversion tools to tone response, white balance, detail and CA. Save the afphoto file and close Affinity. Re-open the software and reload the RAF file. Find your previous tint value change, modify only that leaving your tone, detail and CA adjustments as previously processed and re-generate a new afphoto file.

All other raw converters support that action as they should and quite correctly leave the raw file unmodified as they should.
 
Last edited:
I ordered AP for Windows a couple of weeks ago. After using AP during this time, I like what I see. However, AP takes approximately 25 seconds to open a RAW from my X-T2. I also have a high-end spec PC. This will be a deal killer for me if this issue isn't resolved.
It takes about a half minute to open an X-P2 raw file on my PC as well.
 
BUT, HUGE BUT, OMG!! W*F!!! BUT: Affinity's raw conversion is dysfunctional and should be considered unusable. You can't save your work! Any work you do using Affinity's raw converter is discarded the minute you click Develop and commit the conversion. Re-open the raw file and you're right back at square one.
Incorrect. Saves changes to the raw file. Remember to open the .afphoto file you created when you saved your work, not the original raw file which, quite correctly, is left unmodified.
This is NOT incorrect. The AFPHOTO file contains not only the raw file but the bit-map rendering that was previously generated from your raw conversion. If you want to re-examine your raw file to discover your initial conversion settings (in the Develop Persona) and perhaps tweak them a little, you find that all the earlier development parameters have been reset to the default. That is, you cannot reconsider and tweak your earlier RAW development settings; there is no way to discover what they were.

Moreover, the AFPHOTO files, because they contain your generated bitmaps, layers, and the raw data, are three times as large as the original 50 megabyte raw file
 
Well I don't find it's raw conversion to be very good

This is 100% shadows up on C1 and Affinity



 C1

C1



 AF

AF



--
 
This makes the point quite well.

Each time that he returns to the Develop Persona, he has no idea what the earlier settings were because all of the controls have been reset to defaults (0, 0, etc.).

So his next development cannot undo prior raw development settings by sliding all parameters back to their initial settings.
 
Raw conversion (Develop) tools can be used on an RGB (afphoto) file which is common with functional raw converters as well. So what? There's no way to save the original raw conversion adjustments as re-editable which is a core function of all other raw converters.
 
Raw conversion (Develop) tools can be used on an RGB (afphoto) file which is common with functional raw converters as well. So what? There's no way to save the original raw conversion adjustments as re-editable which is a core function of all other raw converters.
Exactly
 
Raw conversion (Develop) tools can be used on an RGB (afphoto) file which is common with functional raw converters as well. So what? There's no way to save the original raw conversion adjustments as re-editable which is a core function of all other raw converters.
When you go back into Develop your original changes are still applied so you can re-edit. But what is odd is that when you go back into develop your original changes are still applied with all controls at default position. This lets you go beyond the 2 stop exposure adjustment for example. However, the history and snapshots start from scratch. That part is dumb or I am missing how to retrieve them properly.

Shawn
 

Keyboard shortcuts

Back
Top