| MIL 10 Reference
| Customize Help
| Save Settings

MbufCreate2d


See also
Availability
Available in MIL-Lite with restrictions (see remarks)
Available in MIL

Available on Windows with restrictions
Available on Linux with restrictions

Partially supported on:
Partially supported on Host system
Partially supported on Matrox CronosPlus
Partially supported on Matrox GPU processing driver
Partially supported on Matrox GigE Vision driver
Partially supported on Matrox IEEE 1394 IIDC driver
Partially supported on Matrox Iris GT
Partially supported on Matrox Morphis
Partially supported on Matrox Morphis QxT
Partially supported on Matrox Orion HD
Partially supported on Matrox Radient eCL
Partially supported on Matrox Radient eV-CXP
Partially supported on Matrox Solios eA/XA
Partially supported on Matrox Solios ecl/xcl/ev-cl
Partially supported on Matrox USB3 Vision driver (requires Update 19)
Partially supported on Matrox Vio

For any information regarding a MIL system added during a MIL Update, see the MIL system’s release note

Available on Non-Matrox computer
Available on Matrox 4Sight-X
Available on Matrox 4Sight GP
Available on Matrox Supersight
function map Function map
Examples
MbufCopyMask
MbufCreateColor
Synopsis
Create a two-dimensional data buffer.
Syntax
MIL_ID MbufCreate2d(
MIL_ID SystemId, //in
MIL_INT SizeX, //in
MIL_INT SizeY, //in
MIL_INT Type, //in
MIL_INT64 Attribute, //in
MIL_INT64 ControlFlag, //in
MIL_INT Pitch, //in
const void *DataPtr, //in
MIL_ID *BufIdPtr //out
)
Description

This function creates a two-dimensional data buffer that maps to a user-specified data array, or another existing buffer, and associates it with a specific MIL system.

This function should be used with caution because, when using physical addresses, it provides direct access to any of your computer's memory mapped devices; when using logical addresses, memory protection errors could result.

It is generally better to leave buffer allocation, data loading, and memory control to MIL (MbufAlloc2d(), MbufGet2d(), MbufPut2d()), since MIL might require special memory attributes (such as non-paged memory) or alignment to associate the buffer with a particular target system.

You must allocate the appropriate memory before calling MbufCreate2d() and you must free the created buffer when no longer required, using MbufFree() before freeing the memory. Using MbufFree() on a buffer created with MbufCreate2d() will free the internal structure required for a mapped buffer, but it will not free the memory used. MbufInquire() can be used to get the pointer to the data of a MIL allocated buffer.

[Matrox Solios eA/XA; Matrox Solios ecl/xcl/ev-cl]

Note that to map a buffer to on-board memory with a different system, the on-board memory must be in shared memory, unless the created buffer is created on the same system. See your MIL Hardware-specific Notes for more information regarding shared memory.

Note that this function reference has not been updated for a MIL system added during a MIL update. Refer to the MIL system's release note to see which MIL system’s documentation you should use in its place and any possible differences.
Parameters
This function is not supported on the selected boards.
This function reference has not been updated for the selected MIL system. To show the content of this page, choose a second MIL system; refer to the MIL system's release note to see which MIL system’s documentation to choose and any possible differences.
Parameters
SystemId INQ

Specifies the MIL system on which to create the buffer.

This parameter should be set to one of the following values:

function map For specifying the MIL system
CollapseValue Description
Collapse M_DEFAULT_HOST

Specifies the default Host system of the current MIL application.
Collapse MIL system identifier

Specifies a valid system identifier, previously allocated using MsysAlloc().
SizeX INQ

Specifies the buffer width.

[Matrox GPU processing driver]

When dealing with monochrome (1-band) buffers, the buffer width must be a multiple of 4.

function map For specifying the buffer width
CollapseValue Description
Collapse M_DEFAULT

Specifies that the buffer width is identical to that of the source buffer when the ControlFlag parameter is set to M_MIL_ID.
Collapse Value

Specifies buffer width. The units are determined by the selected buffer attribute. For example, if the buffer has an image buffer attribute, width is specified in pixels.

(summarize)
SizeY INQ

Specifies the buffer height.

function map For specifying the buffer height
CollapseValue Description
Collapse M_DEFAULT

Specifies that the buffer height is identical to that of the source buffer when the ControlFlag parameter is set to M_MIL_ID.
Collapse Value

