Jump to content

Dnn

Members
  • Content count

    5
  • Joined

  • Last visited

Everything posted by Dnn

  1. I found several bugs in Affinity photo that unfortunately make this nice programm impossible to work with. I use the 1.7.2 version for Mac. I use it with OS 10.14.5 Mojave on an iMac with 3,2 Ghz Intel Core i5 with 8 Gb of 1867 Mhz memory. 1. layers stop responding I open one photo in 150 or 300 dpi. Or: I open a compressed picture from an iPhone that only is 245 Kb in size with 1136 x 1078 px. When I add a layer and do noise reduction: this works. But when I add a second layer with clarity or high pass or whatever; the effect stops after a while. Not always; but most of the time. And sometimes (not always) this also causes the first layer stop doing his job. I only use two to four layers by the way. The more you use; the bigger the problems get. Sometimes I can 'solve' this strange bug by changing the sequence of the layers. But most of the time I have to delete the layers and start all over again… Or I have to stop Affinity Photo and start again. It happens with all photo’s. Big or small. Color or black/ white. One of the forum users suggest to add a layer with a pixel to solve the layers from non responding, but this does not help... I had read on the internet by the way that likewise problems already happened two years ago with previous versions. 2. saving bigger photo’s takes a lot of time and sometimes causes AP to freeze and crash Also saving bigger pictures (800 Mb to 1 Gb) takes a lot of time. Sometimes it cost more than 10 minutes. And sometimes this causes Affinity Photo to freeze or crash. 3. memory consuming When using Affinity photo with a (1) larger photo file (up to 1 Gb), the programm is memory and hard disc consuming. It is even impossible to use other programm’s at the same time. Hard (real) Memory consuming by Affinity Photo can be up to 5 Gb (while this test iMac 'only' has 8 Gb). At the same time; Affinity uses the hard disc as a virtual memory cache for up to 2 Gb. That makes 7 Gb and it slows down the whole computer. I realise that adding more memory 16 Gb or 32 Gb might help; but I can not imagine that Affinity photo could not do his job with standard memory of 8 Gb found in many desk and laptops. While rendering or saving images in Affinity; I sometimes even have to force quitte other programm’s since they are not responding anymore because Affinity Photo sucks up all the memory. It sometimes even effects the Apple Finder stop responding. 4. Crashing Last but not least bug: Affinity Photo crashed and freezes several times while testing it in multiple ways. 1.7.1 and 1.7.2 unfortunately are not stable. 5. progress bar idea There is a progress bar for monitoring saving. It would be great to see a progress bar while rendering. Free of cost graphic programm’s like GIMP do have this and it is very handy. This might be a good idea to build in next versions of Affinity photo. Thanks !
  2. Hello Chris ! Thanks for your mail. 1. hope an update for the multiple crashing problems comes soon. 2. Everything is saved locally on the local HD. 3. Affinity photo 1.7.2 responds quicker than Apple Photo 4.0. But editing in Affinity Photo on a normal harddisc @ 7200 RPM and with 'normal' Ram 8 Gb is slow and buggy; comparing with GIMP 2.10 and Pixelmator Pro 1.4.2. We did some additional testing here. This time with the same iMac and OS spec's, but now with a high speed internal SSD and 24 Gb Ram. Responding of AP is much quicker. From this point, I would advise to change minimal system requirements into 16 Gb + an advise of AP that AP will work better with SSD or Fusion Drive when using larger files of +100MB. Also with the SSD and 24 Gb of RAM, AP still sometimes crashes (randomly) while editing/ tuning a layer. Also: layers are (randomly) sometimes not responding and need to be deleted and added again. 4. Already several people have send files and crash reports to AP. I am sure that the AP engineers have been able to simulate the crashes in their R&D lab themselves. Let's see what is cooking in the lab's. 5. :-) Thanks and greetings from your neighbours in The Netherlands.
  3. Is it an idea that users do not have to rename that folder, but that Affinity comes up with an update a.s.a.p. that solves the freezing problem?
  4. One of the errors I found out is definitely the same as you have: freezing during saving. Mostly happen's with larger files. But also with smaller ones. That's why I quoted you. It is a bug. The memory bugs I found out with versions AP 7 in combination with larger picture files, happen' on all computers by the way. Computers with a real hard disc will be slow down more of course than cmptrs with SSD. You can see how much memory and/ or how much virtual memory (on the hard disc) Affinity uses at certain moments, by opening the activity program in OS-X >> applications >> utility programs. It is possible that the 'extensive memory using bug' can cause the freezing during saving. Affinity needs to study and examine this.
  5. Hello, Just wanted to let you know that I also experienced the freezing while saving. A couple of times already. OS-X 10.14.5 with AP 1.7.2. It is a random error. It has nothing to do with a hard disc going to sleep. It might has something to do with the memory consuming of Affinity Photo and the long duration of saving pict's in general by Affinity Photo. See my post of today. Cheers.
×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.