See Also

IntroductionImagesInMemoryAndInFiles Members  | Leadtools.Topics Namespace

!MISSING Scrap '_COLLAPSIBLE_HEADER'!

Target Platforms: Microsoft .NET Framework 2.0, Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family

Language

Visual Basic

C#

C++

C++/CLI

Show All

See Also Requirements Languages Leadtools.Topics Send comments on this topic.

Back to Introduction - All Topics

Help Version 15.5.11

IntroductionImagesInMemoryAndInFiles Class

Leadtools.Topics Namespace : IntroductionImagesInMemoryAndInFiles Class

Introduction: Images in Memory and in FilesImaging

For a list of all members of this type, see IntroductionImagesInMemoryAndInFiles members.

Inheritance Hierarchy

System.Object
   Leadtools.Topics.IntroductionImagesInMemoryAndInFiles

Syntax

[Visual Basic]
Public Class IntroductionImagesInMemoryAndInFiles
[C#]
public class IntroductionImagesInMemoryAndInFiles
[C++]
public __gc class IntroductionImagesInMemoryAndInFiles
[C++/CLI]
public ref class IntroductionImagesInMemoryAndInFiles

Remarks

Generally, the size of an image in memory is determined by its dimensions and its color resolution. For example, to calculate the number of bytes for a 500-by-500 pixel, 24-bit image, you multiply 500 * 500 * 3. (Multiply by 3 because there are 3 bytes in 24 bits.) For an 8-bit image, it would be 500 * 500, plus the size of its palette, which is about 1K. There is an exception for 1-bit files, which can be loaded in a compressed format using the LEADTOOLS Document/Medical toolkits.

For any color image, whether the color values are in a palette or in the image data, the color of each pixel in the image consists of red, green, and blue values. They always use the RGB color-space model, which means that red, green, and blue values are combined to represent a color.

The size of the same color image when it is stored in a file is often much smaller, and the color-space model is not always RGB. For example, JPEG and LEAD CMP files both use a YUV color-space model, where Y is a luminance value, and the U and V values are chrominance values. In this color-space model, brightness information is stored in the luminance value, and color information is stored in the chrominance values. JPEG and LEAD CMP achieve data compression through sampling techniques that can affect the accuracy of the YUV values. This kind of compression is sometimes referred to as lossy compression, because you can manipulate the compression parameters to choose between greater compression or greater accuracy. (YCbCr, used in TIFF images, is the same color-space model as YUV.)

Another color-space model used in image files is CMYK (designed for color printing using cyan, magenta, yellow, and blackness). Other compression techniques include RLE (run-length encoding) and LZW (Lempel-Ziv and Welch). Both of these techniques preserve the accuracy of the image data, and they achieve compression solely by identifying repetitions of data. Some grayscale and 1-bit image file formats also use RLE and LZW compression techniques.

There is also a family of Reference Output Medium Metric (ROMM) BGR Color encodings that is a wide-primary output-referred extended color-gamut BGR color encoding. These encodings are used by digital still picture imaging systems to manipulate, store, transmit, display and print digital images. Unlike sRGB color encoding, the range of colors is not limited to those colors that can be displayed on a CRT monitor, and unlike e-sRGB, these encodings do not use negative RGB colorimetry co-ordinates. ROMM color order can be used only with 24 or 48-bit images and is supported by the CMP/JPEG/Exif JPEG/JTIF/TIFF CMP file formats.

The image file formats are not only used for storage in the computer's file system, but are also used for database storage and for transmission of images. Furthermore, some applications keep frequently-used images in memory in a compressed file format. Thus, they can take advantage of memory speed when loading images from these files.

 

!MISSING Scrap '_COLLAPSIBLE_HEADER'!

Target Platforms: Microsoft .NET Framework 2.0, Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family

See Also

IntroductionImagesInMemoryAndInFiles Members  | Leadtools.Topics Namespace

 

 


Products | Support | Contact Us

Copyright © 2006-2007 All Rights Reserved. LEAD Technologies, Inc.