Specifies the buffer height. The units are determined by the selected buffer attribute. For example, if the buffer has an image buffer attribute, height is specified in pixels.

(summarize)
Type INQ

Specifies a combination of two values: data type and data depth per band. Specify the depth of the buffer per band as one of the following:

function map For specifying the data depth of the buffer
CollapseValue Description
Collapse M_DEFAULT

Specifies that the buffer data depth and type are identical to that of the source buffer when the ControlFlag parameter is set to M_MIL_ID.
Collapse 1 +

Specifies a 1-bit (packed binary) buffer. Note that you cannot allocate a 1-bit LUT, kernel, or structuring element buffer.

(summarize)
Collapse 8 +

Specifies an 8-bit buffer.
Collapse 16 +

Specifies a 16-bit buffer.
Collapse 32 +

Specifies a 32-bit buffer.
Combination constants for the values listed in For specifying the data depth of the buffer.

You can add one of the following values to the above-mentioned values to set the data type.

Supported data types depend on the specified depth.

function map For specifying the data type of the buffer
CollapseCombination value Description
Collapse M_FLOAT

Specifies that the type of data is floating-point. The valid data depth is 32 bits.

(summarize)
Collapse M_SIGNED

Specifies that the type of data is signed. The valid data depths are 8, 16 or 32 bits.

(summarize)
Collapse M_UNSIGNED

Specifies that the type of data is unsigned. The valid data depths are 1, 8, 16 or 32 bits.

This is the default value.

(summarize)
Attribute INQ

Specifies the buffer usage. This allows you to specify the type of buffer, intended purpose, compression type, storage format, data direction, location, internal storage format, memory type, and overscan region of the created buffer; all of which provides additional information for other MIL functions.

This function should be used with caution because, when using physical addresses, it provides direct access to any of your computer's memory mapped devices; when using logical addresses, memory protection errors could result.

This parameter should be set to one of the values below.

function map For specifying the buffer usage
CollapseValue Description
MIL system-specific
tooltip (†)
Collapse M_ARRAY +

Specifies a buffer to store array type data. Note that some functions take an M_ARRAY buffer rather than a user-defined array.

(summarize)
† a b c d e f g h i j k l m n o p q r s
Collapse M_IMAGE +

Specifies a buffer to store image data.


You must specify a combination value from the following table:
(summarize)
† a b c d e f g h i j k l m n o p q r s
MIL system specific

Only single-band (monochrome) buffers with a depth of 8 or 16 bits can have an M_IMAGE attribute.

 † d
Collapse M_KERNEL +
[For essential MIL-Lite information, see remarks ]

Specifies a kernel buffer to store a custom filter for convolution functions.

The depth must be 8, 16, or 32-bit integer or floating-point.

(summarize)
† a b c d e f g h i j k l m n o p q r s
Collapse M_LUT +

Specifies a buffer to store lookup table data.

The valid data depths are 8, 16, or 32-bit.

(summarize)
† a b c d e f g h i j k l m n o p q r s
Collapse M_STRUCT_ELEMENT +
[For essential MIL-Lite information, see remarks ]

Specifies a buffer to store structuring element data for morphology functions.

The data depth must be 32-bit. If signed, the range is -32768 to +32767. If unsigned, the range is 0 to +32767.

(summarize)
† a b c d e f g h i j k l m n o p q r s
Combination constants for M_IMAGE.

You must add one or more of the following values to the above-mentioned value to set the intended purpose of this buffer.

Note that this value must not conflict with the attribute of the specified physical memory to which it is mapped. Such a conflict can result in errors that MIL cannot catch.

function map For specifying the intended purpose of the image buffer
CollapseCombination value Description
MIL system-specific
tooltip (†)
Collapse M_COMPRESS +
[For essential MIL-Lite information, see remarks ]

Specifies an image buffer that can hold compressed data. Note that a buffer with this attribute cannot have the M_SIGNED data type.

When mapping buffers for operations that require a source and destination buffer, and one of the buffers has an M_COMPRESS attribute, the data will be compressed or decompressed depending on the attributes of the destination buffer. If both the source and destination buffers have M_COMPRESS specifiers but different compression types, the data will be re-compressed according to the settings of the destination buffer.

(summarize)
† a b c d e f g h i j k l m n o p q r s
Collapse M_DISP

Specifies an image buffer that can be displayed.

