Search the Community

Hello and greetings. I got a strange problem, when I finish editing my pictures in affinity photo and export them, to forward them to friends on my android phone, I can't see them on my phone. (Galaxy A3, Android 8.0) I use the JPG format for exporting, since this seems to be the usual format for this kind of device. I tried different resolutions, DPI settings, changed the pixel format and the ICC profile, but nothing seems to work. The profiles which I used, where Adobe RGB (1998), Pro Photo RGB and srgb iec61966-2.1. The last one is displayed in the info from the pictures of my phone cam, so I hoped it will work, yet it didn't. Final workaround for now was to use a JPG picture from my phone and to copy and paste the desired picture in to that file, just too few and send it with my phone. It worked but this can't be a solution! Another point which may be vital, was the transfer from Adobe Lightroom. I used the “external editing” option in Lightroom to send the RAW files to affinity photo. The settings which I used for the formatting process where: tiff, ProPhoto RGB, 16 bit depth, 300 dpi, no compression. Question is, how do I make these exported JPG pictures visible and usable in my android phone gallery? I hope someone understands my problem and has a better solution.

Hello, I am running Affinity Photo (AfP) 1.7.3 on a MacBook running OSX 10.13.6 I am also printing pictures myself on a Epson SC-P600. A couple of days ago I ran several updates from the Apple store : - AfP from 1.7.2 to 1.7.3 - some minor OSX updates : Safari, security and iTunes From that moment on the print results were no longer good (slight magenta shift and dull colors). The prints are not that bad, but certainly not good enough if you take into account the effort made in AfP to have good results. I then ran the remaining update from the Apple store : Apple printerdrivers https://support.apple.com/nl-nl/HT201465 The print issue was not solved. I also noticed that, after the update(s) AfP (and OSX) has become unstable when another icc-profile than the enclosed is assigned to the document (flickering screen, weird colors, very bright screen). After a while OSX crashes.The document contains a jpg-file with an enclosed sRGB profile The screen/crash problem occurs only if the newly assigned profiles is of version 2.4.0. (as reported by ColorSync.app). There are no problems with profiles of version 2.1.0 and 4.3.0. I can reproduce this and I will submit a crash-report (just cleaned them all). The generic Epson profiles are 2.4.0 So, my questions are : Has anybody else had similar experiences ? Is this a known issue in the AfP community ? Could the print quality be related to the unstability/crash issue ? Thanks jan

Dear Affinity Users and Developers We’re just in the process of evaluating Affinity Publisher (tested with 1.7.0.305 and 1.7.0.312) and we’ve come upon a problem with the PDF/X export: In our workflow our print PDF files are checked in Adobe Acrobat against the preflight profile PDFX-ready Sheetfed Offset Classic HQ V1.5. Among other things this profile checks the MD5 checksums of the used ICC profile against a pre-defined list of profiles known to be appropriate for offset printing. When exporting a PDF as PDF/X-1a with the ICC profile ISO Coated v2 300% (ECI) from Affinity Publisher the preflight returns this error: Looking at the preflight report in the section Output Intents I noticed a difference between a PDF exported from InDesign and Affinity Publisher: The Output Intent is stated as ISO Coated v2 300% (ECI) for the InDesign-PDF and as ISO Coated v2 300% (ECI) (Custom) for Affinity Publisher The Color Management Module had a value of HDM (InDesign) and lcms (Affinity Publisher). Primäre Zielplattform (in English probably: Primary Target Platform): empty (InDesign) and Apple Computer, Inc. (APPL) (Affinity Publisher) Profil erstellt mit (in English probably: Profile created with): Heidelberger Druckmaschinen AG (HDM ) (InDesign) and lcms (Affinity Publisher) The other fields were the same in both files. So I suspected this to be the reason for the different MD5 checksums. But not being an expert on the ins and outs of PDFs and colour management I turned to HilfDirSelbst.ch where we discussed this (in German) in this thread. Olaf Drümmer of callas concluded (my translation): So the question is Is Affinity Publisher correct in changing the meta-data of the profile when writing the PDF file? And if so: Would PDFX-ready need to append their list of MD5 checksums to include those of profiles created with lcms? Any insights and suggestions would be greatly appreciated! Best phph