Enumerations

Enumerations
enum	Movie2_AcqMode { Movie2_AcqAddFrame = 0 , Movie2_AcqSynchronous = 1 , Movie2_AcqAsynchronous = 2 }
	Acquisition modes. More...
enum	Movie2_SyncMode { Movie2_SyncNever = 0 , Movie2_SyncBeforeCopy = 1 , Movie2_SyncAfterCopy = 2 }
	Synchronization modes. More...

Detailed Description

Enumeration Type Documentation

Movie2_AcqMode

enum Movie2_AcqMode

Acquisition modes.

Supported platforms:

Win32
Win64

Related Topics:

Movie2GetAcqMode, Movie2SetAcqMode

Examples:

Visual C++ - VC Movie2 Example

Enumerator
Movie2_AcqAddFrame	Images will need to be added to the AVI stream by calling Movie2AddFrame for each frame to be added. In Movie 1 this mode was called "FrameByFrame". In this mode you have to manage the acquisition. E.g. Grab has to be activated over the Image OCX. But you have the flexibility to add the frame whenever you want.
Movie2_AcqSynchronous	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 Movie2StartRecording and the ImageSnapped Event of the Movie 2 Recorder is called instead of an ImageSnaped Event from an Image OCX. This mode is only useful for slow acquisitions. When you use a driver you should use Movie2_AcqAddFrame or Movie2_AcqAsynchronous.
Movie2_AcqAsynchronous	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 Movie2StartRecording and the ImageSnapped Event of the Movie 2 Recorder is called instead of an ImageSnaped Event from an Image OCX.

Movie2_SyncMode

enum Movie2_SyncMode

Synchronization modes.

Supported platforms:

Win32
Win64

Related Topics:

Movie2GetSyncMode

Examples:

Visual C++ - VC Movie2 Example

Enumerator
Movie2_SyncNever	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_AcqSynchronous, Movie2_AcqAsynchronous) setting Movie2_SyncNever as synchronization mode will cause the ImageSnapped event to not appear at all!
Movie2_SyncBeforeCopy	Synchronization will happen before copying the data. In terms of the Movie2AddFrame mode this means that an Movie2AddFrame call will block if the data from the previous Movie2AddFrame call is still being copied, but will return immediately after signaling that the data is there.
Movie2_SyncAfterCopy	Synchronization happens after copying the data. In terms of the Movie2AddFrame mode this means that an Movie2AddFrame call will not return until all the data has been copied.