ABack
-
Posts
9 -
Joined
-
Last visited
Posts posted by ABack
-
-
@Lem3, that is a DCH packaged driver, so I will wait for 511.x to be available as a Standard package.
The point I was making about updating the driver is that it had no impact.
None of the other applications I use are having problems, most notably Affinity Designer that also uses OpenCL acceleration, so my interpretation is that the realm of the bug must be within Photo, not with anything external.
-
So, yes, it also appears to be stable with Renderer set to the Quadro and H/w Accel (OpenCL) turned off.
And to be honest, I cannot really tell if there is any performance hit from turning off hardware acceleration.
Apologies if this turns out to be a duplicate issue. I did a search and could not find anything that exactly matched my experience.
-
Sorry, yes, forgot to mention that I have left the OpenCL acceleration enabled. The only thing I have changed to stop the crashing is the Renderer.
The text under the Hardware Acceleration option indicates that it is using both the Quadro and Intel UHD.
I will try it the other way around, with Renderer set to the Quadro and H/w Accel turned off and let you know.
-
This is on a workstation laptop (Lenovo P17) with an i7-10850H and 32GB memory.
I have had to change the Renderer in Performance Preferences to Intel UHD Graphics to stop the crashing. This is a recent problem that started in one of the 1.10.x drops, but seems to be worse in 1.10.4.
The crashing happens after doing a few operations. It does not seem to matter what those operations are. An easy example is adding pics from Stock, then deleting some of them. It seems to be worse when using other programs at the same time that use the Quadro for 3D acceleration (e.g. Blender).
The symptoms are that Photo freezes and then after a while Windows reports that "Photo is not responding" and the only way to recover is to kill the program and start again.
I tried updating to the latest Nvidia Studio driver (472.84), but this made no difference.
I also have Designer and Designer is rock solid with the Renderer set to the Quadro. I have a similar laptop (older model with essentially the same specs, previous gen i7 but also including a Quadro RTX 3000) for personal use with the full suite (licensed separately, of course) of Photo, Designer and Publisher, and Publisher is also rock solid while using the Quadro as the Renderer.
While I am pleased that I have a workaround, so I can work in Photo without the interruptions from the crashes, it means I am not able to fully utilize the power of the Quadro RTX card. So here's hoping there will be a fix in the next update to Photo.
If you need more information, please let me know.
-
Update: I thought it was working but sadly it is not. I have tried several sequences of using the dialogue box and no joy. I am using Photo 1.10.1. Maybe it was OK in 1.10.0 and is now broken again.
------------------------------------------------------------------------------------------------------------------------------
Thanks John - very much appreciated.
Yes, I got that to work after a couple of tries as the macro recording is sensitive to how you use the dialogue box. For anybody else, make sure you press <Enter> after typing in the required DPI, and then uncheck Resample. If you do it the lazy way (like I did at first) and don't press <Enter> in the DPI box, the macro will still change the resolution.
- John Rostron and telemax
-
2
-
So, yes, I am using Windows 10. I should have included that to start with. I had no idea that OS X uses a different control. GarryP, I very much agree that a drop-down list is easier for this. I hope this does not get "fixed" by changing to a slider in the Windows build.
John Rostron, thanks, but no thanks. I am working in a corporate environment and downloading from an unknown link is definitely not going to happen. What really needs to happen, on this front, is that whatever worked in 1.6 needs to work now, so that macros can sensibly use this dialogue to change DPI without affecting resolution. That would be enough of a fix for me, as a macro is a one-click operation and there would be no need to even open the dialogue box.
-
Fair enough that you might not have ever used this value, or had cause to use it, but it is a relatively trivial thing to implement that would save me a lot of time and also for anybody else that uses it. I mainly use 150dpi for setting the initial scale of screenshots for use in manuals, so I need to do this quite a lot. It is a preset in Photoshop, which I have ditched in favour of Affinity Photo. It is the only thing I miss from Photoshop. There are other applications where 150dpi is a preset.
I would use a macro, but no joy there.
I searched the forum for "150" before putting in this suggestion. There are a number of references to 150 dpi or ppi returned by that search, so I am not alone.
As the saying goes, if you don't ask, you don't get.
-
150dpi is a very common setting for images. However, this is not one of the preset values in the drop-down list in the Resize Document dialogue box. Given how often I need to use this (and probably others as well), it would be a great timesaver to have this in the list, instead of typing in "150" every time I need it.
Alternatively, an option to have user defined DPI or recently used values would be good.
Default Save As to Any Format
in Feedback for the V1 Affinity Suite of Products
Posted
TLDR: I support this proposal to Save As to other formats, as well as the native format. This would provide a more efficient workflow for a good chunk of my job.
Please embrace a small paradigm shift and make it so.
Long version:
I also want to be able to Save As directly to PNG or other standard image formats, without using the Export dialogue. Especially in Affinity Photo, but this would also be useful in Designer (e.g. to save directly to PNG, SVG, etc.). Not so sure about Publisher, but there are some scenarios where this would be useful. I use all three products on Windows, and I the whole suite licensed for work and I have also bought the whole suite for myself for personal use (i.e. separate licenses).
I do not see how this could be objectionable, as many many other similar pieces of software have this functionality with Save As.
There are two main reasons, both of which slow down my workflow:
1) I do a lot of minor edits on screenshots to tidy them up (the Inpainting tool is my best friend), brought in with New From Clipboard. I don't need to save a whole .afphoto or .afdesign file to preserve the edits. I am well and truly experienced enough to decide when is a good time to preserve a file with the native format or when is a good time to do some quick and dirty edits and just save directly to PNG etc. I just want to hit Ctrl+S, give the file a name and move on. An extra inefficient bit comes when closing the file, as you get asked to save the changes (even though they are already saved with Export). This might not sound like much, but when you are working with 10s or 100s of screenshots, it very much adds up.
2) When you do Export for an <Untitled> file, exporting does not set the file name. For example, if you use New From Clipboard (from a screenshot or whatever), the file is <Untitled>. Let's say you do some minor edits and Export to PNG. Then you want some other minor tweaks and just want to overwrite with Ctrl+S - this does not work as the file is still <Untitled>. Instead, you have to Export again, and then pick out the file to overwrite (potentially error prone). There are, of course, other ways around this, but all of them need extra steps - hence the inefficient workflow.
What is frustrating is that you can open a PNG in Photo, make some edits and then hit Ctrl+S to save the changes. If you have layers, it just asks to flatten them. I just need that same functionality with <Untitled> files.
This DOES NOT make the Export dialogue redundant, but Export should be used when you want to do something different with the file. For example, save a different sized image to PNG, JPG, etc (I do this a lot), save as PNG or PDF without changing the file type on the working copy, etc.
Just to say, I find the software generally excellent, and I much prefer the Affinity suite to the equivalent bloated Adobe monoliths. Please keep the Affinity suite nice and clean and free of annoying things (like constantly running a background process all the time just to make sure the s/w is legit and the user hasn't cheated the license in the last 5 minutes or whatever - Adobe, I'm looking at you).