Jump to content

Recommended Posts

I export from InDesign at JPEG 300 dpi CMYK, but when I open the file in Affinity Photo it's 72dpi and a lot bigger size. I can easily go in and change it back to 300 dpi (and smaller size) but it's kind of a bother when I've got dozens of files.

 

Share this post


Link to post
Share on other sites

Hi APEGamer :)

I'm very sorry to hear this! Could you please provide your JPEG image here so I can investigate this for you?

Share this post


Link to post
Share on other sites

Here is a PDF of the card in Acrobat Pro, properly formatted. This is what I sent to my printer.

image.png.421f38da916884d175376edc0272e5ce.png

In the meantime, I want to have another print/play company turn around a quick copy of the game I can use for the summer conventions. They want the cards in JPEG format, so I import the PDF into Affinity (I tried both Publisher and Photo):

image.png.aa1186e286764ce19af02a554c07dd4b.png

 Notice that the title font got messed up (even though it shows as Cambria Bold 14 pt in both programs) as well as the cube font. I build the cubes in InDesign using grep, which isn't yet available in Affinity, so that explains the cubes but I'm not sure about the card title.

This has caused me to export from InDesign to JPEG, to avoid the font problems altogether. But I find that even though I export at 300 dpi:

image.png.f9819a0aca39c316be54a2604d67aad4.png

Affinity Photo loads it as 72 dpi:

image.png.23034ca9a5f0ebfdd16d99323cfc3ac6.png

Since I wrote my original post, I found that if I export to JPEG from Acrobat instead of from InDesign, it loads as a proper 300 dpi image in Affinity, so I'm past this problem.

Any input you have on the font issues would be appreciated. I'd love to simply load the PDF into Affinity Photo, and for some files I can do that, but the fonts for this game seem to cause problems for Affinity. I'm trying to make the switch off Adobe, but things like this require that I maintain the Adobe subscription.

Kevin

 

Share this post


Link to post
Share on other sites
12 minutes ago, APEGamer said:

Oh, and here's 72dpi JPEG image.

For looking at file details, it can be important to zip a .jpg or .png file, as otherwise the forum software may make changes to the image. So, if you could provide a .zip of that rather than just the image, that would be helpful.


-- Walt

Windows 10 Home, version 1903 (18362.239), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.2.471 and 1.7.2.464 Beta   / Affinity Designer 1.7.2.471 and 1.7.2.4464 Beta  / Affinity Publisher 1.7.2.471 and 1.7.2.458 Beta

Share this post


Link to post
Share on other sites

Thanks.

Exiftool says it's a 300dpi image, yet Affinity Photo says it's 72dp. I'm not sure why.


-- Walt

Windows 10 Home, version 1903 (18362.239), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.2.471 and 1.7.2.464 Beta   / Affinity Designer 1.7.2.471 and 1.7.2.4464 Beta  / Affinity Publisher 1.7.2.471 and 1.7.2.458 Beta

Share this post


Link to post
Share on other sites
1 hour ago, walt.farrell said:

Exiftool says it's a 300dpi image

What’s more, the file doesn’t even contain any Exif info as such. The 300dpi info comes from the file header.

I don’t know if it’s relevant that it’s a CMYK JPEG, but what seems more likely to be relevant is the fact that the header identifies the file type as ‘Photoshop 3.0’ rather than ‘JFIF’.


Alfred online2long.gif
Affinity Designer/Photo/Publisher 1.7.1.404 • Windows 10 Home (4th gen Core i3 CPU)
Affinity Photo for iPad 1.7.1.143 • Designer for iPad 1.7.1.1 • iOS 12.4 (iPad Air 2)

Share this post


Link to post
Share on other sites

Apple's Preview tells ...

file_preview.jpg.82ef9c4ac5fd711a75e170078e6b37a6.jpg

Graphics Converter and PSE tell ...

file_gc.jpg.615d0e402c993cba439397f325451eb0.jpg

ImageMagick tells ...

Quote

