NotMyFault

Thank you for uploading. I get better results, directly from RAW files. But I always deactivate noise reduction (which is 40% by default and is absolutely unnecessary for your images). Can you please make screenshots of all settings used for creating HDR from RAW (new HDR stack dialogue) Creating TIF from RAW (which RAW engine Serif or Apple, all settings like noise reduction / refinement (which is effectively unsharp mask) creating HDR from TIF (new HDR stack dialogue) As a side note, new HDR from raw produced far too dark image, so I needed to boost exposure by about 2.6 units. (serif RAW). here my results (after mild tone mapping, and 2nd adding high pass and unsharp mask)

To give some examples where this function could be beneficial, and technically possible: you have misplaced a layer to fractional positions, causing blurriness. You want to change the layer position to whole integers, and re-apply all later steps. you have created 1000 objects, using the same color (or layer fx). Now you detect that you need to change the color, starting with object 201. Or assign a layer tag color (label) starting for no 201, allowing to select them and change their colors / styles in one click you have deleted one layer by mistake. The layer never gets individually edited layer, it is just required that it is in the layer stack and gets included in layer blending. No later edit will affect specifically this edit. you have used power-duplicate to create 7 shapes along a circle, one for every family member, by entering 360/7 for rotation in transform panel. One year later you want to create the same document structure, but include a new-born, so change rotation to 360/8, and add one CMD-J. The newly duplicated shape can stay as it is. You will add steps to place a photo into the added shape after re-applying all steps from history.

Thank you for this reply. I’m aware of this method. What I’m looking is unfortunately not possible with that method: copying those steps after a specific point in history.

Thank you for kind reply. Glad that the issue is solved. Happy to assist in future if you observe any issues. Many users (including me) are preoccupied by the thought issues their observe must be software bugs of Affinity apps. It helps to stay open to all possibilities and question yourself or the forum what could possibly have caused the issue (user error, UI traps, bugs in hardware, driver, operating systems, peripheral devices, or Affinity software bugs).

in such situations, don’t panic. First, save your document (as a new document) with history enabled. No matter what you did, you then have a recovery point, both for continuing editing, and analysis what might caused that issue (e.g. by uploading it to the forum publicly or to a private Dropbox link, on request available from Affinity staff) Then, before closing or saving over the current file: make a copy of the current file, to have a second (older) recovery file. Activate the navigator panel, and enlarge it, either by increasing the size of the panel column, or removing it from panel to floating, where you can make it as big as your display. Does the document rendering look ok in Navigator panel? next, we need to find out if you actually edited the file, or changed some app settings unrelated to the data in the document, but impacting how it is rendered. if you have a parallel installation of Affinity on another PC or iPad, transfer the saved file and open it there. Looking ok there? Then quit Designer on the PC having issue, restart the PC, and try again. Issue solved? If Issue is in the document: upload file here for analysis. If issue is how the canvas is rendered: check which view mode is active (pixel / vector /. -ray etc) and switch back to vector. To repair a potentially damaged file: open a new one of same size (in Publisher if possible), and import pages form the old file. Again, if something goes crazy the first rule is to stay cool, save the file with history, take a breath, and then use all resources like other PCs and the forum. This forum and all the great members, and Affinity staff of course, is the biggest advantage of using Affinity apps vs. Photoshop. You will get very fast and qualified support, including moral support.

Already filed a day ago 😁

A user can „destroy“ any document using the regular app in seconds, e.g. by deactivating history and deleting or flattening everything. I want to give experts users the option to actually use the saved history, to selectively remove unwanted edit steps, naturally on their own risk. This will not damage the document in the sense of „save not possible“ or file structure damage, it will only render some edit actions in history to „no-ops“ which can be simply and safely ignored. It is similar about getting the right to repair for documents which contain a defect. Of course you can destroy your iPhone when trying to swap the display or battery without the proper skills, spare parts and tools. Never the less, there are good reasons that Apple must allow such self-repairs. I just want the option to repair a sequence of edit steps (I made myself), and re-using a potentially lengthy chain of steps after the faulty one.

It is absolutely no problem if you think in the way of a software developer. Affinity apps can be seen as database apps, consisting of sql code (recorded macros) and data stored in the db (affinity documents, layers and their content). it would no problem to load the source code into an editor, and change a line containing an error. Of course, if you remove a line defining a variable, all references to that variable name would become invalid. But as a software devolved you are capable to change all dependent lines, and modern editors support this with search/highlighting etc. would you forbid editing source code because a developer could produce buggy code? for me, editing images is equivalent to writing program statements (macro recordings does this), plus handling of stored data. open a SVG document with a text editor: it contains just a list of drawing statements. You can edit any line, and as long as you keep the structure intact, editing some lines is absolutely no problem. Again, you can break the document, but this is no reason to totally reject the option.

Mein macro macht das Zerstörungsfrei durch „Sichtbares zusammenlegen“. Dabei wird eine Kopie erzeugt, und das Restaurieren passiert in dieser Kopie.

It really depends on individual circumstances. In case color profiles do not match perfectly, Affinity must convert the colors, and some normalization is applied (I’m not in those details, e.g. if you can avoid this). Currently there is a bug where you select a profile, and the wrong entry (down one position the list) is applied. This is an unfixed bug, which might play into the game.

I see this point. But Affinity allows to export bushes - this would even cause more damage. It would really help if Affinity would at least provide the information which brushes were used, which license used, etc. Similar to "resource panel" for stock images. For self created brushes (marked in metadata), unrestricted editing / export is a must. It is not a good practice to limit usage of data based on the most restrictive potential license - and offering no way to store and inspect those metadata.

on request only, not automatically.

Inpaint tester.afmacro Hi, I recorded a macro. Import it as preparation. create new file, 4K size add any image covering canvas run macro "inpaint" a selections is still active. Bug observed: Deselect does not work if hand tool or move tool is active. you need to activate any selection tool, and create a new selection, to get rid of old selection. Expected: CMD-D or Selection->Deselect should work no matter what tool is active

If possible, just switch the GUI language to English (if taking screenshots for the forum). You may install a beta app, to keep your working app in German. This will really help forum users to interpret the screenshots, and the app will show the correct terms. Translation service are of no use, as these UI terms are named quite "interestingly" in Affinity

I tried it with a 4K document and a stock image (https://www.pexels.com/photo/selective-focus-photography-of-assorted-color-ornaments-1208091/) Macro works. You can import the macro and try on your own. Inpaint tester.afmacro

I must apologise. I found time to check recording a macro with pinpointing step on MacOS. Bad news: When executing the macro, the inpainting step simply deletes the current layer! This is clearly a bug, I file a report.

Just create a fresh on, e.g. „new brush from selected layer“. More important, we need the principle function to inspect / re-edit vector brushes, e.g. export to PNG, and save metadata like intensity / image brush etc.

Hi, you steps refer all the second file. Can you check again? next, assigning a new profile will keep the color values, but change the rendering. Makes less sense if you want to keep the color representation. it would help if you can upload screen shots of every step (or a screen recording), and use info panel to inspect color values.

Can you try the 3rd option, selecting all areas (in additive mode), and then using the menu function? The layer must be rasterized to allow inpainting this way, so add this step (before).

What you see the state of art regarding Affinity apps. There are many operations not getting beyond a single cpu core, like file IO, layer stack analysis. GPU is only used for certain operations, and divides the data into many partitions (so every GPU core uses the same program, but different data). Even then, the runtime can differ for the „partitions“, so the slowest partition defines the pace, other GPU core Just idle. take this as simplistic explanation from an outsider, i have no insight how Affinity software actually works beyond what is publicly available (mostly in this forum, Spotlight, YouTube etc)

Still same issue on iPad M1, using V2.2 any update from Affinity?

Might be directing to a possible cause - we had other functions specifically breaking on M1/M2 iPads only Solved in V2.1 https://forum.affinity.serif.com/index.php?/topic/180157-designer-on-m1-ipad-unusable-with-pencil-or-touch/#comment-1040068 Unsolved: https://forum.affinity.serif.com/index.php?/topic/187093-v21-barely-usable-on-m1-ipad-layer-boundary-and-adjustment-ui-vanishes/#comment-1091141

There are many possible reasons. We would need several artifacts to be able to help in your specific case: a screen recording (at least screenshots) showing the full application window, including as many panels as relevant (color, brush, transform, navigator,info) include all brush settings, including „more“ (opacity, wet edges, protect alpha, ) we need to see all,color,and opacity values (layer, color, brush,channels) upload the actual affinity document. Always try to reproduce the issue in a new document, newly selecting the relevant brush from brush panel. of course, we welcome every report of users searching for help to get this solved. it is always possible to push partial transparency to zero or one, with 3 clicks: Add levels adjustment, on top of the layer with partial transparency choose alpha channel set white level to 0, or black level to 100 (boost to full / none) optional: merge down to bake in the result

While agree from a user standpoint that this is desirable, it is not the case in some cases. There are several PS functions not available in Affinity, and others can only be use with totally different workflow (e.g. channels panel, copy/paste, focus on non-destructive workflows) Wrt color profiles, Photo does not support Camera Profiles (X-rite). I don’t want to start another PS/AF discussion, I’m just explaining the best practices while using Affinity products - specifically for cases where user expectations are not met. You are free to consume this information, or stay on your point of view. Other forum users who find this thread via search might find my post helpful (or yours).

Auto-correction on Affinity. Would be glad being able to auto-correct all the software bugs in Affinity instead of just the spelling.