nickbatz
-
Posts
491 -
Joined
-
Last visited
Posts posted by nickbatz
-
-
There are a lot of potential causes for lousy prints, and you're talking about color spaces rather than resolution. Is the color the problem?
One issue could be that you're using the Mac system print driver, which is at best just okay. The installation details are going to be different for your Epson printer than for a Canon one, but you need to select the right ICC profile for the printer and paper you're using to get the right colors.
That's in any case, whether you use the Mac driver or not. And that leads to the next suggestion: download a trial of Binarten Qimage One and see whether that improves the quality.
If the problem is low resolution, probably the first thing to check is the DPI inside Affinity Photo: Document->Resize Document, then set it to 300 DPI. I've been using the Bicubic resampling algorithm.
Just a few things off the top of my head.
-
5 hours ago, - S - said:
Your "white" is set to 0% opacity in the Colour panel. If you change it to 100% opacity, it will then show as 55% grey (or whatever the slider is set to).Duh. Thanks!
It's always something simple...
-
I can't figure out whether this is a glitch or something I'm missing. Probably the latter, but as you can see, it makes no difference whether I've painted the maskl with white or black on this mask.
(This may have been a bad spot to show as an example, but what's underneath really is different, and the fact that the thumbnails show alpha stuff to the right is irrelevant - this is the behavior I'm getting everywhere on the picture.)
Mac Studio, macOS Ventura 13.1, AP 2.0.3
TIA
-
-
What's this about? Did I hit some funny things on the keyboard by mistake?
It feels like it wants to record a macro maybe?
I did give it permission, but of course that's easy to reverse.
TIA
Mac Studio, Ventura 13.1, Affinity Photo 2.0.3.

