Jump to content


  • Content Count

  • Joined

  • Last visited

About affinian

  • Rank

Profile Information

  • Gender
    Not Telling
  1. Hi, in the help for Affinity Photo 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
  2. 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.
  3. 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
  4. 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
  5. Good morning Sean, thanks for the hint. According to a quick morning test it seems to be the right one. At least I saw some dynamic. Tonite I will come back to it to understand all necessary and optional parameters better. Thanks a lot. :) affinian
  6. Hi, after I've updated the Wacom drivers to version 6.3-20.3 I still think the vector brushes' pressure sensitivity does not work. However, since I hadn't found much time to dive any further during the holidays the underlying problem might also be an user error. :D Hence I'd like to ask wether someone could provide a simple fool-proof step-by-step procedure to verify the pressure sensitivity is indeed working correctly over here (e.g. take default brush #123, with high pressure the strokes should become clearly wider.) Thanks a lot. affinian
  7. 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
  8. 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
  9. @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
  10. 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
  11. 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
  12. 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
  13. 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
  14. I've only just realized that Wacom tablet issues have been explicitly addressed with AD release So this thread and section might not be the best place for giving feedback on that. @mods: maybe a mod can move my post somewhere better, e. g. append it to the corresponding release thread? Thanks, affinian
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.