Jump to content

chris_s

Members
  • Content count

    8
  • Joined

  • Last visited

  1. chris_s

    Affinity Photo Crashes

    Just crashed again. Memory usage on the machine was over 80%. I was using the Selection Brush at the time. It sent you a crash report.
  2. chris_s

    Affinity Photo Crashes

    I did some further experimenting this morning and this time, I couldn't get it to crash. The only difference I can see is that memory on my machine was probably 70 -80% full when I was getting the crashes. Today it's more in the range of 50 - 60%. I'll have to try filling it back up and trying it again.
  3. chris_s

    Affinity Photo Crashes

    Did you get the dump/log that the app supposedly sent to you after one of the crashes?
  4. chris_s

    Affinity Photo Crashes

    It isn't document specific. I was able to recreate the problem with this document in a matter of minutes. DSCF2778_pseudo-IR_b.afphoto
  5. chris_s

    Affinity Photo Crashes

    It crashed on me a number of times. In most/all cases, I was using the paint tool to do a bit of air brushing. Once I close the "Unhandled Exception" box, it goes into a busy state and doesn't respond. I have been using Affinity Photo for a while (on previous releases) and didn't have any problems (nothing else changed at my end). The most recent time, it sent a crash report to you.
  6. chris_s

    Another Color Profile Problem

    What does Aff Photo use to determine that an image is 'unprofiled.' Just to be sure, I downloaded the file that I sent you the link for. I had a look at the EXIF info and it shows: Photometric Interpretation: RGB Color Space Data: RGB (in ICC Header) Profile Description: sRGB (in ICC_Profile) FYI: DCRaw defaults to sRGB (-o 1) so it puts in the 3 fields shown above and thinks that this is adequate to define it as sRGB. Maybe Photo is looking at some other field(s) as well.
  7. chris_s

    Another Color Profile Problem

    Here is a link to a tiff sample link
  8. I looked through a number of previous posts on this topic and that didn't lead to an obvious answer. This is the situation: Loading a raw file (RAF) or the JPEG thumbnail from it works fine and everything looks normal. Loading a .tiff file converted from the RAF file (using DCRaw) triggers the warning about using a default profile (sRGB) because it is an unprofiled document. It creates a very dark over-saturated image in Affinity. This .tiff can be opened in other applications (e.g. Windows Photo Viewer) and displays correctly. Everything is defined as sRGB (the camera, the file, the monitor and the Affinity RGB color profile). I found that if I go into Color Balance and choose 'screen' rather than 'normal' it makes the image look proper. Is this normal behaviour and if so why.
×