nschall

Dear developers,
It's unbelievable: since 2015, hundreds of users have asked here in the forum for "sticky settings" for the tools, but it is simply ignored by the Serif developers.
Sorry, but it's just annoying to have to reconfigure the tools again and again after opening each file!!!
...and with the selection brush it's even worse: here you even have to select the mode separately each time.
It can't be that difficult to integrate these functions into the app. Every other image editing app offers this by default.
Please, oh please 🙏 finally provide sticky settings with the next update!
 

I do not need to imagine. The current state of the Develop persona for raw files is effectively useless for much of my work. I have resorted to using (under protest and with much muttering and cursing) the software from Canon to develop my CR2 files when I need to. There is another piece of software that does some batch like stuff that helps too.
What really drives me up the wall with the way things are is that Affinity Photo has a Batch process ability. Photo's Develop Persona can remember named and saved settings and apply them to new raw files but the engineers have decided for what ever reason not to implement a bulk process for the Develop persona.
It is as though we have to process each image on a 36 exposure roll of 35mm film separately, take a 90 minute process and multiply it by 36.

Seriously why is this feature not getting attention? I have a timelapse of 1500 RAW photos. My only way to develop those RAW photos are to do manually or go back to adobe? :(

Nothing? Nobody?

Hi, 
 
I would like to know if there is a possibility tweak multiple RAW images with a workflow similar to the one offered by Canon's Digital Photo Professional or Lightroom. I know it is not generally ok to mention competing solutions, but this is the simplest way of explaining. 
So, what I want to do is the following: import a batch of photos in the Develop Module, create a recipe for one photo, copy -> paste it to al photos in the batch, and after those general adjustments are done go to each photo and make some finer adjustments, then export the files (as JPG or whatever format I want to use later maybe for some more post processing). Importing and exporting file by file takes a lot of time, while importing a batch of RAWs and only applying the same recipe to all does not allow fine tuning them separately. 
This workflow, described above, saves a lot of time and I cannot figure out how it can be done using the Affinity software. Basically this is the only thing that keeps me from switching as of now.  
 
Thanks in advance!
 
P.S. I know some may say that Affinity is not an alternative to other packages so that one would switch, but I really don't wanna go through multiple things retouch a photo. This is just a hobby for me.

It's been on the roadmap, but no way to know when, exactly, we will see it. It's unknown where in the priority stack this one is positioned. 
 

I agree!
I can't make the adjustments I desire to my raw files in the photo persona. The changes I need to make aren't available in the photo persona; therefore, I can't batch the changes I want to make to between 100 - 500 files per session. Can a dedicated macro panel be added to the develop persona? I really need this ability.
Thanks

I second (or third?) this feature request!
The method mentioned below isn't a real alternative to what the OP (and myself) really required.
I believe what this does is to develop first and then apply adjustments on the developed file (presumably only 8-bit). On the other hand, developing persona does use the higher bit info (10/12/14 depends on your camera manufacture) in raw files. This will results in significant difference if one need to adjust aggressively.
Here is a demo attached: the first picture is process in batch with a macro (+3EV and some denoise tweak). For the 2nd picture, the same tweak is applied in develop persona. I intentionally used a way underexposed photo to exaggerate this (note the bright spot in the sky is moon). But you can see the difference is non-trivial

Hello all,
I know this has been discussed countless times earlier, but I still can't wrap my head around about how this feature still isn't available by now.
As a timelapse photographer coming from Lightroom I need to process about 400 photos for each timelapse sequence. What is so difficult to just provide the feature of copy and pasting adjustments on one photo to a bunch of others? Or, since you provide the macro feature, use this also on the development panel? I really hope to see this feature in an update soon, or at least I'd like to have an explanation on why an apparently simple option like this can't be implemented.
I saw this topic being discussed for more than 5 years already. I really like AP and it's interface but this is a must have for me. Otherwise I need to go back to LR which is not what I want to.
Best regards
Mo

In 1.8.4.693, I've noticed the following behavior of the Crop Tool:
Open an image. Switch to Crop Tool. Switch to Unconstrained mode. Note the dimensions. For my image, the crop size defaults to 1050px x 590px. I change the Units from Pixels to Inches, and I see this in the Context Toolbar:

  I now type "8in" into the width box, and I get this:

  If I again type "8in" into the width field, I get this (note that the width changed to the same wrong value, but the height jumped to a wildly different value):

More information:
The Context Toolbar has two fields for the crop size, an input field for width and height, and an output field showing the resultiing crop size.
I start with the Context Toolbar showing this when I invoke the Crop Tool:

Both fields are consistent, and correct.
I change the units to inches, and I get this:


The input fields have been properly recalculated to be in inches. The output field has not changed. All is correct.
I then type a new width in the input field, and press Enter. If I use 8in I get this:

 
Note that the input fields now say inches, but both are really in pixels and match the Crop field. The values are correct for pixels, given that DPI. It's only the units in the width/height that are shown incorrectly.
I then type 8in into the width field again, and get this:

Note that the width remains the same incorrect 576 inches (is really 576 px). And the height has become 42525 inches. The Crop size shows 45256 px as the height.
Where did that height come from?
If I again type 8in into the width field and press enter I get:

Again, notice the height value, which is now up to 3061800 inches. The units are wrong, but the value matches the shown crop height. But where did that height come from?
 

Hi I am a windows user and yesterday I made the upgrade to AP 1.8.4 and I could not use Crop Tool properly, I could not change from pixel to mm, if I tried the scale was not correct to the added numbers.
I tried to reinstal, restart the computer everything, but only removing 1.8.4 and instaling 1.8.3 solved the issue. 
Please have a look on this issue. I had no anything like this before. 

This is just bad usability. Sorry, I love your product, but I have no alternative way to put it. I scratch my head everytime I have to manually change the aspect ratio. PLEASE FIX THIS. Thank you and keep up the good work

Click here to download the latest beta
Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
Fixes
[Installer] Prevent installation into non-empty directory Added EOS 1D-X Mark III to list of known CR3 cameras  Fixed Flood Selection Tool is offset with 'All layers' enabled Minor CR3 tweaks Fixed CR3 from a Canon EOS-R opening with a purple haze Fixed Develop Persona Red Eye Removal Tool crash Improved support for X3F files Removed units from the Crop Tool ratio option Fixed rotating a raw file in Develop Persona darkens it  Fixed adding guides in Develop Persona darkening image Removed "Windows Ink" option, and replaced with high precision WinTab support Fixed AI import incorrectly identifying as EPS when it was actually a PDF with extra data at the front Fixed PDF import for documents with extra data at the front Fixed PDF export for some Asian fonts that support many glyphs Fixed Layers panel dropping of items of right of thumbnail in expanded parents Fixed right-click context menu to disable Merge Down when attempting to merge a Pixel Layer into a shape Fixed PDF import crash due to infinitely searching for fonts Fixed HSL ring displaying incorrectly when returning to the adjustment  Fixed being unable to drag afassets into the app  Changed PDFs to open as restricted if we don't have permission to edit, copy or print them Fixed PDF export accidentally outputting all RGB images at 16-bit 1.8.4.650 release notes

Hallo Jörg und willkommen in den Foren
Derzeit ist es nicht möglich, mehrere RAW-Bilder gleichzeitig zu entwickeln oder Einstellungen von einem RAW auf ein anderes zu übertragen. Das Entwicklerteam plant, diesen Aspekt in einem zukünftigen Update zu verbessern, bei dem Einstellungen von einer RAW-Datei auf eine andere übertragen werden können.

This is what dev has just said—would this be everyone's preferred method? If so, I can log it as a formal improvement. 
Edit - I've just logged this. It seems this would be the preferred method internally so I hope this satisfies everyone else  

Yep! The fix should be available at some point as I've already seen it go in! 

Todays: Workflow and WINDOWS
(putting all my critics in one thread seems to overtax you - since 90% gets lost)

- if you resize (zoom in/zoom out) the content of an undocked window can you please resize the window accordingly. (if the resulting content is smaller than the workspace of the screen, adapt the window accordingly, if the content is larger, maximize the window frame with scrollbars)
- If you zoom a view too 100% the position of the content seems to be "random". Please instead center the content and resize the window accordingly! (I know you can do it since you do it with the "fit window" view as well)
- having all windows floating a new document should start in floating mode as well
- when selecting  "float all" the content of all windows should be centered and not randomly put somewhere over the screen - (one is happy to find the content at all). Window size should be adapted to content.
- One should be able to drag and drop a layer from one document into another document (not just with CTRL+c CTRL+v). Additionally: when trying to drag and drop the user gets the impression It would work based on the way the cursor changes when you drag a layer into another document - but in fact nothing happens.
- ESC still does not cancel essential operation e.g. cropping

Most of these bullet points have been mentioned many years ago even though they are absolutely crucial workflow topics. And we are not talking complicated additional features and rocket science - we are talking absolutely BASICS! You just simply ignore them. People that seriously try to work with the software are not of interest for you guys - what upsets me. I keep bringing them up every 6 month what seems to be a complete waste of time. I would roughly guess that AP takes up 30%-40% additional mouse-movements, keystrokes and actions to get to the same results as PS does JUST and purely due to your extremely poor workflow and handling issues. And we all know that time is money.

Cheers, Timo

Then the bug was introduced in APhoto Ver 1.7 and still exists in Ver 1.8. It does not exist in Ver 1.6 (I have all three versions running on three different computers).
I have long wondered why the simplest bugs persist for so long without being fixed in APhoto, just as I have long wondered why such obvious bugs are not caught in beta testing. I rarely use cropping and even more rarely specify a custom ratio, but I noticed the units in the ratio box immediately.
Serif appears to lack a systematic beta program that ought to include detailed checklists of features and functions to be verified in every new beta version. Simply waiting for random users to report on the limited number of features they themselves use, or testing only new or revised features, is not really beta testing as I knew it years ago. Cropping preset functions were changed significantly in Ver 1.7 when compared to Ver 1.6, and even when that major change was made beta testing was insufficiently rigorous to catch this obvious, very simple bug.

Thanks @walt.farrell for explaining how this works. It was far superior in APhoto 1.6. I did not even notice the vanishingly small "burger menu" in the upper right corner of the Cog menu dropdown  until you mentioned it and I went looking for it. Serif seems committed to making APhoto's UI ever more unreadable. Perhaps youngsters with fighter pilot vision can make out the full 4 bars. The Help system mentions the Presets Manager but doesn't mention the tiny "burger menu" that opens it. Presets Manager is not found by the search function in Help.
The Custom Ratio setting is very odd, at least when compared to the more sensible way this worked in APhoto Ver 1.6. Previous discussions of crop ratios in these forums emphasized that crop ratios are dimensionless. That is why the Units box is grayed out on the context toolbar and why the numbers defining the ratio were unitless. But now when you enter a number in the boxes to define your ratio, APhoto adds the symbol px to each number, implying it is measuring in pixels rather than in unitless ratios. I'd call that a bug, but perhaps thinking has changed at Serif.
 
 
 
 

Affinity is one of the most annoying programs of all time when it comes to usability with the tools as they forget settings each time.
1) NEEDS to remember tools settings - this is a non negotiable requirement for any computer program
2) Needs to remember file settings (I don't want to open .txt files in Affinity Photo), not sure why it does this
3) Hardware support on Windows

