Processing of certain embedded bitmap types has deteriorated in build 386

Forum for the PDF-XChange Editor - Free and Licensed Versions

Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Paul - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange

User avatar
David.P
User
Posts: 1637
Joined: Thu Feb 28, 2008 8:16 pm

Processing of certain embedded bitmap types has deteriorated in build 386

Post by David.P »

Hello Forum and Tracker Support Team,

up to recently, we were always able to edit embedded PDF images, either with the built-in editor or with an external editor, in their original resolution and color depth.

This still works at least up to build 366.

In the current build 386 however, this no longer works as intended, at least for certain types of black and white images, see for example the attached sample PDF.

If one of the black and white bitmaps contained therein is edited in the built-in editor or with an external editor, the image will be converted to full color with 24-bit color depth, as soon as it is passed to the editor. The same happens if the image is simply saved to disk.

This is very inconvenient, as this naturally increases file size massively for exported or edited images. Additionally, image quality and sharpness are reduced when editing or exporting black and white images.

Let us please return to the previous behavior which allowed editing or exporting of whatever images in their respective original color depth and resolution.

Thank you
David.P

DE10202311B4.pdf
You do not have the required permissions to view the files attached to this post.
David.P
PDF-XChange Pro
User avatar
rakunavi
User
Posts: 1671
Joined: Sat Sep 11, 2021 5:04 am

Re: Processing of certain embedded bitmap types has deteriorated in build 386

Post by rakunavi »

Hello David.P,

It might be helpful to be informed in advance of the status of the "Save without Display Transformations" option in the Save File As dialog and the "Ignore Display Transformations" option in the Edit Image menu so that Tracker Support can better assist you. This is because the color depth, etc. will be affected by both options.

  • figure1.png

    figure2.png
For example, the behavior of the "Save without Display Transformations" option was changed in build 370 after the report in this post. The results before build 368 and after build 370 are the exact opposite, so if you want the same output results as before, you need to reverse the check. The issue reported in this topic is still present in build 386, and I too think there is still room for improvement in this area. So I am not saying that changing the option settings will solve everything.

Best regards,
rakunavi
You do not have the required permissions to view the files attached to this post.
TOP desires for PDFXCE
forum.pdf-xchange.com/viewtopic.php?t=39665 LassoTool
forum.pdf-xchange.com/viewtopic.php?t=38554 CmtGarbled
forum.pdf-xchange.com/viewtopic.php?t=37353 FulScrMultiMon
forum.pdf-xchange.com/viewtopic.php?t=41002 DisableTouchSelect
User avatar
David.P
User
Posts: 1637
Joined: Thu Feb 28, 2008 8:16 pm

Re: Processing of certain embedded bitmap types has deteriorated in build 386

Post by David.P »

Thank you rakunavi,

Toggling the "Save without Display Transformations" option sure enough solved the problem.

I agree that it is not entirely self-evident in all cases what exactly this option does, even more so when just saving an embedded image to disk that has not even been edited. So maybe there is some room for improvement, at least regarding clarity of this option.

Perhaps the option could be called "Save original embedded image, ignoring any transformations".

Anyway, for me, the problem is solved for the time being.

Thanks again,
David.
David.P
PDF-XChange Pro
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19856
Joined: Mon Jan 12, 2009 8:07 am

Re: Processing of certain embedded bitmap types has deteriorated in build 386

Post by Stefan - PDF-XChange »

Hello David.P, Rakunavi,

Happy to see you helping each other, and I will pass your suggestion for renaming that option to the people working on the UI command names for consideration!

p.s. It has been discussed and the devs decided that for now they would not be updating the wording and description there.

Kind regards,
Stefan