Capture One 6.2 released
Today Phase One has released the long awaited/anticipated update of Capture One 6. Version 6.2 has some interesting functional improvements and enhancements besides bug fixes and expanded camera support. See the release notes for more details.
Some personal highlights:
Functional enhancements
- saturation and clarity in local adjustments (Pro/DB)
- copy local adjustment mask to another layer / invert local adjustment mask (Pro/DB)
- more camera controls for Canon and Nikon (Pro)
- extensive configurable warning preferences
- auto adjust includes white balance, is configurable
Cameras
Phase One IQ series of course, and Canon, Fuji, Nikon, Panasonic, Ricoh, Samsung and Sony cameras
Performance
Memory issues, OpenCL, 64-bit performance
I hope to discuss more details with you shortly and look forward to hear your experiences.
Some personal highlights:
Functional enhancements
- saturation and clarity in local adjustments (Pro/DB)
- copy local adjustment mask to another layer / invert local adjustment mask (Pro/DB)
- more camera controls for Canon and Nikon (Pro)
- extensive configurable warning preferences
- auto adjust includes white balance, is configurable
Cameras
Phase One IQ series of course, and Canon, Fuji, Nikon, Panasonic, Ricoh, Samsung and Sony cameras
Performance
Memory issues, OpenCL, 64-bit performance
I hope to discuss more details with you shortly and look forward to hear your experiences.
0
-
A note on installation of CO 6.2 for Windows.
First, it is best practice to uninstall the previous version of CO 6 before installing 6.2. In case you had any issues with a previous version or want to start with a clean bill of health, delete the default session file (Capture One.col50), the preference file, and clear the batch history. Note that this may cause session information to be lost so think before act.
Next, new for the Windows version of CO 6.2 is the requirement of Microsoft .NET Framework 4 (until now 3.5 SP1 was required). The CO 6.2 installer includes a web installer for .NET Fx 4. If you're system is not connected to the internet or you have multiple systems to update/upgrade to 6.2, it is better to download the full standalone .NET Fx 4 installer from the Microsoft web site and install .NET Fx 4 before CO 6.2:
http://www.microsoft.com/downloads/en/d ... 1f31ab88b7
You can select different languages before download.0 -
Hi Paul,
I've installed CO 6.2 like you said and .Net Framework 4 was already installed on my machine (Windows XP SP3).
After ten minutes of working with the program (several color corrections and fullscreen watch) I've got the famous "out of memory" crash. The visibility of the color corrections is also slower than in version 6.1.1.
I doubt that the real problems of the "out of memory" crashes are solved and I've noticed that in the Windows logfiles there are several RSVP-faults the moment the program starts.
René (The Hague)0 -
Hi René, I think it is best to report this to Phase One in a case, preferably with the crash log (they'll instruct you how-to if necessary) some hardware specs and type of raw files.
(oh yeah, The Hague, my place of birth I left just a few years ago 😉)0 -
I am glad 6.2 rectify the broken link between C1PRO and EM2. I see that 6.2 fixed a few bugs and one particular tiny bug I've reported. I am happy. 😊
I forgot to uninstall and did the 6.2 install over the 6.1.1 and no problems thus far. I did receive the dialog to download .NET 4 when I ran 6.2.0 -
Thanks for the heads up Ronald, I was curious about the EM2 link as I had not tested it myself. 0 -
I did my usual practice of leaving the previous version (for me 6.0.1) in place and installing 6.2 over it. It flagged me to install net framework which I thought I had - netdot 4 client profile 64bit. However you need netdot 4 extended (for me) as well, running win 7 64bit. so i installed it from the link.
No opencl problems. 6.2 is slower to open (about 10 sec, previously about 7 secs) with my sata HDDs, no SDDs yet! My support case re. import menu choices not being sticky is resolved, sticky now. The import window size and thumbnail size is still not sticky, c'est la vie! However so far so good.0 -
The release notes say 6.2 32-bit is compatible with WinXP SP3 , but the download page doesn't list WinXP for the 32-bit version. What gives?
(Also noted that the release notes say .net 4.0 is required, but the download page only says .net 3.5)0 -
The "Delete after import" check box has been fixed.
I absolutely love the localized clarity option! 😄 So many great uses for that!
Now all they need is localized noise reduction and be able to profile and automatically correct lens distortions. 😊0 -
[quote="Alex1111" wrote:
The release notes say 6.2 32-bit is compatible with WinXP SP3 , but the download page doesn't list WinXP for the 32-bit version. What gives?
(Also noted that the release notes say .net 4.0 is required, but the download page only says .net 3.5)
I notified Phase One already on the .NET issue yesterday, will add the XP 32-bit listing too. Thanks for reporting. The release notes are leading as source of information as far as I am concerned.0 -
Hi Paul, I'm glad we have a new version.
Now, how do I restore my personal workspace from 6.1.1 ?
Thanks.0 -
[quote="Jean1" wrote:
Hi Paul, I'm glad we have a new version.
Now, how do I restore my personal workspace from 6.1.1 ?
Thanks.
Window menu, Workspace?0 -
[quote="Paul_E" wrote:
Window menu, Workspace?
No, nothing there !0 -
[quote="Jean1" wrote:
[quote="Paul_E" wrote:
Window menu, Workspace?
No, nothing there !
Same thing here...installing 6.2 deleted my saved workspace...
Not a big deal though...I just made it again.0 -
No big deal indeed, but it would have been nice. 0 -
[quote="Jean1" wrote:
No big deal indeed, but it would have been nice.
Hey guys, are you using Pro or Express?0 -
I am using Pro 64-bit. 0 -
upgraded without any problems. Am still a happy C1 v6.2 user since long time.
regards
Martin
Photography Martin Steiner
Switzerland
www.martin-steiner.ch0 -
[quote="Jean1" wrote:
Hi Paul, I'm glad we have a new version.
Now, how do I restore my personal workspace from 6.1.1 ?[quote="Jean1" wrote:
I am using Pro 64-bit.
I just recalled that workspaces on Windows are stored in the user preference file, not in separate files as on Mac. Maybe this caused it not to be available after the update.0 -
[quote="Paul_E" wrote:
[quote="Alex1111" wrote:
The release notes say 6.2 32-bit is compatible with WinXP SP3 , but the download page doesn't list WinXP for the 32-bit version. What gives?
(Also noted that the release notes say .net 4.0 is required, but the download page only says .net 3.5)
I notified Phase One already on the .NET issue yesterday, will add the XP 32-bit listing too. Thanks for reporting. The release notes are leading as source of information as far as I am concerned.
Thanks Paul. That means I'll give 6.2 a go this weekend. I've long been waiting for the 'out of mem' fix so I can move to v6.0 -
I updated this morning and lost all my previously set shortcut keys that I had changed, also the quick toolbar had to be manually restored.
I've never had this problem before this update.
Never mind, no real damage done 😊
(Running Windows 7 & V6 pro)0 -
I had 6.2 32-bit (XP SP3) crash instantly when going full screen (Nvidia GTX275, 270.61 drivers), but uninstalling and reinstalling 6.2 seems to have fixed the problem (how, why...?).
PS.
- Not quite sure if I like the auto-hiding toolbar, an option would be nice.
- The local saturation adjustment is fantastic.
--
jk0 -
So Disappointed.
Fully clean install. Wiped all previous remnants of CO using the Phase One documented uninstall procedures. Deleted all .cof and .cop files.
Installed 6.2 Express 32-bit on WinXP SP3 system w/4GB memory. It only took browsing ~10 images until the 'Out of memory' dialog box appeared. What the? I've been waiting months for this release with a well documented service case and feedback there and in this forum this issue was being worked. Come on Phase One.0 -
Oh well...I had to switch back to 6.1.1
With 6.2 CO1 went so slow it was practically useless which is a pity...
(Win7)0 -
Express runs well enough on my Win7/64 bit/6 gb machine, but it's a bit of a kick in the teeth (though not remotely surprising I suppose, based on past experience) that Express users get none of the potentially useful, IQ-benefitting new toys to play with.
Yeah, there's vignetting - like that's going to be routinely useful for a bird photographer. For God's sake, of all the crumbs off the "Pro" table, did Phase One deliberately pick the most gimmicky, least useful one?0 -
[quote="Alex1111" wrote:
So Disappointed.
It only took browsing ~10 images until the 'Out of memory' dialog box appeared. What the? I've been waiting months for this release with a well documented service case and feedback there and in this forum this issue was being worked. Come on Phase One.
It is disappointing to see the Out of Memory error still alive. I briefly played around 6.2 with 1 or 2 photos and the log still said memory was leaking:2011-04-30 17:28:27.453 (0x10c4) | ############################## CaptureCore Log File Started ##############################
2011-04-30 17:28:27.468 (0x10c4) | Initializing Capture Providers
2011-04-30 17:28:27.484 (0x1124) | Thread 4388 (0x1124) started [P1 Cam Finder - monitor thread]
2011-04-30 17:28:27.531 (0x1114) | Thread 4372 (0x1114) started [Event dispatcher thread]
2011-04-30 17:36:56.468 (0x1114) | Thread 4372 (0x1114) exited [Event dispatcher thread]
2011-04-30 17:36:56.484 (0x1028) | TERMINATING CaptureCore
2011-04-30 17:36:56.484 (0x1124) | Thread 4388 (0x1124) exited [P1 Cam Finder - monitor thread]
2011-04-30 17:36:56.484 (0x1028) | Error: CaptureCore object leak detected. 5 objects not released.
2011-04-30 17:36:56.484 (0x1028) | ------ CaptureCore terminated ------0 -
[quote="Urukhai" wrote:
[quote="Alex1111" wrote:
So Disappointed.
It only took browsing ~10 images until the 'Out of memory' dialog box appeared. What the? I've been waiting months for this release with a well documented service case and feedback there and in this forum this issue was being worked. Come on Phase One.
It is disappointing to see the Out of Memory error still alive. I briefly played around 6.2 with 1 or 2 photos and the log still said memory was leaking:2011-04-30 17:28:27.453 (0x10c4) | ############################## CaptureCore Log File Started ##############################
2011-04-30 17:28:27.468 (0x10c4) | Initializing Capture Providers
2011-04-30 17:28:27.484 (0x1124) | Thread 4388 (0x1124) started [P1 Cam Finder - monitor thread]
2011-04-30 17:28:27.531 (0x1114) | Thread 4372 (0x1114) started [Event dispatcher thread]
2011-04-30 17:36:56.468 (0x1114) | Thread 4372 (0x1114) exited [Event dispatcher thread]
2011-04-30 17:36:56.484 (0x1028) | TERMINATING CaptureCore
2011-04-30 17:36:56.484 (0x1124) | Thread 4388 (0x1124) exited [P1 Cam Finder - monitor thread]
2011-04-30 17:36:56.484 (0x1028) | Error: CaptureCore object leak detected. 5 objects not released.
2011-04-30 17:36:56.484 (0x1028) | ------ CaptureCore terminated ------
Both please report to Phase One. I know they have put considerable effort into this but there is always room for improvement.0 -
Of course I will report. I know they have been trying, but also realize I and others have put more than several hours into this too, hours could be working on photos instead. Supporting a support case takes a lot of time with all the data collection, uninstalls, re-installs, testing on images, etc. all the while losing set ups, etc. because of clean installs over and over again each time PO asks to test something else. I work in v5, then try 6.x, then go back to v5 the asked to try something else, repeat, over a dozen times. I am almost losing interest in going thru this again after 6.0, 6.0.1, 6.1.1 and now 6.2 as I have after all these months of waiting and hours of test&input getting nothing better. 0 -
Alex, you frustration and disappointment are understandable as much as your effort is appreciated. 0
Post is closed for comments.
Comments
53 comments