Search the Community

It would be great if Serif could add some transparency of the encoders used, versions and the equivalent parameters for the encoder libraries. Give us a scale in the documentation or similar, so we could check with the encoder library to more precisely tune our final output quality. Currently the quality slider exposed in the export interface isn't directly comparable to anything from the encoders used, this makes it difficult to ensure similar quality when exporting across multiple applications. Some background for the request. JPEG XL is supported in Affinity 2, but nowhere is it documented what library, which version, what effort settings or what quality/distance equivalent the quality slider in AFP corresponds to. This information could be hugely useful when more precise control of final output quality is desired, and not only for JPEG XL but all export formats supported. *There's no third-party notice for anything to do with JPEG XL.

I just bought Affinity Publisher V2. And I see that the installation was not made over the previous version. Now I have both versions! This is nice! If, for some reason I want to use V1, it's there. If I want use V2, it's also there! This is what I call freedom to choose.

Apologize for the confusing post below, but this has been a confusing introduction to Publisher. Soooo happy to be using Publisher and not having to boot to an external drive running Mavericks just to get to Adobe InDesign 5.5. However, for reasons still not uncovered, Publisher has had serious and consistent crash problems since the beginning. I now see that Affinity Publisher is available on the App Store. When I purchased Publisher on original release day, it was only available through the Affinity website as a download. Going through other areas of this support forum (beta, bugs, etc.), one can find my numerous posts regarding consistent crashes. Currently, I have achieved a workaround to the crashes (generally regarded as a unique, user-oriented issue rather than the software itself). This workaround has me setting up a separate user account and using a beta build (1.7.3.475). The beta builds were suggested prior to the suggestion of setting up a separate user account. If you are confused reading this, believe me, I have been confused on my end ten-fold. No matter, at this point I am working towards updating my OS to Catalina and considering what to do about the user accounts, beta builds and basically consolidating everything back to a normal setup. In this regard, I am also wondering if I should (or could) be using the App Store version, although since I originally downloaded from the Affinity website, the App Store is listing Publisher as a purchase. How would it work to download from the App Store? I do have my Product Key and all the particulars, but don't want to be charged additional money. Just want to set Publisher up normally as I have with Affinity Photo (downloaded from the App Store) and hopefully delete this separate user account that has been preventing the crashes from happening.

Hello, Just a quick question..I purchased my copy of Affinity Designer for Windows from Affinity store in February of 2018. I'm curious how long we receive updates. Do we receive lifetime updates, specific time-frame or version? Thanks.

Something strange I noticed when I exported a simple two page layout recently. Publisher didn't export the file as it looks in the program currently but rather as an old version from several days ago. I have never seen anything like this as I exported files in the past. Has that happened to anyone else? I don't use Publisher a lot but I thought I would try it out with a simple layout.

According to the Affinity Store, "when you launch your product, you’ll be prompted to download the latest update if available. On clicking Download you will be directed to a web page that will offer you the latest Windows release for your Affinity product." I've had Affinity Designer since December 2017 and have not been prompted to download any updates. The version I currently have is 1.65.123. Can somebody tell me is there been updates since then? (I'm getting numerous crashes so I'm thinking that it has to do with not having the latest version.) If so, is there a link to get the updates? TIA

I have a large menu document that needs to have a pdf version that is full res and I also need a low res version needed for documentation, spec sheets, email, etc. How can I save out from my live version in AD and create these? Maybe in one operation.

One of the things that really bugged me about my PS / LR workflow is the way that Photos would get passed back and forth between the two apps. With a typical workflow you start with a Photo in LR and then need to send it to PS to do something that LR can't do. LR makes a copy of the photo so when you are done editing it you now have two similar photos in your library. If you decide you want to edit the photo again you now have three copies and then four etc. The way this operation should really work is you make an adjustment in Apple's upcoming Photos app, say move the brightness to 27, and then when you export the file to Affinity Photo it uses the same photo instead of a copy of the photo. You should then see your brightness adjustment of 27 in Affinity Photo and then be able to make an adjustment to the brightness again to 15 which should then show up in the settings to Apple's app as you return back to it. I can understand some of the reasons why Adobe's workflow was clumsy, they were trying to get a 17 year old app to work with a brand new app after all. But now that both Apple and Affinity are both starting out at version 1 and at essentially the exact same time let's try and get the way this works under control. I disagree with many people on this forum that Adobe's photo solution works pretty well I think there is a huge opportunity for taking on Adobe in this area.