Gregory St. Laurent
-
Posts
191 -
Joined
-
Last visited
Posts posted by Gregory St. Laurent
-
-
This doesn't seem to be an issue with Windows 11 (from FastStone), but my 2 other Windows 10 machines had the issue. A heads up if people are having trouble with the batch file, check your anti virus. Avast was flagging the batch file and putting it in Quarantine every time I would launch it. Took me a little time to realize what was happening. I added an exception, now all is well.
-
-
It is definitely something in your setup, I use Faststone to Affinity Photo as my workflow (for 5 years) and it works flawlessly. You need to add AP in the edit in external program dialog, it must point to the exact program path on your drive.
-
I also can confirm. Turning off parallel processing clears up the issue for me, so try doing this as a work around until a fix is issued.
-
On 12/7/2021 at 3:31 PM, Patrick Connor said:
Additional Cameras supported by SerifLabs RAW engine in all Affinity Photo Desktop 1.10.5 builds (going forward)
-
DJI
- Mavic Air 2S
-
Fujifilm
- GFX 50S II
- GFX 100S
- X-E4
-
GoPro
- HERO9
- HERO10
-
Nikon
- Z fc
-
Olympus
- E-P7
-
Panasonic
- DC-GH5 Mark II
-
Pentax
- K3 Mark III
-
Ricoh
- GR IIIx
-
Sony
- A1 (ILCE-1)
- A7R-IIIA (ILCE-7RM3A)
- A7R-IVA (ILCE-7RM4A)
- ZV-E10
- Multiple Camera Phones added
-
Canon
- EOS M50 Mark II (was supported but not listed in camera list)
Is there any chance in the near future that the Sony A7 IV Lossless Compressed RAW files will be supported? Thanks
-
DJI
-
12 hours ago, walt.farrell said:
The Affinity applications provide some functionality like that, and Windows itself provides some more, I believe. Perhaps this FAQ article will help:
Thank You! I will try this on my laptop. I didn't know there was this granular control over selection, I thought it was all or nothing
-
On 11/1/2021 at 10:14 AM, Andrew7D said:
I have been experiencing Affinity Photo hanging randomly since upgrading to version 1.10...
I am using a Dell XPS with an Nvidia 1080 GTX graphics card and Windows 10 pro 64 bit, with all drivers up to date.
Switching off the hardware acceleration 'cured' the problem, but I noticed that my system also has an integrated Intel UHD GPU and both were shown in the Preferences window. I have now disabled the integrated Intel GPU (via device manager) and use just the Nvidia card with hardware acceleration enabled, and so far haven't had any further issues. It would seem that in my case there is a conflict between the two GPU's
I think you are on to something here. I just upgraded my desktop setup which has no integrated GPU (with a RTX 3070) and everything runs flawless, my laptop on the other hand has an integrated GPU along with a GTX 1060 GPU and I see artifacts and hangs. It would be great if they could add a feature to choose which GPU's we would like to use. To be fair the newer .4 update is working much better on my laptop.
-
19 hours ago, Mesquito said:
1.10.4 appears to have corrected the issues that I was having with funky square boxes and pixilation under 1.10.3.. Thank you.
Me too, but I will have to do some more testing to confirm that it is totally gone. But it looks like it is!
-
1 minute ago, Lee D said:
Thank to everyone for letting us know, it's been logged with the developers to investigate further as it does seem to be related to hardware acceleration. In the meantime if you disable it in Preferences > Performance you should be able to continue using the app.
Yes, as soon as I disable acceleration the problems disappear.
-
13 minutes ago, Galm said:
I have a similar setup (gtx 1660 super; 32gb ram; i7 processor, win10), and just applied unsharp masks and clarity filters to a bunch of photos, with acceleration on, without any problems. Could it be the graphics card driver? I'm using the studio version, currently 472.12.
I've tried a few, including removing the driver and reinstalling a clean install of the latest version. I will check again to see if I tried that driver.
-
1 hour ago, r0b_k said:
Hello everyone,
I had the same issue,
altough i could not reproduce it after a clean reboot and resetting photo.
by pressing CTRL while starting the applicationWell, its back. I only get this when using unsharp-mask and clarity filters. I guess it depends on the performance lvl of the GPU.
Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
NVIDIA GeForce GTX 1080
Microsoft Windows 10 Probest regards,
r.Yup looks familiar, I'm also getting it in the Develop persona.
-
I'm having a lot of issues with HD acceleration with the new 1.10.3.1191 that I didn't have with prior 1.10 versions. I've tried newest driver, uninstalled old driver and installed clean (ver 496.13) but I'm still getting graphic artifacts, breakups and program lockups, had to resort to turning acceleration off. i7 7700, nVidia GTX1060, 32 Gb Ram on Windows 10 21h1
-
I was having the same problems with freezing with my GTX 1060, I determined that the nVidia 471.xx series of drivers were causing the issue, I installed the June 466.77 drivers and all my freezing issues went away. Latest drivers aren't always the best.
-
On 8/24/2021 at 5:17 PM, RichardMH said:
Froze with OpenCl acceleration on, Nvidia GeForce GTX 1650 SUPER. Up to date driver 471.68. Managed to get a dump file but its 12Gb. Do you want it?
FYI All the nVidia 471.XX series drivers freeze Affinity photo on me but when I reverted back to the nVidia 466.77 drivers it works perfectly! Sometimes the latest driver isn't always the best, try playing with different drivers.
-
-
On 8/12/2021 at 6:22 PM, Laika said:
I'm using the most recent NVIDIA drivers... easiest just to disable HW acceleration.
I myself was having issues with the Latest nVidia drivers, try a slightly older driver. I did and all my issues went away. The HW acceleration is worth the effort!
-
After completing editing on a substantial photo shoot, I can confirm major performance improvements with ver 1.10 Great job Dev's! Affinity Photo is better than ever!
- NotMyFault and Patrick Connor
-
1
-
1
-
Affinity Photo seems to have a few issues with DNG files. I experience weird color cast when importing DNG files (with bright highlights) created with DXO PureRAW. I was hoping ver 1.10 would have cleared up the problems. Hopefully they will address it soon.
-
15 hours ago, foxxweb said:
If I open an image and start to work on it after very little time and doing next to nothing AP freezes and i have to use Task Manger to shut it down.
I have 32Gb RAM
In performance RAM usage limit was set to about 4Gb so I upped to 28GB and now its worse
I was experiencing freezing also and it was do to the latest nVidia drivers. Try changing drivers for your GPU or turn off hardware acceleration to see if it is GPU related.
-
3 hours ago, i5963c said:
I encounter regular freezes of Affinity Photo in recent days. These problems were certainly not happening last week!
My system setup is as follows: Windows 10 Pro (up to date), AMD Ryzen 3090X CPU, Nvidia RTX3060 GPU (with 12 GB dedicated GPU memory, driver update of last week), 32 GB of RAM, Affinity Photo 1.10.0 (latest 'official' version), HW acceleration ON, Wacom Intuos PTK640 tablet (drivers up to date).
This setup worked flawless till last week (apart from a different bug that I reported recently in relation to pattern layers, but this bug is not related to the workflow that triggers my actual problems).
Context:
I'm working on a large photo restoration project. It includes many old photos (some of them almost 100 years old), that I've digitized with a high resolution camera and a macro lens.
My standard workflow is as follows:
- Capturing of the pictures happens via tethering in Capture One. B&W conversion, perspective correction, cropping, and, if required, some dynamic range adjustments also via Capture One.
- Then, further processing in Affinity Photo (via the 'Edit with...' menu option of Capture One). The transfer between both applications happens via 16 bit TIFF files with the AdobeRGB profile.
- In Affinity Photo, I duplicate the background layer. To this layer, I (optionally) apply a 'Dust and Scratches' live filter that I tune to remove some of the finest scratches (common problem with old photos, easily visible with a sharp macro lens). If appropriate, a mask is applied to the live filter (e.g. to avoid loss of sharpness around the eyes, which I may restore manually in the next step - see below)
- Next, on top of the duplicate background layer, I create an empty pixel layer that I use to remove further blemishes in a non-destructive way, via the Inpaint brush (with the 'Source' parameter set to 'Current Layer and Below').
- Depending on the picture, I sometimes apply further external filters from within Affinity Photo (Silver Efex Pro and/or Topaz Sharpen AI), after first 'merging all visible layers' to make sure that the external filter is applied to the 'combined' native Affinity layers.
As said, till last week, this process worked perfect.
Now, this same process makes that Affinity Photo freezes after some strokes with the Inpaint brush. The only thing that I changed for my system (in recent days) is the update to the most recent version of the Nvidia drivers (from version 471.41 to version 471.68).
Whenever I execute my regular workflow, I notice (via the Windows Task Manager) that the Dedicated GPU memory usage grows very fast from the initial 'stable' position (around 2 GB used) towards its limit (just below 12 GB), and then, Affinity Photo freezes (the message 'Not responding' appears in the top-left corner). It doesn't crash (so, no dump files), but it just remains in an endless frozen state. The only way to get out of it, is to kill the application.
Further findings:
If I don't apply an empty pixel layer to draw strokes with the Inpaint brush, but if I apply the Inpaint strokes directly on the duplicated background layer (= destructive editing), there is still an increase in the memory usage, but this increase is much lower, and - so far - I haven't been able to freeze Affinity Photo. To me, this looks like a memory problem in Affinity Photo.
As a next experiment, I disabled HW acceleration. In this situation, Affinity Photo doesn't increase the usage of the dedicated GPU memory, but what is very strange in this scenario (at least to me) is that the GPU (3D graph in Windows Task Manager) shows a percentage of up to 33% whenever I use the Inpaint brush. I would expect that the GPU is not used when HW acceleration is switched OFF?
Because the above workflow worked perfect till last week, and the only system change (I can remember) is the driver update of the Nvidia GPU, I wonder whether there is a way that I can downgrade this driver? If this is feasible, thanks to let me know whether this is advised, and how it can be done in a safe way.
Many thanks.
I experienced freezing also when I update to the 471.41 drivers, I reverted back to an older driver and my freezing disappeared.
-
1 minute ago, JeffreyWalther said:
This is my video edit workstation and the system with my video editor is well tuned. I think it is more a memory management issue inside Photo (as it always was). Because I can edit 4K footage (RAW) with much more and higher demanding effect and color, non-destructive processing without a problem. And video is really demanding. Editing photos with some 15-20 layers is a just a joke compared to it – or at least it should be.
You can't compare how one program runs to another, just because your video stuff runs perfect doesn't mean all programs will run perfect. That is the nature of computers, I run into this all the time. I run a $10,000 3D CAD workstation where I work it was running perfectly, until an update to Adobe PDF reader installed in the background. Out of nowhere my CAD software would lockup every 10 minutes took me days to figure out what was going on, all my other software was working fine. Just saying.....
-
9 hours ago, Penime said:
After a few moments of work, Photo just does not respond, and I have to close it and reopen it like this all the time, I use version 1.10, but it's also was with previous version 1.9, I did not notice if it actually happens when I do something specific.
I have attached a DUMP file and a video
Does anyone know of a version that does not crush?
crashpad_handler.DMP 29.66 MB · 1 download Photo.7z 549.64 MB · 1 download
I was having the same EXACT problem and I believe it was the latest nVidia drivers, because I reverted back a few driver revisions and the problem went away. I don't know what your hardware is but play around with the drivers, and the newest isn't always best as I found out.
-
22 hours ago, JeffreyWalther said:
CUDA support (hardware acceleration) in Affinity Photo is unfortunately not usable in version 1.10 either. Despite the latest NVIDIA Studio driver, the operation in Photo is very delayed and jerky. You still have to deactivate the acceleration to be able to work reasonably.
I noticed you are on the latest nVidia drivers (471.41) those drivers were giving me problems so I reverted to a few revisions back and all my problems disappeared. You may want to try a different driver, newest isn't always the best!
-
Hi, I'm just curious if any progress was being made with the various problems that happen using DNG files. I've seen a few other posts with issues with DNG files similar to mine. Thanks
Affinity Photo 2 for Windows - (2.0.3)
in News and Information
Posted
Great update! V2 overall has met or exceeded all my expectations! Thanks for the awesome work!