-
Posts
1,253 -
Joined
-
Last visited
Posts posted by David in Яuislip
-
-
Here's a pdf exported from Inkscape 1.3 (0e150ed6c4, 2023-07-21), seems to open ok in Publisher V1
-
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 -
This is my effort using Document/ Add Pages from File
Windows V1.10.6 -
After creating the preset it should appear in the Adjustment panel so it can be reused
Have a look here re. suggestions
https://forum.affinity.serif.com/index.php?/forum/52-feedback-suggestions/ -
The file doesn't open properly in Chrome either. I didn't understand
shape-inside: url(#rect4);
so I deleted it. That showed the text positions same as Chrome so delete the tspan styles as below. Do File/Clean Up Document, Save from Inkscape and it will now load properly into Chrome and Affinity -
Load an image and make the level adjustment layer as required
Select the adjustment layer and Copy
With the Macro panel start recording
Paste
Stop recording
Add macro to library
Use New Batch Job to apply the macro to multiple selected imagesIf you're new to macros and batch jobs then the built in help is pretty good
-
-
-
Photo V2 is supposed to open heif files so you could try renaming file.hif to file.heif
Otherwise you can use ImageMagick eg
magick file.hif file.tifwhich works for V1, good luck
-
@Xamora I've used the lensfun data but changed the crop factor to 1. The vignette no longer occcurs and the correction matches Photolab very well. Hope it's of use
-
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
-
2 hours ago, walt.farrell said:
Those PDFs have restricted editing capabilities, based on their security settings.
It's not too difficult to modify these files so that they can be opened/placed in Publisher or opened in a browser with copying enabled but this stuff is copyrighted and that should be respected, so no hints from me
-
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 -
-
I posted one earlier, see this
-
1 hour ago, Kepa Online said:
Sometimes I forget about this bug
Bug? What bug?
Using V1 I just exported an oversize image to png and opened an .afphoto file (66.9MB 6000x4000px) while that was happening
It took a couple of minutes to produce a 408MB png and open the new one. No crash, no problemMaybe it's a V2 mac issue
-
-
-
-
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" -
Most fx will cause rasterisation on export. If you open the svg in a text editor you may find something like
<image id="_Image1" width="2228px" height="1346px" xlink:href="data:image/png;base64,iVBORw0-----QmCC"/>
Cameo probably expects vector data and cannot process bitmaps -
Some files using
exiftool -makernotes:all File > File.txt
on the raws and the jpegs from Photo V1
4,769 NikonNEF.txt
0 NikonJpg.txt
7,418 OlyORF.txt
0 OlyJpg.txtYou can use exiftool to copy metadata from the raws to the jpegs until Serif gets this sorted
-
If you download Adobe DNG Converter you will have access to many .lcp files which should work with Photo by placing them in the Lens Profile folder
eg
RF 24-70mm F2.8 L IS USM - RAW.lcp
RF 50mm F1.2 L USM - RAW.lcp -















How to work on very large document way faster?
in Affinity on Desktop Questions (macOS and Windows)
Posted
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