Category: PaperScan

Hi folks,

As promised in the previous article, today we will try to untangle the frequent confusions generated among many computer users by this simple word : “resolution”.
To do that, we are going to explain screen resolution, printing resolution, pixel dimensions, physical dimensions and how everything relates with regard to bitmaps.

Bitmaps dimensions are expressed in pixels (image width x height) either separated (usually for image files) or as the effective result of the multiplication (usually to express digital cameras sensitivity).
For example, an “8 Megapixels digital camera” means the photos it produces (actually bitmaps) are made up of cca. 8 million pixels, a photo being, for example, 3456 pixels wide by 2304 pixels high, which gives 7,962,624 pixels (cca. 8MP).
Funny thing is that the pixel dimension of the image has little to do with how the bitmap image appears on screen but is has lots to do with how the image will print!
How comes?

Well, to begin with, a pixel is a logical unit, not a physical one.
In other words, a pixel doesn’t have a fixed measured size, its size depends on the screen it is displayed on.
For example, imagine an LCD monitor having a screen resolution of 1000×1000 pixels, the screen’s physical dimensions being 1000×1000 mm.
In such case, the dimension of a pixel will be 1 square milimeter (1×1 mm).
Now imagine that you change the output resolution setting of the same monitor to 500×500 pixels: as monitor’s physical dimensions don’t change, a pixel will now be 2×2 mm, meaning 4 square milimeters.
To continue this exercise of imagination, think about a bitmap image having pixel-dimensions of 1000×1000 pixels: in the first case (screen resolution of 1000×1000) the image will be rendered full screen.
And for the second, case (chaging the screen-resolution of the same monitor to 500×500 pixels), the image will appear bigger (because each pixel is bigger than before) and will be displayed only partially on screen.
Of course, there are no such monitors/resolutions standards in real life, we only gave these examples to show that image size in pixels is relative, not “absolute”.
So perhaps at this point it will be easier to understand what pixels-per-inch (PPI) is : it is a value expressing how many pixels “fit” inside an inch but its significance depends on the context.
-when used with regard to an image resolution, PPI (often reffered to as DPI in this context) is the number of pixels per inch in the bitmap grid and is meant for printers (to determine how the image is to be printed within a specified size);
-when used with regard to a screen resolution’s appearance, PPI is the number of pixels per inch (or pixels-per-centimeter (PPCM) when metric system is used) depending on screen’s physical size and screen’s resolution as set by user;
Here are a few real life facts to help understanding:

-a monitor in 800×600 mode has a lower PPI than the same monitor has in a 1024×768 or 1280×1024 mode;
-a monitor of 12 inches wide (horizontal) by 9 inches height (vertical) at a resolution of 1024×768 pixels has a PPI value of cca. 85 (1024 pixels / 12 inches = 768 pixels / 9 inches = 85.3);
-a monitor on a Windows Operating System typically displays at 96 PPI;
-a bitmap image of 1,000 × 1,000 pixels, if labeled as 250 PPI (DPI is frequently misused to replace PPI in such context), will instruct the printer to print it at a size of 4 × 4 inches.

With printers there’s a different story.
First of all, there is an important difference between how an image appears to the human eye on screen and how it appears when printed.
Due to visual perception physiology, an image don’t need to have a very high resolution in order to appear at a decent size and with good quality on a computer screen.
Unfortunately, this is not the case when it comes to printing it : what is seen on print simply doesn’t match the quality of what is seen on screen.
Screens displays colors out of red, green and blue (RGB color model), by mixing them together into a vast color palette and light is emitted directly to the eyes.
White is obtained when all 3 colors are displayed at full intensity, black is obtained by their absence (zero intensity), hence the name “additive color model” for RGB.
Printers work differently : they create colors by mixing cyan, magenta, yellow and black inks (CMYK color model but there’s also a CMY model), inks absorbe light and human eyes see light reflected from paper.
White is obtained by using none of the 4 colors (as it’s the paper’s color) while black is obtained by full combination of all 4 (or 3, for CMY) colors inks, hence the name “substractive color model” for CMYK.

