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

Crashing during preview generations?

NNN634348707184089826
This is so frustrating. I have loaded a very small aperture library to C1 (300 images) and everything works great. I tried a larger one consisting of about 2500 images. It loaded fine. But it crashes during the preview generation. I can usually start it up again and it will crash again. I have the latest iMac with 32GB RAM and running 4 GHz Intel Core i7. It is a hybrid SSD/hard drive.

Anyone with similar problems and hopefully with any solutions. I have sent lots and lots of the crash report to Phase One and put support email but I have heard nothing from them.

This is the trail software. If I can get it to work then I will buy it.

Any thoughts?
0

Comments

10 comments

Date Votes
  • SFA
    [quote="NNN634348707184089826" wrote:
    This is so frustrating. I have loaded a very small aperture library to C1 (300 images) and everything works great. I tried a larger one consisting of about 2500 images. It loaded fine. But it crashes during the preview generation. I can usually start it up again and it will crash again. I have the latest iMac with 32GB RAM and running 4 GHz Intel Core i7. It is a hybrid SSD/hard drive.

    Anyone with similar problems and hopefully with any solutions. I have sent lots and lots of the crash report to Phase One and put support email but I have heard nothing from them.

    This is the trail software. If I can get it to work then I will buy it.

    Any thoughts?


    Thoughts,

    Crash reports are generic and usually anonymous. Interesting and useful but don't produce responses from any software vendor I am aware of.

    You need to create a Support Case to get fast and personal support. Find the "How to Contact Technical Support" option.

    https://www.phaseone.com/en/SupportMain ... tCase.aspx


    I would suggest that there is something in the Aperture library, as converted, that C1 does not like. Difficult to suggest what that might be but the supporters may have a short list of candidates to check for.


    HTH.


    Grant
    0
  • NNN634348707184089826
    I did send in a support request a couple of days ago. Maybe because its the 30 day demo I am not eligible for that support? On the crash reports. If they are anonymous, why do ask for your email. Or at least mine does.
    0
  • SFA
    [quote="NNN634348707184089826" wrote:
    I did send in a support request a couple of days ago. Maybe because its the 30 day demo I am not eligible for that support? On the crash reports. If they are anonymous, why do ask for your email. Or at least mine does.


    Being on a demo makes no difference. Can you access the Support Case via your user account? Do you have a Case number?

    Crash reports are generic.

    In some cases a developer might pick out a particular report and seek further info - therefore they need to know how to contact you. But in general they will simply be part of an automated mass analysis that is useful to the developers in order to see what sort of things are happening "in the wild" but cannot be the basis for thousands of individual investigations.


    HTH.


    Grant
    0
  • NNN634348707184089826
    I might have figured it out. I took an Aperture library that I knew would crash on C1. I re-generated all of the previews. I did a smart filter and removed all of the Aperture previews that showed that they were offline (no identified master). I then changed the aperture managed library to a reference library. 3400 images loaded fine with the C1 Aperture library import. I selected all images so C1 could generate previews. They all DID!!!

    So I am guessing that I was trying to get C1 to process some broken image files. I am not sure if changing from managed to referenced on the Aperture was necessary. But I have read that to future proof your portfolio that its good to do.

    I am now doing this for the other 4 libraries that I have for a total of 40K images. I will post my results here.
    0
  • NNN634348707184089826
    Nope. I split my main Aperture library into 4 separate libraries. Re-did the previews, relocated the masters for a ref. system, removed all offline files an other files like .psd and . mov files. I loaded the first one and it was stable. Added the second one as a collection. Stable. Added the third and sometime last night it crashed. I did a verify and repair But now I have a brand new message that it cannot recognize the database?

    I am on the verge of giving up and going to LR
    0
  • dredlew
    I have yet to do a full Aperture transition as well, but I've started in small batches... mainly based on various comments here in this forum regarding large libraries (and Aperture Import Tool). C1's DB is apparently not built to handle large volumes, so the more photos you add to your library, the more performance issues you'll likely encounter.

    Hence, the approach I use is keeping a library small. Split your Aperture library into categorized sub libraries (i.e. Wedding, Engagement, Travel, Sports, etc.) and basically create a C1 library for each category and import your images into the respective libraries. You can switch between libraries from within C1, however I would not recommend that, since it doesn't seem to purge out the previous library from memory when switching. It just keeps adding until you run out of RAM. Instead, I would choose the library you want to work in upon application launch. Just press the alt/option-key right after clicking on the application icon. This will bring up the library chooser. Select from there. Or, just double click a library file and that's the one that will open.

    The multiple-library approach has some obvious disadvantages, like the inability to search across multiple libraries and keywording. You'd have to keep an external list up-to-date with keywords that you would need in more than one library. However, the whole keywording in C1 isn't the most solid either and it's incapable of writing metadata to the original (only into a separate XMP file), so I personally prefer to handle the metadata outside of C1 anyway. I also have all my images referenced, which makes it easier.

    This has been working for me so far, haven't had any library issues or complete catalog corruption like others (including you) have reported. Might be worth a try...
    0
  • lewisl
    If you have the resources and the willingness to invest in learning time, I'd recommend using Lightroom as the "library". Size is minimally a factor and performance is good up to many tens of thousands of images.

    And use C1 for editing your most important or challenging images where you want the best results. You can use C1 like a "file browser" with an image processor: create a session; open the session; use the library tool to go to any folder on your system (internal drive or connected drive); edit any image. The resulting edits will be saved in a CaptureOne folder within the folder you browsed to.

    Two things:

    1. The Lightroom thumbs and previews will NOT reflect these changes. This would also be true if you used Photo Supreme, Photo Mechanic, ACDSee, or On1 Browser as the "library" (these products are not, strictly speaking, equivalent). Sounds terrible but you can always open C1 and navigate to the image. To get from Lightroom to the right place, use show in finder. In Finder, just use "Open with..." to open the image in C1. Of course, if you are actively working on a lot of photos just keep both apps open. Lightroom manages memory properly (unlike C1) and C1 working with sessions is not a memory problem at all. With 8G of RAM, this should work fine.

    2. It really helps to keep track of which images have nice C1 versions. I use the "Instructions" metadata field. I enter "C1 Edits" in that field. In Lightroom, I can quickly (e.g., instantly) find all of the images I've edited in Capture One. Note that there are some issues if you are editing tiff or jpeg files this way, but it works for RAW. However, to sync metadata you will need to sync metadata to file in Capture One. it is better to sync explicitly than do full sync of xmp because full sync is really slow. On the Lightroom side, you should read in the metadata. The cool thing about lightroom is that it will be able to tell that its metadata is out of date. It will put an exclamation point in the upper right corner of the thumb. Or, you can actually search in the entire catalog for any image with out of date metadata and read the metadata. You an make this automatic on the Lightroom side (similar to C1) by syncing xmp automatically. This doesn't crush lightroom as badly as it crushes C1, but it still slows things down. As I've written, it sounds like a big burden but in practice, it's not. After you do the big Aperture conversion and you are working (mostly) with new photos, you'll just have a shoot or two to work with.

    These gotchas are not the "fault" of C1. The same would be true if you use DXOMark or Photo Ninja or anything else. The nature of non-destructive editing, which is a very good thing, is that a set of "edit instructions" is maintained for each image. Only the app that created those instructions can actually show their results correctly. You can freeze the edits into a jpeg or tiff, but this sort of defeats the purpose of non-destructive editing. The only time to do this is when you need to export an image to post to the web, to print (if using a different app than the image editor to print), or to make an edit that the raw processor/non-destructive editor just can't do. A lot of people find that many things they might have done in Photoshop or Nik can be done in C1 because C1 has great local/layered edits and terrific color correction.

    Hope this makes sense.
    0
  • peter Frings
    [quote="lewis" wrote:

    These gotchas are not the "fault" of C1.


    Technically, they're not. But the sorry state of the DAM in C1 is the reason why we have to jump through hoops like this.

    And to all apologists out there that say we have to use sessions, or keep our catalogues clean: I had to look up an image of stonehenge I knew I took somewhere between 2000–2005. Launched Lr, searched for stonehenge (keyword), filtered on year, and I had my image in less that 40 secs. Launching LR included! In 40 secs, C1 would still be showing the "Opening" screen!

    Now, I have to admit that I still need to think about the concept of C1 as a processor (maybe sessions), and then filing the "developed" images (JPGs) in a place that can easily be searched. However, in all my years of using Aperture and then LR, there was never a need for such a construct. Still, the idea has its merits, I must admit. However, that should not be an excuse for not fixing the poor performance of the DAM.

    Cheers,
    Peter.
    0
  • lewisl
    Peter,
    Totally agree. Made several long posts about the severe problems. If you want to use Capture One at all you have to concede for the meantime that catalogs aren't feasible with more than 10,000 images or so. Hard to tell if Phase One cares. Maybe medium format camera users just use tethered sessions.
    I'd say that they probably do care because they keep trying, but seem to not have the technical prowess or adequate resources to tackle the problems.
    0
  • Permanently deleted user
    [quote="lewisl" wrote:
    Maybe medium format camera users just use tethered sessions.

    They certainly don't shoot the volumes of images that users of smaller formats typically do, so won't likely encounter issues with catalogues of tens of thousands of images, or more. A few dozen images is a huge shoot for most medium system users.

    So therein lies the problem. Capture One's principal market and, indeed, its reason for existence, is to support Phase One users. The rest of us, using other equipment, merely subsidise that primary objective. If there was ever a problem with Capture One for Phase One users, I reckon it would be fixed quick as a flash.
    0

Post is closed for comments.