affinian

An "Edit/Purge" option is a good idea!

On the functional (requirements) side this would be "easy" to improve. Rename the current locking mechanism to "Soft Lock" and add a second "Hard Lock" which makes the layer (all its contents and relevant meta data) "view only".

@chessboard Now we have covered the whole ground: Win10 / Win11, AMD / Intel / nVidia - seems to be a rather tough one. Maybe it's due to a somehow compromised migration of the V1 settings. @affinity team: I'd like to offer my support for nailing this down even if it takes some time (reset settings, fresh install whatsoever) provided there will be appropriate guidance (and a debug version).

AWS is the "cloud "provider where (all) the Affinity Services are run from, I suppose. (Almost) No company of this size and in such a business would opt for on-premise operations to run this kind of services nowadays.

I'm in the same boat (so far, for Designer 2.0). Without having time for deeper analysis it needs a certain (still small like 20-30 upwards) number of layers and the UX will start to become lagging. This is most notable when navigating through the layer stack. For instance, after clicking on a layer there's always a small lag before the layer gets its selection highlight as well as its objects selected (with the move tool active). Once this has happened to start, a brush move also starts to loose its smooth "flow", sometimes the frames drop to 0 fps (stuttering). The usual recommendations (gpu rendering on/off etc.) don't have any obvious effects. It's no showstopper, as I can continue to do my hobbyist things - but it is obvious and reminds me of my past experiences 15-20 years ago when the machine was always to slow for nearly every non-standard usage scenario. cpu: ryzen 2600x ram: 32 GB Win 10 2H22 (latest release)

Why would you like to "develop" non RAW images in the first place, they're already "developed"? Is it just for the seemingly fast and intuitive workflow?

1. AP: Non-destructive RAW development (did someone mentioned the Ger..., DAM? 😁) 2. AD: Measurement tools (addition of document persistency would be highly welcome, though) 3. Universal license (even though this requires online activation)

Finally, yeah! And between the words/lines I hear a DAM is on the way as well. I have to prepare my wallet.

Hi Pšenda, yes, this makes sense. Thanks a lot.

Hi, in the help for Affinity Photo 1.6.5.123 there's mention of a preference <Font UI Size>. However, in the User Interface section of the preferences I can't find this option. Bug or feature? Thanks, affinian

I guess, auto-exporting development recipe parameters into an re-usable and human-readable format such as a side-car file wouldn't be the most challenging task. I consider defining the overall (base) direction more difficult, since it implies careful considerations, for instance - proprietary approach vs. XMP standard (can of worms)? - write AND read (re-import)? - history support? - versioning support (sort of virtual copies)? But yes, this is a feature I also would like to see as soon as possible.

Hi ostonica, I don't have the comparison experience on my own, but I can tell you why I didn't go for the i7: in contrast, to the - various - desktop family of processors afaik the i7 is "just" an i5 with higher frequencies. You don't get more real or virtual cores or other features relevant for your usage scenario. And an top when you do high duty stuff the i7 will be very likely throttled anyway thereby coming even closer to the i5 in practice. affinian

Hi, Windows platform user here. Though I don't know the impact implementationwise (especially as compared to MacOS), and I don't need dedicated stretch options I indeed would welcome a full-screen mode like the ones all concurrent major browser offer (F11). affinian

Hi rhidav134, it generally works (i5, 8 / 256), though I haven't done any have duty jobs yet*. *: I doubt I will ever do this, because this is what my workstation with a calibrated monitor is used for. But for minor touch-ups (for instance, when on the road) it should work well. Larger icons as an option would be a good start. ;) affinian

When I'm using my SurfacePro 4 as a "paint" tablet I also find the history panel a tiny bit too fiddly, with my finger it's a hit-and-miss thing. Surprisingly my hit rate with the context toolbar tool "buttons" is much, much better. But I also think, the toolbar isn't the right place. My wish - hey, it's Chistmas time :) - is one (or more) of the following options: - add support for a left/right wipe gesture - add two optional context toolbar icons for undo/redo (to allow for better separation from graphical tools they could be located on the bottom of the context toolbar) - bleduc's idea maybe is a good compromise? (post #16) affinian

