VBrick Systems VB6000 Welding System User Manual


 
2 © 2008 VBrick Systems, Inc.
Microsoft Windows Media Player 7.1 (Windows 98 or 2000 only); Media Player 9, 10, or
11 (Windows XP only).
Standard Features
The VB6000 WM Appliance supports approximately 40 Mbits/sec total throughput via the
Ethernet/IP connection. This bandwidth can be used for any of the standard features shown
in Table 1 but the overall performance of any one of these features can be affected by the
sum total. For example, you can download more content from the hard drive when the
encoder(s) are not streaming, pushing, and/or multicasting. In a typical scenario, the hard
drive will support the progressive download of a video file to a maximum of 20 simultaneous
viewers, or 20 MBits/sec—whichever comes first.
Table 1. Encoder and Reflector Features
Typical VBrick Applications
The following scenarios describe typical applications for the VBrick WM Appliance. These
applications can be LAN-based, WAN-based, or a combination of both LAN and WAN
network topologies. Note that the VBrick WM Appliance can support all of these
Standard Feature Encoder Reflector
Accepts composite or S-Video input. X
Available as single or dual channel. X
Multiple bit rate support. X
Windows Media Audio 8 encoding (5 Kbps–192 Kbps). X
Windows Media Video 9 encoding (20 Kbps–4 Mbps). X
Optional 60 GB hard drive for local archiving. X X
8-bit 4:2:0 color format. X
Up to 640x480 resolution. X
Initiate HTTP Pull from a WM appliance or a WM server/encoder. X
Receive HTTP Push from a WM appliance or Microsoft encoder. X
Progressive download (20 simultaneous viewers). X X
Multicast streaming (UDP). X X
† Any combination of up to 200 clients including:
Unicast RTSP Streaming (UDP).
Unicast HTTP Streaming (TCP).
Stream Push (25 maximum) to a VBrick Reflector, a Microsoft
Windows Media Server, or RealNetworks Helix Server via
HTTP (TCP).
Stream Pull from Microsoft Windows Media Server or
RealNetworks Helix Server via HTTP.
XX
The total number of supported clients will be reduced if you are using the JPEG capture
feature. See JPEG Capture Constraints
on page 68 for details.