Search the Community

I decided to try real work in the beta and after an hour or so I got a save failure. I don't know if it's beta related or not but I haven't had a save failure in ages. I'd done nothing interesting since my last incremental save except for editing text and copying and pasting one inline image. I was saving to iCloud (which I always do) but saving to a local drive didn't make a difference, it just created a 0 byte file. Hopefully it's a one off but I'm mentioning it in case it's not an isolated incident. EDIT: I should add for others that doing real work in a beta is at our own risk. I choose to accept the risk so I can give it a good workout but I save and back up frequently in case I run into an issue like this.

I mean... Sure. Fixing the file corruption is a given. However, incremental saves are done for the very reason that sometimes things do in fact break, whether it's crashes or corrupted files. Just because corrupted saves need to be fixed doesn't change that incremental saves more often than not help bypass faulty software malfunctioning. You basically have two alternatives here. You can have your single copy fail which will lose you several hours if not days/weeks/months of work if you haven't remembered to do a secure manual copy. Alternatively, your latest copy and also multiple incremental saves are corrupted, but at least one of them actually work. At most you lose some time having to wait for a back-up save to be done. Losing minutes vs losing hours. Whole productions have been saved because of back-ups having been made. One such example being Toy Story 2, which was saved only because one person happened to have had a back-up after having worked from home. Objecting to what is a pretty standard feature in many software productions is quite frankly ridiculous.

One feature I hope gets added is the ability to have automatic incremental saves of a document. There have been times when of some unknown reason my documents get corrupted and lose data as a result of a save (happened to me just the other day). Having the option to have back-up copies that are a bit older than the latest save would help in safeguarding documents from getting unrecoverable data loss. Auto-save with a timer is also a feature that goes hand in hand with the previous feature. It makes it easier to ensure you have a reliable back-up copy in case of breaking documents. Being able to set these things up as either on a per document basis or done globally would be even sweeter.

This is the way most apps work but you don't notice it with other apps because you're not adding so much content to them at once as you do when you place a large image in Affinity. Apps don't save the entire file from scratch each time you save, they do an incremental save, saving only the changes from the last save. This saves time so you can get back to work immediately but it makes the file more complex and overtime it gets a bit fat. When it reaches a certain point the app does a full save which reduces the file size. You can do a full save at any time by choosing File > Save As instead of File > Save. Cheers

I don't think it's possible as you describe it. But, without relying upon any specific undo/history capacities of the software, you could go back in the history of the file, and recover only some changed elements (text, images, objects, styles,…) by copy-paste from an old version — instead of restoring the whole file. It's always possible to recover at least how file was before the last save, or older versions if you have some versioning, like the Revert command in the File menu of Apple's softwares, or manually by by systemically renaming files, or with Time Machine or other incremental backup solutions. Here, I don't suggest to restore the file but only open it, peep in and copy what you want. In practice: (If you don't have any other version of the file, or unwanted change happened since last save, do this first:) "Save as" your current work, with a new name or place In File menu > Open recent, open your previous version. Open an old version containing the element you want to recover unchanged Search and select this element Copy it "in its pristine state" Back in your recently modified document, paste the original element (perhaps applying though the new modified style, depending on what you missed) Or conversely, paste only the unchanged style to new objects. Sounds simple but this saved me many times!

Thank you, @LondonSquirrel and @v_kyr, I guess I understand what you say about incremental, atomic, database. But is this sufficient to explain the various scenarios in which these problems can occur? Also, especially the kind of coincidence of resulting consequences of these errors appear confusing to me. For instance: A. Save > file lost / must close –> Document re-opens fine and contains the saved modification. B. Save > file lost / must close > corrupted –> Document can't get opened but can get restored via "Add Pages From File". C. Save > file lost / must close > corrupted –> Document can't get opened and not get restored. D. Open > file lost / must close –> Document opens fine a few seconds later (!!). E. Open > file lost / must close > corrupted –> Document can't get opened and gets a new modification date although the user even had no chance choose "Save". (!!!! very rare but strange, too / never should be possible. Noticed 2x in the last 2 years + confirmed 1x by another forum user some weeks ago.) In my experience it can work but also can fail to choose the recovery / restore option when launching Affinity after an app crash or a manual app close without having saved all open documents –> means, .autosave files may be useful or not while it appears fully unclear when they work. As if it is unclear to Affinity itself what gets in fact stored in the two temp data folders. The "Recovery interval" in my APub is set to the default 300 (= 5 minutes) whereas I definitely got modification recovered that I did within the last minute before a crash, – well, I can't tell when the last .autosave or temp file was saved. Where are the last file modifications stored in the example below? Obviously not in the two temporary folders, although they immediately responded before to my back-steps in the history panel. What would happen to the last layout changes if the app would crash before the last save action? autosave & temp _live.m4v

