メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

C1 v 5.0.1 crashes ImgCoreProcess.exe and error output

NN5072
Hi,

Since I have installed the vers. 5.01, it did work once at beginning, but now each time I start up, an error closing de ImgCoreProcess.exe appears. I close and it looks like I can work normally but if I want to convert a .CR2 file to JPEG, always I receive an error: Error Setting Source: C\.... \cache\proxies\file.CR2.crop - Error. But the directory CaptureOne\Cache\Proxies is there hanging up in every image directory I have.

Reloading de aplication does not fix the problem. Actually my C1 is broken so I can not use it to convert my .CR2 phtos to JPEG.

Any way to solve this ?? I am running Windows Vista Home Premium 32 Bits, and two Windows updates has been made lastly.

Thanks
0

コメント

12件のコメント

日付 投票
  • Paul Steunebrink
    I suggest to start to clean both the process history (you can do that from within CO5) and also remove the proxies of the image folder with Windows Explorer before you restart CO5 (CO 5 will regenerate the proxies).
    0
  • NN5072
    [quote="Paul_E" wrote:
    I suggest to start to clean both the process history (you can do that from within CO5) and also remove the proxies of the image folder with Windows Explorer before you restart CO5 (CO 5 will regenerate the proxies).


    But then I shall lost all the adjustments I have done, or no?? I have already proccessed more than 300 images !! And still I have the problem with the ImgCoreProccess.exe.

    Cheers
    0
  • Paul Steunebrink
    [quote="NN5072" wrote:
    [quote="Paul_E" wrote:
    I suggest to start to clean both the process history (you can do that from within CO5) and also remove the proxies of the image folder with Windows Explorer before you restart CO5 (CO 5 will regenerate the proxies).


    But then I shall lost all the adjustments I have done, or no?? I have already proccessed more than 300 images !! And still I have the problem with the ImgCoreProccess.exe.

    Cheers

    No, you won't loose any adjustment; these are saved in the adjacent Settings50 folder.
    0
  • NN5072
    [quote="Paul_E" wrote:

    No, you won't loose any adjustment; these are saved in the adjacent Settings50 folder.


    Done, but still the same problem ...

    Cheers
    0
  • Paul Steunebrink
    [quote="NN5072" wrote:
    [quote="Paul_E" wrote:

    No, you won't loose any adjustment; these are saved in the adjacent Settings50 folder.


    Done, but still the same problem ...

    Cheers

    Did you clear the process history as well?
    0
  • NN5072
    [quote="Paul_E" wrote:
    [quote="NN5072" wrote:
    [quote="Paul_E" wrote:

    No, you won't loose any adjustment; these are saved in the adjacent Settings50 folder.


    Done, but still the same problem ...

    Cheers

    Did you clear the process history as well?


    From Menu: Adjustments --->> Process History (I can access until here) -->> Clear from Primary IS NOT HIGHLIGHTED; so I can not do it

    From Batch -->> History --->>> I have killed the images in there

    System is taken a lot of time and still did not start to convert the RAW ; but after a while ... the ImgCorePorcess.exe error appears again and then the rest ...

    So still the same.

    After many resets; clear history; etc... and Restart program it looks now like the ImgCoreProcess is not crashing but when I try convert one by one image or just a few ones ... I notice is like hang-up; but looking to the activities, the system is running and when I click on Activities I can see the program is generatinng Proxies !!! ... say Generating 67 of 461 proxies, about 3:11 left !!!! but i´ts taken a lot more time !!

    Thats crazy !!

    Then If I close de C1 and restart again, after loading the image directory, the conversion in the queue is starting, but only convert one image (the firts one) and then in the activities start again to generate proxies !! (freezen the process queue). I am going to leave the system generating all proxies and wait to see what happens then ... but it says 2:58 for example but it´s taken a lot more time ... and I have 3Gb of RAM in my computer.

    OK:. STILL THE SAME PROBLEM: ImgCoreProcess.exe crashes during the final part of the proxies generation, so then appears the error with C\.... \cache\proxies\file.CR2.crop - Error and all process in the activity window are closed !!

    I am using Canon 7D RAW files ... later on I shall try with Canon 50D & 5D Clasic RAW files to see if there is any difference.

    Cheers

    BTW: Thank you for your help, Paul !
    0
  • NN5072
    OK

    Some feedback .... with the 50D and the 5D Clasic RAW files it seems to work ....

    The problem arises when I go to 7D directory where I have 718 RAW images ... it takes a very , very , very long time generating proxies and here I think is from where all the problems arise. It looks like each time is doing some task, it is generating the proxies again !?

    I did open this morning again C1 and after loading the 718 images of my current 7D directory, I went to the Batch section, and inmediadtly start in the activities to generate proxies of the last coneverted images !! The 20 images of a Canon 50D directory ... but again it did take long time to generate proxises ... and after it crashes again the ImgCoreProcess.exe.

    Any possible solution to this ???

    Cheers
    0
  • Paul Steunebrink
    I opened a folder with 20 new Canon 5D images and it took CO 501 37 sec. to generate previews. Same test with 20 new 7D images: 59 sec. to generate previews. The ImgCoreProcess.exe process in Task Manager took 107 KB (5D) to 179 KB (7D). System: XP SP3 32-bit, single core, 512 MB RAM (!) [how slow can you go?]

    If your system is significantly slower than this either the system is not functioning properly (in general I mean), or your 7D files are different from mine.

    Tip: monitor the ImgCoreProcess.exe size in Task Manager while it generates previews. If it grows exorbitantly you might want to open a case with Phase One.
    0
  • NN5072
    Thanks Paul...

    I strongly believe it´s related to the new vers 5.0X when it has to generate the proxies (or may be new version + 7D RAW files).... since I have installed this version I am having problems. I have opened a case with the Phase One Support about this.

    I did work with vers 4.8 in this same computer without problems and afterwards with vers 5.0 but very limited. When I go to an old directory with 7D raw images where I have worked before with vers 5.0 (so the proxies generated with vers 5.0 are there), the vers 5.01 has not problems to start the batch process and make the conversion .It start and works as usually do.

    But when I did erase the subdirectory CaptureOne (proxies + setting50) and I did restart vers 5.01 again -->> go to this directory, load the images and go to convert the images to JPEG, then the problems appears again !! Start generating proxies very, very, very slow and with chance to crash ImgCoreProcess.exe (sometimes not). The conversion only start after all proxies are generated (3-5 minutes time) and also sometimes only convert the first file in the queue and then crash. So the problem arise with the proxie generation when I start the batch process.

    I need to convert my images, so I am going to do it with DPP from Canon, at least I can work with it ....

    I shall wait for the help of the Support team

    Cheers
    0
  • Konrad Wasylewski
    I have exactly the same problem.

    5.0.1 worked fine for over a month and suddenly i got the same error message when exporting files today.

    I'm lucky to have 4.8.5 with license and it works but i expect Phase1 to solve this problem ASAP. I paid for the upgrade and i have no idea why this error comes up.

    I have Windows 7 and 5D Mk2.

    My computer has 8 GB of RAM and just like in your case the proxy generation takes a lot of time now and i cannot export anything!!!! Do anybody have a solution for this problem????


    Konrad
    0
  • MikeR
    The whole slow proxy thing has been a huge problem for a while. Instead of just letting users turn off the auto proxy generation, customer service wanted me to go through hoops, changing my monitor color profile, or putting folders on a different hard drive, or putting less files in a folder.

    I don't have time for this crap! The software is supposed to make work EASIER, and all it's done is make life miserable.


    IT'S NOT THE COLOR PROFILE. IT'S NOT THE HARD DRIVE.
    This is running on a machine with 16GB RAM, and a RAID 5.


    FIX YOUR SOFTWARE. OR AT LEAST LET US TURN OFF THE STUPID AUTO PROXIES.
    0
  • Drew Altdo
    [quote="MikeR" wrote:
    FIX YOUR SOFTWARE. OR AT LEAST LET US TURN OFF THE STUPID AUTO PROXIES.


    Mike,
    Judging from your case and response here, I am inclined to think the issue is simply your RAID 5. From experience, even Photoshop has issues running off of scratchspace on a RAID 5.
    In the end, Capture One needs the Proxies to operate. If you have a group of images that you do not want Capture One to generate proxies for, simply keep those images in a separate folder, it's as simple as that.
    0

投稿コメントは受け付けていません。