lepr
-
Posts
5,510 -
Joined
Posts posted by lepr
-
-
18 minutes ago, Hangman said:
The Math is actually very simple, for non-balanced dashed strokes 1 unit = 1 point for both the dash and gap widths.
1 unit = width of stroke
-
Welcome to the Affinity forums
Most likely, you will find great improvement by disabling 'Snap to gaps and sizes'.
-
5 hours ago, Torstein said:
It works the way I expect with the Mask layer at bottom, as long as I don't select preserve alpha in the blur layer. With preserve alpha it gives the photo "aura" treatment in any way I order the Mask layer before or after the Blur layer(s).
No, Preserve Alpha prevents the "aura" effect. It should, logically, do that and it actually has worked correctly every time I have enabled it over the years.
-
19 minutes ago, Torstein said:
Some more experimentation and I have found that the order you arrange Mask and Blur layers is important!
Yes, that's what I told you.
19 minutes ago, Torstein said:(That feels like a bug too me!)
I disagree.
19 minutes ago, Torstein said:To my surprise, the last sample with Mask below Blur works fine, while the one with the Mask above the Blur do not!
Yes, I said the blurring with Preserve Alpha enabled must happen after the masking.
15 minutes ago, Torstein said:Now I do understand what you are saying....
Cool
-
1 hour ago, Torstein said:
Can it have had something with the preserve alfa selection?
That and the order of operations is crucial. See my most recent example with four variations. In all four, Preserve Alpha is enabled and blurring is happening after masking.
-
6 hours ago, PierMax said:
Seem that is a bake problem
The bake distortions are a big problem, but a perspective Warp Group itself produces terrible results - circles should become ellipses but they become ovoids, and straight lines should remain straight but many become curved. Example below:
-
We've all been overcomplicating the solutions. Here's an AP1 document with four simple alternatives which give the same result:
blurred background four variants (AP1).afphoto
-
3 hours ago, thomaso said:
You misunderstood me
I'm quite good at that LOL
-
5 hours ago, thomaso said:
Ah, I hadn't noticed yet inpainting as menu command. It gets the worm of the apple … ;•)
You can see in the AD document I provided that I didn't have that problem.
-
-
8 minutes ago, NotMyFault said:
you can heal this with help of a levels adjustment, to boost alpha back to 100%.
excellent
-
22 minutes ago, R C-R said:
Except that on my iMac's screen the effect is not there at all, unless I change the view mode to one of the pixel ones.
Wrong. It's there in 'vector view' as well as the 'pixel views'. Your personal failure/inability to see it doesn't mean it's not there.
Two videos of the effect happening were posted by v_kyr. Your own video shows the effect! Your own screenshots show the effect!!
31 minutes ago, R C-R said:I have no idea why it looks different in the forum posts, but as I said, I can only go by what I see on my Mac.
Maybe a leprechaun is manipulating screenshots and videos to upset you.
-
-
2 hours ago, R C-R said:
Yes, of course vector objects are always antialiased on screen (because they are resolution independent & computer screens are not) but that is not what we are talking about here, which is changing the appearance of vector lines on screen by changing the coverage map to either show stair-stepped pixelated edges or smooth ones.
The OP says that 1 pt lines drawn with the Pen tool display as "very pixelated", but the only way I can duplicate that is to switch to one of the pixel view modes, where not only are jagged pixelated edges quite visible but unlike for vector view mode, changing the coverage map has a profound effect on if or how much antialiasing is applied to them.
Exactly the same 'profound effect' is happening in so-called vector view mode, as is proved by your very own screenshots!
I feel like shouting, "Are you blind, man?!"
-
On 10/13/2023 at 9:04 PM, Pixelplucker said:
Much of my work is spot color. If I create anything in Affinity I am unable to export the files out with pantone spot colors. All exports from PDF or EPS are converted to cmyk and pms colors are lost.
I use Corel for separations but despise the softwares instability in newer versions.
Am I missing something here on my file exporting?
Thanks
Your Affinity document is using a Pantone process colour, not a Pantone spot colour. Some of the Pantone palettes contain spot colours, while others contain process colours.
-
-
53 minutes ago, NotMyFault said:
You will never be able to spot this by eye on high DPI displays.
I have to disagree with the never. Far less noticeable than on a 'standard DPI' display, but still detectable at arm's length viewing distance (depending on acuity of vision, of course).
-
8 hours ago, R C-R said:
Doesn't happen for me in V2 -- it is just like the screen captures I posted above.
Your pair of screenshots do show a difference in antialiasing created by changing the Coverage Map. The one with the upward slope in the CM graph has Affinity's standard antialiasing. The one with the horizontal line in the CM graph has no antialiasing and looks jagged.
Without intending offence, I'll remind you that you previously admitted to problems with your vision.
BTW, please post PNG, not JPEG, screenshots in future. JPEG adds artefacts.
-
55 minutes ago, R C-R said:
In the default Vector View Mode at any zoom level there is no antialiasing regardless of how the coverage map is set.
One word:
bullsh!twrong. -
21 minutes ago, Bitarts said:
I just need a small feature to accommodate people who work this way.
In all seriousness, you could easily be waiting a decade or more for the small feature.
-
18 minutes ago, R C-R said:
if it is indeed all vector curves then changing the coverage map of the original should have no effect because vectors are resolution independent
Coverage Map affects the antialiasing of the rendering of vector objects, specifically.
(I think the OP's screenshot shows normal antialiasing, so I don't know why he finds the display to seem distinctly more jagged than it did the day before.)
-
10 hours ago, Bitarts said:
Some of your white fills are HSL (0, 0, 100) while others are RGB (255, 255, 255), and Affinity alway considers fills defined with different colour models to not match.
Your screenshot of Colour panel shows the padlock enabled to the left of HSL. That will cause a conversion from any non-HSL colour definition to HSL to be displayed in the panel. The padlock must be disabled for the true definition of a colour to be shown when an object is subsequently selected.
-
@Bitarts See the attachment I added to my comment before this one.
-
4 hours ago, Bitarts said:
I just tried it in this quick'n'dirty file where disabling edit all layers has no effect?
This happens when I then select an object in a group and then command+a for select all:
There was a communication breakdown. My advice concerned objects inside a Group because you talked about objects inside a group. I didn't realise you were using the word group to refer to a clipping object rather than a Group.
Attached is your document with a very simple change - each of the two sets of windows is now a Group - and you can now use the functionality that I explained earlier.
Replace all elements
in Affinity on Desktop Questions (macOS and Windows)
Posted · Edited by lepr
If you convert just one item to an Image object and then create duplicates of that Image object, you'll have multiple references to the one Image, which can be changed to some other image file that is in your file system.
Alternatively, try the Symbols functionality. You'll find info in the Help, but come back to this thread if you still need assistance after reading that.