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
-
Trial-and-error troubleshooting: clear batch history, repair permissions (Disk Utility). If that does not help: clear Capture One cache and preference files. 0 -
Okay. I'll try the lot and see if it helps.
Thanks,
Brion0 -
I had the same problems sometimes when I had Media Pro running. Once I closed it and restarted C1 it worked fine again. 0 -
Same problems, tried to process but nothing happened. Clearing batch history and preference files helps, but after few times of processing ( or restart of CO, or booting system, couldn't find a certain event ) problem comes up again. Happens on the MacPro i7 AS WELL AS on the MacBook Pro i5, both OS 10.6.7. Repair Permissions didn't help.
Anyone else? Solutions?0 -
same problems.
no solution but restarting c1 all the time.
frustrating …0 -
Same here! Also no solution but restarting. Annoying. 0 -
I had this problem twice in the last week. And only C1 was running. It seems it appeared since 6.2 or so. No idea why. Anyone already sent in a ticket for support request? 0 -
Is everyone having this issue using 10.6.8?
Since it is a new update and made changes specific to the way RAW files are read by the OS it may be directly related to this issue. From the few cases we've had that seems to be a consistent theme so if anyone can chime in with whether or not this error corresponded to the recent Mac update it be worth looking at.0 -
I use 10.6.8 and it I think it started with the OS updated. 0 -
Now that you mention the update to 10.6.8 my system is consistently locking up with C1 being the main program I am running. This is a new behavior on my machine and it could be the update of the OS. 0 -
Anyone brave enough to give this a try to see if it resolves the issue?
https://discussions.apple.com/message/15510907#15510907
Just curious at the moment as no one seems to want to take the risk, I'll give you $1. 😉0 -
Drew-
Make it a free upgrade when C1 version 7 comes out and you are on.0 -
Ran into this issue today first time. CO Pro 6.2.1, 10.6.8. After some editing, process queue ran but no images in the output folder (earlier same day, all worked fine). I closed CO 6, which required a force quite without logging crash data, started it again and all was back to normal.
Drew, I can run tests on 10.6.7 which ran fine for months. Problem is that the issue is intermittent on my current 10.6.8 setup.0 -
[quote="Paul_E" wrote:
Drew, I can run tests on 10.6.7 which ran fine for months. Problem is that the issue is intermittent on my current 10.6.8 setup.
Paul,
That may be but we never had any reports of this issue prior to the release of 10.6.8.
Doug,
My offer stands at $1 and or a 1% discount on an upgrade cost of $99 😉0 -
Drew...
Never hurts to "try" and negotiate... 😂0 -
I believe it has been since I upgraded to 10.6.8 that this issue has become more frequent but I have seen it happen very occasionally over the last few of years. So rarely though, that I usually just wrote it off as an uncommon glitch, restarted and everything was fine. 0 -
My MacBookPro 2,1 with 10.6.8 is 100% broke. Nothing I have tried including all the suggestions from support will let me write a processed image.
I have another MacBook2,1 at 10.6.7. It only has 1MB memory so I'm going to upgrade it to 2 and my pro to 3 then try C1 Pro 6.1 on both.
I'm surprised and disappointed that this product has this behavior, i.e. it records the processed file into the log, produces no error message or log entry but does not write the file. I am a professional programmer and this seems like an unhandled exception, one of the most common programming flaws. There should also be better tools to debug this, for example a way to turn on extensive logging.
As soon as I receive the memory I'll test the two OS-X versions and give an update.0 -
[quote="PhaseoneUser452" wrote:
...
I have another MacBook2,1 at 10.6.7. It only has 1MB memory so I'm going to upgrade it to 2 and my pro to 3 then try C1 Pro 6.1 on both.
Thanks for the heads-up. You might even update your CO 6.1 to the current 6.2.1.
FYI, I run a MBP 2,1 with 3 GB RAM and 10.6.8. I have occasionally encountered this no-output error. A restart of CO Pro 6.2.1 solved it for me each time. When the error occurs, the system is already swapping heavily pages to disk due to RAM constraints when I use both CO Pro and PS CS5 simultaneously.0 -
Sorry.. I mis-entered the release. I am using the current realease 6.1.2 0 -
I just can't get it right..6.2.1 Makes me wonder what else I'm doing wrong. 0 -
try re-setting the output folder. -1 -
And try CO 6.2.2 although I am not sure this issue has been targeted in this release. 0 -
I installed 6.2.2 and the results are the same...no output file. I created a new empty directory, selected it for output, and nothing goes there, same as before.
To say the least, this is very dissapointing. I used C1 v4 for several years with no issues. This version, and 6.2.1 are completely broken and no apparent fix in site. I don't even know if is being worked on. My hardware meets described requirements. In fact, I used to always run C1 and PS and other things open as well. If a system runs out of RAM it will be slow as it swapps jobs out of memory but C1 should not fail to perform a key function with no warning or error. I have not experienced such a gross failure of a professional software product for many years and never on the Mac.
I have memory upgrades on the way and once installed I can check both OS-X versions.
I certainly appreciate everyone's help and hope this is resolved soon. I have about 1000 raw files waiting on this and I have no other way to process them. I just love C1 when it works and don't want to go to the expense and learning curve of something else.
Thanks,
Don0 -
Do you have anything set in the advanced tab? Have you tried creating a new recipe? 0 -
Where do I find the Advanced Tab?
I have created several processing recipes but still no output.
I received my memory upgrades and have performed the following tests:
I upgraded my MacBook Pro to 4GB RAM. It is running 10.6.8 and C1 Pro 6.2.2. This is the original system with the problem (nothing written to the output file upon 'Process')
I also upgraded another MacBook to 2GB RAM. This system is running 10.6.7 and first-time C1 install (pro 6.2.2). I tried it both as a 'trial' and with my license key. My first action was to set OpenCL to never.
Results: The MB Pro with additional RAM shows no change (still no output file).
The new MB had never had C1 installed before this test.
I copied over a few .DNG raw images to a newly created directory. I created a new empty directory. C1 processed these images including output correctly.
I then connected my 'real' USB drive with my 1000 or so images. Still using the source images copied over, I pointed output to the folder on the USB drive to make sure there was no problem with the folder permissions. C1 correctly wrote output to this folder. The MB Pro would not write a single image here.
The Third and final test was to open a folder of images on the USB drive. I began processing using my normal workflow with output to the same folder on the USB drive and everything worked correctly for exactly 25 images, then the output stopped with exactly the same behavior as before, i.e. the wheel spins for a second or so, no progress bar, and no output file.
I rebooted and restarted C1, and just one image was correctly processed, then stopped again. A second reboot and no image output.
How can this be! What do I do to get a refund?
I don't believe in such software voodoo. The only real function / purpose of this software is to write a tiff or jpg image of the original raw image. This, above all else, should just work. I don't believe system reboots or software restarts should ever be necessary. We've (not me) accepted that as the first standard debug step because of Windows. OS-X is a Unix system very similar to Linux. My Linux laptop has not been rebooted in more than a year and everything works. Before C1 I've never had to reboot my Mac. I've never had an app fail on an OS version upgrade, PhotoShop, SilverFast and many others. What's going on? (Forgive my ranting, I'm just at wits end with this.)
Thanks,
Don0 -
[quote="PhaseoneUser452" wrote:
Where do I find the Advanced Tab?
The Process Recipe tool, where you select Format, Compression and so on, has three tabs: Basic, Advanced, Watermark.0 -
Now I remember seeing that tab, but I don't think I made any changes there.
I'll double check all this when I get back to my system this evening.
thanks0 -
On the Advanced Tab I have root folder set to Output Folder, sub name and sub folder blank, and all checked except include rating.
I have tried setting to specified folder and to input folder. I have also unchecked everything.
Nothing helps. I have also created various new recipes and new output folders. Everything seems to work, subfolders created, but never an output tiff.0 -
Just an idea (sorry if I missed it): create a new user account on your Mac and give it a shot with a few images... 0 -
Thanks for the suggestion. I'll give that a try.
However, I believe I did that with the fresh install on my other system. That was in effect a new account.
Also, support just suggested that I move off of the USB drive, which is where all my images and output is located.
The testing on the second system using the local hard drive worked but I only tried two images. It then worked on the USB drive for 25 images before it stopped.
I use the USB drive extensively with Photoshop and SilverFast. I've been scanning 5x7 negatives which creates almost giga-byte files and then edit with PS. Everything works perfectly except of course rather slow due the hugh size.
I therefore doubt the problem is USB related but will perform this test as well.
I will move some images directly from the camera card into a fresh folder on the hard drive and will do all of this under a newly created account. I'm going to do this on both OS-X versions using C1 6.2.2.
Any other suggestions? I'm simply guessing, and I'd think support could do a lot more than that, but for this to work correctly for 25 images and then suddenly stop hard seems like something somewhere, probably a parameter of configuration file, has become corrupted. It's odd that a reboot then resulted in one image being processed correctly before it stopped again.
This is just crazy!0
Post is closed for comments.
Comments
48 comments