Jump to content
You must now use your email address to sign in [click for more info] ×

David in Яuislip

Members
  • Posts

    1,253
  • Joined

  • Last visited

Posts posted by David in Яuislip

  1. I would suggest updating the graphics driver first as it's free.
    I don't have any Affinity results to share but using PhotoLab v7.2.0 to export 42 images 5134x3888 down to 600 high took 2h 1m 20s with the old driver, it now takes 0h 28m 25s

    Just created an image in V1 per your numbers 7086 x 10629, 32bit ROMM RGB and the performance is fine using paintbrush, clone stamp, smudge, erase brush 1000px diameter, this is a pretty mediocre spec pc as you can see below

  2. Resizing canvas is a pita in a macro. Transforms are hopeless, Duplicate and Equations are useful but although equations can increase an object's size it will be clipped by the canvas so that needs to be increased first. You can use John's advice to resize to a large number but here is another way. If you 
    duplicate a pixel layer
    rotate 90° around its centre 
    unclip canvas
    you will generate a square canvas
    Then use a fill layer
    rasterise
    rotate 45°
    unclip canvas
    you will generate a canvas increased by a bit less than x root2 so it's greater than your 20%
    (Do that step again and the canvas will be almost double the original etc.)
    The attached macro does this but I'm a bit foxed. The resized fill layer will have partial transparent pixels at the edges
    I tried a procedural texture of =ROUND(A/255)*255 for the Alpha but that failed
    I tried applying a curves layer to boost the alpha and that worked a couple of times but fails in the macro
    So, you can resize, for example, an 800x600 image to either 958 (x1.1975) or 962 (x1.2025) wide, I can't get it to be exactly x1.2

    MacroChoices.png

    ResizeCanvas120pc.afmacro

  3. Harsh but justified, I gave up after the msi/msix debacle

    As someone who spent a working life in heavy engineering where document revision control can be the difference between life and death I found this amusing
    https://forum.affinity.serif.com/index.php?/topic/191874-220-prompt-still-appearing/

    Now no one will die because of a few wobbly pixels but it reflects the company's attitude. Good luck to you

  4. 17 minutes ago, Sam1999 said:

    so where do I copy the mil-canon.xml file

    If you copy mil-canon.xml into the lens profile folder then the lens will not be auto selected when you open a raw file
    The xml file I posted has been modified
    <model>Canon RF 16mm F2.8 STM 288</model><!-- needs 288 for Affinity Photo V1 -->
    so that V1 auto detects it, I cannot comment on V2 as I don't use it

    LensProfilesFolder.png

  5. Yep, same in V1 however all is not lost providing you have a sense of humour
    If I need a column width of 497px, change the units to mm, dig out Excel, calculate 42.07933333mm @300dpi and enter that
    Change the units back to pixels and confirm, don't touch the cell widths when units are pixels
    Hard to believe that this is, "By Design"

    PubTableWidths.png

×
×
  • Create New...

Important Information

Terms of Use | 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.