VIDEOLOGIC CAPTIVATOR RELEASE 1.0.3 - README FILE
=================================================

This README file contains the following sections:

1. Documentation errata
2. Troubleshooting
3. Playing back YUV files on other PC systems
4. Removing the Captivator software


1. Documentation errata
-----------------------
Page 5: The minimum possible video size is 32 (width) x 24 (height), not 32 x 32.

Page 37, paragraph 4, VideoSnap: You cannot save an image in 16- or 24-bit format and then create a palette from the image afterwards. Similarly, applying a palette to a 16- or 24-bit image will not convert it to 8-bit.


2. Troubleshooting
------------------
The following issues are covered in this section:
	- Problems when installing Captivator
	- Grainy or Low Quality Color Live Video Window
	- Corruption of Capture File Name in VidCap
	- Philips Videodisc Color Lock Problem
	- Monochrome Live Video
	- Poor Mouse Response in VideoSnap
	- Momentary Loss of Video
	- VidEdit "A frame of this file..." Warning
	- Limit of 20 16- or 24-bit Windows in VideoSnap
	- Compatibility with VideoSnap's 16-bit DIB files

*       Problems when installing Captivator
	===================================
When you install the Captivator software the installation program checks to see whether any of the I/O addresses suitable for Captivator are being used by other cards or peripherals. However, certain cards and peripherals can cause PC systems to crash when their I/O address is read.

These peripherals include:

	NOVELL NE2000 Ethernet Card
	Intel i596 based Ethernet Products
	MediaSpace Video Compression Card

Solution :
During a "Standard" installation, you are informed that a scan is about to be made. If the PC crashes at this point, run Setup again choosing "Custom" installation.

During "Custom" installation you can select which of Captivator's four possible addresses are to be scanned. If you know the I/O addresses of any peripherals (including motherboard sound or networking hardware) in the PC, these addresses should be unchecked. If Setup has been run previously and crashed when scanning an I/O address, this address will be grayed out when Setup is run a second time.

The automatic interrupt (IRQ) scan that Setup performs is usually accurate. However, it is possible that Captivator's interrupt setting (IRQ) conflicts with another board. In this case, the suggested IRQ value can be overridden using the VideoLogic Captivator Capture Driver configuration dialog (accessed through Drivers in the Windows Control Panel)

Captivator may not install properly if another Video for Windows video capture card is, or has been, installed on your PC. Remove all such hardware and any associated drivers before installing Captivator. These drivers can be accessed through Drivers in the Windows Control Panel.

*       Grainy or Low Quality Color Live Video Window
	==============================================
This could be due to one of two things:
1. Running in 16- or 24-bit Captivator image format whilst having only an 8-bit Windows display driver
2. Running Windows in 16-color mode.  
Solutions:
1. If possible, increase the number of colors your graphics card displays to match or exceed the number of colors in your Captivator movie (consult the documentation supplied with your computer or graphics card to see how to do this). If your graphics card is only capable of displaying 256 colors (an 8-bit display), changing your Captivator image format to 8-bit will improve the quality of your movie. However, the movie will be monochrome until you select a palette.
2. Increase the number of colors your graphics card is displaying (consult the documentation supplied with your computer or graphics card to see how to do this). We recommend that you use Captivator with a display that has at least 256 colors.

*       Corruption of Capture File Name in VidCap
	=========================================
This problem occurs if version 1.0 of Microsoft's Video for Windows VidCap is used.  
Solution: Install version 1.0c of Video for Windows, which is supplied with Captivator.

*       Philips Videodisc Color Lock Problem
	=====================================
With certain Philips Videodisc players, 'green flashes' and other video artefacts can be seen with Captivator. This is due to slight incompatibilities between different Philips components.
The problematic Videodisc Players are: VP310, VP312, VP380.

*       Monochrome Live Video
	=====================