The auto updater was a nice change in theory, but in its current form it is quite clunky and i think its actually a step back compared to the old process 1) If you choose to update there is literally no way to stop / pause / cancel the update until it finishes. You also can't use or interact with the software in any way while the update is in progress. 2) if you defer updates for too long to the point where you have multiple updates to download, there is no way to install them all at once or with a single prompt. You have to open up the software and click 'update', then close it and repeat for each update you are missing. All the meanwhile you are completely locked out of whatever you were working on. Compared to the current process, I strongly preferred the old method of manual downloads bc at least you could let the updates download in the background while you continued working on your project. And you also didn't have to worry about installing every incremental update in between your current version and the latest version, you could just download the latest installer and be done with it.

Trying to create text on a path and making adjustments to the path makes the app crash. Tried making incremental saves, but each time the app crashes the file reverts back to the same spot before the saves, so saving is not actually working.

I am looking at your signature, and you have the same card than I do, and practically my same Windows. Your CPU is very good. But mine is a generic PC (built by parts), while Dell surely has included special differences in hardware and software configuration. Super random, but do you have your Screen custom scaling (at windows settings/system/screen/custom scaling) at 110%? (I have a wild, crazy theory...). I'm sure future updates of 2.x will make it rather more stable also in less common scenarios, as you should be able to activate OpenCL in most systems. I am reading that those with AMD cards have worse experience ...I was expecting the opposite, as Open CL comes from AMD, kind of. But there are many factors here. Major global upgrades in every software I know (I believe it happened with the first release in Photo, if I remember correctly, but with many versions of Photoshop, etc) have a first stage, first moment, that is hard for early adopters, but for me, it is rewarding due to the massive improvements I am discovering in other matters. The JPG rotation. It's a bit a short in the dark, but I have experienced some apps, some software include certain special tags in the file headers, like in JPEGs (where meta data and certain stuff is stored), related to flipping and rotation. In the past, old apps would do this from time to time, that would flip your image but would display fine in the app that generates this, while once read back by another app, that header tag (a text that is stored inside the file) would be interpreted differently, forcing the rotation or flip. My suggestion is to do this same workflow with a different software as the external application to modify the linked files. And if you don't mind, uploading here a jpg of a non private image (like a free image of pixabay, unsplash or pexels, just modified (even with a brush stroke) in the external app you are using, and exported from there as JPG). So that I can open it here with tools that I have to check the file header of such JPG, see if it has some problematic tag, so that I can test it with or without the tag, and check how it displays in my Aphoto, if rotated or not. If so, then we know the culprit and how to avoid it, surely. In that case, you could even end up using one of these free utilities to clean that header every time (surely can use in batch mode, or do a simple python script for it), if you have a strong need to use such external app, or instead, the easy solution: using a different one (ie, csp doesn't provoke that). For starters, using now a different one would determine immediately if this is what is happening there. The jpg files saved externally, are losing quality due to compression every time you save them as jpg (png/tiff/psd are lossless) in any external application, or in actual Affinity, if you save the entire project as JPG instead of *.afphoto. So, if you modify the jpgs once embedded (ie, made them embedded, rasterized) in Photo, to my understanding, should not lose any quality as afphoto format is totally lossless, and the whole thing is being saved as such. If you keep them linked and only move (or even scale, flip or rotate) the linked object, to my understanding, it is not modifying the original pixels in the file; you are modifying like a reference, a connection point/box. As long as they are linked, only will lose quality if modified again in a external software, in the moment of re-saving there as JPG. And will lose again if exporting the whole thing (the entire aphoto file) as a big JPG, for example. And yep, the loss is cumulative, incremental, with every jpg-save. It is quite less perceived with very high quality settings, but it is still happening, it is in its nature. It is more noticeable with some graphical features (text, etc) than others. But while the JPGs being linked, just for moving them (or even scaling, etc, them), that's like a packet that you put there, that is referenced another file, so, in theory no quality is lost in the original JPG, is not being re-saved in any way. And if you embed or rasterize the linked files, it's all saved as an aphoto, no loss is added. Ehm, I should have explained that with fewer words and more clearly. Glad that I inspired you to give it a second chance. Everything is a trade off... I prefer a bit of complexity if I get a better deal in the long run, very generally speaking.

