Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by sveto

  1. BUG 1: After opening 2 images simultaneously i want to switch back to the other one with CTRL+SHIFT+TAB. Nothing is happening. I have to press the same key combo a second time to get the application to react to my input. ---------------------------------------------------- BUG 2: After opening 10-20 images simultaneously, the last opened image is shown (like expected). Then i hit CTRL+TAB to switch to the next tab (being the last, it should wrap to the first tab automatically). But it switches to the 4th or 5th tab from the left. I get the feeling the tab switching is unpredictable. --------------------------------------------------- Can you guys reproduce these issues?
  2. I usually have to postprocess a bigger amount of images from a job. I open between 20-40 images at once, striving for uniformity, editing, switching between them, saving, and then closing everything. Then i repeat that with the next 20-40 images. I noticed that the loading of the images gets slower each time. On the 3rd, 4rd or 5th batch Photo freezes completely. I have to end the process in task scheduler. Looks like a memory leak. But i'm no programmer, just a photographer. The images i open are just 1300px wide. I shudder to think what will happen if i try this with full size images. My hardware is Intel i7 6700k, RTX 2070 Super graphics card and 16GB RAM that has worked for 3 years without a single hiccup. Nothing is overclocked, and the mainboard is a popular MSI model.
  3. Chris, unfortunately there is no choice to disable parallel processing globally (for opening multiple files). Or is it? And if you advise to disable it when batch processing, why not make it the default? We all know that Affinity still doesn't remember tool and filter settings (i hope this gets adressed in v2.0 ), so it's easy to forget to untick it and freeze the application.
  4. I attached the most recent one (from yesterday when i did the test), i hope it helps. My thoughts about this issue: I have sometimes freezes when i batch process with "parallel processing" enabled. I learned that i need to disable it (i wish Photo would remember my selection!), and the reason is simple: i use a normal hard disk for my files. With parallel processing the app tries to access multiple files at the same time and everything actually gets slower. Parallel processing of files is meant for SSDs, not for HDDs. I suspect this as a culprit for the crashes when opening and closing many files. IMO parallel processing should be an option that the user can disable. That could probably take care of another issue - not keeping the order of the files when opening multiple ones: But this is probably a topic for the request forums. edb019fc-e018-4509-befc-bcba900a1c84.dmp
  5. OK, i did the test. I did 4 batches of ~40 images (1300px wide, with 2-4 adjustment layers each). I simulated my usual workflow, but without any editing (if i edit, i think the issue happens sooner). 1- selecting images in explorer 2- "open" from context menu, waiting for loading and until CPU goes down from 100% 3- going through all images and resetting zoom to 100% because images are shown to fit by default (very bad behavior! just imagine editing icons or similar small stuff!) 4- closing everything down one by one (because there is no "close all" functionality in aPhoto, unfortunately) 5- back to step 1 for the next batch The memory utilization in Task Manager never got above 35-40%. BUT, on the 4th batch the program crashed (closed silently) while loading the images. And to answer your question: Yes, if i close and reopen the program regularly i can prevent those crashes. But that's not a workaround i can accept as someone who uses this software professionally.
  6. Sorry, i saw your reply just today. I'll try out your suggestion and report the results.
  7. Glad that it's taken care of. Thanks!
  8. I made a macro that places a PNG watermark (file from hard disk) onto the image. It worked as long as i kept Photo open. As soon as i restarted the program, the same macro crashes Photo. Any thoughts?
  9. In the batch processing dialog you can choose macros. My question is, and i think it is an important one: Does the macro get applied before or after the resizing?
  10. Thanks for getting back with the official info. I did post already in the bug section. When the program crashed multiple times, a crashpad_handler.exe connected to the internet - i hope it transmitted some relevant data to you about the crashes.
  11. I see what i can do. No promises. I'm on the verge of giving up on Affinity, with all the problems i had recently and the time i lost.
  12. I have a curve adjustment layer and want to move two of the points at the same time. But i can't manage to select both points simultaneously - i tried Shift+Click, CTRL+Click, Alt+Click - nothing works. I can't google this issue, because all i get is vector curves topics. Please help.
  13. Of course i can do that. When i find the amount of time that is needed for: - choosing a proper example so that everyone can understand - searching for the right image in my archive - checking publishing permissions - making an understandable explanation in English, which is not my main or second language [EDIT: this post alone took me 10 minutes to write] - making probably additional graphics of curves that go with the written explanation So, basically, you are asking me to write more or less a short article, because i asked a simple technical question that can be answered by official staff in seconds? Wow.
  14. My example was a theoretical one. In practice my curves a more complicated. It's not that i don't know how to do it. My point is that in Affinity it would cost me double or triple the time compared to Photoshop, because i need to adjust each point separately when i decide to change a broader part of the already edited curve. I thought that stacking curves might be the answer because i can do it faster and keep it editable. What i don't understand is why do i need to explain my workflow in detail when all i ask is a technical question with a probably easy answer from an Affinity employee with inside knowledge. Is this not an official Affinity forum?
  15. Why don't you try it out? You seem like practical person, judging by your posts. How would you compress the highlights but simultaneously keep midtone contrast the same? I'm well aware of that. The question is: Is the result the same between case 1 and case 2? Or is case 2 worse quality because of rounding errors? Case 1: i achieve a certain thing with just one curves layer Case 2: i need to use several curve layers to achieve the same thing
  16. You didn't read my initial two posts, it seems. I quote myself then:
  17. If i could define that i wouldn't be asking. And as well - i wouldn't be asking if the software didn't force me to do that, given that i can't select multiple points in an Af.Photo curve. My question is meant to prevent me from doing harm to my files that i could discover only later. Hell, even normal adjustments are hard to see when the eyes are tired.
  18. How would i know? I'm just a photographer. That's why i'm asking.
  19. Rounding errors? (In the audio world we edit in 32 bit floating point resolution, just to avoid rounding errors.) I don't know how much rounding errors play a role in image processing in 16 bit per channel data. That's why i'm asking.
  20. Ever done adjustments in 8 bit per channel? Ever saw the image degrade? That's what i mean. And probably other things that i can't think of. I guess in 16 bit it is safe enough to stack 2 or 3 curve adjustment layers, but you never know. That's why i'm asking. I appreciate you trying to help, but i'd rather hear some statement from the Affinity staff, because they should know the technical details, right? But they rarely read this forum, or do i have the wrong impression?
  21. Well, i meant things like posterizing or color shifts. Very difficult to detect with the naked eye until (if) you do some serious further processing. Isn't this an official forum? I'd normally expect people from Affinity to help here. Sadly, when it comes to the more technical issues and/or questions, i feel ignored.
  22. It looks like the macros get processed before the resizing. Although i still would appreciate a heads-up from an official source. I lost half an hour testing this, because Af.Photo crashed multiple times when i did the batches. Turns out that the macro that places the logo/watermark crashes the program. But that's a topic for the bugs forum, i guess.
  23. Am i expected to do multiple technical tests to determine if the software can deal with advanced editing? Do you realize that some artifacts could remain invisible until later in the workflow when you can't go back anymore because you are approaching the deadline?
  24. I know that i can stack them. My question was if i'll get rounding errors and/or artifacts when pushing around the same tones multiple times in a row. I always work in 16bit per channel, but maybe it's not advisable to stack different curve adjustment layers on top of each other. I need a clarification, because i'm looking for a workaround for not being able to select multiple points. I had the idea to do my fine adjustments on one curves layer, and then some coarser adjustments on another, etc.

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.