(summarize)
† a b c d e f g h i j k l m n o p q r s
MIL system specific

Single-band display buffers with a depth greater than 16 bits cannot be allocated. Three-band display buffers can only be allocated with 8 bits per band.

 † f
Collapse M_GRAB

Specifies an image buffer in which to grab data. This type of buffer is usually allocated in MIL-reserved, physically contiguous, non-paged memory.

For Host buffers (M_HOST_MEMORY), the maximum (total) number of grab (M_GRAB) buffers is restricted by the total amount of MIL-reserved, non-paged memory (specified at installation time or using the MILConfig utility).

For on-board buffers (M_ON_BOARD), maximum (total) number of grab (M_GRAB) buffers is restricted by the total amount of on-board memory.

The physical nature of the buffers (using the ControlFlag) must be set to M_PHYSICAL_ADDRESS.

(summarize)
† a b c e f g h i j k l m n o p q r s
MIL system specific

Only single-band (monochrome) buffers with a depth of 8 or 16 bits can have an M_GRAB attribute.

 † c j k l m o p q r s

Only single-band (monochrome) buffers with a depth of 8 bits can have an M_GRAB attribute.

 † b f g h n
Collapse M_PROC +

Specifies an image buffer that can be processed.

 † a b c d e f g h i j k l m n o p q r s
Combination constant for M_PROC.

You can add the following value to the above-mentioned value to set the allocation of an overscan region.

Note that this value must not conflict with the attribute of the specified physical memory to which it is mapped. Such a conflict can result in errors that MIL cannot catch.

function map For allocating an overscan region
CollapseCombination value Description
Collapse M_ALLOCATION_OVERSCAN

Specifies that the buffer is allocated with an overscan region. Specify the size of the region using MsysControl() with M_ALLOCATION_OVERSCAN_SIZE.

(summarize)
Combination constants for M_COMPRESS.

You can add one of the following values to the above-mentioned value to set the compression type.

The image buffer's data depth dictates which compression type can be selected.

Note that this value must not conflict with the attribute of the specified physical memory to which it is mapped. Such a conflict can result in errors that MIL cannot catch.

function map For specifying the compression type INQ
CollapseCombination value Description
Collapse M_JPEG2000_LOSSLESS
[For essential MIL-Lite information, see remarks ]

Specifies that the buffer will be used to hold JPEG2000 lossless data. The supported data formats are: 1-band, 8- or 16-bit data.

(summarize)
Collapse M_JPEG2000_LOSSY
[For essential MIL-Lite information, see remarks ]

Specifies that the buffer will be used to hold JPEG2000 lossy data. The supported data formats are: 1-band, 8- or 16-bit data.

(summarize)
Collapse M_JPEG_LOSSLESS
[For essential MIL-Lite information, see remarks ]

Specifies that the buffer will be used to hold JPEG lossless data. The supported data formats are: 1-band, 8- or 16-bit data.

(summarize)
Collapse M_JPEG_LOSSLESS_INTERLACED
[For essential MIL-Lite information, see remarks ]

Specifies that the buffer will be used to hold JPEG lossless data in separate fields. The supported data formats are: 1-band, 8- or 16-bit data.

(summarize)
Collapse M_JPEG_LOSSY
[For essential MIL-Lite information, see remarks ]

Specifies that the buffer will be used to hold JPEG lossy data. The supported data format is 1-band, 8-bit data.

This is the default value.

(summarize)
Collapse M_JPEG_LOSSY_INTERLACED
[For essential MIL-Lite information, see remarks ]

Specifies that the buffer will be used to hold JPEG lossy data in separate fields. The supported data format is 1-band, 8-bit data.

(summarize)
Combination constants for M_IMAGE.

You can add one of the following values to the above-mentioned value to set a storage format and a location specifier.

MIL will interpret the created buffer according to the specified intended usage attribute. The source buffer's actual storage format can differ. If a specific internal format is required, it should be specified.

function map For specifying a storage format and a location specifier
CollapseCombination value Description
MIL system-specific
tooltip (†)
Collapse M_DIB
[This is only applicable to Windows]

Specifies that the buffer to be a DIB buffer. This ensures that your buffer is stored with a DIB header. Use MbufInquire() with M_BITMAPINFO to return a pointer (LPBITMAPINFO) to the header of the MIL buffer.