@Dan C Update - I just replicated the issue with my big existing document saved directly to my SSD, no iCloud (although the linked images were still on iCloud). I was testing by going to a page, adding some gibberish into the existing story in the text frame on that page, saving, and repeating until it happened. I was just trying to create delta versions with changes in a lot of places. I did not use Save As. One clue I can offer is that the final change I made before saving and encountering the alert was that I accidentally selected all the text in the story, which contained dozens of linked images, and overtyped the text, deleting all of it and the linked images. Saving would then have been meaningfully different than the last incremental save. I started typing this reply and then went back to Publisher, clicked OK, and chose Save again. I didn't make any additional changes and it worked fine. I'll try this the next time I encounter it to see if this is always true, that it's just a temporary glitch. In the past when I've encountered it I've always immediately used Save As but perhaps it really could Save if given a second chance. After it saved successfully the second time I kept going, adding more gibberish to random places in the document. Had this been real work I would have restarted for safety but I was being reckless since I was testing. I soon got an 'unrecoverable error' alert and the document was force closed. I wasn't able to re-open it because Publisher still had a lock on it.

Until everyone will finally learn that using any kind of cloud synced folders for storing current project files during working with them is a very bad practice and should be avoided. It may lead to all sorts of syncing errors and unwanted partial fragmentation that might occur when one app is using incremental saving method and cloud service is uploading file by parts at the same time. It’s always better to temporarily pause syncing while you work on the files and then just turn it back on once you’re done for today. That should save you from most kinds of possible file damage.

From what I've found, using CMD/CTL + Z or the Undo in the Menu, does nothing different than pressing the Reset button. Of the editing apps I have, Affinity Photo, Corel PSP, and Corel PhotoPaint, the latter is the only one having a Cancel button. Pressing Cancel, however deletes the adjustment. I agree with RC-R. How incremental would the step-back/forward need to be. Using the Levels Adjustment as an example, would the step-back be for just the Master Channel, or would it be for each Color Channel? How about each of the Color Models, RGB, CMYK, LAB? When we have the Merge, Delete, Reset and clicking on the X in windows or whichever color button on Macs, accepts the changes, adding a Cancel button to just revert to prior state is way to complicated, and unnecessary, when we already have actions that essentially do just that. Perhaps it requires one or two more clicks, but come on, are we getting that lazy nowadays.. 🤔 Further to the above, we can add multiple of the same type adjustment layers. We can choose to just add a new adjustment layer, we can duplicate one that we've made changes, then change that one. Hiding/Showing each separate adjustment layer (think the before/after used so much in tutorials) to revert to a previous state. I hope we don't continue a descent towards more and more AI, which tends to remove or prohibit our personal creative ability. Like AI? How about Singularity?

Shanezep Reading some of the other posts, I note that incremental save is available with the beta. I obtained a copy of the beta, but my skills are very low. Did not find how to do the incremental save. I lost all my work once in the 1990's, therefore I tend to save often. My original books were in PagePlus. However like many others, I do tend to get involved and keep on working. Being retired and re-learning for fun, anything I lose means that I will need to re-do the lessons again. I feel for you. I've forgotten so much and realise that I did most of it wrong anyway. However, back to the gist. Hopefully 'incremental save' will come on the next upgrade. Regards Ross

Hello I made a circular progress graphic within a Text frame in a newsletter template. Two issues immediately became apparent. 1) The donut/pie tools (why are they duplicated???) is really very oddly calibrated. Most compasses, clocks, counters, start with 0/12 etc at the top, NOT due East, 3 o'clock or 15 seconds. Most compasses, clocks increase in degrees CLOCKWISE. I can only think of one situation where 0 is horizontal and this is not a CAD programme. Even then, incremental increases usually go clockwise, as on a standard protractor. Not anticlockwise. The finished graphic then has to be rotated to achieve the desired result. Not a problem, but a niggling quirk the reason for which is not at all obvious. Why does this weirdly duplicated tool perform these functions back to front, contrary to common experience/intuition? 2) I wanted to add some text (a number) within this graphic to indicate the %age of progress the graphic is measuring. I could not see how to do this in Publisher and the programme insisted in inserting the text INTO the frame even though I had specifically selected the graphic object. I tried opening this in the associated Designer but the same problem. The only way around was to copy the graphic to a new page in Designer, overlay the text in the usual way and copy it back. Now find that I can actually select this overlay text, in the graphic, in Publisher. If I can select the added text NOW, there should be a way to insert in DIRECTLY in Publisher without the Text frame 'taking focus' - and all this time. I assume there has to be a way around such a laborious procedure. What would it be? Thanks Richard newsletter.afpub

