Vuescan focuses the scanner before scanning like Nikon Scan does, right? I noticed that Nikon Scan has a plethora of setup and calibration options that I fear I would lose out on in Vuescan.
Which version of NikonScan are you running? At first I would have guessed it was an issue with the tray, but if VueScan works with the same tray then I wonder...I guess Vuescan will have to do for now, as it does work with the 35mm film carriers. I wonder why Nikon Scan is having issues with only some carriers but not others.
Vuescan focuses the scanner before scanning like Nikon Scan does, right? I noticed that Nikon Scan has a plethora of setup and calibration options that I fear I would lose out on in Vuescan.
Nikon Scan 4.0.3.
As for VueScan, I'm trying out my first scan with the full version now, but I can't work out how to prevent the scanner from outputting an inverted color scan, rather than the scan of the negative as is. I'd prefer to do my own color correction outside of VueScan for now.
I feel your pain! Getting the frame spacing and off-set is a pain in the rump. I even bought the VueScan Bible and it doesn't even explain it that well.Just received my (relatively cheaply!) found 9000 (incl. a bunch of film holders, incl. the rotating 120 one, this alone seems to sell for twice of what I paid...) and tried it with vuescan under Linux, using my old laptop's expresscard FireWire card which I had used before with Minolta scanners. Beside a dead cable everything went smooth.
What confused me: trying to scan with the glassless 120 holder, vuescan gives me arbitrary frames when when I select manual cropping. I looked it up and seems I have to fiddle manually with frame spacing and offset. Is there no other way? With the Epson v800 I could just zoom out the whole preview and crop frames manually, this doesn't seem to work. Any better idea?
I am also installing right now a Windows XP virtual machine on this laptop, with the goal to try out Nikon scan, since it seems not that great supported on win10 (which I have installed aside Linux)? But I'm afraid getting the FireWire card pass through to the XP virtual machine might be a mess, let's see... Anyone tried out this route?
Firewire pass through is not supported on any VM I'm aware of. Nikon scan works just fine on win10 if you follow the instructions. If you want to try XP with a firewire scanner you need a machine that runs XP and you need xp drivers for your firewire card. USB pass through works fine though.Just received my (relatively cheaply!) found 9000 (incl. a bunch of film holders, incl. the rotating 120 one, this alone seems to sell for twice of what I paid...) and tried it with vuescan under Linux, using my old laptop's expresscard FireWire card which I had used before with Minolta scanners. Beside a dead cable everything went smooth.
What confused me: trying to scan with the glassless 120 holder, vuescan gives me arbitrary frames when when I select manual cropping. I looked it up and seems I have to fiddle manually with frame spacing and offset. Is there no other way? With the Epson v800 I could just zoom out the whole preview and crop frames manually, this doesn't seem to work. Any better idea?
I am also installing right now a Windows XP virtual machine on this laptop, with the goal to try out Nikon scan, since it seems not that great supported on win10 (which I have installed aside Linux)? But I'm afraid getting the FireWire card pass through to the XP virtual machine might be a mess, let's see... Anyone tried out this route?
Nikon scan works just fine on win10 if you follow the instructions. ...
edit: OK looking a bit more into it. Seems like there there *might* be a possible work around with PCI-E pass through.
It does. I'm running windows 10 on an old mac mini 2012 with firewire scanners connected. You probably just have to find the win10 driver if it doesn't work out of the box.I have 2 desktop with firewire but Windows 10 or 11 doesn't support firewire. So a firewire card isn't a solution.
Thanks, I had read somewhere win10 wasn't running it stable, but if it's fine, this would be easier, I'll give it a try. And of course just out of curiosity the VM route, since I have win XP now already up in KVM.
I would be very interested in your views between NikonScan and VueScan. I already have mine, but am curious as to what other folks think.Alright, just to come back: Nikon Scan installed without problems on Win10 using the instructions from https://www.shtengel.com/gleb/getting_nikon_coolscan_scanners_work_under_Win7.htm and the file from https://lincolnscan.co.uk/Reference.html . I have not actually used it yet, but the scanner gets recognized.
I tried as well the VM XP route, which failed at least for my setup. I had let myself guid by Google's AI mode, isolating the device drivers from the Linux host and adding them to the XP system. Unfortunately, on my laptop the Firewire ExpressCard seems to hang on the same PCI bus as some other required devices and a complete isolation was impossible, so the VM did not start after handing over this PCI bus. On a different system this could still a way to go, but at least for me (Kubuntu with KVM/virtual machine manager + Windows 10 VM, on a Thinkpad T540p with Startech Firewire 400 ExpressCard) this wasn't working.
Which is fine, I have now Vuescan (in Linux) and Nikon Scan (in Win10), will compare how I like Nikon Scan or if I continue using Vuescan (raw scans and invertion in Darktable).
I have now Vuescan (in Linux) and Nikon Scan (in Win10), will compare how I like Nikon Scan or if I continue using Vuescan (raw scans and invertion in Darktable).
Because I rarely use Windows, it's just a leftover of the OS installed when I bought the computer. I prefer Linux, using Kubuntu (at least private) since 15 years or so.Why not use both Vuescan and Nikon Scan on your Win10 platform?
Because I rarely use Windows, it's just a leftover of the OS installed when I bought the computer. I prefer Linux, using Kubuntu (at least private) since 15 years or so.
Thanks for reporting back. Reading what you wrote, it seems to work differently than I expected. I thought the VM would just expose the to PCI bus to XP, and you still would have to have the native XP driver for the firewire card, but sounds like it is capable in of getting around this. The card you mentioned seems to have native support in XP anyway though.I tried as well the VM XP route, which failed at least for my setup. I had let myself guid by Google's AI mode, isolating the device drivers from the Linux host and adding them to the XP system. Unfortunately, on my laptop the Firewire ExpressCard seems to hang on the same PCI bus as some other required devices and a complete isolation was impossible, so the VM did not start after handing over this PCI bus. On a different system this could still a way to go, but at least for me (Kubuntu with KVM/virtual machine manager + Windows 10 VM, on a Thinkpad T540p with Startech Firewire 400 ExpressCard) this wasn't working.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?