XChange vs. Adobe Pro: 10x File size when scanning

[belier]

Hello.

I'm using the New Document From Scanner feature and I'm getting extremely big file in comparison with Adobe Pro.
Scanning a single document results in 3Mb file, while the same document, scanned with Adobe Pro, using same scanner settings results in a ~300k file. Has it something to do with OCR?

Thanks in advance.

[Paul - PDF-XChange]

Hi belier,

can you post the files in a zip archive for us?

thanks

[belier]

Hi belier,

can you post the files in a zip archive for us?

thanks

Hi. Thanks for answering.

I pm you the link (MU) of the rar with two files. It's the scan of the same document, using both Adobe Pro, and the other with XChange.

First is 400 kB (410.598 bytes) long.
Second is 2,61 MB (2.739.669 bytes) long.

Both scanned with same scanner and same settings (300 dpi)

Thanks in advance

[Paul - PDF-XChange]

thanks belier,

I have your samples. I see what you mean about the file size. I will need to consult with the development team and get back to you.

regards

[rmcmanamy]

Did this never get fixed? In the latest version I'm seeing the same problem. The file size the PDF-XChange Viewer is making for a color is 12.68 MB. PDFTool4 is 1.28 using the same TWAIN scanner and settings. The problem also exists for the WIA driver for this same scanner.

The PDFTools one for the image has both a FlatDecode and DCTDecode where the Viewer only adds a FlatDecode to it. Both of them the PDF shows the image as 8 bit DeviceRGB.

[Stefan - PDF-XChange]

Hello Rodney,

I've asked our devs for a further comment on this - and will post here as soon as I hear back from them.

Best,
Stefan

[Ivan - Tracker Software]

V2.x of the viewer uses only Flate compression to compress scanned images. V3 can use more types of compressions.

[belier]

V2.x of the viewer uses only Flate compression to compress scanned images. V3 can use more types of compressions.

When will be available v3?

Thanks in advance

[John - Tracker Supp]

Very Soon and more than that we cannot say - its a big job because unlike most of our competitors we will allow complete PDF editing for both end users and Developers using our toolkits - and also 3rd party developers will have the ability to provide 'Plugins' to extend the functionality of the Viewer/Editor for the additonal benefit of all concerned ...

Its a complex task and the error checking and compatibility required between the different modes is crucial - hence the reason it has taken us much longer than anticipated - it is close - but rather than risk dissapointing again and again - we will not say anymore until we have a beta ready to release.

Thanks for your patience and understanding.