To reset to the automatic color balance setting, double-click on the image with the right mouse button (with control key on Mac OS).
If the lighting in the scene is unusual (i.e. at sunset or with stage lighting), try setting "Color|Color balance" to "Neutral".
Using Scanner as Copier
Working with Scanned Images
VueScan is designed to save scanned images to JPEG files (by default) or TIFF files (optionally).
You can configure your favorite image editing program to automatically open each image when a scan completes. Use the "Prefs|External viewer" option to control this.
On Mac OS X, you can set up the default viewer for .tif and .jpg files by:
On Linux, use the "Prefs|Viewer" option to select the application to use to view .tif and .jpg files.
Scanning Roll of Film
If you're scanning many frames from the same roll of film, the following procedure will optimally set the CCD exposure and film base color (i.e. mask color):
To scan multiple images in a batch, set "Input|Batch scan" to "All" to scan all frames in a device, or set it to "List" and type in the list of frames (i.e. "4 3 1" for frames 4, 3 and 1, in that order).
For more information, refer to the VueScan User's Guide.
What's new in version 9.4.08
VueScan supports more than 2300 different scanners on Windows, 2100 scanners on Mac OS X and 1900 scanners on Linux. These scanners are organized by vendor name below.
If your scanner isn't on this list, VueScan may still work with your scanner if you can find a WIA driver (Windows) or an Image Capture driver (Mac OS X) on the scanner manufacturer's web site.
Please note that not all scanners work with all operating systems or SCSI/USB/Firewire interfaces, but most combinations are known to work. The best way to find out for sure if VueScan works with your scanner, operating system and interface is to download the trial version of VueScan from www.hamrick.com.
On Mac OS X, VueScan works with most USB to SCSI converters, including the Adaptec USBXchange and USB2Xchange. VueScan also works with most Firewire to SCSI converters. You don't need to install any vendor software to get this to work. Only one SCSI device per converter is supported, and you should use SCSI ID 0 with USB to SCSI converters.
VueScan supports raw scan files for the digital cameras in the following list. However, note that the colors may will be more accurate if you use an IT8 camera target (like the one produced by Wolf Faust) and if you use VueScan's "Profile|Profile scanner" command to create an ICC file for your camera.
**There is a program available that will enable raw files on these Canon digital cameras.
If VueScan doesn't see your scanner on Mac OS X, first make sure that Apple System Profiler can see the scanner. If it doesn't, try powering off the computer, powering off the scanner, powering on the scanner and then powering on the computer. In addition, make sure Mac OS 9 / Classic is off.
If VueScan doesn't find your Canon or Epson scanner and if you're using an Intel Mac, try clicking on the VueScan icon while holding the control key, choosing "Get Info" and setting "Open using Rosetta".
Some older versions of the Canon MP-series software won't work if it's the non-English version. In this case, install the English version from the American download site at www.canon.com.
You can share one copy of VueScan among multiple Mac OS X users by putting the VueScan folder into a read-only folder somewhere on the hard drive. This will cause the default folder for each user to be that user's "Pictures" folder.
If you're using a Ratoc Firewire-SCSI adapter, you may need to configure one of the options. Try setting the time between the power on and the SCSI bus reset to 40.
If you're using the Ratoc USB->SCSI adapter, set up the adapter with the Ratoc utility to "Mass Storage" mode.
If you're using a SCSI scanner on Mac OS X 10.4 (Tiger), have an Adaptec 2906 or 2930CU SCSI controller and your SCSI scanner isn't working properly, try the following commands in the terminal window:
If you've installed the Umax software for a Firewire scanner on Mac OS X, you need to remove (or rename):
/System/Library/Extensions/UmaxFireWire.kext (the name begins with Umax but might have a slightly different name)If you're using a Canon LiDE 40 or LiDE 50 on Mac OS X, install the Canon software for the LiDE 35. These scanners are identical except for the outside plastic, and there's a universal binary driver for the LiDE 35 on www.canon.com.
If you're using a Canon LiDE 80 on Mac OS X and are having problems seeing the scanner or starting VueScan, try re-installing the Canon scanner drivers. If you're using Mac OS X 10.6, you'll also need to copy the folder from the LIDE80_7275MXEN.dmg file in the "Into Users_Shared" folder called CanoScanLIDE80 to the /Users/Shared folder on your hard drive.
If VueScan hangs with Firewire scanners, make sure OpenFirmware has "security-mode" set to "none". Other settings cause problems.
Canon N-series and LIDE scanners are powered directly by the USB port. The USB port must provide a power supply of 500 mA. If you plug the scanner into the USB port on a keyboard or other USB device, the scanner may not work properly. Attach the scanner directly to a USB port on the computer or to a 500 mA self-powered USB hub. If you find that an N-series or LIDE scanner doesn't work with one of your USB ports, try plugging it into the other USB port.
If you're using a Microtech FireSCSI adapter, make sure that you're using SCSI ID 0 and that the SCSI termination is correct.
If you're using an Orange Micro 906F SCSI card, make sure it's upgraded to at least firmware version F1.35.
There's a bug in Microsoft's scsiscan.sys driver when using Firewire or SCSI scanners on 64-bit versions of Windows. You can get a hotfix for this problem from Microsoft at http://support.microsoft.com/kb/922498
If you've set up a shortcut to vuescan.exe and are having problems, try double-clicking \Program Files\VueScan\vuescan.exe directly. This will test whether the problem is with the way the shortcut was set up or whether the problem is with VueScan.
To use PIE (Pacific Image Electronics) scanners with VueScan, you need to first install CyberView X (not CyberView 32). VueScan uses the CyberView X libraries to control the scanner.
To use the Epson Perfection 3170, 4180 or 4490 with VueScan, you need to first install the Epson software for this scanner.
To use most newer HP or Canon scanners, you need to first install the HP or Canon software. VueScan uses HP-supplied and Canon-supplied libraries to talk to these scanners.
If you're using a Microtek scanner, you need to remove the Microtek Scanner Finder from the startup folder in the Start button.
There have been reports of VueScan freezing while scanning using Minolta scanners when the McAfee virus scanning software is enabled. If you have this problem, try disabling the McAfee software.
If your scanner has a button on the front and if a program starts up when you press this button while running VueScan, you have a program running in the background that you need to stop. To stop this program, press control-alt-delete, choose the task manager and use it to stop this program. One example of this is the Epson Status Monitor.
VueScan works on Windows NT/2K/XP/Vista, and works with all known SCSI cards. It also works fine with multiple computers on a single SCSI bus (i.e. dual ported access to scanners).
If VueScan won't start and you have Logitech MouseWare or a Logitech keyboard installed, try stopping EM_EXEC.EXE and/or ITOUCH.EXE. There have been some reports of these two programs causing problems with VueScan. (These two Logitech programs cause problems for many other Windows programs as well.) Alternatively, try turning off the "Smart Move" option in MouseWare.
If you have the Adaptec DirectCD Wizard on the Toolbar, you may have to remove it to get VueScan to run.
If you have an ELSA Synergy III graphics card (or possibly other NVideo graphics cards) and VueScan hangs when starting, you may need to disable the Desktop Manager that comes with the card (the file that causes the problem is nvdesk32.dll).
On Linux, run vuescan from any directory. Your serial number will be stored in ".vuescanrc" in your home directory.
If you're using a newer version of Ubuntu Linux, you can install the needed version of libstdc++ with the command "sudo apt-get install libstdc++5". If you're using 64-bit Linux, you might also need to install "ia32-libs" and "ia32-libs-gtk".
If you're using a newer Linux distribution that's LSB compliant, edit "/etc/udev/rules.d/50-udev-default.rules", find the line that begins with "libusb device access" and change 0644 to 0666. (It might be in "/lib/udev/rules.d")
If you're using a Firewire scanner, make sure you've loaded the sbp2 module.
If you get errors from gtk when starting VueScan, make sure the LANG environment variable is set to C.
If VueScan crashes on startup, make sure you aren't using the idescsi module - this can cause problems.
Note that PIE (Pacific Image Electronics) scanners do not work with VueScan on Linux because CyberView X isn't available on Linux. VueScan uses the CyberView X libraries to control the scanner.
If you're using an Epson scanner that uses a plugin library, make sure you've installed the Epson iscan plugin package There's more information about this on VueScan Supported Scanners page for your scsnner.
You need to make sure all of the /dev/sg* devices are read/write accessible. To see what scanners are available, type "cat /proc/scsi/scsi".
Note that the Adaptec AVA-1505 SCSI card doesn't work with a Nikon film scanner, and will cause a hard bus hang if you use VueScan with it. This is due to a bug in the aha152x driver. Another bug in this driver causes junk to be appended to the end of a raw scan when using the PhotoSmart. Other SCSI cards seem to work fine with VueScan on Linux.
There have also been problems reported with the Adaptec AVA-2904E and the Canon FS2710, although this combination works fine on Windows.
If you want to add or remove scsi devices without rebooting your system, use the following commands:
echo "scsi add-single-device 0 0 ? 0" > /proc/scsi/scsi echo "scsi remove-single-device 0 0 ? 0" > /proc/scsi/scsi (use the SCSI ID in place of "?" above)If you're using libusb to access a USB scanner, you need to make sure the protections in /proc/bus/usb are set up properly. There's some information about setting up libusb on Linux.
To use the scanner.o module on Linux, you need to load the scanner driver and specify the vendor ID and product ID of the scanner. For instance, to recognize the Canon N670U, use "modprobe scanner vendor=0x04a9 product=0x220d". Then type "cat /proc/bus/usb/devices" and make sure "Driver=usbscanner" is enabled for your scanner.
If you're using Linux 2.4.12 or later, you don't need to do anything special to have the scanner auto-recognized.
If you're using an earler version of Linux with a USB scanner, set up the SCANNER0 environment variable to point to /dev/usbscanner or /dev/usb/scanner (it needs to be read/write accessible), set up the SCANVID0 environment variable with the USB Vendor ID (VID) and set up the SCANPID0 environment variable with the USB Product ID (PID). You can support up to 8 USB scanners at a time by using SCANNER1, SCANNER2, SCANVID1, SCANVID2, etc.
For instance, to set up VueScan for the Epson 640, use the following commands if you're using csh:
setenv SCANNER0 /dev/usbscanner setenv SCANVID0 04b8 setenv SCANPID0 010cor if you're using sh or bash:
export SCANNER0="/dev/usbscanner" export SCANVID0="04b8" export SCANPID0="010c"Note that you don't need to set up these environment variables on newer Linux kernels or if you're using libusb.
If you're having problems with USB timeouts (i.e. with the Nikon CoolScan IV (LS-40), make sure you use the "usb-uhci" (CONFIG_USB_UHCI) module instead of the alternate "uhci" (CONFIG_UHCI_ALT) module. You might also increase the kernel usb timeout value (CONFIG_USB_LONG_TIMEOUT=y).
To remove VueScan, delete the entire folder containing VueScan. There are no files installed elsewhere on the system.
THIS SOFTWARE AND ACCOMPANYING DOCUMENTATION (INCLUDING INSTRUCTIONS FOR USE) ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, FURTHER, HAMRICK SOFTWARE DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF USE, OF THE SOFTWARE OR DOCUMENTATION IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS, OR OTHERWISE. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU. IF THE SOFTWARE OR WRITTEN MATERIALS ARE DEFECTIVE, YOU, AND NOT HAMRICK SOFTWARE OR ITS DEALERS, DISTRIBUTORS, AGENTS, OR EMPLOYEES, ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
HAMRICK SOFTWARE DISCLAIMS ALL OTHER WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, THAT IS MADE BY HAMRICK SOFTWARE, ON THIS HAMRICK SOFTWARE PRODUCT. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY HAMRICK SOFTWARE, ITS DEALERS, DISTRIBUTORS, AGENTS OR EMPLOYEES SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY AND YOU MAY NOT RELY ON ANY SUCH INFORMATION OR ADVICE. YOU MAY HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE.
NEITHER HAMRICK SOFTWARE NOR ANYONE ELSE WHO HAS BEEN INVOLVED IN THE CREATION, PRODUCTION OR DELIVERY OF THIS PRODUCT SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL OR INCIDENTAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, AND THE LIKE) ARISING OUT OF THE USE OR INABILITY TO USE SUCH PRODUCT EVEN IF HAMRICK SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Copyright © 2013 Hamrick Software