C1 6.2 NOT PROCESSING
I have .CR2 files in the capture folder. When I select all to process, in the queue it looks as if it takes less than a second to process each image(much much faster than normal), then queue empties. However, there are no processed files in the output folder. When I dragged the .col file into C1 6.1.1 everything processed just fine. What gives?
C1 Pro 6.2, OSX 10.6.7, MacBookPro, 2.66GHz i7, 8GB RAM
C1 Pro 6.2, OSX 10.6.7, MacBookPro, 2.66GHz i7, 8GB RAM
0
-
[quote="Neil62" wrote:
When I dragged the .col file into C1 6.1.1 everything processed just fine.
This quote is puzzling to me as well as scaring me. Do you have multiple installations of CO6 on your Mac? And what is 'dragging your .col file'? From what to what (I now that a .col50 file is the session file).
Tip: check your process recipe or better delete and create a new one.0 -
well, after restarting the computer all works as normal, sorry for the freak out! 0 -
I'm having the exact same problem, but even after restarting, the problem persists. Any idea what's causing this? I've been trying to process .dng files from a Leica M8, attempting to export about 200 .dng files as .jpg files. C1 acts like it's processing, but zips through them in about 20 seconds, with nothing actually exported. I've tried everything I can think of to troubleshoot the problem but have run out of ideas. Is there anybody else having this problem? 0 -
Does the Batch Queue show the images as ready to process? 0 -
No, it does not. Nothing shows up in the Batch Queue until I begin processing. It then flies through them at an extremely fast rate as though it's processing them, but nothing actually gets processed. I've tried reinstalling C1 6.2 several times, re-capturing my images into C1 again, and tried applying multiple process recipes that have always worked for me, but nothing works now. Is there some sort of hidden system preference file on the Mac that I can delete and force C1 to rebuild again, perhaps clearing up the problem? I'm running out of ideas. Thanks for any suggestions you can give me!
Glenn0 -
Update: I finally got it to work. I ended up creating a new session and re-captured my photos into the new session. I then tested it out by processing about 5 photos just to make sure it worked. It did.
I then spent quite some time reapplying all of my adjustments one photo at a time. When I tried processing them all, I ran into the same problem again. It zipped through them all within seconds without actually processing anything. I then decided to reinstall Capture One 6.2 and try processing the photos again. This time it worked, processing all 200 photos without any problems. Hooray!0 -
Hmmm... if you have the time to create a new support case and provide the LOG files for your software it sure would be good to have them for other users reference. 0 -
Thanks, Drew. I'll do that. Where would I find the LOG files you mentioned?
Glenn0 -
[quote="NN199084UL" wrote:
Thanks, Drew. I'll do that. Where would I find the LOG files you mentioned?
In <home folder>/Library/Logs you'll find CaptureOne*.log plus com.phaseone.*.log files
In <home folder>/Library/Logs/CrashReporter you'll find Capture One_<date>_<computer name>.crash files (I suggest you send in a few of the more recent)0 -
I really don't understand what is going on.....I am having a problem getting my Capture One Pro 6.2 to process (output) files similar to what has been reported here. While the program is building its images I can process a file but after it has completed the process, I click on "Process" and it sails through without processing the file. When I look in Batch History it shows that it was processed, but nothing happened. Tried all kinds of stuff, but the end result is the same.
One interesting element of note is that I receive a note that Capture One was not able to generate a preview on a file. I suspect that this is affecting the program. However, when I click "Show All" it shows me files not included in this Session/Folder. Even when I click "Clear" they still show up.?0 -
Although it doesn't let us (Phase One) know the cause of the issue, performing a clean uninstall and reinstall should resolve the 'zippy' process that leaves you empty handed.
http://www.phaseone.com/en/search/artic ... nguageid=1
Based on the description I would think the Image Core isn't initiated being initiated but without a support case and details I can't say for sure.0 -
Hi Drew and Paul_E,
I just submitted a new support case as you suggested, summarizing within the description the problem I was having. I also gathered up all of the Capture One log files and crash reporter files I could find and uploaded them within a .zip file. Hope the files are helpful to you.
Thank you both for all your help on this!
Glenn0
Post ist für Kommentare geschlossen.
Kommentare
12 Kommentare