Jump to content


  • Content Count

  • Joined

  • Last visited

About toyotadesigner

  • Rank
    Advanced Member

Profile Information

  • Gender

Recent Profile Visitors

1,000 profile views
  1. 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...
  2. 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.
  3. 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.
  4. 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 developer team plan to fix this bug?
  5. Because I did not get any feedback from the developers, I've abandoned Affinity Photo and returned to PhotoLine.
  6. 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.7 GB in size.
  7. 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.
  8. 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 needed to correct the exported image dpi EXIF setting in the X Resolution and Y Resolution TAGs: exiftool -XResolution=300 -YResolution=300 --Orientation --FileModifyDate -overwrite_original_in_place [FileName or Directory] The command inside Affinity Photo only needs the first two options to generate a correct EXIF on export. In short words: If **I** can figure it out (as a non-coder!), it should be a very simple task for your magic coders to solve this bug in an instant. I even wrote an app in Automator, so that I can drag and drop any file onto the Automator app icon I called 'print300' to correct the file to print resolution without altering any of the other EXIF TAGs of the file. ANY feedback from the development team will be highly welcomed, as well as an implementation in the next release!
  9. 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 anyway.
  10. I have a scanned TIFF with these data: Now I resize and resample the image with these settings: What I get is this - AP completely ignored the 300 dpi setting! So please do NOT tell me that this bug has been solved...
  11. Someone has moved the bug to the 'resolved' list, but it has not been resolved at all.



  12. When will you work on the EXIF data problem, that means that the wrong resolution is stored in the EXIF after I have resampled from 4.000 ppi to 300 dpi? This is very important because many printing companies don't open the final TIFF and just send it to the RIP. This is how it should look in the EXIF:
  13. When will you fix the bug that Affinity Photo (and Designer as well) do NOT remember the path or location of the original file when trying to SAVE or EXPORT ? Any plans at all to fix these bugs?
  14. Thanks for the info, I'm having the same problem and thought it could be related to some weird setting in the Wacom panel.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.