Process Queue Runs but no Images are Produced
Has anyone else seen this strange issue I've been noticing lately? I couldn't find a reference to it in the forums.
Sometimes, when I select an image or a group of images to process and then click the process button, they will populate the process queue and run through BUT very quickly and nothing is actually produced in the process folder.
A restart of the application usually fixes this.
This is worrisome. Most of the time I process large batches after setting all my adjustments and it is easy to notice that the process folder is empty. But sometimes I like to set adjustments and run images one at a time and, unless I carefully watch the queue, it is almost impossible to notice that they never processed.
For the record, I am using CO 6.2.1 on a MacPro 2x2.66 GHz Quad-Core Intel Xeon with 12GB of RAM. My operating system is 10.6.8. Open CL is turned off.
Thanks,
Brion
Sometimes, when I select an image or a group of images to process and then click the process button, they will populate the process queue and run through BUT very quickly and nothing is actually produced in the process folder.
A restart of the application usually fixes this.
This is worrisome. Most of the time I process large batches after setting all my adjustments and it is easy to notice that the process folder is empty. But sometimes I like to set adjustments and run images one at a time and, unless I carefully watch the queue, it is almost impossible to notice that they never processed.
For the record, I am using CO 6.2.1 on a MacPro 2x2.66 GHz Quad-Core Intel Xeon with 12GB of RAM. My operating system is 10.6.8. Open CL is turned off.
Thanks,
Brion
0
-
I'm embarrassed to say it looks like a session configuration issue.
Support suggested I move off the USB drive so I carefully went thru all the steps to create a new session and recipe, along with newly created folders on the hard drive. I copied over a few images and everything worked perfectly. I began to move back to the USB gradually by creating new sessions, and at each try everything worked.
I haven't exactly figured it out but it seems there was some inconsistency with folder settings between the session and recipe.
In any case, I still think it is a 'bug' for C1 to write to the output log that the image was processed when in fact something went wrong and the image could not be written, even in the case of mis-configured folder settings.
Thanks for everyone's assistance, especially PhaseOne support!0 -
I am stuck at this point with many files to process. What is the work around 0 -
Well I just found the answer to my issue. I had two forms of tagging (color and Star) and I could not process the files. After force quitting the software and restarting it and removing all forms of tagging I was able to start a new queue of images and fully process the images without any further problems. There must be a software glitch.
Glad to have gotten it figured out!0 -
Well. I lied. Stupid software got stuck again! 0 -
One last very interesting issue I found was that the activity viewer showed 4 "imagecoreprocesses" working rendering my system unuasable (basically). Wow Phase One you are memory hogs as you don't shut down the software after a crash fully.
What is going on. Please help!0 -
Shawn,
Please follow up with the currently active support case.0 -
I am in a current support case. I however am not at a place of resolution yet. I think I am getting close but am awaiting another response! 0 -
I am having the same problem. From reading this thread I deduce that 1. if you have some inconsistencies in your session set up that can cause it to crash. 2. If you have any form of tagging or two different kinds of tagging that can cause it to crash.
Why doesn't Capture One tell you if there's a problem like that? Where's the error message?
Capture One support have advised me to upgrade to version 6.2.2 but there's nothing in the notes to that version about this issue. And I don't know whether that will wipe all the files that I spent 3 days working on. (I had to go through 2 days of my assistant's work over the weekend because it somehow got wiped over when I applied settings from one image to an other and it applied them to the whole lot. Partly my fault, but I'm new to this software and why no warning again? It's too easy to make mistakes with this software.)
I am in the situation of having to show a client some images tonight that I cannot finish because Capture One keeps having problems. I've been up two nights in a row trying to fix this. I've scarcely seen my children for days. Not happy!
Come on Capture One, this is a great piece of software but you need to sort this out before I leave the house in about 40 minutes time, so i can run the damn files! thank you!0 -
[quote="NNN634484229989164102" wrote:
...
Capture One support have advised me to upgrade to version 6.2.2 but there's nothing in the notes to that version about this issue. And I don't know whether that will wipe all the files that I spent 3 days working on.
There are only a very few things I am sure of in my life. One of them is that updating Capture One 6.x to a later release does not affect any adjustments made with the previous version.
Go 6.2.2.0 -
This just happened to me yesterday. I was shooting on location and my client wanted a few jpegs to play with on his machine. I started processing the files and turned around to shoot. Next thing C1 would not process files from the open session at all. The queue would populate and then empty in just a few seconds. So I felt like somehow the settings in the session were corrupted. Checked another session and things worked fine for awhile but soon no session I opened would process files.
Today I played around with this and eventually my studio machine was also not processing due to the corrupted session. Both machines are running 10.6.8 and C1 6.2.2 I opened a case with P1 and was instructed to do a clean install of C1 which I did. The results were the same. On a side note I had to deactivate and for some reason P1 had my old product code in their records so I could not activate again until I changed the code to the new C1 6 code. Not wanting to give up in the middle of a busy week I went back to the batch queue tab which I had previously cleared and stopped then restarted the queue. Success C1 is now processing files from the corrupted session and any other, I will update if the problem returns.
So I am thinking this is a bug in C1 since both my machines were functioning perfectly and were both taken down by the same incident and session.0 -
I believe it is a memory issue. C1 is an absolute hog. Try to open activity viewer and start working with files. Watch what C1 does to your memory. It takes an incredible amount just for the program then another program called "coreimageprocess" (or something close to that) opens up when you do anything almost equal to the program size so all the sudden the program is using 4Gb of info leaving very little for other programs. I have 8gb in my macbookPro and I can watch my memory go to about 1gb or less. Crazy. I think they need to get this figured out a little better in terms of memory use and leaking! 0 -
I think it is related to a corrupted session since I have 8gb in my MBP and 16gb in an 8 core Mac Pro. This behavior first appeared in the Mac Pro when I attempted to process from the corrupted session and no other programs were running. I also am now able to process from new and old sessions without a problem.
So from my perspective it started when I was shooting tethered while the software was processing or possibly when we attempted to process from a second session while the first corrupted session was processing. Either way the prompt appearance on both machines with one particular session to me indicate that session was somehow corrupted.
I often create multiple sessions one the same day to prevent a loss of performance. Say after lunch do a restart and create a "B" session for the job to minimze the amount of files we are dealing with.0 -
Just a small note. I've had this same problem with OSX 10.5.8 and CO 6.2 so it's not limited to Snow Leopard machines. Restarting CO has worked with me. 0 -
Well, bought an update from C1 v5 to v6 last week and got this problem to.
First it worked okey, but when I installed Media pro it started to give some trouble. And now it doesn't work at all. After trying all night I only got 2 images proceced. So no idea why some images do and some images don't get proceced.
Removed media pro from my computer, reinstalled C1 and even made an new session but nothing works.
I tried to understand some of the solutions given above, but am no real computer expert. Someone can give some things to try?
And is it possible to still use my old licence from C1 v5 since I updated it to 6?0 -
[quote="NN161480UL1" wrote:
...
And is it possible to still use my old licence from C1 v5 since I updated it to 6?
Yes. (this part of your post was easiest to answer...)0 -
Okey, thanks. So if the need is really big, I can always go back to C1 v5. Not ideal, but its possible 😊
This morning I tried C1 again before going to work but nothing happened. No picture was procesed...
Since I did not had this problem a week ago I think it has something to do with installing media pro. So I want to completely remove both C1 and MP from my computer and install C1 only.
I uninstalled C1 before but when I installed it again still some presets were present in C1, and the serial code was there to.
How can I completely remove C1 and Media pro from my system? Are there any extra maps of things I have to remove to get a fresh start?
And, offcourse I will keep my photofolders with the C1 adjustments files. Don't want to have to procs all the images again. When I make a new start, what is the best way to re place those images? Just put it in the C1 folder? or import the images again and than replace the C1 adjustment files?
I really hope this will help, or that there will be a fix soon. Really frustrating to buy a 220 euro upgrade to see it doesn't work.0 -
Uninstalling the software does not affect the activation or your images and their adjustments. A more thorough description of uninstalling CO6 can be found here:
http://www.phaseone.com/en/search/artic ... nguageid=10 -
Okey,
I got it working again.
First completely removed C1 and media pro. Including all extra files.
Threw out all libraries I had.
Than reinstalled C1 and again it didn't work with a serie shots from Berlin, but worked with new imported shots.
When I opened the berlin shots in C1 I got the message thumbnails could not be generated. So went trough the berlin shots and fond four DNG's from 2 mb while all others are mucht bigger.
So threw them away, restated C1 and finally it works.
Now processing a lot of pictures to see if it keeps working but hopefully I got the troublemaker...0
Post ist für Kommentare geschlossen.
Kommentare
48 Kommentare