VIDVUE v3.0 - Windows Multimedia Viewer/Util
Full GIF 89a, AVIdeo,WAVaudio,MIDImusic,FLI
FLC animation. Multiple TIFF & DCX (FAX),
PCX,TGA,WMF,JPG/JPEG,BMP/DIB,EPS,WPG,PICT,
Photo-CD,MOV/Quicktime. User slideshows.
Image processing. Prints, converts ...more!
VBRUN300.DLL req. 100% Functional Shareware.
Featured in CompuServe Mag, Apr 94 & Jul 94.

VIDVUE v3.0 - Windows Multimedia Viewer/Util
Full GIF 89a, AVIdeo,WAVaudio,MIDImusic,FLI
FLC animation. Multiple TIFF & DCX (FAX),
PCX,TGA,WMF,JPG/JPEG,BMP/DIB,EPS,WPG,PICT,
Photo-CD,MOV/Quicktime. User slideshows.
Image processing. Prints, converts ...more!
VBRUN300.DLL req. 100% Functional Shareware.
Featured in CompuServe Mag, Apr 94 & Jul 94.
1&7xShareware Distribution
VIDVUE30.ZIP can be freely copied and distributed, unmodified. You can also copy and distribute your registered disk(s) set as long as you DELETE the TECHSUPP.TXT file (only registered users get telephone support) and do not disclose your Personal S/N.

DEMO.TXT: Slideshow Example
In your VIDVUE app directory is a text file - DEMO.TXT. This file shows you how to write a multimedia slideshow script. Simply change the "FILENAME=" keyword to equivalent files in your own drive/directory then save the text file with a *.SHO extension (eg., DEMO.SHO). Additonal sample scripts are also included (see Jmpstart.txt and Traviata.txt). See VIDVUE.HLP file for details on how to write user-scripted slideshows.

Mach64 Incompatibilities
If you are using a Mach64-based card with Mach64 drivers v1.0 to v1.3, Quicktime for Windows (QTW) will crash !!! In addition, VIDVUE will incorrectly display multiple-image GIFs in 256-color modes. In 32K, 64K, 24-bit and 32-bit video modes, except for QTW crashing, VIDVUE will behave normally.

Edit the [Macx] section in your Windows SYSTEM.INI file; backup your SYSTEM.INI file (eg., make a copy called SYSTEM.BAK). Using a text editor (eg., NotePad), add the following entry:

DeviceBitmap=OFF

Also, despite the above setting, the 1024x768x256 video mode may ocassionally cause a "Page Fault" depending on the image size; for these images either set AUTOSIZE=OFF in your script or turn off the AutoSize option if you play immediate slideshows with graphic images. You can also keep the AUTOSIZE=ON keyword and avoid driver problems by setting FULLSCREEN= to a number less than 100 (eg., FULLSCREEN=95).


Diagnosing MCI Installation in Windows
If you get MCI driver errors when loading AVI, WAV, MID or FLI files, you may have a parameter
missing from your SYSTEM.INI or WIN.INI file. Ensure that you have installed the MCI drivers by
using the Media Player to verify successful installation.

If you downloaded NEWPLA.ZIP (from GO ASOFT or a BBS) or WAPLAY.EXE (from
GO GRAPHSUP at CIS) instead of AAWIN11.ZIP (or higher) to play FLI/FLC animation files, you
may get MCI errors with VIDVUE, since the original setup program is not included.

Copy SYSTEM.INI and WIN.INI to *.BAK; this way you can undo changes. Enter items that
DO NOT EXIST in each of the INI files with a text editor. Close and restart Windows.

Entries in SYSTEM.INI file:

[mci]
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
AVIVideo=mciavi.drv
Animation1=mciaap.drv

[drivers]
midimapper=midimap.drv
VIDC.MSVC=msvidc.drv
VIDC.RT21=indeo.drv
VIDC.MRLE=msrle.drv

;following are new drivers/codecs in VFW 1.1a
VIDC.IV31=ir30.dll
VIDC.CVID=iccvid.drv
VIDC.YVU9=isvy.drv
VIDC.IV32=ir30.dll

;other drivers with VIDC.????= will appear too over time

Entries in WIN.INI file:

[mci extensions]
wav=waveaudio
mid=sequencer
rmi=sequencer
avi=AVIVideo
fli=Animation1
flc=Animation1

VIDVUE.INI and MCI Initialization
Due to the way different systems react to MCI device initialialization; VIDVUE now includes every possible combination for MCI devices initialization. If the the default routines still result in an MCI error loading AVI, WAV, MID or FLI files, after

1. verifying that all relevant entries are in SYSTEM.INI or WIN.INI file
2. and Media Player plays the files,

then you can use a text editor to add/modify the following entries in the VIDVUE.INI file.

AUDINIT=n
AAAINIT=n
VIDINIT=n

where n=1,2 or 3

"AUDINIT=" modifies WAV and MID initialization.
"AAAINIT=" modifies FLI and FLC initialization.
"VIDINIT=" modifies AVI and MOV initialization.

If you have problems loading WAV and MID files, experiment by adding:
AUDINIT=1
or
AUDINIT=2
or
AUDINIT=3
restart Windows, run VIDVUE and play your WAV or MID file to see if it loads correctly.

If you have problems loading FLI and FLC files, experiment by adding:
AAAINIT=1
or
AAAINIT=2
or
AAAINIT=3
restart Windows, run VIDVUE and play your FLI or FLC file to see if it loads correctly.

