OS/2 Shareware BBS: Multimed/Multimed.zip/vidfmm5.zip/read.me

Text File | 1996-05-28 | 11KB | 250 lines

    *** Beta 5 ///FAST Movie Machine TV drivers ***

Release Date: May, 28th, 1996, internal revision 1.21

Kirchhoff & Grill Software GmbH
Lazarettstr 8
91054 Erlangen
Germany

Fax.: [phone]
[e-mail]
http://ourworld.compuserve.com/homepages/hmkirchhKGS

Welcome to Beta 5 of the OS/2 drivers for the ///FAST Movie Machine II
TV drivers.

NOTE: This is a Beta Version, the usual care should be taken with this
      software. This build will expire July 15th 1996 and will not work
      after that date.

DISCLAIMER!!!
 * THIS SOFTWARE IS PROVIDED BY Kirchhoff & Grill Software GmbH ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL Kirchhoff & Grill Software GmbH BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.

LICENCE AGREEMENT!!!
 * You may use this BETA software for your own evaluation purposes only. You
 * are granted the right to use this software until July 15th, 1996.
 * After this date you are required to delete the software from your system
 * and destroy all backup copies you made.
 * You may redistribute this software as long as you do not charge a fee for
 * the distribution or make profit from the distribution in any other form.
 * You may NOT modify the software in any way or use it for commercial purposes.

INSTALLATION OF THE SOFTWARE INDICATES AGREEMENT ON YOUR PART WITH THESE TERMS.








*******************************************************************************
*** WE NEED HELP PLEASE!!! ****************************************************
* IBM needs to fix their MMPM DLL's. Clipping is STILL NOT implemented in this
* Beta release. We are STILL WAITING for a fix for the MMPM so that we can
* implement clipping. If you are using our driver, please ask the IBM support
* when the MMPM fixes to enable clipping for overlay cards will be available.











