Vuescan 9 6 31 Mm

broken image


plustek_opticfilm_7600i

film scanner

Model: Plustek OpticFilm 7600i
image sensor: CCD
hardware resolution: 7200 dpi
dynamic range: 3.6
scan modes: color - 48 bit input, 24 / 48 bit output, grayscale - 16 bit input, 8 / 16 bit output, black and white - 1 bit
scanning speed: 3600 dpi - approx. 35.91 seconds (multi-sampling ON), 7200 dpi - approx. 112.59 seconds (multi-sampling ON)
scanning area: 36.8 mm x 25.4 mm (W x L) for negative (1.45 inch x 1.0 inch)
preview speed: (multi-sampling ON) negative film - approx. 7.96 seconds, positive film - approx. 7.57 seconds
feed: manual feed
other: iSRD - infrared Smart Removal of Defect
Dimensions: 120 x 272 x 119 mm (W x D x H, 4.73 x 10.7 x 4.7 inches)

Links: sniffusb 2.0, VueScan might support this scanner,

History:
2020-04-30: c1 - I compiled latest sane-backends from git, as the 7600i is supported there, then test it:
tingo@kg-core1$ scanimage --version
scanimage (sane-backends) 1.0.29-614-g9aad35503; backend version 1.0.29
tingo@kg-core1$ scanimage -L
device `genesys:libusb:000:004' is a PLUSTEK OpticFilm 7600i (v1) flatbed scanner
nice! I also downloaded, compiled and installed sane-frontends from git, this gives me xscanimage, and I used that to test.

2020-04-24: z30b - next up, connect the scanner and see if vuescan finds it. The scanner shows up
tingo@z30b:~/dl/lin/vuescan$ lsusb -d 07b3:0c3b
Bus 001 Device 009: ID 07b3:0c3b Plustek, Inc.
how about vuescan? It detects the scanner: 'PLUSTEK OpticFilm 7600i - Transparency', 'Press Preview, adjust crop box, press Scan'. Scanning a few images of a negative film strip, in different resolutions - yes, this works.
2020-04-24: z30b - a laptop running Debian 10.3. Let me install vuescan on that
tingo@z30b:~/dl/lin/vuescan$ sudo dpkg -i vuex6497.deb
Selecting previously unselected package vuescan.
(Reading database ... 186182 files and directories currently installed.)
Preparing to unpack vuex6497.deb ...
Unpacking vuescan (9.7.27.0-0) ...
Setting up vuescan (9.7.27.0-0) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
tingo@z30b:~/dl/lin/vuescan$ dpkg-query -L vuescan
/.
/usr
/usr/bin
/usr/bin/vuescan
/usr/share
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/scalable
/usr/share/icons/hicolor/scalable/apps
/usr/share/icons/hicolor/scalable/apps/vuescan.svg
/usr/share/appdata
/usr/share/appdata/vuescan.appdata.xml
/usr/share/applications
/usr/share/applications/vuescan.desktop
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/60-vuescan.rules

2020-04-23: vm4 - I downloaded vuescan, now try to install it
tingo@kg-vm4:~/dl/lin$ sudo dpkg -i vuex6497.deb
Selecting previously unselected package vuescan.
(Reading database ... 154320 files and directories currently installed.)
Preparing to unpack vuex6497.deb ...
Unpacking vuescan (9.7.27.0-0) ...
Setting up vuescan (9.7.27.0-0) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
tingo@kg-vm4:~/dl/lin$ dpkg-query -L vuescan
/.
/usr
/usr/bin
/usr/bin/vuescan
/usr/share
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/scalable
/usr/share/icons/hicolor/scalable/apps
/usr/share/icons/hicolor/scalable/apps/vuescan.svg
/usr/share/appdata
/usr/share/appdata/vuescan.appdata.xml
/usr/share/applications
/usr/share/applications/vuescan.desktop
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/60-vuescan.rules
hmm, what does that udev rules script specify? Oh, just a buncg of 'mode 0666' for the scanner models.
2020-04-23: vm4 - connected the scanner to a Debian machine, running debian 10.3
lsusb shows the scanner
tingo@kg-vm4:~$ lsusb -d 07b3:0c3b
Bus 003 Device 003: ID 07b3:0c3b Plustek, Inc.
tingo@kg-vm4:~$ sudo apt list --installed sane*
Listing... Done
sane-utils/stable,now 1.0.27-3.2 amd64 [installed,automatic]
and sane-find-scanner
tingo@kg-vm4:~$ sudo sane-find-scanner -v -v
This is sane-find-scanner from sane-backends 1.0.27
[..]

bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255
bDeviceSubClass 255
bDeviceProtocol 255
bMaxPacketSize0 64
idVendor 0x07B3
idProduct 0x0C3B
bcdDevice 4.00
iManufacturer 10 (Plustek INC)
iProduct 11 (Film Scanner )
iSerialNumber 12 (1)
bNumConfigurations 1

bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 192 (Self-powered)
MaxPower 10 mA


bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 0 ()

bLength 7
bDescriptorType 5
bEndpointAddress 0x81 (in 0x01)
bmAttributes 2 (bulk)
wMaxPacketSize 512
bInterval 0 ms
bRefresh 0
bSynchAddress 0

bLength 7
bDescriptorType 5
bEndpointAddress 0x02 (out 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 512
bInterval 0 ms
bRefresh 0
bSynchAddress 0

bLength 7
bDescriptorType 5
bEndpointAddress 0x83 (in 0x03)
bmAttributes 3 (interrupt)
wMaxPacketSize 1
bInterval 8 ms
bRefresh 0
bSynchAddress 0

checking for LM983[1,2,3] ...
this is not a LM983x (bcdUSB = 0x200)
checking for GT-6801 ...
this is not a GT-6801 (bcdUSB = 0x200)
checking for GT-6816 ...
this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GLxxx ...
this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)

found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c3b [Film Scanner ], chip=GL842) at libusb:003:003

2020-04-22: c1 - testing the scanner under FreeBSD 11.3-stable:
root@kg-core1# uname -a
FreeBSD kg-core1.kg4.no 11.3-STABLE FreeBSD 11.3-STABLE #2 r352605: Sun Sep 22 22:53:27 CEST 2019 root@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
root@kg-core1# pkg info sane*
sane-backends-1.0.29
sane-frontends-1.0.14_10
root@kg-core1# usbconfig -d ugen0.4
ugen0.4: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (10mA)
sane-find-scanner
root@kg-core1# sane-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c3b [Film Scanner ], chip=GL842) at libusb:000:004
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
root@kg-core1# scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
root@kg-core1# sane-find-scanner -v -v
This is sane-find-scanner from sane-backends 1.0.29
[..]

bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255
bDeviceSubClass 255
bDeviceProtocol 255
bMaxPacketSize0 64
idVendor 0x07B3
idProduct 0x0C3B
bcdDevice 4.00
iManufacturer 10 (Plustek INC)
iProduct 11 (Film Scanner )
iSerialNumber 12 (1)
bNumConfigurations 1

bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0 ()
bmAttributes 192 (Self-powered)
MaxPower 10 mA


bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 0 ()

bLength 7
bDescriptorType 5
bEndpointAddress 0x81 (in 0x01)
bmAttributes 2 (bulk)
wMaxPacketSize 512
bInterval 0 ms
bRefresh 0
bSynchAddress 0

bLength 7
bDescriptorType 5
bEndpointAddress 0x02 (out 0x02)
bmAttributes 2 (bulk)
wMaxPacketSize 512
bInterval 0 ms
bRefresh 0
bSynchAddress 0

bLength 7
bDescriptorType 5
bEndpointAddress 0x83 (in 0x03)
bmAttributes 3 (interrupt)
wMaxPacketSize 1
bInterval 8 ms
bRefresh 0
bSynchAddress 0

checking for LM983[1,2,3] ...
this is not a LM983x (bcdUSB = 0x200)
checking for GT-6801 ...
this is not a GT-6801 (bcdUSB = 0x200)
checking for GT-6816 ...
this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GLxxx ...
this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)

found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c3b [Film Scanner ], chip=GL842) at libusb:000:004
[..]

2014-01-08: for usb sniffing under winXP, the tools sniffusb 2.0 is recommended.
2014-01-04: testing the scanner with sane-backends 1.0.24 (compiled, not installed):
tingo@kg-core1$ uname -a
FreeBSD kg-core1.kg4.no 8.4-STABLE FreeBSD 8.4-STABLE #0 r253646: Thu Jul 25 10:12:31 UTC 2013 root@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
root@kg-core1# pwd
/usr/ports/graphics/sane-backends/work/stage
root@kg-core1# usr/local/bin/sane-find-scanner -q
found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c3b [Film Scanner ], chip=GL842) at libusb:/dev/usb:/dev/ugen2.4
interesting. Try scanimage -L:
root@kg-core1# usr/local/bin/scanimage -L
/libexec/ld-elf.so.1: Shared object 'libsane.so.1' not found, required by 'scanimage'
ah. Try with LD_PRELOAD then:
root@kg-core1# LD_PRELOAD='./usr/local/lib/libsane.so.1' usr/local/bin/scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

2014-01-02: testing the scanner under FreeBSD 8.4-stable:
tingo@kg-core1$ uname -a
FreeBSD kg-core1.kg4.no 8.4-STABLE FreeBSD 8.4-STABLE #0 r253646: Thu Jul 25 10:12:31 UTC 2013 root@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
usb info:
root@kg-core1# usbconfig -d ugen2.4
ugen2.4: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
usb device description
root@kg-core1# usbconfig -d ugen2.4 dump_device_desc
ugen2.4: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x00ff
bDeviceSubClass = 0x00ff
bDeviceProtocol = 0x00ff
bMaxPacketSize0 = 0x0040
idVendor = 0x07b3
idProduct = 0x0c3b
bcdDevice = 0x0400
iManufacturer = 0x000a
iProduct = 0x000b
iSerialNumber = 0x000c <1>
bNumConfigurations = 0x0001
usb current config
root@kg-core1# usbconfig -d ugen2.4 dump_curr_config_desc
ugen2.4: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
Configuration index 0
bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x0027
bNumInterfaces = 0x0001
bConfigurationValue = 0x0001
iConfiguration = 0x0000
bmAttributes = 0x00c0
bMaxPower = 0x0005
Interface 0
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x0000
bAlternateSetting = 0x0000
bNumEndpoints = 0x0003
bInterfaceClass = 0x00ff
bInterfaceSubClass = 0x00ff
bInterfaceProtocol = 0x00ff
iInterface = 0x0000
Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0081
bmAttributes = 0x0002
wMaxPacketSize = 0x0200
bInterval = 0x0000
bRefresh = 0x0000
bSynchAddress = 0x0000
Endpoint 1
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0002
bmAttributes = 0x0002
wMaxPacketSize = 0x0200
bInterval = 0x0000
bRefresh = 0x0000
bSynchAddress = 0x0000
Endpoint 2
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0083
bmAttributes = 0x0003
wMaxPacketSize = 0x0001
bInterval = 0x0008
bRefresh = 0x0000
bSynchAddress = 0x0000
testing with sane-backends 1.0.23_2:
root@kg-core1# sane-find-scanner -q
found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c3b [Film Scanner ], chip=GL843) at libusb:/dev/usb:/dev/ugen2.4
2010-05-26: I tested the scanner under FreeBSD 8.0-stable:
root@kg-v2# uname -a
FreeBSD kg-v2.kg4.no 8.0-STABLE FreeBSD 8.0-STABLE #2: Sun Apr 11 19:39:02 CEST 2010 root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
usb info:
root@kg-v2# usbconfig -u 3 -a 2 dump_info
ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
root@kg-v2# usbconfig -u 3 -a 2 dump_info
ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
root@kg-v2# usbconfig -u 3 -a 2 dump_device_desc
ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x00ff
bDeviceSubClass = 0x00ff
bDeviceProtocol = 0x00ff
bMaxPacketSize0 = 0x0040
idVendor = 0x07b3
idProduct = 0x0c3b
bcdDevice = 0x0400
iManufacturer = 0x000a
iProduct = 0x000b
iSerialNumber = 0x000c <1>
bNumConfigurations = 0x0001
testing with sane-backends 1.0.20_6:
root@kg-v2# sane-find-scanner -q
found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c3b [Film Scanner ], chip=GL843) at libusb:/dev/usb:/dev/ugen3.2
found USB scanner (vendor=0x03f0 [HP], product=0xc202 [Photosmart 8200 series]) at libusb:/dev/usb:/dev/ugen1.2
found USB scanner (vendor=0x06bd [AGFA], product=0x2061 [ Snapscan1212u_2]) at libusb:/dev/usb:/dev/ugen2.2
root@kg-v2# scanimage -L
device `snapscan:libusb:/dev/usb:/dev/ugen2.2' is a AGFA SNAPSCAN 1212U_2 flatbed scanner
testing with sane-backends 1.0.21:
root@kg-v2# sane-find-scanner -q
found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c3b [Film Scanner ], chip=GL843) at libusb:/dev/usb:/dev/ugen3.2
found USB scanner (vendor=0x03f0 [HP], product=0xc202 [Photosmart 8200 series]) at libusb:/dev/usb:/dev/ugen1.2
found USB scanner (vendor=0x06bd [AGFA], product=0x2061 [ Snapscan1212u_2]) at libusb:/dev/usb:/dev/ugen2.2
2010-05-26: I picked up the package at my local post office.

