Capture One missing curves

[fotoism]

Advertisement (gone after registration)

I cross-posted on another forum in the hope that I will get help from as many people as possible. Here is my problem:

 

I have been using Capture One on my Win XP machine for a long time (moving up from C1-3 to the current C1-5.2.1) with no major problems. Then I built a new computer with Win 7 64 bit and installed C1 on it after deactivating C1 on the old computer. Installation went well, but when I opened C1 and went to my files some of them were not showing any curves or had the slide-bars grayed out. Some would show no color in the color balance circle. Some showed only the histogram and nothing else, and the entire EXIF page was grayed out.

 

It is sporadic: some files are okay but some files not, even in the same folder. Then there are some folders with all files not showing anything. This happened on DNGs as well as TIFF and JPEG files. Totally random and I cannot even find a pattern what works and what doesn't. Some had a little eye on the thumbnails and some don't, but that doesn't make a difference whether it would work or not.

 

I tried installing the trial C1 v.6 (64 bit) and the same thing happened. I have since uninstalled the trial C1 v.6, went to registry and cleaned out everything Phase One or Capture One related, and reinstalled C1 v.5.2.1. Still the same.

 

There ware no error messages. Things just don't show up the way they should, or have the adjustment grayed out.

 

Is it a known problem that C1 v5 cannot run properly in Win 7 64 bit environment becasue it is 32 bits? My other 32 bit programs seems to run okay though.

 

Here are some specs, if relevant: Win 7 64 bit, Intel Core i5 2500k (2nd gen.) CPU with integrated graphics, on-board H67 video chip with maximum shared 1748MB memory, 2 x 4GB DDR3 memory, SSD system drive and one 7200rpm internal and two external data drives.

 

Any suggestions (other than telling me to go buy a Mac)?

[MitchoIankov]

Hi, Phil I use C1 v.5.2 on Win7 64-bit with no problems.

 

If you have 'Enable JPEG Editing' or 'Enable TIFF Editing' check boxes un-checked (Edit/preferences menu ; Image tab) then you get everything grayed out (not working) for these types of files.

 

For DNG files it should work fine.

[fotoism]

Those boxes were checked, but no dice. Even the DNG files are acting up. Why are the little gray eyes showing up in lower right corner of the thnumbnails?

[jaapv]

Delete and reinstall.

[george +]

C1 can be tricky. But it is worth the effort.

 

Have you tried Phase One Support? They are about the best that I have seen.

They respond fast and will stay with you until the problem goes away.

[fotoism]

Jaap:

Thanks for the reply. I did tried uninstalling and clean reinstalling several times, I even cleaned out the registry entries every time in between, didn't work.

 

George:

Thanks. I contacted support yesterday and I got a reply this morning. They told me to uninstall and do a clean reinstall, pretty much the same as what Jaap said. But I tried that and did not help.

 

However, I found out something else I am going to share here, just in case it could be of any use to other forum members. Following is my reply to Phase One support:

 

-----------------------------------------------------------

I have tried clean uninstalling a couple of times already exactly as described, even going into registry and delete all data pertaining to Capture One or Phase One before each new installation. The results have been the same. Some folder/files were blocked and some others were accessible. The blocked files include DNG, TIFF, and JPEG, dating from the most current to years back.

However, I just tumbled into something I have not tried before and it seems to be working somehow. I went to the captureone.exe file and under the compatibility tab I checked off the box before "Run this program as an administrator". After I checked that off and restarted C1, the little eye icons were gone from the files and I had once again full access to all files.

How this works I don't know. How this would affect the files or other programs I don't know. And how safe it is to run a program at this highest privilege level I don't know. There are no other programs I need to do this in order to run in Win7 64bit, not even 32 bit programs. The fact that it allows some files and deny some files is really strange, and I hope your software engineer can figure out if there are some compatibility issues hidden deep underneath which would surface unexpectedly under certain conditions. I know this may not be a reproducible thing but I have been struggling to get it up and running again for the past several days.

I got a lot of advice from people telling me to uninstall and reinstall, which I tried many times to no avail, so there might me something more to do with installation. The installation files are direct downloads from PhaseOne website and it worked before I move from winXP to win7 x64, so it could not be the installation package being corrupted. I even tried a fresh download of a trial C1 v.6 and it did the same thing. One thing stands out is that this privilege level check box is only in win7, not in winXP, so I never had to worry about it. Maybe that makes a difference?

