Jump to content

sveto

Members
  • Content count

    61
  • Joined

  • Last visited

Posts 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. 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.


  3. 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


  4. 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.


  5. 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.


  6. 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.


  7. My example was a theoretical one. In practice my curves a more complicated. :)

    1 hour ago, walt.farrell said:

    I don't really see the problem with doing that

    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?


  8. 5 hours ago, R C-R said:

    I do not understand what you mean about destroying the relation between the points.

    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?

     

    5 hours ago, R C-R said:

    all adjustment layers are non-destructive

    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


  9. 25 minutes ago, R C-R said:

    I don't understand why the inability to select more than one point on the curve at a time forces you to use stacked Curve Adjustments layers. What is it that you can't do, even if you have to adjust one point at a time?

    You didn't read my initial two posts, it seems.

    I quote myself then:

    Quote

    It's part of my workflow. I often establish a good combination of contrasts for different parts of the curve that i like and then want to raise or lower a broader part of the curve without destroying the relation between the points.

     


  10. 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?


  11. 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.


  12. Example: I have a logo/watermark that is intended for 1300px wide images. If i want to batch resize the original images (4200px) and apply the logo/watermark, it should resize first.

    Actually, with this pretty clear example, i could try it out. But it wouldn't hurt to point out such things in the manual - some processing is best applied on the full size image.

×

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.