Status: Beta Purpose: Fixes Requirements: Purchased Affinity Publisher Mac App Store: Not Submitted Download: Download Auto-update: Not Available --- We are pleased to announce that Affinity Publisher Customer Beta 1.10.5.1214 is now available as a download from the link above. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.10.4 version recently released to all customers. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below. --- Fixes and Updates - Mitigated UI stalls caused by a bug in macOS 12.0.1 (as best we can, things won't be back to normal until Apple fix the underlying issue). - Attempted to fix graphics corruption for some users of earlier macOS versions. Publisher 1.10.4 Release Notes --- To be notified about all future Mac beta updates, please follow this notification thread To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

It’s a shame iPad version shows only one decimal place so that such small incremental change in size is not evident. Hopefully mods will come back and investigate further. Psenda reports interesting change to rectangle size when loading svg file back to desktop and viewing in transform panel. But no change to rectangle position that I could see from his screenshot.

Hmm, sounds like the "Save" might now have added an additional amount of data which a "Save As" before probably didn't. I recall that the Affinity file format is build-up partly in a similar manner/fashion like backup software formats, meaning here that it saves the initial file and then also the incremental changes made to that. Further there is the build-in history function (which you already named and don't have activated), which when activated should store much more data, in order to be able to step back & forth between history states. Hard to tell what causes this, but honestly I have to say that I'm no Publisher user and thus others can tell you for sure better. - However, Publisher has a bunch of glitches too and it might be actually version dependent, especially also in terms of M1 and Monterey support here.

Status: Beta Purpose: Features, improvements and fixes. Requirements: Purchased Affinity Photo Mac App Store: Not submitted Download ZIP: Download Auto-update: Available Hello, We are pleased to announce the immediate availability of the third build of Affinity Photo 1.9.4 for macOS. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below. The 1.9.4 beta will have a performance focus as we circle back to clean up some inefficiencies which have crept in over time. If you notice performance improvements (or regressions!) over 1.9.3, or if you notice rendering bugs which appear to have been introduced in 1.9.4, please let us know. Affinity Photo Team  Changes Since Previous Beta - Added the ability to open FITS files directly, with control over demosaicing. - Performance and memory usage improvements when using placed images. - Performance and memory usage improvements when using embedded documents. - PDF import and export improvements. - Significant performance improvements in low memory situations. - Fixed small visual issues when switching back to templates from presets in the new document panel. - Fixed gradient map adjustment rendering issues. - Fixed expression input issues with decimal separators other than ".". - Fixed issue whereby ISO speed was incorrectly reported for some images. - Assorted other small fixes. - Localisation improvements. - Help improvements. Changes Since 1.9.3 - Added support for Xtrans sensor images in astro stacking. - Added GPU acceleration for blending ranges (in Advanced Blending). - Further, significant, performance improvements for documents with many layers. - Significant performance improvements when converting documents between ICC profiles / pixel formats. - Fixed performance issues with previous build with certain GPUs. - Fixed spare channel / mask editing. - Assorted metadata panel tweaks. - Further panorama stitching performance tweaks. - Added a new "median" mode to the frequency separation filter. - The gradient map adjustment now has a GPU implementation. - Restored the GPU rendering improvements which were dropped towards the end of the 1.9.2 beta. The benchmark version is once again set to 1920. - Improve performance when manipulating the selected layer immediately after loading a document. - Significant performance improvements in low-memory situations, reducing use of the swap file. - Panorama stitching performance improvements. - Significant performance improvements for documents which contain flattened, opaque layers (usually the result of merge visible). - Render EXIF exposure time as decimal if above 1. - Fixed F-number always showing as "f/0" for Leica M-series cameras (and others). - Fixed issue whereby LUTs would incorrectly report "Identity" as the description. - Fixed potential crash when quitting with layers still on the clipboard. - Fixed performance issues with CMYK documents when GPU acceleration is enabled. - Assorted small fixes. - Localisation improvements.

