|Enosoft DV Processor Help|
How It Works
How To Use It
A Real World Example - Live web streaming from a remote DV camcorder
Configuring Your Network
The essence of the Enosoft DV Processor is to perform real-time processing of an incoming DV stream and send to either a local file, the computer's display or an attached DV device. The most powerful option is that of device-to-device processing. This effectively inserts the processor between the two DV devices. However, this only works when the output device is a physical, external device such as a DV camcorder, tape recorder or some DVD recorders with FireWire input. It would be very useful if computers could be connected together such that they appear as DV devices. This would allow computers to be daisy-chained together and provide subsequent processing of the Enosoft DV Processor's output. In theory, such capability is possible but it has not been implemented for Windows by Microsoft.
An example of where this capability would be useful is live web streaming of athletic events where the video needs to be processed before streaming. Such processing might include graphics showing the score and channel branding. If it were possible, the Enosoft DV Processor would take the live video, process it and then send it to another computer. This second computer would see the first one as a DV device and the necessary live web streaming software would convert it and then stream it.
Enosoft Net DV effectively implements this capability by sending a live DV stream from one computer to another via TCP/IP on a local area network (LAN). A similar function for sharing DV streams between applications running on a single computer is provided by Enosoft Virtual DV.
XP ONLY: Windows XP supports simple networking via IEEE-1394 (FireWire). i.e., two computers each running Windows XP can be connected via FireWire using the TCP/IP. Using Enosoft Net DV over such a connection solves the problem of sharing DV streams between computers via FireWire.
Enosoft Net DV consists of two components that both appear to the operating system as DV devices even though they aren't real hardware devices. These "virtual" devices can be seen by other programs that can connect to external DV equipment. The two components are the Enosoft Net DV Transmitter and the Enosoft Net DV Receiver.
This component receives an incoming DV stream such as the processed output from the Enosoft DV Processor. Instead of sending it to an external DV device or a file, it sends the DV stream to a suitable application running on a different computer. To be able to receive the DV stream, the program simply uses the second component described next.
This component receives the DV stream sent by the Enosoft Net DV Transmitter. It appears to applications as a DV capture device. Every frame sent by the transmitter component is made available to the host application as if it were capturing from a DV device.
Only one computer can receive the DV stream being broadcast by the Enosoft Net DV Transmitter.
The following example shows how one instance of the Enosoft DV Processor ("Processor A") can send its output to another instance of the Enosoft DV Processor running on a second computer ("Processor B").
Note, the order in which these steps are made is important.
Launch Processor A, select a suitable source for Input and then select Enosoft Net DV Transmitter for Output:
Launch Processor B, select Enosoft Net DV Receiver for Input and then select a suitable Output:
Note, this step MUST occur before the next one.
Start Processor A running:
Start Processor B running:
In this example, the live incoming DV stream on the first computer is being displayed in a video renderer window on the second computer in real-time.
The transmitter must always be initiated first. It isn't necessary for it to be running but it must be connected to a valid input DV stream.
Once the transmitter has been initiated, it waits for a connection from a receiver. If a receiver is already running, it will NOT be connected to the transmitter.
When the receiver is initiated, it looks for an active transmitter. If it finds one, it will become connected to it. The transmitter must already exist before the receiver is started.
Both applications hosting the transmitter and receiver can start and stop as necessary.
If either of the two applications stop using the transmitter/receiver, both the transmitter and receiver will have to be restarted. How this is done depends upon the host applications. For the Enosoft DV Processor, this simply requires reselecting the components. For other applications, it may require closing and restarting the application.
See also Advanced Options.
This section shows an example of how to stream a live DV signal (e.g., from a camcorder) from Windows Media Encoder (WME).
Windows Media Encoder is required - follow the link for Windows Media Encoder 9 Series from:
Ideally, WME would use the Enosoft Net DV Receiver as its source. However, it can be tricky to get WME to encode successfully. Therefore, the Enosoft DV Processor is used on the second computer to act as a bridge. It is used to receive the broadcast from the first computer and then use Enosoft Virtual DV to make the DV stream available to WME. Schematically,
First computer: Camcorder -> Enosoft DV Processor -> Enosoft Net DV Transmitter
Second computer: Enosoft Net DV Receiver -> Enosoft DV Processor -> Enosoft Virtual DV Renderer ---> Enosoft Virtual DV Source -> WME -> Streaming
The steps required for setting up the first computer are the same as given earlier. When running, the first computer's Enosoft DV Processor will resemble this:
To set up the second computer, follow the instructions given earlier for the second Enosoft DV Processor except select Enosoft Virtual DV Renderer for the output.
Launch WME and follow the instructions for the "Broadcast a live event" wizard:
Select Enosoft Virtual DV Source for both video and audio devices and click Next:
Choose the broadcast method (typically pull mode):
Configure the broadcast network properties as appropriate:
Configure the encoding parameters:
You can continue with additional wizard options or just press Finish.
Once the wizard is complete, Windows Media Encoder will be ready to start encoding:
Start the Enosoft DV Processor on the first computer running followed by the one on the second computer.
Start the encoding process with Windows Media Encoder.
Enosoft Net DV uses the TCP/IP protocol on your local area network (LAN) to share the DV stream between computers. Specifically, it uses the TCP method of sharing data. By default, both Enosoft Net DV components automatically attempt to connect. For most scenarios, this is sufficient. However, it may be necessary to change the networks settings that the components use. In addition, it is necessary to specify the video format (PAL or NTSC) that will be used.
When the Enosoft Net DV Transmitter starts, it opens a TCP socket on port 51829. Likewise when the Enosoft Net DV Receiver starts, it scans the entire subnet for an open TCP port at 51829. i.e., if the receiver is running on a computer with an IP address A.B.C.D, it scans all the addresses between A.B.C.1 and A.B.C.254.
Any firewalls running on both computers must be configured to allow traffic on TCP port 51829.Default settings are used when the following registry keys:
contain a value named
AutoConfigure that is set to 1. Set this
to 0 to use custom configurations. Each component can be configured separately.
The Enosoft Net DV Receiver has to know whether the incoming DV stream will be PAL or NTSC format. It cannot determine this automatically. Therefore, when it starts, it looks in the registry for the necessary information. The registry location is:
and contains a value named
NTSC. For PAL, set
to 0 otherwise set it to 1.
Custom settings are typically required when:
For the latter case, the default behavior will use the first address on the first adaptor as listed by Windows. If a computer has an ethernet connection and a wireless connection, the default behavior may use the less preferable or appropriate one.
The registry settings permit the IP address and TCP port to be configured as
needed. Both the
Tx registry keys (above) contain
two values named
enter an IPv4 address of the form
22.214.171.124 and for the
enter a decimal number in the valid TCP port range.
Last Updated on Sunday, 8th March, 2009. Application Version 1.5.4.
© 2006-2009 Enosoft, Hillsborough, NC. All rights reserved.