Jump to content

Search the Community

Showing results for tags 'foveon'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 9 results

  1. BW Images still open as colour, and when manually converted to BW, they lose all their Foveon benefits. There's two methods to obtain BWs from Foveon RAWs, and neither of them work in AP. Images taken with the Merrill series cameras are normally able to deliver BW images without the mushiness of a CFA (colour filter array, such as Bayer), or the heavy resolution loss from an antialias filter, like with the a Leica Monokrom, yet are not prone to strong aliasing artifacts like many other cameras. All test images were captured in BW, latest camera firmware, and open properly in some other applications as BW (however, some LibRaw demosaic engine apps open them as colour, suggesting LibRaw as a possible element for the problem. Note however, that digiKam which uses LibRaw 1.19 builds these image thumbnails correctly in BW, and it is configured not to extract the embedded jpeg - it is building a downsampled version of the raw). Forcing BW RAWs to convert from colour to BW in Affinity Photo for the nearly 9 months of production and beta AP versions results in severely downgraded noise and detail and tonal range. How can I support Affinity support getting the issue posted to LibRAW's devs, so that it gets added into their mix of stuff 'in the queue' to be prioritized? I'd really prefer if it had the gravity of a respected LibRaw integrator (Affinity) verifying that it's not some lone user that hasn't done any due diligence. As well, the LibRAW folks might not otherwise appreciate that this affects all Merrill sensor Foveons (not all Sigma cameras, but a large percentage of the current user base).
  2. BW Images still open as colour, and even if manually converted to BW, they lose all the Foveon benefits. There's two methods to obtain BWs from Foveon RAWs, and neither of them work. Images taken with 1:1:1 Foveons (such as those with the Merrill series sensors) are normally able to deliver BW images without the mushiness of a CFA (colour filter array, such as Bayer), or the heavy resolution loss from an antialias filter, like a Leica Monokrom, yet are not prone to strong aliasing artifacts like other cameras. All test images were captured in BW, latest firmware, and open properly in many other applications as BW (however, some LibRaw demosaic engine apps open as colour, suggesting a possible source for the problem, for someone within Appian to register this bug to the LibRaw community). Forcing BW RAWs to convert from colour to BW in Affinity Photo for the last 8 months (all production and beta versions) results in severely downgraded noise and detail and tonal range. Thx.
  3. BW Images still open as colour, and even if converted to BW, lose all the Foveon benefits. There's two ways to obtain BWs from Foveon RAWs, and neither of them work. Images taken with 1:1:1 Foveons (such as those with the Merrill series sensors) are able to deliver BW images without the mushiness of a colour filter array, or the heavy resolution loss from an antialias filter, like a Leica Monokrom, yet are not prone to strong aliasing artifacts like other cameras. All test images were all captured in BW, latest firmware, and open in many other applications as BW (some open in colour, and two of those use LibRaw). Manually forcing them to convert to BW in Affinity Photo for the last nearly 8 months (all production and beta versions) results in severely downgraded noise and detail and tonal range.
  4. Members 12 59 posts BW Images still open as colour, and even if converted to BW in AP, it loses all the Foveon benefits (not very usable). There's two ways to obtain BWs from Foveon RAWs, and neither works. This has been occurring for six months of production and beta releases, and is not a newly reported issue.
  5. BW Images still open as colour, and even if converted to BW, lose all the Foveon benefits. There's two ways to obtain BWs from Foveon RAWs, and neither works. Similar crops below from the same image, all at 200% zoom (slight variations in cropping). Most recent of multiple posts (prior beta) Above: AP 1.7.2.414 choosing BW Above: AP 1.7.2.414 choosing BW and only using blue channel Above: IrfanView 4.5.2 as opened (uses DCRaw) Above: Sigma Photo 6.6.1 Export using Blue Channel only
  6. Resolved: Can confirm 1.7.1.404RC2 has full control over noise removal, especially chroma noise (working since recent betas: thank you so much), and is fully usable now on Sigma Merrill cameras. Also, only as of 404RC2 is EXIF and focus reliably consistent. Outstanding: BW images still open as colour: no benefits from in-camera BW captured images. Additionally, some BW images shot at higher than base ISO open like linear exposure (super dark). Quick test images (apologies for quality): 6745, ISO100, BW: in 1.7.1.367 and .404RC2 has EXIF and focus info, but recent prior betas were partially missing EXIF & focus metadata. In all versions, these open as colour (should be BW). 6742, ISO800, BW: Very difficult trying to extract a workable image from these RAWs (shot higher than base ISO). Opens fine in other RAW editors. Why Not Use Normal Colour to BW (Post-processing Conversion): The key issue behind this is that the Foveon Merrill can capture the full spectrum at every single 'pixel' (photosite), and output it in BW (like a Leica M Monochrom). No demosaicing is required (or ever wanted). When these are shot as BW in the camera, Affinity Photo opens them as normal colour images, and loses all their benefits. For instance, Foveons also normally capture full spectrum at every 'pixel', and when all treated as BW, you can get 3 times as much sampling per pixel as the monochrome Leica, for improved noise. See earlier post (Issue #1): https://forum.affinity.serif.com/index.php?/topic/80333-med-resolution-images-auto-upsampled-to-high-bw-images-import-as-colour/ SDIM6745.X3F SDIM6742.X3F
  7. Just an update after doing some testing last night with 1.7.1.385, and the ongoing denoising/demosaicing issues (not sure which was causing the problem) which made Merrill (SD and DP Merrill series cameras) barely usable, now appears significantly improved. Before, there was so much noise evident (mostly chroma, but also some luminance) even with reasonably well exposed images, that to get rid of sufficient noise resulted in also removing so much detail that the output almost looked like a stylized cellphone oilpainting filter. NOTE: this problem only occurred with the Sigma Merrill cameras, and did not affect earlier Sigma cameras, which performed normally. Now, it is possible (for well lit areas within an image) to adjust the denoising so that you can just apply enough to get rid of widespread noise, but through the currently available controls, selectively adjust the extent applied such that a balanced amount of detail can be retained (meaningful noise:detail tradeoffs). It still needs a fairly bright exposure, but it is no longer prohibitive. I don't know if this was due to the hard work of Affinity or LibRaw, but thank you very much. I ran out of time, but images captured as pure BW may still be opening in AP as colour. I will test with .390 this weekend. But this is a huge quality improvement for all Merrill users.
  8. Affinity Photo Desktop Windows, latest (non-beta) rev: 1.6.5.135 Win 10 x64 up-to-date, 16 GB ram, >45 GB on SSD, >400 GB on HD & defragged no SMART errors). GTX 1060 6GB. Camera: Sigma SD1M (M for Merrill, inventor of the Foveon sensor), X3F RAW files. Neither of these issues happen with my SD14. Reproducible. Two unexpected behaviours both occurring during RAW import, even with the same image file. Behaviour One Import B&W RAW image, and B&W setting is lost (appears with separate colour channels). Camera has two methods for obtaining high quality B&W images: 1) At time of capture, choose B&W setting on camera body, which flags RAW metadata to treat R, G, B results as one value (grey) per photosite. Actual raw data would still have RGB per photosite, but image should only open as greyscale. 2) In Post-Processing, extract only the Blue channel from raw RGB data, from every photosite. This method loses the photons from the R&G layers, but since the Blue layer is the top layer, it has the least noise, so is pretty good. The other side-effect to this method is that because only the Blue layer is captured, it would be like using a deep blue filter over the lens, making yellows black, reds very dark, etc. So some things may look a bit different from a full-spectrum B&W image. The advantage is that it is reversible (you can decide you preferred the image as a colour image afterwards, whereas the first method keeps everything B&W for good). I cannot find a way to achieve either method of getting a high quality B&W. I would prefer #1 (above) if I had to pick, as you get panchromatic response and lots of photons per photosite, resulting in ultra-low noise, just like from a Leica Monokrom. In this version, attempting this results in a lot of noise, even in a perfectly exposed image. In other RAW processors, I can use zero sharpening, zero de-noising (colour or luminance), and the images are clean. Also, default behaviour is to open as B&W, with only greyscale available (even Irfanview reads and presents the raw that way). I should note that it's not terrible noise, but the camera is capable of using these modes to deliver super creamy B&Ws, and I was hoping to be able to do that. Behaviour Two Import a RAW image taken at MED resolution, and the imported RAW will be auto-scaled up to FULL/HIGH resolution (I could not find how to defeat this default behaviour). Since it's not a perfect upscaling (I calculated around 47%), there are significant uprezzing artefacts, and it's not as sharp. The camera allows photos to be captured at LOW, MED or FULL/HIGH resolution. Again, it's not horrible, but it's nowhere near how other RAW processors handle it. The camera uses one of the native features (though not all manufacturers make use of the 'feature') of CMOS sensors, 'binning', where arrays can report as if they were a lower resolution sensor: for example, a 4x4 grid of photosites would electronically be merged to act like a single photosite, so that all the photons get added together, giving you lower resolution but super low noise images and more accurate colour. Plus, Foveon images are often upscaled 200% after the fact, and still yield as good images as a Bayer CFA, so the resolution impact isn't near as negative as one might think. Foveons are the best at detecting subtle colours and recording micro-contrast without destructive processing, but sadly, they only do that when shot at low ISO or under loads of exposure, so these are frequent methods users employ. Example: MED resolution photo (see green photo resolution) opened & upsampled/upscaled in Affinity Photo as a FULL resolution image (see yellow Affinity resolution). Also, this same photo was taken as a BW-only image, yet it is apparent that it contains hues. One positive upside I discovered from the comparative testing is that the GPU acceleration in Affinity Photo is faster than the GPU-aided processing in both Corel and much moreso than even Sigma's own software. Haven't benchmarked Rawtherapee or On1 on that yet. I have previously uploaded MED and FULL/HIGH resolution images, as well as colour and B&W images, from my camera to the Forum calling for sample images. Note that neither of these behaviours occur with my SD14 X3F (Foveon) images, so it is confined to the SD1M (aka Merrill). That exact same sensor is used in a few Sigma DP cameras as well (I believe it is the DP3 series), so they may exhibit identical behaviour for both these anomalies. Thanks very much. Still learning a lot about the software, but it has made some things that were unbelievably tedious and error prone into downright easy when using Affinity Photo. Perhaps I have overlooked something and that is also the case here.
  9. I have a Sigma DP2 Quattro and while that camera is partially supported, I get better results from converting X3F files to DNG with X3F Tools and then develop the DNG in Affinity Photo (adjust white balance tint and it looks pretty good). The problem is that Photo doesn't honor the crop instructions. It does honor the size of the output file (5424 x 3616), but displays thick black borders along two sides and cuts off the opposite sides. Older versions of Iridient Developer used to do the same but their newest version works correctly. Here's a link to the tool in question: https://github.com/Kalpanika/x3f/releases/tag/0.54 Here's the announcement on Dpreview, you can find links to some DP Quattro RAW files (too big to upload) in that thread as well: http://www.dpreview.com/forums/thread/3890093 I have some ideas on how you can improve your own Sigma Quattro rendering, but the best would likely be to contact the authors of X3F Tools about integrating their import code in your own software. Their noise reduction is rather impressive...
×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.