Home > A: Camera Basics > History back  Previous chapter  Next chapter  Print  

Image Display Modes

uEye Camera Manual Version 3.80

Image Display Modes

The uEye driver provides different modes for displaying the captured images on Windows systems. We recommend using the Bitmap mode or the Direct3D functions, depending on your specific application.

For a list of API functions for image display see How To Proceed: Image Display.

Achtung

The DirectDraw BackBuffer and DirectDraw Overlay Surface display modes are obsolete. Please use the Direct3D functions instead (see also Obsolete Functions).

1. Bitmap mode (Device Independent Bitmap, DIB)

In Bitmap mode, images captured by the uEye are written to the random access memory of the PC. Programming the image display is up to the user. The application software uses the is_RenderBitmap() function to initiate the image display by the graphics card. This may result in a slightly higher CPU load as compared to the Direct3D display.

The advantage of Bitmap mode is that it is compatible with all graphics cards and that image data in the memory is directly accessible. Programming of overlay functions is up to the user. Since the operating system controls the image display, the image may be completely or partly overlapped by other windows and dialog boxes.

 

Figure 16: How the Bitmap mode works

Figure 16: How the Bitmap mode works

2. Direct3D mode (only under Windows with DirectX)

In this mode, the uEye driver writes the image data to the invisible area of the graphics card. This process runs automatically and does not have to be controlled by the application software. It requires an installed Direct3D driver, sufficient memory on the graphics card and Direct3D function support by the graphics card. For this purpose, graphics cards generally provide better performance than graphics chips integrated on the mainboard. In Direct3D mode, the CPU load may be lower than in Bitmap mode. You can display overlay data and also scale the video image.

The Direct3D mode and the overlay functions can be configured using the is_DirectRenderer() API function.

 

Figure 17: How the Direct3D mode works

Figure 17: How the Direct3D mode works

Comparison of the display modes

The following table illustrates the major differences between the display modes:


Bitmap mode

Direct3D mode

Graphics card requirements

Low. No special graphics hardware required. Runs on all systems.

High. Graphics card has to support Direct3D. Does not run on all systems.

Operating system

Windows, Linux

Only Windows with DirectX

Programming effort

Greater. Memory management, event handling and display performed by the application.

Low. Memory management, event handling and display performed by DirectX.

CPU load

Slightly increased by copying of data.

Low. Display performed by graphics card.

Overlay functions

Not available. A simple overlay can be programmed by the user.

Integrated. Complex overlays can be displayed without flicker.

Access to image memory

Direct access possible. Image data already provided in user memory.

Possible using Steal Mode. Single images can be copied to the user memory.


Suggestion for improvement? Send us your short Feedback on this chapter. Thank you very much!


© 2010 IDS Imaging Development Systems GmbH
http://www.ids-imaging.com