Jump to content

Tamerlin

Members
  • Content Count

    26
  • Joined

  • Last visited

About Tamerlin

  • Rank
    Newbie
  • Birthday December 18

Contact Methods

  • Website URL
    http://WhiteCrane.photography

Profile Information

  • Gender
    Male
  • Location
    Vancouver, BC

Recent Profile Visitors

591 profile views
  1. I just updated, turned OpenCL back on and set the renderer back to the nVidia GPU. It opened up the first image that I tried, so that's definitely an improvement. I'll try it with other images as well soon. Thanks!
  2. I've tried DNGs from a Signa fp and from a DJI Pocket 2, as well as a 16-bit TIFF exported from RedCine-X Pro. When I have OpenCL enabled, Affinity crashes when opening any of them with the renderer set to use the nVidia 2060 6GB GPU in my system, but with WARP or the integrated Iris GPU it's stable. Disabling OpenCL but keeping the renderer on the 2060 also lead to a crash on opening an image. The system is an Asus ZenBook Pro Duo, i9 model with 32GB ram. It's also my system for running Mistika, Scratch, and Resolve, so I keep it up to date driver wise, and have gotten into the ha
  3. My first thought was the drivers... which I keep up to date to run Resolve anyway, and I've also gotten into the habit of using the clean install option. That was my first thought when Affinity Photo crashed on me as well. I'll post everything I know there this evening after work.
  4. It seems like Affinity Photo doesn't get along with nVidia GPUs, at least some of them. It crashes when opening an image if I have my laptop's nVidia 2060 6GB selected as the rendering device, with or without OpenCL enabled. It works fine with OpenCL enabled when using Warp for rendering, or with the integrated Intel Iris GPU.
  5. I found the option to disable OpenCL, but not OpelGL. Turning off OpenCL but setting the display renderer to be my nVidia 2060 6GB resulted in a crash when opening an image. With OpenCL enabled when I set the display rendering to use the integrated Intel Iris GPU, it loads the image.
  6. @MikeDuf I didn't try just disabling OpenGL yet. I'll try it later today and post an update. Thanks!
  7. I have the latest nVidia Studio driver installed. To test, I switched the renderer from GeForce 2060 to WARP, and now I'm able to open both of the images that crashed it with GPU acceleration enabled. Affinity Photo didn't create a dump file though. 😕
  8. For me it's starting up fine, but crashing when I attempt to open a photo. I tried a TIFF exported from RedCine-X Pro as well as a DNG from a DJI Pocket 2, both are causing crashes.
  9. When I tried to use the Liquify Persona and nothing happened, my first thought was that I must have had the wrong layer selected, so I double checked. Even when I disabled the layers above the original, liquify did nothing to the image. With mesh warp I could see the MESH warp, but it didn't affect the image... and I don't know why. I've only ever successfully gotten the Liquify persona to actually modify the image when it's the first thing I do after loading the image, and that combined with the fact that it's a one-shot deal, meaning that there's no possibility of tweaking it after appl
  10. Meh. Resolve is free, and I'd rather have the Affinity team focus on its core products rather than attempting to engage in a futile competition with the likes of Black Magic Design and Avid in the video world.
  11. I've been trying to use the Liquify Persona for some editing, and finding that it's... not great. It seems to only work on the original image, and not at all with images that I've done some color balancing to. That seems broken -- shouldn't I be able to go back to the original pixel layer and use Liquify on that? On one image I used patch to clean up some blemishes, and then merged the patch layer and the original, then tried Liquify... it wouldn't affect the image in any way. I can see the mesh deformation, but the image remains unaffected. Is it really a one-shot deal? Once you apply, i
  12. The divisions slider is backward also. Adding divisions shouldn't make the grid BIGGER, yet it does...
  13. I'm having trouble with some of the liquify tools also. Punch and pinch are backward (pinch expands around the cursor, punch squishes), and the push left and push forward brushes don't ado anything at all.
  14. That's not true. There are several alternatives to Adobe's suite now, like Capture One, Exposure, On1 that provide very similar functionality t what Adobe provides -- and in some cases superior. On1 and Capture one both have a better reputation as far as the final image goes, and both are closing the gap on asset management where it still exists with impressive alacrity. I've been using On1 for most of my asset management since Luminar has been so buggy and nigh unusable, and using Topaz, Imerge, or Affinity for more sophisticated retouching. Affinity doesn't NEED to provide a DAM, b
  15. I agree that the Luminar DAM functionality has been a tremendous disappointment, it's not the only alternative to Lightroom. I've been using On1 Photo Raw lately, that's improved to an impressive degree, and has pretty solid asset management functionality now. I haven't used Lightroom years though, so I can't compare.
×
×
  • 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.