Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by momokoo

  1. I had a similar issue with Affinity Photo (without crashes), it was maxing CPU usage when opening the export dialog or rather whenever it had to recalculate the estimated file size. Most notably my mouse froze too and any music stopped playing. That problem started with one of the 1.6 betas and was still present in the release version. Now it seems I somehow got it fixed by just once opening the preference dialog (and stepping into the performance settings without changing anything). At least I can't reproduce the problem anymore. It also fixed the same freezes I had when merging layers or doing refine selection. Not sue if that makes any sense (maybe it forgot to use RAM?) but thought I might share this just in case it helps.
  2. Just a quick idea: merge visible, copy that layer and go to "File" -> "New from clipboard" Now add the soft proof layer there and once done drag the tab out of the Affinity Photo window. That way you can compare them, not with a slider but maybe better than nothing. On another note: Great videos James. Always interesting to watch. I just wonder how to get so creative to do stuff like the equations with lerp and such and having the result still look good. Perhaps some deeper color knowledge is of use in such cases.
  3. Yeah sorry for the lack of contrast, the photo scan I first encountered it with exceeds the upload limit and I'm currently not physically anywhere near the scanner to put something on it. But I'm glad you guys can reproduce it. The fact that it worked in the previous version and now doesn't made me wonder if that's a problem on my side. Perhaps not a top priority feature to support scan raws but since it was working before I hope it won't be too difficult to get it working again, it's nice to have that option sometimes.
  4. This should work, had to zip it for the forum to allow the attachment. It's just the dusty white cover of my flatbed scanner. raw000388rx.zip
  5. In the new stable release (, Affinity Photo opens the preview miniature image embedded into the DNG file from VueScan instead of the actual "raw" image. In the previous version it didn't do that. And yes the actual scan is bigger than what AP gives me (it works in RawTherapee for example) besides it doesn't go into the develop persona anymore to begin with. I didn't change my VueScan setting either but I updated it trying to fix the issue but it persists also with a new VueScan version.
  6. I would say it's not a limitation but intentional so by design. If you got beyond 100% of an image you will naturally start to see pixels, that's exactly what the file looks like at this zoom level. Without pixels it might look more pleasant but what if you actually want to change those pixels? You would have a problem if Affinity Photo starts to blur at some zoom level. I think the only real way to zoom without (or less) pixelation is to resize, which adds more pixels to your image. PhotoDirector and MS Photos most likely either blur or interpolate the image on the fly (like a resize ) if you don't see pixels as clearly.
  7. I've recently come across a very rare, hard to reproduce bug in Affinity Photo ( There is a chance for the inpainting brush's red selection to remain on the layer without doing the inpainting's healing magic. So how did this happen: I was working remotely on the PC Affinity Photo is on using AnyDesk. While I was using the inpainting brush to remove black dots on that document AnyDesk crashed and after reconnecting the red line was still there (much longer and bigger than attached in the picture I correct that mostly). Technically speaking what I think probably happened is that Affinity Photo was expecting a mouse press release event to fire to finish the task but that never happened because I wasn't connected to the PC anymore. So maybe it can be reproduced by disconnecting the mouse while using the inpainting, my arms just aren't long enough to unplug the cable while keeping the button pressed. To fix this maybe APh can also do it's magic when the mouse is pressed again in case there is still some inpainting waiting to be done. PS: As far as I remember I couldn't "undo" to get rid of the red because obviously the step wasn't officially done yet thus not logged in the history
  8. I've also been working on the first example. The result attached. 1. A level adjustments layer was used to turn it almost black and white, leaving just some color for the red stamp. 2. Another used to bring back some contrast (darken). 3. Now I more or less just used inpainting, blemish removal and healing brush. 4. A high frequency layer in combination with dodge brush (set to highlights) not only adds some more contrast and sharpens the document but also helps removing yellow-ish parts around text and the border which would be a pain to remove with a very small brush 5. That little border chain piece at the bottom had so much detail using the cloning brush didn't look good so I just copied the entire thing (select, copy, paste). It's also a rather sloppy job a couple black dots are left and I only just corrected the border on the right because the rest is just cloning and painting. Originally I added the high frequency trying to bring back in some texture of the paper but I didn't like that so I used it in a different way. The version attached does not show the low frequency layer. The red line at the top border is the inpainting brush's red, it's a very rare bug in APh.
  9. Hi, if you want to continue using AP you could try to lower the the maximum RAM usage and see if that helps. It might slow down AP and increase disk usage however. You can find the setting within the preference menu in the performance section. Write down the value before you change it in case you want to revert (it's most likely set to 4GB in MB though). Your system could also be overheating (maybe as a side effect when moving lots of data from memory to disk and back while also processing data with CPU). Affinity Photo itself works fine, I hope you can get it to work. It seems to need some optimization for laptops and low ram situations though.
  10. Ich befürchte genau das tut AP. Wie bei der Beta prüft es beim Start ob es eine neue Version gibt. Eine Option das zu deaktivieren wäre gut, aber ich persönlich kann auch ohne leben (es fragt nur welche Version die neuste ist und sendet sonst erst mal keine Information). Ich denke die Thematik ist für Serif noch neu, da bei Mac die Updates über den App store geprüft werden. An der Stelle braucht die Windows-Version also eine Sonderlösung. @Ashkos: prüf eventuell mal die "Max. RAM Nutzung" bei den Einstellungen im "Performance" Menüpunkt. Es könnte helfen den Wert da manuell zu reduzieren, ein bisschen. Es wird dort vermutlich der gesamte RAM vom Laptop (in MB) stehen, z.B. 8000 MB also 8 GB.
  11. Hallo! Das Problem ist wohl schon bekannt (Thread auf Englisch) und es wird daran gearbeitet es zu beheben. Ich konnte die Abstürze bei mir auch nachvollziehen. Ich bin mir sicher mit dem nächsten Update sind viele Fehler behoben - die Beta- bzw. Testphase war einfach zu kurz.
  12. Hi, let me rephrase your problem because it might not be clear to everyone what you mean (although taking a good look on your screenshot reveals the issue): The bug described is a wrong translation for the counter-clockwise rotation in the German language. The second rotation menu entry should be "90° gegen den Uhrzeigersinn drehen" but as shown on the screenshot it's the same as turning clockwise.
  13. I'm sorry if it has been reported already, it's very likely I think... When I add a level adjustment layer and change the color format from RGB to let's say LAB and do my settings it's all good. But when I double click the layer to re-open the settings it remembers the color format itself, LAB, but it only ever gives me the secondary/sub options of of the (standard) RGB format (Master, Red, Green, Blue, Alpha). Now since I have to change to something non-LAB to LAB to get back the secondary options it forgets the previous settings as it is designed (which I like if this bug didn't exist). I know in terms of programming it's only a minor flaw but the impact is kind of big when you work with non RGB adjustment layers and have to find that perfect value once again.
  14. I'm very happy about the release of Affinity Photo for Windows. It replaces GIMP in my case. The tutorial videos are also helpful and interesting. I've found a few ways to improve the quality of my scanned images even though it's primarily made for photographs. TWAIN support would be nice to have and save me some time or one step because right now I scan via VueScan and open the file in AP but I do not really need the raw result from VueScan saved on my disk. I could just as well save it with AP when needed if it had direct TWAIN "import". But it's also not a big issue to not have that feature. The dust & scratches filter is sadly of no use for me because it removes too many details but I'm happy to have the set of healing brush tools. All together they help me get my tasks done faster than before. Did you check if the correct layer was selected? Having a wrong one selected happened to me a few times (e.g. an adjustment layer).
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.