Jump to content

geni1105

Members
  • Content count

    10
  • Joined

  • Last visited

  1. geni1105

    Still no Sigma X3F-Raw support

    Sorry, I just noticed I'm on the Windows forum. Actually I did all trials on Mac, but I assume the results apply to Windows too.
  2. geni1105

    Still no Sigma X3F-Raw support

    For the SD15 support, the Libraw website states "raw decode only" - indicating that no color corrections etc. are done by Libraw. So if Affinity Photo relies on Libraw to do the complete job, it cannot work. Unfortunately, AP (or Libraw) also does not do a good job in color rendition for other Sigma cameras - it seems that camera profiles are either not correct or missing, see attached screenshots from Colorchecker shots from a DP3 Merrill. AP is severely off in the yellow / red / orange hues, and the shadows have a distinct green cast (the two gray squares expected on the bottom right). Sigma Photo Pro is nearly correct (as should be expected), but also the open source Kalpanika X3F-to-DNG converter is very close. All samples have been white-balanced on the bottom 3rd square from the right. IMHO Affinity should not claim to support X3F raws, when the results are unuseable. Maybe include the Kalpanika code? Affinity Photo 1.07.106 beta: Sigma Photo Pro 6.6.2 Kalpanika X3F-to-DNG converter (with X3F Wrapper for flat-field correction and Adobe Camera Raw for DNG development):
  3. Unfortunately yes - same behaviour in 1.4.1
  4. I'm disappointed that this is considered a feature request rather than a bug report, and that such a basic functionality does not work correctly in AP. And no reaction from AP staff. I will go back to PS, where dodge/burn works like it should.
  5. I have to bring this up again, because I am not able to reach the dodge / burn results that I want with AP and comparing to PS behaviour. I did a test of dodge and burn brushes on a gradient fill converted to a pixel layer, see attached image. I used brush size 250 for dodging and burning with the 3 options highlights / midtones / shadows each, all other settings left at their default values. One horizontal stripe (going back and forth twice, mouse kept clicked) per setting. I might be doing something wrong, but here are my conclusions: - dodging set to "highlights" reaches far into the midtones, dodging set to "midtones" seems about right, dodging set to "shadows" does not have a significant effect on the shadows - there is virtually no difference in how dodging affects midtones and shadows, irrespective of the highlights / midtones / shadows setting; if anything, dodging set to "shadows" seems to brighten midtones more than dodging set to "midtones" (!) Similar for burning: - burning set to "highlights" reaches far into the midtones, burning set to "midtones" has just a weak effect - burning set to "highlights" darkens midtones slightly more than when set to "midtones" (!) - burning set to "shadows" even kicks in at a hard threshold, which is high up in the midtones Also, I cannot avoid some posterization on the gradient (even tried 16 Bit RGB and 16 Bit LAB), which is strongly increased by dodging and burning. Finally, there is a significant difference in the strength of dodge/burn effect, whether I am brushing back and forth keeping the mouse clicked, or whether I overlay several separate strokes. Maybe this is intended behaviour, but does not seem logical to me. This is with AP 1.4, on an iMac Retina running OS X 10.11 Thanks, Georg
  6. I am using it to implement Ming Thein's workflow, who often uses selective dodging of highlights / burning shadows to increase local contrast. This works very well in Photoshop CS5: when applying dodge/burn brushes to highlights or shadows, they nearly do not affect midtones - ok. However in AP, when either highlights or shadows are selected also the midtones are affected heavily. This can only be worked around by reducing brush opacity to 10%, but then the intended effect is mostly gone. So IMHO a steeper separation between highlights, midtones and shadows would be needed. Secondly, it is annoying that the brushes change to their defaults for every newly opened image. I am pretty sure most users would prefer to keep the last used settings. Not sure if these are feature requests or bug reports ... Anyway, congratulations to this otherwise great application! Thanks, Georg
×