Dv Connectivity

7/28/2019 Dv Connectivity

1/11

TROUBLESHOOTING DV CAMCORDER CONNECTIVITYhttp://www.enosoft.net/

Unless specified, these instructions apply to both 32-bit and 64-bit versions of

Windows XP and Vista.

Unplug all devices from FireWire interface (this includescamcorders, hard drives etc)

Verify FireWire interface is work ing

Look for an IEEE 1394 Bus host controllerentry in Device Manager:

Connect camcorder

With the camcorder turned off, connect it to the FireWire interface and then turn it on.Make sure the camcorder is sending a signal e.g., put the camcorder in camera modeor play a tape in VTR mode. If available, generating color bars is a good option.

2008 Enosoft, Hillsborough, NC. All rights reserved.


2/11

Check Device Manager for new Imaging devices entry

Confirm Digi tal Video Device window pops up on the Desktop



3/11

The exact contents of this pop-up will vary and it may not display at all if you havepreviously selected Always perform the selected action.

Click Cancel to dismiss this pop-up window.

Verify new entry in My Computer (32-bit XP Pro only)



4/11

Open folder to verify incoming DV video is visible (32-bit XP Proonly)

Close the folder (32-bit XP Pro only)



5/11

Al ternative option for other Windows versions open WindowsMovie Maker and choose Capture Video from File menu

Follow the wizards steps until the preview window for the DV device is visible:



6/11

What if the video is blank?

If either of the options above fail to show the video even though the device has beendetected then it is likely that another application or utility program has already staked aclaim to the camcorder.

DV devices communicate with Windows on two levels. The first level is via the AV/CSub-unit Protocol basically, this is an industry standard for controlling an AV devicestransport such as play, pause, record etc. The second level is via the DV streamcontaining the audio and video.

Any application wishing to use a DV device begins by asking Windows for a list of all theDV devices that Windows has detected. The application then asks Windows for accessto the driver that will communicate with the device (this is the MSDV driver). When morethan one application wants to use the same device, each one can communicate at theAV/C level i.e., each application can control the transport of the camcorder forexample. However, one and only one application can communicate with the deviceat the DV stream level. The first application to ask for the driver will get access to the



7/11

DV stream. All the other applications trying to use the device at the same time will notsee the DV stream.

Typically, the symptoms of this behavior are that one application will appear normal butothers will display a blank image while any transport control buttons will work asexpected.

Sometimes these symptoms will occur even though it seems only one application isrunning. In such cases, it is usually due to so-called utilities installed by variouspackages from Nero, Pinnacle and Roxio. Often, these utilities are present in thesystem tray on the desktop. Disabling or removing these utilities usually solves theproblem.

To illustrate the problem (32-bit XP Pro only), carry out the Windows Movie Maker testabove, leaving the wizard open at the preview screen. Now open the My Computerfolder as described earlier to display the video. It will fail with the following message:

Symptoms wi th the Enosoft DV Processor

If a device that is already in use is selected for the Input stage of the Enosoft DV

Processorthen the video will not be visible:



8/11

Note that the timecode and format are available via the AV/C protocol and so aredisplayed.

When the other application that already owns the camcorder is closed and thecamcorder reselected as the input (it is not necessary to close and relaunch thesoftware) then the video is now visible along with other information in the DV stream:



9/11



10/11

WORKING WITH MULTIPLE DV DEVICES

The Enosoft DV Processoris one of the few Windows applications that allow morethan one DV device to be used at the same time. This permits synchronized multicam

capturing, for example. Unfortunately, limitations of the way that DV devices work withFireWire can lead to difficulties in getting more than one device to work simultaneouslywith Windows.

The most common symptom is that one or more of the devices will not show any video much like the way described earlier. Sometimes, the devices wont be detected at all.

When any device is connected to a FireWire, it tries to negotiate with the FireWirecontroller whether or not it should become the bus master. Typically, if it is the firstdevice to be connected after the FireWire interface has been reset then it will be the busmaster. Unfortunately, many DV devices expect to be the bus master and if a DV deviceis already connected then a conflict can occur. Some or all of the DV devices may end

up not communicating properly with the host computer.

Some general rules based upon our experience

In an ideal world, the best recommendation is to dedicate one FireWire interface (e.g.,an interface with 3 ports) per DV device.

Avoid sharing the FireWire interface with other FireWire devices such as external harddrives. Move these to other FireWire interfaces or, if supported, use USB2.0.

Attaching 3 devices to a 3-port interface will almost certainly fail.

Attaching 2 devices to a 3-port interface will often work successfully as long as thefollowing guidelines are followed:

2 devices on one interface

Unplug both devices Reset the FireWire interface (use Device Managerto disable and re-enable the

interface)

Attach one device and turn it on Verify the device is detected follow the steps above to test if the video is

available Attach the second device and turn it on

Repeat the verification for the first device - it is possible that connection of thesecond device causes the first one to stop communicating properly.

Verify the second device is detected and the video is available

If the above fails to provide two fully visible devices then try changing the order in whichthe devices are attached. Ensure that the FireWire interface is reset first.

You can launch two instances of the Enosoft DV Processor one for each device toverify if both are visible at the same time.



11/11

3 devices on two interfaces

Getting 3 devices to work on two interfaces can be a matter of trial and error. Assumethe devices are A, B and C and the interfaces are I1 and I2.

Using only one device at a time, verify that it is fully accessible on both interfaces

in the ways described earlier Using the guidelines for 2 devices on one interface, try to configure devices A

and B on interface I1. If successful, put device C on interface I2. You shouldhave 3 fully accessible devices.

If this doesnt work keep trying each pairwise combination on interface I1. i.e., Band C then A and C.

If this doesnt work, try all the pairwise combinations on interface I2.

Usually, you will find a combination of DV devices and interfaces that will work. Make anote of the successful configuration.

Beyond 3 devices

The same principles apply to attaching 4 or more devices to 2 or more FireWireinterfaces.


Documents

Dv Connectivity