bru
-
Posts
10 -
Joined
-
Last visited
Posts posted by bru
-
-
Nice ! This is what I was seeking for. I was not searching at the right place.
Thank you !
-
This message just to bring this topic up. Should be nice to get an answer... ;)
-
Something that is really missing me is a "paste as a new picture" function, Particularly useful when I want to annotate a screen copy, or to import from an external software in one operation.
This function was present in Photoplus.
-
May-be I have a work-around, but it looks very strange. I think there is a bug or something not properly supported.
To solve the issue, I simply disable the colour correction for my main monitor before starting affinity in the colour management panel of Windows. Once Affinity is started, I re-enable colour management. As long as do not restart Affinity, I do not see the problem while loading pictures.
Anyway, this is not very comfortable, And I am affraid having misunderstood something.
Finally, what I observe is this has no impact on file content, but only on display. I also observe that, when the problem is present, it is something like if Affinity would apply a correction on display that "counteracts" corrections due to the profile: my profile makes dark pixels darker, and affinity try to make them lighter, with quite a similar intensity.
If somebody from Serif staff may have a look and either explain or report...
-
Hello all,
First thank you to attempt to answer.
Nevertheless, modifying the profiles in "preferences/colour" does not produce any change to the display ! :(
I was understanding that these profiles in preferences were the default profiles for the file, and to my understanding, for a picture to be presented on screen, it should be sRGB IEC61966-2.1 anyway. Am I wrong ?
Please have a look to the picture below. It is a screen capture with the same picture presented in Affinity Photo (on the left) and in Windows 10 Photo (on the right). Please look to the difference in dark levels. The screen capture has been performed in one shot, with the two windows overlapping. Please don't take care that Windows Photo smoothes the picture a little. Anyway, it is easy to see that pixel colours are significantly modified, and the Windows Photo colours are identical to those presented by all the other software I have.

Note also that, if I disable colour management in Windows, the problem dissapears. But in this case, there is no longer any correction anywhere and the visual appearance will never be the right one. So this is clearly not a solution.
Note also that the problem is only in display, not in the file. In the experiment here over with RGB values, if I save the file and open it with another software, the pixel values are correct.
Finally, why Affinity photo would modify its display as a function of the display profile of the colour management module of Windows ? I was understanding that these profiles are used there to correct transfer functions at graphic board DAC level, to make the display matching the sRGB colour space. So, there should be no need for a correction at application level. Please explain me why I am wrong ! :(
Anyway, again thank for your help !
-
Hello all !
I encounter a problem that may be linked to some extent to the definition of profiles. This is a topic that has been discussed a lot in the forum, but I didn't find any explanation to the problem I encounter.
When I load a picture in Affinity (whatever is the format - I tried JPEG, 16 bit PSD, 32 bit EXR), I observe that pictures have a lower contrast when viewed in affinity than in any other image editing or presentation tool I have (Gimp 2.8, Photoplus X8, Paintshop pro X8, Windows 10 Photos, Cinema4d Visualiser), while they look identical in all these tools.
I also observe that, if I save the picture in a file, the file looks identical to the original one.
In Affinity, this loss of contrast looks mainly important in dark areas.
To make sure, I have drawn a rectangle with RVB colour 2, 4, 2 in Affinity Photo. Then I made a screen copy and paste it in Photoplus X8. If I get the colour of the rectangle pixels, I find RGB 13, 13, 10.
Please note that I use calibrated monitors (using a X-rite I1 profiler sensor) and therefore ICC profiles are set in the Windows colour management panel. I don't know if there is a relationship with the monitor profile.
The problem is that I generate pictures to be seen mainly on screen, so I need to see them as they will be displayed outside Affinity. Do you know a way to solve this issue ?
Thank you a lot.
-
I want to indicate that I encounter the same problem when I switch to affinity designer (release version) and I try to print from it.
-
-
Hello,
I tried to print a photo on a photo paper with size 4'x6' (10cm x 15cm), with a canon MG5500 printer.
I choose "adapt to printable elements" and paper size selected by driver (because I do not find the right size in the drop down list, but may be this has a name. In other software, I am used to see either 4'x6' or 10x15 cm).
When printing the picture it is overscaled by at least 2 and a random part of the photo is printed.
I was not having updated yet to the last version when I saw this problem, so I have updated now, but the problem is still present.
OS is windows 10 anniversary.
EDIT: I am very sorry, but I see I have not posted into the right section. This relates to Affinity photo beta. Is possible to move the message to the right section. Thank you.


Brush tip continues to revert to default brush with every stroke
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
I have the same problem, and I clearly do not understand the answers and explanations. Sorry !
I would imagine was that a brush that was selected when starting a drawing with the pencil tool was remaining selected for the next drawing. And setting the defaults does not work with a textured brush. I do not find where to change this behaviour.
And the fact that it is a "pencil" for me should be related to the way the path is defined, not to the brush to be used.
EDIT: I was saying behaviour was different in the past. I have restored previous releases and checked. I see behaviour is the same... So my memory is failing. I have modified the related part of my message.