2010-05-25: I got a shipping notice from Activium.
2010-04-26: the company notified me that they are temporarily sold out, but expect a new supply soon.
2010-04-25: I ordered the scanner from Activium, the price was NOK 2800.- plus shipping NOK 61.-.
  1. Vuescan 9 6 31 Mm To Inches
  2. 9x6
  3. Vuescan 9 6 31 Mmol

Conversion Table: fractional inches, decimal inches, mm This page was written by Steven J. DeRose (via Ruby) on 2003-03-28, and was last updated on 2003-03-28. This table of equivalents should be useful for drill bit sizes, wrench and socket sizes, etc. VueScan 9.7 requires Mac OS X 10.9 or later. For scanners that can add a 5 mm white border around a scan. Aug 15, 2021 VueScan is here to help. We reverse engineered over 6500 scanners and included built in drivers in VueScan so you can keep using the scanner you already have. September 23, 2021. Windows 10 x64, 8 x64, 7 x64, Vista x64, XP x64 Download VueScan for other operating systems or older versions.

As I discussed here, I have a need to scan a large amount of 35mm film, mainly black and white negatives and color slides. In this article I'll describe how I use a Nikon D800E to scan 35mm black and white negatives. I'll cover slides in a later article. I may cover color negatives if I can get the process down where it yields quality results quickly.

