The Visual Circuits logo is a registered trademark in the United States
and other countries. All other products, services or compan y names
mentioned herein are claimed as trademarks and trade names by their
respective companies.
cVisual Circuits, 1999-2000. All rights reserved.
No porti on of this manual ma y be copied by any means without the pri or
consent of Visual Circuits.
Visual Circuits
5155 East River Road, Suite 401
Minneapolis, MN 55421
http://www.visualcircuits.com
Visual Circuits Publication Number: 813-0001a
Federal Communications Radio Frequency Interference
Statement
WARNING: Changes or modifications to this unit not expressly
approved by the party responsible for compliance could void the user’s
authority to operate the equipment.
This equipment has been tested and found to comply with the limit s for a
Class A digi tal device, pur s uant to Part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the
instructional manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be
required to correct the interference at his own expense. However, if this
equipment does cause interference to radio or television equipment
reception, which can be determined by turning the equipment off and on,
the user is encouraged to try to correct the interference by one or more of
the following measures
❏Reorient or relocate the receiving antenna.
❏Increase the separation between equipment and receiver.
❏Connect the equipment to an outlet on a circuit different
from that to which the receiver is connected.
❏Consult the dealer or an experienced radio/television
technicia n for help.
Industry Canada
This Class A digital appartus meets all requirements of the Canadian
Interference-Caus ing Equi p ment Re gu lati on s.
Cet appareil numerique de la classe A respecte toutes les exigences du
Regulement sur le materiel brouilleur du Canada.
EMC and Safety Directive Compliance
The CE mark is affixed to this Visual Circuits Corporation product to
confirm compliance with the following European Community Directives:
Council Di rective 89/336/ EEC of 3 May 1989 on the approximation of
the laws of Member States relating to electromagnetic compatibility.
And
Council Directive 73/23/EEC of 19 Februa ry
1973 on th e harmonization of th e laws of
Member States relating to electrical equipment
designed for use within certain voltage limits:
Each ammended by
Council Directive 93/68/EEC of 22 July 1993
on the harmonization of CE marking
requirements.
The Visual Circuits ReelTime 4 and the 4ReelTime Pro boards are
PCI bus boards that can play back up to four MPEG2 or MPEG1
video and audio files simultaneously. The ReelTime 4 supports
composite video, S-video, or interlaced RGBS video (Red, Green,
Blue, with combined H/V sync). This form of RGB video cannot
be displayed on a standard computer VGA monitor. There is CD
quality stereo audio output for each channel.
The 4ReelTime Pro suppor ts compos ite vi deo and opt ional S-video
output. The ReelTime 4 board has replaced the 4ReelTime Pro,
offering the same performance with increased functionality.
NOTE
ReelTime 4 and 4ReelTime Pro boards cannot
be mixed in the same server.
The ReelTime 4, in addition to adding RGB quality video output,
now provides software controlled volume adjustment on the
baseboard. (Volume control previously required an additional
audio or genlock card.) The ReelTime 4 supports the new RT
Daughter card for genlocking. The RT Daughter card also offers
an onboard blackburst generator. (See RT Daughter document for
details.)
Each board is designed to operate as a PCI bus master. This means
that once the software tells the board where to retrieve the MPEG
data from, the board will retrieve and route the data to the
appropriate channel with minimal CPU use. This feature allows
for multiple boards to run concurrently with smooth multi-channel
video and audio playback.
1
An On-Screen Display (OSD) is also included on the boards. This
OSD provides a full-resolution (up to 720x480) graphic or text
overlay on each MPEG file being pla yed. The overlay can be set to
16 levels of transparency and can have up to 16 simultaneous
colors.
A Windows NT driver and software developer’s kit (SDK) is
included with the board. Consult with your Visual Circuits
representative for Linux and Windows 2000 support. Also check
for software downloads at www.visualcircuits.com.
Genlock Options
The RT Daughter card is an additional option for the ReelTime 4.
The connectors on the daughter card attach to the two rows of pins
on the RGB baseboard. The daughter card does not require an
additional PCI slot and easily supports multiple card servers. The
daughter board supports the ability to genlock to an external
composite video source. This module also includes a stereo audio
and composite video switch for roll-free switching between the
MPEG file being played and an external audio/video source. The
genlock module also adds volume and tone control to each audio
channel. An external composite video source can be "switched" to
and displayed on the video display monitors. Audio switching can
be done as well.
2
Overview
A "non-switching" version of Genlock is also available. This is
often used to provid e a cont inu ous signal sync for display dev ic es.
The external syn c sourc e is oft en a bla ckburst gener ator. Howev er,
any composite video signal source may be used. With "Nonswitching" Genlock, S-Video and RGB video output is supported.
The RT Daughter card also has its own on board blackburst
generator for continuous signal sync for video displays and
projectors if required.
Audio/Video Distribution
There are three options from Visual Circuits for audio/video
distribution. None of these devices are powered and follow all
standard audio/video cabling procedures.
1. Mini AV Breakout Box: This box brings out four BNC
composite video connectors, four S-video connectors and four
mini-phonejack stereo audio connectors. The box connects
directly to the DB-25 pin connector on the board and occupies
only one slot width on the back of a PC chassis. S-video and
composite video are simultane ously a vail able on each cha nnel.
No RGB output is supported.
2. Rackmount Breakou t Box: This br ing s out all video signals to
BNC connectors and audio to terminal post ("Phoenix type")
connectors. A twisted ribbon cable with adapters connects the
boards DB 25 pin to the rackmount’s 1 RU enclosure. The
Rackmount Breakout Box supports all configurations.
3. Universal Cable: This cable also supports all board
configurations and comes as a 19 inch cable which attaches to
each board’s DB 25. All output connectors are RCA female
type, requiring appropriate adapters and patch cables. (Visual
Circuits does not carry cable adapters and accessories.)
3
Overview
ReelTime 4 vs. 4ReelTime Pro
The ReelTime 4 is the current multiple-channel board. The
software is compatible with the 4ReelTime Pro with the exception
of some initialization values and some additional driver parameter
selections.
Audio control is now selectable on the RGB baseboard through
software.
CAUTION
Due to board revisions, idividual servers do
not support configurations of both 4ReelTime
Pro and ReelTime 4 boards integrated into the
same system.
The ReelTime 4 supports Red, Green, Blue and Combined
Horizontal and Vertical Sync (H/V). The ReelTime 4 does not
support Sync on Green or Separate H/V Sync. The RGB output is
interlaced and cannot be viewed on standard PC monitors.
Each output channel of the ReelTime 4 can be individually
selected for Composite/S-vide o (available simultaneously) or RGB
(combined H/V Sync). This can be determined by selecting the
video output type. For more information see “VideoTypes” on
page 25.
4
Figure 1. Front view of 4ReelTime Pro board.
Figure 2. Front view of ReelTime 4 board.
Overview
5
Overview
Figure 3. Back view of ReelTime 4 board.
The main visual difference between the ReelTime 4 and the
4ReelTime Pro boards are the four large LSI chips located on the
back side of the RGB board. When in doubt of which type of
board you are using look on the back side of the board as a
reference.
6
Overview
API for Calling the Driver
The source code for the Vidserve demo program is provided for
developers as an example of how to access the driver. The current
version of the driver uses a proprietary C API interface (instead of
a standard interface like MCI, ActiveMovie or Direct X).
Applications can use the driver by calling the dynamic link library
4REELAPI.DLL. The files needed (4REELAPI.LIB and
4REELAPI.H, 4REELSYN.H) are provided in the
VIDSERVE.ZIP file, along with the source code and MS VC++
2.0 project makefile for Vidserve. See 4REELAPI.H for a
complete descriptio n of the interface functions. The interchannel
synchronization functions are declared in 4REELSYN.H.
For further programming details see the ReelTime 4 SDK manual.
7
Overview
8
INSTALLATION GUIDE
The Visual Circuits Corporation 4ReelTime Pro and ReelTime 4
decoder boards are full sized PCI cards. The card is secured using
an IO mounting bracket secured to the chassis. This bracket is
affixed to the 25-pin female D Sub output of the board.
CAUTION
If a card is not lodged securely in the PCI slot
when the system power is applied, damage to
the 4ReelTime Pro or ReelTime 4 board may
occur.
CAUTION
It is possible to damage system components,
primarily the system's mainboard, if power is
applied to an improperly seated card.
CAUTION
Whenever installing a board, never force the
board into position. During the installation if
pressure or tension is noted, stop immediately
and refer to the chassis manufacturer's
specifications for card installation and
placement.
9
Installation Guide
CAUTION
Follow all necessary precautions when
handling electrical circuit boards. Damage can
occur due to frictional contact with board
circuitry or due to electrostatic discharge
(ESD).
Card Installation
To install the card, carefully slide the board into the selected PCI
slot of the mainboard. Ensure that the bracket is aligned with the
IO opening of the chassis and that the outer edge of the card rests
securely according to the chassis’ design. Consult with the chassis
manufacturer for sp ecific guidelines.
Figure 4. Installation of board.
In some systems it may be necessary to install a mounting bracket
extension to the board in order to "reach" the card guide of the
chassis.
10
Installation Guide
In some cases, the extension bracket may have to be modified to
accommodate t he chip circu it ry of th e board before at taching to th e
card.
The bracket mounting screws will be inserted from the back- side
of the card through the card holes. Be sure when attaching the
bracket not to damage any board circuitry.
Using extension brackets and nylon card guides prevents the board
from becoming dislodged from the PCI slot from shipping and
handling.
The use of brackets and card guides also prevents excessive board
"flexing" or "bouncing" due to shipping and handling. Excessive
vibrations and movement can crack or damage circuit board layers
and permanently damage the board.
11
Installation Guide
Cable Installation
1. Back the set-s crews of f fully befo re attachin g the cable. Do n ot
use the attaching screws to “pull” the cable onto the female D
Sub connector of the board.
2. Orient the D Sub on the cable properly and apply slight even
pressure while connecting the D Subs.
3. Secure the Universal Cable in place with the two screws.
4. Attac h the patch cables to the Universal Cable as per the
installation.
NOTE
Apply strain relief as required when attaching patch
cables. The set-screws will easily support the
Universal Cable strain, but will not take into account
the wieght and strain of any connected cables.
12
Figure 5. Cable Installation
Installation Guide
NOTE
The Rackmount Breakout Box ribbon cable assembly
attaches to the board in the same way. Please refer
to the Rackmount Breakout Box documentation for
further details.
13
Installation Guide
14
JUMPER CONFIGURATIONS
The following figures show the d efault jumper settings for the
ReelTime 4 and 4ReelTime Pro board. These jumper settings are
for normal operation. The exception is the voltage jumper. This
jumper ca n be set as follows:
❏Right position: Use 3.3V power on the bus for reduced
power consumption and heat dissipation
❏Left position: Default: Use 5V power on the bus (if the
machine doesn’t have 3.3V.)
Be sure to verify with your system or motherboard manufacturer
for PCI voltage information.
Figure 6. ReelTime 4 (Default) Jumper Diagram
Voltage Jumper (3.3v
selected)
This is the voltage jumper that
may need to be change d.
15
Jumper Configurations
Figure 7. 4ReelTime Pro (default) Jumper Diagram
Voltage Jumper
(3.3v selected)
Starting Playback
Now that your card is installed:
❏Be sure all software applications are closed.
❏Run Vidserve, the playback application located under
Visual Circuits’ programs.
❏Browse to the MPEG file desired and open it.
❏Click Load and wait for the position counter to stop
moving. Then click Play.
For more information on using the Vidserve playback application,
please refer to the Vidserve User Manual. For further
troubleshooting information, see Troubleshooti ng Tips on page 37.
16
EDITING DRIVER SETTINGS
Driver Editing Utility: VccReg.exe
Common Driver Parameters
VccReg.exe is a driver editing utility designed specifically for
editing the VCC4Pro driver s ettings.
NOTE
The driver default settings are used for single board
servers with no adjustments. Because of this the
default settings will not support all server
configurations. RT Daughter card, multiple boards
and other performance settings may be lost. Always
record settings prior to making any changes.
17
Editing Driver Settings
There are four tabs containing different parameters, descriptions of
these parameters, and driver default settings. The four tabs in
VccReg.exe are General, Performance, Audio/Video and Special
and are located on the left side of the window. The right side of
the window contains the Value, Default, Range and Description
fields.
To change a parameter, enter the appropriate information in the
Value field and click the set button . If you want to
restore the default value, click the set to default button
.
18
Editing Driver Settings
General
AudioSync
0 = Video frame drops/adds are used to sync audio and video.
1 = Audio frequency changes are used to sync audio and video.
DSIZEOSD
On-Screen display memory is allocated on the card.
DSIZEOSD > (OSDwidth*OSDheight)/2 + 5
If no on-screen displays are being used, this value may be set to
“0”. This will provide more buffer space when decoding.
Larger buffers increase PAL playback performance. Larger
buffers correspondingly do take longer to load and delays may
need to be increased prior to playing files.
fastload
0 = Fixes audio pop on load; a slight load delay is introduced if
genlock is not available (default for MPEG Plus).
1 = Files load quickly but an audio 'pop' may occur with older
4ReelTime Pro boards.
NOTE
initonopen=0 also fixes this 'pop'
Genlock
0 = Genlock daughterboard is not present.
1 = 4ReelTime Pro with Genlock daughterboard is present.
2 = MPEG Plus board or RT daughterboard is present.
GreenBarFix
0 = May show green on the bottom of overscan monitors.
1 = Eliminates green, but may reduce performance.
19
Editing Driver Settings
InitOnOpen
0 = Files are loaded smoothly without a disturbance to the video
output.
1 = The decod er chip is reinitialized whenever a new file is loaded.
Output is black after load until it plays. Better for cross-channel
sync.
2 = The decoder is reinitialized b ut sync to the display is
maintained by switching to the on board blackburst (RT Daughter
card present only).
Network
0 = The driver cannot read files over the Windows NT network.
1 = The driver can read files over the Windows NT network.
NumberOfChannels
The number of output channels.
OldBoard
0 = Driver will detect whether the board is an RGB (ReelTime 4/
RGB)or a standard model boa rd (4Reel Time Pro). May cause co lor
bars on some 4ReelTime Pro boards to be initiated on startup.
1 = Forces the driver to treat the board as a 4ReelTime Pro board
and should be used with all 4ReelTime Pro cards.
PAL
0 = NTSC (default)
1 = PAL
20
Editing Driver Settings
Performance
AuxSkip
0 = Auto detects additional file playback information such as
picture size, frame rate, bitrate, timeco de, etc.. Most common
setting.
1 = Use videoHSize, videoVSize, and VideoPicRate to set values.
BufferSizePerChannel
Amount of RAM allocated for each channel.
A larger buffer supports larger minimum file reads which reduces
hard drive seeking.
400000 = high performance playback (optimal) recommended.
DmaMode
0 = Normal data delivery mode (backwards compatible).
1 = New data delivery mode (required for API streaming functions
mpgSendMemBuffer, mpgSuppressChi p) .
MaxDisks
This parameter sets the number of disk read threads.
The channels are divided into maxdisks groups, and
each group must play off a different physical drive.
1 = Single MPEG storage drive.
MaxDMA
Sets the maximum data deliv ery size from the syst em memory
buffer to the card.
21
Editing Driver Settings
MaxFileRead
Set the largest file read the driver will perform.
It must be larger than minfileread.
200000 = optimal/recommended.
Setting maxfileread to a half of BufferSizePerChannel is
recommended.
MinDMA
Sets the minimum data delivery size from the system memory
buffer to the card.
2000 = recommended / optimal performance.
MinFileRead
100000 = recommended / optimal performance.
Sets the smallest file read size the driver will manage.
The larger the minfileread is, the less HD seeking there will be.
Setting minfileread to a quarter of BufferSizePerChannel (half
MaxFileRead) is recommended.
NoCache
0 = Normal NT file system caching is used.
1 = The cache is not grown when files are played. Better
performance.
22
Editing Driver Settings
NonPagedPoolSize
Windows NT only.
Reserves a block of memory for decoding.
0 = NT automatically assigns. Usually too low if there are multiple
boards or a large buffer.
Recommended: x800000 where x = number of boards.
When changing No nPagedPoolSize, the system will require
rebooting for Windows NT to allocate memory.
NoReadBuff
0 = Normal file caching.
1 = Disables all hard drive caching. REQUIRED TO BE 1 FOR
WINDOWS NT SERVICE PACK 4 OR HIGHER.
StarveCheck
This is a reserved parameter that should not be changed from its
default value of “0”.
23
Editing Driver Settings
Audio/Video
AudioFreq
0 = AudioFreq, audio frequencies auto detected.
2c = all files are played at 44kHz.
30 = all files are played at 48kHz.
This parameter sets the size of audio memory allocated on the
board.
0 = Automatic.
FrameShift
This para meter adds an offset to the video fr ame relativ e to the
audio track. Positive values are the number of frames to push the
video forward.(e.g. 3 = 3 frame forward). Negative shifts are
represented by the value + 64 (e.g. 67 = 3 frames back).
MaxSyncFix
Sets the maximum audio/video sync correction in units of 90000
decimal per second.
0 = Normal audio operation.
1 = Eliminat es an audio pop that s ometimes occurs when swi tc hing
between audio sources in the genlock module.
24
Editing Driver Settings
Svideo
0 = Comp osite vide o output.
1 = Composite and S-video outputs.
VideoHSize
If non_zero, fix the horizontal pixel number.
Set auxskip=1 if this value is used / not set=0.
VideoPicRate
If non-zero, fix the frame rate to the value.
Set auxskip=1 if this value is used / not set=0.
VideoTypes
0 = S-Video/Composite.
Setting one value determines output for the whole server. If SVideo/Composite video with RGB output is required, refer to the
following table.
NOTE
You can set up multiple boards in a system for
different video type output. A value must then be
set for each card. The first board recognized in the
system's PCI bus will be the furthest value to the
right in the Video Types field. The boards will then
be in order from right to left.
If only composite/S-video or RGB is required for the
whole system, only one value 0 or F is required.
25
Editing Driver Settings
C/S= Composite/S-Video
RGB = RGB output
Channel 1Channel 2Channel 3Channel 4VideoType
s Digit
C/SC/SC/SC0
RGBC/SC/SC1
C/SRGBCC2
RGB RGBCC3
CCRGBC4
RGBCRGBC5
CRGBRGBC6
RGBRGBRGBC7
CCCRGB8
RGBCCRGB9
CRGBCRGBA
RGBRGBCRGBB
CCRGBRGBC
RGBCRGBRGBD
CRGBRGBRGBE
RGBRGBRGBRGBF
26
Editing Driver Settings
Examples:
1 board, all channels RGB
VideoTypes = F
2 boards,
st
board composite video
1
nd
board RGB
2
VideoTypes = F0
2 boards,
st
board channel 1-2 RGB, channel 3-4 S-video (=3)
1
nd
board channel 1-2 composite video, 3-4 RGB (=C)
2
VideoTypes = C3
VideoVSize
If non_zero, fix the vertical pixel number. If a value is entered, it
“hard codes” the video size.
(Set auxskip=1)
If video size is not set to the automatic setting of 0, the AuxSkip
must be set=1 to allow for video size setting.
27
Editing Driver Settings
Special
DSIZEPES
This parameter sets the size of PES memory allocated on the
board.
3000 = Normal operation.
LateLoadNext
Sets the handling of mpgLoadNext calls that arrive after playback
has stopped.
0 = Late mpgLoadNext calls will be ignored.
1 = Playback will always resume (default).
MaxCards
The numbe r of cards to initialize (1-8).
May be set to more than actual number of cards in server.
Recommended setting = 8.
Multiapp
0 = Only one application can link to 4reelapi.dll at a time.
1 = Multiple applications can access the driver, but callbacks are
disabled.
XferSpeed
This sets configuration of the PCI timing (recovery and duration).
0 = 3 PCI clocks
1 = 4 PCI clocks
2 = 12 PCI clocks
3 = 15 PCI clocks
28
MULTI-CARD SERVERS
Multi-Threading and Drive
Mapping
Introduction
Proper drive mapping is crucial for MPEG playback performance.
Fundamentally, this often involves configuring the driver so that it
reads from differe nt physical hard drives simulta neously. In a
system with two MPEG content hard drives, data should be read
from both drives at the same time for maximum performance.
The MaxDisks driver parameter is used to specify the number of
playback storage hard drives used in a system. The driver will
divide the available playback channels into MaxDisks groups and
each group will perform concurrent reads (in software terms, each
group will have a separate ’thread of execution’). Therefore, each
group of channels should read files from a different physical hard
drive. You must configure your application so that MPEGs are
read from the correct drives by the correct channels.
If MaxDisks is left at the default value of 1, reads from all the hard
drives will be sequential. That is, only one read of MPEG data will
be performed at a time. This is normal for a single content drive.
However w ith multiple drives, a read from on e drive will have to
be completed before a read on another drive can be initiated. This
situation does not take advantage of the performance potential of a
multi hard drive system.
It is actually permissible that a channel group reads from a set of
physical hard drives, as long as none of the drives in the set belong
to another channel group. This is beneficial if the MPEG files will
not all fit on a single drive. For simplified mapping, it is
recommended to divide the numbers of channels evenly and
sequenti ally across multiple boards.
29
Multi-Card Servers
Drive Mapping: Examples
Be sure to follow the drive mapping fundamentals for multiple
board systems. The following examples provide some basic
information:
NOTE
File bitrates impact system hard disk and
playback performance. Sample bitrates are
provided with each of the following examples.
File bitrates are expressed in mbps (mega
bits per second).
4 Channel Systems:
4 Channe ls, each with a 6 mbps file (single IDE drive, C:\,
partition with Windows NT and application software only 700900MB in size. The remaining drive space is used for content
storage in a second partition D:\.
Channels 1-4 are mapped to drive D:\
(Default: Ma xDisks = 1)
4 Channe ls, each with a 8 mbps file (single SCSI)
Channels 1-4 are mapped to drive D:\
(Default: Ma xDisks = 1)
NOTE
The next set of examples reserves the IDE
drive for the operating system and software
applications only. Content (MPEG files) is
stored on SCSI drives.
30
Multi-Card Servers
8 Channel Systems:
8 Channe ls, each with a 8 mbps file ("8X8") .
Channels 1-8 may be mapped to a single SCSI drive.
MaxDis ks = 1.
If two SCSI disks are used:
Channels 1-4 are mapped to drive D:\
Channels 5-8 are mapped to drive E:\
Set MaxDisks = 2.
If two sets of disks are used (total of 4 SCSI drives):
Channels 1-4 are mapped to D:\ & E:\
Channels 5-8 are mapped to F:\ & G:\
The setting MaxDisks remains = 2.
12 Channel Systems:
12 Channels, each with a 8 mbps file ("12X8")
With 2 SCSI hard driv es--(Max Disks = 2)
Channels 1-6 are mapped to Drive D:\
Channels 7-12 are mapped to Drive E:\
or
with 3 SCSI hard drives--(MaxDisks = 3)
Each board is mapped to an individual drive
Board 1 to Drive D:\
etc.
16 Channel Systems:
16 Channels, each with a 8 mbps file ("16X8")
Channels 1-8 are mapped to SCSI drive D:\ (boards 1 & 2)
Channels 9-16 are mapped to SCSI drive E:\ (boards 3 & 4)
Set MaxDisks = 2.
To calculate the number to be set for MaxDisks, divide the number
of channels by the number of drives. If there are any channels
remaining, map them to the last drive. Be sure there are no
channels “cross-mapped” within a specific mapping configuration.
31
Multi-Card Servers
32
TROUBLESHOOTING OVERVIEW
NOTE
Only authorized technicians should perform board
troubleshooting or system repairs. Unauthorized
repair of systems may void warranty.
Server Setup Check
Prior to any troubleshooting, power down the system and be sure
that the card is properly installed in the system’s PCI slot. Test
only one card in the system at a time.
❏Confirm that the system has the power connected properly.
❏Confirm that all video and audio cables are connected
properly. (Remember video playback occurs with standard
TVs and monitors but not on a PC monitor.) Select the
correct input type for the display. Examples: Video 1,
Input 1, Svideo, etc. Refer to the display manual for use.
❏Remove all serial cable and network connections from the
system.
Refer to the cases located in Troubleshooting Tips on page 37 at
any time during this process.
Getting Started
1. Power the server up and open Vidserve playback application
located under Visual Circuits programs. (For detailed
instructions on using Vidserve, please refer to the Vidserve
User Manual.)
33
Troubleshooting Overview
Figure 8. Vidserve Playback Application
On the main application window, the radio button selected should
indicate Card 1 found. If it states “VCC4Pro driver not found” see
page 37 for tips on how to fix the error.
2. Next, select Color Bars on the main window. In Composite
and Svideo modes, color bars should be visible. In RGB mode,
color bars will appear incorrectly due to syncronization
requirements, though a co lor bar repr esenta tion should appea r.
If the board indicates activity, the driver is installed and the
card is initialized. If no output is seen, double check displays
and cables. If there is still no output, power the server down
and repeat the initial server check up and color bar test.
3. With color bars visible, select Black on the main window.
Displays should go to black.
NOTE
This ''Black'' does not generate a video output signal
to the displays.
4. Be sure Auto Play and Black are not selected. Using the
Browse b utton , select a f il e for channe l 1 and clic k Open. Note
the Position window and see that the counter has stopped
increasing. Next click the Open button for channel 1 and be
sure that the position counter resets and does not increase.
34
Troubleshooting Overview
5. Next, click Play for channel 1 and view video and audio
playback.
6. Repeat the process for each individual channel by browsing,
opening and playing files. Be sure to play only one file at a
time.
By performing the above process, you can determine if basic
playback for the board is functioning.
For detailed use of Vidserve or for cross-channel playback
applications, please refer to the Vidserve User Manual.
35
Troubleshooting Overview
36
TROUBLESHOOTING TIPS
BIOS Settings
Ensure BIOS settings for Windows NT servers have the “Non PnP
OS” selected.
Blue screen
❏If a Blue Screen occurs dur ing NT startu p and NT cannot be
started, remove all devices from the system and reboot.
❏Try a process of elimination to run the system in a single
minimal system configuration, such as by inserting each
device i n to t he system and reboot ing. Usually st ar ti ng with
the VGA/AGP card if not on board.
Message says ''VCC4PRO Driver not found!''
when Vidserve is started
❏"4-ReelTime: board was not found"
Make sure the board or boards are securely seated in the
PCI bus.
❏"ReelTime 4: Failed to allocate mem "
Be sure and ver ify defaul t performan ce settin gs in VccRe g.
Verify all memory is detected by server on start up or by
right clicking on My Computer and reviewing General.
❏"ReelTime 4: HARDWARE ERROR"
Inspect th e decoder b oard for damage. Also review the
voltage of the server’s motherboard. The 3.3v setting is the
default jumper for VCC dec oder bo ards a nd may ne ed to be
changed to 5v as required. Refer to jumper settings fo r the
board being used.
37
Troubleshooting Tips
No video or audio output
❏Using Vidserve, check the box titled COLOR BARS and
observe if color bars appear on the output.
❏First, ensure that the cable or breakout box is plugged in
properly and tha t the video and audi o outputs are pl ugged in
correctly to the display device. Try testing another channel
of the serv er on t h e same d is p la y. Try us ing other cables or
breakout boxes.
❏Verify the jumpers on the board.
NOTE
You may need to reference the RT Daughter
card document for RT Daughter settings.
❏Note that the o utput of the decoder board will not disp lay on
a PC monitor.
Stuttering files during Playback
Irregular playback on single and multiple channels can be caused
by a number of conditions:
❏Uneven audio to video track lengths: Confirm the length of
the audio track to the length of the video track. The Visual
Circuits VCC4PRO driver , sta ndard wit h all Visual Circuits
boards and digital servers, aggressively synchronizes the
audio and video data of the MPEG file to maintain Audio/
Vi sual (AV) Sync. If the MPEG file’s audio and video
tracks are uneven in length, the driver’s attempt to
synchronize these uneven tracks will result in poor
performance. Mismatched AV track lengths will result in
overall degradation of system performance. Often a "bad"
file will cause uneven or stuttering playback on other
channels of the system as well.
38
Troubleshooting Tips
❏Video only MPEG files played on the same channel as
MPEG files with video and audio data: Confirm that all
files on a particular channel are either video only, audio
only, or audio/video files. It is recommended to have a
"blank" audio track encoded with all MPEG files--even if
no audio is present on the source material. This allows
system flexibility when adding fut ure MPEG files.
❏The bit rate of the MPEG files being played exceed the
system capabilities: The Visual Circuit MPEG decoder
boards and digit al ser v ers al l ha v e a maximum su st ained bi t
rate that can be delivered. Refer to the system board and
specif ications for info rmation. Al way s, consult your Visual
Circuits representative prior to encoding or designing your
installation if there are any questions.
❏Unequal elementar y streams/uneven video or audio trac k s.
Cross channel synchronization requires equal playback
duration and similar timecode starting points of MPEG
files: For cross channel sync all MPEG files must have
equal playback duration. If in a synchronized group of
channels, files vary in length, the driver will attempt to
synchronize these unevenly matched files and cause
"stuttering". It is also recomme nded to encode files with
equal bit rates whenever possible and files lengths that are
exact. Also the starting point of each MPEG’s timecode
must be th e same.
NOTE
Using the timecode provided on the original
source type may not provide the same
timecode starting point for each MPEG file.
Consult your encoding manufacturer's
documentation for information on providing
the same start point for each MPEG encoded.
39
Troubleshooting Tips
❏Incorrect channel to drive mapping in multiple card systems
with multiple content drives. For more information see
“Multi-Card Servers” on page 29.
"Latent Images" or "Flashing" during
playback
❏Incorrect source timecode provided or improperly closed
encoding session. If the incorrect timecode for a file on
tape is given, it is possible to encode a frame or two of
trailer or header inf ormation f r om the tape. Often this
"extra" fr ame may be seen only br iefl y and may appea r as a
visual "flash" on the screen during looping playback.
Review the original source material and determine if th e
timecodes ar e correc t for t he t ape, or i f the encoding s essio n
was actually started and closed on the cor r ect frames .
❏Playing MPEG 1 and MPEG2 files back to back: The
resolution sw itch fr om MPEG 1 f iles (342X240) to MPEG2
files (720X480) causes a "latent image" or a "quadrant
display" of the last played file's image. The only way to
perform seamless playback when using a playlist of files is
to insert an encoded "black file" with blank audio track,
between MPEG 1 and MPEG 2 files. The black MPEG fil e
preceding the play back f ile should be of th e same standard.
In other wo rds, prior to an MPEG 1 file the "black file",
with a blank a udio track, shou ld be MPEG 1 and vi ce versa .
Changing the driver parameter "InitOnOpen" to "1" may
also remedy this problem, as long as back to back
"seamless" playback is not des i red. Each file must be
"loaded" individually prior to playing. (You can use the
40
Troubleshooting Tips
Visual Circuits Driver editin g utility "VccReg.exe" for
changing this parameter.) However, testing should be done
with this driver setting, as with all parameter changes, to
verify the overall effect on the pre sentation . Testing is
especially important in regards to cross-channel
synchronization. Incorporating a delay between files or
calling th e "mpgblack" command , which is actually a
function call on the decoder card, will not solve the
problem.
SMPTE time codes are not recognized
properly
❏Some SMPTE tracks lose information during compression
and may not "trigger" events as required. It is
recommended to encode these tracks "hot", adding
approximately +6 db t o the tr ack while encoding . Testing is
essential to account for variances in encoders and SMPTE
devices involved.
NOTE
Simple audio filters, used at the installation
site, are also useful in eliminating "noise" and
cleaning up the SMPTE signal.
41
Troubleshooting Tips
On Screen (GIF) Overlay Information
Graphic Interchange Format (GIF) files are created with standard
graphics authoring programs. The following are basic creation
guidelines and playback tips:
1. The width, or "X" axis, of the GIF’s resolution must be a
multiple of 16 pixels.
2. GIF must be 16-color non-interlaced format. A palette of
exactly 16 c olors (any col ors) can be used.
3. Animated GIFS are not supported.
4. The GIF file should not go off the edge of the screen.
5. There must be an MPEG fi le underneath the GIF in order for
the GIF to display properly. The MPEG does not have to be
playing.
6. MPEG files using a GIF overlay, should be a minimum of 8
seconds in duration to ensure properly timed GIF display.
For further GIF creation tips and GIF display troubleshooting
information refer to the "On-Screen Display Guideline s"
document.
NOTE
These guidelines serve only as
recommendations and by no means represent
technical data pertinent to any specific
encoding device or process. It is
recommended that prior to beginning any
encoding project, sample files are played
back on the systems to be used to ensure
proper display quality. Visual Circuits does
provide encoding services. Visual Circuits
cannot guarantee any third party encoding.
42
Troubleshooting Tips
Video blocks or stutters when starting
playback
❏Be sure buffers are fully loaded before calling a playback
command. Usually follo wi ng the initial buf fer load, a delay
is required.
Overall blocky or distorted playback
❏Make sure the file is not a transport stream. These files
typically have a .m2t extension. Visual Circuits MPEG
decoders do not support transport stream files.
❏Try p layin g another f il e or a Visual Circuits demo f ile t o see
if the prob l em is specific to a file. If so, th e data may be
corrupt.
❏Make sure that NTSC is not being played to PAL or vice-
versa (the vertical resolution is 576 in PAL and 480 in
NTSC).
❏Check that M2Ps (program files) and M2Vs or M2As
(video or audio-only files) are not mixed on the same
channel.
❏Possible damage or faulty ch annel or decoder card. Use test
files and try other channels to verify. Always try one file
and one channel first as a base line for troubleshooting.
❏Verify ATA 66 to ATA 33 compatible components and
drivers. A different IDE bus driver may be required for
proper system performa nce .
Poor Onscreen Display (GIF) overlay
❏Refer to the "On-Screen Display Guidelines" document for
details.
Problems using the API
❏Make sure you are us ing t he stand ard C call ing co nvention.
Refer to the SDK documentation for questions.
43
Troubleshooting Tips
Mouse lags and overall poor system
performance
❏Verify ATA 66 to ATA 33 compatible components and
drivers. A different IDE bus driver may be required for
proper system performa nce .
MPEG will not play on mapped network drive
❏This will not work unless you set network=1.
Vidserve does not work at all
❏Only one program can access the driver at a time. Close all
programs using the VCC4PRO driver and run Vi dserve
again.
Monitors roll / lose sync when files are
loaded
❏Set InitOnOpen to 0 and test. A blackburst or external
display sync source may be required. Consult your Visual
Circuits representative for details on RT Daughter card
options.
All channels pause when a new file is
started on a channel
❏Be sure buffers are fully loaded prior to playing. As the
number of channels being used increases, this delay may
need to be increased dependi ng on indivi dual server syst em
resources. Test with maximum channels playing to
determin e the system’s threshold and maximum delay
required.
44
Troubleshooting Tips
No audio
❏Make sure mute b utt on is not checked.
❏Check cables and test with other audio source.
❏Be sure not to mix audio only, video only or files with both
audio and video on the same channel.
More than one board will not play or make a
few horizontal lines on the screen
❏Make sure BIOS is not set to PnP operating system.
❏Verify number of boards and number of channels using
VccReg.exe driver editing utility.
RGB Sync or scan line noise
In some installations with sensitive projectors or with long cable
runs, you will notice noise or rolling scan lines. Usually
installations where all 4 channels of a board play back
independently, is more likely to experience this behavior. This is
due to a separate syncronization output for each channel.
❏Verify connect ors, routers , line doubler s and other ha rdware
to be sure that the 75 ohm impedance of the run is not
broken.
❏Confirm cable lengths to signal strength. Visual Circuits’
products conform to standard audio visual standards. If
unsure, consult with the hardwa re manufacturers for
equipment specifications.
❏Be sure that all equipment is properly grounded. Also be
sure all cabling is properly shielded and avoid running
cables across or through other equipment or cabling where
noise may be introduced.
❏RT Daughter Card us e: RT Daughter cards when attached
to the ReelTime 4 baseboard, will synchronize the outputs
of all channels to the same scan rate. This may also
eliminate errant line noise. Consult with your Visual
Circuits representative for details on this option.
45
Troubleshooting Tips
46
CONTACTING VISUAL
IRCUITS CORPORATION
C
Contacting Technical Support
If you are experiencing problems with the ReelTime 4 or
4ReelTime Pro boards, consult Troubleshooting on page 30 and
the support infor mat ion a vai lable at www.visualcircuits.com firs t.
If you need further assistance, please contact your Visual Circuits
Value Added Reseller or Distributor.
What You Should Have Ready
When You Call
Before you call your supplier for support, collect the following
pieces of informat ion:
❏The serial number of the ReelTime 4/Pro board.
❏The date of purchase of the unit.
❏The name of the distr ibutor or sales representat i v e who sol d
the unit.
❏A complete descri ption of th e problem wit h a descript ion of
its use. Example : Multip le cha nnel sy nchroni zed pl ayback
with serial control device.
47
Contacting Visual Circuits Corporation
What You Can Expect When You
Call
As a Value Added Reseller or Distributor, you may contact Visual
Circuits technical support. Your call will be handled in the
following manner:
1. A technical suppor t repr esent ati ve will record severa l piec es of
information (see What Y ou Should Have Ready When You Call,
above).
2. The representative will attempt to resolve your problem.
3. If your problem is too complex to be resolved during your
initial conversation , the representative will arrange for you to
be called back at a later time. You will re ceive an inquiry
number that you can use to refer to your problem in the future.
NOTE
After regular business hours, the technical
support representative will always arrange for
you to be called back the next business day if
your problem is unresolved.
Technical Support Contact
Information for the Value Added
Reseller (VAR) or Distributor Only
The e-mail address for Visual Circuits technical support is:
❏techsupport@visualcircuits.com
The telephone numbers for Visual Circuits technical support are:
❏In the United States, 1-800-250-5533
❏Outside of the United States, 763-571-7588
48
Contacting Visual Circuits Corporation
Returning Materials to Visual
Circuits Corporation
If the ReelTime 4/Pro board has problems that cannot be corrected
over the telephone by Visual Circuits technical support, you may
need to return the ReelTime 4 b oard to Visual Circuits
Corporation. All materials shipped back to Visual Circuits
Corporation must be accompanied by a Return Materials
Authorizatio n ( R MA) number. A Visual Circuits techni ca l support
representative will provide you with an RMA number. Please
write the RMA number clearly on the shipping label.
49
Contacting Visual Circuits Corporation
50
APPENDIX
Hardware Specifications
PHYSICAL
DESCRIPTION
Dimensions:Length = 12.24''
Height = 4.2''
Connector:25pin DSUB for use with breakout
cable or rack-mount box
40 pin connector for optional genlock
daughtercard
POWER
All four
channels
active = 2.6
amps @5VDC
AUDIO PARAMETERS
Sampling rates
supported:
Frequency
response:
MPEG layer 2 audio
Stereo 16 bit output
3.3v may be optionally selected with
a jumper on the card. In this case, the
5V power requirement drops by 1.2
amps and this power is instead drawn
from the 3.3v supply. The advantage
of using the 3.3v supply is that 2.1
watts are not dissipated as heat by an
on-board regulator.
32khz, 44.1 khz, 48khz
20hz - 20khz +/- .5db
51
Appendix
Tone, volume, balance software controllable with
optional genlock module
Software controllable mute
Software controllable stereo channel routing (mono, dual
mono, right or left, etc.)
Audio output
level:
Reproduces encoded audio level up to
3.75v
p-p without clipping. 1-volt p-p
typical for line level.
Audio output
620 ohms/unbalanced
impedance:
VIDEO PARAMETERS
Frequency
0 to 4 MHz +/- .3 db
response:
Differential
3% maximum
gain between
DACs:
Signal to noise
62db
ratio:
Color burst
40 IRE +/- 2IRE
amplitude:
Sync
amplitude:
Output level
composite
video:
Output level
RGB (RT+):
52
40 IRE +/- 2 IRE
1 volt peak-to-peak when terminated
with 75ohms
.7v peak-to-peak when terminated
with 75 ohms
Appendix
Output level
H/V composite
sync for
TTL level negative-going composite
sync
(H and V)
RGB (RT +):
Standards:NTSC or PAL software selectable
Encoder:Broadcast quality digital video
encoder with post filtering
Resolution:CCIR 601 720x480 NTSC or 720 x
576 PAL Driver supports automatic
selection of SIF format for MPEG1
Closed caption
Supported in hardware
support:
STANDARDS SUPPORTED
ISO 11172 (MPEG-1)
ISO 13818 (MPEG-2)
Maximum
bitrate:
Individual channel can play up to
15mbps. Maximum data transfer rate
to card is 5.5 Mbytes/sec (44mbits/
second - total per card).
Decodes audio-only, video-only or program streams file
formats. No transport stream.
53
Appendix
HARDWARE
LSI LOGIC 64002 MPEG2 decoder with 2mb DRAM buffer
per channel
Zoran ZR36120 PCI bridge
STV0117 digital video encoder
BUS INTERFACE
Conforms to PCI-bus electrical specifications 2.1.
Operates in bus master mode. Can make use of 3.3v if
available on bus
Uses INTA line
ENVIRONMENTAL
Ambient
Operating: 0 deg C to 40 deg C
temperature:
Non-operating: -40 deg C to 60 deg C
SYSTEM REQUIREMENTS
Minimum
486 100MHZ
processor:
Minimum
32M (64M recommended)
system
memory:
Hard disk:Driver will play four 6mbit/sec files
from one IDE driver. Higher
performance is achieved with ultra-
wide SCSI drives.
54
Appendix
Audio Video Breakout Cables
For all cables, 75-ohm cable is recommended for all video outputs
and inputs if applicable. The challenge to making cables for RGB
and Daughter Card (Genlock) decoder boards is the number of
wire leads required. In these instances, 24 of the 25 pins available
are used and often do not feed into standard D Sub shells.
When attaching the leads, solder cup connectors work fine, but
crimp type pins provide more durability and hold up better under
strain. An example of a cable that works well for vide o is Belden
series 9221 mini-coaxial cable, but other cable manufacturers can
also be used. Audio lines need to be quality audio wire.
NOTE
Visual Circuits does not sell or stock cable-building
supplies or components. Visual Circuits also does
not stock patch cables or related accessories.
Please contact an Audio/Video specialist for
assistance.
Ensure that all leads are properly grounded within the D Sub and
that proper strain relief is provided to prevent separation of wires
from the pins or connectors. Also ensure that all connectors,
whether BNC, RCA, or other are of high quality material so as not
to break the 75-ohm impe danc e of t he li ne. Also ensure all display
devices are properly grounded to maximize signal strength. Refer
to the following chart for pin-out connections.
55
Appendix
PIN-OUT CONNECTION TABLE:
Pin No.
1
2
3
4
5
6
7
*ReelTime Plus
GROUNDGROUNDGROUNDGROUND
-BAL RIGHTAUDIO
VERT SYNCCOMP
RTDaughter
AUDIO OUT L/4
COMP OUT 4
AUDIO INR/4
OUT L/3
OUT 3
AUDIO INL/3
Composite& SVideo
AUDIO L/4AUDIO L/
COMP 4BLUE 4
LUM 4GRN 4
AUDIO L/3AUDIO L/3
COMP 3BLUE 3
LUM 3GRN 3
RGB
4
8
9
10
11
12
13
14
-BAL LEFTAUDIO OUT L/2
H SYNCCOMP
OUT 2
AUDIO INL/2
AUDIO OUTL
COMP/BLUE
LUM /GRN *AUDIO IN L/1
AUDIO OUT L/1
COMP OUT 1
AUDIO INL/1
COMP IN4
AUDIO L/2AUDIO L/2
COMP 2BLUE 2
LUM 2GRN 2
AUDIO L/1AUDIO L/1
COMP 1BLUE 1
LUM 1GRN 1
SYNC 4
56
Appendix
Pin No.
15
16
17
18
19
20
21
*ReelTime Plus
+BAL RIGHT
COMP SYNC
+BAL LEFTAUDIO
RTDaughter
AUDIO OUT R/4
AUDIO INL/4
COMP IN3
AUDIO OUT R/3
AUDIO INR/3
COMP IN 2
OUT R/2
Composite& SVideo
AUDIO R/4AUDIO R/4
CHROMA4
AUDIO R/3AUDIO R/3
CHROMA3
AUDIO R/2AUDIO R/2
RGB
RED 4
SYNC 3
RED 3
SYNC 2
22
23
24
25
AUDIO INR/2
*COMP IN COMP IN
1
AUDIO OUTR
CHROMA/RED/*AUDIO IN R/1
AUDIO OUT R/1
AUDIO INR/1
CHROMA2
AUDIO OUT R/1
CHROMA 1RED 1
RED 2
SYNC 1
AUDIO R/1
57
Appendix
Theory of Operation
(See Block Diagram of Board on page 60 for the following
description)
The board consists of a PCI bus-mastering bridge chip and four
identical MPEG2 decoder channels. The key to understanding the
operation of the board and the driver is to understand the buffer
management. There is a small FIFO buffer in the PCI bridge chip
to allow for PCI bus latencies, a buffer allocated by the driver in
host memory dedicated to each channel, and a buffer on the board
for each channel. The memory buffer on the board is divided into a
not-yet-decoded raw data section, a section for the decoded video,
and a section for the decoded audio (often referred to as the
payload buffers). There is also a section for the OSD data, and an
optional VBI data area. The rest of the memory is taken up by a
combination of decoding and display areas. This is where the
picture is reconstructed and displayed. All these memory areas are
defined in the software. The data and payload memory are circular
buffers, and the driver reads these pointers into these buffers to
determine how much data the channel needs. The minimum and
maximum size of data delivered to the data buffers are set as a
driver parameter.
When a file is loaded, da ta is transfe rred from the disk into th e
memory buffer for the channel and into the memory data area on
the board (until it is full). When a start command is issued, the
data is demultiplexed and transferred into the payload areas.
Reconstruction and display begin after a few frames are received.
From then on, the driver moni tors th e state of the data buf fer on the
board for each channel, decides which channels most needs to be
fed data, and transfers a portion of data from the host memory
buffer to the data buffer for that channel. Only one channel at a
time can be serviced. The data transfer rate is fixed at 5.5mbytes
per second. The data buffer “drains out” at a speed dependent on
the bitrate of the file .
58
Appendix
There is no explicit end-of-file detection by the decoder chip. It
will continue to decode and display data once it is initialized, and
provided there is no need to change initialization para meters (such
as the display resolution), there will be seamless transitions
between files.
For more detailed operation, refer to the Zoran ZR36120 manual
for the PCI bridge specification, the LSI LOGIC 64002 manual for
operation of the MPEG2 decoder, and the SGS THOMSON
STV0117 manual for the video encoder IC STV0119 for RGB.
59
Appendix
Figure 9. Block Diagram of Board
SCSI CONTR O LL E R
HOST MEMORY BUFFER CHANNEL1
HOST MEMORY BUFFER CHANNEL2
HOST MEMORY BUFFER CHANNEL3
HOST MEMORY BUFFER CHANNEL4
8X32 BIT
FIFO
BUFFER
PCI
LATENCY
BUFFER
PCI BRIDGE
BUS MASTER
HARD
DISK
2 MBY TE B U FFE R
STORES M P EG RAW
DATA, DECODED DATA,
AND PICTURE DISPLAY
BUFFERS)
MPEG2
DECODER
AUDIO AND
VIDEO
VIDEO AND
AUDIO DACS
Figure 10. Block Diagram of Decoder Chip Buffers
DATA BUFFER
STORES RA W
(NON-DECODED)
DATA DIRECTLY
FROM FILE
AUDIO PAYLOAD BUFFER
STORES UNDECODED AUDIO
DATA
VIDEO PAYLOAD BUFFER
STORES UNDECODED VIDEO
DATA
PES BUFFER
STORES PRO GR A M STR EAM
INF ORM A T IO N
AUDIO DECODER
VIDEO DECODER
60
Appendix
How to Build a Server
The following general guidelines are for systems built solely for
the purpose of displaying digital video using Visual Circuits
decoder boards on a Windows NT Works tation op erating p latform.
Systems running multiple devices and software programs may run
smoothly with Visual Circuits decoder boards. However, due to
the short life cycle of components and the emergence of new
products there is alw ays the pos sibility of incompatibility.
Thorough testing should be done on all components during the
integration process. Contact your Visual Circuits representative if
server integration consulting support is required.
Motherboard
Visual Circuits is not aware of any incompatibilities with specific
motherboards. It is adva nta geous to have a BIOS, which allows for
manual setting of which interrupts are assigned to specific PCI
slots. While interrupts may be shared, it is better to avoid sharing
an interrupt with a device such as a SCSI controller. ATX
motherboards shou ld be used so as t o enable th e insta llat ion of four
full-leng th PCI cards.
Memory
Single Channel systems: 64 MB RAM: 4 channel systems (single
board) 96 MB RAM; SCSI systems up to 16 channels: 128 MB
RAM.
Processor (CPU)
All servers currently run only under single CPU support. For 1-8
Channel systems Socket 7 (Pentium) based 300 MHz or higher.
For servers up to 16 Channels PII 350 MHz or higher.
61
Appendix
Hard Disks
Servers run ning 1- 4 c hannels req uire on ly a sing le IDE disk dr ive.
NT Workstation is installed on the first partition of the disk in C:\
using approximately 800 MB of disk space. (This amount of disk
space is recommended in order to perform future software
upgrades to NT or other applications. Playback software and
drivers req uir e o n ly mini mal di sk space >10MB.) The par ti t ion for
MPEG file storage and playback can then be created with the
remaining disk space. Systems with 5 channels and above require
SCSI drives for content storage and playback. Disk transfer rates
(seek time) can be a limiting factor depending on the number of
channels used and the data rate (bit rate) of th e files to be read.
SCSI controllers can be on board (imbedded in the motherboard)
or in the fo rm of an adapter card taking a PCI slot. Make sure that
the transfer rate of the hard drive is set to 40mbytes per second in
the BIOS and that the w i dth is set to 16bits (Wide SCSI). This is
sometimes called SUPPORT FOR UTRA SCSI SPEED
ENABLED. The default setting for this value is often incorrect.
LVD SCSI drives allow for the length of the SCSI cable to be
extended and provide a clearer data transfer mode. However, with
LVD drives some swap bay cartri dges and ter minato rs may need to
be upgraded.
Chassis
With multiple cards in the system, it is important to have air
moving over the cards. Card guides and brackets ensure that
impact on the shipping container does not dislodge the cards from
their slots.
62
Appendix
Tuning Multiple Board Servers
The VCC4PRO driver automatically handles multiple boards for
the system, depending on the driver version. The standard driver
will support 4 boards but drivers for more than 4 boards are also
available.
NOTE
Due to specific driver parameter settings,
4ReelTime Pro and ReelTime 4 boards cannot
be integrated into the same system.
Systems with 4ReelTime Pro boards require a
driver parameter setting: oldBoard = 1.
Systems using ReelTime 4 boards require:
oldBoard = 0.
If RGB output is required on any channel of an individual system,
the entire system must be assembled with ReelTime 4 boards. The
video output t ype of e ach cha nnel may be s elected a cco rdingl y. For
more information see “VideoTypes” on page 25.
Visual Circui ts d eco der cards may share in ter ru pts with each other.
It is also possible for the cards to share interrupts with other PCI
devices in the bus, such as a SCSI card. You will have to test to
see which ReelTime 4 board is assigned by the BIOS to be ‘first.’
Normall y, the card on the left (looking at motherboard from
behind) is card 0. The order then will always the same each time
the PC boots, unless a device is added or removed.
Each 4-ReelTime board requests and then receives data over the
PCI bus at a fixed rate of 5.5 megabytes per second. With multiple
boards in a system, the 5.5-megabyte transfer rate for each board
can essentially be performed in parallel with the other boards.
Tuning the system involves managing the buffers in the multiple
channels. As the decoder drains the data from the channel buffer
on the card, the driver must detect which channel is requires the
most data.
63
Appendix
The driver will examine the status of the channel buffer data
pointers 200 times a second (this is a parameter, which may be
changed). If the MinDMA is set too small, then there will be a lot
of requests for small amounts of data, which can cause too much
overhead. If the MinDMA is set too big, then a channel may starve
because it may b e t oo close to starvi ng be fore it can get se rviced. If
the MaxDMA is set too small, then system performance will
decrease becaus e of the ove rhead in vol ved, and if i t is set too la rge ,
then other channels may starve because one channel takes too long
to service .
The min and max file read size is also critical for optimizing the
seek time . If the minfileread is s et too small, then the disk seek
time will become too great a percentage of the disk access time. If
it is set too high, then the channels will not be serviced often
enough.
These parameter settings have been found to give the best
performance playing multiple high bitrate files off of a single
drive:
❏Publication number went from 50023c to 813-0001a.
❏New sketch art added.
❏Trouble shooting section expanded.
❏4ReelTime RGB and ReelTime 4 are the same produ ct , i t is
a name change only.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.