thomas001le

I tried increasing the file record interval but with no success. Then, just for fun I tried changing the renderer to WARP. And this actually fixed the crashes. Right now, this is 100% reproducable for me, WARP -> no crashes, NVIDIA -> crashes. I noticed that I still had MSI Afterburner running (allows to overlock the GPU). So I disabled it and tried again using NVIDIA, still crashes. I am running NVIDIA drivers 460.89. Now, this could mean a bug in Affinity's render code or a driver bug. Is there anything I can do to help debug this issue, so that it is fixed in future versions?

Hi David, thanks for taking a look at my problem! I checked the performance settings and it looks like RAM limit was already at 32GB: I thought, maybe that is too much, since 32GB will never be fully available, so i lowered it to 20GB and tried again and nothing changed. I tried to create another panorama and watch memory usage. I can confirm that it peaks at ~12GB. This time rendering the panorama completed, but just clicking on the "Transform Source Image" icon crashed Affinity Photo.

I am using Affinity Photo 1.8.5.703 on Windows 10 on a quite powerful machine (Ryzen 2700X, 32GB RAM, NVidia 2070 Ti) and try to stich a largeish panorama of 30 shots. Unfortunately, Affinity Photo repeatedly crashes when creating the panorama. The program crashes directly after creating the panorama, i just see a short flash of the window showing the stitched image when trying to use any tool in the panorama editor, it's enough to click the tool icon to make afifnity photo crash when minimizing and restoring affinity photo after the panorama has been stitched and is shown in the panorama editor I don't think it's a memory issue since the total system ram usage is just 20GB according to Windows' task manager (so ~12GB left). I use Nvidia's studio drivers, so those should be quite stable. I uploaded the source files to google drive since they are quite large (1 GB): https://drive.google.com/file/d/1EZI_VKYCYUlnFZkEj-P_FObZWtHYS76r/view?usp=sharing Some crash reports are attached to the post. reports.zip

Hi community! first a disclaimer: I am no professional designer in any way, I am just trying to do some photobooks of my travels. After having used dedicated photo book software that is directly offered by various book printing companies, I got more and more frustrated. Not only is most software slow and obviously targeted to the completely not tech saavy audience, all of it lacks basic features like "show me all images used in a book", "replace all images by newer versions". I even ended up writing some Python code that does some of those operations that the software should already provide. In the end I decided that I have better things to do with my time, so I started looking into more "professional" software for book design. Though I probably will never need 90% of the provided features, I hope that at least all my needs are fully covered. Long story short, I started looking into Affinity Publisher for book design. Using the software was pleasantly easy and I quickly got some nice results, but I was really missing one tool most dedicated photo book software have: a media browser showing you just all the images you have. From there on, I would be selecting a subset of images to be included in the book. Usually I do not know the correct selection before actually desiging the book as things like color composition along the frame landscape/portrait shoots make the image select very much dependent on the layout. And ratio of all images i have to the images i end up using in the book is usually around 50:1. Bonus points for a image browser that already marks images that have been used in the current book (any book). Using the Windows' file browser feels cumbersome and switching windows back and forth kind of interrupts the workflow and everything just takes longer. Is there anything like an image browser planned for Publisher? If not, what workflow would you recommend instead for my use case? Thanks, Thomas