If you have problems loading AVI files, experiment by adding:
VIDINIT=1
or
VIDINIT=2
or
VIDINIT=3
restart Windows, run VIDVUE and play your AVI file to see if it loads correctly.

Apple QuickTime for Windows (QTW) Runtime
To run *.MOV (Apple QTW MOVie) files, installed MCI drivers for Windows are required. To check if the drivers are installed, use the Media Player accessory to play *.MOV files; if you can play *.MOV files via Media Player then VIDVUE can too.

If you purchased and are currently using any of the following products:

Adobe Premiere 1.0 (or later) for Windows
Macromedia Action 2.5 (or later) for Windows
Macromedia Authorware Pro 2.0 (or later) for Windows

then you probably have installed MCI drivers for MOV playback; verify proper MCI installation via Media Player.

If you don't have the Quicktime for Windows drivers, then CompuServe subscribers can:

1. GO MACDEV.
2. Download LICENS.TXT from Library 8.
3. Read and abide to terms and conditions in LICENS.TXT.
4. If you agree to LICENS.TXT, then download QTDSK1.ZIP and QTDSK2.ZIP.

Note:QTDSK1.ZIP and QTDSK2.ZIP are NOT distributable files.
Only YOU can download and use them (see LICENS.TXT).
READ THE README.WRI FILE IN QTDSK1.ZIP.

5. Extract QTDSK1.ZIP to a blank, formatted 1.44 MB disk.

Example:

If you dowloaded the *.ZIP files to d:\CSERVE\DOWNLOAD then

a - Insert your blank, formatted 1.44 disk in Drive A:
b - in DOS, type "A:" to goto Drive A:
c - Type "PKUNZIP -d d:\cserve\download\QTDSK1.ZIP"
to extract files to directories.

6. Extract QTDSK2.ZIP to another blank, formatted 1.44 MB disk.
7. Insert DISK1, run Windows and run SETUP.

Note:If for some strange reason SETUP cannot find DISK2 when it requests it,
rename the DISK2 directory on DISK2 to "DISK1" then reinstall. You may
have to use a utility like Norton or PCtools to do this.

If you are not yet a CompuServe subscriber, but have a CDROM and several CDROM titles, you may already have the QTW runtime files BUT may not be setup for MCI playback.

1. Copy all QTW runtime files to your \windows\system directory.
The QTW files are usually placed in a separate directory; you must have:

MCIQTW.DRV, MCIQTENU.DLL, QTIMCMGR.DLL, QTIM.DLL
QTOLE.DLL, QTHNDLR.DLL, QTVHDW.DLL, QTNOTIFY.EXE
PLAYENU.DLL, VIEWENU.DLL, and several *.QTC files

Note:Since YOU purchased the book w/ a CDROM or CDROM title, only YOU are
licensed to use the QTW runtime files on ONE/YOUR single computer.
YOU CANNOT DISTRIBUTE THE QTW RUNTIME FILES OR COPY THEM TO
ADDITIONAL MACHINES/COMPUTERS OR SHARE THEM VIA NETWORKS
OR OTHER SHARED DEVICES.

2. Create a QTW.INI file and place it in your \windows directory;
add the following sections and entries.

[Options]
VideoOptimize=DIB

[Video]
Optimize=driver

[QuickTime for Windows]
Implementation=Full

3. Modify your SYSTEM.INI file; add under the [mci] section

QTWvideo=MCIQTW.DRV

4. Modify your WIN.INI file; add under the [mci extensions] section

MOV=QTWvideo

HiColor DDB (Device Dependent Bitmap) Frame Grabs
Since 32K or 64K color modes are the preferred modes for viewing video files, Video for Windows 1.1 (or higher) and Apple Quicktime 1.1.1 (or higher) displays video as DDBs for speed on 32K/64K color displays. DDBs are DEVICE DEPENDENT; thus, you have to tell VIDVUE how to use them. A special entry in the VIDVUE.INI file tells VIDVUE how to access DDBs. This is ONLY required if you want to grab video frames from AVI or MOV video files on 32K/64K color displays and the default setting does not work capture correctly. Run VIDVUE and select "Help-System/Video Info". If "Bits/Pix=16" or "Bits/Pix=15" then this affects you. Otherwise, skip this setup.

Using a text editor (eg., NOTEPAD), add the following entry to the VIDVUE.INI file:

HiColorGrab=RGB

where RGB=0(will save to a 24-bit DIB; this is the default)
RGB=555 (will save to standard 32K HiColor DDB format)
RGB=565 (will save to an XGA-type DDB format)
RGB=655 (will save to a non-standard XGA-type DDB format
typically found with ATI cards)
RGB=664 (will save to a non-standard DDB format typically found with ATI cards)

If you have an ATI card, run the FlexDesk utility then click the Advanced button, the "16 BPP RGB Mode" frame will tell you how you are currently setup.

If you have one of the newer Windows accelerator cards, try

HiColorGrab=565

most will typically default to this mode.

If "Help-System/Video Info" shows "Bits/Pix=15" then try.

HiColorGrab=555


If you don't know what RGB mode you are in, experiment with:

HiColorGrab=555
or
HiColorGrab=565
or
HiColorGrab=0

then restart VIDVUE and try to Grab a video frame; see VIDVUE.HLP if you don't know how to grab video frames.


AVI Installation Checklist & Diagnostic Primer
Firstly, you MUST have Windows (or Windows for Workgroups) 3.1 or 3.11; using Windows 3.0 with multimedia extensions "should" work, but will also increase your chances of incompatibility with new CoDecs compressor/decompressors) appearing in the market in addition to bugs in Windows 3.0 that were fixed with the updates.

