Jump to content
You must now use your email address to sign in [click for more info] ×

sveto

Members
  • Posts

    79
  • Joined

  • Last visited

Posts posted by sveto

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

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

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

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

     

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

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

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

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

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

  11. Sounds like quite the overhead. Strange that this issue is not more widespread. I wonder how other pros (weddings, concerts, events etc) keep their jobs consistent. They probably don't use Affinity, LOL...

    But i've been thinking: for now, i could try to do #3 with all serial shots, and open the rest at once (where the order is not important).

    Thanks for the help.

×
×
  • Create New...

Important Information

Terms of Use | 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.