Status: Release Candidate Purpose: Features, improvements and fixes. Requirements: Purchased Affinity Photo Mac App Store: Not submitted Download ZIP: Download Auto-update: Available Hello, We are pleased to announce the immediate availability of the fifth build of Affinity Photo 1.10.0 for macOS. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below. The changes in the 1.9.4 betas have been rolled into 1.10. Affinity Photo Team  Changes Since Previous Beta - Fixed blend mode issues in the compositor. - Fixed star alignment in astro stacking. - Fixed issues with merge down / visible / selected. - Fixed adjustment panel histogram issues. - Fixed crashes when pasting between documents with different colour formats. - Fixed curves / levels / channel mixer adjustments which affect alpha when placed as an enclosure. - Assorted other tiny fixes. - Localisation improvements. - Help improvements. Changes Since 1.9.3 - Allow OCIO display path to use EDR capability. - Further patch tool fixes in LAB colour mode. - Obey the document colour space when putting PDF data on the pasteboard. - Show a message box on astro stacking completion, reporting light frames which could not be aligned. - Fixed a sporadic deadlock issue when hardware acceleration is enabled. - Fixed potential crash when typing text. - Fixed potential crash when rendering large panoramas. - Fixed issues when loading small documents into separated mode (documents were rotated). - Fixed live defringe bug when zooming. - Improved defringe performance and increased maximum radius. - Improve performance when multiple Info page samplers are placed on the document. - Improve adjustment layer performance when hardware acceleration is disabled. - Added CR3 support for Canon EOS 850D. - Emoji improvements and fixes. - Improved gradient fill noise rendering. - Lens correction improvements for Canon / Tamron / Sigma lenses. - Fixed crash when using monochrome FITS bayer pattern. - Fixed issues when refining a selection and outputting as a new layer with mask. - Fixed mesh warp issues. - Fixed issue which was preventing accurate selection of pixel layers. - Fixed crop tool issue where all presets were landscape. - Fixed Apply Image when used on masks. - Fixed TIFF DPI issues. - Fixed numerous sharpen brush tool issues. - Fixed crash when rearranging swatches. - Fixed issues when pasting pixel layers into larger documents. - Added support for emoji 😃👌😻. - Added the ability to load ACM lens profiles. - Assorted improvements to astro stacking, including the ability to edit the names of stacked images and the ability to stack images for different filters simultaneously. - Fixed issues opening some DNG files. - Serif Labs RAW engine improvements. - Assorted astro stacking improvements and fixes. - Fixed Nikon D780 Raw loading when using Serif Labs engine. - Attempted fix for occasional flickering of rendered document. - Fixed crash when deleting a procedural texture constant while the cursor is still in the description text field. - Fixed erratic behaviour with placed images. - Fixed missing controls when procedural texture dialog is in non-English. - Fixed crash when macro recording selected layer change in Japanese UI. - Fixed lockups when loading certain PSD documents with smart objects enabled. - Added the ability to open FITS files directly, with control over demosaicing. - Performance and memory usage improvements when using placed images. - Performance and memory usage improvements when using embedded documents. - PDF import and export improvements. - Significant performance improvements in low memory situations. - Fixed small visual issues when switching back to templates from presets in the new document panel. - Fixed gradient map adjustment rendering issues. - Fixed expression input issues with decimal separators other than ".". - Fixed issue whereby ISO speed was incorrectly reported for some images. - Help improvements. - Added support for Xtrans sensor images in astro stacking. - Added GPU acceleration for blending ranges (in Advanced Blending). - Further, significant, performance improvements for documents with many layers. - Significant performance improvements when converting documents between ICC profiles / pixel formats. - Fixed performance issues with previous build with certain GPUs. - Fixed spare channel / mask editing. - Assorted metadata panel tweaks. - Further panorama stitching performance tweaks. - Added a new "median" mode to the frequency separation filter. - The gradient map adjustment now has a GPU implementation. - Restored the GPU rendering improvements which were dropped towards the end of the 1.9.2 beta. The benchmark version is once again set to 1920. - Improve performance when manipulating the selected layer immediately after loading a document. - Significant performance improvements in low-memory situations, reducing use of the swap file. - Panorama stitching performance improvements. - Significant performance improvements for documents which contain flattened, opaque layers (usually the result of merge visible). - Render EXIF exposure time as decimal if above 1. - Fixed F-number always showing as "f/0" for Leica M-series cameras (and others). - Fixed issue whereby LUTs would incorrectly report "Identity" as the description. - Fixed potential crash when quitting with layers still on the clipboard. - Fixed performance issues with CMYK documents when GPU acceleration is enabled. - Assorted small fixes. - Localisation improvements.

Status: Beta Purpose: Features, improvements and fixes. Requirements: Purchased Affinity Photo Mac App Store: Not submitted Download ZIP: Download Auto-update: Available Hello, We are pleased to announce the immediate availability of the fourth build of Affinity Photo 1.9.4 for macOS. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below. The 1.9.4 beta will have a performance focus as we circle back to clean up some inefficiencies which have crept in over time. If you notice performance improvements (or regressions!) over 1.9.3, or if you notice rendering bugs which appear to have been introduced in 1.9.4, please let us know. Affinity Photo Team  Changes Since Previous Beta - Serif Labs RAW engine improvements. - Assorted astro stacking improvements and fixes. - Fixed Nikon D780 Raw loading when using Serif Labs engine. - Attempted fix for occasional flickering of rendered document. - Fixed crash when deleting a procedural texture constant while the cursor is still in the description text field. - Fixed erratic behaviour with placed images. - Fixed missing controls when procedural texture dialog is in non-English. - Fixed crash when macro recording selected layer change in Japanese UI. - Fixed lockups when loading certain PSD documents with smart objects enabled. - Assorted small fixes. - Help improvements. Additional Changes Since 1.9.3 - Added the ability to open FITS files directly, with control over demosaicing. - Performance and memory usage improvements when using placed images. - Performance and memory usage improvements when using embedded documents. - PDF import and export improvements. - Significant performance improvements in low memory situations. - Fixed small visual issues when switching back to templates from presets in the new document panel. - Fixed gradient map adjustment rendering issues. - Fixed expression input issues with decimal separators other than ".". - Fixed issue whereby ISO speed was incorrectly reported for some images. - Help improvements. - Added support for Xtrans sensor images in astro stacking. - Added GPU acceleration for blending ranges (in Advanced Blending). - Further, significant, performance improvements for documents with many layers. - Significant performance improvements when converting documents between ICC profiles / pixel formats. - Fixed performance issues with previous build with certain GPUs. - Fixed spare channel / mask editing. - Assorted metadata panel tweaks. - Further panorama stitching performance tweaks. - Added a new "median" mode to the frequency separation filter. - The gradient map adjustment now has a GPU implementation. - Restored the GPU rendering improvements which were dropped towards the end of the 1.9.2 beta. The benchmark version is once again set to 1920. - Improve performance when manipulating the selected layer immediately after loading a document. - Significant performance improvements in low-memory situations, reducing use of the swap file. - Panorama stitching performance improvements. - Significant performance improvements for documents which contain flattened, opaque layers (usually the result of merge visible). - Render EXIF exposure time as decimal if above 1. - Fixed F-number always showing as "f/0" for Leica M-series cameras (and others). - Fixed issue whereby LUTs would incorrectly report "Identity" as the description. - Fixed potential crash when quitting with layers still on the clipboard. - Fixed performance issues with CMYK documents when GPU acceleration is enabled. - Assorted small fixes. - Localisation improvements.

