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

C1-4 Crashing

Comments

14 comments

  • Keith Douglas
    Seems to lockup when it starts to process just like the demo did!
    0
  • scotchman
    Hi All,

    New to C1 and new to this forum - looking for some help.

    The beta of version C1.4 worked just fine and I was so impressed by it that I bought the new version 4 as soon as it became available. Bad move.

    Whenever I click "Process", I get the message "The queue is currently stopped, do you want to start it again?' When I click "Yes', the program crashes - always. I've never managed to process a single image with this program.

    PowerMac Dual 1.8 GHz G5 running 10.5.1, 2.5GB RAM.

    Anyone got any ideas?

    Thanks,
    Dave
    0
  • Bill7
    Possible Solution to C1-4 Crashing on Process:

    1. Go to Batch, select and Clear the Queue*;
    2. Select an image for Processing;
    3. Go to Output and configure your Process Recipe. Important: Select "None" for the Open With selection. Choosing "None" is what solved my problem with crashing. The images I processed were placed in the History file in Batch and the Output folder in Library. C1-4 did not crash.

    I had the idea to select "None" from the second paragraph on page 65 of the User Guide. I have only tried Processing two images to JPEG; each individually. I have not tried this with multiple images or TIFF's. *You must clear the Queue because those images will likely have the instruction to Open With another application, as mine did.
    0
  • scotchman
    Thanks Bill M,

    That's got me on the right track - thanks very much. At least now I get the "Process" to run.

    Unfortunately, a few seconds after it completes (unsuccessfully) the program crashes with a "ImgCoreProcess quit unexpectedly" message. I'm working on that right now and will report any progress.

    Thanks again for your help.

    Dave
    0
  • scotchman
    I've tracked my problem down to .dng files.

    C1-4 will process original camera raw files such as .RAF, .NEF, .CRW, etc, but crashes when attempting to open .dng files created with Adobe Raw Converter.

    Neither will C1-4 save as .dng - I click on "Process" and nothing happens.

    I assume this is a bug since I didn't have this problem with the beta version, which worked perfectly.

    Regards,
    Dave
    0
  • Paul Steunebrink
    [quote="scotchman" wrote:
    I've tracked my problem down to .dng files.

    C1-4 will process original camera raw files such as .RAF, .NEF, .CRW, etc, but crashes when attempting to open .dng files created with Adobe Raw Converter.


    I have tried this for a Canon 10D CRW file, saved as DNG in ACR4.3.1, both compressed and uncompressed. Both show up in CO4 as valid and editable DNGs. The compressed file processes but is not stored, opening the Events windows (Could not process file). Next, the uncompressed converted DNG immediately crashed CO4 when processing starts. After restart of CO4, the Event window shows an event "The Processing queue has been paused", which is correct by the way.

    [quote="scotchman" wrote:
    Neither will C1-4 save as .dng - I click on "Process" and nothing happens.


    This works fine for me, however it is lightning fast so it seems nothing has happened 😂 Check you output folder.
    DNG compatibility both for import and export has to be worked out apparently (a.k.a. bug).
    0
  • Paul Steunebrink
    [quote="Paul Steunebrink" wrote:
    [quote="scotchman" wrote:
    I've tracked my problem down to .dng files.

    C1-4 will process original camera raw files such as .RAF, .NEF, .CRW, etc, but crashes when attempting to open .dng files created with Adobe Raw Converter.


    I have tried this for a Canon 10D CRW file, saved as DNG in ACR4.3.1, both compressed and uncompressed. Both show up in CO4 as valid and editable DNGs. The compressed file processes but is not stored, opening the Events windows (Could not process file). Next, the uncompressed converted DNG immediately crashed CO4 when processing starts. After restart of CO4, the Event window shows an event "The Processing queue has been paused", which is correct by the way.

    Update on my previous posting. I was able to succesfully process both the compressed and uncompressed DNG files (Canon 10D raw, converted with ACR 4.3.1). The solution is that I selected an ICC profile in the Quick Tool tab. With converted DNGs, CO4 does not assign a camera profile automatically. You can either select a profile referring to the camera that made the files or choose (Adobe) DNG File Neutral. I read this tip in the CO4/Windows forum.
    0
  • scotchman
    [quote="Paul Steunebrink" wrote:
    Update on my previous posting. I was able to succesfully process both the compressed and uncompressed DNG files (Canon 10D raw, converted with ACR 4.3.1). The solution is that I selected an ICC profile in the Quick Tool tab. With converted DNGs, CO4 does not assign a camera profile automatically. You can either select a profile referring to the camera that made the files or choose (Adobe) DNG File Neutral. I read this tip in the CO4/Windows forum.


    Hi Paul,

    I can confirm that works for me too. DNGs derived from a Nikon D200 via Adobe DNG Converter now process OK so long as an ICC profile is selected in the Quick Tool tab.

    Thanks and regards,
    Dave
    0
  • Jonathan Gilbert
    Hello,

    Yes! the ICC Profile is the solution. One thing to keep in mind is that once the ImageCoreProcess has crashed, you will need to restart CO4 in order to process any other images.
    0
  • Chris1012
    I am running the latest version of COP on Leopard and i cannot get through a batch without it crashing every 1 to 5 images or so. None of these suggestions work for me. Anyone else still having these issues?

    Thanks,

    Chris
    0
  • Jim R
    [quote="Jon" wrote:
    Hello,

    Yes! the ICC Profile is the solution. One thing to keep in mind is that once the ImageCoreProcess has crashed, you will need to restart CO4 in order to process any other images.


    Do you consider this a bug or normal?
    0
  • Paul Steunebrink
    [quote="NN" wrote:
    [quote="Jon" wrote:
    Hello,

    Yes! the ICC Profile is the solution. One thing to keep in mind is that once the ImageCoreProcess has crashed, you will need to restart CO4 in order to process any other images.


    Do you consider this a bug or normal?

    Hello NN, you are quoting a reply of more than a year old. That is allowed, of course, but since then Phase One has corrected the issue several releases ago.
    0
  • Jonathan Gilbert
    [quote="NN" wrote:
    [quote="Jon" wrote:
    Hello,

    Yes! the ICC Profile is the solution. One thing to keep in mind is that once the ImageCoreProcess has crashed, you will need to restart CO4 in order to process any other images.


    Do you consider this a bug or normal?



    That was a bug, which as Paul mentioned was fixed about a year ago. As for the crashing Chris described, please create a support case if this is happening. Capture One 4.6 has been a big jump in overall stability, so most cases of persistent crashing are related to system instabilities. Of course if we find a vulnerability in our software we will work to correct it.
    0
  • Jim R
    [quote="Jon" wrote:
    [quote="NN" wrote:
    [quote="Jon" wrote:
    Hello,

    Yes! the ICC Profile is the solution. One thing to keep in mind is that once the ImageCoreProcess has crashed, you will need to restart CO4 in order to process any other images.


    Do you consider this a bug or normal?



    That was a bug, which as Paul mentioned was fixed about a year ago. As for the crashing Chris described, please create a support case if this is happening. Capture One 4.6 has been a big jump in overall stability, so most cases of persistent crashing are related to system instabilities. Of course if we find a vulnerability in our software we will work to correct it.


    Sorry, missed the date. Didn't realize these threads are running that old.
    0

Post is closed for comments.