C1Pro 8: Fuji S5 Pro output bug
Capture One Pro 8 Fuji S5 Pro output bug
The Fuji S5 Pro is a 6 MP DX camera with a high dynamic range. C1 is advertised as to support the Fuji S5 Pro and has a very nice new HDR feature. Therefore, the use of Capture One Pro on raw files from the Fuji S5 Pro seems promising.
However I found that C1 cannot correctly make use of the Fuji S5 pro RAF format.
How to reproduce the bug in four simple steps:
1. In C1 open the Fuji S5 Pro RAF file, taken with the dynamic range > 100%, e.g. 400%. You can detect those images by their file size (about 25 MB). These RAF files store the information from the cameras' R- and S-pixels.
2. Auto adjust the image by clicking on A (surprisingly, this gives a slightly different result when selecting Menu > Adjustments > Auto Adjust.).
3. In the Exposure Tab increase High Dynamic Range > Highlight to 100%. For example, this can give a "blown out sky" back its nice blue color. Really impressive!
The histogram also indicates that you could regain information from the highlight side. Very good. Especially the levels curves (red, green, blue) clearly show how C1 will recover "blown out" highlights!
But now, you of course want to *output* the enhanced image. Here is where Capture One Pro 8 fails.
4a. Look at the filmstrip below the Preview. You already can see that all the light greens are turned to a different, darker green. Or:
4b. Take the loupe tool (P) and hover over light green or blue areas. The loupe not only increases details to 100% to check for sharpness, but surprisingly the colors change to a darker tone: dark green, dark blue! Or:
4c. Save the image as a simple JPG (or TIFF, PSD), what everbody wants to do:
- JPEG 80%, sRGB, 300 px, 100% > Process
The resulting output is way different than the adjusted original! You can easily compare the images after re-importing the JPG and displaying them in multi-view side by side. And compare the leves curves.
5. To my surprise saving the images as "JPEG QuickProof (sRGB)" retains the nice adjustments without any shifts in brightness. This reinforces my impression that C1 has an easy to solve bug in the output handling of adjusted RAF raw files from the Fuji S5 Pro.
Conclusion: While Capture One Pro 8 obviously can nicely handle the high dynamic range of Fuji S5 Pro raw files (RAF) in memory, the resulting output to JPG etc. is flawed. I do hope it is only a minor bug that can be solved quickly, since JPEG QuickProof output seems correct. I speculate that incorrect output handling of the R- and S-Pixels is the reason.
Limitations: I have not checked whether other adjustments or other raw formats (NEF etc.) are affected by this output problem as well.
-Mino
C1P8
The Fuji S5 Pro is a 6 MP DX camera with a high dynamic range. C1 is advertised as to support the Fuji S5 Pro and has a very nice new HDR feature. Therefore, the use of Capture One Pro on raw files from the Fuji S5 Pro seems promising.
However I found that C1 cannot correctly make use of the Fuji S5 pro RAF format.
How to reproduce the bug in four simple steps:
1. In C1 open the Fuji S5 Pro RAF file, taken with the dynamic range > 100%, e.g. 400%. You can detect those images by their file size (about 25 MB). These RAF files store the information from the cameras' R- and S-pixels.
2. Auto adjust the image by clicking on A (surprisingly, this gives a slightly different result when selecting Menu > Adjustments > Auto Adjust.).
3. In the Exposure Tab increase High Dynamic Range > Highlight to 100%. For example, this can give a "blown out sky" back its nice blue color. Really impressive!
The histogram also indicates that you could regain information from the highlight side. Very good. Especially the levels curves (red, green, blue) clearly show how C1 will recover "blown out" highlights!
But now, you of course want to *output* the enhanced image. Here is where Capture One Pro 8 fails.
4a. Look at the filmstrip below the Preview. You already can see that all the light greens are turned to a different, darker green. Or:
4b. Take the loupe tool (P) and hover over light green or blue areas. The loupe not only increases details to 100% to check for sharpness, but surprisingly the colors change to a darker tone: dark green, dark blue! Or:
4c. Save the image as a simple JPG (or TIFF, PSD), what everbody wants to do:
- JPEG 80%, sRGB, 300 px, 100% > Process
The resulting output is way different than the adjusted original! You can easily compare the images after re-importing the JPG and displaying them in multi-view side by side. And compare the leves curves.
5. To my surprise saving the images as "JPEG QuickProof (sRGB)" retains the nice adjustments without any shifts in brightness. This reinforces my impression that C1 has an easy to solve bug in the output handling of adjusted RAF raw files from the Fuji S5 Pro.
Conclusion: While Capture One Pro 8 obviously can nicely handle the high dynamic range of Fuji S5 Pro raw files (RAF) in memory, the resulting output to JPG etc. is flawed. I do hope it is only a minor bug that can be solved quickly, since JPEG QuickProof output seems correct. I speculate that incorrect output handling of the R- and S-Pixels is the reason.
Limitations: I have not checked whether other adjustments or other raw formats (NEF etc.) are affected by this output problem as well.
-Mino
C1P8
0
-
Which ICC profile do you use in the process recipe in 4c?
I also wonder if the cameras dynamic range settings (not sure what that is) are reflected in the RAW file.0 -
Hi
There is some limitation with Fuji S2, S3 and S5 cameras due to its diagonal readout and special sensor design.
It is specific to the three cameras and none else.
It should be noticed that this is not a bug. It is a known limitation which applies to all softwares except Fuji's own.
They are supported "as is" and no specific support beyond what we currently do will be implemented.
We do a very good result as is and better then most competitors.
However since there is no future for this sensor design and there is very few active cameras in the marked the current implementation will not be worked on.0
Post is closed for comments.
Comments
2 comments