Capture One 8.0.1 stopped processing images
Hi,
a support ticket has already been created but I am wondering if anyone else ran into this issue. I have a catalog with appr. 40 GB size and roughly 1250 images. I made my selection and adjustments and filtered only to the one's that I want to process. It worked fine for the first 20 something images and my next batch process started, seven images were processed and opened in Photoshop but the remaining 8 images started to hang. I stopped and cleared the queue and even restarted my MacPro (2010) with no success. Capture One is no longer responding and if I force to quit and restart I am not able to process any images any more. Very sad as I have to deliver some images for a magazine.
I am currently copying the catalog to my external hard drive and try to process the files through my MacBook Pro.
Peter
a support ticket has already been created but I am wondering if anyone else ran into this issue. I have a catalog with appr. 40 GB size and roughly 1250 images. I made my selection and adjustments and filtered only to the one's that I want to process. It worked fine for the first 20 something images and my next batch process started, seven images were processed and opened in Photoshop but the remaining 8 images started to hang. I stopped and cleared the queue and even restarted my MacPro (2010) with no success. Capture One is no longer responding and if I force to quit and restart I am not able to process any images any more. Very sad as I have to deliver some images for a magazine.
I am currently copying the catalog to my external hard drive and try to process the files through my MacBook Pro.
Peter
0
-
It is no longer working on my MacBook Pro Retina either and other catalogs show the same behavior. Very strange. Everything worked well yesterday and this morning and all of a sudden on two machines which has not received an update are no longer processing images. 0 -
Interestingly I can process images from session but catalogs seem no longer to work. Nothing has changed 😕 0 -
I'm having the exact same problem but in sessions. Same thing on 2 different computers, a late model iMac and a late model MBP both running 10.9.4. Tried a clean reinstall but no help. Same behavior in different sessions. If I go back to 8.0.0 processing works fine. The files are from a Nikon D810. Wondering if that is part of the problem?
Andrew0 -
Now the same problem is happening with 8.0.0 it just takes a little longer before it starts to happen. I'll have 7 or so successful processing queues before it starts to happen.
Andrew0 -
Please let us know how the support cases shake out - but in the mean time, have you tried clearing the batch queue before processing?
Theoretically it shouldn't matter, but I've found it very helpful to check this when I begin having issues with processing files (or if Capture just begins to crash for no apparent reason).
You can find the batch queue in the finder by navigating to /[Username]/Library/Application Support/Capture One/Batch Queue 5.1/
Just delete the contents of the batch queue directory and re-start Capture One and give it another go.0 -
[quote="brianmerwin" wrote:
Please let us know how the support cases shake out - but in the mean time, have you tried clearing the batch queue before processing?
Theoretically it shouldn't matter, but I've found it very helpful to check this when I begin having issues with processing files (or if Capture just begins to crash for no apparent reason).
You can find the batch queue in the finder by navigating to /[Username]/Library/Application Support/Capture One/Batch Queue 5.1/
Just delete the contents of the batch queue directory and re-start Capture One and give it another go.
Hey Brian,
Thanks for your suggestion! I did try deleting both the "Batch Queue 5.1" as well as the "Batch Queue 8.0" but to no avail.
Andrew0 -
Hi all,
I have not received a response from Phase One support. I am wondering if my ticket went nowhere. All my attempts to get my catalogs back to work failed so far. What helped was to export all images from the catalog including the adjustments and create a new catalog. I'll see how this turns out when I am going to batch edit images. Files are either from my Nikon D4s or my D810. It stopped working with the D4s files...
Peter0 -
Paul's suggestion to delete the <session name>.cosessiondb file and then recreate it in the same place in this post: viewtopic.php?f=55&t=17304
seems to have, at least temporarily solved my problem working in sessions. I think similar to your creating a new catalog, Peter. However since the problem has happened on 2 different computers with several different sessions I suspect it is going to happen again when whatever happened to trigger it in the first place happens again. Hope they come up with a fix for it soon as rather inconvenient to have to create a new session and lose session favorites each time.
Andrew0 -
Is this happening when OpenCL for processing is set to "never", or is it set to "auto"? Just wondering if this is a GPU issue. 0 -
I make a few observations about the issue 'can not process or export, while it was working fine before':
- user has updated to 8.0.1
- user has Nikon D810 files (as far as posters have reported their camera file type)
- reverting to 8.0.0 does not help
- replacing the session db file helps (temporarily?)
- takes place with both session and catalog
I see a parallel thread at here:
viewtopic.php?f=55&t=17304
I will post this in the other thread too.0 -
[quote="dale11833" wrote:
Is this happening when OpenCL for processing is set to "never", or is it set to "auto"? Just wondering if this is a GPU issue.
OpenCL is set to never for both processing and display.0 -
Now even creating a new session db file doesn't do anything! Complete nightmare as I've got a big job to process out today and can't do any processing! Been a couple of work days and haven't heard back from Phase yet on my support case other than asking me for my logs which I got to them right away.
Andrew0 -
[quote="PhaseoneUser78210" wrote:
Now even creating a new session db file doesn't do anything! Complete nightmare as I've got a big job to process out today and can't do any processing!
Andrew
There are some things you can try if you're under the gun.
1. Fresh install on a different Mac. (Don't have one, buy a used Mac Mini cheap)
2. Backup - save off preferences, customizations, Delete C1, ReInstall
3. Install v7.
4. Get a backup RAW processor like Lightroom and configure it for these worst-case scenarios.
One of these has to work. Having been a professional software tester for many years I would never trust a dot zero release, especially these days of Agile and easy delivery of updates.
When a software company can get a fix out at no cost to them, there is no need for a dot zero release to be perfect. Ask Apple about that.
We have to understand this. The boxed release is no more!0 -
[quote="NNN634394493605690167" wrote:
We have to understand this. The boxed release is no more!
Ditto that for all the subcomponent software, conjoining applications, operating systems and device drivers ...
It's a miracle that anything ever works at all - especially where clients are pushing developers to operate at the leading edge of the technologies available to them.
Grant0 -
[quote="NNN634394493605690167" wrote:
[quote="PhaseoneUser78210" wrote:
Now even creating a new session db file doesn't do anything! Complete nightmare as I've got a big job to process out today and can't do any processing!
Andrew
There are some things you can try if you're under the gun.
1. Fresh install on a different Mac. (Don't have one, buy a used Mac Mini cheap)
2. Backup - save off preferences, customizations, Delete C1, ReInstall
3. Install v7.
4. Get a backup RAW processor like Lightroom and configure it for these worst-case scenarios.
One of these has to work. Having been a professional software tester for many years I would never trust a dot zero release, especially these days of Agile and easy delivery of updates.
When a software company can get a fix out at no cost to them, there is no need for a dot zero release to be perfect. Ask Apple about that.
We have to understand this. The boxed release is no more!
Thanks for the suggestions Mark!
I have tried fresh installs on two different computers as well as clean reinstalls but no luck. I did go back to LR to get the processing done but major headache as there were well over 100 images that all had to be retweaked individually as LR obviously can't read the CO changes I did.
I'm with you on the dot zero releases but it's the only way at the moment to shoot tethered with my D810. Absolutely love the camera, just need to get some software to play nicely with it now.
Andrew0 -
>> I'm with you on the dot zero releases but it's the only way at the moment to shoot tethered with my D810. Absolutely love the camera, just need to get some software to play nicely with it now.
Andrew - I see. That's another dilemma.
I guess that's just another point to consider with the workflow. Buying new hardware that isn't yet supported puts more strain and uncertainties on the workflow. I can't blame Phase or Adobe for that. They need time to build in support.
As they say "You're damned if you do, damned if you don't..."0 -
I too am having these problems. I too am using a D810 (two of them). I work solely in sessions. I have an edited, colour corrected session... All captures are separated within their shot folders. I send each shot folder to batch process and thats when the software stalls. I'm on an iMac 2014, 3.5 i7, 32gb RAM. Im running 10.9.5
It either crashes (spiny wheel, no response from finder), or it successfully adds the files to the batch library, and doesn't process them - this is indicated as the timer just grows and grows in time!
I had this problem on set last week. Fortunately i had my MBP 2014, 2.6 i7, 16gb running 10.9.5, so my DT was able to transfer the session and process for the client on this computer, so that the client could leave with job completed as intended! Im now having the same problem today, from an job edit earlier this week, but thankfully at the moment i'm in the comfort of my office working within a comfortable deadline.
This is not good though... I'm off on a trip next week with all this kit and there doesn't seem to be a solution. I am about to open a ticket with Phase now...
NOT GOOD.0 -
[quote="NN130526UL" wrote:
I too am having these problems. I too am using a D810 (two of them). I work solely in sessions. I have an edited, colour corrected session... All captures are separated within their shot folders. I send each shot folder to batch process and thats when the software stalls. I'm on an iMac 2014, 3.5 i7, 32gb RAM. Im running 10.9.5
It either crashes (spiny wheel, no response from finder), or it successfully adds the files to the batch library, and doesn't process them - this is indicated as the timer just grows and grows in time!
I had this problem on set last week. Fortunately i had my MBP 2014, 2.6 i7, 16gb running 10.9.5, so my DT was able to transfer the session and process for the client on this computer, so that the client could leave with job completed as intended! Im now having the same problem today, from an job edit earlier this week, but thankfully at the moment i'm in the comfort of my office working within a comfortable deadline.
This is not good though... I'm off on a trip next week with all this kit and there doesn't seem to be a solution. I am about to open a ticket with Phase now...
NOT GOOD.
You can try and process in 8.0.0. This work around is inconvenient but seems to work most of the time.
Andrew0 -
Same here! I tried to change the camera model in the files with Exif Editor from D810 to D800 and it worked. Maybe it was just luck for teh moment…?
Is there any reply from PhaseOne?0 -
This is triggered by "some" D800 and by the looks D810 images.
Currently having the issue with multiple images in a batch but can process the images, all D800, around the offending image.
If I shut down C1 after removing image that hung batch I can process. This is one by one.
Does not appear to matter what file the conversion is to, TIFF, JPG and PSD all hang.
A C1 restart is required.
It will not process a clone variant of the offending image.
Images where taken as part of a set, same day, same card, same process.
Doing a document Check against the session DB does not help, repair not selectable.
If you manually kill 45888 "C:\Users\<USERNAME>\AppData\Local\CaptureOne\Logs\ImgCoreExternal.log" -- C:\Program Files\Phase One\Capture One 8\ImgCoreProcess.exe and restart C1 WITHOUT removing the offending image from the batch process, on a restart of C1 the image is processed at startup.
To kill ImgCoreProcess.exe I used a tool call Process Explorer on Windows, you would need to go into Terminal in OSX and identify the PID of the process and issue a kill -9 command (if allowed)
Hope that helps resolve the issue
When C1 has hung it appears that ImageCoreProcess.exe remains in memory, having to be manually killed. When there has not been a batch hang ImageCoreProcess.exe terminates as it should.0 -
If you have one problem image I would guess that somehow somewhere there is a bad link in the database to one of the files listed as being related to it. A small glitch in the internal index might be pointing to nothing at all or to a file for a different edit. All sorts of strange things could happen.
I would suggest taking a safe known backup specifically for this processing task and the delete the variant(s) for the suspect file. You may need to re-edit anyway if on of the related edit files is the problem. You could try copying the variant edits one by one to see what happened if applied to a new variant but that may take longer than a re-edit. It would depend in how much you have done to the files.
For others in a similar situation there may be a similar solution if the problem file(s) can be identified. Odd looking thumbnails might be a clue but there could be other ways to spot them as well.
No guarantees that this will help in some way but it's worth checking.
HTH.
Grant0 -
There appears to be a number of minor glitches in version 8, specifically around processing multiple files and I suspect (no evidence, just gut) that this may be trigger something like the corruption Grant speaks of.
On reprocessing the batch again (successfully completed after manual intervention) the process hangs on a different file. This file may have caused problems earlier but I did not notice it being stuck, but the process definitely gets stuck on the file I mentioned in an earlier post.
ImageCoreProcess remains active.
Same process - Close C1, Kill Image core process, reopen and the remaining images are processed.
Will look at testing Grants method tomorrow0 -
That description sounds very similar to a problem I had a year or so back with V7 (The only time I have had such a problem)
I had not got to the stage of processing but during edit - having dived through a set of about 2000 images in a session picking a few samples to distribute, I went back to working through the full set.
C17 crashed. I re-started and carried on for a few files and it crashed again - when scrolling along the files in the browser in my case. This went on with this session (but no other) for some time and I could find nothing obviously wrong. No matter where I started to work n the session list (file name order) it would eventually freeze after a random but low number of edits.
Eventually, about 1/3 of the way through the entire set I spotted by chance a bad thumbnail about 2/3 of the way through the set. I tried to regenerate it and it came out the same as before. So I deleted the edit variant (not the original RAW file of course!) and went back to my editing taks which now allowed me to scroll through files without problem to complete the task.
Returning to the problem file I made a new edit, the thumbnail looked good and the file processed. Job done.
I have no idea what caused the problem to appear but I am quite certain that the cause of the problems was some form of corruption of the index or a file to which it appeared to point. I have only seen the problem that one time.
This was on a Windows machine but there is no reason to suppose that the same sort of issues could not occur on a Mac.
If the effect for some reason is an issue with the process queue it could still be unrelated to the perceived problem files - just like mine was. When browsing I could, in effect, "delete" or skip the last image with which I had had a problem and carry on until the next occurrence. The key to the full resolution seemed to be finding the source of the problem which may not be that easy if "Regenerate Previews" and "Check Document" or whatever tools are available don't spot the problem - which they may well not if it is as rare a thing as it was in my case.
HTH.
Grant0 -
For those of you that created support cases for this issue, Thank You. They were of great help in narrowing down this rather elusive issue.
This issue has been identified as a Bug and the rather obscure cause found. It seems that a small scaling bug in Capture One 8.0.0 specific to the D810 support, which was fixed in 8.0.1 is what is causing the conflict.
D810 files edited and processed in only Capture One 8.0.0 will not see this issue.
D810 files edited and processed in only Capture One 8.0.1 (i.e never touched by 8.0.0) will not see this issue
Only files edited in Capture One 8.0.0 and processed in Capture One 8.0.1 will see this issue. We will have a fix in the next update for Capture One shortly. Until that time please simply process using Capture One 8.0.0 to avoid this conflict.0
Post is closed for comments.
Comments
24 comments