Should I update to VFW 1.1a ?

Video for Windows (VFW) 1.1a includes a LOT of new codecs (eg., CinePak). If you have not upgraded to VFW 1.1a, and play AVI files with new codec, you will get an MCI (Media Control Interface) error stating something "... driver not found" or "... not installed". Also, it incorporates routines to speed up display updates by writing directly to video memory; some video cards may
be incompatible with this enhanced scheme.

Download VFW11A.exe; run it in a temporary directory; it is self-extracting. Then run it's setup.

IMPORTANT:
If you currently installed VFW 1.0 and are dependent on running files for a business or
presentation in the near future, prudence dictates that you back up your entire \windows
and \windows\system directory so that you can restore your entire setup.


How do I know the drivers are installed?

Use a text editor or viewer in DOS, NotePad or SysEdit in Windows and view your SYSTEM.INI
file. You should see the following in the [drivers] section. If it is there then you have installed
"correctly". You should be able to locate the *.DRV files in your \windows\system dir.

[drivers]

VIDC.MSVC=msvidc.drv
VIDC.RT21=indeo21.drv
VIDC.IV31=ir30.dll
VIDC.IV32=ir30.dll
VIDC.CVID=iccvid.drv
VIDC.MRLE=msrle.drv
VIDC.YVU9=indeov.drv

Note: More drivers will appear with succeeding updates.

My SYSTEM.INI drivers refer to the same VIDC.???? driver. Is this causing incompatibility?

If all the "VIDC.????=" entries refer to the same driver (e.g., VIDC.????=ativdacc.drv) then your system uses proprietary multimedia accelerator interceptors/drivers. Generally, the interceptor speeds up your display updates and should not be a problem (but one never knows).

If you suspect incompatibility with your multimedia interceptor/driver restore all the "VIDC.????=" entries to defaults.

a. Backup your SYSTEM.INI file to SYSTEM.BAK (e.g., copy SYSTEM.INI *.BAK).

b. From the list above (see #3) copy all "VIDC.????" entries and replace them
with the specific drivers referred to; this will effectively remove the interceptor from the loop.

Is my video card incompatible ?

To isolate variables related to your video driver, change your Windows video setup to VGA 640x480 (16 colors). AVI files should playback, albeit more slowly, possibly jerky and only with 16 colors (dithered too). Try other video modes and see which one works or doesn't. If specific modes don't playback correctly, then you need updated/corrected drivers from your card's manufacturer. Also, if you video card requires a "memory aperture" try turning it off to see if that is causing a problem.

Insufficient Windows memory?

Newer codecs may require more memory (actually there not swapped to disk). Free all possible
Windows memory by closing all open applications. If the AVI file plays then "insufficient memory"
was the issue. Note: You MUST have 4MB to begin with and be running in 386 Enhanced mode.

Multi-tasking interactions with other apps?

Playback of AVI files is CPU intensive. Free all possible Windows resources by closing all open
applications - particularly DOS sessions, screen savers, clocks, schedulers, e-mail, fax,
communications apps, "green"/power savers, and anything requiring a timer or is in the background. If the AVI file plays then you've isolated interactions with other Windows apps. One or several of those concurrent apps caused an incompatible interaction.

Hard Disk/CDROM caching ?

Generally there should not be a problem with SMARTDRV; the worst case is less extended memory (see "Insufficient Windows memory?" above) or jerky playback.

To isolate problems related to caching:

a. Backup your CONFIG.SYS and AUTOEXEC.BAT; copy it to *.BAK.
b. Delete any caching driver (eg., SMARTDRV) from your CONFIG.SYS or AUTOEXEC.BAT file.
c. Reboot you computer; restart Windows and try playing your AVI file again.

32-bit drive access?

Depending on your hard disk, disk controller, non-standard DOS driver, and bus type
(eg., VLB, PCI, ISA, EISA), a combination can exist that may be incompatible with AVI playback.

Activate your Control Panel. Activate the 386 Enhanced icon and TURN OFF 32-bit access. If that resolves your problem then it had to do with one of the components in the hard disk sub-system(s).

Compressed drives.

Ensure that you are not playing AVI files from compressed drives (eg., DoubleSpace, Stacker, ...).
The device driver will interfere with rapid data transfer. Always place AVI files in the uncompressed
drive for playback.
so that you can restore your entire setup.


How do I know the drivers are installed?
wtplchd`\IXTjPzLzwCsEoBkDg
cv
_
[
WS^OKwsok%gHc_X[|WSOKws2o4k^g`c_`[WSOK+wBsokgd3`\XT P L K wU s| o k g c-!_1![
"W!"S"O"K""w"s"o#k#g)#c#_#[%W.%SF'OT'KT'W(w(s)oC*k*g*c{-_-[/W/S0O1K12w2s4o4k/6gA6c&7_-[/W/S0O1Kcehj|~EBBDBD


2
H
]
t
v








4H\^#%%HD
F



!,79KM~)448CGRvx24`UW469s4^`)Y02CEz3xQ~)+@Bcee K | /!1!!!
"""!"L"N"""""""""""##'#)#####%%0%2%2%&&&D'F'S''(S(U(W((((E)))))))))**-*C*E*~****++q,s,,,-y-{-{---////0w00011f112222333333F444445e5g5-6/6C6E667&7(73f=/2!898(d DOS driver, and bus typ6C6 EISA), a combination can exist that may be incompatible with AVI playback.

