[C++] Comment lire les données d'une image ?

Comment lire les données d'une image ? [C++] - Programmation

Marsh Posté le 10-07-2001 à 01:10:43    

Salut !
 
Je voudrais lire une image BMP 8 bits en dégradé de gris format Windows, mais je ne sais pas comment faire. Je voudrais juste récupéré les intensités de noir pour les stockées dans une matrice.
 
Si vous avez des idées, des tuts ou encore mieux du code, ca m'intéresse :)
 
@+

 

[edtdd]--Message édité par Arlo13--[/edtdd]


---------------
"Software is like sex it's better when it's free !!!! "
Reply

Marsh Posté le 10-07-2001 à 01:10:43   

Reply

Marsh Posté le 10-07-2001 à 10:24:09    

Tiré de la doc de Win32:

Code :
  1. Bitmaps should be saved in a file that uses the established Windows format and assigned a name with the three-character .BMP extension. The established Windows format consists of a BITMAPFILEHEADER structure followed by a BITMAPINFOHEADER structure. An array of RGBQUAD structures (also called a color table) follows the BITMAPINFOHEADER structure. The color table is followed by a second array of indexes into the color table (the actual bitmap data).
  3. The Windows format is shown in the following illustration.
  5. The members of the BITMAPFILEHEADER structure identify the file; specify the size of the file, in bytes; and specify the offset from the first byte in the header to the first byte of bitmap data. The members of the BITMAPINFOHEADER structure specify the bitmap's width and height, in pixels; the color format (count of color planes and color bits per pixel) of the display device on which the bitmap was created; whether the bitmap data was compressed before storage and the type of compression used; the number of bytes of bitmap data; the resolution of the display device on which the bitmap was created; and the number of colors represented in the data. The RGBQUAD structures specify the RGB intensity values for each of the colors in the device's palette. The color-index array maps indices values from the RGBQUAD array to pixels in a rectangular region on the display.
  7. The following hexadecimal output shows the contents of the file REDBRICK.BMP.
  9. 0000    42 4d 76 02 00 00 00 00  00 00 76 00 00 00 28 00
  10. 0010    00 00 20 00 00 00 20 00  00 00 01 00 04 00 00 00
  11. 0020    00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
  12. 0030    00 00 00 00 00 00 00 00  00 00 00 00 80 00 00 80
  13. 0040    00 00 00 80 80 00 80 00  00 00 80 00 80 00 80 80
  14. 0050    00 00 80 80 80 00 c0 c0  c0 00 00 00 ff 00 00 ff
  15. 0060    00 00 00 ff ff 00 ff 00  00 00 ff 00 ff 00 ff ff
  16. 0070    00 00 ff ff ff 00 00 00  00 00 00 00 00 00 00 00
  17. 0080    00 00 00 00 00 00 00 00  00 00 00 00 00 00 09 00
  19. 0090    00 00 00 00 00 00 11 11  01 19 11 01 10 10 09 09
  20. 00a0    01 09 11 11 01 90 11 01  19 09 09 91 11 10 09 11
  21. 00b0    09 11 19 10 90 11 19 01  19 19 10 10 11 10 09 01
  22. 00c0    91 10 91 09 10 10 90 99  11 11 11 11 19 00 09 01
  23. 00d0    91 01 01 19 00 99 11 10  11 91 99 11 09 90 09 91
  24. 00e0    01 11 11 11 91 10 09 19  01 00 11 90 91 10 09 01
  25. 00f0    11 99 10 01 11 11 91 11  11 19 10 11 99 10 09 10
  26. 0100    01 11 11 11 19 10 11 09  09 10 19 10 10 10 09 01
  27. 0110    11 19 00 01 10 19 10 11  11 01 99 01 11 90 09 19
  29. 0120    11 91 11 91 01 11 19 10  99 00 01 19 09 10 09 19
  30. 0130    10 91 11 01 11 11 91 01  91 19 11 00 99 90 09 01
  31. 0140    01 99 19 01 91 10 19 91  91 09 11 99 11 10 09 91
  32. 0150    11 10 11 91 99 10 90 11  01 11 11 19 11 90 09 11
  33. 0160    00 19 10 11 01 11 99 99  99 99 99 99 99 99 09 99
  34. 0170    99 99 99 99 99 99 00 00  00 00 00 00 00 00 00 00
  35. 0180    00 00 00 00 00 00 90 00  00 00 00 00 00 00 00 00
  36. 0190    00 00 00 00 00 00 99 11  11 11 19 10 19 19 11 09
  37. 01a0    10 90 91 90 91 00 91 19  19 09 01 10 09 01 11 11
  39. 01b0    91 11 11 11 10 00 91 11  01 19 10 11 10 01 01 11
  40. 01c0    90 11 11 11 91 00 99 09  19 10 11 90 09 90 91 01
  41. 01d0    19 09 91 11 01 00 90 10  19 11 00 11 11 00 10 11
  42. 01e0    01 10 11 19 11 00 90 19  10 91 01 90 19 99 00 11
  43. 01f0    91 01 11 01 91 00 99 09  09 01 10 11 91 01 10 91
  44. 0200    99 11 10 90 91 00 91 11  00 10 11 01 10 19 19 09
  45. 0210    10 00 99 01 01 00 91 01  19 91 19 91 11 09 10 11
  46. 0220    00 91 00 10 90 00 99 01  11 10 09 10 10 19 09 01
  47. 0230    91 90 11 09 11 00 90 99  11 11 11 90 19 01 19 01
  49. 0240    91 01 01 19 09 00 91 10  11 91 99 09 09 90 11 91
  50. 0250    01 19 11 11 91 00 91 19  01 00 11 00 91 10 11 01
  51. 0260    11 11 10 01 11 00 99 99  99 99 99 99 99 99 99 99
  52. 0270    99 99 99 99 99 90
  55. The following table shows the data bytes associated with the structures in a bitmap file.
  57. Structure Corresponding bytes
  58. BITMAPFILEHEADER 0x00 - 0x0D
  59. BITMAPINFOHEADER 0x0E - 0x31
  60. RGBQUAD array 0x32 - 0x75
  61. Color-index array 0x76 - 0x275


 

