J
Juha Koivisto
I recently bought a used Minolta Scan Elite 5400, and while it's mostly
performing well, there's some streaking present when using the grain
dissolver. Upgrading the firmware to 1.10 may have helped a bit, but did
not fix the problem completely.
The streaking is more apparent in Vuescan but can also be seen in the
Minolta software. With grain dissolver off (resulting in shorter exposure
times) the scans are fine, but unfortunately in the Minolta software this
also means turning off ICE.
I put some test scans here:
<http://www.hut.fi/u/jkoivist/se5400/streaking.html>
The real question is, is this normal, or should I have the scanner
serviced or replaced?
An idea for fixing this in Vuescan: It would be nice if one could create
a file listing the problematic pixels (I'd be happy to just write it with
a text editor), and Vuescan would replace them with the average of the
neighboring pixels. Even if there are 50 pixels to be ignored, like in
my scanner, this would only result in loss of 1% of the total resolution
which would likely not be visible. There could be a checkbox in advanced
settings to turn this filtering on or off (or maybe even a pulldown menu
for selecting between different defect lists, to allow for different
levels of correction).
Something like this could of course also be implemented independently as
a postprocessing filter (to be launched instead of the external viewer),
but that would require always scanning the full width (and saving with
full resolution) so the filter knows which pixel is which.
performing well, there's some streaking present when using the grain
dissolver. Upgrading the firmware to 1.10 may have helped a bit, but did
not fix the problem completely.
The streaking is more apparent in Vuescan but can also be seen in the
Minolta software. With grain dissolver off (resulting in shorter exposure
times) the scans are fine, but unfortunately in the Minolta software this
also means turning off ICE.
I put some test scans here:
<http://www.hut.fi/u/jkoivist/se5400/streaking.html>
The real question is, is this normal, or should I have the scanner
serviced or replaced?
An idea for fixing this in Vuescan: It would be nice if one could create
a file listing the problematic pixels (I'd be happy to just write it with
a text editor), and Vuescan would replace them with the average of the
neighboring pixels. Even if there are 50 pixels to be ignored, like in
my scanner, this would only result in loss of 1% of the total resolution
which would likely not be visible. There could be a checkbox in advanced
settings to turn this filtering on or off (or maybe even a pulldown menu
for selecting between different defect lists, to allow for different
levels of correction).
Something like this could of course also be implemented independently as
a postprocessing filter (to be launched instead of the external viewer),
but that would require always scanning the full width (and saving with
full resolution) so the filter knows which pixel is which.