Video for Windows' default 8-bit palette is grayscale. In Captivator's 8-bit image format, live video will be monochrome until you capture a different palette.
Solution: Capture a palette, or change Captivator's image format to 16- or 24-bit.

*       Poor Mouse Response in VideoSnap
	================================
If you experience poor mouse response when displaying large 24-bit images, try scaling them to 1:2 or 1:4 using Preferences from the Options menu.

*       Momentary Loss of Video
	=======================
A poor video source may cause occasional, momentary loss of video. You can counteract this by turning off Captivator's Auto Detect in the Video Source dialog.

*       VidEdit "A frame of this file..." Warning
	=========================================
When you save a YUV (or 8-bit) movie to a new filename in VidEdit, you may get the warning, "A frame of this file is too big to fit using the current data rate. Continue with an increased data rate?". Click OK; this will not affect your movie.

*       Limit of 20 16- or 24-bit Windows in VideoSnap
	==============================================
This is a limitation of the Windows DIB driver.

*       Compatibility with VideoSnap's 16-bit DIB files
	===============================================
VideoSnap uses the new Microsoft extended DIB format (RGB555) for 16-bit DIB files which is not, as yet, supported by a number of popular applications.

3. Playing back YUV files on other PC systems
---------------------------------------------
To play back a file in VideoLogic's YUV format on a system which does not have a Captivator installed you must install the Captivator software capture drivers.  Run Setup from the Captivator diskette, choose "Custom" install, and check only the "Install Captivator capture driver" option.

4. Removing the Captivator software
-----------------------------------
To remove the Captivator software, you delete the files copied to your hard disk and undo the changes made to SYSTEM.INI by the Captivator Setup program. DO NOT delete the file SYSTEM.INI. 
Listed below are the files copied to your hard disk, and the changes made to SYSTEM.INI by "Standard" install. If you chose "Custom" install, you may not have all the files and changes listed below.

Files :

Name: VLCAP.DRV
Destination: Windows System directory (e.g. C:\WINDOWS\SYSTEM\VLCAP.DRV)
Function: Captivator video capture driver for Video for Windows

Name: VVLCAPD.386
Destination: Windows System directory (e.g. C:\WINDOWS\SYSTEM\VVLCAPD.386)
Function: Captivator VxD (Virtual Device Driver)

Name: CAPSNAP.EXE
Destination: VideoSnap Directory (e.g. C:\CAPTIVE\CAPSNAP.EXE)
Function: VideoLogic Captivator VideoSnap utility for capturing still frames

Name: README.TXT
Destination: VideoSnap Directory (e.g. C:\CAPTIVE\README.TXT)
Function: Readme file

Name: TIPS.TXT
Destination: VideoSnap Directory (e.g. C:\CAPTIVE\TIPS.TXT)
Function: Tips on capturing digital video clips

Name: CAPSNAP.HLP
Destination: Windows Directory (e.g. C:\WINDOWS\CAPSNAP.HLP)
Function: Help file for VideoSnap

Name: PCDLIB.DLL
Destination: VideoSnap Directory (e.g. C:\CAPTIVE\PCDLIB.DLL)
Function: Photo-CD library for importing Kodak Photo-CD images

Name: SCAN.VL
Destination:  Windows System directory (e.g. C:\WINDOWS\SYSTEM\SCAN.VL)
Function: VideoLogic's Setup utility.

Name: CAPSNAP.INI (Created the first time VideoSnap is run)
Destination:  Windows directory (e.g. C:\WINDOWS\CAPSNAP.INI)
Function: Windows INI file for VideoSnap.


The following lines are added to SYSTEM.INI:

Section: [386Enh]
Line: device=vvlcapd.386
Function: Loads virtual device driver

Section: [drivers]
Line: msvideo=vlcap.drv
Function: Points to capture driver

Section: [drivers]
Line: VIDC.VLV1=vlcap.drv
Function: Points to YUV codec

A section [vlcap.drv] is created at the end of SYSTEM.INI.
