"Cannot develop" error w/layer enabled
Using 6.1.1 on win7-64 2core intel proc. 3MB memory, nVidia Geforce 8400 GS vidcard
The program will not develop any image which has an adjustment layer active. I get this helpful message: "Cannot develop filename.ext"
When I disable all layers, the development proceeds normally, albeit without the layer. I had encountered this with earlier versions but didn't pay much attention since I use photoshop for fine adjustments, and had hoped the glitch would go away in subsequent versions.
I noticed on another thread that Capture one needs .net 4 -- according to Control Panel, I am fully up-to-date, with the latest updates installed 6/22/2011.
Has anyone else seen this ( a search ofthe forum turned up nothing). and if so, is there a fix?
Thanks,
Walter Hawn
The program will not develop any image which has an adjustment layer active. I get this helpful message: "Cannot develop filename.ext"
When I disable all layers, the development proceeds normally, albeit without the layer. I had encountered this with earlier versions but didn't pay much attention since I use photoshop for fine adjustments, and had hoped the glitch would go away in subsequent versions.
I noticed on another thread that Capture one needs .net 4 -- according to Control Panel, I am fully up-to-date, with the latest updates installed 6/22/2011.
Has anyone else seen this ( a search ofthe forum turned up nothing). and if so, is there a fix?
Thanks,
Walter Hawn
0
-
If I recall correctly I have seen one earlier report on layers - processing. This user had to select the background layer before processing. Not sure it was on Win or Mac. You could try that.
One issue that might cause this is your amount of RAM. If I read your post correct, you have 3 GB RAM in your machine with Win7 64-bits. That is not great fun. Any chance of extending it to 4 or 8 GB if your wallet and hardware allows it? Or load as few applications as possible when running CO6. Can you test with one image in a folder, point CO6 to that folder, restart your computer, open CO6 again and process?
Next, have you considered updating to CO 6.2.1 (current version)?
CO 6.2 and later need MS .NET Framework 4; CO 6.1.1 is still happy with 3.5 SP1. However, I do not think this is a .NET Framework issue.0 -
Okay, I can't tell the difference between a "G" and an "M"! 😊
I tried all the ideas you presented and a few of my own, and still get the same result. BTW, my mobo will let me go only to 4GB.
Also, didn't mention this, because it's been an ongoing thing since v5: I get, at startup of C1, this message: "ImgCore Socket Error -- an invalid argument was supplied." I click on the ok button and things go on. It became a habit to hardly notice this, and there seemed to be no ill effect. H'ever, it occurred to me that a configuration file may be to blame, but such is not the case, at least in regards to the 'user config' file. Are there others, and, if so, where can I find them?
Frankly, for my work, the layers thing is not all that important, nor is the added camera support, as I use a phase1 back and no other serious digi camera. I use PS for everything beyond color-and-exposure correction, so I may simply revert to an earlier version. I had thought to do all my processing in the Adobe RAW converter, but C1 seems to be both easier and to give better results.
Regards,
Walt0 -
[quote="WalterHawn" wrote:
...
I get, at startup of C1, this message: "ImgCore Socket Error -- an invalid argument was supplied." I click on the ok button and things go on.
Do you perhaps have a 3rd party firewall installed, either as part of a internet security package or stand-alone, like McAfee, Symantec, ZoneAlarm? This might cause this error.0 -
I do, but have given permission for C1 to get through. Though why it needs to phone home with every start, I'll never understand. 0 -
[quote="WalterHawn" wrote:
I do, but have given permission for C1 to get through. Though why it needs to phone home with every start, I'll never understand.
It is not about phoning home (which is not required to start the program by the way). CO6 (and 5, and 4 as well I believe) connect to the local home address 127.0.0.1 which is the network stack on the adapter. I think it is to check whether there is a active network connection anyway. Some firewall programs inadvertently prohibit this. You should give CO6 permission to this address.0 -
[quote="Paul_E" wrote:
You should give CO6 permission to this address.
Have now done that both globally and specifically for C1. Still getting the ImgCore Error.
BTW, C1 has no trouble accessing my network. I keep the image files on a server and have had no problems.
\\'alt0 -
A (nasty?) firewall and image files on the server. Either one of both may cause your layer processing error:
In a trial-and-error attempt, you could try to process an image file stored on a local drive and switch your firewall off (either one and both).
Note that the issue (as I assume there is) regarding the local address does NOT affect network access.
Sidebar: you run Win7 x64: I dare say the Windows' firewall is better than (most) 3rd party firewalls on the market. Even worse, in a recent test of quite a heavy computer magazine most 3rd party firewalls made it easier to compromise the machine than with Windows' own firewall alone. Those firewalls were great on Win XP, not on Win7.0 -
Walter,
I do not know how to solve your problem. I can only say I have HP with AMD x2 processor and 2GB RAM and all seems to be OK. Yes, processing is a bit slow (in a few days I will have the latest Intel i7 based computer 😉 ) but everything else works well. No problems on start up or during the work. I have Norton Internet Security installed. All my work is on home server, however I always work off the local (PC HD) drive, purely for speed purposes.
Have you tried to reinstall the C1? Work from local drive? And as Paul said - make sure firewall is not th ecullprit of your issues.0 -
[quote="Paul_E" wrote:
you run Win7 x64: I dare say the Windows' firewall is better than (most) 3rd party firewalls on the market. Even worse, in a recent test of quite a heavy computer magazine most 3rd party firewalls made it easier to compromise the machine than with Windows' own firewall alone. Those firewalls were great on Win XP, not on Win7.
I admit it: I've not paid attention to the computer press for several years. I was an MS technical beta-tester from win98 through Vista. It was at Vista that I became disgusted with MS's attitude toward the testers and the general public, and dropped out of the testing program. The firewall on Vista was a horror during the beta and the overall OS was such a pain that I never installed my copy on a production machine. (Which mag reviewed the firewalls? Might want to check the article.)
H'ever, win7 has been considerably better in many respects -- mostly in interface design, rather than any changes to the kernel -- but I simply went with a 3rd party firewall, as a matter of course, because... MS's efforts in that regard were, uh, ludicrous in days gone by. You have prompted me to investigate the new firewall, and it is by far superior in design to anything I'd seen before from MS.
Now, to the nut: It was the firewall -- PCTools Firewall Plus -- causing the errors. I'm on the win7 firewall now and C1 is working just fine, with lots of images showing in the browser, with no error messages, and it seems to run faster, too. That may be an illusion, but it's a nice one to have.
Thank you both for your help.
Regards,
\\'alt0
投稿コメントは受け付けていません。
コメント
9件のコメント