Open a raw file and it opens into the Develop Persona. For example you can't re-do white balance. It may seem like a subtle distinction but it can be critical. You can re-edit that RGB file to your hearts content as often as you'd like but that's not your raw file and nothing that you did when originally processing the raw file is re-doable. ![]() Affinity's aPhoto file format is simply their version of an RGB TIFF file. As you note you can save your work as an aPhoto file. It's somewhat paradoxical since Affinity, when used to edit an RGB image, supports state-of-the-art non-destructive processing methodologies. As the software we use has improved and advanced we've been moving toward that goal - Affinity turns around and runs backward. I should be able to go back to any edit and alter any single step in the process independent of any other step in the process. My goal/expectation for a raw processing workflow is to have my work be non-destructive and non-linearly re-editable. I agree the term in that context may seem a bit severe but if you goolgle "Affinity raw workflow destructive" you get hits like this one that use the term in that context: Affinity Photo Destructive RAW developing- deal breaker? I agree that it's a deal breaker and consider Affinity unusable for raw processing until Serif corrects this issue. In the context of an editing workflow it's common to use the term destructive if the software forces your editing changes such that you can't selectively undo any of those changes. Affinity does not change the RAF file so it's not destructive in that sense.
0 Comments
Leave a Reply. |