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

Huge Lightroom catalog import

Kommentare

15 Kommentare

  • Drew Altdo
    My immediate guess is that the stall/crash is because Capture One can't read or access the connected images.
    Try disconnecting the external and Capture One will import the Catalog but not connect to the images. This can go quite quickly (maybe) and then you can connect the external source and "Locate" the folders of images.

    I can't say that I've imported a Lightroom Catalog of that size but it is within the possible realm.
    0
  • sizzlingbadger
    I have imported several LR catalogs, not as big as your one but it was much much quicker. I wouldn't expect to measure the import in days just a few hours.
    0
  • NN635254670070988840UL
    Thanks for the tip about disconnecting the drives. That went alot quicker, and without crashing!

    However, now the Capture One catalog has all the LR collections, but they are all empty! And I can not see an option to reconnect images, when I can't right-click on one? It just says "No images in Collection" 😭
    0
  • sizzlingbadger
    You have to reconnect the folders not the collections.
    0
  • Permanently deleted user
    Capture One simply can't handle large amounts of images without becoming unstable and unreliable.
    Simply is not robust enough.

    Even the media management program thy bought from Microsoft Expression Media could not handle large amounts of images.

    IF you want to handle large amounts of images you are better off with Lightroom.
    0
  • Keith Reeder
    [quote="FredBGG" wrote:
    Capture One simply can't handle large amounts of images without becoming unstable and unreliable.
    Simply is not robust enough.

    And what do you base that "statement of fact" on, Fred?
    0
  • NN635254670070988840UL
    Thanks again for the tip, but it still doesn't work. It doesn't seem like the folderstructure followed the one from Lightroom, because I got all the collections, but no folders. It just says "Catalog" in the folder window. I even tried to add one of the disks, but it didn't show any images. I would also think Captureone was able to at least import the previews from Lightroom, but it's like an empty shell of Collections.
    0
  • sizzlingbadger
    Is it possible to export a new catalog from LR that doesn't include missing images and then try to import that. Exporting to a new catalog often cleans up crap which accumulates in the original catalog.
    0
  • NN635254670070988840UL
    Hi, that would not be an option ☹️

    Could you think of any other solution? I can't figure out why it shouldn't work exporting with the externaldisks unattached?
    I would think LR has some preview information atleast which Capture should recognize, and I cannot understand why the collections have followed, but not the folder structure..
    0
  • sizzlingbadger
    I think it could be a bug. The external storage should not be required to import from the LR catalog, all the information is there already. The CO previews should be built after the import when the external drives become available.

    I have been using CO catalogs for some time now and they are very flakey, I do not rely on them for my main workflow. I still use LR and it has a far more robust catalog system at present. In fact introducing CO to my workflow has caused nothing but pain and I'm seriously considering dropping it all together as I'm not seeing any real benefits.
    0
  • jknights
    [quote="FredBGG" wrote:
    Capture One simply can't handle large amounts of images without becoming unstable and unreliable.
    Simply is not robust enough.

    Even the media management program thy bought from Microsoft Expression Media could not handle large amounts of images.

    IF you want to handle large amounts of images you are better off with Lightroom.



    The original poster covers my experience with this.
    My total image catalog is 77000+ images.

    I have attempted to use COPro cataloging since 7.0. through to current version7.2.1
    All versions have failed at some point. It is OK for about 5000 images then gets slower and slower until it crashes.
    I have never sucessfully managed to get a complete working catalog.
    Sorry but this product is not industrial (or even serious amateur) strength.

    The only products on Mac that I have found that are able to do my catalog are Lightroom5.x (which I currently use and but it doesnt work across the network only for directly attached drives), Extensis Portfolio Server, iView MediaPro, PhotoSupreme.

    On Windows there are several products but for me iMatch3 is without peer. iMatch3 is just superior to everything else, I wish it was available on Mac.
    0
  • Keith Reeder
    And yet I had no problem with a 127,000 image Lr catalogue...

    Maybe it's a Mac/Windows thing? I use Windows.
    0
  • jknights
    [quote="Keith Reeder" wrote:
    And yet I had no problem with a 127,000 image Lr catalogue...

    Keith, I think you are on Windows which makes its behaviours different.
    Also it depends on how your disks are attached (USB, Firewire, direct SATA, SATA/PATA internal).
    0
  • sizzlingbadger
    I have imported several large catalogs into CO from LR without issues on a Mac. The issues I tend to have are after the import. The Catalog just doesn't have the required tools yet to manage it effectively. Creating sub catalogs and merging catalogs cannot be done. Even backing the catalog up is not robust enough yet. I have had several catalogs corrupt and had to lose work because of this.

    Lightroom and Aperture do not give me these issues so its not a Mac only problem. Both Aperture and Lightroom did give me these headaches five or so years ago but they have ironed out the problems now. CO will most likely do the same over the next few years, it as after all a new feature and will take some time to get right.
    0
  • Keith Reeder
    [quote="jknights" wrote:
    ]Keith, I think you are on Windows which makes its behaviours different.

    Yep, the same thought occurred to me.
    0

Post ist für Kommentare geschlossen.