Re: filmscanners: Need feedback on VueScan Idea
Ed asks ... > I'm curious what people think of the idea of having > VueScan with one tab visible at a time (i.e. not having > one group of tabs on the right and the preview/scan > visible on the left, but instead one grouping of all > the tabs). > ... > The problem with having the preview and scan > tabs on the left and the other tabs in a smaller > column on the right is that the tabs don't all > fit, and you need to click an arrow to display > more of the tabs on the right. Myself, I think I'd have a problem with not seeing the controls I'm presently using while I acquire subsequent scans. I therefore wonder if you should be considering what minimum screen resolution you should be designing for. That is, maybe I should simply ask ... "how many of us would need use VS in a 800by600 screen size???" Wouldn't 1024x768 allow for control tabs on the left and display tabs on the right?? (... I always use VS at full screen size ... and 'alt-tab' between applications ...) shAf :o)
Re: filmscanners: Need feedback on VueScan Idea
I like the idea of 1 set of tabs, the split always seemed unnatural to me. - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 06, 2001 6:08 PM Subject: filmscanners: Need feedback on VueScan Idea > I'm curious what people think of the idea of having > VueScan with one tab visible at a time (i.e. not having > one group of tabs on the right and the preview/scan > visible on the left, but instead one grouping of all > the tabs).
RE: filmscanners: Need feedback on VueScan Idea
There's no particular reason to have two groups of tabs. This is completely nonstandard. All tabs should be on the same property sheet. Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] > Sent: Tuesday, March 06, 2001 3:08 PM > To: [EMAIL PROTECTED] > Subject: filmscanners: Need feedback on VueScan Idea > > > I'm curious what people think of the idea of having > VueScan with one tab visible at a time (i.e. not having > one group of tabs on the right and the preview/scan > visible on the left, but instead one grouping of all > the tabs).
Re: filmscanners: Need feedback on VueScan Idea
I am for this. Maris - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 06, 2001 5:08 PM Subject: filmscanners: Need feedback on VueScan Idea | I'm curious what people think of the idea of having | VueScan with one tab visible at a time (i.e. not having | one group of tabs on the right and the preview/scan | visible on the left, but instead one grouping of all | the tabs). | | I've figured out how to make updating the preview | and scan tabs almost instantaneous, so speed | isn't an issue. Is there any particular reason to | have two groups of tabs? | | The advantage of having all the tabs in one group | is that you can display the preview and scan in | more screen space, and the names of all the tabs | are visible at the same time. | | The problem with having the preview and scan | tabs on the left and the other tabs in a smaller | column on the right is that the tabs don't all | fit, and you need to click an arrow to display | more of the tabs on the right. | | Regards, | Ed Hamrick | | P.S. I just got the LS-40 scanning with VueScan | 6.7.6. It works quite nicely.
Re: filmscanners: Need feedback on VueScan Idea
Ed writes ... > I'm curious what people think of the idea of having > VueScan with one tab visible at a time ... ... some thoughts ... First, and I know I've said this before, but Vuescan's scan window presents inaccurate color. Vuescan allows you to create RGB data for every color space other than that for your monitor, so why should the VS scan window be given much of a priority? This is by no means a complaint ... it simply shifts responsibility for properly viewing the scan to an ICM savvy window or application. VS as is, is actually very handy for this capability ... simply create an embedded JPEG and your ICM savvy application opens it automatically. Voila ... the scan properly presented. I actually prefer this ability, and will continue to use it ... in fact I never even see VS's scan window, until I return to VS, maybe for a better scan or the final scan. Still ... that's me ... my workflow and use of VS may cramp someone else's. Here's another thought which may allow a VS control tab to remain visible (... sort of ...). I might think it may be easy for Ed to deliver the scan presentation to an entirely independent window, which allows for a simple clik or alt-tab to return to the same control window ... or possibly better, Ed can create a intimate link to "Vueprint" ... allowing for histograms, exact cropping, and 'save as'. Still, neither of these options allow for accurate presentation of the color spaces available, but for those who choose sRGB because it's close to monitor space, I believe it would be a better option than allowing the scan presentation to monopolize "scan control". In any case ... please don't make it inconvenient to return to the controls in use when the scan button was pushed. It's a small request, but I think it'll make time spent with Vuescan easier. my US$0.02 ... shAf :o)
Re: filmscanners: Need feedback on VueScan Idea
Frank writes ... > There's no particular reason to have two groups of tabs. This is completely > nonstandard. All tabs should be on the same property sheet. We could never make any inovative progress if we stayed with "standards" :o) ... but I understand your gist, and from what I gathered from Ed's description of his reorganization, I think he's addressing the current problems with the 2-set approach. I just had another idea for un-cluttering a tab window, possibly removing entire tab. Since any session, is entirely dedicated to a particular roll of film, why not move all concerns for film type to a menu item?? There may be many "preferences, we'd need less immediate access to, ... preferred color space & whether or not to embed the color space, ... the default application after the scan ... auto scan & auto eject ... watermark ... release memory ... JPEG quality ... all options for the index file ... font size ... beep ... blink ... anyway you get the idea. Can't these be moved to menu items and preference dialogs?? another US$0.02 ... shaf :o)
RE: filmscanners: Need feedback on VueScan Idea
In this case, this standard doesn't exist just for the heck of it. In fact, the Microsoft "User Experience" standard is extremely well thought out and results from thousands of person years experience with user interfaces and we should really think twice before going against its dictates. In fact, the standard is lots better than most Microsoft programs, which would be a lot better off if they followed their own standard religiously. There are reasons for virtually every aspect of the standard and before we go against them, we'd better have thought about it more than the people who over the last 15 years have derived the standard. Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of shAf > Sent: Tuesday, March 06, 2001 7:53 PM > To: [EMAIL PROTECTED] > Subject: Re: filmscanners: Need feedback on VueScan Idea > > > Frank writes ... > > > There's no particular reason to have two groups of tabs. This is > completely > > nonstandard. All tabs should be on the same property sheet. > > We could never make any inovative progress if we stayed with > "standards" :o) ... but I understand your gist, and from what I > gathered from Ed's description of his reorganization, I think he's > addressing the current problems with the 2-set approach.
Re: filmscanners: Need feedback on VueScan Idea
Not necessarily true, What if you're sitting with a small pile of slides to scan, all taken by different people at different times? Maybe a menu check box to save settings for the next scan, or revert to the default settings between scans, with the default assignable. I have been struggling with Insight to find a way to have it prescan with all tools set to default. I keep finding that after the prescan I have to reset all tools. I find that I want to make judgements on each slide individually. BTW, I'm using VueScan now and find I like it. The interface is much more intuitive than it was a few months ago. Thanks ED, you've converted me. Larry Since any session, is entirely dedicated to a >particular roll of film, why not move all concerns for film type to a >menu item?? <:><:><:><:><:><:><:><:><:><:><:><:><:><:><:> Larry Berman Web Sites for Artists: http://BermanGraphics.com Compare Image Compression from the top Graphics Programs: http://ImageCompress.com Explore the Art Show Jury process from a web site: http://ArtShowJury.com <:><:><:><:><:><:><:><:><:><:><:><:><:><:><:>
Re: filmscanners: Need feedback on VueScan Idea
I should be happy to have a single group of tabs, provided that you don't use the dreadful standard MS tab system, where the tabs rotate apparently at random, so that I can't remember which ones I've just looked at. PS: I still remember & love 'Vuescan Classic' where all settings were visible on one screen at the same time. This meant driving the scanner and twiddling its output was analogous to a simplified NASA control centre with knobs & dials, rather than a TV remote control. Regards, Alan T - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 06, 2001 11:08 PM Subject: filmscanners: Need feedback on VueScan Idea > I'm curious what people think of the idea of having > VueScan with one tab visible at a time (i.e. not having > one group of tabs on the right and the preview/scan > visible on the left, but instead one grouping of all > the tabs).
Re: filmscanners: Need feedback on VueScan Idea
- Original Message - From: shAf <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 12:45 AM Subject: Re: filmscanners: Need feedback on VueScan Idea > Myself, I think I'd have a problem with not seeing the controls > I'm presently using while I acquire subsequent scans. Hear, hear! >"how > many of us would need use VS in a 800by600 screen size???" I would, for one. I find the standard text on every 1024x768 display I've seen most uncomfortable to read and fuzzy, and 800x600 on a 17" monitor is just right. >Wouldn't > 1024x768 allow for control tabs on the left and display tabs on the > right?? Yes, but I'd get a headache, and have to visit my optician/optometrist more often. Regards, Alan T
RE: filmscanners: Need feedback on VueScan Idea
I'm sure we're all using at least 1280X1024 and so there is enough real-estate so that the tabs won't overflow. (They don't overflow now, do they? And they will take up less real estate by having them in one control.) There are also two choices the programmer has as to the behavior of tab overflow. One puts out multiple rows and the other puts an arrow at the right that lets you scroll through the tabs. Both options are obnoxious in a most people's opinions. Interfaces should be designed so that tab overflow doesn't happen. One solution when there are a lot of properties is to have nested tab controls, but this is a very thorny problem for programmers, not easily kicked out in a weekend. The Microsoft SDK doesn't support it directly, and I've seldom seen it implemented (I've done it, and know how difficult it is). Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Tyson > Sent: Tuesday, March 06, 2001 9:27 PM > To: [EMAIL PROTECTED] > Subject: Re: filmscanners: Need feedback on VueScan Idea > > > I should be happy to have a single group of tabs, provided > that you don't use the dreadful standard MS tab system, > where the tabs rotate apparently at random, so that I can't > remember which ones I've just looked at. > > PS: I still remember & love 'Vuescan Classic' where all > settings were visible on one screen at the same time. This > meant driving the scanner and twiddling its output was > analogous to a simplified NASA control centre with knobs & > dials, rather than a TV remote control. > > Regards, > > Alan T > > - Original Message - > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 06, 2001 11:08 PM > Subject: filmscanners: Need feedback on VueScan Idea > > > > I'm curious what people think of the idea of having > > VueScan with one tab visible at a time (i.e. not having > > one group of tabs on the right and the preview/scan > > visible on the left, but instead one grouping of all > > the tabs). > >
Re: filmscanners: Need feedback on VueScan Idea
Larry writes ... > What if you're sitting with a small pile of slides to scan, all taken by > different people at different times? > ... This is an example of a situation, for which trying to make VS easy to use, must drive Ed nuts. How to anticipate what is easy, considering one user who scans nothing but Ektachrome, and another who sees individual projects spanning clients or a history of chromes and negatives. I realize some of my suggestions implied leaving some Vuescan users at a disadvantage because they couldn't afford a display which made VS easier to lay out and present. This wasn't my intention ... except to acknowledge even professionals are recognizing Ed's efforts. It is up to Ed regarding my next suggestion ... but I wonder if it isn't time for "Vuescan Pro" ... not that I'm suggesting "Vuescan" remain as is, but if Ed wanted to consider another version, which put demands on the desktop landscape, our hardware, as well as his endevours, I hope I'd be the 1st user asked to pay for the upgrade. shAf :o)
Re: filmscanners: Need feedback on VueScan Idea
Frank Paris wrote: > I'm sure we're all using at least 1280X1024... No, don't be too shure about that: I am working at 1024x768 on a 17" monitor ;-) __ With kind regards, Henk de Jong The Netherlands Email: [EMAIL PROTECTED] Homepage Nepal - Trekking Around Annapurna - Photo Gallery: http://annapurna.wolweb.nl
RE: filmscanners: Need feedback on VueScan Idea
On Tuesday, March 06, shaf wrote: >I just had another idea for un-cluttering a tab window, possibly > removing entire tab. Since any session, is entirely dedicated to a > particular roll of film, why not move all concerns for film type to a > menu item?? There may be many "preferences, we'd need less immediate > access to, ... preferred color space & whether or not to embed the > color space, ... the default application after the scan ... auto scan > & auto eject ... watermark ... release memory ... JPEG quality ... all > options for the index file ... font size ... beep ... blink ... anyway > you get the idea. Can't these be moved to menu items and preference > dialogs?? This strikes me as a very sensible idea. Some settings we want to change from frame to frame. Others only change from session to session, if they ever do. They might well become items in a Settings menu or selections from a Preferences... dialog box. It would help unclutter the main window, and might also make it more clear which settings you need to mess with on a regular basis (something that it took me a while to figure out when I began using VueScan.) Also, this is probably a much longer-term suggestion but while I'm at it: I'd love to be able to preview an entire strip of frames, manually adjust the crop and color correction settings for each frame to my satisfaction, then press Scan and leave it to scan the whole strip while I went away to work on something else. My Minolta can do 6 negative frames at a time at 35mm, and an entire roll of APS at once when I get that adapter. It would help my workflow considerably if I could answer email or write invoices or whatever, rather than having to babysit the scanner for each frame. I can see how this might require some heavy rework of the application, but continuous scanning of longer strips of film seems to be where scanners are headed. Thanks for listening to your users, Ed! Best wishes, Tim Victor [EMAIL PROTECTED]
RE: filmscanners: Need feedback on VueScan Idea
This time you are wrong, Frank. I'm sure there are more than a couple of us with 17" monitors. With a 17", anything over 800x600 is dysfunctional. I'm happy for you that you have something larger, but please don't penalize all of us who don't have the cash or the desk real estate for anything larger. Unless Ed is willing to make a version special for those with the bigger monitors. Hersch At 10:33 PM 03/06/2001 -0800, you wrote: >I'm sure we're all using at least 1280X1024 and so there is enough >real-estate so that the tabs won't overflow. (They don't overflow now, do >they? And they will take up less real estate by having them in one control.) >There are also two choices the programmer has as to the behavior of tab >overflow. One puts out multiple rows and the other puts an arrow at the >right that lets you scroll through the tabs. Both options are obnoxious in a >most people's opinions. Interfaces should be designed so that tab overflow >doesn't happen. One solution when there are a lot of properties is to have >nested tab controls, but this is a very thorny problem for programmers, not >easily kicked out in a weekend. The Microsoft SDK doesn't support it >directly, and I've seldom seen it implemented (I've done it, and know how >difficult it is). > >Frank Paris >[EMAIL PROTECTED] >http://albums.photopoint.com/j/AlbumList?u=62684 > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Tyson > > Sent: Tuesday, March 06, 2001 9:27 PM > > To: [EMAIL PROTECTED] > > Subject: Re: filmscanners: Need feedback on VueScan Idea > > > > > > I should be happy to have a single group of tabs, provided > > that you don't use the dreadful standard MS tab system, > > where the tabs rotate apparently at random, so that I can't > > remember which ones I've just looked at. > > > > PS: I still remember & love 'Vuescan Classic' where all > > settings were visible on one screen at the same time. This > > meant driving the scanner and twiddling its output was > > analogous to a simplified NASA control centre with knobs & > > dials, rather than a TV remote control. > > > > Regards, > > > > Alan T > > > > - Original Message - > > From: <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, March 06, 2001 11:08 PM > > Subject: filmscanners: Need feedback on VueScan Idea > > > > > > > I'm curious what people think of the idea of having > > > VueScan with one tab visible at a time (i.e. not having > > > one group of tabs on the right and the preview/scan > > > visible on the left, but instead one grouping of all > > > the tabs). > > > >
RE: filmscanners: Need feedback on VueScan Idea
On Wednesday, March 07, shAf wrote: > Larry writes ... > >> What if you're sitting with a small pile of slides to scan, all >> taken by >> different people at different times? > >This is an example of a situation, for which trying to make VS > easy to use, must drive Ed nuts. How to anticipate what is easy, > considering one user who scans nothing but Ektachrome, and another who > sees individual projects spanning clients or a history of chromes and > negatives. One of the keys to effective software design is to make the common cases easy and the uncommon cases possible. In the rare case where someone gets stuck with a mixed batch of slides to scan, they'd have waste an extra mouse action per slide. That's a case where they'd quickly learn what the hotkey was for the Preferences... dialog. But the more typical case is working through a batch of a couple of dozen pictures using the same settings. I'd much prefer to have VueScan optimized for that situation. Anyone else? Best wishes, Tim Victor [EMAIL PROTECTED] begin 600 WINMAIL.DAT M>)\^(B,(`0:0" `$```!``$``0>0!@`(Y 0```#H``$(@ <` M& ```$E032Y-:6-R;W-O9G0@36%I;"Y.;W1E`#$(`0V ! `"`@`"``$$ MD 8`X $```$0`P``, (+``\.``(!_P\!50`` M``"!*Q^DOJ,0&9UN`-T!#U0"`&9I;&US8V%N;F5R``(P M`04```!33510`!X``S !' ```&9I;&US8V%N;F5R)V9I;&US M8V%N;F5ROZ=P`*`0,!]R "I /C M`@!P\')Q,B '$P*#`% .]H1C: K 0A@KB<)P"60&D&8$D GP!4#X<&5O"U ?@![1)J@?T#T'@3\D M[QQ_)7\L`E1H#P0`'O $( .197AA;:\GT&D"(+<5$ (0!$`1"X FH-YV(9 N`"#1`V!J%L$$(-IS"K!N`P`?\6,A M@" :D2%!.I3?++(+,3PO&>83H&02C-P;P00:0)@9>TST$D#H$82T!5A(4\UY3N! M>2?_,W 1$#,Q1[ RT">1+.(O(/]0(0A@$4 @8$<12[$G0 7 [R%S,] L4![0 M)RRQ39]2A>1Q=2[@:VP:H"$0"L#O`Z U(T82.0!T1E%3,BYS[4824 EP)M-C M1"$;1B:@V0= ;V<;5QER0CHA1A+[!&!7$GD@\"(@`R!*(BR2FG<%L&LO4SJA M=6<@4C]0IU8A"& G<1E440%D;_YZ))%=L2WP"7 $(#)@7M2_'X$M(!^!$5 ? MTC/!25+!?S*P%6$/<%IR(=)2\AE45KT*4%,B(5#P!3 '<&EA<)\S<%G4'M$M MUS/006X?,/DX<65L$4 HUUR#!Y %0/L#\3N0%```!`0`` M```>`$. "" &``# 1@`XA0```0$`'@`] ;``$%4D4Z( `#``TT_3<``$/( ` end
Re: filmscanners: Need feedback on VueScan Idea
In a message dated 3/7/2001 3:16:19 AM EST, [EMAIL PROTECTED] writes: > This time you are wrong, Frank. I'm sure there are more than a couple of us > with 17" monitors. With a 17", anything over 800x600 is dysfunctional. I'm > happy for you that you have something larger, but please don't penalize all > of us who don't have the cash or the desk real estate for anything larger. > Unless Ed is willing to make a version special for those with the bigger > monitors. I now have my test version of VueScan 7.0 working with set of tabs. It works quite nicely on both small and large monitors. I'm actually surprised how much nicer the user interface seems, since it seems a lot less cluttered and the preview and scan images appear larger. Also, I was asked by one person to put the buttons at the top, above the tabs. This ends up looking quite cluttered, and it's easy to press a tab instead of a button, and vice versa. Putting the buttons at the bottom and having the menus and tabs at the top seems to be quite natural. Unless someone can come up with a convincing argument for putting the buttons at the top, I'm planning on leaving them at the bottom. Regards, Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
I agree too. - Original Message - From: "IronWorks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, 7 March 2001 1:44 Subject: Re: filmscanners: Need feedback on VueScan Idea > I am for this. > > Maris > > - Original Message - > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 06, 2001 5:08 PM > Subject: filmscanners: Need feedback on VueScan Idea > > > | I'm curious what people think of the idea of having > | VueScan with one tab visible at a time (i.e. not having >
Re: filmscanners: Need feedback on VueScan Idea
In a message dated 3/7/2001 3:16:03 AM EST, [EMAIL PROTECTED] writes: > One of the keys to effective software design is to make the common > cases easy and the uncommon cases possible. I completely agree with this. However, one person's logical grouping of controls isn't logical to another person. What do people think of my putting options that affect the raw scan in the Device tab, and other options in other tabs? I've been asked several times in the past few days which options affect the raw scan, and this seems like a logical way to organize things. However, I could also imagine wanting to put the most common options in one tab, and less common options in another, but this would be subject to endless debate about what a "common" option is. Doing it functionally would at least end the debate . It's only a single-click to pull up another tab, so I think it makes sense to organize the tabs functionally. Regards, Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
Eac> I now have my test version of VueScan 7.0 When do you plan to release it at least to play with? Alex
Re: filmscanners: Need feedback on VueScan Idea
> What do people think of my putting options that affect the raw scan > in the Device tab, and other options in other tabs? I've been asked > several times in the past few days which options affect the raw scan, > and this seems like a logical way to organize things. Sounds good to me! __ With kind regards, Henk de Jong The Netherlands Email: [EMAIL PROTECTED] Homepage Nepal - Trekking Around Annapurna - Photo Gallery: http://annapurna.wolweb.nl
RE: filmscanners: Need feedback on VueScan Idea
>From: "Frank Paris" <[EMAIL PROTECTED]> > >I'm sure we're all using at least 1280X1024 and so there is enough >real-estate so that the tabs won't overflow. I use 1024x768. This is the second message I have read in 3 minutes where the author, who has probably never met any of the other Vuescan users, has made a definitive statement about how those people use Vuescan and how they have their computer set-up. I guess if these two messages had of been correct then I would have been impressed by the omniscience of the authors but since they were both wrong then I am just puzzled. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: filmscanners: Need feedback on VueScan Idea
In a message dated 3/7/2001 7:42:04 AM EST, [EMAIL PROTECTED] writes: > When do you plan to release it at least to play > with? Probably before this weekend. Regards, Ed Hamrick
RE: filmscanners: Need feedback on VueScan Idea
>From: Tim Victor <[EMAIL PROTECTED]> > >But the more typical case is working through a batch of a couple >of dozen pictures using the same settings. And how do you know that is the more typical case? Maybe you are right, but please point to the evidence that supports your assertion. Maybe Ed has a pretty good feel for the typical use of Vuescan and will come up with something that will be fine. I'm just concerned that a few people making very definitive statements with no evidence to back them up will influence Ed to make changes that may in fact *not* be best for the most people. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: filmscanners: Need feedback on VueScan Idea
"Hersch Nitikman" <[EMAIL PROTECTED]> wrote: > This time you are wrong, Frank. I'm sure there are more than a couple of us > with 17" monitors. With a 17", anything over 800x600 is dysfunctional. I'm > happy for you that you have something larger, but please don't penalize all > of us who don't have the cash or the desk real estate for anything larger. I agree about not designing on the assumption of 1280x1024, but I have always run my 17" monitors in 1024x768. I wouldn't call it dysfunctional. Having said that, I think that designing for a minimum 800x600 would be OK since anyone using vuescan would surely be using Photoshop or PSP, both of which are unworkable in 640x480. I know Ed has stated in the past that most of the reason for Vuescan's somewhat crowded interface is to fit it into a 640x480 screen. Rob PS It occurs to me that Nikonscan fits into a lot less than 640x480, but then it has its own pecularities of interface design which are frankly unconventional and in many cases counter-intuitive.
Re: filmscanners: Need feedback on VueScan Idea
In a message dated 3/7/2001 9:21:16 AM EST, [EMAIL PROTECTED] writes: > I know Ed has stated in the past that most of the > reason for Vuescan's somewhat crowded interface is to fit it into a 640x480 > screen. I plan to continue making it useful on a 640x480 screen, but this is quite a bit easier now with only one set of tabs. Regards, Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
shAF wrote, re Tabs: >Since any session, is entirely dedicated to a particular roll of film That's true for photographers with filmstrips, but not for archivers with slides and/or negs from many shoots mixed together, nor for reflective (flatbed) use which Vuescan also supports. > Can't these [tabs] be moved to menu items and preference dialogs?? It would allow larger viewing space (good), but going to pull-downs from the current at-a-glance tab organization would be a step backward, IMO, and individual dialog boxes *rarely* include the specific item I need for the problem at hand, in my experience. I prefer tabs--you can see your choices without going to the Help key. Having clear, settable Preference choices for *both* display types could work nicely for different workflow methods, if it doesn't confuse Vuescan's clean and functional GUI too much. Preference Choices are under-used and over-complicated in most Windows programs I've used (or simplistic, unintelligible, and not-findable, which is even worse). It's hard to cover all the bases for every user--some designers don't even try. Best regards--LRA --- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com
Re: filmscanners: Need feedback on VueScan Idea
>From: "shAf" <[EMAIL PROTECTED]> > >Since any session, is entirely dedicated to a >particular roll of film, why not move all concerns for film type to a >menu item?? Not sure how you are able to make such a definitive statement. Almost all of my scanning sessions involve scanning frames from various rolls of film of various type. It is quite rare for me to only scan a bunch of frames from one roll. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
RE: filmscanners: Need feedback on VueScan Idea
Buttons pertinent only to specific tabs should be on that tab, not necessarily on the top. They should not be visible on other tabs. The Exit button just takes up extra real estate and shouldn't be a button at all. I haven't had time to read all the emails on this topic so the following point perhaps has been made before: buttons should be fixed in size and should not scale with the size of the application window. Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, March 07, 2001 2:45 AM > To: [EMAIL PROTECTED] > Subject: Re: filmscanners: Need feedback on VueScan Idea > > > Also, I was asked by one person to put the buttons at the top, above > the tabs. This ends up looking quite cluttered, and it's easy to press > a tab instead of a button, and vice versa. Putting the buttons at > the bottom and having the menus and tabs at the top seems to be > quite natural. Unless someone can come up with a convincing > argument for putting the buttons at the top, I'm planning on leaving > them at the bottom. > > Regards, > Ed Hamrick
RE: filmscanners: Need feedback on VueScan Idea
Ed writes ... > In a message dated 3/7/2001 3:16:03 AM EST, > [EMAIL PROTECTED] writes: > > > One of the keys to effective software design is to make the common > > cases easy and the uncommon cases possible. > > I completely agree with this. .. > > What do people think of my putting options that affect the raw scan > in the Device tab, and other options in other tabs? I've been asked > several times in the past few days which options affect the > raw scan, and this seems like a logical way to organize things. > > ... I happen to believe VS's "raw scan" versus "subsequent crop" philosophy is its greatest strength and what sets it apart form other softwares. I believe you ought to emphasize this, and make it conceptually easy to use, by keeping what addresses the raw scan in one tab, separated from what addresses subsequent cropping. anotheu US$0.02 ... shAf :o)
RE: filmscanners: Need feedback on VueScan Idea
The tabs will still fit. Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Henk de Jong > Sent: Wednesday, March 07, 2001 12:08 AM > To: [EMAIL PROTECTED] > Subject: Re: filmscanners: Need feedback on VueScan Idea > > > Frank Paris wrote: > > > I'm sure we're all using at least 1280X1024... > > No, don't be too shure about that: I am working at 1024x768 on a > 17" monitor > ;-) > > > __ > With kind regards, > > Henk de Jong > The Netherlands > Email: > [EMAIL PROTECTED] > Homepage Nepal - Trekking Around Annapurna - Photo Gallery: > http://annapurna.wolweb.nl >
Re: filmscanners: Need feedback on VueScan Idea
shAF wrote: >... but I wonder if it isn't time for "Vuescan Pro" It probably is, but then that would relegate Ed to the position of "Manager" with a staff of 200 including programmers, analysts, expediters, secretaries, accounts-receivable bookkeepers and various "flacks." I know a *wonderful* joke about that sort of transition that I'd share with anyone that wants to hear it, Off List. Otherwise, I think that "letting Ed be Ed" and "letting Vuescan be Vuescan" is the safest route to "The Best of All Possible Worlds." Best regards--LRA --- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com
RE: filmscanners: Need feedback on VueScan Idea
Lynn writes ... > shAF wrote, re Tabs: > > >Since any session, is entirely dedicated to a > particular roll of film > > That's true for photographers with filmstrips, but not > for archivers with slides and/or negs from many shoots > mixed together, ... I agree with you ... I should have qualified my statement with something like "usually" or "commonly" ... and I even have a backlog of differing films to get at one of these days ... and it is probably becoming more common that people who take on a variety of clientel are becoming VS users. I am sure Ed took my "definitive" statement with a grain of salt, and I'm sure I'll be happy with however he makes V.7 better. shAf :o)
RE: filmscanners: Need feedback on VueScan Idea
> The problem with having the preview and scan > tabs on the left and the other tabs in a smaller > column on the right is that the tabs don't all > fit, and you need to click an arrow to display > more of the tabs on the right. > Do the tabs and the regions they control have to be the same size? That is, could you make the tabs occupy just one row across the top of the window, the options occupy one column on the left side, and the image occupy the remainder? I think a user would require about 5 seconds to adjust to this type of layout, much less time than figuring out multi-layer tabs. I really hate multi-rows of tabs - I have set VueScan's control width so that I end up with just one row of tabs. This wastes a little space, but...
RE: filmscanners: Need feedback on VueScan Idea
Tim wrote: >It would help my workflow considerably if I could answer email or write invoices or whatever, rather than having to babysit the scanner for each frame. It would help everybody's, I'm sure. The solution is co-processors, which is a hardware fix and not in Vuescan's purview. Amiga still has the patents on that, I think (and please forgive me for constantly and good-naturedly bugging you long-time Mac & PC people on that point, and my I-told-you-so rants :-)). It's one of those good ideas that got into the wrong hands and never met its full potential as a result. But the patents will run, soon, and maybe then our new computers can do what we want them to do when we want them to do it. :-) Best regards--LRA --- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com
RE: filmscanners: Need feedback on VueScan Idea
> >I'm sure we're all using at least 1280X1024 and so there is enough > >real-estate so that the tabs won't overflow. > When I read this, I thought it must be tongue in cheek.
RE: filmscanners: Need feedback on VueScan Idea
Tim wrote: >One of the keys to effective software design is to make the common cases easy and the uncommon cases possible. That's well put, Tim, and it's beginning to happen, even. >In the rare case where someone gets stuck with a mixed batch of slides to scan, they'd have waste an extra mouse action per slide. That's a case where they'd quickly learn what the hotkey was for the Preferences...dialog. Rare? I don't think so. Larry B and I are from different disciplines, yet we *both* had similar comments on our experiences. The Real World Fact is that there *is* no "typical case" in prosumer computer graphics. All of us have different applications and goals, and we're "doin' our thing" as best we can for the best results we can get, without having to upgrade to a very-expensive Sun Workstation and custom software--which I would probably give my left arm to have, but for the fact that I need it "on rare occasion!" :-) What makes Vuescan so great is that it does so many things on so many levels, and does them well. Change that, and you change its scope and value for us schlubs who have a job to do and find VS is a good tool and a good buy at a good price. No offense to anyone (please), but I LIKE Vuescan, and I don't want it to become another Photoshop or whatever. Its many features have pulled my butt out of the fire on many occasions, and I can't really say that about very many other program I've ever used in 20-years of computer graphics. :-) Best regards--LRA --- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com
Re: filmscanners: Need feedback on VueScan Idea
[EMAIL PROTECTED] wrote: > Also, I was asked by one person to put the buttons at the top, above > the tabs. This ends up looking quite cluttered, and it's easy to press > a tab instead of a button, and vice versa. Putting the buttons at > the bottom and having the menus and tabs at the top seems to be > quite natural. Unless someone can come up with a convincing > argument for putting the buttons at the top, I'm planning on leaving > them at the bottom. Main reason for it is the same reason that many "toolbars" in programs are at the top just below the menus. The reason is mouse movement. If one exclusively uses one set or the other as alternatives, then it doesn't matter -- but if one goes from one to the other during use, then mouse movement is minimized ("ease of use") by having them next to another. Mike K. > > Regards, > Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
Ed wrote: >What do people think of my putting options that affect the raw scan in the Device tab, and other options in other tabs? I've been asked several times in the past few days which options affect the raw scan, and this seems like a logical way to organize things. Seems to me that that would follow only if people thought of the Raw Scan as "Device Oriented," whereas I would not ("Device" having a HW connotation). The Color tab would be more logical, but not semantically correct. I would personally look for "Raw Scan/File" under an "Output" tab, which doesn't currently exist. Possibly it should, but that wouldn't necessarily be downwardly compatible with previous versions. It's a dilema. I'm *so* glad that you're a much better developer than I am! Best regards--LRA --- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com
Re: filmscanners: Need feedback on VueScan Idea
Unfortunately I've never seen that one. Maris - Original Message - From: "Alan Tyson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 06, 2001 11:27 PM Subject: Re: filmscanners: Need feedback on VueScan Idea | I should be happy to have a single group of tabs, provided | that you don't use the dreadful standard MS tab system, | where the tabs rotate apparently at random, so that I can't | remember which ones I've just looked at. | | PS: I still remember & love 'Vuescan Classic' where all | settings were visible on one screen at the same time. This | meant driving the scanner and twiddling its output was | analogous to a simplified NASA control centre with knobs & | dials, rather than a TV remote control. | | Regards, | | Alan T | | - Original Message - | From: <[EMAIL PROTECTED]> | To: <[EMAIL PROTECTED]> | Sent: Tuesday, March 06, 2001 11:08 PM | Subject: filmscanners: Need feedback on VueScan Idea | | | > I'm curious what people think of the idea of having | > VueScan with one tab visible at a time (i.e. not having | > one group of tabs on the right and the preview/scan | > visible on the left, but instead one grouping of all | > the tabs). | |
Re: filmscanners: Need feedback on VueScan Idea
*We* may be but there are others out in this big wide world - many new to scanning, to graphics. I'm sure there are those of us even besides Alan Tyson who do. I'm also sure that Ed wants to sell to these people as well as to those of us with higher-end equipment. After all, we already have the program and are no longer potential customers. Maris - Original Message - From: "Frank Paris" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 12:33 AM Subject: RE: filmscanners: Need feedback on VueScan Idea | I'm sure we're all using at least 1280X1024 and so there is enough | real-estate so that the tabs won't overflow. (They don't overflow now, do | they? And they will take up less real estate by having them in one control.) | There are also two choices the programmer has as to the behavior of tab | overflow. One puts out multiple rows and the other puts an arrow at the | right that lets you scroll through the tabs. Both options are obnoxious in a | most people's opinions. Interfaces should be designed so that tab overflow | doesn't happen. One solution when there are a lot of properties is to have | nested tab controls, but this is a very thorny problem for programmers, not | easily kicked out in a weekend. The Microsoft SDK doesn't support it | directly, and I've seldom seen it implemented (I've done it, and know how | difficult it is). | | Frank Paris | [EMAIL PROTECTED] | http://albums.photopoint.com/j/AlbumList?u=62684 | | > -Original Message- | > From: [EMAIL PROTECTED] | > [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Tyson | > Sent: Tuesday, March 06, 2001 9:27 PM | > To: [EMAIL PROTECTED] | > Subject: Re: filmscanners: Need feedback on VueScan Idea | > | > | > I should be happy to have a single group of tabs, provided | > that you don't use the dreadful standard MS tab system, | > where the tabs rotate apparently at random, so that I can't | > remember which ones I've just looked at. | > | > PS: I still remember & love 'Vuescan Classic' where all | > settings were visible on one screen at the same time. This | > meant driving the scanner and twiddling its output was | > analogous to a simplified NASA control centre with knobs & | > dials, rather than a TV remote control. | > | > Regards, | > | > Alan T | > | > - Original Message - | > From: <[EMAIL PROTECTED]> | > To: <[EMAIL PROTECTED]> | > Sent: Tuesday, March 06, 2001 11:08 PM | > Subject: filmscanners: Need feedback on VueScan Idea | > | > | > > I'm curious what people think of the idea of having | > > VueScan with one tab visible at a time (i.e. not having | > > one group of tabs on the right and the preview/scan | > > visible on the left, but instead one grouping of all | > > the tabs). | > | > | |
Re: filmscanners: Need feedback on VueScan Idea
I disagree - sometimes I adjust "film type" - maybe the film is old, maybe it's off, whatever. Also, all sessions are not necessarily devoted to one film type - I may want 2-3 frames from one film, and one from another, etc. for a specific project. I prefer all of these controls where they are now, with the exception of Ed's suggestion to combine the tabs/panels and move some options around but tabs still accessible. Maris - Original Message - From: "shAf" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 06, 2001 9:52 PM Subject: Re: filmscanners: Need feedback on VueScan Idea | I just had another idea for un-cluttering a tab window, possibly | removing entire tab. Since any session, is entirely dedicated to a | particular roll of film, why not move all concerns for film type to a | menu item?? There may be many "preferences, we'd need less immediate | access to, ... preferred color space & whether or not to embed the | color space, ... the default application after the scan ... auto scan | & auto eject ... watermark ... release memory ... JPEG quality ... all | options for the index file ... font size ... beep ... blink ... anyway | you get the idea. Can't these be moved to menu items and preference | dialogs?? | | another US$0.02 ... shaf :o) |
Re: filmscanners: Need feedback on VueScan Idea
I like this idea very much - I can conceive of ignoring all the other settings and just setting the Device/Raw Scan Setting tab and checking the preview before continuing with the others (not in all cases but some). I agree with your logic that the settings should be logically arranged - thus easier to remember where they are for all - rather than guessing what might be the most or more 'common' way of using them. Maris - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 5:22 AM Subject: Re: filmscanners: Need feedback on VueScan Idea | In a message dated 3/7/2001 3:16:03 AM EST, [EMAIL PROTECTED] writes: | | > One of the keys to effective software design is to make the common | > cases easy and the uncommon cases possible. | | I completely agree with this. However, one person's logical grouping | of controls isn't logical to another person. | | What do people think of my putting options that affect the raw scan | in the Device tab, and other options in other tabs? I've been asked | several times in the past few days which options affect the raw scan, | and this seems like a logical way to organize things. | | However, I could also imagine wanting to put the most common options | in one tab, and less common options in another, but this would be | subject to endless debate about what a "common" option is. Doing | it functionally would at least end the debate . | | It's only a single-click to pull up another tab, so I think it makes | sense to organize the tabs functionally. | | Regards, | Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
shAf wrote: > > Ed writes ... > > > What do people think of my putting options that affect the raw scan > > in the Device tab, and other options in other tabs? > > I happen to believe VS's "raw scan" versus "subsequent crop" > philosophy is its greatest strength and what sets it apart form other > softwares. I believe you ought to emphasize this, and make it > conceptually easy to use, by keeping what addresses the raw scan in > one tab, separated from what addresses subsequent cropping. > Yes! --Alan
RE: filmscanners: Need feedback on VueScan Idea
On Wed, 7 Mar 2001, Lynn Allen wrote: > Tim wrote: > > >It would help my workflow considerably if I could answer email or write > invoices or whatever, rather than having to babysit the scanner for each > frame. > > It would help everybody's, I'm sure. The solution is co-processors, which is Actually the solution is not co-processors. The reason you can't do this is because VS doesn't currently provide a way to prescan multiple frames, select crop and image processing settings for each, then batch scan and process them all. > a hardware fix and not in Vuescan's purview. Amiga still has the patents on > that, I think (and please forgive me for constantly and good-naturedly I'm not sure what patents Amiga has on this, but both Macs and PC's both offer multiprocessor systems, which have been available for a few years now. -Collin
Re: filmscanners: Need feedback on VueScan Idea
Mike Kersenbrock wrote: > [EMAIL PROTECTED] wrote: > > > Also, I was asked by one person to put the buttons at the top, above > > the tabs. This ends up looking quite cluttered, and it's easy to press > > a tab instead of a button, and vice versa. Putting the buttons at > > the bottom and having the menus and tabs at the top seems to be > > quite natural. Unless someone can come up with a convincing > > argument for putting the buttons at the top, I'm planning on leaving > > them at the bottom. > > Main reason for it is the same reason that many "toolbars" in programs are > at the top just below the menus. The reason is mouse movement. If one > exclusively uses one set or the other as alternatives, then it doesn't > matter -- but if one goes from one to the other during use, then mouse > movement is minimized ("ease of use") by having them next to another. > But, a properly designed program usually uses speed keys for the buttons anyway, and location is not a concern. I have yet to meet many users that don't recohgnize the efficiencies picked up by shortcuts, aliases, and speed keys. Even the function keys can be programmed to handle the tabs. Jim Snyder, Software Engineer
RE: filmscanners: Need feedback on VueScan Idea
> > >It would help my workflow considerably if I could answer email or write > > invoices or whatever, rather than having to babysit the scanner for each > > frame. > > > > It would help everybody's, I'm sure. The solution is > co-processors, which is > > Actually the solution is not co-processors. Most scanners do hog the system quite a bit. The issue is both hardware and software from what I can tell. The issue is the data is sent as it is scanned, and as such, there is a real time requirement on the software to take the data as it arrives. Polling is typically faster than interrupts in this case, and as such, the system is bogged down in a loop checking for data... A solution would be either a SCSI controller or scanner with some large amount of memory, and you only transfer data when you have a lot to transfer, and make it interrupt driven, instead of polled. You don't need the entire image at once, but possibly two 4M buffers that get ping-pong'd or something like that would certainly aid the situation. A caching controller could be made to accommodate this, but I doubt they currently will handle it the way one would want it to for a scanner.
RE: filmscanners: Need feedback on VueScan Idea
>From: "shAf" <[EMAIL PROTECTED]> > > I happen to believe VS's "raw scan" versus "subsequent crop" >philosophy is its greatest strength and what sets it apart form other >softwares. I believe you ought to emphasize this, and make it >conceptually easy to use, by keeping what addresses the raw scan in >one tab, separated from what addresses subsequent cropping. Yes, I agree with this. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: filmscanners: Need feedback on VueScan Idea
Rob Geraghty wrote: >anyone using vuescan would surely be using Photoshop or PSP, both of >which are unworkable in 640x480. Unworkable? I'm using PS at 640 x 480 (and using Vuescan) and both work fine. Colin Maddock
Re: filmscanners: Need feedback on VueScan Idea
In a message dated 3/7/2001 12:05:50 PM EST, [EMAIL PROTECTED] writes: > Main reason for it is the same reason that many "toolbars" in programs are > at the top just below the menus. The reason is mouse movement. If one > exclusively uses one set or the other as alternatives, then it doesn't > matter -- but if one goes from one to the other during use, then mouse > movement is minimized ("ease of use") by having them next to another. I just did a version to put the buttons at the top (it's 4 lines of code difference). It looks a lot better with the buttons at the bottom. It looks really cluttered with the buttons at the top, since there are then three rows of things at the top: the menu bar, the buttons and then the tabs. I've organized the tabs from left to right in the order that they'll typically be used: Device, Crop, Process, Files, Prefs, Preview (for image), Scan (for image). I'm going to try to order the options within each tab in a way that's somewhat related to frequency of use. I've also removed those things from the menus that can be done with a button to simplify things a bit. The typical mouse movement will be to select a tab (at the top), change an option (on average in the middle left of the window) and then press a button (at the bottom of the window). This left to right, top to bottom mouse movement seems natural. Also, when a button is pressed, the status will be updated at the bottom, which is near where the eye will leave off after clicking a button. I quite like this new arrangement, and I'm going to release it as the first 7.0 beta in a day or two. I'd be happy to tweak it some more at that time. To top it off, the LS-40 is working as close to perfectly as I can tell. It was amazing how few the required changes were. Regards, Ed Hamrick
RE: filmscanners: Need feedback on VueScan Idea
On Wednesday, March 07, Henry Richardson wrote: >>From: "Frank Paris" <[EMAIL PROTECTED]> >> >>I'm sure we're all using at least 1280X1024 and so there is enough >>real-estate so that the tabs won't overflow. > > I use 1024x768. As do I. I don't have the desk space for a larger monitor. Tim Victor [EMAIL PROTECTED]
RE: filmscanners: Need feedback on VueScan Idea
On Wednesday, March 07, Lynn Allen wrote: > Tim wrote: >>It would help my workflow considerably if I could answer email or write >> invoices or whatever, rather than having to babysit the scanner for each >> frame. > > It would help everybody's, I'm sure. The solution is co-processors, which is > a hardware fix and not in Vuescan's purview. Amiga still has the patents on > that, I think (and please forgive me for constantly and good-naturedly > bugging you long-time Mac & PC people on that point, and my I-told-you-so > rants :-)). No problem. I did some Amiga programming back in the day and they did have some nice ideas. But with the accelerated graphics controllers I/O subsystems on current PC's, I think the Intel world has just about caught up by now. :-) As I said in another message, I don't mind leaving my main PC alone to get the batch scanning done as quickly as possible. I'll work on my laptop or read a magazine or something in the meantime. What I meant to suggest was simply the ability to preview a whole batch scan, manually set the crop, rotation, image processing, etc., for each frame (and yes, interactive preview of color correction settings, as others have suggested, would be lovely!) and then scan the batch unattended. Best wishes, Tim Victor [EMAIL PROTECTED]
RE: filmscanners: Need feedback on VueScan Idea
Wednesday, March 07, Collin Ong wrote: > On Wed, 7 Mar 2001, Lynn Allen wrote: >> Tim wrote: >> >>>It would help my workflow considerably if I could answer email or write >>> invoices or whatever, rather than having to babysit the scanner for each >>> frame. >> >> It would help everybody's, I'm sure. The solution is co-processors, which is > > Actually the solution is not co-processors. The reason you can't do this > is because VS doesn't currently provide a way to prescan multiple frames, > select crop and image processing settings for each, then batch scan > and process them all. Yes, Collin, that's what I was thinking of. I wasn't so much concerned with being able to using the scanning PC while it was scanning. I can move to my laptop to work on something else, or go get a snack or make a phone call. As you say, I'd just like to be able to batch scan a strip of frames with pre-entered manual settings for cropping and image processing. VueScan's batch scanning is very nice if you're using the automatic options for those features, but I prefer to set them myself. Consequently I'm tied to the computer for a couple of hours when I could be doing something else. Best wishes, Tim Victor [EMAIL PROTECTED]
RE: filmscanners: Need feedback on VueScan Idea
On Wednesday, March 07, Henry Richardson wrote: >>From: Tim Victor <[EMAIL PROTECTED]> >> >>But the more typical case is working through a batch of a couple >>of dozen pictures using the same settings. > > And how do you know that is the more typical case? I don't really, Henry. It seemed reasonable to me. Sometimes I'm scanning a frame from here and two from there, but the cases where I'm really worried about throughput and work flow are the ones where I have several full rolls of film to get through. Maybe I'm the weird one though... > Maybe Ed has a > pretty good feel for the typical use of Vuescan and will come up with > something that will be fine. I'm just concerned that a few people making > very definitive statements with no evidence to back them up will influence > Ed to make changes that may in fact *not* be best for the most people. Yes, it's Ed's program and ultimately Ed's call. All we can do is provide him with as much feedback as possible based on our own experience, and then count on Ed's judgement to make the right calls. Best wishes, Tim Victor [EMAIL PROTECTED]
RE: filmscanners: Need feedback on VueScan Idea
> I did some Amiga programming back in the day and they > did have some nice ideas. But with the accelerated graphics controllers > I/O subsystems on current PC's, I think the Intel world has just about > caught up by now. :-) The Amiga was basically a grown up Atari. The first "graphics accelerator" for consumer use was in the Atari 400/800 as far as I know. There were other graphics processors before Atari, namely those used by Computervision and Aplicon. I do not believe the Apple II had a graphics accelerator at that time...it was purely memory mapped display memory...
Re: filmscanners: Need feedback on VueScan Idea
I mean Vuescan v5.9t53 (Feb2000) and earlier. It didn't have a preview, and Ed's made many algorithmic strides since then, so it was primitive by current standards. However, all settings were visible on a single screen. Alan T - Original Message - From: IronWorks <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 5:02 PM Subject: Re: filmscanners: Need feedback on VueScan Idea > Unfortunately I've never seen that one. > > Maris > > - Original Message - > From: "Alan Tyson" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 06, 2001 11:27 PM > Subject: Re: filmscanners: Need feedback on VueScan Idea >. > I still remember & love 'Vuescan Classic' .
Re: filmscanners: Need feedback on VueScan Idea
Ed, This all sound marvelousbut does this mean my Prescan Window suggestion didn't make the cut? Is there hope for this in the future? or is it just too much programming. Bob Kehl - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 1:55 PM Subject: Re: filmscanners: Need feedback on VueScan Idea > > I've organized the tabs from left to right in the order that > they'll typically be used: Device, Crop, Process, Files, > Prefs, Preview (for image), Scan (for image). I'm going > to try to order the options within each tab in a way that's > somewhat related to frequency of use. > > I've also removed those things from the menus that can be > done with a button to simplify things a bit. > > I quite like this new arrangement, and I'm going to release > it as the first 7.0 beta in a day or two. I'd be happy to tweak > it some more at that time. > > To top it off, the LS-40 is working as close to perfectly as > I can tell. It was amazing how few the required changes > were. > > Regards, > Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
In a message dated 3/7/2001 5:04:49 PM EST, [EMAIL PROTECTED] writes: > This all sound marvelousbut does this mean my Prescan Window suggestion > didn't make the cut? Is there hope for this in the future? or is it just > too much programming. Can you describe what you mean by a "Prescan" tab again? Is it basically the same thing as the "Scan" tab, except without any files being output? Can't this be accomplished by just turning off outputting files in the Files tab and then pressing the "Scan" button? Regards, Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
Colin wrote: >Rob Geraghty wrote: >>anyone using vuescan would surely be using Photoshop or PSP, both of >>which are unworkable in 640x480. > Unworkable? I'm using PS at 640 x 480 (and using Vuescan) and > both work fine. Sorry, I didn't mean to say they *wouldn't* work. I was just saying that at least in my opinion, 640x480 leaves too little desktop space to accomodate all the tools, buttons etc and still have enough of the image actually visible unless the image is small. When designing interfaces, I find 800x600 is a minimum to be able to space things out and have a "nice" display. Trying to squeeze everything into a smaller desktop takes a lot more work. Rob Rob Geraghty [EMAIL PROTECTED] http://wordweb.com
RE: filmscanners: Need feedback on VueScan Idea
Lynn wrote: > It would help everybody's, I'm sure. The solution is > co-processors, which is a hardware fix and not in > Vuescan's purview. Amiga type coprocessing is no different from hardware acceleration on any number of peripherals like graphic accelerator cards, DMA capable drives, etc. Those issues aren't really important in interface design - the hardware is largely transparent to the software as far as the Windows display is concerned. Rob Rob Geraghty [EMAIL PROTECTED] http://wordweb.com
Re: filmscanners: Need feedback on VueScan Idea
- Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 3:27 PM Subject: Re: filmscanners: Need feedback on VueScan Idea > In a message dated 3/7/2001 5:04:49 PM EST, [EMAIL PROTECTED] writes: > > > This all sound marvelousbut does this mean my Prescan Window suggestion > > didn't make the cut? Is there hope for this in the future? or is it just > > too much programming. > > Can you describe what you mean by a "Prescan" tab again? > Is it basically the same thing as the "Scan" tab, except without > any files being output? Can't this be accomplished by just > turning off outputting files in the Files tab and then pressing > the "Scan" button? is the prescan in NikonScan just a scan? it's seems awful fast, even faster than the fastest vuescan preview. ~j
RE: filmscanners: Need feedback on VueScan Idea
Nope. I was dead serious, and obviously totally deluded. Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Shough, Dean > Sent: Wednesday, March 07, 2001 8:12 AM > To: '[EMAIL PROTECTED]' > Subject: RE: filmscanners: Need feedback on VueScan Idea > > > > >I'm sure we're all using at least 1280X1024 and so there is enough > > >real-estate so that the tabs won't overflow. > > > > When I read this, I thought it must be tongue in cheek.
RE: filmscanners: Need feedback on VueScan Idea
Then it's a good thing that no one, including myself, is proposing an interface that would require anything higher than 640X480. Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of IronWorks > Sent: Wednesday, March 07, 2001 9:10 AM > To: [EMAIL PROTECTED] > Subject: Re: filmscanners: Need feedback on VueScan Idea > > > *We* may be but there are others out in this big wide world - many new to > scanning, to graphics. I'm sure there are those of us even besides Alan > Tyson who do. I'm also sure that Ed wants to sell to these people as well > as to those of us with higher-end equipment. After all, we > already have the > program and are no longer potential customers. > > Maris > > - Original Message - > From: "Frank Paris" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, March 07, 2001 12:33 AM > Subject: RE: filmscanners: Need feedback on VueScan Idea > > > | I'm sure we're all using at least 1280X1024 and so there is enough > | real-estate so that the tabs won't overflow. (They don't > overflow now, do > | they? And they will take up less real estate by having them in one > control.) > | There are also two choices the programmer has as to the behavior of tab > | overflow. One puts out multiple rows and the other puts an arrow at the > | right that lets you scroll through the tabs. Both options are > obnoxious in > a > | most people's opinions. Interfaces should be designed so that > tab overflow > | doesn't happen. One solution when there are a lot of properties > is to have > | nested tab controls, but this is a very thorny problem for programmers, > not > | easily kicked out in a weekend. The Microsoft SDK doesn't support it > | directly, and I've seldom seen it implemented (I've done it, > and know how > | difficult it is). > | > | Frank Paris > | [EMAIL PROTECTED] > | http://albums.photopoint.com/j/AlbumList?u=62684 > | > | > -Original Message- > | > From: [EMAIL PROTECTED] > | > [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Tyson > | > Sent: Tuesday, March 06, 2001 9:27 PM > | > To: [EMAIL PROTECTED] > | > Subject: Re: filmscanners: Need feedback on VueScan Idea > | > > | > > | > I should be happy to have a single group of tabs, provided > | > that you don't use the dreadful standard MS tab system, > | > where the tabs rotate apparently at random, so that I can't > | > remember which ones I've just looked at. > | > > | > PS: I still remember & love 'Vuescan Classic' where all > | > settings were visible on one screen at the same time. This > | > meant driving the scanner and twiddling its output was > | > analogous to a simplified NASA control centre with knobs & > | > dials, rather than a TV remote control. > | > > | > Regards, > | > > | > Alan T > | > > | > - Original Message - > | > From: <[EMAIL PROTECTED]> > | > To: <[EMAIL PROTECTED]> > | > Sent: Tuesday, March 06, 2001 11:08 PM > | > Subject: filmscanners: Need feedback on VueScan Idea > | > > | > > | > > I'm curious what people think of the idea of having > | > > VueScan with one tab visible at a time (i.e. not having > | > > one group of tabs on the right and the preview/scan > | > > visible on the left, but instead one grouping of all > | > > the tabs). > | > > | > > | > | >
Re: filmscanners: Need feedback on VueScan Idea
Jules writes ... > is the prescan in NikonScan just a scan? it's seems awful fast, even faster > than the fastest vuescan preview. The "prescan" in NS simply measures the proper exposure, altho it also measures the exposure during the "preview" (one of the preferences). With Vuescan, the exposure is measured according to your preference as well, during the preview (default), or for (presumably) batch scans, before the scan. HTH ... shAf :o)
Re: filmscanners: Need feedback on VueScan Idea
- Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 5:27 PM Subject: Re: filmscanners: Need feedback on VueScan Idea > Can you describe what you mean by a "Prescan" tab again? > Is it basically the same thing as the "Scan" tab, except without > any files being output? Can't this be accomplished by just > turning off outputting files in the Files tab and then pressing > the "Scan" button? > > Regards, > Ed Hamrick The Prescan Tab would display a Prescan Window. The Prescan Window would display low resolution thumbnail prescans of whatever film was placed in the scanner, up to 40 frames. These thumbnails would be selectable via the mouse using standard Windows selection techniques. (left click, control-left click, shift-left click). The selection would show up in the Frame Number settings. While your at it, a histogram with mouse selectable white and black points would be way cool. Add a little Unsharp Mask and most images could be scanned and be ready to go straight out of Vuescan. Photoshop would only be needed for image manipulation or darkroom type finessing, not for scanning images. And the value of Vuescan will have grown exponentially (IMO). Bob Kehl
Re: filmscanners: Need feedback on VueScan Idea
Ed: Taht works for me. i have not read the help file for some time and I am sure that insruction iis in there. All I have to do is remember to click it back on to get the output file. Gordon [EMAIL PROTECTED] wrote: > In a message dated 3/7/2001 5:04:49 PM EST, [EMAIL PROTECTED] writes: > > > This all sound marvelousbut does this mean my Prescan Window suggestion > > didn't make the cut? Is there hope for this in the future? or is it just > > too much programming. > > Can you describe what you mean by a "Prescan" tab again? > Is it basically the same thing as the "Scan" tab, except without > any files being output? Can't this be accomplished by just > turning off outputting files in the Files tab and then pressing > the "Scan" button? > > Regards, > Ed Hamrick
Re: filmscanners: Need feedback on VueScan Idea
Jules wrote: >is the prescan in NikonScan just a scan? it's seems awful fast, even faster >than the fastest vuescan preview. AFAIK it's a low resolution scan just like the Vuescan preview scan. Rob Rob Geraghty [EMAIL PROTECTED] http://wordweb.com
Re: filmscanners: Need feedback on VueScan Idea
Austin Franklin wrote: > > Most scanners do hog the system quite a bit. The issue is both hardware and > software from what I can tell. The issue is the data is sent as it is > scanned, and as such, there is a real time requirement on the software to > take the data as it arrives. Polling is typically faster than interrupts in > this case, and as such, the system is bogged down in a loop checking for > data... > > A solution would be either a SCSI controller or scanner with some large > amount of memory, and you only transfer data when you have a lot to > transfer, and make it interrupt driven, instead of polled. You don't need > the entire image at once, but possibly two 4M buffers that get ping-pong'd > or something like that would certainly aid the situation. A caching > controller could be made to accommodate this, but I doubt they currently > will handle it the way one would want it to for a scanner. My old machine has dual processors. With Win98 only one processor gets used. When the scanner is scanning and if I try to open some image files by Photoshop at the same time the scanner's buzz slows down. So I tried Win2k so that the 2nd CPU gets used. It does. The scanner does not slow down any more. However, Photoshop (5.5) is noticeably slower on Win2k than Win98. My guess is that PS is a 16 bit program optimized under 16 bit OS such as Win98. But Win2k is a 32 bit OS. Quoton
Re: filmscanners: Need feedback on VueScan Idea
Jim Snyder wrote: > > > But, a properly designed program usually uses speed keys for the buttons > anyway, and location is not a concern. I have yet to meet many users that > don't recohgnize the efficiencies picked up by shortcuts, aliases, and speed > keys. Even the function keys can be programmed to handle the tabs. You're suggesting to get rid of the menus and buttons inasmuch as their design doesn't matter and just have shortcuts, aliases, and speed keys? How about a CLI? Mike K. > > Jim Snyder, Software Engineer
Re: filmscanners: Need feedback on VueScan Idea
"Quoton" <[EMAIL PROTECTED]> wrote: > down any more. However, Photoshop (5.5) is noticeably slower on Win2k than Win98. > My guess is that PS is a 16 bit program optimized under 16 bit OS such as Win98. > But Win2k is a 32 bit OS. Odd. I thought PS5.5 and later were optimised for dual processors out of the box. :-7 Maybe there's a config setting somewhere? Rob
Re: filmscanners: Need feedback on VueScan Idea
Jules wrote: >is the prescan in NikonScan just a scan? it's seems awful fast, even faster than the fastest vuescan preview. Scanwit's Mira Photo driver also uses a fast scan (at 300ppi) to show all the frames in the film-holder. This has the advantage of allerting me to "problem frames" that aren't so apparent on a light table w/o a loupe. In Vuescan, something like that could possibly be useful in batch neg scanning, where you wouldn't want over-all corrections specific to that frame's values. With problem slides, I separate them out and go straight to Vuescan! :-) --LRA --- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com
Re: filmscanners: Need feedback on VueScan Idea
Mike Kersenbrock wrote: > Jim Snyder wrote: > > > > But, a properly designed program usually uses speed keys for the buttons > > anyway, and location is not a concern. I have yet to meet many users that > > don't recohgnize the efficiencies picked up by shortcuts, aliases, and speed > > keys. Even the function keys can be programmed to handle the tabs. > > You're suggesting to get rid of the menus and buttons inasmuch as their > design doesn't matter and just have shortcuts, aliases, and speed keys? Not at all. I am suggesting that having buttons located at the bottom of the screen is not a handicap to workers who use speed keys, aliases, and shortcuts for efficiency. Since everybody uses software differently, redundancy is a good thing (except for customer support). Since someone 'mousing around' is not using the most efficient way to do things, the minor inconvenience of buttons being across the screen from tabs is probably not even noticed. Think of Ed's audience as being a pyramid. Most users are not that skilled and are the base of the pyramid. The next band of power users is a smaller group, and is topped by a tiny group of gurus who use every efficiency they can get. That broad base of users with less than stellar skills will use the tabs and buttons regardless of where they are on the screen. The middle band may use a mixture of methods, and are likely to be irritated by little things. The top layer of gurus will once again not notice, because they are using the most efficient way supplied. Jim Snyder
Re: filmscanners: Need feedback on VueScan Idea
I may have known once, but I can't remember what a CLI is. Hersch At 10:32 PM 03/07/2001 -0800, you wrote: >Jim Snyder wrote: > > > > > > But, a properly designed program usually uses speed keys for the buttons > > anyway, and location is not a concern. I have yet to meet many users that > > don't recohgnize the efficiencies picked up by shortcuts, aliases, and > speed > > keys. Even the function keys can be programmed to handle the tabs. > >You're suggesting to get rid of the menus and buttons inasmuch as their >design doesn't matter and just have shortcuts, aliases, and speed keys? > >How about a CLI? > >Mike K. > > > > > > Jim Snyder, Software Engineer
Re: filmscanners: Need feedback on VueScan Idea
>From: Hersch Nitikman <[EMAIL PROTECTED]> > >I may have known once, but I can't remember what a CLI is. CLI = Command Line Interface _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: filmscanners: Need feedback on VueScan Idea
As Henry says, CLI means "Command Line Interface". (Like DOS and native Unix, and millions of programs running under them.) To assist my filmscanning, I still use only one example regularly: Open a DOS window, and type the drive letter for your CD-ROM drive. Type "DIR /s >C:\files.txt". This puts a nice directory listing of the CD into "C:\files.txt", amazingly (under Win98) including long filenames, and it'll load beautifully into Excel or Word so that you can search it, or even add columns to tell you what the image files were. Regards, Alan T - Original Message - From: Hersch Nitikman <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 09, 2001 10:29 PM Subject: Re: filmscanners: Need feedback on VueScan Idea > I may have known once, but I can't remember what a CLI is. > Hersch
Re: filmscanners: Need feedback on VueScan Idea
On Wed, 7 Mar 2001 09:08:20 +0100 Henk de Jong ([EMAIL PROTECTED]) wrote: > > I'm sure we're all using at least 1280X1024... > > No, don't be too shure about that: I am working at 1024x768 on a 17" monitor > ;-) Huh. I'm currently working with Vuescan at 640x480 on a 10" monitor, since my NEC died explosively, shortly after the motorbike alternator, and (this week) the toilet pan self-destructed. Regards Tony Sleep http://www.halftone.co.uk - Online portfolio & exhibit; + film scanner info & comparisons
Re: filmscanners: Need feedback on VueScan Idea
on 3/14/01 4:00 PM, Tony Sleep at [EMAIL PROTECTED] wrote: > On Wed, 7 Mar 2001 09:08:20 +0100 Henk de Jong ([EMAIL PROTECTED]) wrote: > >>> I'm sure we're all using at least 1280X1024... >> >> No, don't be too shure about that: I am working at 1024x768 on a 17" monitor >> ;-) > > Huh. I'm currently working with Vuescan at 640x480 on a 10" monitor, since my > NEC died explosively, shortly after the motorbike alternator, and (this week) > the toilet pan self-destructed. > > Regards > > Tony Sleep And I'm using 832x624 on 15" NEC, still/ -Berry
RE: filmscanners: Need feedback on VueScan Idea/min res for VS
As a rule of thumb, applications should be designed to fit on a 640X480. I've never had an assignment where I was permitted to violate this convention. But this is only a rule of thumb. For image editing, this is just too small, and the rule of thumb can probably be relaxed. Is anyone running at 640x480? In any case, this whole discussion of min res is moot, since I don't think any of the changes being proposed would overflow an 800x600 screen. Frank Paris [EMAIL PROTECTED] http://albums.photopoint.com/j/AlbumList?u=62684 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Rob Geraghty > Sent: Wednesday, March 07, 2001 6:06 AM > To: [EMAIL PROTECTED] > Subject: Re: filmscanners: Need feedback on VueScan Idea > > > "Hersch Nitikman" <[EMAIL PROTECTED]> wrote: > > This time you are wrong, Frank. I'm sure there are more than a couple of > us > > with 17" monitors. With a 17", anything over 800x600 is > dysfunctional. I'm > > happy for you that you have something larger, but please don't penalize > all > > of us who don't have the cash or the desk real estate for > anything larger. > > I agree about not designing on the assumption of 1280x1024, but I have > always run my 17" monitors in 1024x768. I wouldn't call it dysfunctional. > > Having said that, I think that designing for a minimum 800x600 would be OK > since anyone using vuescan would surely be using Photoshop or PSP, both of > which are unworkable in 640x480. I know Ed has stated in the > past that most > of the > reason for Vuescan's somewhat crowded interface is to fit it into > a 640x480 > screen. > > Rob > > PS It occurs to me that Nikonscan fits into a lot less than 640x480, but > then it has its own pecularities of interface design which are frankly > unconventional and in many cases counter-intuitive. > >