(summarize)
† a b c d e f g h i j k l m n o p q r s
Collapse M_DIRECTX
[This is only applicable to Windows]

Specifies that the buffer to be a DirectX surface.

 † a b c d e g h i j k l m n o p q r s
Collapse M_GDI

Specifies that the buffer to be compatible with GDI.

When using a device context (using MbufControl() with M_DC_ALLOC) for drawing, the buffer should be internally stored in GDI format, and cannot be a child buffer.

(summarize)
† a b c d e f g h i j k l m n o p q r s
Collapse M_LINUX_MXIMAGE
[This is only applicable to Linux]

Specifies that the buffer to be an X11 Ximage.

 † a b c d e g h i j k l m n o p q r s
Combination constant for M_IMAGE; M_LUT.

You can add the following value to the above-mentioned values to specify a location for a buffer that is FPGA accessible.

Note that the following value cannot be used with M_COMPRESS, M_DIB, M_DIRECTX, M_GDI, or M_LINUX_MXIMAGE.

function map For specifying that the buffer is FPGA accessible
CollapseCombination value Description
MIL system-specific
tooltip (†)
Collapse M_FPGA_ACCESSIBLE +

Specifies that the buffer is in a bank of memory that is accessible from the Processing FPGA. The exact bank of on-board memory is determined by the other attributes used with this value.

If combined with the M_HOST_MEMORY attribute, the buffer is in non-paged Host memory.

If combined with the M_GRAB, or M_PROC attribute, the buffer is created in memory bank 0.

If combined with the M_PROC attribute, the buffer is created in memory bank 1.

If combined with the M_PROC + M_FAST_MEMORY attribute, the buffer is created in memory bank 2.

(summarize)
† j l m p r
Combination constants for any of the possible values of the Attribute parameter.

You can add one of the following values to the above-mentioned values to set a location for a buffer.

function map For specifying a location for a buffer
CollapseCombination value Description
MIL system-specific
tooltip (†)
Collapse M_HOST_MEMORY

Specifies that the buffer is in Host memory.

(summarize)
† a b c d e f g h i j k l m n o p q r s
MIL system specific
This is a MIL system specific default value. † a b c e f g h i j k l m n o p q r s
Collapse M_MAPPABLE

Specifies that the buffer is in non-paged memory that can be set in the address space of the process (Host memory). By default, however it is not mapped to Host memory (that is, by default the buffer will have a physical address, but not a Host address). Use MbufControl() with M_MAP to enable or disable the mapping to Host memory.

This setting is useful when dealing with many large buffers that cannot all be mapped in Host memory at the same time. By allocating a buffer as M_MAPPABLE, it can be mapped and unmapped as needed.

Note that, if used with the M_PAGED attribute, an error will be generated.

(summarize)
† a b c e f g h j k l m n o p q r s
Collapse M_OFF_BOARD

Specifies that the buffer is not in on-board memory.

(summarize)
† a b c d e f g h i j k l m n o p q r s
MIL system specific

To ensure that an M_OFF_BOARD buffer can be used by the bus master transfer section of the board, the buffer must be created in non-paged memory (M_OFF_BOARD + M_NON_PAGED or M_HOST_MEMORY + M_NON_PAGED).

 † f g h i j l m n p r
Collapse M_ON_BOARD +

Specifies that the buffer in on-board memory.

(summarize)
† f g h i j k l m n p q r
MIL system specific

By default, all on-board buffers are allocated in memory that is not mapped on the PCI bus. This unshared memory cannot be accessed by the Host or any system other than the one on which it was allocated. See combination values below (M_SHARED) to change this default behavior.

 † j k l m p q r

This is only available for grab buffers (M_GRAB).

 † f

This is only available for image buffers (M_IMAGE).

 † g h i k n

This is only available for image (M_IMAGE) and LUT buffers (M_LUT).

 † j l m p q r
Collapse M_VIDEO_MEMORY
[This is only applicable to Windows]

Specifies that the buffer is in (off-screen) display memory of your graphics controller.

If Direct3D hardware acceleration mode is being used for display, the buffer cannot be created in display memory when any of the following attributes are used: M_GRAB or M_NON_PAGED. This is also the case when using DirectDraw 7 hardware acceleration mode if also using a non-Matrox graphics controller.

If Direct3D hardware acceleration mode is being used for display and you create the buffer in display memory, you must use the lock-unlock mechanism to access the buffer (MbufControl() with M_LOCK / M_UNLOCK).