Similar to how pixel is the picture element of an image on screen, a dot is the picture element of a printed image.
And similar to how PPI value describes the density of pixels on screen, the DPI (“dots-per-inch”) value expresses how many individually printed dots “acomodate” within an inch.
Of course, the higher the DPI value, the better quality of the printed image will be.
But printers have a limited range of colors for each dot and their color pallette is lesser than in the case of screens.
So in order to obtain similar output quality, a bitmap image has to be printed in much higher DPI value than the PPI value needed for good screen viewing.
It is said that the printing process “could require a region of four to six dots (measured across each side) in order to faithfully reproduce the colour contained in a single pixel” so if a 100×100-pixel image is to be printed inside a one inch square, the printer must be capable of 400 to 600 dots per inch in order to accurately reproduce the image.

Finally, as if the already described confusions wouldn’t be enough, DPI is used to also express the resolutions in scanning processes, whereas the correct term to use appears to be “samples-per-inch” (SPI).

Hope that from now on, when using PaperScan it will be easier for you to deal with resolution-related terminology in bitmaps!

See you next week !

Bogdan

Big Browser on May 10

Why your password can’t have symbols—or be longer than 16 characters Read article Apache Web Server Attacks Continue to Evolve Read article Announcing the release of Windows Azure SDK 2.0 for .NET Read article Spyware used by governments poses as Firefox, and Mozilla is angry Read article "Nothing is safe once your Glass has been hacked," hacker warns. Read article

What’s WIA

Hi folks,

After having presented previously the basic idea about scanner drivers as well as the bottom line on TWAIN, today we will try to shed some light on WIA.

Wikipedia definition reads: “Windows Image Acquisition (WIA; sometimes also called Windows Imaging Architecture) is a Microsoft driver model and application programming interface (API) for Microsoft Windows ME and later Windows operating systems that enables graphics software to communicate with imaging hardware such as scanners, digital cameras and digital video-equipment.”

So what does it mean from a user’s point of view ? And how is WIA different from TWAIN?

Well, to begin with, both TWAIN and WIA goal is to connect various imaging devices to various imaging softwares.

But…

-TWAIN is meant to be an industry standard (covering all image acquisition devices, for all Operating Systems) while WIA is a vendor (Microsoft) API provided to image acquisition device manufacturers for Windows Operating Systems only.

-WIA is said to offer better support when it comes to digital cameras while TWAIN has a strong orientation towards scaners.

-both TWAIN and WIA allow scanning operation control via dialog or programatically (with no dialog showed).
WIA uses a common dialog for all devices while TWAIN uses the dialog created by the device manufacturer.

-when scanning in duplex mode, TWAIN supports options for each side of the page while WIA uses the same settings for both sides.

-if the device manufacturer has created custom capabilities, TWAIN allows you to use them even though they don’t exist in the TWAIN specifications.

-WIA provides a transparent compatibility layer which allows TWAIN compatible applications to employ and use WIA-driver-based devices.

Remember that PaperScan supports both TWAIN and WIA so it provides users with universal image acquiring feature and full image and document processing power!

See you next week!

Bogdan

Big Browser on April 12

Blink. Chrome’s new rendering engine Read article WebKit Group Strikes Back: Let's Remove Chrome Read article PC Sales Decline In Q1 2013: The Worse in Last 20 Years, sais IDC Read article From touch displays to the Surface: a brief history of touchscreen technology Read article Apple New Campus Cost Seen Jumping to $5 Billion Read article

Casual Friday on April 12

You can't have them both

Hi folks,

In this article we are going to explain to our general public what color detection is all about and how can it be used to dramatically reduce the size of your electronically stored documents.

In a previous article, we were showing that bitmaps (or raster images) are made of pixels (ordered in arrays or matrices, each pixel having its own coordinates and color) in a way similar to how mosaics are made out of pieces of coloured glass.
Since bits (“0″ and “1″) are used to store information about color, it is quite logical that, the more colours need to be encoded in an image, the more bits per pixel (or “bpp”) are necessary to store that information and therefore, the larger the size of the bitmap image file will be.