With black and white negatives the results are as good as, or better than, the results from a 4000dpi Canon CanoScan FS4000US that I have been using. In fact the picture from the D800E is almost the same size as the 5000dpi result from my ScanMate 5000 drum scanner, and seems to resolve almost as much info.

Results

400 Speed film

Aug 25, 2021 VueScan 9.7 requires Mac OS X 10.9 or later. For scanners that can add a 5 mm white border around a scan. VueScan Pro 9.6.20 Multilingual netest.19.9 MB.neni moje. What's new in version 9.6.20.Improved support for some older Brother scanners.Added support for installing Photoshop CC 2019 plugin.Added support for 'Input Page border' option For scanners that can add a 5 mm white border around a scan.

Snapshot of Will. Nikon N80. Ilford Delta 400 film, most likely shot at EI 200.
Scanned on ScanMate 5000 drum scanner @5000dpi.

Let's start off with a brief look at the results that are possible. First up is a snapshot of my son William taken roughly 10 years ago. The shot was almost certainly taken with a Nikon N80, and probably using either the 28-105 f/3.5 to 4.5 AFD, or possibly the 50mm f/1.8 AFD lens. Focus would have been attempted on the eyes, but they look a bit unsharp. I scanned this negative on a ScanMate 5000 drum scanner at maximum resolution, about 5080dpi, a Canon CanoScan FS4000US CCD scanner at 4000dpi, and using the Nikon D800E. I then adjusted the tonality of each in Photoshop to match closely. No sharpening was applied to either of the scanned images, but the D800E received a bit of default sharpening from Adobe Lightroom as it was imported.

