ðòïåëôù 


  áòèé÷ 


Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 

  óôáôøé 


  ðåòóïîáìøîïå 


  ðòïçòáííù 



ðéûéôå
ðéóøíá












     áòèé÷ :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tilted Scans (was: filmscanners: Vuescan feedback )



On Wed, 7 Mar 2001, Arthur Entlich wrote:
> Collin Ong wrote:
> > I believe that the main culprit is the totally nonsensical scan order, as
> > you pointed out.  The SDII scans frames from out to in, which maximizes
> > the time the frames spend exposed to the environment.  Combine that with
> > the fact that the scan direction for each frame is in the *OPPOSITE*
> > direction, which means that after scanning, the *slow* transport has to
> > move back across the frame to get to the next one.  I have no idea what

> Could it be that they were thinking of people who want to scan just one 
> slide, and would otherwise have to wait until the whole carrier was 
> pulled in before scanning, and then having to wait for the whole carrier 
> to eject?  Just a thought.

That's a good thought, and it made me consider those people for a while,
but I concluded:

First off, why add the expense of a film transport for batch scanning,
then make it unbearably painful to use it for batch scanning?

Second, if somebody is scanning only one frame in a strip, then its
equally likely that the frame will be closer to one end or the other.
Either way, there will be some times when they'll have to wait for the
transport, and it'll average out.

But batch scanners suffer every time.

-Collin





 




Copyright © Lexa Software, 1996-2009.