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

Web Gallery Crashes Too Often

TonyArmstrongPhotos
I love C1Pro -- I'm a convert from Adobe Lightroom -- but one thing is bugging me to no end (!!). 🤬

I continue to have random crashes as C1Pro tries to build a web gallery for me -- seven times so far for this one group of images. The session contains 112 photos, but C1P refuses to build the entire gallery. At one point, it will crash after 47 images, the next time 12, the next 50. But it will not finish.

Does anyone have a recommendation on what I can do to complete the gallery without crashing?

I don't want to have to go back to LR, but I have to say, it's gallery feature is much more complete and stable.

Help would be appreciated...
0

Comments

6 comments

Date Votes
  • Paul Steunebrink
    Version of CO Pro and OS X? What raw files are you bringing to a web gallery?
    0
  • Drew Altdo
    As a test you could try to process all the same images to the QuickProof format.
    If the processing crashes Capture One then odds are you have a corrupt file in the mix.
    0
  • TonyArmstrongPhotos
    Oh, sorry...

    I'm using C1P 5.1.1 on Mac OS X 10.6.3. I was processing IIQ files from a P40 back.

    As an aside, to start troubleshooting, I did a complete de-install of C1P and reinstalled it from a fresh download.

    I'll give the QuickProof format test that you suggest, Drew. If a corrupted image is the reason for the crashes, what would cause such a corruption and why would it be across sessions?

    Thanks for the quick response, gentlemen...
    0
  • Drew Altdo
    [quote="TonyArmstrongPhotos" wrote:
    If a corrupted image is the reason for the crashes, what would cause such a corruption and why would it be across sessions?


    Improper function of anything. It's as vague as that.
    Corruption can be caused by one simple miscalculation when writing a "1" or "0". It can be caused by an arrant mouse click, poorly placed cable or computer (my favorite was an External RAID stored atop a Subwoofer!), crimped firewire cable, user error, failing components of every variety... the list is endless. If you find a corrupt file, we'll investigate the cause then.
    0
  • TonyArmstrongPhotos
    OK, after repeated attempts, I finally got the gallery to generate all the way through. I could not determine where, if any, there was corruption. I'm just chalking it up to C1P idiosyncrasies. I hope it will be improved in the coming release(s) of C1P.
    0
  • Drew Altdo
    It's hard to fix idiosyncrasies that can't be narrowed down.
    If you could create a support case and walk us through the issue with some examples we might be able to pin down the cause and then address it, either locally on your machine or in the software.
    0

Post is closed for comments.