Code :
  1. typedef struct tagBITMAPFILEHEADER { // bmfh  
  3.         WORD    bfType;
  4.         DWORD   bfSize;
  5.         WORD    bfReserved1;
  6.         WORD    bfReserved2;
  7.         DWORD   bfOffBits;
  8. } BITMAPFILEHEADER;
  11. The BITMAPFILEHEADER structure contains information about the type, size, and layout of a file that contains a device-independent bitmap (DIB).
  13. Members
  15. bfType
  17. Specifies the file type. It must be BM.
  19. bfSize
  21. Specifies the size, in bytes, of the bitmap file.
  23. bfReserved1
  25. Reserved; must be zero.
  27. bfReserved2
  29. Reserved; must be zero.
  31. bfOffBits
  33. Specifies the offset, in bytes, from the BITMAPFILEHEADER structure to the bitmap bits.
  35. Remarks
  37. A BITMAPINFO or BITMAPCOREINFO structure immediately follows the BITMAPFILEHEADER structure in the DIB file.


 

Code :
  1. typedef struct tagBITMAPINFOHEADER{ // bmih  
  3.    DWORD  biSize;
  4.    LONG   biWidth;
  5.    LONG   biHeight;
  6.    WORD   biPlanes;
  7.    WORD   biBitCount
  8.    DWORD  biCompression;
  9.    DWORD  biSizeImage;
  10.    LONG   biXPelsPerMeter;
  11.    LONG   biYPelsPerMeter;
  12.    DWORD  biClrUsed;
  13.    DWORD  biClrImportant;
  14. } BITMAPINFOHEADER;
  17. The BITMAPINFOHEADER structure contains information about the dimensions and color format of a device-independent bitmap (DIB).
  19. Members
  21. biSize
  23. Specifies the number of bytes required by the structure.
  25. biWidth
  27. Specifies the width of the bitmap, in pixels.
  29. biHeight
  31. Specifies the height of the bitmap, in pixels. If biHeight is positive, the bitmap is a bottom-up DIB and its origin is the lower left corner. If biHeight is negative, the bitmap is a top-down DIB and its origin is the upper left corner.
  33. biPlanes
  35. Specifies the number of planes for the target device. This value must be set to 1.
  37. biBitCount
  39. Specifies the number of bits per pixel. This value must be 1, 4, 8, 16, 24, or 32.
  41. biCompression
  43. Specifies the type of compression for a compressed bottom-up bitmap (top-down DIBs cannot be compressed). It can be one of the following values:
  45. Value Description
  46. BI_RGB An uncompressed format.
  47. BI_RLE8 A run-length encoded (RLE) format for bitmaps with 8 bits per pixel. The compression format is a two-byte format consisting of a count byte followed by a byte containing a color index. For more information, see the following Remarks section.
  48. BI_RLE4 An RLE format for bitmaps with 4 bits per pixel. The compression format is a two-byte format consisting of a count byte followed by two word-length color indices. For more information, see the following Remarks section.
  49. BI_BITFIELDS Specifies that the bitmap is not compressed and that the color table consists of three doubleword color masks that specify the red, green, and blue components, respectively, of each pixel. This is valid when used with 16- and 32-bits-per-pixel bitmaps.
  50. biSizeImage
  52. Specifies the size, in bytes, of the image. This may be set to 0 for BI_RGB bitmaps.
  54. biXPelsPerMeter
  56. Specifies the horizontal resolution, in pixels per meter, of the target device for the bitmap. An application can use this value to select a bitmap from a resource group that best matches the characteristics of the current device.
  58. biYPelsPerMeter
  60. Specifies the vertical resolution, in pixels per meter, of the target device for the bitmap.
  62. biClrUsed
  64. Specifies the number of color indices in the color table that are actually used by the bitmap. If this value is zero, the bitmap uses the maximum number of colors corresponding to the value of the biBitCount member for the compression mode specified by biCompression.
  65. If biClrUsed is nonzero and the biBitCount member is less than 16, the biClrUsed member specifies the actual number of colors the graphics engine or device driver accesses. If biBitCount is 16 or greater, then biClrUsed member specifies the size of the color table used to optimize performance of Windows color palettes. If biBitCount equals 16 or 32, the optimal color palette starts immediately following the three doubleword masks.
  67. If the bitmap is a packed bitmap (a bitmap in which the bitmap array immediately follows the BITMAPINFO header and which is referenced by a single pointer), the biClrUsed member must be either 0 or the actual size of the color table.
  69. biClrImportant
  71. Specifies the number of color indices that are considered important for displaying the bitmap. If this value is zero, all colors are important.
  73. Remarks
  75. The BITMAPINFO structure combines the BITMAPINFOHEADER structure and a color table to provide a complete definition of the dimensions and colors of a DIB. For more information about DIBs, see the description of the BITMAPINFO data structure.
  76. An application should use the information stored in the biSize member to locate the color table in a BITMAPINFO structure, as follows:
  78. pColor = ((LPSTR)pBitmapInfo +
  79.     (WORD)(pBitmapInfo->bmiHeader.biSize));
  82. Windows supports formats for compressing bitmaps that define their colors with eight or four bits per pixel. Compression reduces the disk and memory storage required for the bitmap. The following paragraphs describe these formats.
  83. When the biCompression member is BI_RLE8, the bitmap is compressed by using a run-length encoding (RLE) format for an 8-bit bitmap. This format can be compressed in encoded or absolute modes. Both modes can occur anywhere in the same bitmap.
  85. · Encoded mode consists of two bytes: the first byte specifies the number of consecutive pixels to be drawn using the color index contained in the second byte. In addition, the first byte of the pair can be set to zero to indicate an escape that denotes an end of line, end of bitmap, or delta. The interpretation of the escape depends on the value of the second byte of the pair, which can be one of the following:
  87. Value Meaning
  88. 0 End of line.
  89. 1 End of bitmap.
  90. 2 Delta. The two bytes following the escape contain unsigned values indicating the horizontal and vertical offsets of the next pixel from the current position.
  91. · In absolute mode, the first byte is zero and the second byte is a value in the range 03H through FFH. The second byte represents the number of bytes that follow, each of which contains the color index of a single pixel. When the second byte is 2 or less, the escape has the same meaning as in encoded mode. In absolute mode, each run must be aligned on a word boundary.
  93. The following example shows the hexadecimal values of an 8-bit compressed bitmap.
  95. 03 04 05 06 00 03 45 56 67 00 02 78 00 02 05 01
  96. 02 78 00 00 09 1E 00 01
  99. This bitmap would expand as follows (two-digit values represent a color index for a single pixel):
  101. 04 04 04
  102. 06 06 06 06 06
  103. 45 56 67
  104. 78 78
  105. move current position 5 right and 1 down
  106. 78 78
  107. end of line
  108. 1E 1E 1E 1E 1E 1E 1E 1E 1E
  109. end of RLE bitmap
  112. When the biCompression member is BI_RLE4, the bitmap is compressed by using a run-length encoding format for a 4-bit bitmap, which also uses encoded and absolute modes:
  114. · In encoded mode, the first byte of the pair contains the number of pixels to be drawn using the color indices in the second byte. The second byte contains two color indices, one in its high-order four bits and one in its low-order four bits. The first of the pixels is drawn using the color specified by the high-order four bits, the second is drawn using the color in the low-order four bits, the third is drawn using the color in the high-order four bits, and so on, until all the pixels specified by the first byte have been drawn.
  116. · In absolute mode, the first byte is zero, the second byte contains the number of color indices that follow, and subsequent bytes contain color indices in their high- and low-order four bits, one color index for each pixel. In absolute mode, each run must be aligned on a word boundary. The end-of-line, end-of-bitmap, and delta escapes described for BI_RLE8 also apply to BI_RLE4 compression.
  118. The following example shows the hexadecimal values of a 4-bit compressed bitmap.
  120. 03 04 05 06 00 06 45 56 67 00 04 78 00 02 05 01
  121. 04 78 00 00 09 1E 00 01
  124. This bitmap would expand as follows (single-digit values represent a color index for a single pixel):
  126. 0 4 0
  127. 0 6 0 6 0
  128. 4 5 5 6 6 7
  129. 7 8 7 8
  130. move current position 5 right and 1 down
  131. 7 8 7 8
  132. end of line
  133. 1 E 1 E 1 E 1 E 1
  134. end of RLE bitmap
  137. If biHeight is negative, indicating a top-down DIB, biCompression must be either BI_RGB or BI_BITFIELDS. Top-down DIBs cannot be compressed.


 