(summarize)
† a b c d e f g h i j k l m n o p q r s
MIL system specific

Buffers cannot be created in video memory when any of the following attributes are used: M_COMPRESS, M_DIB, M_GDI, M_NON_PAGED, or M_PHYSICAL_ADDRESS.

 † d
This is a MIL system specific default value. † d
Combination constants for the values listed in For specifying that the buffer is FPGA accessible; and for the following value: M_ON_BOARD.

You can add one of the following values to the above-mentioned values to specify a specific bank of on-board memory.

Note that this value must not conflict with the attribute of the specified physical memory to which it is mapped. Such a conflict can result in errors that MIL cannot catch.

function map For specifying a specific on-board memory bank
CollapseCombination value Description
MIL system-specific
tooltip (†)
Collapse M_MEMORY_BANK_0

Specifies that the buffer is in memory bank 0 of memory that is accessible from the Processing FPGA.

Memory bank 0 is acquisition memory. This is the default memory bank for on-board buffer created with the M_GRAB or M_PROC attribute.

(summarize)
† j k l m p q r
Collapse M_MEMORY_BANK_1

Specifies that the buffer is in memory bank 1 of memory that is accessible from the Processing FPGA.

Memory bank 1 is SDRAM memory. If not available, an error is generated. This is the default memory bank for on-board buffer created with the M_GRAB or M_PROC attribute.

(summarize)
† j l m p r
MIL system specific

Memory bank 1 is SRAM memory. This is the default memory bank for an on-board buffer created with the M_PROC + M_FAST_MEMORY attribute.

 † j p r
Collapse M_MEMORY_BANK_2

Specifies that the buffer is in memory bank 2 of memory that is accessible from the Processing FPGA.

Memory bank 2 is SRAM memory. This is the default memory bank for an on-board buffer created with the M_PROC + M_FAST_MEMORY attribute.

(summarize)
† l m
Combination constants for the values listed in For specifying that the buffer is FPGA accessible; and for the following value: M_ON_BOARD.

You can add one of the following values to the above-mentioned values to set a location in a specific type of memory.

function map For specifying a location in a specific type of memory
CollapseCombination value Description
MIL system-specific
tooltip (†)
Collapse M_FAST_MEMORY

Specifies that the buffer is created in the fastest memory available.

Use MbufInquire() with M_EXTENDED_FORMAT to establish if the buffer is created in fast processing memory.

This attribute can only be combined with M_GRAB + M_FPGA_ACCESSIBLE. This value is typically the same as using M_MEMORY_BANK_2.

(summarize)
† j l m p r
MIL system specific

For Matrox Solios eA/XA and eCL/XCL, the fasted memory available is the SRAM. If SRAM is not present on your Matrox Solios, SDRAM will be used instead.

 † l m
Collapse M_SHARED

Specifies that the buffer is in shared processing memory. This memory is mapped on the PCI bus.

Note that this combination value can only be added to M_ON_BOARD.

(summarize)
† j k l m p q r
Combination constants for any of the possible values of the Attribute parameter.

You can add one of the following values to the above-mentioned values to set the attribute of the specified physical memory type.

Note that this value must not conflict with the attribute of the specified physical memory to which it is mapped. Such a conflict can result in errors that MIL cannot catch.

function map For specifying the attribute of the specified physical memory type
CollapseCombination value Description
Collapse M_NON_PAGED

Specifies that the buffer is in MIL-reserved, non-pageable memory.
Collapse M_PAGED

Specifies that the buffer is in pageable memory.
ControlFlag

Specifies the physical nature of the buffer. This parameter can be set to one of the values below.

function map For specifying the physical nature of the buffer
CollapseValue Description
Collapse M_HOST_ADDRESS +

Specifies that DataPtr is a logical address that points to the data.

Note that when using logical addresses, memory protection errors could result.

Note that you can use MbufInquire() with M_HOST_ADDRESS to get the logical address of a MIL allocated buffer.


You must specify a combination value from the following table:
(summarize)
Collapse M_MIL_ID +

Specifies that the new buffer maps to an existing source buffer. DataPtr points to the MIL identifier of the source buffer.


You must specify a combination value from the following table:
(summarize)
Collapse M_PHYSICAL_ADDRESS +

