PDF-export: Small images (icons) seem corrupt on right side when compression is on
Indesign: 14.0.2. x64
Win 10 pro x64, 1809 up to date
So small images look strange and you can see they appear corrupt on the right side. In the last 15 years I have never experienced an issue like this so I would like to know if this is an ordinary behaviour which I ran into by chance or bad luck.
The used image is a scaled down image of a rather small photoshop-file.
At first I thought my guides might cut the images, but they don´t. I worked on the .PSD file, I increased the size of the image containers/frames, which took me over an hour of wasted time and thus: money - before I realized the PDF-export might be the problem.
A regular day of work with Adobe apps I guess. grml.
But: it might be a regular behaviour caused by the combination of file and the way the recompression works.
Image bug1 shows what it looks like in the indesign doc, as u can see with enlarged outer frame box.
Image bug2 shows what it looks like after PDF export. You can see it is not right when printed too, so it is not a bug of representation.
Image bug3 shows the PDF settings I use since I can think of for print files.
Sorry I can´t show larger images as I am not allowed to show content by contract.
Unfortunately I have no time to try multiple scenarios or (compression) settings so in this case we just deal with a bigger file size.
Thanks for your time and maybe feedback!
I am sorry, I was talking about the "bicubic recalculation" on export, where on my bug3 image it says "Bikubische Neuberechnung" I have to select "No recalculation" for those cut edges not to appear in the PDF.
JPEG compression is fine and can be activated and still decreases the file size a lot
Maybe if I had increased the white space in the photoshop file on the right side the recompression would have allowed the painted pixels to spread correctly.
That would seem possible to me, still would be pretty annoying as I use the photoshop automatic crop function all the time and never had an issue with it. So maybe, just maybe it is a bug in the current versions. dunno.