tudor

Yes, that seems to be the problem. In the Designer Mac app bundle there is a Info.plist file containing the incomplete version number. After I modified that string from "1769" to "2.1.0.1769", StudioLink started to work again. So we need new macOS builds for the Designer and Photo apps, folks.

I've updated and run all three apps, I restarted the computer and tried again. Same issue.

I've just updated all three beta apps and now I can't send files for editing between Designer and Publisher. On macOS 13.3.1. This popup appears In Publisher when I click on the Designer or the Photo icons on the toolbar.

Still not fixed in beta 1769

Not really. For example, ChatGPT made me an Adobe Illustrator JavaScript that worked from the first try. I am not a programmer, I barely understand some JS code. I just described what I needed in plain English. Any Illustrator user could do that. I can only imagine how much more advanced those chatbots will be in a few months/years. AI chatbots are not just tools. A drilling machine is a tool that helps me drill more holes, faster. An app like Affinity Designer is a tool that lets me create better and faster. AI chatbots will completely replace the need for a human in the creative process. The clients will simply talk directly to a chatbot instead of paying a designer or programmer to do that for them.

There is a workaround for this issue: apply colors using the color wheel in the Context Toolbar, while watching the CMYK values from the Color panel. CleanShot 2023-03-29 at 13.46.53.mp4

I have the same issue. Publisher crashes after placing a Designer file on a master page and then saving the .afpub file. macOS Ventura 13.2.1, latest 1732 betas

@Old Bruce could you open the attached file in the latest beta and try selecting some nodes with the lasso? Please let me know if it works correctly or not. It's weird: on some files it works, on others it doesn't. test.afdesign

Here the preview looks fine.

Now it's doing something weird, it selects some nodes outside the selection area...

Have you actually tried selecting and moving nodes using alt-drag? On my computer it displays the lasso on screen, but it doesn't select anything.

@Walter Nissen In the PDF export window, enable the "Convert image color spaces" option. Here is a PDF sample: 1 Page 02.pdf

Same here.

@keithrt try this tool: https://www.sinwaver.com

Those arrows do not respond to my clicks. It's like they are purely decorative. And it's not only those from my screenshot. Anywhere there is an input field, those buttons are disabled. They do work in Publisher v2.0 and in Designer v2.0 and v2.1 beta. Earlier today MEB acknowledged this issue, but now I see that he deleted the message for some reason.

All these tiny up/down buttons don't work anymore in Publisher 2.1 on macOS 13.2.1.

Are you sure your black color is CMYK 0/0/0/100? Select the text and check the values displayed in the Color panel. Which PDF preset did you use for exporting?

Play with the image compression settings in the Advanced section of the PDF export panel: The image downsampling resolution The JPEG compression For example, if you publish a PDF to be viewed online (not printing it on a commercial press), try lowering the resolution to 150 DPI and the JPEG compression to 80 and see how big the resulting PDF is. You can go lower with those values, and the PDF file will be even smaller, but the images will degrade more.

Bingo! Thank you for checking.

But it means that I can't use the PDF workaround to exchange files with users of other design apps, and eventually that's going to stop me from using Affinity apps altogether. Affinity could investigate and try fixing this or not, it's their choice.

This article seems to explain the space issues in PDFs: https://blog.idrsolutions.com/how-are-text-spaces-created-in-a-pdf-file/

This is how an online PDF analyser sees the content in my Affinity PDF file:

FWIW, I've searched the internet and found similar issues affecting various other applications that generate PDFs (not related to Affinity). In one discussion someone said this: "I had a long chat session with the Adobe help team yesterday. It seems that the problem arises when a document created in some other editor is saved as PDF this problem can arise resulting in spaces not appearing to be standard ones under ISO (or ASCII 32)."

Adding a fifth editing app that I've just tried and was unable to interpret spaces in an Affinity PDF: QuarkXpress.

This happens only with PDFs generated by Affinity apps. It's hard to believe that the four editing apps I tried, made by four different companies (one of them being Adobe) all have the same bug.