Ondra Kozák Posted March 26, 2018 Share Posted March 26, 2018 I'm new to the Affinity Photo (v 1.6.4.104) and love it so far. Maybe my PC is not powerfull enough (W10, 64bit, i5-6200U CPU @2.3 GHz, 8 GB RAM, NVIDIA GeForce 940M GPU) or my settings are wrong but I can't really work with panoramas in from RAW images. Recently, I tried to stitch a panorama from 5 .NEF images (total size 111 MB). After several adjustments and 3 pixel layers added, the afphoto file is 773 MB which maybe is OK but I can't really work in the program since every adjustment takes soooooo long to be reflected in the preview. I found that autosave function might be the problem since the .autosave file I found in the AppData\Roaming\Affinity\Photo\1.0\autosave folder created for this particular project is 6,6 GB (!) large. Any suggestions? Thank you! Quote Link to comment Share on other sites More sharing options...
John Rostron Posted March 26, 2018 Share Posted March 26, 2018 I take a heretical approach to problems like this and eschew the .afphoto files. For your problem I would first develop your five .nef files using exactly the same parameters for each. Export each as a .tiff, .png or even a 100% quality .jpg (I do!). You can then load your five non-raw images into the panorama option. When you have it adjusted to your liking, you can then export it in one of the formats suggested. The disadvantage of not using the.afphoto format is that you lose any saved intermediate processing. The advantage is that you save a lot of space, and loading time. You can still save your panorama as an .afphoto file. You will be given the option to do so when you close it. I usually decline this on the grounds that, if needs be, I can re-create my panorama in a minute or so from scratch. John Quote Windows 10, Affinity Photo 1.10.5 Designer 1.10.5 and Publisher 1.10.5 (mainly Photo), now ex-Adobe CC CPU: AMD A6-3670. RAM: 16 GB DDR3 @ 666MHz, Graphics: 2047MB NVIDIA GeForce GT 630 Link to comment Share on other sites More sharing options...
v_kyr Posted March 26, 2018 Share Posted March 26, 2018 AFAIK autosave files which contain incremental file changes, are more used for file recoveries in cases where some accident occured and in order to restore unsaved files etc. I'm not sure if these should affect the usual memory usage in some other way. Thus something like the MS/Sysinternals Process Explorer can be helpful here in order to see and detect to see how much mem is used by what resources for an app. Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2 Link to comment Share on other sites More sharing options...
evtonic3 Posted June 27, 2018 Share Posted June 27, 2018 I have accumulated 32 gigs of autosave files (I'm cleaning out my mac). Is it okay to delete these files from time to time? Quote Link to comment Share on other sites More sharing options...
R C-R Posted June 27, 2018 Share Posted June 27, 2018 22 minutes ago, evtonic3 said: I have accumulated 32 gigs of autosave files (I'm cleaning out my mac). Is it okay to delete these files from time to time? Yes, as long as the Affinity app quit normally the last time you used it & is not currently open. Theoretically, an .autosave file should be deleted automatically when you close the file that it is associated with, & also if you open a file with unsaved changes due to an app crash & decline to restore it. However, for reasons I don't understand, sometimes some of those .autosave files are not deleted & just hang around using up file space unnecessarily. Quote All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.