-
35 minutes ago, loukash said:
Looks similar to KM with more focus on gestures as trigger.
I'm more the "keyboard shortcuts type"…
I’m more the both type, including gestures + keyboard modifiers.
-
1 hour ago, loukash said:
I just realized that long time ago I have excluded Affinity v1 in Keyboard Maestro as well, but not Affinity v2 yet. I didn't even notice any slowdowns with v2. But then again, I'm not yet using v2 for production either, only for "toying" so far…
To be clear, it's only the clipboard manager feature in BetterTouchTool that needs to be turned off for Affinity Photo. That's what I'd forgotten about - I use BTT for all kinds of gesture and keyboard shortcuts all day long (although not in AP, but that may change). It's brilliant.
-
1 hour ago, loukash said:
Fair enough.
Personally, I'm using a clipboard cache (via Keyboard Maestro), so I can always go dozens of clipboards back to reuse content that may be days or even weeks old. That doesn't always work with proprietary content like Affinity objects though.Yes, I was having drastic slowdowns copy/pasting on my new Mac Studio. Affinity’s very impressive tech support person nailed the problem with his first question.
it turned out that I’d forgotten about BetterTouchTool’s clipboard manager. Disabling that feature for Affinity Photo was all it took to solve the problem.
-
Am I right that the only way to paste picture onto a pixel layer in another picture is copy/paste?
You can't open a second picture in a tab and drag it over, right?
This is one variation of something I do all the time - never mind that I'm a walking edge case.
TIA
-
On 12/12/2019 at 6:07 AM, Chosen Idea said:
There should be a keyboard shortcut for everything.
This is three years later, and of course it's a matter of personal preference... but is this really the kind of operation you perform often enough to warrant assigning a keystroke to it?
I'm not trolling, I'm just surprised that this would be so important to anyone.
-
Just now, Pšenda said:
So why are you creating another thread with an identical topic?
Because my goal in life is to be annoying.
Just now, Pšenda said:How could anyone point this out when it's a newly added feature?
Is it a newly added feature? I thought it was just that I was clicking in the wrong place all along.
-
12 hours ago, Ron P. said:
Right-Click on the Layer Text to get the full menu, having Merge Visible.
THANK YOU!
I had a whole thread on this and no one pointed that out.
See? This is why no one should pay attention to anything I say.
-
You still have to create a useless pixel layer to merge visible if the top layer is an adjustment.
This is worse than the Devil!
Okay, not quite, but still, I vote for it to be fixed next update.
-
For what it's worth, Edit With [Affinity Photo 1 or 2] works perfectly on macOS Monterey and Ventura on a Mac Studio.
More than that, it opens in a couple of seconds.
It didn't work consistently on my previous machine, a 5,1 Mac Pro running Mojave. Also, it took about 25 seconds for Affinity Photo itself to open off a standard SSD on that machine - vs. literally two on the Mac Studio.
-
Techbro incels trying to replace the soul of humanity with algorithmic garbage.
Other than that I'm all for it.
- Alfred and JakeStaines
-
1
-
1
-
21 hours ago, drstreit said:
Better concentrate on the fact that everybody WILL have access to such tools, and they WILL create and modify images without any technical skills needed.
My answer is that no machine could possibly do what I do.
-
37 minutes ago, dcr said:
The use of AI to create (as opposed to manipulate) images is intriguing, but until the rights issues are actually sorted out,
Similarly, if I need an image of a cup of coffee, and cannot create it myself, I can hire someone to do it or license an image from a stock image site.
The copyright issues will need sorting out, but to me the issue is using machines to create "art."
Why do people have a need for artistic expression in the first place?
But as to copyright... well, I have to give you credit for using coffee as an analogy rather than cars.
Really, how are you going to calculate royalty payments when these services have every image on the Internet in their databases? With prescription drugs you can criticize the whole concept of copyrights in general, i.e. it doesn't make a whole lot of sense for sick people to finance drug development. But IP is quite different from prescription drugs (and coffee).
-
3 minutes ago, debraspicher said:
Well, they already pushed the envelope by introducing a fee to receive program updates for a version people already bought... they need less controversy not more
(I'm not up on Clip Studio, just snorting at AI "art.")
-
-
2 hours ago, drstreit said:
Must read article: https://www.marktechpost.com/2022/11/29/artificial-intelligence-ai-researchers-at-uc-berkeley-propose-a-method-to-edit-images-from-human-instructions/
And again: The current models are developed less than 2 years, so 3xpect much more to come.
And to Serif: Would it not be great to integrate someting like that? Its all open source, so expect that eceryth8ng that has an SDK will have it implemented by enthusiasts…
Utter revulsion aside, I just don't understand the point.
We already have humans. Minor flaws aside, I think we're pretty remarkable.
-
31 minutes ago, Pšenda said:
The context menu is simply not supposed to offer all the commands, the list of which would be completely confusing, but only the selected commands for the given item and situation (are there other layers selected?).
I'm sorry, the Monty Python Argument Clinic is down the hall.
-
Well, in the example I started this post with there's no nesting - it's just a brightness/contrast adjustment applying to everything beneath it.
I usually use nested adjustments as well, but this particular one was global.
At least I'm pretty sure it was.
-
1 hour ago, Pšenda said:
I don't think it's a bug, on the contrary - the context menu has to respond to the situation and the item for which it's invoked (that's why it's also called a context menu). In the context menu of the Adjustments layer, the Merge command has nothing to do. If you still want to execute it - it is in the standard place for these commands, i.e. in the Layer layer.
It's great that Affinity has started using the context menu in a proper/contextual way. For example, if you select two or more layers, Merge Selected is added to the context menu, which version 1 did not do. Great, that should work.
P.S. Adding Merge Selected to the context menu is proof that Serif listens to users' requests and comments. Thanks.
Merge Selected is cool.
Merge Visible should merge what's visible, no? I don't think it's a bug, but this behavior does create an extra step - a very small one, but nonetheless an extra step. If there's a reason for it (which is how I framed my post) then I'm fine with being wrong, but I don't see one.
And if there isn't one, frankly I find the justification that there's some kind of "context to respond to" rather contorted.
I mean, I too am a huge fan of Affinity Photo and don't want to nitpick over minor details, but in this example I added an adjustment and was ready to merge what I saw and liked. End of story; I usually do that to consolidate my work so I can turn off unnecessary layers below it, or sometimes to create a compound raster image that I can cut/paste from.
Exactly what trouble is avoided by either selecting a pixel layer or adding a blank one?
That's a rhetorical question.
-
1 minute ago, R C-R said:
Try nesting the adjustment layer in V1 & see what you get.




Print quality less than Display
in Affinity on Desktop Questions (macOS and Windows)
Posted
I guess, but my garden variety Samsung monitor with the plebeian stock profile and the output of my Canon Pro-1000 (using the ICC profiles for the two different fine art papers I use) are as closely matched as you're going to get.
That could be dumb luck, and I'm certainly not snorting at the concept. But my sense is that in this "why do my prints look lousy" case it would be shooting flies with an anti-aircraft gun.