Enumerations

Enumerations
enum	Movie2_Acq_Mode { Movie2_Acq_AddFrame = 0 , Movie2_Acq_Synchronous = 1 , Movie2_Acq_Asynchronous = 2 }
	Acquisition mode. More...
enum	Movie2_Sync_Mode { Movie2_Sync_Never = 0 , Movie2_Sync_BeforeCopy = 1 , Movie2_Sync_AfterCopy = 2 }
	Synchronization mode. More...

Detailed Description

Enumeration Type Documentation

Movie2_Acq_Mode

enum Movie2_Acq_Mode

Acquisition mode.

Examples:

Visual Basic - VB Movie2 OCX Example
Visual C++ - VC Movie2 OCX Example

Enumerator
Movie2_Acq_AddFrame	Images will need to be added to the AVI stream by calling AddFrame for each frame to be added. In Movie 1 this mode was called "FrameByFrame". In this mode the caller has to manage the acquisition. E.g. Grab has to be activated on the Image OCX or through the CVCDriver.dll, but the caller has the flexiblity to add the frame whenever he wants.
Movie2_Acq_Synchronous	Images will be acquired automatically by the recorder object using single Snap calls on the image object. In Movie 1 this mode was called "SingleSnaps". The acquisition is started automatically with StartRecording and the ImageSnapped Event of the Movie 2 Recorder is raised whenever a new image has been acquired. This mode is only useful for slow acquisitions - usually it makes more sense to use Movie2_Acq_AddFrame or Movie2_Acq_Asynchronous.
Movie2_Acq_Asynchronous	Images will be acquired automatically using the IGrab2/IPingPong interface of the image object if possible. Otherwise the AVI recorder switches back to single snap mode. If both are present, Movie2 will always use IGrab2. In Movie 1 this mode was called IGrab2/IPingPong. The acquisition is started automatically with StartRecording and the ImageSnapped Event of the Movie 2 Recorder is raised whenever a new image has been acquired.

Movie2_Sync_Mode

enum Movie2_Sync_Mode

Synchronization mode.

Examples:

Visual Basic - VB Movie2 OCX Example
Visual C++ - VC Movie2 OCX Example

Enumerator
Movie2_Sync_Never	Synchronization of Acquisition and memcopy will not happen which means that for best performance we always rely on the acquisition of the next image to take more time than the copy of the previous one. In real acquisition modes (Movie2_Acq_Synchronous, Movie2_Acq_Asynchronous) setting Movie2_Sync_Never as synchronization mode will cause the ImageSnapped event to not appear at all!
Movie2_Sync_BeforeCopy	Synchronization will happen before copying the data. In terms of the AddFrame mode this means that an AddFrame call will block if the data from the previous AddFrame call is still being copied, but will return immediately after signaling that the data is there.
Movie2_Sync_AfterCopy	Synchronization happens after copying the data. In terms of the AddFrame mode this means that an AddFrame call will not return until all the data has been copied.