Jump to content
You must now use your email address to sign in [click for more info] ×

AndyGordon

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. @Gabe Sorry for the delay, but re-booting makes no difference. Just an idea thought but I’ve been using the production version tonight and it worked fine for NEF’s from my Z7 with the Nikon 14-30 but failed the same as soon as I tried a NEF taken with the Z7 and the Nikon 24-200. Is this as simple as a lens compatibility issue on the Serif Lab raw decoder?
  2. Hi Gabe, Just tried this with a fuji RAF file on the beta version and worked fine using Serif Labs and Apple Core image raw, Nikon Z7 files (uncompressed, lossless compressed and compressed) all in 14bit has the same problem. Also the 12 bit versions of the files and the same result. Not sure if its just me? Re iPad model, its the 2018 iPadPro 12.9" model with 256gb storage running iPadOs 14.6 Andy
  3. Still not working on iPad 1:10.0.247 - latest build pick a nef, use serif Lab raw, get blank image, use Apple (core image raw) works fine. I’ve had this bug a while now, is it just me?
  4. Tried with Nikon and Fuji raw, same result, presented with blank screen. If you select develop AP will develop the raw using Serif Lab First image opened using Serif Lab raw, second using Apple core image raw. iPad Pro 2018 12.9” model, running iPadOS 14.2
  5. I’ve found that if you start affinity under intel emulation rather than m1 native then Nik and affinity works as they should its when you have the mix of affinity running native m1 and Nik running on intel that it doesn’t work
  6. Just tried the Nik collection on an M1 MacBook Pro and whilst the plugins are visible in the menu, selecting e.g Color Efex does nothing at all. I've also got DxO and this works wit the Nik collection just fine on the M1 MacBook. I've also tried the same with the same version of Affinity Photo and Nik collection on a 2015 iMac running Big Sur and that works. I've also tried the beta version on the M1 Mac and that fails as well as the production version
  7. Yes probably the same thing, it looks like a general bug with the tone mapping persona.
  8. Just opened a Nikon raw (Z6) into beta, developed it, selected tone mapping persona and got blank screen. Selecting split view showed as per image below. iPadPro 2018 model running iPadOS v 14.0.1 Affinity Beta 1.9.0.199. Works fine on 1.8.6 ipad version. Cheers Andy
  9. Tried with latest beta. Infer LUT causes immediate crash. Load LUT works as per production version. Same behaviours as this bug in release 1.8.x (https://forum.affinity.serif.com/index.php?/topic/108877-infer-lut-failing-beta-182171-18-production/)
  10. I opened a Nikon raw on my iPadPro, Surface Book and iMac applied the same raw development settings to the image and exported as a 16 bit Tiff with the same settings applied (full disclosure, I forgot to remove the spot top right hand corner on the windows version) and got slightly different results, with the iMac and Surface Book looking the same, but the iPadPro version slightly different when they are all viewed on the same screen. Viewed all 3 on both the iMac and Surface Book and the same results. I couldn't compare on the iPadPro as it just didn't want to display the 3 images - more an iPad thing given the iMac and Surface Book with full os's were able to. My question is.....should I expect the same result from these products on different platforms? It's noticeable that the iMac and Surface Book versions are the same file size and same look, whereas the iPadPro version is a slightly smaller file and looks slightly different. The machines were all running the latest version of Affinity Photo: iPadPro AP 1.8.4, iOS 13.6.1 iMac AP 1.8.4, Catalina 10.15.6 SurfaceBook AP 1.8.5, Win 10 Pro, 19041.450 As far as I can see all at the latest versions of product and platform
  11. I had this and reported it. It’s been fixed in beta 1.8.4, so should be out soonish when Affinity releases it
  12. Hi, This was fixed in current beta 1.8.4. I’ve tested it and it works fine now Andy
×
×
  • Create New...

Important Information

Terms of Use | 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.