PDA

View Full Version : Capture One 3.7 Questions


drisley
13th of June 2005 (Mon), 03:42
I've been using PS CS for my conversions now for quite a while, and I have prefered the output and workflow over Capture One.
However, I've heard so many good things about the ETC Profiles for Capture One, I've been giving the 3.7 trial a go.
Question...

In the preferences, I've changed the default Noise Suppression, Banding Suppression, and Default Color Saturation settings to my liking.
However, none of these changes are reflected in the C1 Browser windos (Focus Tab and Exposure Tab).
CS (saturation) stays at zero, and the Noise and Banding sliders stay where they always were. I've tried restarting C1 Pro, and tried a fresh batch of images, but none of the preference settings seem to matter. Is this a known bug?

the.digital.guy
19th of July 2005 (Tue), 20:11
I've been using PS CS for my conversions now for quite a while, and I have prefered the output and workflow over Capture One.
However, I've heard so many good things about the ETC Profiles for Capture One, I've been giving the 3.7 trial a go.
Question...

In the preferences, I've changed the default Noise Suppression, Banding Suppression, and Default Color Saturation settings to my liking.
However, none of these changes are reflected in the C1 Browser windos (Focus Tab and Exposure Tab).
CS (saturation) stays at zero, and the Noise and Banding sliders stay where they always were. I've tried restarting C1 Pro, and tried a fresh batch of images, but none of the preference settings seem to matter. Is this a known bug?


Check this link out for some answers:
http://forum.phaseone.com/index.php?sid=4bd17b86cc40277bcba41daafc792700

wintoid
19th of July 2005 (Tue), 23:54
Have you tried File->Preferences->Preview Cache->Clean up the preview cache now?

Just a guess.

drisley
20th of July 2005 (Wed), 09:20
Wintoid and tdg, thanks for responding.
Somebody in the phaseone forum pointed out that the changes will only apply to images that have not been opened in C1 Pro before. It's very odd, but it does now work with my new images :)