CO1 6.2.2 corrupting output files/folders
I have already made a support case, but haven't received any reply as yet. I had just installed 6.2.2 and processed a number of P45+ files into TIFFs. At first I could open the files in Photoshop, but soon discovered I could not save them with their original name (after some editing'. I could save them under a different name in the same folder. It also turned out I could not delete those files although I had manually removed, or at least tried to remove, any protections (there weren't any). Now the entire folder/directory can no longer be accessed and seems severely corrputed. I have never had this problem before. Can anyone help? Files processed into JPG do not have these issues.
I am using Windows 7 64/bit, but my laptop with Vista 32/bit, has exactly the same problem, which leads me to believe it must be CO1 causing these problems.
Thanks
Piet Gispen Photography
http://www.pietgispen.com
I am using Windows 7 64/bit, but my laptop with Vista 32/bit, has exactly the same problem, which leads me to believe it must be CO1 causing these problems.
Thanks
Piet Gispen Photography
http://www.pietgispen.com
0
-
While I still haven't been able to do a system restore (no restore point preceding the installation of the upgrade), I have managed to get CO1 6.1.1. working again (after all it does not make use of WIC as CO1 62x is doing, apparently without the knowledge of the Danish Support Team).
I found out that somehow my Wacom Tablet/Pen may be involved in these problems. There seem to be known issues between WISPTIS.exe and the use of the pen. Anyhow WISPTIS.exe is having a conflict with the CO1 wrapper.dll found in the WIC. It is all getting a bit complicated and I had rather be doing my work instead of spending hours getting my software to work. Even re-installing 6.2.1. didn't do the job, most likely because I cannot go back with Windows 7. This makes me fear for CO1 6.2.3.
In my case the Phase One Support Team seems to think the work on their part is done. I no longer get answers. It is very frustrating.
Piet0 -
[quote="Piet12" wrote:
...In my case the Phase One Support Team seems to think the work on their part is done.
Once an issue as in your case is acknowledged and passed on to R&D, the support team closes the case as their job (1st line of support) is done. That does not imply that they think your issue is solved, but is being taken care of at the next level.
Hope this helps to understand.0 -
[quote="Jim MSP" wrote:
[quote="Gilles" wrote:
Jim,
did you reboot after reinstalling the 6.2.1 ?
Probably not. However, I did reboot after I did a system restore.
Jim,
I suspect a loop somewhere on your system, or a variable in memory corrupted, which had no reason to return in a normal state, except with a reboot (or only a close of the session). But I admit that, after reading all issues, I decided to restore, me too.
The title is wrong : I found no corrupt files/folders at all : but the behaviour of files access was corrupt.
So, it is finished now, the 6.2.1 works okay here, the Event Viewer is all in blue, I know that PhaseOne is working, end of story.0 -
[quote="Piet12" wrote:
While I still haven't been able to do a system restore (no restore point preceding the installation of the upgrade), I have managed to get CO1 6.1.1. working again (after all it does not make use of WIC as CO1 62x is doing, apparently without the knowledge of the Danish Support Team).
I found out that somehow my Wacom Tablet/Pen may be involved in these problems. There seem to be known issues between WISPTIS.exe and the use of the pen. Anyhow WISPTIS.exe is having a conflict with the CO1 wrapper.dll found in the WIC. It is all getting a bit complicated and I had rather be doing my work instead of spending hours getting my software to work. Even re-installing 6.2.1. didn't do the job, most likely because I cannot go back with Windows 7. This makes me fear for CO1 6.2.3.
In my case the Phase One Support Team seems to think the work on their part is done. I no longer get answers. It is very frustrating.
Piet
Piet,
You say that CO 6.2.x uses Windows Imaging components ? Where ? 😲 I am sure of one thing : WIC with ICC profiles I have made with Argyll and an X-rite colorimeter, makes all blacks level disappeared in the 0 level. At level 17/255, it is 30% darker than the normal grey (down to 11/255). The only way to retrieve a linear gray scale is to clear the screen profil, or to set the sRGBIEC61966 profil. But it is another topic. Just to say that if CO was using it, I should see it... lol. I bought mainly Capture One for the wonderful debayering, his color management, and the very professionnal approach.
And, Piet, I dare : may be you should see why you do not have snapshots anymore. It can be useful.
Kindly,0 -
[quote="Gilles" wrote:
Jim,
I suspect a loop somewhere on your system, or a variable in memory corrupted, which had no reason to return in a normal state, except with a reboot (or only a close of the session). But I admit that, after reading all issues, I decided to restore, me too.
The title is wrong : I found no corrupt files/folders at all : but the behaviour of files access was corrupt.
So, it is finished now, the 6.2.1 works okay here, the Event Viewer is all in blue, I know that PhaseOne is working, end of story.
Gilles,
You may be right, but I really don't recall.
Anyway, I am like you - this is the end of the story for 6.2.2 for me, and I will await 6.2.3. I will continue with 6.2.1, recognizing that it still has memory leak issues which lead to crashes or lock ups.
But before I install that new version, I will set a system restore point; just in case. 😉
Jim0 -
Just to keep everyone updated with my saga, in the hope it may be of some use. Today I decided to do a complete Windows repair, i.e. reinstall Windows 7 by running the upgrade again, which re-installs the complete system, but without affecting data and programs. I had hoped that would help. After several hours of installing updates etc, I uninstalled CO 6.1 and installed 6.2.1 (NOT 6.2.2.). Very much to my dismay, the problem had not gone!! This time I made sure I had a system restore point, although it probably isn't of much use since the problem is still there. At least I can use 6.1. I'll process my X100 files with Lightroom. It does make me wonder what will happen once 6.2.3 is there; will that solve my problems, or will I have to do a complete re-install of everything costing a number of days and a lot of hassle.
Piet0 -
I followed the advice uninstalling 6.2.2 and back to 6.2.1 (I had no good win recovery point), and now Capture 1 works.
But If i try to enter a directory Capture 1 have cached, with either the explorer or any other program they will crash.
My computer now is utterly useless and needs a reinstall from scratch it seems :/
/M0 -
I haven't read through this entire thread, so this may not be the same issue, but I purchased CO Pro today and I'm pretty pissed. It seems I cannot move files without a few (sometimes it's one, sometimes more) files refusing to move. I get the "this file is in use or was left open" error.
I thought I finally resolved this by properly using sessions, but that doesn't seem to be the case. I ended up editing one photo and processed it to the output folder as a tiff assuming I could get some work done. Of course that's not the case as it will not save over the same file.
I'm extremely frustrated and angry, especially since I have a big shoot this weekend, but mainly for the fact that I just spent $400.00 on a program that doesn't seem to work properly and wasted pretty much an entire day trying to fix it.
I'm on Windows 7 and I've never had issues like this, ever.0 -
Hi all
Here is the temporary solution
http://www.phaseone.com/en/Search/Artic ... nguageid=1
It will be fixed in next release.0 -
[quote="Ulf" wrote:
Hi all
Here is the temporary solution
http://www.phaseone.com/en/Search/Artic ... nguageid=1
It will be fixed in next release.
Before I do this, do you know it it effects Media Pro ?
Jim0 -
[quote="Ulf" wrote:
Hi all
Here is the temporary solution
http://www.phaseone.com/en/Search/Artic ... nguageid=1
It will be fixed in next release.
And maybe a short description of what that temporary solution does to my computer?0 -
[quote="digitalgene" wrote:
[quote="Ulf" wrote:
Hi all
Here is the temporary solution
http://www.phaseone.com/en/Search/Artic ... nguageid=1
It will be fixed in next release.
And maybe a short description of what that temporary solution does to my computer?
From a non-authoritative source: it disables the Phase One WIC extension by removing the relevant registry keys. You should apply the suggested workaround as a user with administrative privileges and I would advise to reboot afterwards.0 -
I'd settle for knowing how I'm supposed to "run" it... 0 -
[quote="Keith Reeder" wrote:
I'd settle for knowing how I'm supposed to "run" it...
If you refer to the WIC workaround: it is a *.reg file, a.k.a. a registry file. Double-clicking on it executes it with the Regedit program. Of course you can right-click on it and choose to open it with Regedit and load/execute it manually.0 -
I have installed the work-around and it just works. Thank you Phase One for this quick service after a most unfortunate mishap. I really appreciate it. Whatever it exactly does I don't know: it just does what it is supposed to be doing.
Regards,
Piet Gispen0 -
Double-clicking wasn't working, Paul - Windows just tried to open it as a text file - but explicitly opening it with Regedit did the trick. 0 -
This problem has more to do with Microsoft Explorer locking files. It's not Capture 1 problem. Here is a link to Microsoft Forum on this issue http://social.technet.microsoft.com/For ... 85d7a6c851. Customer Support sent me a reistry edit and you also have to disable indexing. Program will run fine after this fix. 0 -
[quote="Ulf" wrote:
Hi all
Here is the temporary solution
http://www.phaseone.com/en/Search/Artic ... nguageid=1
It will be fixed in next release.
Thank you Ulf.0 -
Thank you Phase One. The workaround works. 0 -
Dear Ulf,
I have the same problem as the above folks and have a support case. The "WIC" workaround did not work for me. Once I downloaded it, I just double clicked it to execute the file. A popup window said my registry was edited successfully but I'm still having problems. I'm not sure if I did the workaround correctly (since I'm a newbie with those things), but it looked good. Do you or anyone else have any suggestions for me? Thanks in advance.
Jaz0 -
LIke Jaz I continue to have the problem (on a 32 bit system) with locked files despite apparently succesfully running WIC and getting confirmation of successful registry edit.. 0 -
[quote="Jaz" wrote:
Dear Ulf,
I have the same problem as the above folks and have a support case. The "WIC" workaround did not work for me. Once I downloaded it, I just double clicked it to execute the file. A popup window said my registry was edited successfully but I'm still having problems. I'm not sure if I did the workaround correctly (since I'm a newbie with those things), but it looked good. Do you or anyone else have any suggestions for me? Thanks in advance.
Jaz
That's basically why I went back to 6.2.1, as I use a lot of other software on the same computer and I cannot afford to have any file issues. I also had to restore the Win op system to a state before I installed 6.2.2
6.2.1 continues to run pretty well, though it occasionally still hangs up trying to refocus on a photo. I have not been able to correlate this hang up with any particular #files, commands used, etc. My gut feeling is that these hangups are like those in Media Pro - the software cannot handle more than a couple of stacked commands that it hasn't processed yet.
So I slow down and let it catch up.0 -
I'm sure all Windows users having this problem with files after researching the problem for pass two weeks and reinstalling Windows7 64, and installing one program at the time come to find out it's a CO1 creating a problem at this time and few other programs. Here is a solution for now uninstall CO1 so you don't loose your files and check for the other programs. Problem is not CO1 it's Windows. Recently Windows did their regular update to Framework 4 and that did it. Some one has to fix it at the moment it seems like dead end can't use CO1 on the possitive note Lightroom works. Here some info from Microsoft http://support.microsoft.com/kb/2263996 0
投稿コメントは受け付けていません。
コメント
53件のコメント