Status: Release Candidate Purpose: Features, improvements and fixes. Requirements: Purchased Affinity Photo Mac App Store: Not submitted Download ZIP: Download Auto-update: Available Hello, We are pleased to announce the immediate availability of the fourth build of Affinity Photo 1.10.0 for macOS. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below. The changes in the 1.9.4 betas have been rolled into 1.10. Affinity Photo Team  Changes Since Previous Beta - Allow OCIO display path to use EDR capability. - Further patch tool fixes in LAB colour mode. - Obey the document colour space when putting PDF data on the pasteboard. - Show a message box on astro stacking completion, reporting light frames which could not be aligned. - Fixed a sporadic deadlock issue when hardware acceleration is enabled. - Assorted small fixes. - Localisation improvements. - Help improvements. Changes Since 1.9.3 - Fixed potential crash when typing text. - Fixed potential crash when rendering large panoramas. - Fixed issues when loading small documents into separated mode (documents were rotated). - Fixed live defringe bug when zooming. - Improved defringe performance and increased maximum radius. - Improve performance when multiple Info page samplers are placed on the document. - Improve adjustment layer performance when hardware acceleration is disabled. - Added CR3 support for Canon EOS 850D. - Emoji improvements and fixes. - Improved gradient fill noise rendering. - Lens correction improvements for Canon / Tamron / Sigma lenses. - Fixed crash when using monochrome FITS bayer pattern. - Fixed issues when refining a selection and outputting as a new layer with mask. - Fixed mesh warp issues. - Fixed issue which was preventing accurate selection of pixel layers. - Fixed crop tool issue where all presets were landscape. - Fixed Apply Image when used on masks. - Fixed TIFF DPI issues. - Fixed numerous sharpen brush tool issues. - Fixed crash when rearranging swatches. - Fixed issues when pasting pixel layers into larger documents. - Added support for emoji 😃👌😻. - Added the ability to load ACM lens profiles. - Assorted improvements to astro stacking, including the ability to edit the names of stacked images and the ability to stack images for different filters simultaneously. - Fixed issues opening some DNG files. - Serif Labs RAW engine improvements. - Assorted astro stacking improvements and fixes. - Fixed Nikon D780 Raw loading when using Serif Labs engine. - Attempted fix for occasional flickering of rendered document. - Fixed crash when deleting a procedural texture constant while the cursor is still in the description text field. - Fixed erratic behaviour with placed images. - Fixed missing controls when procedural texture dialog is in non-English. - Fixed crash when macro recording selected layer change in Japanese UI. - Fixed lockups when loading certain PSD documents with smart objects enabled. - Added the ability to open FITS files directly, with control over demosaicing. - Performance and memory usage improvements when using placed images. - Performance and memory usage improvements when using embedded documents. - PDF import and export improvements. - Significant performance improvements in low memory situations. - Fixed small visual issues when switching back to templates from presets in the new document panel. - Fixed gradient map adjustment rendering issues. - Fixed expression input issues with decimal separators other than ".". - Fixed issue whereby ISO speed was incorrectly reported for some images. - Help improvements. - Added support for Xtrans sensor images in astro stacking. - Added GPU acceleration for blending ranges (in Advanced Blending). - Further, significant, performance improvements for documents with many layers. - Significant performance improvements when converting documents between ICC profiles / pixel formats. - Fixed performance issues with previous build with certain GPUs. - Fixed spare channel / mask editing. - Assorted metadata panel tweaks. - Further panorama stitching performance tweaks. - Added a new "median" mode to the frequency separation filter. - The gradient map adjustment now has a GPU implementation. - Restored the GPU rendering improvements which were dropped towards the end of the 1.9.2 beta. The benchmark version is once again set to 1920. - Improve performance when manipulating the selected layer immediately after loading a document. - Significant performance improvements in low-memory situations, reducing use of the swap file. - Panorama stitching performance improvements. - Significant performance improvements for documents which contain flattened, opaque layers (usually the result of merge visible). - Render EXIF exposure time as decimal if above 1. - Fixed F-number always showing as "f/0" for Leica M-series cameras (and others). - Fixed issue whereby LUTs would incorrectly report "Identity" as the description. - Fixed potential crash when quitting with layers still on the clipboard. - Fixed performance issues with CMYK documents when GPU acceleration is enabled. - Assorted small fixes. - Localisation improvements.