In no particular order:
Bug fixes Develop persona: Batch processing and non-destructive RAW development (sidecar files) Develop persona: Eyedropper for white balance Develop persona: Support for CHDK DNG opcodes / dead pixel interpolation Develop persona: Wider parameter range for adjustments that are limited to 25% or 50% today (saturation, for example) Develop persona: Better support for OnePlus DNG files (currently they always get a green tint and almost no saturation whatsoever - Lightroom handles them correctly in these regards) and other RAW/DNG files that have similar problems in Affinity today Photo persona: Numeric parameters in Curves Photo persona: Eyedroppers for whitepoint, blackpoint and graypoint in Levels and Curves Photo persona: Numeric parameters in auto adjustments (auto color, auto contrast, auto levels etc) Photo persona: Both Fill and Opacity parameters like in Photoshop, especially for "special" blend modes like Hard Mix - and fix the wording in the Layer Effects window that says "Fill opacity" - it's just regular opacity, same as the one in the layers list. Photo and Develop persona: Crop tool extended with "Crop to bounds" and "Crop to opaque" like in Panorama mode Any slider, particularly in Develop and Tonemapping personas: Doubleclick to reset slider to zero/default.

Photo: a total usability and workflow overhaul. More than any given feature.

It's in the context toolbar

I'm experiencing same issue with 1.8.2.  I'm using the Extract Detail Macro that Pedro Soares created here:   https://forum.affinity.serif.com/index.php?/topic/36265-extract-detail-macro/&tab=comments#comment-178831 

It too uses Vivid Light filter. Works fine on Jpegs, but creates colored artifacts on raw (NEF) files.  Problem disappears when I convert to RGB/8 bit.