Paul Mudditt

No. That is common with most software suppliers who already have a Mac app available to not allow their mobile apps to work on the Mac On the Mac you can download a free trial for testing purposed, hope this helps. https://affinity.serif.com/en-gb/photo/

What type of HD are you using and is it powered externally?

Have you tried rebooting your iPad with a Forced Restart?

Try using the Smart Selection brush, be careful to adjust size of brush, pay attention to the add and subtract bottom left of context tool bar which allows you to correct errors in selection easily. Plus as I show, you don’t have to do it all in one go you can do it in stages, just pay attention to which layer you have selected as you do it. IMG_0170.MP4

Ideally we could do with somebody with the same MacBook as you but with the 16 GB RAM to try your files to see what time they get.

Affinity is already optimised with V1.8.6 for the M1, that was why Serif appeared at the Apple M1 product launch. Versions prior to V1.8.6 were not optimised for M1, might try and install that version to see how much it slows down. I would be interested in what other apps have been installed, ant-virus perhaps or I have seen a few people who reported slow performance with Big Sur benefit from uninstalling Keystone which gets installed rather secretly by Chrome. See Chromeisbad.com for more details on why you should never install Chrome on a Mac.

5-10 seconds more for automatic ghost removal. Screen_Recording_2021-03-06_at_22_54_17.mov

@the_tux 33 Seconds Note: I do not have Chrome the stealer installed by the way. Screen_Recording_2021-03-06_at_22_19_01.mov

Install iCloud on your PC, create a folder structure in ICloud Drive pick up on your iPad and vice versa. Just always remember to save and close your files on PC and on iPad out side of the app before you open on other device. Don’t leave files open in tabs on PC or on home page on iPad otherwise you will have problems.

So are you able to upload your images to be used as a benchmark so the devs can check on any further optimisation? Maybe they are too large for the forums.

Like the benchmark tool built into V1.9? Mac, PC iPad and M1 results here.

It might be worth uploading your images here for others to check on their M1 systems if you like. A quick test of the Workbook beach 8 image HDR stack was 14 seconds on my M1 Mac mini. EDIT: 20 seconds including automatic ghost removal I used these workbook images :- https://affin.co/hdr

^X will do cut which is the same as delete if you don't paste. Otherwise I just use the waste paper bins in the layers studio or bottom left in AD.

Think it is because photo is the most computationally intensive app out of the trio.

Ok, I bought the 16GB 1TB model and paid more but performance wise this is the same machine and will be just as quick for Affinity and very usable.

Available BEFORE you open any documents as mentioned above. Mac and PC and iPad.

Are you using V1.9?

M1 is great, for £699 (EDIT: for the radgie gadgie) you get a great machine at a fraction of the cost of an equivalent PC. Don't think that's ever been said about a MAC before! I only keep the PC for COD.

Yes I agree, I was surprised that my NVIDIA screen recorder could not cope and slowed Affinity right down.

I created the Metal compute test (attached) that James demonstrated, here is a recording of performance on my I5 and it isn't too far behind my M1. How do you have your performance parameters set up? EDIT: I could not screen record on PC using the NVIDIA game recorder as performance slowed dramatically so used my iPhone. M1_Screen_Recording_2021-02-27_at_08_59_08.mov PC_Intel_I5_7400_IMG_2320.MOV metal compute test.afphoto

Your results are much better than my PC version Intel I5-7400 32GB + GTX 1650. But my PC works well. Also here is my M1 for comparison and why I prefer that.

Did you try running the benchmark tool under the Help menu, might be worth taking a screen shot after running and posting it here.

I have a problem here too but positive it is nothing whatsoever to do with Affinity and entirely to do with Big Sur. I can't open my scanner from System Preferences -> Printers & Scanners -> Scan -> Open Scanner, however the scanner opens ok when I uses the built on macOS -> Image Capture. These are both built in macOS features, might be worth others checking whether this works as well or not.

Yes agreed, looks like the conflict between INTERNAL build numbers and PUBLIC versions numbers has slipped through the release verification stages on Designer. Photo looks to have done things the correct industry standard way with internal builds semi hidden in the fourth numerical field (225), not displayed on publicity etc. When you have multiple teams working on different but similar products I have seen these same things happen before in industry, once started on a certain path it can be very difficult for a team to change tack as all internal paperwork quality control documents can get messed up easily. I feel their pain.

Hi Chris, now it has started working on the RC1 beta, put it down as finger problems on my part I guess.