From a color point of view, bitmaps can be:

– Black and white
Being only 2 colors, they are encoded in 1 bpp (either “0″ or “1″ for either black or white) so these bitmaps consumes less size the lesser possible size for color information.

– Grayscale

Such images are in black, white and various sets of intermediary grey shades.
Generally, a 8 bpp color encoding is considered acceptable, but you will note that each pixel color requires already 8 times more data than for the B/W images.

– Color

Images are colored in nuance (color gradation) palettes of various sizes but 24 bpp color encoding is considered to be satisfactory as it can store over 16,7 million colours while the human eye can discern only about 10 million.
Of course, each pixel color for such images takes 3 times more data than the 8 bpp and 24 times more data than the 1 bpp.

Now, why is all this so important?

In real life, not only the professionals in document storage but also most of us are forced to compromise between the needs of storing documents at as high quality as possible but at smallest possible size (mainly for sharing purposes).
To achieve that, scanning operators have to separate B/W pages from grayscale and from colored ones and scan each of those sets at 1 bpp, 8 bpp and 24 bpp, respectively.
This is a terribly slow, painful and subject to human error task.

What if everything could be done instantly, automatically and with no scanning constraints?

Well, we at ORPALIS have developed a patent pending, proprietary technology of automatic color detection.
All you have to do is put all your documents in one batch, no matter their color type, scan them all in color mode and our software will automatically determine the color type of each page.
Then, depending on the detected color-type, the filter will automatically encode the image in its best suited / optimized bits-per-pixel encoding.
In other words, providing best quality for smallest possible size.

This feature is already implemented in PaperScan Pro starting with version 1.6 and will be fully programmatically available in next GdPicture.NET major release.

Care for a practical testing?

Make sure you have latest PaperScan Pro (even a trial version) installed.
For your convenience, we provide a 3 TIFF test files in a zipped folder to use for batch import, but you can test using your own images, either acquired from scanner or importing existing images files.
Each TIFF file is bigger than 1 MB so the 3 will total more than 3 MB in size.
Now save them in PDF multipage format.
The resulting PDF file (PaperScan creates it using JPEG optimization and PDF pack technology) will be about 800 kb in size.
Not bad, but if you think we can’t do even better, you’ll have to think again!

From the main menu, go to “Options / Batch Acquisition/Import Filters…“.

PaperScan Pro Batch Acquisition/Import Filters...

PaperScan Pro Batch Acquisition/Import Filters…

Select “Automatic Color Detection” option and click “Save

PaperScan Pro Automatic Color Detection

PaperScan Pro Automatic Color Detection

Now import the TIFF files again and save as multipage PDF : the resulting file is 65 kb in size !
Ta-daaam!

Our next step is to provide automatic color detection for regions of same single document.
This will be available for end-users since one of the upcoming PaperScan versions and, of course, programmatically for developers using our next GdPicture.NET toolkit!

Cheers!

Bogdan

10licenses

Hello!

 

February is now over and so is our Birthday Give-Away.

Thank you so much everyone for participating and giving your thoughts on PaperScan!

Yesterday we decided to change the rules a little bit… We’re not going to give the 10 licenses randomly.

Instead everyone who posted a comment will get one!

Learn more ...

1st-birthday

 PaperScan is one year old!

To celebrate the first birthday of the release, I wanted to share its story with you. Because PaperScan has gone a long way!

It started as a small demo app for scanners to show what could be done with the GdPicture SDKs. The application was so convenient and we were a few people to use it on a regular basis to scan, organize and save our documents. Then we thought: since it’s useful for us, maybe other people would like it too! So we decided to sell it as an end-user software. Why not giving it a try? As a student myself (still…) I use PaperScan for my PhD thesis all the time and now I can finally say goodbye to the thousands of photocopies which were lying around everywhere in my apartment.

Learn more ...