Specifies that DataPtr is a physical address that points to the data.

Note that using physical addresses provides direct access to any of your computer's memory mapped devices.

Note that you can use MbufInquire() with M_PHYSICAL_ADDRESS to get the physical address of a MIL allocated buffer.

This setting must be used for all buffers with the M_GRAB attribute.


You must specify a combination value from the following table:
(summarize)
Combination constants for the values listed in For specifying the physical nature of the buffer.

You must add one of the following values to the above-mentioned values to set how the pitch is measured.

function map For specifying how the pitch is measured
CollapseCombination value Description
Collapse M_PITCH

Specifies that the pitch is in pixels.

This is the default value.

(summarize)
Collapse M_PITCH_BYTE

Specifies that the pitch is in bytes.
Pitch INQ

Specifies the size of the pitch. The pitch is the number of pixels or bytes (as specified by the ControlFlag parameter) between the start of any two adjacent rows of the buffer. The actual length of a row in the buffer, in physical memory, might be different from the value of the SizeX parameter (for example, due to use of buffer overscan).

Note that your code should not make assumptions about the actual pitch of the source memory. If the memory was allocated using an MbufAlloc...() function, use MbufInquire() with M_PITCH or M_PITCH_BYTE to establish the required pitch.

function map For specifying the size of the pitch
CollapseValue Description
Collapse M_DEFAULT

Specifies that when dealing with a 1-bit buffer, the pitch is a multiple of 4 bytes; otherwise the pitch equals the SizeX parameter.
Collapse Value

Specifies the pitch in pixels or bytes (as determined by the ControlFlag parameter).

For an M_DIB buffer, if the pitch is in pixels (M_PITCH), the pitch must equal the SizeX parameter. If the pitch is in bytes (M_PITCH_BYTE), the pitch must be the next multiple of 4 that is larger or equal to (SizeX * bytes per pixel ).

(summarize)
DataPtr

Specifies the MIL identifier of a buffer, or a pointer to the data array, to which to map the created MIL buffer.

When the ControlFlag parameter is set to M_MIL_ID, DataPtr specifies the MIL identifier of the source buffer.

When the ControlFlag parameter is set to M_HOST_ADDRESS, DataPtr specifies a logical address that points to the data.

When the ControlFlag parameter is set to M_PHYSICAL_ADDRESS, DataPtr specifies a physical address that points to the data.

BufIdPtr

Specifies the address of the variable in which the buffer identifier is to be written. Since the MbufCreate2d() function also returns the buffer identifier, you can set this parameter to M_NULL. If allocation fails, M_NULL is written as the identifier.

Return value
The returned value is the buffer identifier. If allocation fails, an identifier of 0 is returned.
Remarks
  • [MIL-Lite]
    Note that during development and at runtime, compression support, particularly for an M_COMPRESS buffer type, requires the presence of a MIL license that grants access to the compression/decompression package. This access is only granted by default with the development license dongle for the full version of MIL. In other cases, you must purchase access to this package separately.
  • [MIL-Lite]
    You can allocate an image buffer with an M_KERNEL or an M_STRUCT_ELEMENT attribute with MIL-Lite. However, these attributes are not required to work under MIL-Lite.
Compilation information
Header Include mil.h.
Library Use mil.lib.
DLL Requires mil.dll.
DEFAULT HOST DEFAULT DEFAULT DEFAULT FLOAT SIGNED UNSIGNED ARRAY IMAGE KERNEL LUT STRUCT ELEMENT COMPRESS DISP GRAB PROC ALLOCATION OVERSCAN JPEG2000 LOSSLESS JPEG2000 LOSSY JPEG LOSSLESS JPEG LOSSLESS INTERLACED JPEG LOSSY JPEG LOSSY INTERLACED DIB DIRECTX GDI LINUX MXIMAGE FPGA ACCESSIBLE HOST MEMORY MAPPABLE OFF BOARD ON BOARD VIDEO MEMORY MEMORY BANK 0 MEMORY BANK 1 MEMORY BANK 2 FAST MEMORY SHARED NON PAGED PAGED HOST ADDRESS MIL ID PHYSICAL ADDRESS PITCH PITCH BYTE DEFAULT ARRAY IMAGE IMAGE M COMPRESS IMAGE M PROC IMAGE M GRAB KERNEL LUT STRUCT ELEMENT DEFAULT DEFAULT DEFAULT