The results surprised me. I hadn't really focused on how much resolution the D800 has until I did this scan. The image size is essentially the same as what the ScanMate delivers at 5000dpi. The CanoScan at 4000dpi is smaller by 20% in linear resolution, and 44% in total pixels captured. One question to ask is, does my film hold any extra information that needs 5000dpi to capture. I suspect not for most of what I have shot, and almost certainly not for the images shot on 400 speed film, like this example.

This exercise didn't start out to be a scanner test, but rather a simple test to see how much I would loose by scanning film with the DSLR. If the resolution captured came close to the lower resolution CanoScan I would be happy. My main goal is to quickly scan many rolls of film to have them available in LightRoom and to post on the web in galleries for the family to view. When I saw that the DSLR seemed capable of out-resolving the CanoScan I was a bit shocked and decided to also scan a few frames on the drum scanner for a point of reference.

All three seem to resolve the film grain well. The Drum scanner has the most well defined grain. This could be softened a bit by opening up the aperture one stop on the scanner, at the expense of some detail. In this case with this film I think that would be the right choice for a pleasing scan. The ScanMate also seems to have resolved a little more detail in the shirt over the other two, but not a huge amount.

The D800E produces an image that's almost the exact size as the drum scanner. I'm not quoting the exact size because it depends a bit on how I setup the bellows and the film copy attachment. By leaving a bit of room on the edges I assure I can capture the full film frame, at the expense of some resolution and the need to crop the image.

