Jump to content

toyotadesigner

Members
  • Content Count

    284
  • Joined

  • Last visited

About toyotadesigner

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    North Germany

Recent Profile Visitors

1,109 profile views
  1. I know 3 (in words: THREE) other users, one of them owns a print company, who face the same problem. Besides this, you definitely do NOT belong to the developers.
  2. You want me to send sensitive customer data to an unknown person? How absurd is this! I want that the developers code a solution, nothing else. Just to repeat the problem: AFFINITY PUBLISHER DOES NOT EMBED THE COLOR PROFILE IN PDF/X-3 FILES. As long as this problem persists, the software is absolutely unusable. Thank God that I have Scribus to continue my work...
  3. Nobody interested in working on the bug or feeling obliged to deliver a solution and a short term update?
  4. If you don't know where the problem is, how should I know it? They checked the document (exported PDF) with Acrobat Pro, and Acrobat displayed that there is no color profile embedded. Acrobat did not mention anything about a missing output intent. I know that there is a huge difference between a missing output intent and a missing color profile. At least in Scribus I can export a PDF for PDF/X-3 without an output intent or string. Scribus will ask me, but if I don't submit it, the file can be printed anyway. I'm already doing pre-press for 30 years, but never encountered such a weird beh
  5. Affinity Publisher 1.9.1 • macOS Catalina 10.15.7 I've set up a document for print. Exported and transferred it to the print company. They called me and said that there is no color profile embedded. I used the standard settings for »Export for Print«. Then I exported the same document as PDF/X-3, because it does contain RGB images. Again no color profile embedded. What is wrong with this version, is there any workaround? I never had that problem with Scribus, and I don't have the time to re-build the document in Scribus. Any help will be appreciated!
  6. I had the same problem today after I had moved several folders to a new project folder. This method from walt farrel solved the problem: https://forum.affinity.serif.com/index.php?/topic/92418-feature-request-relink-resources/&do=findComment&comment=490577 Thanks a ton Walt!
  7. AP still does not remember the original folder when exporting a file. AP still does not handle the exif data in the resolution field correctly. What a shame...
  8. I wrote: IMPORT the PDF, not open! That is a big difference. Besides this, it didn't even work with an exported EPS or SVG from AD. Starting with Scribus version 1.5.1, you can also import a PDF without placing it into a frame. Never mind, I've rebuilt the logo and the title in Scribus, so I can continue from that point. Thanks anyway.
  9. I've already tried your version of exporting the file. It doesn't work. I guess you don't know anything about Scribus, otherwise you'd know how hilarious your comment is. As I said: PDF files from any other software on my Mac import without any problems into Scribus.
  10. I have a document, size A4, with the word bookbinder in the center. Now I select the word, then export -> PDF -> selection with background -> export. Then I want to import this PDF, which displays ok in Preview, into Scribus Mac. I immediately get an error message: Not a valid PDF file. Same thing happens when I export the word as SVG or EPS. Problem exists only in Affinity Designer. PDF files from all other applications import flawlessly into Scribus. Am I correct if I say the AD PDF file format does have a bug? Does the dev
  11. Because I did not get any feedback from the developers, I've abandoned Affinity Photo and returned to PhotoLine.
  12. Chris, this was a scanned image with an ECI RGB v2 profile assigned. The original image had been scanned @ 4.000 ppi, so modifying the resolution to 300 dpi and then converting the color space to sRGB could be the problem. My guess: same problem as with scaling the document and still having 4.000 dpi in the final image. I did some touch up and then wanted to convert it to sRGB. Yes, I can reproduce the error, as well as with other large format scans. Sorry, but the file size 1.31 GB - too much for an upload. Most of my scanned files are between 650 MB and 1.
  13. I was working on a large image - 602 mm x 1.917 mm or 7.110 x 22.642 pixel @ 300 dpi @ 16/48 bit - and tried to convert it to sRGB for printing. The beach ball appeared an then Affinity Photo just quit. That was it. In addition, the inpainting tool refused to work on this large image.
  14. MEB, looks like the 'bumping up / raise' didn't have any effect, and it appears that none of the developers does have any intention to solve the problem. Or did you get ANY feedback until today? In the meantime I started to look into ExifTool, which is included in the Affinity Photo container (OS X -> show package contents -> Contents -> Resources -> Exiftool). Because I already used Exiftool a while ago, I started digging into this tool a bit further and experimented with it. I found out, that following command in Terminal did exactly what I nee
  15. MEB, once again: No file will leave our office without embedded Metadata (copyright!). Besides that, how will a printer RIP know something about the resolution, if there is no EXIF? It shouldn't be too complex or hard to code, because PhotoLine, Photoshop and even GIMP do handle this feature correctly... Tomorrow will be the release of Pixelmator Pro. If that app will be able to handle this issue as well as remembering the folder of the original file, I'll say good bye to AP very soon, because I need a professional tool for my work. Thank you very much anyw
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.