Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] Any New Film Scanners Coming?

2003-05-30 by murph278

Thanks for your response - I've learned alot, just reading everyone's posts.  By long in 
the tooth, I meant that they've been around awhile relatively without new models.  
From someone who doesn't own a film scanner it seems like the current line-up has 
been there a while - buy maybe that's just my impatient nature working too.  Didn't 
mean to degrade the current line-up as a few posts convey'd.  

I'm thinking about buying the Nikon 8000 ED, but don't want to spend the cash if 
another scanner was coming out immenintly with higher resolution - just part of my 
due diligence.  The other problem is that I want to have flexibility to make large 
prints with my medium format scans.  

Anywall all the info is appreciated...thanks...

-Murph

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Austin Franklin" 
<darkroom@i...> wrote:
> Murph,
> 
> > The current line-up is getting long in the tooth...
> 
> I'd be interested in knowing what about the current line-up is long in the
> tooth in your opinion?
> 
> > However, CCD's (& CMOS) technology seems to be
> > moving so fast
> > that I'm suprised no new film scanners have been announced with
> > greater resolution,
> > faster, etc.  Any info would be appreciated...thanks...
> 
> They probably won't get any higher resolution than a 10k sensor which, over
> a 2.25" span is why the current crop are 4k scanners), and they probably
> won't get much faster.  CCD properties haven't gotten such that they require
> less light to register the density of the film...that's a noise issue...
> You are scanning, and have an exposure time of X, and scan, say, 10,000
> lines...so it's quite deterministic to see that 10,000 times X is your
> minimum scan time.
> 
> Do you really need more than 4k SPI?
> 
> Austin

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.