Activate your Control Pan Arial the 386 Enhanced icon and TURN OFF 32-bit access. If that resolves your problem then it had to do with one of the

VIDVUE v3.0 - Windows Multimedia Viewer/Util
Full GIF 89a, AVIdeo,WAVaudio,MIDImusic,FLI
FLC animation. Multiple TIFF & DCX (FAX),
PCX,TGA,WMF,JPG/JPEG,BMP/DIB,EPS,WPG,PICT,
Photo-CD,MOV/Quicktime. User slideshows.
Image processing. Prints, converts ...more!
VBRUN300.DLL req. 100% Functional Shareware.
Featured in CompuServe Mag, Apr 94 & Jul 94.
1&7xShareware Distribution
VIDVUE30.ZIP can be freely copied and distributed, unmodified. You can also copy and distribute your registered disk(s) set as long as you DELETE the TECHSUPP.TXT file (only registered users get telephone support) and do not disclose your Personal S/N.

DEMO.TXT: Slideshow Example
In your VIDVUE app directory is a text file - DEMO.TXT. This file shows you how to write a multimedia slideshow script. Simply change the "FILENAME=" keyword to equivalent files in your own drive/directory then save the text file with a *.SHO extension (eg., DEMO.SHO). Additonal sample scripts are also included (see Jmpstart.txt and Traviata.txt). See VIDVUE.HLP file for details on how to write user-scripted slideshows.

Mach64 Incompatibilities
If you are using a Mach64-based card with Mach64 drivers v1.0 to v1.3, Quicktime for Windows (QTW) will crash !!! In addition, VIDVUE will incorrectly display multiple-image GIFs in 256-color modes. In 32K, 64K, 24-bit and 32-bit video modes, except for QTW crashing, VIDVUE will behave normally.

Edit the [Macx] section in your Windows SYSTEM.INI file; backup your SYSTEM.INI file (eg., make a copy called SYSTEM.BAK). Using a text editor (eg., NotePad), add the following entry:

DeviceBitmap=OFF

Also, despite the above setting, the 1024x768x256 video mode may ocassionally cause a "Page Fault" depending on the image size; for these images either set AUTOSIZE=OFF in your script or turn off the AutoSize option if you play immediate slideshows with graphic images. You can also keep the AUTOSIZE=ON keyword and avoid driver problems by setting FULLSCREEN= to a number less than 100 (eg., FULLSCREEN=95).


Diagnosing MCI Installation in Windows
If you get MCI driver errors when loading AVI, WAV, MID or FLI files, you may have a parameter
missing from your SYSTEM.INI or WIN.INI file. Ensure that you have installed the MCI drivers by
using the Media Player to verify successful installation.

If you downloaded NEWPLA.ZIP (from GO ASOFT or a BBS) or WAPLAY.EXE (from
GO GRAPHSUP at CIS) instead of AAWIN11.ZIP (or higher) to play FLI/FLC animation files, you
may get MCI errors with VIDVUE, since the original setup program is not included.

Copy SYSTEM.INI and WIN.INI to *.BAK; this way you can undo changes. Enter items that
DO NOT EXIST in each of the INI files with a text editor. Close and restart Windows.

Entries in SYSTEM.INI file:

[mci]
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
AVIVideo=mciavi.drv
Animation1=mciaap.drv

[drivers]
midimapper=midimap.drv
VIDC.MSVC=msvidc.drv
VIDC.RT21=indeo.drv
VIDC.MRLE=msrle.drv

;following are new drivers/codecs in VFW 1.1a
VIDC.IV31=ir30.dll
VIDC.CVID=iccvid.drv
VIDC.YVU9=isvy.drv
VIDC.IV32=ir30.dll

;other drivers with VIDC.????= will appear too over time

Entries in WIN.INI file:

[mci extensions]
wav=waveaudio
mid=sequencer
rmi=sequencer
avi=AVIVideo
fli=Animation1
flc=Animation1

VIDVUE.INI and MCI Initialization
Due to the way different systems react to MCI device initialialization; VIDVUE now includes every possible combination for MCI devices initialization. If the the default routines still result in an MCI error loading AVI, WAV, MID or FLI files, after

1. verifying that all relevant entries are in SYSTEM.INI or WIN.INI file
2. and Media Player plays the files,

then you can use a text editor to add/modify the following entries in the VIDVUE.INI file.

AUDINIT=n
AAAINIT=n
VIDINIT=n

where n=1,2 or 3

"AUDINIT=" modifies WAV and MID initialization.
"AAAINIT=" modifies FLI and FLC initialization.
"VIDINIT=" modifies AVI and MOV initialization.

If you have problems loading WAV and MID files, experiment by adding:
AUDINIT=1
or
AUDINIT=2
or
AUDINIT=3
restart Windows, run VIDVUE and play your WAV or MID file to see if it loads correctly.

If you have problems loading FLI and FLC files, experiment by adding:
AAAINIT=1
or
AAAINIT=2
or
AAAINIT=3
restart Windows, run VIDVUE and play your FLI or FLC file to see if it loads correctly.

If you have problems loading AVI files, experiment by adding:
VIDINIT=1
or
VIDINIT=2
or
VIDINIT=3
restart Windows, run VIDVUE and play your AVI file to see if it loads correctly.

Apple QuickTime for Windows (QTW) Runtime
To run *.MOV (Apple QTW MOVie) files, installed MCI drivers for Windows are required. To check if the drivers are installed, use the Media Player accessory to play *.MOV files; if you can play *.MOV files via Media Player then VIDVUE can too.

