Top  Previous 

Below is the list of the most frequently encountered issues and remedies for their resolutions:

Problem description

The camera is not recognized by ActiveDcam. "No DCAM camera found" message appears in the control window.
The camera is not receiving power.

1394 Camera Driver is not installed for the camera.

The camera is not DCAM-compliant.

Windows 7 Gap Count Optimization is enabled

This is a typical issue for notebook computers that do not provide power to external 1394 devices. Use a FireWire hub or DC power cable to connect your camera to a laptop.

ActiveDcam will not work with a system driver provided by your camera manufacturer. Refer to Driver Setup for the DCAM driver installation procedure.

ActiveDcam only works with IIDC-1.30 and -1.31 compliant cameras. Non-compliant cameras (such as DV-camcorders) will not be recognized by ActiveDcam. Use the manufacturer's provided software.

a) Modify/Create the registry key HKEY_LOCAL_MACHINE\SYSTEM\
Parameters\EnableGapCountOptimization to have a DWORD value of 0.
b) Alternatively, switch the default Microsoft OHCI driver to the legacy version

Live video occasionally freezes. After restarting the application "Error in the system 1394 driver" appears in the control window. In some cases system reboot is required.
The camera and 1394 board have a compatibility problem.

The computer/board/cabling has an intermittent hardware issue
Some 1394 boards/chipsets are known not to perform well with certain models of 1394 cameras. For example, Hitachi cameras have trouble running with Adaptec and Matrox boards. Replace your board with a board recommended by your camera manufacturer.

Replace the cable or try to run the camera/software on a different system.
The video is corrupted (frames are broken into parts, jittering occurs or synchronization is lost). Some video formats and frame rates do not work.
The camera and 1394 board have a compatibility problem.

The processor has an extensive latency in the C3 power state transition.

You are running Windows XP and the camera is connected to 1394b board.
See the solution above.

This problem is common for notebook computers. To correct the latency setting, run C3State.reg file located in the Driver folder. Restart the system for the changes to take effect.

If you are using a 1394a camera, run the following fix from Microsoft:
If you are using a 1394b camera, perform a "rollback" procedure as described in 1394b (FireWire 800)

Problem description

When switching to certain video modes, I get blank screen.
Some cameras require turning the acquisition off while switching between video modes.
Turn the acquisition off by setting the Acquire property to off, then select the desired video mode and turn the acquisition on.
VB.NET and C# sample applications do not work.
.NET framework is not installed on the system
Install the latest .NET framework from Microsoft:

When I try to compile sample projects from their default directories in C:\Program Files, I get an error message "Could not create an output directory"
You do not have write permissions due to User Account Control (UAC).
Copy the Samples folder from C:\Program Files\ActiveGige\ to one of your user directories (e.g. Desktop) and open sample projects from there.

Alternatively, ask your system administrator to provide you with writing permissions for the ActiveGige folder.
When I run a live video application from within Visual Studio.NET, everything freezes.
Live video is active in the Design mode. Visual Studio.NET doesn't close the designer while starting the application.
ActiveDcam cannot run two instances of live video acquired from the same camera. Make sure to close the design view before running your application. The best way to avoid this problem is not to use live display in the design mode except for testing purposes. You can initiate acquisition in your code by setting the Acquire property to true.
I am trying to do real-time image processing in .NET, and I experience a significant drop in the frame rate.
VB.NET and C# have performance issues when working with large arrays.

FrameAcquired event has an overhead that might affect the performance
For performance boost, use unsafe code and pointers to directly access ActiveDcam image buffer. A pointer to the image buffer is provided by GetImagePointer.

For VB.NET, C# and C++ applications use FrameAcquiredX event.
AVI files are not recorded in real-time, many frames are being dropped.
Your system does not provide enough throughput or CPU power to keep up with the camera frame rate
Switch to a lower resolution mode or reduce the frame rate. If you are using a Bayer camera, consider recording the monochrome video instead of color one. Alternatively, upgrade your system to a faster hard drive and/or CPU.

Problem description

ActiveDcam installation fails with the following error: "ActiveDcam.dll failed to register, HRESULT -2147024770"

Runtimes components of Visual C++ 2005 are not installed on your system
Install Microsoft's VC++ 2005 Redistributable Package, then run ActiveDcam installation again.

For the 64-bit OS you may also need to install VC++ 2005 Redistributable Package 64-bit

ActiveDcam installation fails with the following error: "ActiveDcam.dll failed to register, HRESULT -2147220473"
This error is usually caused by a corrupted registration of atl.dll system file.

1. Locate atl.dll, generally found in "C:\WINNT\system32" or "C:\WINDOWS\system32".
2. Open the command-line prompt
·o Start Menu/Run  
·o type "cmd"  
·o press "ENTER"  
3. Using the atl.dll filename and path, call regsvr32, i.e. at the command-line prompt, type:
·o regsvr32 "C:\WINNT\system32\atl.dll"  
·o press "ENTER"  
4. You should see a regsvr32 window, confirming success: Close it.
5. Repeat ActiveDcam installation.