******************************************************************************
*** NEW FEATURES
+ Teletext support (NOTE: the Teletext applet is distributed as a seperate
  package and expected to go into beta in june '96, see TELETEXT.TXT)
+ Fix for WarpTV's misbehaviour with FPS60
+ Single image capture has been fixed.

******************************************************************************
***     WarpTV
This driver is designed to work with IBM WarpTV. WarpTV is not part of the package.
Please refer to
           http://www.europe.ibm.com/getdoc/psmemea/prodcat/opsys/wtv/
for more Information on WarpTV. Download WarpTV from
           ftp.europe.ibm.com in directory /psmemea/os2drivers/warptv/
and follow the instruction to install it. You don't need to install any of the
Haupauge drivers.
The order of installation is irrelevant. Install WarpTV or our driver first,
whatever you prefer.
In the documentation for WarpTV simply replace "Celebrity Device Driver" with
"///FAST Movie Line Device Driver". Details will differ but the general outline
for installing and setting up the device is the same.

NOTE: WarpTV has just been updated. You will need "warptv.zip" and "mpegcsd.zip".
Download these files, unzip them into a directory (do not unzip them into the
same directory), change directory to that directory and type MINSTALL from the
commandline *IN THAT DIRECTORY*. Do not open the "Multimedia Install" icon from
the Multimedia Folder. You have to execute MINSTALL from the directory you installed
the mpegcsd to. Otherwise MINSTALL will fail.

******************************************************************************
***     Installation of the driver

Open the multimedia folder on your desktop and choose install. Select
a:\ or whatever location you are installing from. The installation
will copy the neccessary files to your harddrive and install the driver
in the config.sys. Halfway through the installation you will be asked to
enter the cards IO address and interrupt level.
The interrupt level is not being used at present, so you could enter
any value there. Future versions of this driver will require an IRQ
however.
For the IO address, specify a value that is not used by another hardware
device in your system. Please note that the MM2 needs at least 16
consecutive addresses so if you specify 310 all values from 310 through
at least 320 will be taken up. If you have installed any extensions such
as the MJPEG extension, the MM2 needs more consecutive IO addresses.
If you have installed the windows drivers for the card, use the same
values for the OS/2 drivers than with the windows version.
NOTE: Nothing prevents you from trying to use the device under OS/2 and
WinOS/2 at the same time. The results however are unpredictable.

You can also edit the CONFIG.SYS and change the values there. Look for
a line
DEVICE=x:\MMOS2\VIDFMM.SYS /B318 /I10 /1

/Bxxx specifies the base IO address, /Ixx is the interrupt value and
/1 tells the driver to install itself as the first ///FAST device.

NOTE !!!: The IO Port address can also be specified in the VIDFMM1.INI
file. The value in VIDFMM1.INI takes precedence over the value in the
CONFIG.SYS statement.

******************************************************************************
*** Setup and Overlay Adjust.

After you installed the software, you need to adjust the overlay. This also
needs to be done everytime you change your display frequency. Open
the Multimedia folder on your desktop and activate "Multimedia Configuration".
Click on the notebook tab that says "MovieMachine x", then click on the
minor tab "Defaults". Click on the "Alignment" button.
This will start the overlay adjust dialog. Please note that it takes a while
for the dialog to start. This is normal. The mousepointer changes to "busy"
while the adjust dialog is prepared.
If you have adjusted the overlay with the windows software, the dialog
should be familiar to you. The procedure is the same, you can even use
the same values.

To align the overlay properly, you need to adjust the settings so that the
overlay signal (vertical white lines) overlap the red/green window in the
dialog.

First select the horizontal scaling value 1, 2 or 3. The higher your graphic
card frequency is, the higher you need to set the horizontal scaling value.
Desktop resolutions of higher than 1024x768 pixel (non-interlaced) will need
a hscale of at least 2, resolutions of 1280x1024 need a hscale of 3. Higher
resolutions are not supported. The MM2 drivers have been tested with a resolution
of 1280x1024 and a vertical frequency of 75Hz on a SPEA Mirage P64.

Next set the "interlaced" checkbox, if you are running an interlaced
resolution. Deselect this checkbox, if you are not using an interlaced graphics
mode.

Change the X-Offset / Y-Offset values until you see the video signal from the
overlay card.

Now you need to set the "PLL Adjustment" value. If the overlay video signal
is out of sync (you don't see vertical lines, instead the white signal
flickers across the screen), reduce the PLL value. PLL values around 500
should always give you a stable picture.
Change the PLL value until the overlay video signal has about the same width
as the red/green window. If the overlay video signal overlaps the red/green
window, you should see a clear border between the red and the green part
in the control window.

Hit "OK" to save the values. You are done.

******************************************************************************
*** Video Format: NTSC, PAL or SECAM

To change the video standard you need to edit the "VIDFMM1.INI" file located
in your \MMOS2 subdirectory. Find and change or add a line
 VIDEOSTANDARD=x
to the [VMC] section. x specifies the standard: 0 is NTSC, 1 is PAL and 2 is
SECAM.

[VMC]
 VideoStandard=0

sets the standard to NTSC. Default is PAL.

******************************************************************************
*** Fixed problems... (hopefully)
+ WarpTV crashed when you where using the driver with the FPS60, not with the
  MM II.

******************************************************************************
*** Known problems...
- Although more than one instance of the driver can be active at any given
  time, the results are unpredictable.

- Clipping is not implemented at the moment. The overlay video signal will
  shine through all underlying windows, even if they are not meant to be
  overlayed. As a result WarpTV's popup menus are very hard to read.
  A future update of the OS/2 MMPM should take care of that. IBM has to
  provide some new DLL's. We are still waiting for them.

- Stream capture or playback is not implemented.
  Future versions of the driver will be able to record and playback AVI
  files that will be compatible to the windows versions. That way you can
  use OS/2 to record/playback your videos and use your favorite video
  editing program, even if it is a windows program only.

- WarpTV: On resolutions greater 800x600 the video overlay will remain in the
  upper left corner even if the WarpTV window is moved.

******************************************************************************
*** Support

At the moment ...
    basically none. We are working on it.

In the future ...
    We will make the driver available as a commercial product. The price
    for the entire package (driver and teletext applet) will be below
        $80. You will receive support through email and fax.
        Beta 5 will very likely be the last public beta version.

******************************************************************************
*** Bugs and bugreports

Please report any problems you find in this software to

[e-mail]

******************************************************************************
history

$Log: read.me,v $
Revision 1.5  1996/05/28 17:03:07  hajo
+ BETA5

.\" Revision 1.4  1996/04/09  09:04:19  KIR
.\" + BETA 4
.\"
.\" Revision 1.3  1996/03/12  20:35:17  KIR
.\" + CEBIT Version -> small change in mm2.c
.\"
.\" Revision 1.2  1996/03/12  20:29:58  KIR
.\" + BETA2, CEBIT Version
.\"
.\" Revision 1.1  1996/02/27  11:14:20  KIR
.\" * BETA 1 release
.\"