============================================================= Osprey Video Division ViewCast Corporation Osprey MultiMedia Capture Driver For the following Card(s): Osprey-100 Osprey-101 Osprey-200 Osprey-210 Osprey-220 Osprey-230 Osprey-300 For Windows 2000 Version 2.2.3, build 9 8/9/2004 Sections in this file: - Introduction - Troubleshooting - Osprey-300 IEEE 1394 Ports - Testing the Driver - Manuals and Help - Latest Drivers - Revision History - Known Issues in version 2.2.3 - Information - Upgrading from Windows NT 4.0 to Windows 2000 - Osprey MultiMedia Windows 2000 Installation - Important Notice - Contact Information Introduction: ============================================================= ============================================================= This version of the driver is for Windows 2000 only. It is a Video for Windows Video and Audio capture driver that is plug and play compatible. The new Osprey-300 card is supported in this release. This driver works only with Bt848/Bt878/Ct878A cards sold by the Osprey Video Division of ViewCast Corporation. A new feature available in this release of the Osprey MultiMedia driver is the ability to test drive the Osprey SimulStream(TM) feature. Included in this release is a 10-day evaluation license for SimulStream. The 10-day period begins once the driver has been installed. There is a user option to toggle this capability on and off. While in evaluation mode a watermark will appear on the active video region which denotes usage of an evaluation version of Osprey SimulStream (TM). After the 10-day trial period has expired, one may renew the Osprey SimulStream (TM) evaluation by visiting our website at http://www.ospreyoffers.com/ospreysseval. Troubleshooting ============================================================= ============================================================= If the installation program for this driver appears to hang, press Alt-Tab to ensure that the installation screen is not hidden. When multiple boards are present in a machine while installing the driver, the user should wait 10 seconds before clicking the 'Yes' button when the 'Digital Signature Not Found' window for the Video portion of the driver appears for the 2nd, 3rd, etc Osprey MultiMedia card. Osprey-300 IEEE 1394 Ports ============================================================= ============================================================= The Osprey-300 is essentially an Osprey-230 with two IEEE 1394 ports added to it. The 1394 ports reside on a separate Plug and Play device that is controlled by standard windows drivers; they are separate from the Osprey analog Bt878A device and the Osprey Video for Windows analog drivers. The 1394 ports support Digital Video devices such as camcorders, and also non-DV devices such as hard drives. The 1394 ports are WDM rather than Video for Windows devices. DirectShow applications such as Windows Media Encoder 9 will work directly with them. Video for Windows applications will probably not work with 1394 devices - for example, VidCap32 does not. Many DirectShow applications will capture DV video but not DV audio - for example, the AMCap test application included in this release has this limitation. The 1394 device works only on Windows 2000 and XP;not on NT4, which does not have built-in 1394 support. Testing the Driver: ============================================================= ============================================================= Click on "VidCap32" in the Osprey MultiMedia Capture program group to test the driver. To test the Osprey-300 IEEE 1394 DV ports, use "AMCap" in the Osprey MultiMedia Capture program group. Manuals and Help: ============================================================= ============================================================= The document SimulStreaming.pdf contains general information about the SimulStreaming capabilities which are available at added cost in this driver version. There are 2 User's Guides included with this release. For detailed information about the Osprey-210, 220, 230, and 300 boards and driver, refer to the Osprey-210/220/230/300 MultiMedia Capture Device User's Guide. Refer to the Osprey MultiMedia Capture Driver - User's Guide, for detailed information about the Osprey-100, 101, and 200 boards and driver. These 2 manuals are in PDF format, and are kept in folder \Win2000\ on the CD. After the driver has been installed, shortcuts to these Users's Guides are placed in the "Osprey MultiMedia Capture" program group, as "Osprey 210-220-230-300 Manual" and "Osprey 100-200 Manual". These manuals require the Adobe Acrobat Reader, which is available on the CD, or by download from www.adobe.com. You can read the manuals on the CD by opening files Osprey-210-220-230_Manual.pdf and Osprey100-200_Manual.pdf. The Help inside the Osprey driver is in HTML. This Help requires a frames-capable browser with JavaScript enabled, such as Microsoft IE 4.0 or later, or Netscape 4.5 or later. Latest Drivers: ============================================================= ============================================================= Before installing, check the Osprey Video Division ftp site or the www.ospreyvideo.com website for the latest drivers: For the ftp site, go to: ftp://ftp.ospreyvideo.com/pub/OSP-300/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-230/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-220/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-200/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-100/win2000/latest/ For the website, navigate: www.ospreyvideo.com --> click on Downloads --> click on Software & Drivers --> select your board and operating system from the table If there isn't a newer driver at the time of your installation, please check the website or ftpsite frequently thereafter. Revision History ============================================================= ============================================================= Changes from 2.2.2 build 24 to 2.2.3 build 9: ============================================================= - Added support for new Osprey-300 card. - Provided registry-enabled workaround to turn off SimulStream warning message that displays when starting an encoding session with a larger image size than a currently running stream. To enable workaround, set HKEY_CURRENT_USER\Software\Osprey\Osprey100\Device0\VcDll\ExtFlags to 0x100. For more than one device, replace Device0 with the appropriate device number. - When turning off SimulStream warning messages the default behavior (where appropriate) is now to assume the user does not want to continue in error cases. So now the driver will FAIL implicitly on capture stream open if a SimulStream usage error has been detected. - Added new flag for SCX software to control SimulStream dialog warnings: HKEY_USERS\.DEFAULT\Software\Osprey\Osprey100\VcDll\scx_flags bit 0: 1 == disable SimulStream dialog warnings 1: 1 == return immediate failure - Audio boost factor and volume level calibration have been improved. Changes from 2.2.0 build 781 to 2.2.2 build 24: ============================================================= - Added support for new Osprey-230 card. - Added warning message to warn that no SimulStream license is present if user tries to open 1 board in multiple capture/encoding sessions without SimulStream feature enabled. - Changed timeout-period in driver startup for checking whether a SimulStream evaluation key is enabled. - Fixed bug which could possibly crop incorrect vertical region if the user had enabled SimulStream capability but not CC decoding. - Fixed bug in CropApp and full-size PAL video can now be displayed in that application. - This driver now responds to MMAC_ADV_CONTROL2 and MMAC_ADV_CONTROL control messages. These affect controlling software de-interlace from an application written using the Osprey SDK. - Fixed a Blue Screen crash "stop 0xA IRQL_NOT_LESS_OR_EQUAL crash on some Dell PowerEdge machines. - Fixed bug where video driver crashed or behaved incorrectly when application requested HD video size (larger than 720x480 for NTSC). - Fixed minor video discoloration for every 4th pixel during de-interlacing when looking at RGB16 color format. - Fixed memory leak in audio portion of driver. Changes from 2.0.0 to 2.2.0 build 781: ============================================================= - A new feature available in this release of the Osprey MultiMedia driver is a free 10-day test drive of the Osprey SimulStream(TM) feature. Included in this release is a 10-day evaluation license for SimulStream. There is a user option to toggle this capability on and off. While in evaluation mode a watermark will appear on the active video region which denotes usage of an evaluation version of Osprey SimulStream (TM). After the 10-day trial period has expired, one may renew the Osprey SimulStream (TM) evaluation by visiting our website at http://www.ospreyoffers.com/ospreysseval. - A new feature, software de-interlace, has been added to the 'Advanced Features' page of the Osprey's video control dialog. De-interlacing is optimized for Windows 2000 and later; it will consume fractionally more CPU cycles when enabled under Windows NT. Please see Chapter 5 of the Osprey MultiMedia User's Guide for a description of de-interlacing. - The Closed Caption checkbox is now disabled when the Video Standard in use is PAL format, since PAL does not support closed captions. - Added warning message to warn that no SimulStream license is present if user tries to open 1 board in multiple capture/encoding sessions without SimulStream feature enabled. - Audio upsampling quality has been improved. - Fixed potential audio capture failure to start problem. - When matching audio and video devices, changed to use only the lower 4 bits of PCI bus. This fixes problem for Magma expansion chassis. - Fixed a bug which could potentially cause a Blue Screen crash when an application using the Osprey card terminated abnormally. - Fixed a bug which could result in a race condition when using SimulStream feature. - Fixed DirectShow audio mixer error; the Microsoft DirectShow audio mixer will now control Osprey cards. The DirectShow mixer is accessed from inside Windows Media Encoder 7/7.1, or any other application that displays DirectShow audio property pages. When multiple Osprey cards are present, this mixer only controls the first Osprey card. - Fixed NetMeeting audio tuning wizard error message "Your soundcard does not support a microphone volume control". - Fixed microphone check problem in Powerpoint 2000. When setting up an online broadcast presentation in Powerpoint, the error message "Powerpoint is not receiving sound from the microphone" has been resolved. - To make audio and video device driver names more consistent, a hyphen was added to the name of the Osprey audio device. For example, previous names were of the form "Osprey 200 Audio", and are now "Osprey-200 Audio". This may cause a problem with saved encoding profiles that have stored the old audio driver name. Applications such as the Windows Media Encoder, when loading a saved profile with this old name format, will issue an error and indicate that a device has not been found. The solution is edit the profile and change the audio device name. - Fixed memory access violation in driver. - Fixed a bug in resuming from power-down state. - The functionality of the parameter 'Progressive scan digital camera' has been renamed to 'Field Order'. The feature has been moved to the 'Advanced Features' page of the Osprey's video control dialog. - A bug which caused audio failure on some machines where Device Properties address of PCI device was 0, has been fixed. Changes from version 1.55 to 2.0.0: ============================================================= - Versions 2.0.0 and later are capable of SimulStreaming. - The parameter 'Progressive scan digital camera' on the Video Source dialog page allows the user to select the scan order the driver uses, in order to accommodate a wider variety of cameras. This parameter allows to user to choose between even/odd and odd/even orders. - The parameter 'Access to Multiple Boards' on the Video Configuration page has been changed to 'Multiple Opens'. The meaning of this checkbox has also been changed. This checkbox should be selected when using the SimulStreaming feature of the driver. - Closed Caption decoding may stop after 8 hours when multiple streams are using the same Osprey card (i.e. when SimulStreaming). - The 'Apply to all boards' checkbox on the Closed Caption dialog page has no effect. - Fixed a bug in mixer driver that caused CPU utilization to hit 100% if card was installed in the same machine as a SoundBlaster Live card and an optional utility from Creative. Changes from version 1.54: ============================================================= - The software gain setting in the registry has been moved to HKEY_CURRENT_USER\SOFTWARE\Osprey\Osprey200\DeviceX\Audio\Gain This applies only to Osprey-200 cards, and not to Osprey-210 and 220 cards. - Non-administrator users can now set and save all audio controls (audio source and volume settings). These settings are now stored in a registry location which does not require Administrator rights to change. - The Audio Settings applet has been removed. - A bug which caused portions of the Osprey-100 VFW SDK MMAC_o100_SRC_CONTROL interface to not work correctly has been fixed. - A bug which caused balanced audio to be unavailable on Osprey-220 cards has been fixed. - The msvideo string written to the registry has been shortened. Some machines limit this string to 31 characters. - Extraneous files oemsetup.inf has been removed. Changes from version 1.53: ============================================================= - The Osprey driver includes the new capability to crop the incoming video signal in hardware before it is encoded or captured. Please see the CropApp Manual (in PDF format) which is installed in the Osprey MultiMedia Capture program group for details on using this feature. It is HIGHLY recommended that users read this entire document before enabling hardware cropping. - A method for improving video quality under conditions of PCI bus contention has been added. - Fixed problem where a user who is not a member of group Administrator could not view the Configuration tab of the Osprey driver's Control Dialog. Known issues in version 2.2.2: ============================================================= ============================================================= - The uninstall program does not prompt the user to reboot after uninstalling the driver. The machine must be rebooted to complete the uninstall. - With the existing SimulStream architecture, you MUST pair your fastest desired framerate with your session with the largest pixel size resolution when creating multiple capturing/ encoding sessions using the optional SimulStream feature. This is explained in the SimulStreaming_Users_Guide.pdf as "...all frames must be scaled copy or none of the frames must be scaled copy." If you do not follow this guideline, some streams may fail to start encoding/capturing, or a blue screen crash could possibly occur. - RealProducer 8.5 / Heavy Load Problem: There is a known problem with RealProducer 8.5/8.51 in which it adds video buffers to the capture device before RealProducer has finished processing the buffers. Typically under non-loaded CPU utilizations this is not a problem because the buffer can be processed by RealProducer before being prepared for capture. However, under heavy CPU load, the capture driver can prepare the buffer for capture before RealProducer finishes or even starts processing the buffer. The result is typically a processed image that has a multicolored pattern in the image. The size / height of this pattern depends on how far RealProducer has processed the buffer before it is prepared for capture. If you find this situation occurs first try to reduce your CPU load before contacting Osprey support. - PCI bus numbers of 16 or higher The drivers do not support devices on a PCI bus number equal to or above 16. This bug may affect users who attempt to use a large number of Osprey-230 cards in a system. The Osprey-230 contains a PCI bridge that creates an additional PCI bus for each Osprey-230 card. As a result, adding multiple Osprey-230 cards to a system may create more than 16 PCI buses on a system. The drivers will fail to function properly with cards on PCI bus number 16 or higher. Upgrading from Windows NT 4.0 to Windows 2000: ============================================================= ============================================================= If the Osprey card(s) are now installed on a PC that was running Windows NT 4.0 and was upgraded to windows 2000, you will have to install this software. *The Windows NT 4.0 Osprey drivers are not compatible with Windows 2000.* Following any of the two options in section (2) "Osprey Card(s) is Physically Installed & Previous Driver Installation" under the heading "Osprey-100/101/200 Windows 2000 Installation" will be sufficient to bring your devices up to date. Osprey-100/101/200/210/220/230/300 Windows 2000 Installation: ============================================================= ============================================================= Depending on your system setup, you will have multiple options for the installation of the Osprey MultiMedia drivers. Following are the different scenarios and their methods of installation: * THREE INSTALL SCENARIOS There are three 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, but Osprey Software not Installed. * RECOMMENDED METHOD* Scenario 3: Osprey Card(s) Physically Installed, and Previous Osprey Software Installed. If you have upgraded from Windows NT 4.0 or Windows 95/98 and had Osprey drivers installed on the previous operating system, follow Scenario 3. 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 after you have installed the Osprey card(s). 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. It is important to note here that installing one instance of this software using the indicated "Recommended Methods" above, will setup multiple cards if they exist in the system. If the "Non-Recomended Methods" are used, then these methods will have to be repeated for each Osprey card in the system. You can skip the detailed instructions if you are upgrading from one Osprey driver version to another. Just run the setup.exe file and all the updated components will be installed. -- 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 Osprey Video Capture Device, then for the Osprey Audio Capture Device. This happens because Windows sees the audio and video sections of the card as two distinct logical devices. The logical audio device is present even on Osprey-100/101 cards that have extra video or power connectors in place of audio connectors. 5. Choose No when prompted to reboot at this time. The Osprey software is now fully installed. It will be ready for use after you install the Osprey card in your computer. 6. When you are ready to install the card, shut down Windows 2000 and power off your computer. Install the Osprey card in your computer. Then power up the computer and start Windows 2000. Windows 2000 will detect the newly present Osprey card, and begin to activate the pre-installed driver. It will prompt with a Digital Signature Not Found message twice for each card. Click YES in response to all of these messages, and click Yes to reboot when prompted by the System Settings Change window. The Osprey card will be ready for use after this reboot. -- SCENARIO 2: OSPREY CARD(S) PHYSICALLY INSTALLED, BUT OSPREY SOFTWARE NOT INSTALLED In this case you have two options: Option A: Run the Installation Program (Recommended): When windows 2000 is first started for the first time after the Osprey card is installed, the New Hardware Found wizard will appear one or more times. CANCEL OUT OF THESE WIZARDS. After Windows 2000 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, there is no need to restart the PC. Your Osprey card(s) can be used directly. If there are multiple Osprey cards in the system, this installation method will set up all of them at once automatically. Option B: Use the New Hardware Found Wizard (Not Recommended): This method is more complicated than Option A. It is particularly inconvenient if you are installing multiple cards at once, since each card has to be set up separately. When Windows 2000 starts it detects the new card(s) and starts the New Hardware Found wizard. Note: For all Bt/Ct878-based Osprey cards, the Wizard detects two logical devices for each card- a Multimedia Video Controller device and a Multimedia Controller device. The Multimedia Video Controller is the video section of the Bt/Ct878 device; the Multimedia Controller is the audio section. The audio logical device is present even on Osprey-100 and Osprey-101 cards that have video or power connectors in place of the audio inputs. When the Hardware Wizard detects a device: 1. Note carefully whether the Wizard says Multimedia Video Controller or Multimedia Controller (audio device). Click Next. 2. Choose Search for a suitable driver... option and click Next. 3. Check the Specify a Location box and click Next. 4. Use the Browse... button to locate the INF file o100drv.inf. This INF file is located in the same directory as the driver files that you are installing either on the CD or in the temporary directory where you expanded the web package. Then click OK. 5. Click Next. Highlight the description of the Osprey device you are installing. Click Next. 6. A Digital Signature Not Found windows will appear. Click Yes to continue. 7. Click Finish, then click Close to exit the Hardware Wizard. 8. If you are installing multiple Osprey cards, this sequence will appear once for each card. 9. If you wish to use the Osprey application software, or access the online Users' Guide from the Start Menu, you will still have to run the installation program after Windows 2000 has finished starting. Double click on the Osprey setup.exe file to run the install. -- SCENARIO 3: OSPREY CARD(S) PHYSICALLY INSTALLED, AND PREVIOUS OSPREY SOFTWARE INSTALLED This scenario is for the case when the Osprey card is physically installed in the PC and there is a previous installation of the Osprey drivers. These methods work for upgrades either from an old Osprey Windows 2000 driver to a newer one, or - if you have upgraded the operating system -from a Windows NT 4.0 driver to a Windows 2000 driver. Under this scenario you have two options. With both options, it is not necessary to uninstall the old driver before installing the new driver. Option A: Run the Installation Program (Recommended) 1. Double click the setup.exe file. This will start the installation program. 2. Select Destination Folders and Program Folders when prompted. 3. 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 Osprey Video Capture Device, then for the Osprey Audio Capture Device since they are two distinct logical devices. The logical audio device is present even on Osprey-100/101 cards that have extra video or power connectors in place of audio connectors. 4. If you have one or more Osprey-200s in the system, you will need to restart the system before you can use the updated audio. If you have video-only cards, you do not need to restart the system - the Osprey card(s) can be used immediately. Option B: Use the Device Manager (Normally not Recommended) This method will only install the drivers without updating the bundled applications, Users' Guide, or Start Menu. 1. From the Start Menu select: Settings -> Control Panel -> System ->Hardware -> Device Manager. 2. Double click the Sound, video and game controllers entry. 3. For each entry listed as Osprey Video Capture Device, Osprey Audio Capture Device, or similar description, perform the following steps: a. Double-click on the entry. A Properties dialog appears. b. Click on the Driver tab, then the Update Driver... button. c. The Upgrade Device Driver Wizard window will pop up. Click Next. d. Choose the Display a list of the known drivers for this device... option and click Next. e. Click the Have Disk... button which will bring up an Install From Disk window. f. Use the Browse... button to locate the new file o100drv.inf, located where the new driver files are located. Highlight this file, click Open in the browse box, then click OK. g. Click Next. Three Osprey device descriptions will be listed: Osprey Video Capture Device, Osprey Audio Capture Device, and Osprey Function 1 Placeholder. If the device you are updating is a video capture device, select Osprey Video Capture Device. If the device you are updating is an audio capture device: If your Osprey cards are Osprey-200s, select Osprey Audio Capture Device. If your Osprey cards are not Osprey-200s, select Osprey Function 1 Placeholder. If you have a mix of Osprey-200 and non-Osprey-100 devices, select Osprey Audio Capture Device. Click Next. h. An Update Driver Warning may appear at this point. If you have followed the instructions carefully, this is a safe operation. Click Yes. Click Next. h. A Digital Signature Not Found window will appear. Click Yes to continue. i. Click Finish to close the wizard. 4. When all devices are upgraded, click Close to exit from the device manager. 5. If you have one or more Osprey-200s in the system, you will need to restart the system before you can use the updated audio. If you have video-only cards, you do not need to restart the system - the Osprey card(s) can be used immediately. Important Notice ========================================================== ========================================================== If you are using an Osprey-500 or Osprey-2000 card in the same machine as your Osprey MultiMedia card, we strongly recommend that you upgrade the Osprey-500 or Osprey-2000 card to the version 2.1.0 or later driver. Contact information: =============================================== =============================================== voice: 888-684-6622 fax: 919-319-9814 email: support@ospreyvideo.com web: www.ospreyvideo.com ftp: ftp://ftp.ospreyvideo.com/pub/OSP-100/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-200/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-210/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-220/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-230/win2000/latest/ ftp://ftp.ospreyvideo.com/pub/OSP-300/win2000/latest/ /