0 Replies Latest reply on Jul 17, 2017 8:23 AM by maxim.maximov

    There are couple bug in photoshop pdf parser


      1. Case 0187645151. “After doing more research on this issue, we are able to reproduce it on out end , we will be logging a bug for this and hopefully this will be fixed in the next update of PS. Will be forwarding this to the engineering so that it is taken care of in the future updates. “ - it was above year ago, and issue still exist in current Photoshop version.



      What is this case about.


      Create a frame in an illustrator or Indesign (or Corel for example), fill it with any color and put any object (picture or vector) inside the frame and output it in pdf, then open this pdf in Photoshop. When rasterizing, a thin stroke of the frame color over the object appears.@


      Example - https://yadi.sk/i/RjHKli3H3L8hhR


      In placed pdf or rasterized pdf (cc2015) stroke are 1 px (antialiasing)

      1 layer - pdf rasterized in cc2015

      2 layer - pdf rasterized in cs5

      3 group - pdf placed as smart object in cc2015



      2. Case 0222342754 Issue is about image quality in Photoshop pdf parser from CS6 or above (include latest version). examples - https://yadi.sk/d/QIgeY7VV3KHtBY


      Helix-Long-Red-mega-hair.indd - layout


      Helix-Long-Red-mega-hair.pdf - pdf from layout


      Helix-Long-Red-mega-hair.psd - 300dpi rasterized pdf and addition layers with same % scaled original image via Photoshop automatic resize)


      Helix-Long-Red-mega-hair.tif - original image




      - shift of the rectangular areas of the result image ( marked by cyan zones in psd)

      - blurred downscaled images

      - pixelized upscale images


      Both to increase and to reduce the image, the Nearest Neighbor method is used. The Worst Available image resize method in Photoshop. This is a bug.


      As Result - is there any posibilites to use old CS5 pdf parser in CC? Or the chances that the interpolation method in the next versions will be returned to the adequate one?