$ identify -verbose MonsterCards_final.jpg
Image: MonsterCards_final.jpg
  Format: JPEG (Joint Photographic Experts Group JFIF format)
  Mime type: image/jpeg
  Class: DirectClass
  Geometry: 815x1110+0+0
  Resolution: 300x300
  Print size: 2.71667x3.7
  Units: PixelsPerInch
  Colorspace: CMYK
  Type: ColorSeparation
  Base type: Undefined
  Endianess: Undefined
  Depth: 8-bit
  Channel depth:
    Cyan: 8-bit
    Magenta: 8-bit
    Yellow: 8-bit
    Black: 8-bit
  Channel statistics:
    Pixels: 904650
    Cyan:
      min: 0  (0)
      max: 203 (0.796078)
      mean: 83.2631 (0.326522)
      standard deviation: 55.1423 (0.216245)
      kurtosis: -1.58813
      skewness: -0.185879
      entropy: 0.905169
    Magenta:
      min: 0  (0)
      max: 203 (0.796078)
      mean: 95.0809 (0.372866)
      standard deviation: 43.065 (0.168882)
      kurtosis: -1.31466
      skewness: -0.273257
      entropy: 0.891817
    Yellow:
      min: 0  (0)
      max: 241 (0.945098)
      mean: 115.985 (0.454841)
      standard deviation: 43.1452 (0.169197)
      kurtosis: -0.338882
      skewness: -0.517781
      entropy: 0.905884
    Black:
      min: 0  (0)
      max: 255 (1)
      mean: 53.956 (0.211592)
      standard deviation: 60.604 (0.237663)
      kurtosis: -0.320517
      skewness: 0.718099
      entropy: 0.549556
  Image statistics:
    Overall:
      min: 0  (0)
      max: 255 (1)
      mean: 87.0711 (0.341455)
      standard deviation: 50.4891 (0.197997)
      kurtosis: -1.07726
      skewness: -0.201789
      entropy: 0.813106
  Total ink density: 285.49%
  Rendering intent: Perceptual
  Gamma: 0.454545
  Chromaticity:
    red primary: (0.64,0.33)
    green primary: (0.3,0.6)
    blue primary: (0.15,0.06)
    white point: (0.3127,0.329)
  Matte color: grey74
  Background color: white
  Border color: srgb(223,223,223)
  Transparent color: none
  Interlace: None
  Intensity: Undefined
  Compose: Over
  Page geometry: 815x1110+0+0
  Dispose: Undefined
  Iterations: 0
  Compression: JPEG
  Quality: 93
  Orientation: Undefined
  Properties:
    date:create: 2019-07-21T03:13:05+02:00
    date:modify: 2019-07-20T11:02:16+02:00
    icc:copyright: Copyright 2000 Adobe Systems, Inc.
    icc:description: U.S. Web Coated (SWOP) v2
    jpeg:colorspace: 4
    jpeg:sampling-factor: 1x1,1x1,1x1,1x1
    signature: b8b55f6418b36d3a06c4a0348718104a4542f8abb6982fff4e3780e28d51a1d4
  Profiles:
    Profile-8bim: 28 bytes
    Profile-icc: 557168 bytes
  Artifacts:
    verbose: true
  Tainted: False
  Filesize: 917462B
  Number pixels: 904650
  Pixels per second: 15.0775MP
  User time: 0.060u
  Elapsed time: 0:01.060
  Version: ImageMagick 7.0.8-40 Q16 x86_64 2019-04-16 https://imagemagick.org

 


☛ Affinity Designer 1.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
Share on other sites

Thanks for your image APEGamer, I'm not currently certain why this is importing into Affinity at 72dpi. I've just tried exporting an image as a 300 DPI CMYK JPEG (all the acronyms ;)) then reopened this is Affinity and the correct DPI is read. I'll log this JPEG with our developers to be investigated further, but as it's reporting a different DPI through various methods (see v_ykr's post above) it may be an issue with InDesigns exporter, especially considering -

On 7/20/2019 at 4:19 PM, APEGamer said:

I found that if I export to JPEG from Acrobat instead of from InDesign, it loads as a proper 300 dpi image in Affinity

I'll update this thread with any information regarding this file provided by the developers :)

Could you provide a copy of your PDF file so I can look into the font issue for you? I've not previously seen the correct font be detected, but not applied on PDF import!

Share this post


Link to post
Share on other sites

Excellent, thanks!

Per the @Dan C request, here is a PDF that shows the font issue. Photo finds and loads Cambria Bold in the title, but it got the case and spacing wrong. The cube font in the card's body isn't right, but that's to be expected - I used Adobe's grep to color it.

Kevin

MonsterCards_final.pdf

Share this post


Link to post
Share on other sites

Thanks for that Kevin, I can see the the 'small caps' isn't being correctly read on import, which in turn is messing up the spacing.

I'll get this logged with our developers for investigation, many thanks! :) 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×