Psenda Not sure how to pick up a post. I typed 'incremental back up' as a search. Went straight to the post. https://forum.affinity.serif.com/index.php?/search/&q=incremental back up Hope this works.

Here are my top three items which drive me up the proverbial wall. Designer Swatches Panel Add New Document Palette. Currently requires a trip back to the hamburger menu and navigation to the Rename item. Add New Global Colour. Right click and navigation to the Rename item. Photo Channels Panel Create Spare Channel. Right click and navigation to the item. Frustratingly there is no incremental numbering, all the channels are named Spare Channel. I never want my new Document Palettes to be named Unnamed, Unnamed 2 with their new swatches to be named Global Colour 1, Global Colour 2 etc. And the same is true for the Spare Channels. Only occasionally am I satisfied with Spare Channel as a name. The Brushes work the same way as the Palettes from the Swatches, in regards to Categories. I don't find it in the least useful to have to navigate to the hamburger menu's rename item to change the default Brushes name.

Status: Beta Purpose: Features, improvements and fixes. Requirements: Purchased Affinity Photo Mac App Store: Not submitted Download ZIP: Download Auto-update: Available Hello, We are pleased to announce the immediate availability of the third build of Affinity Photo 1.10.0 for macOS. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below. The changes in the 1.9.4 betas have been rolled into 1.10. Affinity Photo Team  Changes Since Previous Beta - Fixed potential crash when typing text. - Fixed potential crash when rendering large panoramas. - Fixed issues when loading small documents into separated mode (documents were rotated). - Fixed live defringe bug when zooming. - Improved defringe performance and increased maximum radius. - Improve performance when multiple Info page samplers are placed on the document. - Improve adjustment layer performance when hardware acceleration is disabled. - Assorted small fixes. - Localisation improvements. Changes Since 1.9.3 - Added CR3 support for Canon EOS 850D. - Emoji improvements and fixes. - Improved gradient fill noise rendering. - Lens correction improvements for Canon / Tamron / Sigma lenses. - Fixed crash when using monochrome FITS bayer pattern. - Fixed issues when refining a selection and outputting as a new layer with mask. - Fixed mesh warp issues. - Fixed issue which was preventing accurate selection of pixel layers. - Fixed crop tool issue where all presets were landscape. - Fixed Apply Image when used on masks. - Fixed TIFF DPI issues. - Fixed numerous sharpen brush tool issues. - Fixed crash when rearranging swatches. - Fixed issues when pasting pixel layers into larger documents. - Added support for emoji 😃👌😻. - Added the ability to load ACM lens profiles. - Assorted improvements to astro stacking, including the ability to edit the names of stacked images and the ability to stack images for different filters simultaneously. - Fixed issues opening some DNG files. - Serif Labs RAW engine improvements. - Assorted astro stacking improvements and fixes. - Fixed Nikon D780 Raw loading when using Serif Labs engine. - Attempted fix for occasional flickering of rendered document. - Fixed crash when deleting a procedural texture constant while the cursor is still in the description text field. - Fixed erratic behaviour with placed images. - Fixed missing controls when procedural texture dialog is in non-English. - Fixed crash when macro recording selected layer change in Japanese UI. - Fixed lockups when loading certain PSD documents with smart objects enabled. - Added the ability to open FITS files directly, with control over demosaicing. - Performance and memory usage improvements when using placed images. - Performance and memory usage improvements when using embedded documents. - PDF import and export improvements. - Significant performance improvements in low memory situations. - Fixed small visual issues when switching back to templates from presets in the new document panel. - Fixed gradient map adjustment rendering issues. - Fixed expression input issues with decimal separators other than ".". - Fixed issue whereby ISO speed was incorrectly reported for some images. - Help improvements. - Added support for Xtrans sensor images in astro stacking. - Added GPU acceleration for blending ranges (in Advanced Blending). - Further, significant, performance improvements for documents with many layers. - Significant performance improvements when converting documents between ICC profiles / pixel formats. - Fixed performance issues with previous build with certain GPUs. - Fixed spare channel / mask editing. - Assorted metadata panel tweaks. - Further panorama stitching performance tweaks. - Added a new "median" mode to the frequency separation filter. - The gradient map adjustment now has a GPU implementation. - Restored the GPU rendering improvements which were dropped towards the end of the 1.9.2 beta. The benchmark version is once again set to 1920. - Improve performance when manipulating the selected layer immediately after loading a document. - Significant performance improvements in low-memory situations, reducing use of the swap file. - Panorama stitching performance improvements. - Significant performance improvements for documents which contain flattened, opaque layers (usually the result of merge visible). - Render EXIF exposure time as decimal if above 1. - Fixed F-number always showing as "f/0" for Leica M-series cameras (and others). - Fixed issue whereby LUTs would incorrectly report "Identity" as the description. - Fixed potential crash when quitting with layers still on the clipboard. - Fixed performance issues with CMYK documents when GPU acceleration is enabled. - Assorted small fixes. - Localisation improvements.

