While it is understand this is acceptable for novice users, in the area of high end graphics we have different requirements. Our typical image size is 40,000x20,000 pixels. For a typical file, this translates into about 8 minutes to save a file on the highest speed Thunderbolt2 SSD based RAID storage. Please understand why we prefer the option of disabling disk activity as our productivity is hampered by tasks not desired.
Simply stating that the saving of autosave is 'very quick' has no meaning. I currently have a 56,000x28,000 pixel document open and the app has been 'very quickly' saving the data for the last 12 minutes as the rest of the UI is frozen.
Our first impression is that large files keep the background tasks (such as saving change data) so busy the UI becomes unresponsive to inputs. This occurs to the degree even closing a window is not possible.
Too, the lack of a progress bar for operations such as opening a file leaves the user wondering what is happening. On these large files that typically require minutes to open the user is left hanging as to what is happening.
Another concern is how much disk space is being consumed by saving of this data. Noticing a large file can be closed and reopened very quickly suggests a caching strategy, which, while nice, could prove overwhelming for disk space. How does one delete this cache file?
As a side note, we just purchased Affinity Photo today for evaluation. We appreciate this is a new product and there is room for advancements which is good. First impressions? Affinity Photo is very impressive but possibly not suited to large images. Yes, we are entrenched in that 'other' photo editing program and welcome an alternative but we also realize there is a reason the 'other' program rules supreme.
