walt.farrell
-
Posts
43,565 -
Joined
-
Last visited
Posts posted by walt.farrell
-
-
9 minutes ago, Old Bruce said:
But I see it happening a lot.
I have not noticed it yet, on Windows. I have not looked at it on macOS.
-
2 minutes ago, thomaso said:
I can't follow your conclusion. The fact that faulty GPU driver software causes issues does not affect the question whether Affinity is fully compatible with Hardware Acceleration in general. If Affinity would be fully compatible then all these issues were caused by faulty OS or drivers but not by Affinity – which appears odd if you consider that apps and documents are coded for specifications given by the OS, not vice versa.
The applications are coded for specifications such as the OpenCL specifications, which are not provided by the OS but by an industry consortium.
The drivers and GPUs are also coded for those specifications.
Any of those (the application, or the drivers and/or GPUs) could be coded incorrectly. Sometimes it may be Affinity, but sometimes it is the drivers or GPUs that have the issue.
6 minutes ago, thomaso said:For Windows it appears additionally confusing that Hardware Acceleration is an Affinity System Requirements although + while this feature in particular may need to get disabled by users in case of lacking compatibility.
The Affinity applications will run without that requirement, as far as I know. And if the GPU/driver does not provide it, the settings will be disabled automatically by the application. The problem comes when the GPU/driver claims to provide OpenCL and Direct 3D level 12 support, but does not provide it completely or correctly or fully, then Affinity will enable it based on the GPU/driver's claims, and problems will result.
9 minutes ago, thomaso said:But hardware acceleration not only causes rendering/display issues, but can also cause Affinity to freeze or crash, according to related posts.
Both freezing and crashing can be due to errors in the GPU/drivers. It's not just display problems.
10 minutes ago, thomaso said:Could Serif use their existing "Benchmark" test code, perhaps augmented with display feedback, to provide a reliable recommendation for an "optimal" performance setting for any specific, individual hardware/software configuration?
I have no idea what would be possible in this area, but it's an interesting idea.
-
2 minutes ago, Pšenda said:
Ctrl+H?
That is Hide, not Delete.
-
Generally the resize step will do something, but will do it in a way you won't like. It would distort any image you apply it to that does not have the same aspect ratio as the image you used when recording the macro. And that probably is not what you want.
The usual recommendation for resizing images using macros is to use Filters > Distort > Equations which will not have that problem.
You can find more on doing that in the Resources section of the forums: https://forum.affinity.serif.com/index.php?/search/&q=macro resize&type=forums_topic&quick=1&nodes=11&search_and_or=and&sortby=relevancy
If your macro is truly doing nothing, I'm not sure what might be going on.
-
@PeFreeDoM: Which Affinity application and which release of the application are you using?
-
On 4/20/2024 at 10:12 PM, Nanette2024 said:
at how slow the response is to commands
What commands?
What OS?
-
In the Data Merge Manager you can specify the separator you want to use:
But using LibreOffice Calc, I have no problem generating a CSV file whose fields contain the "," character, and which uses the ";" as the separator. And as mentioned above, any fields that contain a "," are automatically quoted. And the file works properly for Data Merge.
Samples (using Publisher 2.5.0.2402, but should open in Publisher 2.4):
-
17 minutes ago, Komatös said:
Kann ich nicht nachvollziehen. Wenn ich ein Dokument in Millimetern anlege, eine Linie zeichne und diese Linie mit dem Maßwerkzeug ausmesse, wird der Messwert bei mir auch in Millimeter ausgegeben.
This topic is about the Rulers in scaled documents, e.g. a document with 1:10 scaling specified in the document setup.
-
14 minutes ago, MikeTO said:
Em/en quad serve no purpose in digital typography which is why Affinity doesn't show special characters for them, they take up the same horizontal and vertical space as em/en space. I just included them in my chart for completeness in case anybody stumbles across them, especially when importing text from another application.
From your description of them, though, em/en quad are not "non-breaking" like em/en space are, which would seem to give them a purpose: An em/en space if the surrounding characters are on the same line, but do not force them to be on the same line.
Or should their description be amended?
-
-
8 minutes ago, PeteBoi said:
Although I have no idea what the abbreviation UI stands for
User Interface
You could type UI into the search box in the Help, and this is the first result:
https://affinity.help/photo2/en-US.lproj/pages/Workspace/uiAppearance.html
Glad you have it working now.
-
1 hour ago, thomaso said:
It appears that Affinity doesn't fully support "Hardware Acceleration" of various computers and/or operating systems, right?
I don't think that's quite right, at least for Windows.
On Windows, the GPU and its drivers indicate their capabilities, and if they claim that they support the correct levels of processing and OpenCL, then Affinity Photo trusts that they are telling the truth and allows you to enable Hardware Acceleration.
Issues can arise when the GPU or drivers lie about having the proper support, or they have implemented the support incorrectly. (Or, I suppose, if Affinity Photo is using it incorrectly, but I'll ignore that as we have seen definite cases where it is the drivers that have the issues.)
1 hour ago, thomaso said:So I wonder if the app would be able to selft-test its compatibility on a specific configuration with the goal to choose the 'optimal' (most compatible) setting automatically
I'm not sure to what extent that would be possible. If the error is one related to the on-screen display, such a test would require that the application be able to contain a copy of the expected screen display given a particular starting point and sequence of applications, and that it then be able to perform those operations and then retrieve, from the GPU, the current screen display to make a comparison. If that that retrieval is possible, then what you propose sounds like an interesting idea.
-
I would also recommend watching the Tutorial videos from Serif, and other YouTube videos about the Affinity suite.
There will be significant differences, and probably you will need to learn about them and figure out how to adjust your workflow. But that is probably true if you were to switch to any different software package.
-
Welcome to the Serif Affinity forums, @roelandvbb.
That seems like a complex workflow, with a bit of ambiguity in the way you've expressed it.
Your use of "import" makes me think that perhaps you are creating a document, then using File > Place to add your DNG file to it as an Image layer, rather than Opening the DNG file directly. Do I have that right?
-
Welcome to the Serif Affinity forums, @Chris Bartlett.
I haven't experienced that, nor seen reports of it from others.
What OS do you use? And what is your monitor setup?
Can you give us a screenshot of what you're seeing?
-
7 minutes ago, Wayne Burrows said:
And by looking at the absolutely ridiculous difference in size, I believe that I made a mistake by choosing to use the EXE files last time.
Windows reports the sizes of the MSIX versions incorrectly. They are approximately the same size as the EXE/MSI versions.
Have fun
-
20 minutes ago, NotMyFault said:
While using Develop Persona:
For Raw images processed with the Develop Persona, you can also set it to Develop to a Raw layer (not a Pixel layer), then immediately click Develop without making any changes. Then you can start recording a macro, and within the macro you can go back into the Develop Persona, make your changes, and click Develop again. Then, back in the Photo Persona, you can stop recording the macro, and save the macro into the Library.
You can then apply that macro to other Raw images, either manually or via File > New Batch Job.
But I agree that for mass editing, this is cumbersome.
-
21 minutes ago, PeteBoi said:
but step 3 failed as there are no 'Persona' or 'UI Elements' in the two pop up menus, (or any other menu/pop up) that I can find in the Shortcuts pane. Clearly I must be doing something stupid. All help/suggestions welcome.
It should start out looking like this, where Photo is the Persona, and Affinity Photo 2 is the UI element (aka menu item).
You need to change the second one to View.
-
18 minutes ago, Wayne Burrows said:
Now, that didn't apply to the intermittent updates that pops up every month or so, correct? Only for an initial install, correct?
No, every one.
In V1 you always had to go to the download page, manually download, and run the installer/updater.
In V2:
- with MSIX, you are prompted to Install or skip for now. Install automatically downloads the installer/updater, runs it, and restarts the application.
- with EXE/MSI, it's just like V1: you are prompted to Download or skip for now. Download takes you to the website where you must manually choose the correct version of the update program (MSIX, which is very prominent, or EXE which is more hidden), download it, and run it.
21 minutes ago, Wayne Burrows said:Before the most recent update a few weeks ago, I never had to leave outside of the Affinity app to go retrieve a file to get the latest version. When the notification popped up about a newer version was available, I would just simply click it and It would automatically install the latest version right then and there. I think the most that I had to do is just re-open Affinity to continue on with my work.
So that sounds like you were using the MSIX version, which makes it strange that you lost your settings. Except that perhaps you're confused by the beta having different settings than the retail version has. The first time you ever ran a V2 beta, it would have offered to copy settings from the retail version. But only that first time. Any changes you made to your retail application settings after that would not be copied into the beta. (You can copy most of them from retail to beta using the Settings dialog in the beta, which has a Beta section that will allow you to copy the retail settings again.)
24 minutes ago, Wayne Burrows said:Is there a way to save your profile's settings?
The MSIX versions keep their information in %USERPROFILE%\.affinity and you could backup various files or directories from there, and restore them later if you needed. The EXE versions use %AppData%\Affinity for the retail version, but something different for the beta from an experiment I just did. I need to do some more research on that before saying more.
-
32 minutes ago, Wayne Burrows said:
Now that I know that those 2 files aren't connected in any way, I will make sure to use the MSIX downloads from here on out and hopefully I won't have to deal with this again.
Looking at your description again, yes, I think you were using the EXE/MSI version before. Which would mean you made a conscious decision to switch from the default MSIX to the EXE/MSI at some point. The EXE/MSI version has always required you to manually download the installer, and manually run it, even back in V1.
But when you go to the Download page for V2 during the update process, you need to be careful to choose the EXE version again, as the MSIX version is more prominently shown.
If you were using the EXE version before, you may well want to uninstall the MSIX version you just installed, redownload, and reinstall the EXE version. Then you'll have the advantages of the EXE that you perceived before, and your old settings back.
-
20 minutes ago, Wayne Burrows said:
(which can't be automatically done any longer from within the app for some irritating reason and now forces you to go to their website to download the file all over again to reinstall it from scratch – which is aggravating as @#%%^!!!!)
I (and I think most other users of the beta) have had no problem updating from the 2.4.2 beta to the 2.5.0 beta. Perhaps we should look at the issue had with the update in more detail?
Please provide more information.
-
Have you tried Exporting as a TIFF with the option Save Affinity Layers enabled? That gives you a TIFF file which your DAM should be able to handle, with a .afphoto file embedded in it for Affinity Photo to use.
-
No, there isn't.
You could Save or Export them to a specific folder, then later in File > New Batch Job you could easily select all of them to add to the batch.
But there's no way to do what you're asking, today.
-
22 minutes ago, Petar Petrenko said:
It supports layers. What you mean with "other data"?
Think of all the kinds of things you can have in an Affinity document and save in PSD format.
But really, something like JPEG XL is no different in this area than something like TIFF. Photoshop can embed a PSD file in a TIFF container, and Affinity can embed an Affinity file in a TIFF container, but that doesn't help interoperability. It's not the format specification of TIFF or JPEG XL that matters for that, but the format and documentation of the data it's going to contain.
That is really what needs standardization.
Invert layer selection
in Feedback for the Affinity V2 Suite of Products
Posted
Good point. But Ctrl+H is still hide, not Invert Layer Selection.
Beyond the ones in the earlier topic that resulted in the creation of this one, no.