============================================================ Osprey Video Division ViewCast Corporation Osprey Multimedia Capture Driver For the following Card(s): Osprey-100 Osprey-200 Osprey-210 Osprey-220 Osprey-230 For Windows XP Version 3.1.0 Build 6 8/20/2004 Sections in this file: - Introduction - Installation over a previous Osprey WHQL-signed driver - Troubleshooting - Testing the Driver - Revision History - Known Issues version 3.1.0 - Mixed Installation of VfW and AVStream drivers - Limitations on Windows 2000 - Windows XP Installation - Contact information ============================================================ Introduction ============================================================ This version of the driver is for Windows XP only. Windows 2000 is not supported for this driver, but may be installed with certain limitations as described in the section "Limitations on Windows 2000". The latest DirectX Runtime is recommended. This driver works only with cards sold by the Osprey Video Division of ViewCast Corporation. ============================================================ Installation over a previous Osprey WHQL-signed driver ============================================================ This driver has not been signed by WHQL. When installing on a machine with a previous Osprey driver signed by WHQL, it is highly recommended that you remove the old driver and reboot before installing this driver. Go to the Control Panel Add/Remove Programs to remove old driver files. After rebooting the machine, cancel out of the Install Wizard and follow the instructions for Windows XP Installation at the end of this file. It is also highly recommended that all Osprey cards to be used with the non-WHQL driver are installed in the system before installing the driver. If another Osprey card is added to the system after installing the non-WHQL driver, Windows will by default prefer to install the previously signed driver for the new device. ============================================================ Troubleshooting ============================================================ If the installation program for this driver appears to hang, press Alt-Tab to ensure that the installation screen is not hidden. ============================================================ Testing the Driver ============================================================ Run "VidControl" or "SwiftCap" under Program Files\Osprey Multimedia Capture\Samples to test the driver. ========================================================== Revision History ========================================================== ========================================================== Changes from 3.1.0 RC5 build 8 to 3.1.0 build 6: ========================================================== - The ability to use the pause button in Windows Media Encoder 9 has been fixed. - Save snapshot while capturing has been fixed. Changes from 3.1.0 RC4 build 2 to 3.1.0 RC5 build 8: ========================================================== - Documentation has been updated. - Pal goes greyscale when ntsc hue is min or max has been fixed. - A defect in AudioConfig resulting in incorrect device selection has been fixed. Changes from 3.1.0 RC3 to 3.1.0 RC4 build 2: ========================================================== - Mono modes now work correctly. - Audio boost factor and volume level calibration has been fixed. - Video drop count has been fixed. Changes from 3.1.0 RC2 to 3.1.0 RC3: ========================================================== - Problem in which when running two SimulStreams with the exact same format, starting or stopping one stream may cause the other stream to stop as well is corrected. - Number of video capture buffers is registry-settable. Changes from 3.1.0 RC1 to 3.1.0 RC2: ========================================================== - Problem in RC1 in which the video would stop after a machine-specific, repeatable interval of 10 to 40 minutes is corrected. ========================================================== Summary of major changes from 3.0.0 build 57 to 3.1.0 RC1 ========================================================== Video: - Preview video is no longer timestamped, in accordance with Microsoft recommendations. - On-screen rendering of video is corrected for various sizes including CCIR sizing. - Problems with rendering multiple instances of preview video are corrected. - Capture of video at non-standard rates such as 17fps or 23fps will now happen at the requested rate. - Problems with certain sizes of I420 video are corrected. - Several problems in the driver with SimulStream and with cropped video are corrected. - Several problems with SwiftCap, CropApp, LogoApp, and CCApp are corrected. VBI, WST, closed captioning: - PAL WST and closed captioning work. - PAL VITC timecode works. - The VITC timecode filter, TCOverlay.ax, is enhanced. - A VITC timecode demo applet, TCApp, is added. Audio: - Display in audio mixer of just a single unbalanced line for Osprey-220 and Osprey-230 is corrected. - The plug-and-play audio placeholder for bt878-based Osprey-100s now exposes no filters, rather than exposing nonfunctioning filters. ============================================================ Known Issues in version 3.1.0 ============================================================ This driver is fully functional under Windows XP only. See below for limitations with Windows 2000. If your display adapter is based on a NVidia GeForce FX 5200/5600, or similiar chip, you must use a NVidia driver 5.6.7.2 dated 3/24/2004 or later. We have verified that this version works correctly when used with our product. With earlier NVidia drivers video capture may stop after several hours;NVidia driver 5.2.1.6 dated 10/06/2003 is known to have this problem. To find the correct NVidia version information please do the following: - right click on My Computer and select Properties - click on the Hardware tab - click on the Device Manager button - open Display Adapters - right click NVIDIA GeForce 5X00 - click the Driver tab - the version and date are here This driver does not support Windows Media Encoder 7.1. Please upgrade to Windows Media Encoder 9. Audio mixer will initially display incorrect audio inputs if driver is installed in same machine with 2.2 or earlier version of driver for any Osprey card, or if the 2.2 or earlier driver has not been fully uninstalled. User can manually switch the mixer to the correct device. If the earlier driver does not have to be installed and working, this situation can be corrected by the following registry edit: In the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows NT\CurrentVersion\Drivers32 delete all REG_SZs named mixer or mixer1...mixer9 that reference an Osprey mixer such as o2ca_mix.dll. In Helix Producer Plus, with SimulStream installed, changes to "Settings ... DirectShow Pin" do not take effect until the device is deselected then reselected. This driver does not currently support power management standby or hibernate modes. If an Osprey-2x0, Osprey-300, and Osprey-540/560 are in the same system, all of the devices should be updated to the 3.1.0 driver. The driver property pages may not all work correctly if this is not done. If you install the Osprey MultiMedia Capture Driver version 3.1.0 on top of any earlier Osprey AVStream Capture Driver, the installer may prompt you to overwrite the o200avs.ax file. The message may ask, "Overwrite the English (United States) file with the unspecified language one?" If this message is displayed select "Yes". ============================================================ Mixed Installation of VfW and AVStream drivers ============================================================ To have a mixed installation that includes an Osprey Video for Windows (VfW) driver (driver version 2.2.2 or lower) for one (or more) Osprey card(s) and the Osprey MultiMedia 3.1.0 AVStream Capture driver for the other Osprey card(s) do the following: I. Install the Video for Windows driver if it is not already installed. II. Install the Osprey MultiMedia 3.1.0 Capture Driver. This will upgrade all devices to the AVStream drivers, but will not delete the Video for Windows files from the PROGRAMFILES directory. III. Use the Device Manager and run the INF file to reinstall the VfW driver on one or more of the devices. 1. The following files must be present in the PROGRAMFILES directory (ex. C:\Program Files\Osprey MultiMedia Capture\driver) on your machine: o100drv.sys, o100vc.dll, o2ca.sys, o2ca_usr.dll, o2ca_mix.dll, o2ca_wav.dll, o200board.dll, and o100drv.inf. 2. On the Start Menu right click on "My Computer" and select "Properties" from the list. 3. When the next dialog box is displayed select "Hardware" from the top of the menu. 4. In the second row of the next dialog box there is a section called "Device Manager". Click on the button to the right that says "Device Manager". 5. Double click on the heading that reads "Sound, video and game controllers". There will be two or more Osprey AVStream Devices in the drop down list. 6. Right click on the Osprey device that you want to set up with the VfW driver, and select "Update Driver...". 7. When the Hardware Update Wizard screen is displayed select "Install from a list or specific location (Advanced)" and then click Next. 8. In the next screen "for choosing your search and installation options" select "Don't search. I will choose the driver to install" and click Next. 9. Select "Have Disk" in the next screen. 10. Click on "Browse" and point to the VfW INF file which is located in your PROGRAMFILES directory. For example, C:\Program Files\Osprey MultiMedia Capture\driver\o100drv.inf. Click on "OK" at the top of the screen and then click Next. 11. When the Windows Logo Testing dialog box is displayed select "Continue Anyway". 12. Click on Finish. 13. Perform steps 6-12 again for other AVStream devices that you would like to set up for VfW. IV. In a mixed VfW / AVStream installation the audio mixer will always initially display the inputs for a VfW device, even if an AVStream device should be the one selected. User has to switch manually to the correct device using the mixer's Options -> Properties control. ============================================================ Limitations on Windows 2000 ============================================================ This driver may be installed on Windows 2000 with the following expected limitations: - No SimulStream audio. - No peak level meter in the mixer (mixer may not work at all). - Need to install the latest DirectX Runtime. - Need to manually create registry key to enable audio driver. To enable, set: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\o200avs\DX9 to a non-zero value. =============================================== Windows XP Installation: =============================================== Depending on your system setup, you will have multiple options for the installation of the drivers. * TWO INSTALL SCENARIOS Following are the different scenarios and their methods of installation: There are two main situations that might apply to you: - Scenario 1: Osprey Card(s) not Physically Installed in the PC. - Scenario 2: Osprey Card(s) Physically Installed In all cases, the most efficient and complete installation method is to run the setup.exe program on the product CD or in the web package that you downloaded. The setup program automates the Plug and Play steps required to install the drivers and ensures that they are performed correctly. It also installs the bundled applets and Users' Guide. If you have multiple Osprey capture cards in the system it sets all of them up at once. -- SCENARIO 1: OSPREY CARD(S) NOT PHYSICALLY INSTALLED IN THE PC This is the method that we recommend if you are installing an Osprey card for the first time on a system, and the Osprey software has not yet been installed. This scenario is called the "Preinstall Scenario". After the install is run, as soon as an Osprey card is installed in the PC, it is detected and its drivers are started automatically. 1. Double-click the setup.exe file to start the installation. 2. Select Destination Folders and Program Folders when prompted. 3. You will then be prompted to preinstall the drivers. Select yes to continue. 4. Messages saying Digital Signature Not Found will now appear, asking Do you want to continue? Click Yes for each message. This message will appear twice for each card, first for the AVStream Video Capture Device, then for the AVStream Audio Capture Device. This happens because Windows sees the audio and video sections of the card as two distinct logical devices. 5. The Osprey software is now fully installed. Assuming you want to use the Osprey card and drivers immediately, shut down Windows XP, install the card, and restart your computer now. When it starts, Windows XP will automatically recognize the card and start its preinstalled drivers. You do not have to install the Osprey card or restart the system immediately. At any time in the future, if Windows XP finds an Osprey card(s) installed, it will automatically activate the driver. -- SCENARIO 2: OSPREY CARD(S) PHYSICALLY INSTALLED Run the Installation Program: When Windows XP is first started after the Osprey card is installed, the Found New Hardware Wizard will appear one or more times. Cancel out of these wizards. After Windows XP has finished starting, do the following: 1. Double-click the setup.exe file. This will start the installation program. 2. Select Destination Folders and Program Folders when prompted. 3. One or more Digital Signature Not Found windows may appear during the installation process. Click Yes in each of them continue. 4. When the installation is finished, you must restart your PC. If there are multiple Osprey cards in the system, this installation method will set up all of them at once automatically. Contact information: =============================================== =============================================== voice: 888-684-6622 fax: 919-319-9814 email: support@ospreyvideo.com web: www.ospreyvideo.com