Jump to content


  • Content count

  • Joined

  • Last visited

About ygoe

  • Rank
    Advanced Member

Contact Methods

  • AIM
    does that still exist?
  • Website URL
  • ICQ
    8 digits, long forgotten
  • Jabber
    not in use anymore
  • Skype

Profile Information

  • Gender
  • Location
    : erlangen.de
  • Interests
    Software Development, Fine Art & Travel Photography, Webdesign

Recent Profile Visitors

421 profile views
  1. ygoe


    I've found your previous post on this topic in the other thread. These numbers are better than the last ones. But I first found this post and wondered, these aren't especially good numbers, are they? 25 seconds for startup is – ages! Felt, at least. I've just measured 1.6.5 and startup times on my computer (Win 10 x64, i7-3770, 16 GB). After a few iterations for warmup, it's 20 vs 15 seconds. Not much better. I'm still waiting for that thing to let me start working. While 1.6 shows the splashscreen (with "loading fonts") for almost all the time, the 1.7 beta shows the splashscreen half the time while the other half I've got an empty application window with a spinning mouse cursor. If that second half of the waiting could go away, I'd be much happier!
  2. Looks good. I couldn't find any such errors at numerous zoom levels. Thank you.
  3. The perspective live filter doesn't render properly. I've moved the corners of an image so that they match the position where the embedded image should be placed in the outer image. While that generally does work, parts of the embedded image become invisible at certain zoom levels. It looks like AP partitions the embedded image into rectangular blocks with vertical and horizontal edges. Some of these blocks are missing when zooming in. On every zoom level, different blocks are missing and not rendered. This makes it hard to paint a layer mask at the edges of the embedded image with changed perspective. Sometimes when I have the mask layer activated and a brush with black colour, when hovering parts of the image, other random (but not too far away) areas show similar rendering errors. I believe this comes from the preview nature of the brush outline, which also affects the perspective filter layer rendering. Affinity Photo on Windows 10.1709 x64 (Windows Store installation) CPU: Intel Core i7-3770 with embedded GPU Demonstration video
  4. That sucks. Additionally, Affinity cannot export to TIFF without anti-aliasing. So I'll have to go back to the dark Middle Ages: Export to a modern PDF with Affinity, then convert to the printer's PDF/X with Adobe Illustrator. Affinity just isn't there to replace it yet. I hope this conversion doesn't break things only visible on paper.
  5. @Callum, did you have a chance to look into why this bug happens? I need to produce that file soon and would have to take the detour with Affinity Photo. Additionally, that method clips my bleed area, so it produces even more work. For now, I'll have to drop the background and consider it impossible to use with Affinity/PDF. I'll check with the printer what resolution of a raster image (without anti-aliasing) I need to provide to get as sharp text outlines.
  6. It looks the same. I can still provide a screenshot this evening if you like.
  7. Ah, I found it. Linear gradients are okay, but radial and elliptical gradients not. And the background of the raster image rectangle doesn't seem to be a single colour but rather a bad copy of the actual gradient behind it. Here's a sample file. Export with the PDF/X-3:2003 preset and disable JPEG compression just to be sure. Then look at the file in current Acrobat Reader. Interestingly, a linear gradient in the background seems to be exported with transparency, which PDF/X-3 prohibits. The other gradients are rendered in the bitmap image background, just with the wrong colours. So every gradient background seems to cause problems with PDF/X export. PDFX-Gradient.afdesign
  8. I'm trying to reproduce with a test case but cannot do that for now. Simple files are exported fine, but my 70 MB file fails. I'd rather not upload that file anywhere so I'm trying to find a smaller test case.
  9. I'm designing a layout that shall be printed. The printer requires a PDF/X-3:2002 file. My Designer document contains a circular gradient in the background and transparent bitmap images on top of that. When I export the image with current PDF compatibility, everything looks good. But in PDF/X mode, the bitmap images have a solid background that doesn't correspond to the gradient in the background. You can clearly see a rectangle around the images with a different colour. That colour seems to be what the gradient has at one edge of each image, but on the other edge it should of course be another colour, it's a gradient. Is this a bug in Affinity Designer 1.6.5 or should I use different export options? Update: It might be a work-around to rasterise the gradient, but that also behaves strangely. When I use the "Rasterise..." command, the rectangle is immediately converted to a raster image. The three dots usually indicate a dialog with options showing up, but that didn't happen. The operation immediately started. And it produced a bitmap of different dimensions. The bleed area is then lost on three of the four sides. It is only left there at the bottom edge while the other three sides are cropped to the artboard. (To the bottom there is another artboard for the back side.) Rastering everything in the PDF export is unacceptable because it also converts the text into pixels, which are furthermore anti-aliased. That screams for very blurry text when printed.
  10. But when I set the artboard size to the cut size, I can't see what's in the bleed area anymore. How should I control what is placed there when it's not accessible?
  11. I don't get it. I've created a document with two artboards. Each of them has a final paper size of 85x55 mm (front and back side). The bleed should be 3 mm on top of that. So my document and artboards have now 91x61 mm with 3 mm margin and 3 mm bleed on each side. Now I need to export that as PDF with cut marks. But whatever I select, I get the cut marks at 91x61 mm, not at 85x55 mm. What should I do to make this basic print export task work? I mean, in Adobe Illustrator this always worked intuitively and never caused any problems or even questions. In Affinity designer I stumble over this thing every single time. Most of the time I didn't care because I didn't need cut marks, but now I do and they just don't work. Please advise now and fix in a future version. Affinity Designer 1.6.5 on Windows 10.
  12. Well, then there's something wrong with my copy of ADesigner. I did more tests now and the PDF export indeed works with the desktop install version on two computers. It still fails with the Microsoft Store install version on one computer (not installed that way on the other).
  13. Oh, here's a demo file. The TIFF and the afdesign. Freshly created with APhoto and ADesigner. Can't export the afdesign file to a PDF with default settings. The TIFF image has been added to the afdesign file by dragging it in, you you could create one yourself, too. Grey.afdesign Grey.tiff
  14. I get the error at default settings. Here's your daily German lesson.
  15. The log file consists of a listing of all my installed fonts. In the end, there's a tiny bit of what I'd consider an error. Here it goes: PDF_begin_document_callback(p_0x000001D08F5FC740, wp_0x00007FFF44DF63F0), "removefragments=true autoxmp=true compatibility=1.7"[Begin document #1] PDF_set_info(p_0x000001D08F5FC740, "Title", "test.pdf") PDF_set_info(p_0x000001D08F5FC740, "Creator", "Serif Affinity") PDF_set_option(p_0x000001D08F5FC740, "compress=9") PDF_set_info(p_0x000001D08F5FC740, "trapped", "false") PDF_create_pvf(p_0x000001D08F5FC740, "/Serif/profile/Coated FOGRA39 (ISO 12647-2:2004)", /*c*/0, data_0x000001D08C210000, /*c*/654420, "") PDF_load_iccprofile(p_0x000001D08F5FC740, "/Serif/profile/Coated FOGRA39 (ISO 12647-2:2004)", /*c*/0, "usage=iccbased") /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 95)[95] */ /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 65536)[65536] */ /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 65536)[65536] */ /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 65536)[65536] */ /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 65536)[65536] */ /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 65536)[65536] */ /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 65536)[65536] */ /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 65536)[65536] */ [1] PDF_delete_pvf(p_0x000001D08F5FC740, "/Serif/profile/Coated FOGRA39 (ISO 12647-2:2004)", /*c*/0) [1] PDF_load_iccprofile(p_0x000001D08F5FC740, "sRGB", /*c*/0, "usage=iccbased") [2] PDF_begin_page_ext(p_0x000001D08F5FC740, 595.439987, 841.919981, " defaultgray=1 defaultrgb=2") [Last exception 2312 in PDF_begin_page_ext]["Setting DefaultGray requires a 1-component ICC profile"] /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ PDF_delete(p_0x000001D08F5FC740) /* PDF_get_opaque(p_0x000001D08F5FC740) */ /* [0x00000005523BF228] */ /* writeproc(data[0x000001D0A4602040], 28273)[28273] */ [2018-09-02 21:49:03] Seems to be related to colour profiles. One of the TIFF images is a greyscale and the other an RGB (sRGB) file. The intended target profile for the PDF would be sRGB, as is the document's working colour space in Designer. Does that help?