ImgCoreProcess.exe error
I get this Windows 'ImgCoreProcess.exe error' message several times per session (about 150 files), usually while processing a file. On top of that, sometimes my settings are lost.
Am I the only one with this problem? (Toshiba Satellite with Windows XP, SP2 etc., 2Gb RAM, Pentium 2.6Ghz).
I never had this problem with version 3.7.
Any help gratefully appreciated.
Am I the only one with this problem? (Toshiba Satellite with Windows XP, SP2 etc., 2Gb RAM, Pentium 2.6Ghz).
I never had this problem with version 3.7.
Any help gratefully appreciated.
0
-
Hello,
Update to 4.0.1 and this should be solved. http://www.phaseone.com/Content/Downloads/CO4.aspx0 -
Thanks for the answers. I use v. 4.0.1 with a Pentax K10D. I don't use DNG f iles but Pentax's PEF files.
A fellow Pentaxian says his problem is solved, I will try what he said and report to the forum.0 -
I've just encountered this problem and I'm on 4.01
Happens only on batch processing and only after awhile.
I can restart C_1 and work OK for a while and then it crashes again with the same message (IMGCoreProcess.exe shut down)
frustrating
Thanks for help0 -
[quote="Steve g" wrote:
I've just encountered this problem and I'm on 4.01
Happens only on batch processing and only after awhile.
I can restart C_1 and work OK for a while and then it crashes again with the same message (IMGCoreProcess.exe shut down)
frustrating
Thanks for help
OK, you're on 4.0.1. Some more info like Windows version, camera, input and output profile, number of processed images before crash, other applications running might give us a better picture.0 -
[quote="Steve g" wrote:
I've just encountered this problem and I'm on 4.01
Steve, are you sure you are using build 4.0.1.14990? I only ask as the original release version also said 4.0.1 but a different build number. Very confusing!
Iain0 -
is there any known difference between 4.01.14990 and 4.01.14900? 0 -
Oooops! Well, typing never was my strong point!
Typos aside, my point still stands though.0 -
OK well it's build 4.01.14900
I'm on XP, Canon RAW from 40D, with the 40D generic profile in the right spot. Input and output profiles are both adobeRGB, and I'm batch converting to TIFF in a separate folder. No other apps are running except virus and firewall type stuff.
Number of images before it goes down varies, usually 20, sometimes more or less. Have to close down C-One, and reopen to get another lot converted before it goes down again.
Thanks for any help
steve0 -
Hi Steve, if I recall correctly someone had a similar problem while processing to a external or network drive. Do you use the internal hard disk?
You could remove the Capture One.col file from the Capture One Library folder and see it helps.0 -
I get this error when batch processing TIF files. The computer will chug away happily on it's own processing as many jpg files as I throw at it, but not TIF files. I have found that it will process 12 files at a time, but if I attempt to process 14 files, it will fail after doing four of them. I now process TIF files in batches of 12. 0 -
I said I would report to the forum - better late than never!
It seems that my problem is solved: I now download my SD card on my computer (I used an external hard disk before) and output the TIFs to the external drive.
Also, I use the camera profile for my K10D.
I don'k know which of these 2 changes did the trick (and I'm not prepared to test it) but it's fine now.0 -
Well, I rejoiced too quickly after all, the problem persists! I wonder if it is because there are variants in the batch. I will watch for a pattern there.
However, my settings were not lost this time...0 -
This is getting me crazy, all the more that I thought the problem was solved. Here is the error message I get:
Error Setting Source C:\\PHOTO PROCESSING\\ORIGINALS\\2008-04-05 - Château d'Agassac\\CaptureOne\\Cache\\Proxies\\IMGP6109.PEF.cop - Error0 -
hi luxart,
You talk about 'the problem', but it seems to me that there are different problems and potential causes. You started this thread with a 'ImgCoreProcess.exe error' and I think you solved that.
Your latest 'Setting Source' error seems to indicate that CO4 is having troubles in reading or writing the preview files. Not much information, so some questions:
Is this the only message (I assume you have more images in that folder), or one in a list of similar messages for different images?
When does the message(s) occur (when opening the folder for example)?
Do you get previews and thumbnails?
Are you able to apply adjustments and save them?
If it is a specific image, can you copy it to a different folder (with a short name without special characters) and open it? Same/different result?0 -
Hello
A long shoot, but try to have cataloge and file name with only a-z, 0-9 and w/o ´ etc
Roine0 -
Hi Paul and everyone who answered,
Thanks for answering. I'll try to be more precise.
I still have the "ImgCorePrecess.exe error" message. In my last post, I also copied the error message generated within CO4 (I had omitted to do this in my previous posts). This message is generated for each of the files that fails to be processed in the batch.
To sum my workflow:
1. I import files from SD card to C:\\ drive under the name "YYYY-MM-DD - Job xyz"
2. I apply the Pentax K10D profile
3. I copy the profile
4. I apply the profile to all files
5. I adjust each image individually
6. I batch process (to the C:\\ drive) and this is when the problem occurs: CO4 will process the first files (usually about 20 to 30) than I get the "ImageCore" error, AND AT THE SAME TIME, CO4 opens a window and rolls out the list of the images that were not processed and displays "error source c:\\PATH... - Error" (as I explained in my previous post - 1 message for each image that was waiting to be processed in the batch).
I close CO4 and restart it but it doesn't respond. I have to reboot my computer. Sometimes, my adjustments are lost, sometimes they stick.
I will try to have a "cleaner" filename as Roine suggested.
I hope this can be solved as I do like the software!
Regards0 -
It did it again: I had a batch of 81 files. It processed 21 files successfully then I got the "ImgCorePrecess.exe" error message. When I clicked "do not report" this window appeared:
http://farm3.static.flickr.com/2229/2408856810_20c49d9fdc_o.jpg
I hope it helps.0 -
I have the same problem.
raw files imported to hard drive via C1
XP on Quad 6600 with 4 gig RAM
Raw files from Canon 1Ds3
Problem occurs on batch processing to 16 bit tiff. Based on the lack of response to the OP I assume there's no resolution yet?
Ken0 -
Sad to report, this problem is not limited to batch processing, it just crashed again while processing files individually. Seems we're still in beta testing mode with this release. 0 -
[quote="kenincalgary" wrote:
I have the same problem.
[...]
Problem occurs on batch processing to 16 bit tiff. Based on the lack of response to the OP I assume there's no resolution yet?[quote="kenincalgary" wrote:
Sad to report, this problem is not limited to batch processing, it just crashed again while processing files individually. Seems we're still in beta testing mode with this release.
Hi Ken,
A few remarks to your posts. First I like to encourage you to provide more details besides a 'me too' remark and stating we are in beta mode. Next, regarding lack of response: I do not understand what you are referring to. This is a user-to-user forum, people helping each other voluntarily. You can always report a problem in a support case with Phase One. I believe they are determined to iron out as much problems as possible.
I hope this helps and you will choose your best options for support and enjoy using this software.0 -
[quote="luxart" wrote:
[...]
I will try to have a "cleaner" filename as Roine suggested.
Hi luxart,
Your last post makes your workflow more clear, thank you. Just doing me a favor, process to a folder like \\Mes Documents\\Mes Images\\TIFF or ..\\JPEG. I'll tell you why: sometimes a long folder name can overflow a buffer in a software component, leading to a crash. Sometimes it is after 16 images, or 21 or whatever number, depending on size of the path.
If the error remains with the short path, please log a support case with Phase One as well (I run out of bright ideas 😄 )0 -
Hi Paul,
OK, I'll try that and will report to the forum. Keep up the good work!0 -
Well, I did a batch of (only) 50 files in folders with short filenames and it worked flawlessly, so maybe we're getting somewhere there.
I should have the opportunity to do bigger batches this weekend. In the meantime, it would be nice if people who had this problem could give it a go too.0 -
I ran some tests with a (very) long path name to the source (raw) files. If the path is over 250 characters (approx.), CO4 does not open the files at all, clearly explaining the problem. If the path is approx. 200 characters long, it will open and start processing but stops with error mentioned by Luxart. The exact file in the queue (I queue exactly 100 images from a single folder) were processing stops varies, even with the same queue of images. A shorter path name (not determined a threshold) will run without problems (but the size of the queue might have influence but you do not process 200 or 2000 images in a single queue that often).
My assumption of a buffer overflow still stands. The buffer is reset when the application restarts.
My second assumption (for luxart) is that only a slightly shorter path name than you currently use might resolve the problem already.0 -
Well, I can live with short names, this is not a problem. And I suppose it will be fixed in an update anyway.
Thanks for your help, and regards.0 -
Hello
As a programmer I have had problem with filpath+name longer than 142 in total.
Roine0 -
Hello there,
I'm brand new to Capture One and have been very impressed until I ran into this problem. I use a Nikon D300 and have set my ICC Profile to D300/Generic. My source files are on my main hard disk as .NEFs and my target output is 16bit TIFF . I only downloaded the software yesterday from the downloads available on this site and my version is reported as 4.0.1.14900.14887. I'm running on XP (Media edition) with a duel core something or other and 2gig of main memory.
I've not yet managed to reproduce the ImgCoreProcess error yet with 8bit TIFFs or JPG conversions, though I am not convinced yet this makes a difference (only done about an hour testing so far).
My image sample consists of only 10 NEF files; sometimes it runs through giving me 10 16 bit TIFFs and sometimes it doesn't.
I have mixed feelings about the product so far. I feel that I want to commit as it offers me a great deal and would, I think, make a good addition to my workflow, but this error is driving me to distraction, which is to say, distracting.0 -
[quote="JohnJo" wrote:
[...]
My image sample consists of only 10 NEF files; sometimes it runs through giving me 10 16 bit TIFFs and sometimes it doesn't.
I have mixed feelings about the product so far. I feel that I want to commit as it offers me a great deal and would, I think, make a good addition to my workflow, but this error is driving me to distraction, which is to say, distracting.
John, could you be more specific about the error? BTW, if your error is not related to what is discussed in this thread, you might be better of starting your own.0 -
[quote="Paul Steunebrink" wrote:
John, could you be more specific about the error? BTW, if your error is not related to what is discussed in this thread, you might be better of starting your own.
Sorry Paul, it's the ImgCoreProcess.exe error which comes up during batch processing.
Interestingly enough I've been using Capture One 4 on and off all day while testing some new lights and it's worked perfectly since I reported the error. Not sure what has changed, different batch of images and I did delete the Capture One.col file manually at one point.
I've been sitting here taking screen caps for the last half hour trying different things to reproduce the bug for you guys and to provide more details but the bug has hidden itself away for now.
I'm getting to love the product and it's performance is great.
I'll get back to you if I can reliably reproduce the thing with, I hope, some screen caps and the like.0
Post is closed for comments.
Comments
51 comments