If you purchased and are currently using any of the following products:

Adobe Premiere 1.0 (or later) for Windows
Macromedia Action 2.5 (or later) for Windows
Macromedia Authorware Pro 2.0 (or later) for Windows

then you probably have installed MCI drivers for MOV playback; verify proper MCI installation via Media Player.

If you don't have the Quicktime for Windows drivers, then CompuServe subscribers can:

1. GO MACDEV.
2. Download LICENS.TXT from Library 8.
3. Read and abide to terms and conditions in LICENS.TXT.
4. If you agree to LICENS.TXT, then download QTDSK1.ZIP and QTDSK2.ZIP.

Note:QTDSK1.ZIP and QTDSK2.ZIP are NOT distributable files.
Only YOU can download and use them (see LICENS.TXT).
READ THE README.WRI FILE IN QTDSK1.ZIP.

5. Extract QTDSK1.ZIP to a blank, formatted 1.44 MB disk.

Example:

If you dowloaded the *.ZIP files to d:\CSERVE\DOWNLOAD then

a - Insert your blank, formatted 1.44 disk in Drive A:
b - in DOS, type "A:" to goto Drive A:
c - Type "PKUNZIP -d d:\cserve\download\QTDSK1.ZIP"
to extract files to directories.

6. Extract QTDSK2.ZIP to another blank, formatted 1.44 MB disk.
7. Insert DISK1, run Windows and run SETUP.

Note:If for some strange reason SETUP cannot find DISK2 when it requests it,
rename the DISK2 directory on DISK2 to "DISK1" then reinstall. You may
have to use a utility like Norton or PCtools to do this.

If you are not yet a CompuServe subscriber, but have a CDROM and several CDROM titles, you may already have the QTW runtime files BUT may not be setup for MCI playback.

1. Copy all QTW runtime files to your \windows\system directory.
The QTW files are usually placed in a separate directory; you must have:

MCIQTW.DRV, MCIQTENU.DLL, QTIMCMGR.DLL, QTIM.DLL
QTOLE.DLL, QTHNDLR.DLL, QTVHDW.DLL, QTNOTIFY.EXE
PLAYENU.DLL, VIEWENU.DLL, and several *.QTC files

Note:Since YOU purchased the book w/ a CDROM or CDROM title, only YOU are
licensed to use the QTW runtime files on ONE/YOUR single computer.
YOU CANNOT DISTRIBUTE THE QTW RUNTIME FILES OR COPY THEM TO
ADDITIONAL MACHINES/COMPUTERS OR SHARE THEM VIA NETWORKS
OR OTHER SHARED DEVICES.

2. Create a QTW.INI file and place it in your \windows directory;
add the following sections and entries.

[Options]
VideoOptimize=DIB

[Video]
Optimize=driver

[QuickTime for Windows]
Implementation=Full

3. Modify your SYSTEM.INI file; add under the [mci] section

QTWvideo=MCIQTW.DRV

4. Modify your WIN.INI file; add under the [mci extensions] section

MOV=QTWvideo

HiColor DDB (Device Dependent Bitmap) Frame Grabs
Since 32K or 64K color modes are the preferred modes for viewing video files, Video for Windows 1.1 (or higher) and Apple Quicktime 1.1.1 (or higher) displays video as DDBs for speed on 32K/64K color displays. DDBs are DEVICE DEPENDENT; thus, you have to tell VIDVUE how to use them. A special entry in the VIDVUE.INI file tells VIDVUE how to access DDBs. This is ONLY required if you want to grab video frames from AVI or MOV video files on 32K/64K color displays and the default setting does not work capture correctly. Run VIDVUE and select "Help-System/Video Info". If "Bits/Pix=16" or "Bits/Pix=15" then this affects you. Otherwise, skip this setup.

Using a text editor (eg., NOTEPAD), add the following entry to the VIDVUE.INI file:

HiColorGrab=RGB

where RGB=0(will save to a 24-bit DIB; this is the default)
RGB=555 (will save to standard 32K HiColor DDB format)
RGB=565 (will save to an XGA-type DDB format)
RGB=655 (will save to a non-standard XGA-type DDB format
typically found with ATI cards)
RGB=664 (will save to a non-standard DDB format typically found with ATI cards)

If you have an ATI card, run the FlexDesk utility then click the Advanced button, the "16 BPP RGB Mode" frame will tell you how you are currently setup.

If you have one of the newer Windows accelerator cards, try

HiColorGrab=565

most will typically default to this mode.

If "Help-System/Video Info" shows "Bits/Pix=15" then try.

HiColorGrab=555


If you don't know what RGB mode you are in, experiment with:

HiColorGrab=555
or
HiColorGrab=565
or
HiColorGrab=0

then restart VIDVUE and try to Grab a video frame; see VIDVUE.HLP if you don't know how to grab video frames.


AVI Installation Checklist & Diagnostic Primer
Firstly, you MUST have Windows (or Windows for Workgroups) 3.1 or 3.11; using Windows 3.0 with multimedia extensions "should" work, but will also increase your chances of incompatibility with new CoDecs compressor/decompressors) appearing in the market in addition to bugs in Windows 3.0 that were fixed with the updates.

Should I update to VFW 1.1a ?

Video for Windows (VFW) 1.1a includes a LOT of new codecs (eg., CinePak). If you have not upgraded to VFW 1.1a, and play AVI files with new codec, you will get an MCI (Media Control Interface) error stating something "... driver not found" or "... not installed". Also, it incorporates routines to speed up display updates by writing directly to video memory; some video cards may
be incompatible with this enhanced scheme.

