So this one got some more than just the usual 'adjust contrast, desaturate, increase vibrance' treatment. After seeing what someone made of my fog post with some local contrast etc, I thought I'd experiment a bit. So I first did some work on the overall picture, toning down highlights, increasing ambiance, desaturating and setting the white balance a bit further to the cold side.
But then I added some extra darkening to the shadows of the road to increase its local contrast and lit up the shadowy regions of the mountains. Somehow that makes the image work a lot better now imho.
just downloaded the software and gave it a try - same issue as most others. It doesn't ingest the pixel-wise correction matrix and therefore gives an image that is blighted and has a red-shift in the middle, while getting some vignette in the corners...
I did some "research:"
Many photography software applications struggle to handle RAW images from pixel-wise sensors (such as those found in phones like Google Pixel) due to several key factors:
1. Proprietary RAW Formats:
Pixel-wise sensors, especially in smartphones, often use proprietary RAW formats that require specific decoding algorithms. Manufacturers may not publicly release detailed specifications, making it challenging for third-party software developers to support these formats efficiently.
2. Computational Photography Differences:
Smartphone cameras, including those in Google Pixel devices, rely heavily on computational photography techniques, such as multi-frame processing, AI-based enhancements, and advanced noise reduction. RAW files from these sensors may contain unconventional data structures that traditional RAW processors are not designed to handle.
3. Sensor-Specific Calibration:
Pixel-wise sensors often have unique color filter arrays (such as Quad Bayer or Non-Bayer patterns) that require specialized demosaicing algorithms. Standard RAW processing software may not include tailored profiles for these sensors, leading to inaccurate color representation and dynamic range issues.
4. Metadata Complexity:
RAW files from smartphone cameras often include extensive metadata related to AI processing, HDR stacking, and depth information. Traditional photo editing software may not be equipped to interpret or utilize this metadata effectively, leading to compatibility issues.
5. Different Color Science Approaches:
Professional-grade cameras from companies like Canon, Nikon, and Sony follow well-established color science workflows that have been optimized over years. Smartphone manufacturers may use different approaches to color reproduction that do not align with traditional workflows, making it difficult for standard RAW editors to achieve accurate color reproduction.
6. Lack of Standardization:
Unlike the well-established DNG (Digital Negative) format, many smartphone manufacturers opt for proprietary RAW formats without adhering to industry-wide standards. This forces software developers to reverse-engineer these formats or wait for official support, which may not always be available.
7. Software Optimization Priorities:
Many traditional photo editing tools are optimized for DSLR and mirrorless cameras, which produce RAW files with more predictable data structures. Adding support for smartphone-specific RAW files may not be a high priority for these companies, given the relatively smaller demand compared to professional workflows.
To address these challenges, some users turn to manufacturer-recommended apps (such as Google Photos or Snapseed for Google Pixel devices) or use software that supports DNG files, which are more widely compatible across platforms.
To improve Capture One’s ability to handle RAW images from your Pixel-wise sensor (such as those from Google Pixel phones), consider the following steps:
1. Convert to DNG Format
• Google Pixel devices can save RAW files in DNG format, which is widely supported by Capture One.
• If your Pixel’s RAW files are in a proprietary format (e.g., .PEF or .RAW), you can use Adobe DNG Converter (a free tool) to convert them to DNG before importing them into Capture One.
2. Use Capture One’s Generic DNG Profile
• Capture One offers a generic DNG profile that may improve compatibility with your converted RAW files.
• Import the DNG files and manually adjust color profiles and sharpening to better suit the Pixel sensor’s characteristics.
3. Custom ICC Profiles
• If you notice significant color inaccuracies, consider creating or downloading a custom ICC profile tailored for your Pixel device.
• Tools like X-Rite ColorChecker can help you generate a profile that Capture One can use to apply more accurate color corrections.
4. Tweak Capture One’s RAW Processing Settings
• Since Capture One is optimized for DSLR and mirrorless cameras, manual adjustments may be necessary:
• Increase Noise Reduction, as smartphone RAW files often contain more noise.
• Adjust Sharpness and Structure to compensate for differences in smartphone sensor processing.
• Experiment with Base Characteristics > Curve to find a setting that closely matches the smartphone’s output.
5. Try Third-Party Plugins
• Some third-party tools and scripts may extend Capture One’s support for certain smartphone RAW formats.
• Look for community-developed tools or Capture One plugins that can preprocess these files before import.
6. Capture One Feature Request
• If you frequently work with Pixel RAW images, consider submitting a feature request to Capture One’s developers. They might consider adding support in future updates if there’s enough demand.
7. Alternative Workflow
• If Capture One struggles too much with your files, consider processing them first in software better suited for smartphone RAW files (e.g., Adobe Lightroom, Affinity Photo, or RawTherapee) before exporting them as high-quality TIFFs for final editing in Capture One.