Jump to content

Maarten Langeveld

  • Content Count

  • Joined

  • Last visited

Everything posted by Maarten Langeveld

  1. With even number of images the median should be calculated as the mean of the two middle observations, which Affinity apparently does not. Curious how Affinity calculates the median when even number of images is stacked... Agree with you suggestion: next to the 'outlier' stack operator a 'remove outlier' stack operator should be more than welcome.
  2. Loading a pair of images twice (4 images stacked : two same pairs) results in same error as with two different images. Mathematically the median should have same result as the mean which it does not with Affinity. Curious...
  3. Interesting... Good to know it works fine using three images. Keeps me wondering what happens when two images are used... Maybe Affinity developers can clarify on this?
  4. Stacking two photo's in Affinity Photo, I get different results between 'mean' and 'median'. Which really surprises me since with two samples the mean and median mathematically have the same outcome, while in Affinity the respective results differ a lot ! I would have expected same results in Affinity Photo. What's going (wr)on(g) ?
  5. Thanks, Good to know ! I have calibrated my monitor using Spyder, which has created a wide gamut monitor profile for my standard monitor preset, this Spyder generated profile I have installed as default profile for my display in Windows Colour Management. But since Windows itself is not colour managed, the Windows GUI looks very over-staurated, so when doing regular tasks websurfing, e-mail etc. I switch my monitor to built-in (i.e. in the monitor itself) RGB profile. When working with Affinity I switch my monitor to (wide gamut) standard preset and like with Windows GUI, Affinity GUI looks very over-saturated. Maarten Edit: for some reason cannot reproduce over-saturated colours with Affinity. Have installed all profiles again, and now seems okay! Probably did something wrong that I have looked over. My apologies.
  6. Hello devs, As a photo enthusiast I use a calibrated wide gamut monitor. Affinity does support colour management for the workflow but it seems, the application itself is not colour managed. Nowhere I can find the option to select the appropriate (calibrated wide gamut) colour profile for my display. For office work I use a standard sRGB profile on my monitor as default since Windows GUI is way too over-saturated when working with AdobeRGB. But for photo work I use calibrated AdobeRGB profile. Problem with Affinity is the same: when working with wide gamut colour profile for my photos the Affinity GUI is also way too over-saturated. Another wish I have is the option to export a picture with colour conversion (not just exporting with a different profile, but actually converted on the fly). I mean: when I work in a project in AdobeRGB I would like to export the result in sRGB JPEG without converting the project itself from AdobeRGB to sRGB (irreversible). Thanks, Maarten
  7. Hi Chris, Thanks for your feedback. I understand but do not understand quite frankly. When it takes at least 200 MB per 16 mp photo that I process in Affinity, I won't using Affinity anymore I'm afraid. Hope you guys and girls at Affinity understand that file sizes are extremely huge. Hope you'll add a 'save for archiving' option that (1) strips all redundant data (for optimisation) en (2) losslessy compresses remaining project data to Affinity Photo (and not exclusively for Publisher).
  8. When working on a affinity photo project, the .aphoto project file size keeps increasing even when I delete layers, convert document from RBG/16 to RGB/8. After my workflow from importing 16 megapixel RAW file as AdobeRGB in RGB/16, develop the image using Development Persona, doing some stuff in Photo persona using a second pixel layer, in the end flatten to one pixel layer and just adding two non pixel layers layers (soft proof adjustment and high pass filter), convert document to sRGB in RGB/8, leaves me a .aphoto file of 199 Mb (!!! not kidding). Save as reduces filesize to (a still ridiculous) 159 Mb. It is: (1) strange that "save" and "save as" the same .aphoto project leaves different filesizes (in casu 199 Mb vs 159 Mb), should be the same! (2) ridiculous that a affinity photo project containing just a 16 megapixel 8 bit RGB pixel layer and one adjustment layer and one filter layer has a file size that is more than three times the image size (16 Mega pixel times 3 bytes (8 bit colour per channel)) These ultra huge file sizes are a problem, please fix. I am using Affinity Photo on Windows 10.
  • Create New...

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.