XFer
-
(multi sampling support)
Usually scanner firmware exposes to the driver a set of commands which are relatively high level.
This has many advantages, from easier driver programming to less documentation to be given out to less chance for a bug in the driver to damage the scanner.
To move multi sampling out of the firmware and into the software (driver) you should expose to the driver very low-level commands (like: "advance film one step" - "acquire row" - "acquire row" - "acquire row" - etc.). I don't see a scanner manifacturer doing that.
Well it depends from film type and scene captured. Without separate RGB exposure you get -2 EV dynamic range for B and you have to compensate for this by boosting the B channel during negative inversion.
It may not affect a particular image in a visible way, but may be quite important for a different image.
It's not so easy to show this because of the way scanning softwares work (you can't easily tell a software "do not use different RGB exposure"
). With Vuescan it is doable, but frankly, Vuescan is quite limited in treating color negatives.
I should perform raw scans with and without separate RGB exposure compensation, invert the raw scans with an appropriate software (Photoshop sucks badly at that) and avoid misrepresenting the results (for example because of different color balance corrections / gamma curve corrections).
I did some tests time ago, I'll see if I can dig them out.
Sadly, I think you're right.
Fernando
Usually scanner firmware exposes to the driver a set of commands which are relatively high level.
This has many advantages, from easier driver programming to less documentation to be given out to less chance for a bug in the driver to damage the scanner.
To move multi sampling out of the firmware and into the software (driver) you should expose to the driver very low-level commands (like: "advance film one step" - "acquire row" - "acquire row" - "acquire row" - etc.). I don't see a scanner manifacturer doing that.
Well it depends from film type and scene captured. Without separate RGB exposure you get -2 EV dynamic range for B and you have to compensate for this by boosting the B channel during negative inversion.
It may not affect a particular image in a visible way, but may be quite important for a different image.
It's not so easy to show this because of the way scanning softwares work (you can't easily tell a software "do not use different RGB exposure"
). With Vuescan it is doable, but frankly, Vuescan is quite limited in treating color negatives.I should perform raw scans with and without separate RGB exposure compensation, invert the raw scans with an appropriate software (Photoshop sucks badly at that) and avoid misrepresenting the results (for example because of different color balance corrections / gamma curve corrections).
I did some tests time ago, I'll see if I can dig them out.
Sadly, I think you're right.
Fernando
XFer
-
Thanks Joe!
More reviews coming (Minolta 5400-II is next in line). I hope to get a Plustek 120 on loan to review it, possibly with Vuescan support.
In the meantime, the German site filmscanner.info announced that a review of the Plustek 120 is scheduled for April (they usually publish a German version first, and an English version afterwards).
I guess Plustek, understandably, prefers using the first production lots to fulfill backorders instead of giving scanners on loan to testers.
Fernando
brbo
Well-known
Usually.
On the other hand, Plustek scanners don't work with any scanning software without binary driver provided by Plustek/LaserSoft. After OS X Lion fiasco with Plustek scanners you would think that Ed Hamrick wouldn't hesitate to earn a few quick $$$ if driving Plustek scanners was as trivial as most of the others. So, I have my suspicions that a LOT of stuff is actually going on in driver and not firmware.
I agree. In theory it should make a huge impact at scanning color negatives. In reality I didn't notice much improvement. I guess typical RGB exposure ratios can be 'baked-in' (and probably are - I remember reading that even when you are scanning to raw in Vuescan you should use 'negative film', maybe this is one of the reasons). It's not like you will scan many negatives with 'orange' mask that is actually green. Basic setting should work well enough for most color negatives.
It's not so easy to show this because of the way scanning softwares work (you can't easily tell a software "do not use different RGB exposure"
I should perform raw scans with and without separate RGB exposure compensation, invert the raw scans with an appropriate software (Photoshop sucks badly at that) and avoid misrepresenting the results (for example because of different color balance corrections / gamma curve corrections).
I did some tests time ago, I'll see if I can dig them out.
I did just that. I invert raw scans with ColorPerfect. Sadly, I think I already deleted my files as the results didn't show that it was something worth pursuing further (at least for that negative). I hope to do another test soon.
XFer
-
I'm (very slowly) developing a negative inversion utility (from raw scans), because even ColorPerfect did not cut it, for my tastes.
When it becomes a bit more useable I'll have the tool to do that kind of tests again, in a more meaningful way then I did at the time. I'll report back.
Fernando
visualbassist
Member
i use colorperfect too. for me it's still the best/most time efficient method. imperfect though. i do have trouble creating consistent colors from throughout the roll.
mani
Well-known
One more vote for ColorPerfect - it's the best there is so far...
... but this I would very much like to see! Work faster!
... but this I would very much like to see! Work faster!
brbo
Well-known
Work faster and let us be your beta testers!
johnny.moped
Established
beezil
Established
Ed Hamrick is still waiting for a scanner on loan to add support for it.
I imagine Plustek will send one after the preorders are fullfilled. Let's hope it's as soon as possible.
Fer
i swear....if i run into a bunch of bs with the current software and/or drivers, and ed is still having trouble getting one of his own, i'll ship him MY scanner!
XFer
-
Too bad I can't click "Like"
XFer
-
I'd love to share this software, but it's really complicated to use in a meaningful way.For each film, it requires two calibration shots (one with an IT8 target), plus certain calibration scans for each film+scanner combination.
I'm developing it for myself, just because I'm a scanning nut, but I would not recommend it to anyone else!
Fernando
beezil
Established
finally cleared the decks so I could have a day to use my new plustek.
I really want to post up some scans....
but i can't
I can't get past "processing scan" after the scan phase.
I've lost count on how many times silverflake has crashed.
not fun.
I really want to post up some scans....
but i can't
I can't get past "processing scan" after the scan phase.
I've lost count on how many times silverflake has crashed.
not fun.
Bob Parsons
Established
I've noticed there is a LOT of disk activity while the scan is being processed, and that's with 32GB of RAM in the machine and a large chunk of it available
. Are you sure you're not running out of disk space? Have you tried scanning at a low resolution so that the output file that has to be generated is much smaller?Bob.
clayne
shoot film or die
Vuescan does a similar thing when it runs out of diskspace while writing to the temp file used for a scan. Definitely verify you have enough diskspace because SF might just not be handling the error condition gracefully. One way to verify this indirectly is to scan at a low resolution - if there's no issue then its probably a problem with the amount of projected space a high resolution scan needs.
sny
Member
beezil
Established
sny
Member
I also have 16 Go of RAM and have allocated 10 Go to Silverfast, this functions very well.
Regards,
S.
cabbiinc
Slightly Irregular
Such an innocent question.
beezil
Established
beezil
Established
http://www.rangefinderforum.com/forums/showthread.php?p=2073655#post2073655
started a new thread on tips tricks, trouble shooting etc......
started a new thread on tips tricks, trouble shooting etc......