Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Brush Lag Between Strokes

Comments

14 comments

  • Eric Valk
    For comparison I have a late 2015 27" iMac with 4GHz i7. According to Geekbench my CPU is about 1/3 more powerful than yours, which I wouldn't think makes that much difference because it is usually lightly loaded.

    Your main drive is faster than mine, since I have a fusion drive and you have an SSD.

    I don't see the problem you have.

    One thing you might do is run disk utility and run First Aid the main drive. I have occasionally seen a Mac run very slow when information on the main drive is corrupted.

    One thing worth comparing would be the type and size of the images you are editting. Mine are 16MB and 20MB Panasonic and Olympus RAW files.
    0
  • photo by FA
    I suspect OpenCL codes were either broken or not working with pre 12.0.3 so try to have the latest version.
    Also try to run on a low res mode to see if that helps?
    0
  • Permanently deleted user
    A couple of questions:

    Are you in Auto Mask mode? If so, it's normal for a big pause to happen after the first stroke or 2 while C1 does some sort of computation to set the mask. After that, it should be fluid.

    What are you using for drawing? If one of the new Intuos tablets via a Bluetooth connection, try it with direct USB. I find (and there are many web comments about this) that their Bluetooth connection is a little laggy, although it doesn't bother me at all.

    If you're using another wirelessly connected drawing device, try a direct connected one just to be sure that the problem really is C1 and not the device.
    0
  • Richard Bock
    I have the same issue. When drawing a mask and I lift my pen from the Wacom tablet after the first stroke, there are a couple of seconds where it becomes completely unresponsive. After it starts again there seems to be no lag from that point on (at least on that layer). I don't have auto-masking turned on and my Wacom tablet is plugged in via USB. It's an annoying glitch that breaks up the work flow.
    0
  • RK
    HI,

    @Eric Nepean
    thanks for the comparison. Following your suggestions. I rebooted the whole machine and just ran with C1 and this seemed to reduce the issue.

    Files are from a sony A7R2 so raw file is 85Mb. Maybe the issue.

    @atihayoglu
    I Updated to 12.0.3 with no real effect. The release notes don't mentioning OpenCL issues

    @Nature Isme
    No auto mask selected.

    Wacom tablet with USB connection and Bluetooth apple mouse.

    @NNN634623303328933092
    It would be interesting to know your machine spec.


    Activity monitor shows CPU use climbing to over 400% during.

    I'm not sure where the issue lies. I've tried editing a file with a single adjustment layer with no effect.

    Is There a way to run a new user with just a bare bones system and no plug ins running etc? Any suggestions where I may find a resource for this configuration?

    thanks

    ross
    0
  • Eric Valk
    [quote="NN150632UL1" wrote:

    -----
    Is There a way to run a new user with just a bare bones system and no plug ins running etc? Any suggestions where I may find a resource for this configuration?


    Make another admin account on the Mac, and copy a few images to it.
    To ensure that the copied image files are owned by the new account --> the last copy operation should be done from the new account
    Then run C1, and only C1, from the new account.
    0
  • Permanently deleted user
    Having used CO for several years, I too, have noticed lag in creating and applying masks ins particular.
    0
  • photo by FA
    [quote="NN150632UL1" wrote:
    HI,



    @atihayoglu
    I Updated to 12.0.3 with no real effect. The release notes don't mentioning OpenCL issues

    ross


    Yes I know the release notes does not mention anything about it, but it can be under bug fixes right? Quite few people have reported in early v12 version, there were problems with the adjustment speeds and same people have reported the response time of the software has increased with .3 version. However your issue might be different.
    There are few ways to test if you get support from your GPU, turn on focus mask and try to draw a masker some adjustments, if the focus mask disappears during drawing a mask or making adjustments, that means your OpenCL was working. (as an example with .2, my OpenCL was not working but with .3 it is working). The other way would be to turn on Activity Monitor and see how your GPU is responding during drawing a mask.

    BW,
    Fatih
    0
  • Markus Monnerjahn
    I have the same problem running C1 12.0.3 on a brand-new iMac 5K with i9 CPU and Vega 48 GPU under Mojave 10.14.5 (see specs below), otherwise a really fast machine. 😄

    When drawing masks, no matter if I have the red mask display on (M key) or draw in the adjustments directly, there's a very noticeable lag (I'd say 1/2-1 second) between moving the brush and seeing the effect (or the mask drawn). This is not only true for the first brushstroke, but happening constantly. I'm editing 24MP RAWs with 40GB RAM, preview size is at default 2560px.

    What's strange is that while this machine is nearly 4 times faster than my old MBP when exporting, drawing masks is no faster on the 2019 iMac than on the 2011 MBP (17", i7@2.2GHz). I tried turning GPU acceleration off for "display", and have the impression the process is slightly faster, but still sluggish.

    Set up the machine from scratch, so it shouldn't be a problem of "software interference".

    I'd be happy for any help if that is a problem specific to certain machines/setups. 😊
    0
  • photo by FA
    I believe there is a problem with 4/5K machines, OpenGL and GPU support. Way back when I have had my iMac 5K, PO team has blamed Apple that the GPU they were using is not enough to drive the screen but it’s been few years now and GPU specs have increased significantly yet there is still a problem. So now I think there is an issue with the software itself.
    0
  • Markus Monnerjahn
    [quote="fatihayoglu" wrote:
    I believe there is a problem with 4/5K machines, OpenGL and GPU support. So now I think there is an issue with the software itself.


    I think so too. Did some testing today-when I resize the Capture One window to 1/4 of the screen, I feel the lag is less (but sill there), so it seems to be affected by the screen resolution.

    Another thing that's strange is that my 2011 MBP and 2019 iMac show (in my perception) the same amount of lag, and when I check with Activity Monitor, Capture One uses only 2GB of my 40GB RAM, and neither CPU nor GPU are anywhere near their limit. So I'd think there's some basic thing in their masking algorithm thwarting the process (preventing a faster CPU or GPU having a significant impact), if that makes sense. Ok, to be fair, the iMac has approx. 6x the pixels of the 17" MBP. But the Vega 48 is on another planet from the MBP's Radeon 6750M, too.

    I think I'll open a service case with them to address the issue... hopefully they will improve on this in the future. I just switched over from Lightroom and love C1's output and especially the color editor and masking functionality, but this severe lag when trying to draw in adjustments is a major annoyance in the otherwise nice and smooth workflow.
    0
  • photo by FA
    To start with, keep the review size at max since it should match to your screen size or the next highest resolution. You can measure the picture area on your screen, depends on how you use CO. I use toolbar on the lest and browser on the right, viewer in the middle which give me a screen area nearly 3500 pixels so I keep my previews at the option below max.

    Another way to see if you get some performance increase is running the software on low res mode, which you can enable it by right clicking the software icon in applications folder and enabling low res mode.
    0
  • Markus Monnerjahn
    [quote="fatihayoglu" wrote:
    To start with, keep the review size at max since it should match to your screen size or the next highest resolution.


    I tried that, didn't reduce the lag by much, sadly.

    What would also help if they added a feature that would let you zoom out more than "to fit". This way, you could reduce the viewer size conveniently with the mouse wheel when wanting to draw in adjustments, without having to reduce the window size.
    0
  • SFA
    [quote="Bohemien" wrote:
    [quote="fatihayoglu" wrote:
    To start with, keep the review size at max since it should match to your screen size or the next highest resolution.


    I tried that, didn't reduce the lag by much, sadly.

    What would also help if they added a feature that would let you zoom out more than "to fit". This way, you could reduce the viewer size conveniently with the mouse wheel when wanting to draw in adjustments, without having to reduce the window size.


    Set up a recipe for a small output size - say 600 pixels max on widest side.

    Turn on Recipe Proofing.

    You will have a small image to work with.

    Lag, compared to the same image full screen or 100% seems to be reduced a little but my system is not the fatest for this sort of activity. That said I find that after the initial start of the mask drawing and once te mask is in screen (assuming one is working with it visible) the painting action has less lag. (This the degree of lag rarely aver concerns me so I may not be representative in this discussion.)

    100% settings for Hardness, Flow and Opacity may be a little faster but not so much I would bet on it.

    For large areas or regular straight edges the line drawing assists can speed things up a lot of course. That might be useful for some people and of little use to others.

    Change to a different Recipe with a different size setting to work with more detail or turn off Recipe Proofing to go back the the 'normal' image.

    If using a catalogue and Previews which are less than the original file size it would be interesting to make the original file unavailable and therefore work just with the preview for editing to see if that makes a noticeable difference Assuming that layers are functional in that situation). In theory there should a lot less data to manipulate so one might expect better response but not knowing what the software has to try to do to work as it does I guess that is just speculation.


    Grant
    0

Post is closed for comments.