Jump to content

Saijin_Naib

Members
  • Content count

    67
  • Joined

  • Last visited

About Saijin_Naib

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've been exploring Darktable and a feature that has really wowed me is the Dark Frame library concept. In short, the user dumps whatever number of dark frames from whatever bodies they have at whatever combinations of ISO and shutter speed they can into a folder. Darktable will optionally subtract these darkframe(s) from a RAW that is closest in ISO/shutter when matched to the body in the EXIF. With one dark frame, a very minor reduction in luminance/chroma noise was apparent. Switching to 6 dark frames completely removed my hot pixels and reduced color cast and fine color noise on pushed exposures/high-ISO INCREDIBLY. I'm working towards using the DeepSkyStacker recommended 30x dark frames to see if there is any benefit to that number of dark frames for non-astrophotography exposures. It really cleans up the images wonderfully. Areas for improvement: Folder can't be recursed for subfolders by camera/setting Original RAW files only supported (TIFF/PNG/other lossless raster of equivalent bit-depth or greater should be possible as well) Averaging happens at image load, takes significantly long to open image with 6x dark frames. Generation of averaged/stacked proxy TIFF/PNG would likely speed this process up. No Darkframe Subtraction: 6x Darkframes (averaged) Subtracted:
  2. I'd like to see the RAW Demosaic process improved, somewhat along the lines of how DarkTable handles things. I like Affinity's ease of use, so setting sensible defaults for Demosaic engine, settings, etc., makes total sense. However, there are instances where a user might want to tweak the Demosaic or use an entirely different algorithm. For instance, the Markesteijn+fast produces far superior results for X-Trans data to other algorithms in other engines (typically AMaZE-based). This is crucial for IQ, especially when pushing exposure or sharpening at all, basically.
  3. This is quite a clean image for a stacked/HDR set of exposures in pretty poor light for a 2/3" sensor (my monitor+red LED backlight for the monitor). I was also able to really push the white balance with no noticeable color noise introduction, likely because of each of the 3x exposures per EV being "mean" blended before being exported to 24bit PNG for HDR composite (which the below is a screengrab of).
  4. I'd love to be able to easily integrate a stack or a number of stacks into a HDR Merge for Tonemapping without having to rasterize, composite, dump out, and then re-import the layers. My reasoning is thus: 2/3" sensor with a bit of noise. I take 3x exposures at each +1 EV, =0 EV, -1 EV. For each EV, I make a stack and use the "mean" blend mode. This reduces the image noise quite nicely. What I'd like to do here is feed the three stacks into the HDR Merge functionality, possibly with assigning the EV manually, and be able to merge/tonemap right away.
  5. MacOS version has it already, NFI on the Windows version. I would hope they reach feature parity on a major feature like that prior to release
  6. Just wait until the Windows build can use the GPU for effects rendering/compositing, not just drawing to the display. Should be a MASSIVE boost.
  7. Apparently the current AP on Mac uses GPU rendering for effects/etc, not just drawing to the screen as the Windows version does. Fingers crossed, this is coming far sooner than later.
  8. Saijin_Naib

    RAW Engines

    The slightest of improvements in color and shadow detail rendition, and now the X-S1 Lens Profile is applied properly. Clipping is still a massive problem, and it is still far from ideal/usable.
  9. You can register Affinity Photo to have an App Execution Alias, which will allow command line operations to be done against it with ease. A few "core" MS apps support this already, and a number of other released apps do as well. I can't find the documentation at present, but I believe it is only a modification to the app's manifest file to accomplish this. Big gain for a small investment from you, Serif. Here's an example:
  10. I'm a Fuji-X Shooter as well, though I'm using the even more esoteric EXR sensor with dual-subframes, which Affinity to date has not supported terribly well. I'm hopeful that the latest beta addresses any number of these shortcomings, but currently, I use Fuji RFC to do all my developing and then dump into Affinity for further compositing or editing. I tried CaptureOne Fuji edition, but found it lacking in comparison to Fuji RFC when it came to color/brightness accuracy. I also tested every free RAW developer I could find, and found them all to handle the EXR RAFs with varying levels of inadequacy. Bayer images from my wife's X-A1 did not suffer any issues with any of the other engines I tested, including Affinity.
  11. Saijin_Naib

    Automatic HDR panorama merges

    I'd love this as well
  12. Saijin_Naib

    Raw developer

    I agree that more actions should be able to be taken during the develop, such as multiple successive passes at Chromatic Aberration removal, or Defringing, with the SAME ability to set color/sensitivty/etc that we can with the filter once developed. Swapping channels/etc should also be possible prior to developing.
  13. Saijin_Naib

    Faster updates to Serif Labs

    I use PC/MS Store version. Will these be following the 1.7 beta shortly?
  14. I've noticed similar. Fuji RFC/SilkyPix8.x is really quite exceptional in terms of rendering, especially when compared to other RAW engines. I've a bit of a comparison in my thread here that confirms your findings:
×

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.