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

485 profile views
  1. I'm drawing a image with Affinity Designer and have removed a shadow from a product image from the web. After using the selection brush, I used the refine option. It used all of my CPU cores for several seconds (the image isn't big at all) and presented me with this funny pixel garbage. It's equally broken for all display modes (overlay; black background). If you want to try and reproduce it, open this URL in Firefox: https://www.google.com/search?client=firefox-b-d&biw=1244&bih=949&tbm=isch&sa=1&ei=eFMGXcz8EuGd1fAP0JW18AQ&q=anker+pd+power+10000&oq=anker+pd+power+10000&gs_l=img.3...8433.9291..9485...0.0..0.108.597.3j3......0....1..gws-wiz-img._328jfAGGGo#imgrc=d5tUonyiRSQbvM: Then right-click the large image and "copy image", then paste to AD. Then switch to pixel persona and erase the cables in the corner. Then use the selection brush, which behaves very wildly here. Not used to that. It's almost impossible to select anything reasonable with it. I've given up and kept the shadow for now. It's not important, just a sketch for myself.
  2. Installed the beta 384 on Windows 10.1709 (yes, it's old). Publisher wasn't already installed but I did have it installed earlier on this system. Everything went well. Startup worked, I shortly tested linked text blocks with some decorations and text flow around an image. No problems at all while moving things around on the page. For anything else, I'd probably have to watch tutorials first, or spend more time exploring on my own.
  3. RC means Release Candidate. That means that this is considered the release version unless something unexpected is still discovered. I'm always surprised how people call a version RC and state that new features are added. Microsoft did it a lot in the past with .NET Core versions where RC2 had a lot of breaking changes from RC1.
  4. A "workaround" may be acceptable, but it certainly isn't desirable.
  5. I haven't read all of your post, but it sounded like you believe that arrows on lines are only for technical drawings. Have you never seen any arrows in your environment outside of technical drawings? Or is everything with an arrow a "technical drawing" for you? I see arrows every day, in all kinds of places. They are one of the most basic sign language concepts of mankind. And as with a drawing tool, I want to be able to style my arrows as I like while keeping them accurate (i.e. not MS Paint freehand-mouse style). The old point-outline-shape tools were simply inappropriate for most such cases. I very much welcome the addition of arrows in the beta and now quickly switch from 1.6 to 1.7-beta whenever I find I need arrows in a document.
  6. Where is the thread about the app icons? I can't find it but also noticed that the only way to distinguish the Photo and Designer icons is by their colour. Those funny random lines going in any direction don't tell me anything.
  7. I just can't say the PDF/X export does anything useful. I've had problems with it before (1.6) and version 1.7 seems to be even worse than that. While version 1.6 produced a totally wrong background behind bitmaps with transparency, version rasterises the whole thing from the start. My PDF export doesn't seem to contain a single vector, everything's just in pixels, including text and other graphics. Then I tried to rasterise that problematic gradient rectangle and use that background bitmap in place of the gradient. Since it's a very subtle gradient, raster resolution shouldn't be an issue in print. But that fails, too. Version 1.6 crops that background rectangle at the left, top and right edges to the document sizes. Only the bottom edge sticks out into the bleed area. The rest is gone. That will produce white edges in print after cutting for sure! v1.7 seems to preserve the real size of that rectangle but the resulting PDF doesn't contain any data outside the document size. The bleed area is just white. Not what it's meant to be for. Here's the full image file, you can try it out in 1.6 and 1.7. So I'm still pretty clueless and unhappy with Affinity Designer when it comes to print export with PDF. I'm not sure why print shops want PDF/X from two decades ago when every web browser can render modern PDF just fine. Maybe the print machines are two decades old and there's no software upgrade for them? So I might even be able to run my own code through a security hole on their machine, or whatever. But that's the requirement. I can't go to a print shop with a modern PDF. That means I still can't use Affinity Designer for the job. Since I've already made the whole design in AD, I need to figure out what I did last time to convert a modern PDF to a proper PDF/X with Adobe Illustrator CS6. It would be really helpful if that export would work one day. I don't care about the gradient, I can rasterise it if needed, but even that fails as of now. Also, the bleed area handling is still completely misleading. I never know what it's doing there. Do I have to add it to the document size or not? Will it be added? Should I select the "include bleed" option on export? What if not? What will it do? No idea, really. Again, Adobe Illustrator CS6 does that so much better and I never had to ask any question.
  8. 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!
  9. Looks good. I couldn't find any such errors at numerous zoom levels. Thank you.
  10. 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
  11. 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.
  12. @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.
  13. It looks the same. I can still provide a screenshot this evening if you like.
  14. 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
  15. 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.