CI SE 3.6 Crashes upon opening!

Comments

9 comments

  • E Michelson
    Close SE.

    Please delete the the Batch Job folder located at ~/Library/Application Support/Phase One. ~ means your Home folder.

    Sometimes Capture One won't start up due to corrupted files in that folder and the easiest thing to do is to trash the entire folder. Capture One rebuilds the folder although you will lose the contents of Batch Queue.
    0
    Comment actions Permalink
  • Des1
    Good Day Sir,

    Aha!--that seems to have fixed the problem--for the moment thank you- Do I have to do this every time I use the V3.6?

    Grateful for the reply and assistance.

    Des
    0
    Comment actions Permalink
  • E Michelson
    No, this should not happen very often at all. But you may want to stick it in your bag of tricks for future reference.
    0
    Comment actions Permalink
  • mtomalty
    'E',

    I've been experiencing the same repeated crashes as Des.
    Unfortunately,the remedy that worked for him has had no affect
    on my crashes.

    The only action that I've done (I've done it frequently in the past)
    which likely may have triggered the problem is that,after
    successfully quitting CaptureOne,I merged the folder of images
    that I had been working on just prior to closing CO with another
    folder on my desktop.
    After that point,game over!
    Since then,every time I try to launch CO (it crashes between a fraction
    of a second to a couple of seconds) it creates a folder on my desktop
    with the same name as the one I had merged,and deleted.

    FWIW,the folders in question contained new Canon 1DsMkll files.

    Any thoughts on how I should proceed?

    Thanks,
    Mark Tomalty
    0
    Comment actions Permalink
  • E Michelson
    Hi Des,

    If you are going to \"merge folders\" together I recommend that just before quitting capture one you remove the session to be merged into another folder from the session list. That way Capture One there is no possibility for confusion about what Capture One expects to see when it starts up.

    What exactly are you doing when you merge folders together? Are you moving an entire capture folders (including the folder) into another session capture folder? Just the raws? the raws + previews?

    Eric Michelson
    0
    Comment actions Permalink
  • mtomalty
    Eric

    Fortunately,for Des,he is not the one messing around with folders
    on his desktop.

    I'm the guilty party!

    In a nutshell,I had a series of folders on my desktop that each
    contained between 15 and 30 images,all being various test images
    from a new Canon 1DsMkll.
    After viewing each folder in CO,and processing out a few tests from each
    folder,I quit CO,as I normally do leaving the last set of thumbnails I had
    worked on open in the thumbnail pane.

    At some point thereafter,knowing that I was done with certain test images
    I trashed most of the files from assorted folders (as the images purpose
    was only to get an early overview on a new camera) and amalgamated
    the remaining few files from assorted folders into a new remaned
    folder after which I trashed the now empty test folders.
    One of these trashed,but empty,test folders was unfortunately the
    folder which had been 'active' when I had earlier quit CO.

    FWIW,I'm running OS 10.2.8.
    My laptop is running 10.3.5 and is still running CO 3.6 without problem
    despite working in the same messy style I have outlined above.

    Mark
    0
    Comment actions Permalink
  • E Michelson
    Hi Mark,

    Always delete a folder reference in Capture One if you move, rename or trash it. While it should not cause a crash it will cause the folder to appear in red type in the organize tool, the software's way of saying \"I can't find it!\"

    In general the desktop is not my favorite place for storage despite the apparent convenience of it. I am not sure why but it has been my experience that folders on the desktop are characteristically unreliable. When you load Capture One the default location for Sessions is the ~/Pictures. I'm happy with that.

    Try not to have too many favorites. We have no limitation on how many you can have but having lots of favorites makes it that much harder to track your folders and files especially if you create sessions and keep the default names for the Capture, Process and trash folders. I have suggested that if you create a session called \"Blue\" that it is not a bad idea to add Blue to the Capture and Process folders to so there is no confusion which session a folder belongs to.

    Every now and then repair the disk permissions on your boot disk, too.
    0
    Comment actions Permalink
  • mtomalty
    Eric

    Thanks for the advice and,to be sure,I will apply them in future.

    More critically,though,is that I am still shut out of CO 3.6-since Saturday.

    How do I proceed to remedy this situation? It has been suggested by
    someone,not familiar with CO software,that the solution would be to
    dump everything CO related-applications,perfs,libraries,etc and start
    fresh.

    Help! Canons DPP is wearing thin .

    Mark
    0
    Comment actions Permalink
  • mtomalty
    Eric

    Just so i don't waste anymore of your time on this i wanted to let
    you know that the local Phase rep just left the studio after slapping me
    around for abusing the system and 3.6 is up and running.
    DPP is once again in the rear view mirror :>))

    Thanks again
    Mark
    0
    Comment actions Permalink

Please sign in to leave a comment.