3.6 Does Not Work with 1DMKII
I processed about 1000 files from my recent event shoot last night with the new software. 20D files were nice as were the 10D. However, the main two cameras - 1DMKII - produce output files (800 of them) with a severe doubling and distortion along the bottom edge for horizontal and right edge for vertical. None of the out put can be used. About 10% of the frame is bad. It happened for both cameras on two different computers. I tried several different color spaces, profiles, scaling, output file types . . . . Nothing works.
-
This seems like a case where you should take to http://support.phaseone.com where you can upload a file and we can verify it and see where the problem lays. -
The problem seems to have happened ONLY on files that had been previously opened in v3.5.2. I had started to work on the files and then updated to 3.6. I continued to work the files and the preview was great. However the files were bad. I had a card in my camera with some photos that had been processed the day before. I took some new pics on that card. The new files processed fine, the old ones still were in error. I TOTALLY wiped out my install of v3.5.2 (keeping a backup . . . ) and installed 3.6 like no previous versions of C1 had ever lived there. All file process fine now (at least the few I tested individually). It has something to do with installing 3.6 into the same folder where 3.5.2 had lived.
Thanks for the help. Perhaps this and the file I sent will help others. I had to re-edit the 800 files. Bummer. They are developing now in a batch. I hope everything is REALLY fine. If not, I'll let you know.
Bobby -
I'm experiencing the same problem. It seems like all the conversions from the old .work files pointing to my EOS 1D MII images are corrupt. Nothing is wrong with my D60-images.
I tried renaming my preview folder and made a new one with the same old name, so C1 was forced to generate new work- and preview-files. Now there's nothing wrong with the processed images.
But all my settings, whitebalance corrections, exposure corrections etc is lost and I will have to start all over with several thousand images.
I really hope that PhaseOne can and will do something about this. I've been a very satisfied C1-user up till now, but I most say that I'm a little shaken right now ☹️
Best regard,
Kim Biledgaard -
Thanks for the input. I sent several files to the support folks. Luckily, I was caught up on processing except for that one event. I spent about 4 hours re-working what I lost. I have been waiting on this release so I can take the 20D off the shelf and use it as a backup! Perhaps I should have waited just a tad longer? In any case, the support response was very quick and sincere. I believe they will find and fix the problem soon. I'm not so sure we'll get an update that soon though. I really like using C1 and don't plan to slow down. I have v3.5.2 working as well now just in case.
Take care,
Bobby -
Same here, new files convert just fine, older files (with *.work files instead of the new *.C1w format) are visible but impossible to re-process.
I tried to re-convert a CR2 file, the progres bar showed the computer was busy, but no file was saved. Very, very strange.
I then looked in to the preview folders and saw that the new work files have a different extension than the old ones (*.C1w instead of *.work).
I moved the old *.work files to a different directory and restarted 3.6 PRO. Strangly enough, even though I moved (not copied) the old *.work files to another directory, my settings were still present and the conversion still didn't work. I closed C1 again and now deleted all the *.C1w files with todays date. Now all my settings were gone and the conversion succeeded.
This is a serious bug. I hope they get it fixed soon so I can copy back my old work files. -
I had a problem when I did the installation of the Pro version the program didn’t find the profile of the Mark II, and indeed the profile was not in the menu. I installed the 3.52 SE version again en the problem was gone. Now the profile of de Mark II is in the menu of the 3.6 Pro version.The Pro version is working properly with older files processed with the 3.52 SE in the past and with the new files I shot recently and processed only by the 3.6 Pro version.
Greetings.
Jeff C. -
[quote="hvr_oosterzele" wrote:
Same here, new files convert just fine, older files (with *.work files instead of the new *.C1w format) are visible but impossible to re-process.
I tried to re-convert a CR2 file, the progres bar showed the computer was busy, but no file was saved. Very, very strange.
I then looked in to the preview folders and saw that the new work files have a different extension than the old ones (*.C1w instead of *.work).
I moved the old *.work files to a different directory and restarted 3.6 PRO. Strangly enough, even though I moved (not copied) the old *.work files to another directory, my settings were still present and the conversion still didn't work. I closed C1 again and now deleted all the *.C1w files with todays date. Now all my settings were gone and the conversion succeeded.
This is a serious bug. I hope they get it fixed soon so I can copy back my old work files.
I have exactly the same problem and I know several users with the same.
As well there still is the problem (only with MK II) files that in some cases (it seems to be on pictures taken under thungsten light) the colour of the previews does not look like the ready pictures. Colourmanagement is enabled. The same picture done in 3.5.2. is ok ! -
Is this what you all are seeing?:
http://andersenfamily.homestead.com/files/C1SE36_issue.jpg
For me it doesn't matter if it's an old or new image, and happens regardless of the camera settings or C1 RAW development settings...It doesn't happen when I develop the RAW in PS CS, so it's certainly a C1 bug...
This really upsets me....Any ideas yet on a fix yet, or how to go back to previous versions??
😡 -
[quote="SouthFla" wrote:
Is this what you all are seeing?:
For me it doesn't matter if it's an old or new image, and happens regardless of the camera settings or C1 RAW development settings...It doesn't happen when I develop the RAW in PS CS, so it's certainly a C1 bug...
This really upsets me....Any ideas yet on a fix yet, or how to go back to previous versions??
😡
Yes it ist - and again NO ANSWER from PO ❗️ -
This morning from Phase One Support: This is a know conversion problem we have between 3.5.2 and 3.6. Please reset your settings at the specific file that have this problem by clicking workflow-> selected capture setting-> reset in the menu.
Worked for me, hopefully for you all as well 😄
YAY! -
[quote="SouthFla" wrote:
This morning from Phase One Support: This is a know conversion problem we have between 3.5.2 and 3.6. Please reset your settings at the specific file that have this problem by clicking workflow-> selected capture setting-> reset in the menu.
YAY!
But that meens you loose all your old settings ?! 💡 -
I got a prompt reply from the support team :
\"Hi. Thanks for your patience. We have confirmed a bug with compatibility of the older .work and .preview files on v3.6 that affects some users, although I can't say why some people are affected and some are not. The problem causes the batch queue to stall, that is the files won't be converted.
I cannot say why you were able to see your settings changes even though you moved the work files out of the Preview Cache. Perhaps you chose an intermediate step prior to moving them that copied your setting into a new .C1w file such as Restoring Archive from the Workflow menu.
In any event we are working on a update that will solve the problem. We hope to have it out shortly.
I have marked the case as closed. You can simply reply to reopen it.
Phase One Support\" -
[quote="SouthFla" wrote:
Is this what you all are seeing?:
For me it doesn't matter if it's an old or new image, and happens regardless of the camera settings or C1 RAW development settings...It doesn't happen when I develop the RAW in PS CS, so it's certainly a C1 bug...
This really upsets me....Any ideas yet on a fix yet, or how to go back to previous versions??
😡
This only happens if you have old previews in the preview cache, apparently. If you have a clean install in a new directory you shouldn't see this at all. If you're installing over the previous directory you need to clean out the preview cache (and maybe the old work files) to avoid this.
Bill (no problems with my 1D M II's but I'm not using old work files and have 3.6 in a separate directory)
Please sign in to leave a comment.
Comments
16 comments