Although I seem to be able to get it up and running, I still appreciate input from you as what else could be the real reason. My worries is I don't know if my "fix" could lead to any future problems, whether to Capture One software, to other software, or to the OS as well.

This is a really weird case and I appreciate your looking deeper into it for a root cause.

Regards,

Philip

 

--------------------------------------------------------------

 

What an experience but I hope something good comes out of it.

[michael_b_elmer]

Advertisement (gone after registration)

Why use a 32 bit programme on a 64 bit machine when you can get a 64 bit programme?Why not deinstall once more and install the newest Capture One Pro ver 61.1. 64 bit

[fotoism]

Two reasons:

1. when a perfectly working program started to have problems after switching platform I want to at least know why, instead of just throwing it out the window right away and go buy new stuff, and

2. I am happy with C1-5.2.1 as it is and don't want the extra outlay of cash to get the new version with features I do see the need at this moment.

 

Also, as I mentioned before, I had downloaded C1-6.1.1 x64 as a trial and it also did not work. The same symptoms came back just the same, so it is not a 32 bit vs 64 bit or C5 vs C6 problem. BTW, all my other 32 bit programs still work the way they used to be under 64 bit and none required administrator privilege to run.

 

Your suggestion is not rejected, though. I may still upgrade at a later date, but not at the moment and not for this reason.

[george +]

Hey Phil, you are not alone. We have a few things in common:

 

On a previous version PhaseOne Help suggested installing as administrator - and it worked; on version 6.1 I had to go to the 32 bit version - and it worked; and we both built our own 64 bit W7 computers.

 

At any rate, I like C1 a lot and find their support outstanding. They keep on working at problems and version 6.1.1 works fine for me in 64 bit mode.

 

What does this tell about the future? Love as I love them, I may not rush to install new versions of C1 on day one.

[fotoism]

George:

If you are in win7 x64 I really don't think they should tell you to use x86. After my reply above they came back and said they had nothing more to look into, it's a windows problem. I suspect that might be the case so I investigated further. And I found new information.

 

I have been running my OS and apps off an SSD and have a second HDD for data. I also have a couple of external data HDD for my image files. I found out I actually did not have to run the C1 as administrator (which PhaseOne support said is recommended).

 

The fact that my files are on an external HDD makes a difference how Win7 looks at them. I have to grant permission for win7 to access those files. So I did, and voila! All files are now accessible without running C1 as administrator!

 

Like you I love C1 and I hope it gets better and better.

 

I understand on many photo forums Mac users out-numbered win users, and maybe for good reason. I just hope whatever information I shared here is of some use to someone somehow someday, that's all.

[jaapv]

Great you got it working - and boy, am I glad I switched my home computer to Mac recently I must confess I run my PCs on XP pro and plan to keep them that way as long as possible...

[fotoism]

Jaap:

 

I read about your crossing the floor earlier on and I was thinking maybe I should too, because at that time I was looking at upgrading my computer as well. I didn't. This is my "punishment", I guess.

 

Joking aside, I am glad it's now working and I learned something new along the way. Thanks.

[ho_co]

... This is my "punishment", I guess....

It's not "punishment" so long as you're capable of finding the problems and sharing the solutions! More power to you!

[perb]

I went to the captureone.exe file and under the compatibility tab I checked off the box before "Run this program as an administrator". After I checked that off and restarted C1, the little eye icons were gone from the files and I had once again full access to all files.

 

I think the "little eye icons" signify restricted file access/permissions.

 

Rather than executing as an administrator, you should look at the files in your file system and set the file permissions such that your normal UID (User IDentity; the login name of your ordinary user) has sufficient file access. This usually means full read/write access.

 

0. As administrator, always uninstall the older version before upgrading (just in case, though you should be able to have several versions in parallel)

 

1. As administrator, install new version of C1.

 

2. Always run C1 under your normal UID.

 

As long as you follow the above you will hardly see any problems, except, of course, regular bugs

 

Regards

Per

[fotoism]

Per:

That's what I did in order to resolve the accessibility issue (eye icon = read only) with my files. I do not normally run programs as administrator unless I absolutely have to. As I mentioned in my earlier post, I finally narrowed it down to a permission issue and granted my folders full permission under my user ID, and that was the trick that worked. I never had to do that in win XP but apparently Windows 7 has some new security features previous versions didn't have, you just have to know where to look and tweak it. Now I do.