Cobalt
-
Posts
47 -
Joined
-
Last visited
Posts posted by Cobalt
-
-
Hi guys, thanks for the responses.
Yeah, windows 10 here and I don't have a scroll wheel (I find this trackball more ergonomic than mice for 3D CAD work).
@Callum Scrollbars and/or Middle-mouse grab and scroll (like in Blender) would also help. -
When saving as package it includes Liberation Sans as a font. I don't know which text object is using it (can't find any).
Is there a way for Designer to select for me which objects use that font ?
-
-
-
If an image has effects and crops and such and want to convert it from embedded to linked without starting over, how do you do it ?
-
-
Is there a way to lower the top layer's luminosity without affecting the layer below it ?
(In this example the yellow must remain identical, but the tiles must be uniformly darker) -
-
Edit: Had the exact same problem. Looks like upon update the brush tool defaulted to something other than Normal blending.
-
3 minutes ago, Lagarto said:
If you stil have the print pdf of the book cover and open it in Photoshop, do you get the same values? If you do, I'd say the printer has made a mistake. One possible explanation may be that the deep black in the cover may have contained too much tint for their process and they have run a routine that reduces tint. In that process, the grays have changed, as well, but in a way that has caused cyan to become too prominent.
Yes, the PDF opened back in Photo displays neutral as expected and the CMYK values are mentioned earlier.
Thanks for your thoughts on this. At least I am not going crazy.
-
5 minutes ago, Lagarto said:
Certainly not. Did you get this with the mentioned CMYK values?
Yup !
-
5 minutes ago, Lagarto said:
Colors are complex. How badly were they tinted -- ever so slight cyan tone can be expected with these values, but it also depends on paper, and naturally on viewing conditions. If you want to have absolutely neutral grays, you should use mere K values.
@Lagarto Compared to the gray card (bottom of attached photo) there is a significant tint I think. Is this normal ? (unless we are looking at ghosting and their cyan plate is not properly aligned ?)
-
@Lagarto Thank you for explanation. It open as you say in photoshop indeed. It looks like some image editors ignore the color profile (like the attached image of the OP). XnView even reduces it to 8bit before opening it.
-
Indeed color management is a complex topic.
Recently I sent a PDF file to a printer (the Affinity document was in CMYK and I embedded the ICC profile during export).
95% of the file was neutral gray with a few touches of color in a couple of places.All grays came back cyan tinted. The printer argues with me that all my Cyan values are elevated like the OP example CMYK (60,52,52,21) and they claim it is my fault.
I don't understand why say that. I thought once they have the ICC they can work back to neutral.
-
-> ok, the jpeg is in CMYK format. Still, why does it look cyan ?
->So, when I sent this file to the printer (as a PDF with the ICC embedded) and their print is cyan tinted (like the jpeg above) whose fault is it ?
-
In Affinity starting with an RGB value of (100,100,100) translates to a CMYK value of (60,52,52,21).
-> Why so much cyan ?
-> Why is it different than this ? (here or here)
-> If I plug the CMYK (60,52,52,21) in reverse here I get rgb(80,95,95) with a cyan tint, but affinity says rgb (102,100,100). Why ?In the attached file the color format is set to CMYK with profile (US Web coated SWOP v2).
-> Exporting the file to PNG gives me correct result (exactly as shown on screen)
-> Exporting to JPEG with color profile included gives me a cyan tint. Why ? (it doesn't include the profile after all ?) -
10 minutes ago, carl123 said:
This post explains why you get half the size at 144
I also saw we get half the size at 96dpi when it should be 192dpi but I had lost the will to live by then
QuoteBecause your document is set to 144 DPI the Export Persona automatically creates half size exports when outputting to 1x format, the correct size when outputting at 2x, and double size when out putting at 3x. If you work at 288dpi, then your document will export at the correct size when using 3x, half size then using 2x and then half that when using 1x.
I don't even care to know in what universe such convoluted logic makes sense.
-
On 4/18/2019 at 7:05 AM, Sean P said:
Because your document is set to 144 DPI the Export Persona automatically creates half size exports when outputting to 1x format, the correct size when outputting at 2x, and double size when out putting at 3x. If you work at 288dpi, then your document will export at the correct size when using 3x, half size then using 2x and then half that when using 1x.
If you work at any other DPI other than those 2 then you should be ok!
Hope that helps!
I have no idea what you just said, neither would I ever remember it. Why trip up the customers so deliberately ?
-
@carl123. It's deliberate ? Exporting half the pixels at 96dpi instead of 192 ?
-
@Greyfox Using the export option via File menu works correctly.
This means, there is something wrong with the "slices" interface specifically in association to the 192dpi and 144dpi resizing options. -
@Greyfox. Somehow I am not quite convinced you are following the steps correctly. As of the slices tab, it doesn't matter (every document has a default full image non-deletable slice). If anything it means something is broken.
@carl123. BINGO ! Changing the dpi to 190 works as expected. At 192 it goes back to exporting half what it's supposed to.
-
The problem happens in Photo (Designer is using the same underlying code. So both should be affected).
One more time to make it super clear:
Resizing Dialog looks like this:
- Photo is reported as 1008x680
-The export persona reports 1008x680
The export dialog looks like this:
---> REOPEN the exported image and it is back to 504x340 -
Yes, resample was on by default and on my screen it shows 1008x680 every time, but the exported image is NOT the size it shows on screen during export.
-
How do we scroll down for panels ?
in Affinity on Desktop Questions (macOS and Windows)
Posted
Still an issue in 2.1