Zum Hauptinhalt gehen

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

C1 stop responding right after launching!!

ettore.causa
I have recently imported my full photo collection in C1
The files (more then 50000 images + many videos) are stored on an external 2T drive while the catalog is on the flash drive of my macbook pro retina,2.7gh,16g ram and NVIDIA GeForce GT 650M 1024 MB

In the last days I have experience many crashes,most of them are happening shortly after launching C1,either while importing or while browsing photos
The browsing experience is generally speaking pretty bad!.....switching from one folder to the other is really slow and even going from one photo to the next takes way too long

I have noticed that right after launching the application, C1 begins every time counting the number of images !!!!
...once it gets to the final number the overall performance improves a bit
Do you find that normal?
If i would store all the files inside the C1 catalog,would i see any improvement?
Would it help splitting my collection in multi catalogs?

Thanks for your help

Ettore
0

Kommentare

12 Kommentare

Datum Stimmen
  • AdamJ

    I have noticed that right after launching the application, C1 begins every time counting the number of images !!!!
    ...once it gets to the final number the overall performance improves a bit
    Do you find that normal?


    Unfortunately, yes. I have only 19,500 images in my catalog (referenced) and when I open Capture One I have to go get a glass of water or cup of coffee, as it takes between 100 and 130 seconds to finish 'counting'.

    I opened a ticket for this issue, and was told that its a known performance issue and that there may or may not be improvement in the future.

    Frankly this scared me away from using the catalog any further, I cannot wait 2-3 minutes every time I open C1 just to use the application.


    If i would store all the files inside the C1 catalog,would i see any improvement?


    No, but if you open your catalog and select all images and let C1 finish building previews (or turn them off) then backup/optimize the catalog when you quit it will ensure the fastest loading performance.

    Would it help splitting my collection in multi catalogs?


    Yes, smaller catalogs have less 'counting' - but for me that is a deal breaker, the idea of a catalog is to be able to use metadata to group/search across the entire catalog. Switching between catalogs breaks that to the point where I might as well just use sessions.

    Here's to hoping to the future for usable catalogs in C1! It's the only thing preventing me from leaving LR.
    0
  • ettore.causa
    It takes about 3 and half minutes for C1 to count all my images !
    but real problem is that after that,yes... the overall performance is better but I still get the mac beach ball so many times
    (especially going from one folder to the other) and I still experience daily crashes

    Hope they will soon fix it

    Ettore
    0
  • Rick Allen
    How big is the Catalog file? What image size is the preview set to?
    0
  • ettore.causa
    [quote="rapdigital" wrote:
    How big is the Catalog file? What image size is the preview set to?


    SIze preview set to 1280px
    at the moment the catalog file is 24GB
    (while the images files stored on the external HD is about 1.5TB)
    0
  • Rick Allen
    Yeah that catalog is never going to work as expected 😕 Is there any way you can split your collection into smaller catalogs? I think Capture needs to load the catalog into Ram and then you need some extra for overhead so maybe with 32gb of ram you'd be ok but even then I think you would struggle. I think catalog's are a step forward but needs real evolution before its ready for such big collections.

    Without hijacking your thread for me the number one problem with them is inability to push or sync back your settings/adjustments back to the original file structure. Without this option what chances do you have to break up the catalog now without losing your work? AFAIK there is none.
    0
  • alessandro ceccnoi
    Ettore, one thing I have learned the hard way and after many discussions with the support people is that the catalog MUST reside on your primary drive. I was having the same problem as you and it was because my catalog was on the same external HD as the files folder. Once I moved it back onto the main HD all went well.
    Unfortunately it means that you must re-catalog all your pix but after that life should be somewhat normal again
    0
  • AdamJ
    I do not agree.

    The catalog consists of 3 main pieces of data:
    1. Database (settings/metadata)
    2. Cache (previews)
    3. Originals (Images stored inside the catalog)

    My catalog of 19500 images is 22GB in size, it is broken down with the database being 119MB, cache is 21.8GB and Originals 0.

    Loading the catalog does NOT load all 21GB of image previews into RAM.

    Why shouldn't the catalog work as expected? I have these images also in a Aperture and LR catalog and they don't need 3 minutes to finish 'counting' images. Both apps are 'ready' for use in less than 10 seconds.

    I do agree with the last statement, the catalog is nice but it needs real improvement before it can handle even MEASLY small catalogs of 19500 images - much less a multi-year pro catalog with 100000 images.

    [quote="rapdigital" wrote:
    Yeah that catalog is never going to work as expected 😕 Is there any way you can split your collection into smaller catalogs? I think Capture needs to load the catalog into Ram and then you need some extra for overhead so maybe with 32gb of ram you'd be ok but even then I think you would struggle. I think catalog's are a step forward but needs real evolution before its ready for such big collections.
    0
  • AdamJ
    Once the counting is done - and I'm sure that all preview generation is done - my C1 works fine.

    I don't have any single folder that has more than about 70 images, if you have more in a single folder that can delay switching folders.

    As someone else mentioned the catalog needs to be on a hard drive local/internal to the computer.

    [quote="NNN635022403475152212" wrote:
    It takes about 3 and half minutes for C1 to count all my images !
    but real problem is that after that,yes... the overall performance is better but I still get the mac beach ball so many times
    (especially going from one folder to the other) and I still experience daily crashes

    Hope they will soon fix it

    Ettore
    0
  • ettore.causa
    Unfortunately even after the counting is done and with the entire photo library preview generates
    the performance is poor....
    and I I get many times the f....(sorry) beach ball !!!!!!

    I dont know what to do at this point...
    I cant have all images on the computer drive since I "only" have 500GB flash drive on my macbook pro

    I am still wondering if I would store all the images inside the catalog(obviously on an external drive) would improve anything

    Hope the team can suggest something...


    Thanks
    Ettore
    0
  • alessandro ceccnoi
    Ettore, only the catalog needs to be on your drive NOT the images. Understand that there is a difference. The catalog is few hundreds of MB. The files can be on an ext drive as big as you like. Until you do that C1 wont work. Is it wrong?? maybe but that is the way it is for now.

    Catalog file on system HD (preferably in the picture folder) files where you like.......

    [quote="NNN635022403475152212" wrote:
    Unfortunately even after the counting is done and with the entire photo library preview generates
    the performance is poor....
    and I I get many times the f....(sorry) beach ball !!!!!!

    I dont know what to do at this point...
    I cant have all images on the computer drive since I "only" have 500GB flash drive on my macbook pro

    I am still wondering if I would store all the images inside the catalog(obviously on an external drive) would improve anything

    Hope the team can suggest something...


    Thanks
    Ettore
    0
  • Malcolm McGhee
    I have a similar problem to this.

    My present 'test' catalog has only 2553 RAW images.

    If I open this catalog it takes about 12 seconds for C1 to be ready and useable.

    If I create duplicate the catalog and then add some 'User collections' the time to open the catalog rises to about 190 seconds.

    If you have 'User Collections' in your catalog(s) try deleting them and see if it makes any difference to catalog opening times.

    I have created a 'Case ID' of 116210.

    However it has gone very quiet and I have not had any responses to my last inputs to that 'Case' so I don't know if the issue is being looked at or if I am the only one with the problem.
    0
  • Sander Salim
    CO1 Pro 7 has superb rendering (far better than LR4), but I am too disappointed by its performance so far...

    With slightly less than 20,000 photos in the (test) catalogue, it also takes a very long time (if not irresponsive) for me to launch and work with. I do think smaller catalogue, which also means smaller/less Cache and thumbnails etc. will help the application to speed up.

    CO1 v7.1.1
    0

Post ist für Kommentare geschlossen.