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

nickbatz

Members
  • Posts

    491
  • Joined

  • Last visited

Everything posted by nickbatz

  1. 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.
  2. 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.
  3. 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
  4. 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.
  5. 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.
  6. 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.
  7. 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
  8. 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.
  9. Because my goal in life is to be annoying. Is it a newly added feature? I thought it was just that I was clicking in the wrong place all along.
  10. 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.
  11. 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.
  12. 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.
  13. Techbro incels trying to replace the soul of humanity with algorithmic garbage. Other than that I'm all for it.
  14. 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).
  15. Utter revulsion aside, I just don't understand the point. We already have humans. Minor flaws aside, I think we're pretty remarkable.
  16. 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.
  17. 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.
×
×
  • 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.