These useful documents are straight from the technical support staff
at Iomega. They go into detail
on some of the hardware and configuration issues regarding Buz. I did
not write these; I got them from Iomega and added a little HTML
formatting. Please consider sending some email to Iomega and
letting them know how useful you find in-depth information and help
documents such as these.
Index
- Field Reversal/Order Problem
- Video Jitter
- Ultra SCSI Configuration
- S3 Vision 968/868 memory bug
- Resetting the Extended System Configuration Data
- AMIBIOS
- Phoenix Technologies
- Award BIOS
- PCI 2.1 Compliance, Bridge Chip Support and Multifunction Cards
- Optimizing the PC for video capturing performance
- High Quality Settings:
- Capture Settings
- Generic:
- Windows 95 Settings
- Reserving Interrupt Requests with the Buz Multimedia Producer
- How to Boot from a SCSI drive
- How to select a SCSI boot drive
- Booting from Removable Media
- Buz Drivers Version 1.2 Installation Instructions (4/28/98)
- How to install the drivers
- Changes in this Version of the 1.2 driver
- Field Reversal
- Secam Support
- Still Frame Capture in RGB Format
- The Iomega Corp. Buz Beta Release 1
- Buz and Third Party Codecs
1: Field Reversal/Order Problem
This problem presents its self when capturing video and adding an
effect like text to a segment in the video and then produce the clip.
The Field Reversal/Order Problem is most noticeable when the objects
in the video clip have diagonal lines. Vertical and horizontal lines
in video clips don't show the problem. "Stair stepped or Jagged" edges
tend to show up in video clips that have been produced. Installing
the new 1.2 driver will fix this problem.
2: Video Jitter
The known issue with "Jittering" is caused by the "3-2 Pulldown" when
using Hollywood Video Industry formatted tapes or sources. This is
common among all analog video capturing boards in the computer
industry.
This situation can be seen when a single image from an interlaced
Motion JPEG AVI video file, (640x480 or 720x480), is opened on the
computer display and a monitor is attached to the output of the Buz
Box. The image that is displayed on the output monitor appears to
shake or jitter while the video is paused or stopped.
The Jitter effect is known in the Video Industry as "3-2 Pulldown".
The problem is evident only in interlaced video footage captured from
a video source that was re-mastered from a "Hollywood" movie. The
movies made by the Professional movie studios are generated at 24
frames per second vs. 30 fps for video capture boards. Altering of
Hollywood movies from the 24 fps to 30fps for VHS, DVD, and Laser Disc
formats is required to support these devices. The alteration process
is done in this manner, for every four frames of actual video a fifth
frame is generated. Estimation of the difference between 24 fps to 30
fps is used to generate frame. Thus when the video is digitized, with
interlacing (640x480 or 720x480), the effects of this generated frame
are apparent. The Jitter problem can be corrected by using devices
that create a 30 fps format such as a camcorder, footage from a
camcorder tape or a NTSC TV.
Conclusion
The effects of "3-2 Pulldown" should only be apparent when the frame
of video is paused or is stopped on the screen. The human eye can not
detect the generated frame while playing video from any source because
the refresh rate is fast enough that the can not detect it.
3: Ultra SCSI Configuration
- Boot the Computer.
- The AdvanceWare screen appears immediately after the system starts
to boot up. Press Ctrl-A. when the light blue AdvanceWare block
appears.
- Select Adapter Configuration when the AdvanceWare menu appears,
using the up/down arrows on the keyboard and press Enter or
Spacebar.
- Select Ultra SCSI Feature in Adapter.
- Enabled the Ultra SCSI Feature by highlighting then press Enter
or Spacebar.
- Press Esc until you return to the main menu, then select Write
Setup and Exit, select Yes to Write the configuration and exit. This
will save the changes you have made. The AdvanceWare utility will
automatically reboot the system, allowing the configuration changes
to take effect.
4: S3 Vision 968/868 memory bug
Erratic system behaviour can occur if an S3 968/868 based video card
and a Buz Multimedia Producer installed on a PC. The problem is
caused by the S3 Vision 968/868 video controller, which is used on the
Diamond Stealth 64 Video 3000 series, Number Nine 9FX motion 771, and
other popular video cards, all contain a memory bug. This bug may
cause problems with the Buz Multimedia Producer. The 968/868 claims to
require 32 MB of memory, but it actually decodes 64 MB of memory. The
Buz Multimedia Producer can be mapped by BIOS and/or Windows 95 into
the 968/868 memory decode address. To solve this problem Buzdiag.exe
detects and adjusts the memory range of the Multimedia Portion and/or
the SCSI portion of the Buz card away from the S3 Vision 968/868.
If Buzdiag.exe fails to resolve the conflict you can manually adjust
the memory range by following the steps listed below:
How to view the memory ranges
- Right click on My Computer
- Select properties
- Select the Device Manager tab
- Expand the display adapters tree (click on the plus sign)
- Double click on the video card
- Select the Resources tab
- Scroll down the Resource Settings and write down the memory range
- Click cancel
- Expand the SCSI controllers tree
- Double click on the Iomega Buz PCI Ultra SCSI Host Adapter
- Select the Resources tab
- Write down the memory range
- Click cancel
- Expand the Sound, video and game controllers tree
- Double click on the Iomega Buz Multimedia Producer
- Select the resources tab
- Write down the memory range
- Click cancel
- If the video card has the memory range of F0000000-F1FFFFFF the
Buz SCSI or Multimedia devices will likely get F2000000-F2FFFFFF.
This is a conflict because the video card is actually using
F0000000-F2FFFFFF.
To adjust the conflicting device by
- Select the Device Manager tab
- Expand the corresponding tree (click on the plus sign)
- Double click on the conflicting device
- Select the Resources tab
- Uncheck use Automatic Settings box
- Double click on the Memory Range
- Use the scroll bars to adjust the memory range. In the example the
video card is using F0000000-F2FFFFFF. So adjust the conflicting
device to F3000000-F3FFFFFF
- Click Ok
- Reboot
Windows 95 will reconfigure the devices to work with each other.
5: Resetting the Extended System Configuration Data
The BIOS stands as the first link between hardware and software in
coordinating the startup configuration of computers. A Plug and Play
BIOS automatically configures the computer's hard drives, disk drives,
processors, chipsets, interrupts, and memory configurations. This
information, which is refereed to as Extended System Configuration
Data (ESCD), is stored into NVRAM. A NVRAM device maintains the ESCD
to provide the Plug and Play operating system a constant configuration
every time the computer is turned on or reboot once the systems is
properly configured. If you install the Buz card and notice a
hardware conflict or erratic behavior, reset the ESCD. Listed below
are the procedures of how to reset the ESCD for different BIOS
manufactures.
Note:
Also See: Buz CLCA White Paper "I2VXINI Not Responding" for
additional methods of resolving system resource conflicts.
Creating a PnP environment:
Process for Freeing up system Resources
NVRAM #ESCD##BIOS Manufactures Procedure
AMIBIOS
- Shut down the computer
- Install the Buz card.
- Hold Down the INS key.
- Turn On the Computer.
- You should on the screen NVRAM cleared, and it should not appear
again
- Start Windows 95
Phoenix Technologies
- Shut down the computer
- Install the Buz card.
- Go into the BIOS Setup and find a field labeled, "Reset
configuration data."
- Set this field to "yes".
- Save and exit the Setup program. The system restarts and clears
ESCD during POST.
- Windows 95 will automatically configure your system and load ESCD
with the new data.
Award BIOS
- Shut down the computer
- Install the Buz card
- Go into the BIOS Setup and find a field labeled, "Reset
configuration data"
- Set this field to "Yes"
- Save and exit the Setup program. The system restarts and clears
ESCD during POST.
- Windows 95 will automatically configure your system and load ESCD
with the new data.
- Continue with the installation
Note: Some PC manufactures developed their own BIOS software. Please
contact your computer manufacture for more information.
6: PCI 2.1 Compliance, Bridge Chip Support and Multifunction Cards
The Iomega BUZ card is a Multifunction PCI card. This means that
Iomega has taken the function of two PCI cards and integrated those
functions on one card.
Iomega customers benefit by getting two completely independent
functions that take up only one PCI card slot in their computer.
Video Capture and Playback are done by the built in video chip set
with resolutions up to 720x480 @ 29.97 fps. The Ultra SCSI adapter
will provide 20MB/sec data rates and support any standard SCSI device,
Jaz drive, Zip drive, hard drive, scanner, and etc.
Iomega engineering followed PCI Local Bus Specification 2.1 in the
design of this card for reliable operation and multifunctional device
support. This specification is the industry standard for the PCI 2.1
communication bus on the motherboard. Computers and PCI devices (like
BUZ card) that fully support PCI 2.1 will work together. The
component on the Iomega BUZ card that allows multifunction performance
is a "Bridge" chip. The bridge chip connects your computers PCI bus
to the Video and SCSI controllers on the BUZ card. The bridge chip
has an internal traffic cop that allows PCI bus communication to only
one of these controllers at a time.
The Iomega BUZ card must be connected to a computer that supports
Multifunction PCI cards which is 2.1 PCI specifications or it will not
operate correctly. Most of the computers that Iomega identified as not
BUZ compatible are due to the inability of these computers to support
any PCI multifunction cards, including BUZ. The great majority of
computer manufacturers follow PCI Local Bus Specification 2.1. Some
manufacturers have not instituted all of the needed design
requirements on all of their models. Some PC manufactures only
configured one PCI slot to meet 2.1 PCI Compliance. This means that
Buz customers will have to locate the one PCI slot that supports 2.1
PCI Compliance and install the Buz card into it. Examples of the way
manufactures do not support the needs of multifunction cards are;
insufficient number of interrupt (IRQ) lines connected to the PCI
expansion card slots or the computers BIOS does not support
multifunction cards.
7: Optimizing the PC for video capturing performance
High Quality Settings:
Capture Settings
- 720 X 480 @ 29.97 fps
- Use S-Video source and High Quality Cables
- S-VHS tapes and decks
Generic:
64 MB of Ram is ideal
- Optimize Capture Drive by:
- Scan for disk errors
- Defragment
- Close all other applications
- Exit all applications that load automatically during boot
- Disconnect from Network
Windows 95 Settings
-
Change "Read ahead optimization" to "None" on the slider.
Settings/Control Panel/System/Performance/File System
-
Select "Disable write-behind caching for all drives".
Settings/Control Panel/System/Troubleshooting
-
Un-select "Audio Insert Notification".
Settings/Control Panel/System/Device Manager/CD-Rom/Settings
-
Select DMA whenever using U-DMA drives.
Settings/Control Panel/System/Performance/Device Manager/Disk Drives/Disk Drive
8: Reserving Interrupt Requests with the Buz Multimedia Producer
Standard computer systems have only sixteen Interrupt Requests. This
document was written to resolve conflicts with interrupt requests.
One way is to reset the NVRAM; this option is only available if your
BIOS support this feature. Another way is to manually reserve
Interrupt request in the BIOS and/or Operation System (OS) before
installing the Buz card. Modifying resources using Windows 95 is not
always going to work because not all devices are dynamically
configurable. It might be necessary to remove or disable unused
devices to free up extra Interrupt Request.
Note:
Only computers with Windows 95 OSR2 or higher can have PCI devices
sharing the same Interrupt Request.
Using the systems BIOS to reserve Interrupt Request
- Install the Buz card
- During boot up enter BIOS setup (This is different for each
system.)
- In the BIOS setup go to the PCI/PnP configuration (This is
different for each system)
- You should see a list of Interrupt Requests and DMA channels. The
Interrupt Requests have 2 different settings, PCI/ISA PnP and Legacy
ISA. If set to PCI/ISA PnP allows the BIOS so assign an Interrupt
request to the device. If set to Legacy ISA this interrupt is not
used unless a device specifically calls for it or the operation
system assigns a device to it.
Using Windows 95 to reserve Interrupt Request
- Make sure you don't have the Buz card installed.
- You can skip this section if you have not installed the Buz card
before
- Uninstall by using the maintenance setup.
- Go to Device Manager (Click Start on the Taskbar, Choose Settings,
Control Panel, double-click on System and Click on the Device Manager
Tab)
- Expand the SCSI controller tree (Click on the + sign to the left)
- Remove the "Iomega Buz PCI Ultra SCSI Host Adapter"
- Turn off your computer.
- Remove your Buz Card.
- Start Windows 95
- Go to Device Manager (Click Start on the Taskbar, Choose Settings,
Control Panel, double-click on System and Click on the Device Manager
Tab)
- Double-click on "Computer" at the top of the list.
- Click on the Interrupt Request radio button
- Scroll down and note which Interrupt Requests that have PnP
devices
- Click on the Reserve Resources Tab
- Click on Interrupt request radio button
- Click on the Add Button.
- Select The Interrupt request you would like to reserve (Buz
requires two interrupt requests so add two if applicable).
- Reboot your computer
- Go to Device Manager note if any devices are in conflict with
your reserved resources
- You can skip this section if there is no conflicts found in Device
Manager
- Select the device with the conflict
- Click on Properties
- Click on Resources Tab
- Click on Set Configuration Manual button and/or Uncheck the Use
Automatic Settings check box.
- Double-click on Interrupt request under Resource Type
- If you are unable to modify the value leave everything the same
and follow Method One to try and move it during boot up.
- If you were able to change the value to an open Interrupt Request.
Make sure Use Automatic Settings is not check.
- Click Ok.
- Reboot
- Return to Device manager to verify that your setting were resolved
the problem.
- Double-click on Computer at the top of the list.
- Click on the Reserve Resources Tab
- Click on Interrupt request radio button
- Delete all Reserved Interrupt Requests
- Reboot and continue with the Buz install.
9: How to Boot from a SCSI drive
Many of the new motherboard BIOS have functions that allow the user
to choose the PC boot device. (IDE, SCSI, floppy, network, CD-ROM,
floptical.) Older motherboard BIOSs look for IDE drive before
SCSI drives to boot from therefore no IDE or ATAPI hard drive can be
connected to the motherboard if trying to boot from a SCSI drive.
How to select a SCSI boot drive
The Buz card will try to boot from the lowest SCSI No. by default.
If you have multiple SCSI IDs and you do not want to boot to the
lowest ID on the SCSI chain.
- Reboot, if the computer is on.
- Press Ctrl-A, when the light blue AdvanceWare block appears on the
screen, immediately after the system starts to boot.
- Select SCSI Configuration from the menu, using the up/down arrows
on the keyboard and press Enter or Spacebar.
- Go to the BIOS Target Control line in the SCSI. The computer will
not boot from a SCSI ID that has No selected, but the computer can
still access and the device and it will function properly. Select
Yes to in able booting capabilities for that device.
- Press Esc until the main menu screen is displayed, then select
Write Setup and Exit, select Yes to Write the configuration and
exit. This will save the changes you have made. The AdvanceWare
utility will automatically reboot the system, allowing the
configuration changes to take effect.
Booting from Removable Media
- Reboot, if the computer is on.
- Press Ctrl-A, when the light blue AdvanceWare block appears on the
screen, immediately after the system starts to boot.
- Select SCSI Configuration from the menu, using the up/down arrows
on the keyboard
and press Enter or Spacebar.
- Select Adapter Configuration, using the up/down arrows on the
keyboard and press Enter or Spacebar.
- Select Removable Media Support in Adapter Configuration.
- Change the Removable Media Support by highlighting Enabled then
press Enter or Spacebar.
- Press Esc until you return to the main menu, then select Write
Setup and Exit, select Yes to Write the configuration and exit. This
will save the changes you have made. The AdvanceWare utility will
automatically reboot the system, allowing the configuration changes
to take effect.
General Note:
Occasionally the Operating System dislikes having the SCSI adapter
assigning the drive letters. Force the adapter to assign the first
drive letter and let the Operating System assign the rest.
- Reboot, if the computer is on.
- Press Ctrl-A, when the light blue AdvanceWare block appears on the
screen, immediately after the system starts to boot.
- Select Adapter Configuration, using the up/down arrows on the
keyboard and press Enter or Spacebar.
- Select Multiple Drive Support in Adapter.
- Change the Multiple Drive Support by highlighting Disabled then
press Enter or Spacebar.
- Press Esc until you return to the main menu, then select Write
Setup and Exit, select Yes to Write the configuration and exit. This
will save the changes you have made. The AdvanceWare utility will
automatically reboot the system, allowing the configuration changes
to take effect.
10: Buz Drivers Version 1.2 Installation Instructions (4/28/98)
How to install the drivers
- UnZip the Buzupdate file:
- Double click on the file "Buzupdate"
- Select UnZip from the WinZip Self Extractor window
- Write down the directory where the file is extracted
- Select "OK" after the WinZip Self Extractor window appears
- Close the WinZip Self Extractor window
The Buzupdate file will extract three files:
-
Click on the "Windows Start" button. Select "Settings", "Control
Panel". Double click on the "System" Icon and then select the "Device
Manager" Tab. Expand the "Sound, video and game controllers" tree by
clicking on the "+" sign to the left. Click the "Iomega Buz
Multimedia Producer" item and then click "Remove". Select the "Yes"
button to complete removal of the device.
Or
Open "Device Manager" by holding down the Alt key and double clicking
on "My Computer". Select the "Device Manager" tab and then double
click on "Sound, video and game controllers" icon. Single click on
the "Iomega Buz Multimedia Producer" and click on "Remove". Select
the "Yes" button to complete removal of the device.
-
Open Windows Explorer by clicking "Start", then "Programs" and then
"Windows Explorer". Select the drive and directory where the Buz
Drivers were expanded. Double click on the "Buzup" file to start
the extraction process in the "Buz" folder.
-
After the Update is complete, Close the "BUZUP" Window (if still
open) and then Restart your computer by selecting "Start" then "Shut
Down" and then choosing the "Restart the Computer" option.
-
Windows will display the Found New Hardware dialog box, for the
"Iomega Buz MultiMedia Producer" after the restart. If prompted for
the driver files (inf file), select "Browse" and then choose the
drive and directory where the update was extracted to, then click
"OK". Click the "Finish" button and then "Yes" to restart the
computer when prompted.
-
Buz Display Diagnostics will run after restarting the computer.
Answer the dialog windows when prompted to complete the driver
update. The process is similar to the first time the Buz was
installed on the computer.
Changes in this Version of the 1.2 driver
There are several changes in this version. They are listed below:
Field Reversal
There was an issue found when a capture was done, at 720x480
resolution, and then this clip was produced at the same resolution.
The resulting clip would "jitter" during play back. This problem was
caused by the Buz driver rebuilding the produced file with the video
fields in the reverse order of the way they were captured. This issue
is solved in Version 1.2.
Note: This Version does not solve an issue known as "3:2 Pulldown".
Video Jitter
The known issue with "Jittering" is caused by the "3-2 Pulldown" when
using Hollywood Video Industry formatted tapes or sources. This is
common among all analog video capturing boards in the computer
industry.
This situation can be seen when a single image from an interlaced
Motion JPEG AVI video file, (640x480 or 720x480), is opened on the
computer display and a monitor is attached to the output of the Buz
Box. The image that is displayed on the output monitor appears to
shake or jitter while the video is paused or stopped.
The Jitter effect is known in the Video Industry as "3-2 Pulldown".
The problem is evident only in interlaced video footage captured from
a video source that was re-mastered from a "Hollywood" movie. The
movies made by the Professional movie studios are generated at 24
frames per second vs. 30 fps for video capture boards. Altering of
Hollywood movies from the 24 fps to 30fps for VHS, DVD, and Laser
Disc formats is required to support these devices. The alteration
process is done in this manner, for every four frames of actual video
a fifth frame is generated. Estimation of the difference between 24
fps to 30 fps is used to generate frame. Thus when the video is
digitized, with interlacing (640x480 or 720x480), the effects of this
generated frame are apparent. The Jitter problem can be corrected by
using devices that create a 30 fps format such as a camcorder,
footage from a camcorder tape or a NTSC TV.
Conclusion:
The effects of "3-2 Pulldown" should only be apparent when the frame
of video is paused or is stopped on the screen. The human eye can
not detect the generated frame while playing video from any source
because the refresh rate is fast enough that the can not detect it.
Secam Support
This version enables Secam video format support for capture. The
captured file must then be produced to Pal to be output back to tape.
Still Frame Capture in RGB Format
Still frame captures in RGB format would result in black BMP's. This
issue is solved in Version 1.2.
The Iomega Corp. Buz Beta Release 1
The word "Beta" is removed from the Manufacture General Tab in Device
Manager.
11: Buz and Third Party Codecs
Iomega does not support third party codec(s) with Buz Multimedia
producer these drivers are not the same as ours. Some third party
codecs do break VideoWave because there is no API interface for the
silent settings. Use of a third party MJPEG hardware codec will not
provide full functionality for the Buz card, and third party codecs
could damage the board because the drivers were not designed for our
chipset. Use of the third party codex could void the warranty on Buz.
The following codec(s) are known to be used with Buz:
| Company:
| Paradigm Matrix M-JPEG Codec
|
| Software Name:
| Paradigm Matrixs software/hardware codec
|
| Version:
| Release Version 1.10N February 28,1998
|
| Notes:
| This codec is developed for MJPEG editing. A central computer
with MJPEG hardware support captures the video clips and other
computers edit the video with this codec. It is unknown what the
quality of the video is when edited with this codec and ported back
to Buz.
|
- During video capture, playback, and previewing edits no video was
sent through the output of the Buz card.
- During playback the hardware was not used. This caused very poor
video playback quality.
FAQ Last modified: Mon May 18 05:01:24 1998
Steve
Haehnichen