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. ⚠️

Slow down

Comments

15 comments

  • mstauss
    From my experience (v3.4 upward) this has always been an issue with CO. Lag issues usually start to occur when the image count reaches over 100. Try keeping your capture count below or around 100 and you should not experience this issue. Unfortunately this issue is an old one and still has not been fixed. Hope this helps.
    Cheers,
    Matt
    0
  • SFA
    [quote="Photocor" wrote:
    Dears,
    I work with Session.
    I noticed that if I have a lot of photos in the folder (> 500), there is a delay in the local adjusment between what I wish to draw and what is displayed on the screen. This does not exist if a the folder of the session has only one hundred photos.

    Do you meet this?

    Regards


    You mention Local Adjustment. Do you mean that this only becomes a problem when you are using local adjustment layers?


    Grant
    0
  • Photocor
    [quote="SFA" wrote:


    You mention Local Adjustment. Do you mean that this only becomes a problem when you are using local adjustment layers?
    Grant

    That's it.
    Regards
    0
  • SFA
    [quote="Photocor" wrote:
    [quote="SFA" wrote:


    You mention Local Adjustment. Do you mean that this only becomes a problem when you are using local adjustment layers?
    Grant

    That's it.
    Regards


    Well, using version 6 at 32bit on my old and not very powerful machines painting a mask could often be a rather erratic process and not a very good experience.

    With a much more powerful notebook and of course 64bit Windows running V7.1.6 (I have not yet moved to 7.2) things are fine using sessions even with over a thousand files in a folder. Of course it probably helps to have a large SSD.

    I assume you do not all of the files selected at the same time.

    Masks have their own data files but I can't think of any obvious reason for that to slow things down.

    I notice a slight slow down sometimes if I have more than 5 or 6 local adjustment layers especially if they are defined to be doing something quite process intensive when working at, say, 100%. But I would expect that.

    What sort of system specification are you working with?



    Grant
    0
  • Christian Gruner
    [quote="mstauss" wrote:
    From my experience (v3.4 upward) this has always been an issue with CO. Lag issues usually start to occur when the image count reaches over 100. Try keeping your capture count below or around 100 and you should not experience this issue. Unfortunately this issue is an old one and still has not been fixed. Hope this helps.
    Cheers,
    Matt


    I have to strongly disagree here. CO7 can handle hundreds and even thousands of images in a collection with no major performance-reduction. Of course the collection load times increase proportionally with the collection size, but once loaded, performance impact due to sheer number of images is limited.

    Working with a lot LA and masks can however affect performance, especially if the machine has little RAM and masks ares used a lot.
    0
  • mstauss
    Can you please list your machine specs? It would be helpful to have something to base your machine's performance off of. Thanks.
    Matt
    0
  • Photocor
    Dears,
    [quote="Christian Gruner" wrote:
    I have to strongly disagree here. CO7 can handle hundreds and even thousands of images in a collection with no major performance-reduction. Of course the collection load times increase proportionally with the collection size, but once loaded, performance impact due to sheer number of images is limited.
    Working with a lot LA and masks can however affect performance, especially if the machine has little RAM and masks ares used a lot.


    Sorry but your argument doesn't convince me:
    Intel Core I7: 3770
    RAM: 32Go
    Graphic cards: GeForce GTX 770 with pilot 335.23
    Win seven 64 bit professionnal and software on a SSD (128Go)
    3 hard disk 3To.

    I never work pictures in batches when I use mask.
    To day I did the test with two folders: one with 63 photos and the other with 511 photos.
    I worked with 3 layers on one of 63 pictures: no slowdown.
    I worked with 1 layer on one of 511 pictures: slow down with a delay between the position of the brush of my Wacom and the position on the picture.
    As mstauss said, it is not new for me, but now because the evolution of C1 I whished to stop to use Photoshop and this slowdown stopping me.
    It is realy irritating!

    Regards.
    0
  • mstauss
    HD specs? Scratch space available?

    Like I mentioned before, I have experienced this issue since 3.4, but as mentioned above; once the images "res up" you shouldn't experience anything too detrimental to your workflow.

    A great work around is keeping a separate shooting and editing Session. This way the larger files with masks will not eat up your processor while shooting. You can move you all your files (.cR2, .cos, etc.) from the shooting session into the editing session and maintain your edits. This works pretty well for exiting and keeping an extra archive. If you do not let all your files import/"res up" before you begin working, then you will still experience the issues you are having.
    0
  • Photocor
    [quote="mstauss" wrote:
    HD specs? Scratch space available?

    1 SSD 128GO OCZ Vertex, 62Go free.
    2 Harddisk Seagate red RAID 1 , 3TO, 1,6To free.
    Like I mentioned before, I have experienced this issue since 3.4, but as mentioned above; once the images "res up" you shouldn't experience anything too detrimental to your workflow.

    Sorry, but I am french and I don't understand the wording "res up".

    A great work around is keeping a separate shooting and editing Session. This way the larger files with masks will not eat up your processor while shooting. You can move you all your files (.cR2, .cos, etc.) from the shooting session into the editing session and maintain your edits. This works pretty well for exiting and keeping an extra archive. If you do not let all your files import/"res up" before you begin working, then you will still experience the issues you are having.

    I import pictures from the APN in a session mode, always the same, named "Herve". And these pictures are placed in a specific folder, always different,by the way the folder contains pictures and subfolders Capture one with cache and Settings.
    Each time when I reopen Capture one, time is necessary before working as it is necessary to regenerate previews. And I meet what is described before.
    Do you have an idea?

    Kind regards.
    0
  • SFA
    Do you have any idea why your system is always regenerating previews when you open C1?

    In the preferences do you have your default Preview size set to the resolution of your screen (or smaller)?

    When displaying an image for edit C1 will apply the rules of a selected Process Recipe. Do you have anything in that connection that might be a challenge?

    I'm running an i7 3820QM CPU with 24Gb RAM (there is always spare RAM available no matter how I try to use it up!)

    Win 7 Pro 64bit.

    I have a 512Gb Samsung SSD. No raid drives on this notebook, just one external 4Tb USB3 unit to back up to.

    The GPU is a low power nVidia that C1 bypasses. Windows uses it sometimes.

    I have the Preview resolution set to the native full screen resolution.

    I run sessions with several folders and up to several thousand files. I don't see anything like the problems of slow speed in the way you describe it on this machine.

    As an experiment try a new session to see if anything changes.

    Also run the Windows Advanced Tools to see if the performance issues can be seen in the reporting tools available.

    I hope this information will eventually help you in some way.


    Grant
    0
  • Photocor
    [quote="SFA" wrote:
    Do you have any idea why your system is always regenerating previews when you open C1?
    Unfortunately no. When I use the brush in a layer, only 5Go of RAM are used.
    In the preferences do you have your default Preview size set to the resolution of your screen (or smaller)?
    Resolution is 1024px for preview
    When displaying an image for edit C1 will apply the rules of a selected Process Recipe. Do you have anything in that connection that might be a challenge?
    No, unfortunately.
    As an experiment try a new session to see if anything changes
    .
    I made this: on my SSD I put a session and I import on it two folders: one with 60 pictures, and the other with 500 pictures.
    When I draw a line with the brush from side to side of the image in 4 seconds, in the picture of the folder with 60 images the brush has the same speed the design pictured. It takes a second longer with the file 500 images.

    I hope this information will eventually help you in some way.
    Grant


    Thanks a lot for your help, I think I will open a ticket with the C1 support.

    Kind regards.
    Hervé
    0
  • Christian Gruner
    [quote="Photocor" wrote:
    [quote="SFA" wrote:
    Do you have any idea why your system is always regenerating previews when you open C1?
    Unfortunately no. When I use the brush in a layer, only 5Go of RAM are used.
    In the preferences do you have your default Preview size set to the resolution of your screen (or smaller)?
    Resolution is 1024px for preview
    When displaying an image for edit C1 will apply the rules of a selected Process Recipe. Do you have anything in that connection that might be a challenge?
    No, unfortunately.
    As an experiment try a new session to see if anything changes
    .
    I made this: on my SSD I put a session and I import on it two folders: one with 60 pictures, and the other with 500 pictures.
    When I draw a line with the brush from side to side of the image in 4 seconds, in the picture of the folder with 60 images the brush has the same speed the design pictured. It takes a second longer with the file 500 images.

    I hope this information will eventually help you in some way.
    Grant


    Thanks a lot for your help, I think I will open a ticket with the C1 support.

    Kind regards.
    Hervé


    What are your screen resolution ? 1024 px is very low for previews
    0
  • Photocor
    [quote="Christian Gruner" wrote:

    What are your screen resolution ? 1024 px is very low for previews

    It is a ColorEdge CG276, resolution 2560x1440.
    1024, Yes it is low, but I think by this way it is shorter to obtain previews.
    Do you think this could be the problem?!
    Regards
    0
  • Paul Steunebrink
    [quote="Photocor" wrote:
    [quote="Christian Gruner" wrote:

    What are your screen resolution ? 1024 px is very low for previews

    It is a ColorEdge CG276, resolution 2560x1440.
    1024, Yes it is low, but I think by this way it is shorter to obtain previews.
    Do you think this could be the problem?!
    Regards

    A too low preview setting makes CO7 continuously regenerate previews, with every move you make. The kills the preview concept and one of the most effective ways to slow down the program.

    I suggest you set your preview to your screen size or one step lower (unless you work often full screen), select all images, regenerate previews, let regeneration finish, restart CO7.

    Hope this helps.
    0
  • Photocor
    [quote="Paul_Steunebrink" wrote:

    I suggest you set your preview to your screen size or one step lower (unless you work often full screen), select all images, regenerate previews, let regeneration finish, restart CO7.

    Hope this helps.

    I meet some difficulty to understand why previews are continuously regenerate if size is lower than the definition of the screen.
    And of course I made what you suggested, and unfortunately nothing changed.
    When I check the performance, at the maximum of sollicitation of th computer with C1, only 4go of ram are used (I have 32Go on my computer.)
    Regards
    0

Post is closed for comments.