Download VFW11A.exe; run it in a temporary directory; it is self-extracting. Then run it's setup.

IMPORTANT:
If you currently installed VFW 1.0 and are dependent on running files for a business or
presentation in the near future, prudence dictates that you back up your entire \windows
and \windows\system directory so that you can restore your entire setup.


How do I know the drivers are installed?

Use a text editor or viewer in DOS, NotePad or SysEdit in Windows and view your SYSTEM.INI
file. You should see the following in the [drivers] section. If it is there then you have installed
"correctly". You should be able to locate the *.DRV files in your \windows\system dir.

[drivers]

VIDC.MSVC=msvidc.drv
VIDC.RT21=indeo21.drv
VIDC.IV31=ir30.dll
VIDC.IV32=ir30.dll
VIDC.CVID=iccvid.drv
VIDC.MRLE=msrle.drv
VIDC.YVU9=indeov.drv

Note: More drivers will appear with succeeding updates.

My SYSTEM.INI drivers refer to the same VIDC.???? driver. Is this causing incompatibility?

If all the "VIDC.????=" entries refer to the same driver (e.g., VIDC.????=ativdacc.drv) then your system uses proprietary multimedia accelerator interceptors/drivers. Generally, the interceptor speeds up your display updates and should not be a problem (but one never knows).

If you suspect incompatibility with your multimedia interceptor/driver restore all the "VIDC.????=" entries to defaults.

a. Backup your SYSTEM.INI file to SYSTEM.BAK (e.g., copy SYSTEM.INI *.BAK).

b. From the list above (see #3) copy all "VIDC.????" entries and replace them
with the specific drivers referred to; this will effectively remove the interceptor from the loop.

Is my video card incompatible ?

To isolate variables related to your video driver, change your Windows video setup to VGA 640x480 (16 colors). AVI files should playback, albeit more slowly, possibly jerky and only with 16 colors (dithered too). Try other video modes and see which one works or doesn't. If specific modes don't playback correctly, then you need updated/corrected drivers from your card's manufacturer. Also, if you video card requires a "memory aperture" try turning it off to see if that is causing a problem.

Insufficient Windows memory?

Newer codecs may require more memory (actually there not swapped to disk). Free all possible
Windows memory by closing all open applications. If the AVI file plays then "insufficient memory"
was the issue. Note: You MUST have 4MB to begin with and be running in 386 Enhanced mode.

Multi-tasking interactions with other apps?

Playback of AVI files is CPU intensive. Free all possible Windows resources by closing all open
applications - particularly DOS sessions, screen savers, clocks, schedulers, e-mail, fax,
communications apps, "green"/power savers, and anything requiring a timer or is in the background. If the AVI file plays then you've isolated interactions with other Windows apps. One or several of those concurrent apps caused an incompatible interaction.

Hard Disk/CDROM caching ?

Generally there should not be a problem with SMARTDRV; the worst case is less extended memory (see "Insufficient Windows memory?" above) or jerky playback.

To isolate problems related to caching:

a. Backup your CONFIG.SYS and AUTOEXEC.BAT; copy it to *.BAK.
b. Delete any caching driver (eg., SMARTDRV) from your CONFIG.SYS or AUTOEXEC.BAT file.
c. Reboot you computer; restart Windows and try playing your AVI file again.

32-bit drive access?

Depending on your hard disk, disk controller, non-standard DOS driver, and bus type
(eg., VLB, PCI, ISA, EISA), a combination can exist that may be incompatible with AVI playback.

Activate your Control Panel. Activate the 386 Enhanced icon and TURN OFF 32-bit access. If that resolves your problem then it had to do with one of the components in the hard disk sub-system(s).

Compressed drives.

Ensure that you are not playing AVI files from compressed drives (eg., DoubleSpace, Stacker, ...).
The device driver will interfere with rapid data transfer. Always place AVI files in the uncompressed
drive for playback.
so that you can restore your entire setup.


How do I know the drivers are installed?
wtplchd`\IXTjPzLzwCsEoBkDg
cv
_
[
WS^OKwsok%gHc_X[|WSOKws2o4k^g`c_`[WSOK+wBsokgd3`\XT P L K wU s| o k g c-!_1![
"W!"S"O"K""w"s"o#k#g)#c#_#[%W.%SF'OT'KT'W(w(s)oC*k*g*c{-_-[/W/S0O1K12w2s4o4k/6gA6c&7_-[/W/S0O1Kcehj|~EBBDBD


2
H
]
t
v








4H\^#%%HD
F



!,79KM~)448CGRvx24`UW469s4^`)Y02CEz3xQ~)+@Bcee K | /!1!!!
"""!"L"N"""""""""""##'#)#####%%0%2%2%&&&D'F'S''(S(U(W((((E)))))))))**-*C*E*~****++q,s,,,-y-{-{---////0w00011f112222333333F444445e5g5-6/6C6E667&7(73f=/2!898(d DOS driver, and bus typ6C6 EISA), a combination can exist that may be incompatible with AVI playback.

Activate your Control Pan Arial the 386 Enhanced icon and TURN OFF 32-bit access. If that resolves your problem then it had to do with one of theVIDVUE v3.0
Copyright 1993-1994 Lawrence Gozum
All rights reserved.


SUMMARY:

VIDVUE is an easy-to-use Multimedia player/slideshow/viewer/utility
distributed as 100% Functional Shareware.