Status: Beta Purpose: Features, improvements and fixes. Requirements: Purchased Affinity Photo Mac App Store: Not submitted Download ZIP: Download Auto-update: Available Hello, We are pleased to announce the immediate availability of the second build of Affinity Photo 1.10.0 for macOS. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below. The changes in the 1.9.4 betas have been rolled into 1.10. Affinity Photo Team  Changes Since Previous Beta - Added CR3 support for Canon EOS 850D. - Emoji improvements and fixes. - Improved gradient fill noise rendering. - Lens correction improvements for Canon / Tamron / Sigma lenses. - Fixed crash when using monochrome FITS bayer pattern. - Fixed issues when refining a selection and outputting as a new layer with mask. - Fixed mesh warp issues. - Fixed issue which was preventing accurate selection of pixel layers. - Fixed crop tool issue where all presets were landscape. - Fixed Apply Image when used on masks. - Fixed TIFF DPI issues. - Fixed numerous sharpen brush tool issues. - Fixed crash when rearranging swatches. - Fixed issues when pasting pixel layers into larger documents. - Assorted small fixes. - Localisation improvements. Changes Since 1.9.3 - Added support for emoji 😃👌😻. - Added the ability to load ACM lens profiles. - Assorted improvements to astro stacking, including the ability to edit the names of stacked images and the ability to stack images for different filters simultaneously. - Fixed issues opening some DNG files. - Serif Labs RAW engine improvements. - Assorted astro stacking improvements and fixes. - Fixed Nikon D780 Raw loading when using Serif Labs engine. - Attempted fix for occasional flickering of rendered document. - Fixed crash when deleting a procedural texture constant while the cursor is still in the description text field. - Fixed erratic behaviour with placed images. - Fixed missing controls when procedural texture dialog is in non-English. - Fixed crash when macro recording selected layer change in Japanese UI. - Fixed lockups when loading certain PSD documents with smart objects enabled. - Added the ability to open FITS files directly, with control over demosaicing. - Performance and memory usage improvements when using placed images. - Performance and memory usage improvements when using embedded documents. - PDF import and export improvements. - Significant performance improvements in low memory situations. - Fixed small visual issues when switching back to templates from presets in the new document panel. - Fixed gradient map adjustment rendering issues. - Fixed expression input issues with decimal separators other than ".". - Fixed issue whereby ISO speed was incorrectly reported for some images. - Help improvements. - Added support for Xtrans sensor images in astro stacking. - Added GPU acceleration for blending ranges (in Advanced Blending). - Further, significant, performance improvements for documents with many layers. - Significant performance improvements when converting documents between ICC profiles / pixel formats. - Fixed performance issues with previous build with certain GPUs. - Fixed spare channel / mask editing. - Assorted metadata panel tweaks. - Further panorama stitching performance tweaks. - Added a new "median" mode to the frequency separation filter. - The gradient map adjustment now has a GPU implementation. - Restored the GPU rendering improvements which were dropped towards the end of the 1.9.2 beta. The benchmark version is once again set to 1920. - Improve performance when manipulating the selected layer immediately after loading a document. - Significant performance improvements in low-memory situations, reducing use of the swap file. - Panorama stitching performance improvements. - Significant performance improvements for documents which contain flattened, opaque layers (usually the result of merge visible). - Render EXIF exposure time as decimal if above 1. - Fixed F-number always showing as "f/0" for Leica M-series cameras (and others). - Fixed issue whereby LUTs would incorrectly report "Identity" as the description. - Fixed potential crash when quitting with layers still on the clipboard. - Fixed performance issues with CMYK documents when GPU acceleration is enabled. - Assorted small fixes. - Localisation improvements.