In this image the CanoScan resolved the least detail, but not by much. I think in a 16×24 inch print I couldn't tell the difference without some close study. That is a print size that's much larger than I ever print 35mm film.

If this were about picking the ultimate quality I would use the drum scanner every time. But loading the drum scanner takes time, costs money for the scanning fluid and mylar overlay. Each scan also takes roughly 10 to 15 minutes (I haven't timed it). The CanoScan loads a strip of 6 negatives quickly. The VueScan software I use can also batch scan all 6 images without further user input. Scans still take a long time, especially since I run this scanner over the slow USB connection. The D800E takes about 20 seconds per frame to align and click the shutter. Images can be automatically imported into LightRoom. But the best part of this is the quality appears to be at least as good as the CanoScan, and I can get many rolls of film scanned in an evening. Put on a movie I've seen before and just process film.

100 Speed film

Vuescan 9 6 31 Mm To Inches

Railroad trestle, Crawford Notch NH. Arista Legacy Pro 100 (Fuji Acros). Shot at EI 50.
Scanned on ScanMate 5000 drum scanner @5000dpi.

So, what are the results like for a finer grained 100 speed film? Surprisingly I don't have much of this to choose from. I mostly shot faster film in 35mm because I could get good results handheld of fast moving subjects. I am not usually concerned with getting the most resolution out of 35mm shooting. For that I use a larger format film, and usually a tripod. However I did find a roll of Fuji Acros (actually rebranded as Arista Legacy Pro), which is a nice fine grained film. It was shot on an Olympus XA in bright sunlight. I suspect I shot at f/8 given the lighting levels, but I'm not sure. The XA lens is pretty decent, but surely not as sharp as you can get for the format. I'm sure with careful technique and good equipment you can get better results than I am showing here.

Most of the same comments from the other film hold true for this as well. I don't see a whole lot of difference in the amount of detail each scanning method was able to extract from the film. Based on that I estimate that the film really only contains about 12 to 18 megapixels of information, and it's probably closer to the 12 mark for the images I have here. But considering that when I set out on this experiment I was only looking to get web quality images out of the scans, I think this is still impressive.

How To in Theory

In short all you need to do is to take a picture of your negatives and invert the image. But for best results you want to make sure the camera is perfectly square to the negative. This will prevent distortion and assure that focus is even across the entire negative. You will also want a lens that will work in the macro range of one to one (1:1) reproduction ratio. In other words the subject will be projected on the camera sensor at original size of the film. This assumes a full frame sensor. If you are using a DX sensor camera the ratio will be closer to 1:1.5, depending on the exact camera.

You can make any lens work by adding extension tubes of the right length. But lenses designed for the reproduction range you are using will give you noticeably better results. Most camera systems have macro lenses that will do a fine job at 1:1 ratios. You will sometimes still need to add extension tubes to allow the lens to focus close enough.

Another helpful, but not necessary, piece of equipment is a bellows system. These act as variable extension tubes, and some allow movements like a view camera (this isn't needed here). I've found that a bellows is by far the easiest method to adjust the the framing and focus in this operation. Many bellows also support a film or slide holder to hold your film and a piece of diffusion plastic to create a smooth light source, which is convenient. These were originally intended to copy slides, or make internegatives. But they work just as well for 'scanning' film with your DSLR.

The simplest solution is probably something like the Nikon ES-1 Slide Copy Adapter, which I have not tried. But if I didn't already own the bellows that's what I would try. I have also seen home made versions of this online made out of what look like cardboard tubes.

A tripod and lightbox will also work, but I found that very difficult to keep aligned over the long run. But it was certainly good enough for a proof of concept. The important part is the lens. The rest is just convenience.

How To in Practice

I use a Nikon PB4 bellows with a Rodenstock 75mm f/4 Rodagon-D lens. This lens was designed for 1:1 reproduction of medium format film. It is very sharp across the whole frame. But I have also used a Nikon 55mm f/2.8 AIS macro lens on the bellows and gotten excellent results, especially with the D7000 camera (DX format, so 1:1.5 ratio). For a light source I have used a desk lamp, my light box stood on it's edge, a flash, and as pictured here an Omega color enlarger head. For black and white negatives all gave similar results.

At these ratios a small adjustment in distance is very visible, so the magnified LiveView image is very helpful. I usually frame and roughly adjust the setup using the viewfinder, but I focus using LiveView at 100% magnification. Focus only needs to be setup one time. With the PB4 bellows I have found you need to make slight adjustments to the tilt to get the plane of focus perfectly parallel to the sensor. With LiveView it's pretty easy. Just check that the sides are as sharp as the center.

I set the lens to f/5.6 which seems to be a good compromise between diffraction and compensating for minor film curvature or warpage.

I shoot in manual mode since the light is constant. I adjust exposure by examining the histogram in a sample shot and adjust the exposure time to fully expose the image to the right of the histogram. By exposing to the right, but not clipping you will minimize the noise from your camera. This is especially important since the image will be reversed and any noise that would normally be buried in the shadows will now be in your highlights. Exposing to the right keeps the image nice and clean.

I tether the camera to Lightroom so the images are imported as I take them. This makes it easier to check them as I take them, but shooting to a card and importing works just fine.

Vuescan 9 6 31 Mm

A safe setup that will result in low contrast images. This is best if you are going to do extensive edits. It's better to start out with a simple linear inversion and correct in Photoshop.

During the import process I apply a User Preset to each photo. This preset does a few things. First, it inverts the image with a custom Tone Curve. Second it sets the image treatment as Black and White.

Notice in the top histogram the the plot is pushed to the left. This is because this histogram shows the results after adjustments. Since we have inverted the image using a very basic Tone Curve things are looking a little dark and low contrast. In the Tone Curve you can see the original histogram, which is exposed close to the right.

As it is now this Tone Curve is very safe in that no information is clipped, but it produces a very flat (see the histogram bunched at the one side). When I am scanning a lot of film at once I will tweak the curve to give better results as a default. This has the advantage of making decent looking images in LightRoom, which is really what I want for most of my scanning. Note that the curves are reversed from the normal way of working in PhotoShop because we are dealing with a negative.

This type of tone curve adjusts the image to have a full range of tones from black to white. It also adds an S curve to add a bit of contrast to the image. This curve may not work well on the next image scanned on the roll, and it will certainly need adjusting for another film type. But it looks much better in Light Room.

9x6

You can save many setups as Presets and have Lightroom apply these as it imports files, or after the fact just by clicking on them.

Vuescan 9 6 31 Mmol

If all of this seems too complicated, it's really not too bad in practice. The hardest part will be finding a good way of holding the camera and film at the correct distance, and possibly finding a good lens if you don't have one. But the results are as good as or better than any 35mm scanner on the market. If you don't own a scanner this will let you digitize your old archive of negatives. Once you factor in the speed this method becomes even more compelling.

But it must cost a lot right? Even if you don't have any of the equipment besides a DSLR you can pick up a 55mm AIS macro lens for about $150 and a Nikon PB-5 Bellows for about the same. The ES-1 is about $70. So for about $200 to $300 you can have a very decent scanning solution (less if you shop carefully on ebay). You don't need a fancy autofocus lens, or image stabilization. In fact the older lenses with an aperture ring are better for this. I don't know what's available in other brands, but with Canon at least you can use Nikon lenses with a cheap adapter. If you own a higher resolution DSLR you will get much better results out of this setup than you will with a low end scanner, and you will have a macro lens and bellows to take cool pictures of small things on top of that.





broken image