It fully supports FULL-FEATURED 89a and 87a GIFs with, probably, the fastest
decode-to-screen Window routines (80x86 assembly). Includes Full Screen
decoding and full support for JPG/JIF, BMP/DIB, PCX, TIFF, TGA and DCX
formats, plus, raster image support for WPG, EPS and PICT files - and, full
vector support for WMF files. Comment viewing, with many options, for GIF
and JPG/JIF files is also supported.

It plays AVI video, WAV audio, MIDI music, FLI/FLC animation files and
APple Quicktime MOVies. AVI and MOV playback can be fully scaled in a
sizeable window. Includes AVI frame grab function to import and save
AVI and MOV frames to other formats.

Multimedia slideshows (w/ all formats) can be played with marked files and
user scripts. Includes Shuffle Play, AutoCenter, AutoDither, AutoSize,
variable delays and backgrounds and AVI scaling, special GIF processing,
plus other features PER SLIDE! Plays WAV and MID files with displayed
images. Unlimited slides (as many as you want).

Conveniences include last file(s) recall (up to eight files); last
drive/directory recall and last desktop position recall.

Image printing on B/W printers supports error-distributed dithering for
superior gray shades. Interface includes a simulated document to resize and
position image on paper before printing.

Special image processing includes 'hotspot removal' for converting GIFs to
BMP Wallpaper without the "burnt colors", and PackVideo, for enhancing video
frame captures and resizing.

VIDVUE also converts file formats, sharpens, smoothens, adjusts contrast
and brightness, resizes, flips/rotates, dithers, reduces colors, converts
to gray, and copies DIBs to/from clipboard, among other features.


REQUIREMENTS:

Required: Windows 3.1 running in Enhanced mode and VBRUN300.DLL.
********* Browse/search for "VBRUN" to check availability in any forum/RT,
or check local BBSs for VBRUN3.ZIP or VBRUN300.ZIP.

Optional: Installed Video for Windows (VFW) runtime for AVI playback.
Browse/search for "VFW" to check availability, or check local
BBSs for VFWRUN.ZIP or VFW11A.ZIP.

Optional: Installed MCI drivers for WAV and MIDI playback.
These come with your sound card.

Optional: Installed MCI drivers for FLI/FLC playback.
At CIS, download NEWPLA.ZIP from GO ASOFT
or WAPLAY.EXE from GO GRAPHSUP.
At GEnie, download AAWIN11.ZIP from CYBERSPACE RT;
or check local BBSs for AAWIN11.ZIP (or later).

Optional: Installed MCI drivers for MOV (Quicktime for Windows) playback.
You most likely have installed MCI drivers for Quicktime for
Windows (QTW) playback, if you purchased and are currently using:

Adobe Premiere 1.0 (or later) for Windows
Macromedia Action 2.5 (or later) for Windows
Macromedia Authorware Pro 2.0 (or later) for Windows

If you have a CDROM and several CDROM titles, you may already have
the QTW runtime files, VIDVUE's README.WRI file details how to
setup for MCI playback.

At CIS,

1. GO MACDEV.
2. Download LICENS.TXT from Library 8.
3. Read and abide to terms and conditions in LICENS.TXT.
4. If you agree to LICENS.TXT, then download
QTDSK1.ZIP and QTDSK2.ZIP.

Note: QTDSK1.ZIP and QTDSK2.ZIP are NOT distributable files.
Only YOU can download and use them (see LICENS.TXT).
READ THE README.WRI FILE IN QTDSK1.ZIP.


VIDVUE 3.0 Update

o Added DDE capability to show images or play multimedia files
via one instance of VIDVUE. Source code is included for writing your
own VB app to display/playback graphics and multimedia files via VIDVUE.

o Enhanced virtual memory management.

o Added conversion to Promote 256-color to 24-bit color process.

o Added conversion to Promote 16-color to 256 color process.

o Added conversion to Promote B/W to 256 color process.

o Added 32-bit AVI and MOV (Quicktime MOVie) grab support.

o Added "On-the-Fly" Gamma error adjustment for displayed images.

- Variable adjustment ranges between 0.01 to 1.99.

- "On-the-Fly" preview/feedback of results; imagesa can be saved
to any supported format with adjustments.

- Supports 256-color, gray shade and True-color (24-bit) images.

- Device-independent, works on image "in memory" regardless of
current video mode (eg., will work on VGA 16-color mode while
adjusting True-color (24-bit) images.

- Independent slideshow image support; can be adjusted/set for
EACH slide in your multimedia slideshow. Great for viewing
read-only images (ie., from CDROM) that come from different
sources/originators using different monitors/video cards.

o Enhanced JPEG/JPG/JIF 24-bit encoding; suberb image quality
at greater compression levels!

o Added JPEG/JPG/JIF 8-bit encoding for saving files with 256 gray shades;
automatically promotes and saves 256-color images.

o Added Kodak PHOTO-CD support.

- Supports maximum resolution of 2048x3072.

- Automatically reduces resolution to next base level if memory
resources are running low (eg., switches to 512x768x16M if
1024x1536x16M image cannot fit in memory).

- Fully integrated with all Automatic options (eg., AutoSize and
AutoDither) and Slideshow options/keywords.

- Fully integrated with AutoDither option; uses Kodak's FAST dithering
routines; if AutoDither is set,it will dither/reduce color depth to
256-colors or 16-colors depending on user's video driver.

o Multiple-image support; quickly views multiple-image "documents" with
VARIABLE PAGE SIZES (eg., half-page fax cover at 100 dpi low resolution
with legal-size documents at 200 dpi high resolution plus a drawing at
non-standard, 300 dpi "SuperFax" resolution).

- Multiple-image DCX (Intel format) support;
- Multiple-image TIFF support; very fast CCITT, G3, G4 decoding.

o Added SPEAKER.DRV support for WAV playback. Users without sound cards
can now enjoy WAV playback via the generic PC speaker driver. Slideshow
support is also included.

o FLI device drivers are now verified prior to first playback during any
session and optimal initialization procedure is used.

o WAV device drivers are now verified prior to first playback during any
session and optimal initialization procedure is used.

o Added fast WAV file "browser" to immediately play a selected file from
the file list box; it plays immediately and instantly terminates with
next selection to be played.

o Added convenient recall of Load drive/directory during session.

o Added convenient recall of Save drive/directory during session.

o Added convenient recall of Save file format during session.

o Added convenient recall of Load file format during session.

o Added automatic File Recall exit from File Save mode (if active) to
immediately view selected image; great for iterative JPG saves to
experiment with optimal quality vs. size setting.

o Added full Font dialog for selecting the font, font style and font size
for comment text viewing (remembered during the entire viewing session).

o Increase AVI slideshow scaling to 300% to account for faster multimedia
accelerators and CPUs.

o Optimized AVI and MOV/Quicktime playback (normal and slideshow mode);
modified to take advantage of multimedia accelerators and 64-bit cards.

o Bugfix: AVI and MOV grabs did not capture correctly in HiColor, and
24-bit video modes with new 64-bit video cards and multimedia
accelerator drivers; corrected.

o Bugfix: Last file recall update to last 8 files did not update correctly
on some systems configurations; corrected.


VIDVUE 2.4 Update

o Added Clipboard DIB Support.

- Copy DIB to Clipboard
- Paste DIB from Clipboard
- Empty Clipboard

o Added Quicktime (*.MOV) movie support.

- Virtually, all AVI (Video for Window) functionality implemented.
- Complete Slideshow support/integration.
- Quicktime (*.MOV) movie frame grab function (similar to AVI grabs)
for importing and exporting graphic frames to different file formats.

o Added HiColor DDB (device-dependent bitmap) support for grabbing
32K-color and 64K-color AVI (with VFW 1.0 or VFW 1.1 runtime) and MOV
(Apple Quicktime) movie frames; includes DDB support for 5/5/5, 5/6/5,
6/5/5 and 6/6/4 display modes.

o Control Window is now "Always On Top" when showing AVI, MOV (Quicktime)
or FLI/FLC animation to account for increasingly large video frame
sizes (eg., 640x480).

o Added "RIFF walker" for FAST AVI file info.

o Added "RIFF walker" for FAST WAV file info.

o Added File Date field to all File Info functions.

o BUGFIX: Resizing of images with systems low on memory triggered
a DLL missing error; corrected.

o BUGFIX: Monitor Contrast and Brightness adjustments updated incorrectly
in Viewing Window AFTER decoding a GIF to Full Screen; corrected.

o BUGFIX: VIDVUE's Setup trigerred an error during install with
Windows for Workgroups; corrected.

o BUGFIX: With VFW 1.1 runtime, playing AVI files WITHOUT an audio track
trigerred an MCI error; corrected.

o BUGFIX: With VFW 1.1 runtime, playing AVI slideshows trigerred a GPF
when palette updated on some systems in 256 color modes; corrected.

o BUGFIX: Ending slideshow by clicking on screen sometimes trigerred an
MCI error depending on speed of CPU and transfer rate of data; corrected.

o BUGFIX: Setup still caused an error on European systems using various
characters for date delimiters (eg., 5.28.94); corrected - totally
removed date dependencies in setup.


IMPORTANT:

Please ensure that VBRUN300.DLL is in your Windows directory or
Windows System sub-directory before running SETUP.EXE from Windows.

To install, select "Run" from the Program Manager menu bar then enter
the pathname and "SETUP". For example, if you extracted the files
into "e:\test" then type "e:\test\setup".

VIDVUE's Setup now provides an option to setup ALL files in it's specified
application directory.

IN THE UNLIKELY EVENT YOU HAVE SETUP PROBLEMS, PLEASE READ INSTALL.TXT.

The following files MUST be included in this distribution set.
**************************************************************

README 1ST This file.
INSTALL TXT Notes on VIDVUE Setup.

SETUP EXE Setup program
LG_SETUP DLL

VVU EXE THESE FILES ARE IN YOUR VIDVUE DIRECTORY
VIDVUE EXE
DEMO TXT \
TRAVIATA TXT > Skeleton Slideshow scripts
JMPSTART TXT /
VVUDDE MAK \ DDE VB sample code
VVUDDE FRM /
GAMMA BMP --> Test file for gamma adjustment
README WRI --> Read this!
VIDVUE HLP --> VIDVUE Help

VIDVUE DLL THESE FILES ARE PLACED IN YOUR VIDVUE DIRECTORY
ACCUVB16 VBX OR, OPTIONALLY IN THE \WINDOWS\SYSTEM DIRECTORY
MDICHILD VBX
SUBEZ VBX VIDVUE WILL NOT RUN IF ANY OF THESE ARE MISSING!
THREED VBX
IMVBX3 VBX
VBCTL3D VBX
CMDIALOG VBX
PCDLIB DLL
IM2PCX DIL
IM2TIFF DIL
IM2XJPEG DEL
DIB DRV