Code :
  1. typedef struct tagRGBQUAD { // rgbq  
  3.     BYTE    rgbBlue;
  4.     BYTE    rgbGreen;
  5.     BYTE    rgbRed;
  6.     BYTE    rgbReserved;
  7. } RGBQUAD;
  10. The RGBQUAD structure describes a color consisting of relative intensities of red, green, and blue.
  12. Members
  14. rgbBlue
  16. Specifies the intensity of blue in the color.
  18. rgbGreen
  20. Specifies the intensity of green in the color.
  22. rgbRed
  24. Specifies the intensity of red in the color.
  26. rgbReserved
  28. Reserved; must be zero.
  30. Remarks
  32. The bmiColors member of the BITMAPINFO structure consists of an array of RGBQUAD structures.


 
Bonne lecture! ;)

Reply

Marsh Posté le 10-07-2001 à 10:48:29    

ce sera peut être plus facile en français...  
http://progzone.free.fr/graphisme/formats/bmp/bmp.html

Reply

Marsh Posté le 10-07-2001 à 10:56:12    

coucou Toucouch et Pitounet ca va ?
Moi ca va. Il me reste plus que 9 jours de stages. Vous aussi je suppose !!!

Reply

Marsh Posté le 10-07-2001 à 12:28:36    

Hé ben, ça glande sec les stagiaires! :D
Pitounet > C'est vrai que c'est mieux en français! :)

Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed