unitizer

Uploaded and thank you for the help!

I am having this same issue, an orthomosaic that is very large and Affinity cannot open it. Is there a solution? I am able to open it in PS Elements so I think the file is OK.

No to let anyone off the hook but I have not noticed the loss of auto-brightness. I actually like having brightness be manual as I want to know exactly where it is when manipulating images.

Turning off auto-brightness seems to have cleared it up for me as well. Thank you!

By "re-enabling Metal" you mean uncheck and then recheck that box? And the automatic brightness should be kept off permanently? I made these changes and will report back if they help with the spinning ball.

OK so we are blaming the OS, is that I should read out of this thread? Is there something else I need to do to make this an actual bug report?

I don' really have any specific workflows. I tend to use AP for editing collages, usually an image that is 4k x 3k roughly which has several images that I have copied, pasted and scaled from other JPEGs. I add some text and then export a low- and high-res JPEG. It's very basic, that is why this is strange. I can get the ball at file open/close or during operations in AP. I don't have a predictable/repeatable recipe. I never had the ball on my Intel machine, for the exact same work.

That iMac is not an M1 machine though. I'm asking if the M1 native version of AP is somehow slow.

I'm getting lots of spinning balls using Affinity Photo 1.10.5 on Monterey. Trying to figure out if this is an M1 issue or what. I'm not doing anything heavy so seeing any lag is surprising. Just wondering if this is normal, if others are seeing this as well.

This is such a trivial fix that it is bizarre it has not been made yet. I'm starting to look at Affinity more and more like Adobe and that is not good. Please fix this.

Thank you that mostly works. No more sliding off the snap, but it can snap at the midpoint of the grid. I must have a division in there someplace. This is way better though.

I have a grid that is the exact size of some imported images that I then want to arrange in that grid. I set-up snap to do this, and it mostly works, but it is able to slide off the snap sometimes. Is there a "snap only to the grid" setting? There are so many options but this seems like the most basic use of snap-to-grid, I'm not sure why it is not the default.

In that case I don't understand why there is a "Develop" step. All that step does is create an AFPHOTO file based on the CR2 -- what else would a user be doing when they open the CR2? I mean at least ACR has a button to save as a JPEG, skipping the larger PS altogether. ACR is really a standalone application if all one is doing is adjusting basic RAW image data like exposure, WB etc.

OK so I am definitely wrong about what "Develop" does. It sound like rather than baking the settings created in the initial opening of the CR2, it instead expands the source file fully into an AFPHOTO format. I guess there is a plus and a minus to that. The minus I have already covered, but the plus would be that the resulting file would have full latitude / depth for all further processing. My understanding in PS was that once "Open" was pressed, the full latitude of the RAW file was lost, in fact that is why only certain operations occur prior to "Open" (or Develop). I'm thinking now that the pre - Open/Develop changes are only those that are encapsulated non-destructively in the CR2 file. I will say that in my experience, operations done post-Open in PS are not nearly as detailed as those done pre-Open in ACR. Even comparing something simple like exposure in ACR versus an exposure layer in PS, they don't behave the same. I have not used RAW in Affinity enough to say if the same is true (obviously). Thank you!

Thank you, I'm familiar with RAW in general though. I've been shooting Canon RAW for years and also owned a RED camera. Maybe I am incorrect in thinking that the Affinity "Develop" step is supposed to mimic the "Open" step in Adobe's Adobe Camera Raw (ACR). With ACR, the adjustable parameters in the RAW file get baked into a PS file that can then be further edited, all when you press "Open". The resulting PS file size though is nowhere close to 7x, in fact IIRC it is roughly the same size or smaller. That makes sense -- once you bake the RAW you do not need the massive amount of data, and if you do it still resides in the original RAW/CR2 file. It is hard for me to imagine any instance where having such a massive file -- should I repeat it, it's 150MB -- would be useful. Something is just not right here. The document you suggest is not clear on what should be expected in a Develop step. The solution is pretty easy I guess. Bake the RAW using Develop, then export to an intermediate format, like a juicy PNG or JPEG. Then bring it back into Affinity for further processing. Seems silly but the file size is just not negotiable for me.