nickbatz

Okay, this is now starting to become a real issue. Right now I'm going to have to force quit and lose some work that took me a while, which is somewhat less than thrilling. Maybe the screenshot below from Activity Monitor will offer some insight. All I did was tell it to save, and several minutes later it's still showing the beachball. Again: Mac Studio Max, 64GB, 32-core GPU, Affinity Photo 2.0.3, macOS Ventura 13.1 Why would any program need to use 435.54 GB of virtual memory?

I'm not in Affinity Photo this second, but I think you're just saying that it doesn't work over alpha channel areas?

Also, it has no problems loading files into Affinity Photo ridiculously fast. And the program starts up (from the internal storage) in two seconds. And I mean that literally - two seconds. It's really great!

I don't know, because I don't have the documents on the internal SSD. But I use the external drive for all kinds of things, including very demanding music applications (specifically streaming large sample libraries, and you'd hear clicks and pops if there were any issues doing that), so I'm absolutely confident there's nothing wrong with the drive or the connection.

The Affinity files are on an external SSD - again, a 4TB m.2 one in a Thunderbolt enclosure that does 2500 MB/S read and write. Yes, I'm guessing they are linked to recovery files on the internal storage. And that shouldn't matter, even if the external SSD were SATA 2 (which has about 10% the transfer rate). Using external drives is a totally normal thing to do. It's going to be hard to troubleshoot, because it doesn't do it every time. Just now it quit right away, for example. For what it's worth, Saving As the 650MB file I have open right now (before quitting) takes ten seconds. The beachball on quit is much longer than that - long enough to make me force-quit the program.

Thanks. This happened a couple of days ago after I closed a file I'd opened by mistake, i.e. I made no changes and didn't Save or Save As. Or maybe I just quit, but either way I didn't save anything. And it's happened since, but I forget what the circumstances were. It may well be a Ventura-related Affinity glitch. I don't have the same issue with other programs on this machine, including Logic Pro and DaVinci Resolve (the other two programs I use that can create large files). By the way, Affinity's tech support nailed a similar issue I was having when copy/pasting layers with their first question - I had forgotten about the clipboard manager in BetterTouchTool, that otherwise magnificent utility. But that's still disabled for Affinity Photo 2, so it's not that this time.

Thanks. And yes, of course you're right about the clipboard. I wasn't thinking. The recovery file must be the answer, and I agree that it should be fast on my machine, between the computer horsepower and the storage. And presumably the recovery files are saved on the internal storage, which is ridiculously fast. But my external m.2 drive with my Affinity files is in a Thunderbolt enclosure that's still very fast, even though it benchmarks at a little under half the speed of the ridiculously expensive internal storage. So I think there's an issue. Is it just me?

I mean exactly what I asked: whether it's saved for recall with a file. And you say no. I didn't think it was. Thanks. And since I just opened a file and then closed it, that means Bruce's theory is probably not what's happening, at least it's not the only thing happening - which surprises me, because I was having problems This seems like a glitch. I'll narrow down the problem and then file a support ticket.

Question: is the clipboard content saved with a file? I just opened up a picture, closed it because it was the wrong on, and got the spinning ball. it could also just be that each layer is saved. Like all my pictures, this one has a lot of them.

That sounds totally plausible. Thanks. That's not to say that it's normal for a clipboard to have this effect on a program, but it does seem like a very likely culprit. I do copy and paste a lot of very large chunks.

In general the program is responsive on this machine. It's clearly confused when I quit - but not always, just some of the time.

Mac Studio Max, 64GB, 32-core GPU, Affinity Photo 2.0.3, macOS Ventura 13.1 It often hangs for a good 20 seconds on quit, but only when I've closed a large file (as my files tend to be). Come to think of it, this may happen when I just close the file too, I forget. But it's only when I have a file open, i.e. if I just open the program and quit right away it doesn't do that. Is it saving a recovery file? Even that seems slow, considering the speed of the storage on these machines. Not a show-stopper, I just want to see whether there's anything I can do to make the program happier.

A mask! That's the answer. Thanks so much. There's still so much I don't know about this program, even after using it a lot for a year.

I *think* what's going on here is that I applied this HSL adjustment to a selection of the pixel layer below it rather than the whole thing. What did I do here? I sort of like the effect, but I'd want to do a lot of tweaking to the selection it's being applied to. This is just a fragment of the picture. The top is what I'm asking about, below is what it looks like without the HSL adjustment to half the picture. TIA

Well, I can only repeat what I posted already. Nothing wrong with monitor calibration, but that's talking about what accent color to paint a dining room wall in a house that has no plaster on the walls.

And to put a finer point on it, my sense is that issues like the printer simply not being able to produce a particular color you feed it dwarf monitor calibration. (The Pro-1000 has 11 colors, and it doesn't produce some shades of blue, it turns some maroon shades brown, etc.) But there's also an angry mob of printing nerds gathered outside my office with pitchforks, so don't take anything I say as gospel. I've only been serious about printing for about a year. Put another way, I'm confident that Robert's issues are much more fundamental.

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.

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.

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

Interesting. Thanks.

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.

I’m more the both type, including gestures + keyboard modifiers.

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.

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.