Jump to content


  • Content Count

  • Joined

  • Last visited

About creature

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Location
  1. I think this bug is new in the 1.9.x series; I didn't see it in 1.8.x. I'm running Affinity Photo 1.9.1 on macOS 10.14.6. I have a right-hand side panel, and the middle section controls don't go "all the way across". Here's a full screenshot in develop persona for context, along with just the middle panel in the photo persona. It also affects develop persona tones/lens/details, and photo persona adjustment/effects.
  2. I am indeed, and that workaround does work – thanks! I run Affinity Photo on my "primary" display, a 27" BenQ at 2560x1440 – WQHD. Hopefully the macOS Displays panel gives the details you asked for:
  3. I'm trying to expand my knowledge of colour grading techniques for photos, and I found this tutorial for a method in Photoshop. It uses Photoshop's curves tool to take a particular look from a source image and apply it to your own picture. Essentially, you build a curves adjustment by sampling colours for a photo's shadows, midtones, and highlights – then set your own photo's shadow/midtone/highlight tone points equivalently. Affinity Photo's curves panel doesn't have a colour picker, so this technique isn't directly portable. Can anyone suggest an equivalent? I've used the Gradient Map
  4. Sometimes, the HSL adjustment panel (ie. the window to configure an HSL adjustment window) has the colour wheel and swatches mis-scaled, so only a quarter of it is visible. (Random guess: maybe it's presuming it's running on a retina screen?) This panel isn't adjustable, so HSL is unusable in these circumstances until Affinity Photo is restarted. I'm running Affinity Photo 1.9.0 on macOS 10.14.6, but I've seen this issue on 1.8.6 before too.
  5. @Mark IngramI generally shoot with a Fujifilm X100F, and have it set to "RAW + JPEG", so I have plenty of example images to contribute. One of the distinctive features of Fujifilm cameras is their film simulations – allowing you to pick a particular look for your SOOC JPEG. Some of these are pretty subtle changes, but some are quite distinct (such as the B&W conversions and the 'classic chrome' mode). For this project, do you prefer to receive examples just using the "Provia" setting (ie. the default), or is a variety of RAW/JPEG pairs better?
  6. I'm experiencing this too (High Sierra, Fuji X100F RAWs). For me, this seems to be associated with using the Apple RAW engine (selected via the "Assistant" menu in the Develop persona). It went away when I switched back to the Serif engine, though that might be co-incidence. The image opens fine for me via OSX's quick look feature, as well as in the Preview app. I've also seen the doubling change for the same image (eg. I had one occurrence where the image was duplicated into the top left corner, and another one where the bottom half was repeated one on top of the other). So I sus
  7. I tried to reproduce this in 1.5.2 beta 3, and had no luck – but then, I didn't have exact steps to reproduce before. It just kinda showed up as part of my workflow. I'm not planning on using the beta day-to-day, but I'll report back if it recurs. I did log several other bugs at the same time as this one that so far haven't been addressed; it would be nice if they could be checked out too. :)
  8. I'm using Affinity Photo 1.5.1 on macOS Sierra 10.12.2. When I try to start a new batch job, Affinity Photo crashes. This initially happened when I had two RAW images open and I tried to start a new batch job, but now Affinity Photo is opening without any files and it's still happening. I've never used the batch functionality in Affinity Photo, so I shouldn't have had any opportunities for it to get into a weird state. My only guess is that it's a side-effect of the "macro library failing to load" bug alluded to in the 1.5.2b2 notes, as I'm affected by that and I think the batch panel lists ma
  9. I'm afraid I haven't got exact steps to reproduce on this one, and I don't have any ideas about likely causes or common elements. It doesn't happen every time I open an image, for sure. As best as I can recall, this has never happened from opening AP "fresh" – it's always been when opening a RAW image in an already-running instance of AP. I do have AP set as my default RAW editor, yes. As for my workflow: after a shoot, I copy images from my camera into a new folder, then browse them in the Finder. Thumbnail mode at maximum zoom gives me a good idea about whether I want to edit the image,
  10. I haven't got any other image editors that support Photoshop plugins, unfortunately, so I've no easy way to try in other apps. But yes, it happening in Photoshop does suggest it's a fault in the plugin. I was guessing it was in Affinity Photo, because I haven't found any other reports of this issue online. AFAIK Google hasn't come out and directly stated "We're not updating the Nik Collection any more", but that seems likely. So I guess I'm out of luck with getting this fixed. :( Thanks for looking into it, though! (While trying to find info about Nik Collection updates I did find thi
  11. In Adobe Lightroom, when you hold down the backslash key, it shows you the original version of your photo (before any edits). The sliding before/after and side-by-side comparisons in Affinity Photo are great, but it'd be wonderful to have a similar "press to see original" feature too. Given the way that you can move between modes in Affinity Photo, perhaps this should work as "holding a button shows how the image looked when you entered that mode". Cancelling out of a mode shouldn't change the "before" image for the previous mode, but accepting the changes would.
  12. I'm using Affinity Photo 1.5.1 on macOS 10.12.2, but I'm pretty sure that this bug has been around since 1.4.x and Sierra. I loaded a RAW image into Affinity Photo and attempted to adjust its white balance (in the Develop persona) using the UI's spinner buttons. Rather than changing the white balance a little bit, the arrows cause the white balance to leap to the extreme ends of the scale. Often, it doesn't matter whether "up" or "down" is clicked; the white balance gets set to 2000K either way. The white balance is adjustable by dragging the slider as normal. I've attached a GIF scr
  13. I'm using Affinity Photo 1.5.1 on Sierra 10.12.2. As I understand it, the various presets in the "Develop" persona are specific to each tab. That is, the "Basic" presets only affect parameters listed on the basic pane, the "Tones" presets only affect parameters on the tone pane, and so on. However, it seems that choosing a preset also alters the map zoom. As far as I can tell, the behaviour is: If no point is selected, reset the map zoom to its most zoomed-out. If a point is selected, set the map zoom to its most zoomed-in. I would expect that choosing a preset should not affect the m
  14. I'm using Affinity Photo 1.5.1, but this bug was also present in 1.5.0 and the 1.4.x series. Steps to reproduce: 1. Open a RAW file in a copy of Affinity Photo that has some develop-mode presets. 2. Pick a preset to use, then develop the image. Save your image, then close it. 3. Open a different RAW file. The UI will indicate that your previously-used preset is selected and has been used, but it's not. Clicking the preset will actually apply it. You can see this in action in this GIF. I recorded this to illustrate another bug in the location pane, but you can see that the prese
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.