@Asser82: yes you're right. Infinite options will end in a "disaster". From the Affinity Photo feature roadmap (didn't see this before) If this is what I guess, then it could be - it. :) affinian

Hi, just: though I'm an "old" RTFM sort of guy, these are absolute fantastic guiding aids! I've watched them all. :lol: Extremely well done, and for a non-native speaker listening the speakers talking is a real joy. :) Thanks heaps to the documentation team. affinian

Ok, found it out by myself. Indeed, it's the AppData pathway, in detail - for AD it's %HOMEPATH%\AppData\Roaming\Affinity\Designer\$version\user\ - for AP it's %HOMEPATH%\AppData\Roaming\Affinity\Photo\$version\user\ Within these folders there seems to be put everything imported by the user (I reckon the *.propcol extension stands for property collection) affinian

Hi Len, interesting thoughts. I thought all the time that a requirement for "real" (aka not just saving series of snapshots) non-destructive work is the parametric approach. So as you've comprehensively laid out, every single step (aka parameter change) gets filed/protocol-led and processed on the fly. In my belief, having a fixed order of the instruction sequence is no inherent "feature" of that approach. Afair, in LR the fixed sequence is the result of optimizations with respect to quality and performance and hence doesn't want to be exposed to the user simply by decision of the product management. As for AP - and leaving all destructive procedures aside -, aren't all adjustment layers in the Photo Persona nothing but parametric containers? Which can be freely re-sequenced? In my over-simplified view, the crucial entity is the base "layer" on which all those Photo Persona adjustments are working on. In detail, it is the question, why one need to explicitly hit the "develop" button to continue the work in the Photo Persona. Of course, all signs indicate that this step indeed is creating the pixel base layer for further processing, and which then gets co-stored in the .afphoto file. But what if in theory all settings in the Develop Persona would be changed into (invisible?) parametric "adjustment" layers building up their stack on the referenced raw file? The base pixel layer would be created on the fly in-memory each time a .afphoto file is generated and re-opened. Like in LR the performance critical sequence of those development instructions could be hardwired as well. This way, the files could become smaller. I know, reality is tremendously more complicated (performance!), and lots of internal dependencies not known to me are likely to conflict with this in practice. But my idea is, that AP has all the major building blocks already in use. affinian

Hi Sean, thanks a lot.

Hi, I may have posted my observations into the less proper section. So I'd like to reference it from this subforum: https://forum.affinity.serif.com/index.php?/topic/31411-ad-brush-settings/?p=156900 Summary: there's still something (not) going on with vector brushes. affinian

Hi, before I go into detailed learning, I want to have my settings backup routines set up (Windows 10). When tools (brushes, strokes, palettes etc.) get imported are the source files just referenced, copied or rather neither one, as the files serve as transfer containers only? Other way round: is it sufficient to backup %HOMEPATH%\AppData\Roaming\Affinity? Thanks, affinian

Hi there at Serif/Affinity, new customer here (long time Lightroom and Photoline user). :) I've just bought Affinity Photo for Windows w/o ever trying it before (though I was reading the beta news before) - just to support the venture to prove there is still a valid market for a uncloudified and non-rental software business model. Kudos for going that route! Though - also confirmed from the today's reactions posted here - the news about the "sudden release" of the final came to my rather surprise, I do see the underlying motivation from the marketing POV. But I am convinced Affinity (for Windows) came here to stay (that is, all the hickups reported will be solved within a reasonable period of time), so I have no problem with a release being slightly premature. Actually, at the current price tag, I had to vote with my wallet! Anyway, I just played with the develop persona, and can confirm, loading A7II, compressed raws from SSD is indeed slow (~10-15 secs). Furthermore the blockwise nature of the viewport update is visually evident on a fresh installation. Q: is there a setting for temp folders (for memory swapping)? affinian