Eac I now have my test version of VueScan 7.0
When do you plan to release it at least to play
with?
Alex
The examples I posted earlier provide enough
information for a more sophisticated approach.
No, they don't provide any useful information for a more
sophisticated approach.
b *shrug* Actually they do. That's why I selected them. But I'd rather be
b taking pictures than arguing so
Henk, my g was in no way directed to Ed !!
Certainly he is doing a great job and fully get the burden of
the support as well as he moves VueScan forward (rapidly!).
I am probably in the minority of this list because photography is my
hobby: I am a software developer, not a professional
VZ There are several problems here, easy noticable, I highlighted them.
VZ Hardly these could be attributed to lack of my experience with VueScan,
VZ which I admit.
Looks like misaligned scans.. Never saw such ghosts with my LS-30.
VZ 2. Sometimes VueScan get into some strange state, when
Ed However, I'd appreciate it if other people would do these comparisons and post
Ed their results.
Haven't played with 6.6 much, but just scanned a very dark old slide
with noticeble color shift ( Ls-30, 4+1 passes, Restore Colors ) and
noticed that colors used to fill scratches resemble ones
RG Define "quality". The Nikon IV ED is 4000dpi which is higher resolution
RG than a standard Photo CD.
Sorry, but it is 2900dpi. Coolscan 4000 ED is
4000dpi, but IV ED unfortunately is not.
-- Alex
s suggestion it would be to update the 2nd digit whenever, he changes
s how the primary scan is measured, exposed, or scanned. For example,
Ed may be fixing 'raw scan' related bugs. It follows your
'2nd digit' rule, but hardly can be a reason for changing
major version number.
I see that Ed
Certainly, you are right and I agree with you completely. I just wonder
why Ed used such a default, which (perhaps just for me, my slides and
my LS-30) is actually not a default setting which I would use most of the
time.
Of course, I can use my own settings with my own vuescan.ini file, I
