[filmscanners] Re: filmscanners: Vuescan memory error
yeah its entirely possibly that you could have some faulty memory that only shows up when you are trying to do a certain thing. I had that myself and norton picked it up. whipped the simm out and everything worked fine catchy From: Herm [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [filmscanners] Re: filmscanners: Vuescan memory error Date: Fri, 28 Dec 2001 18:39:07 -0500 do an exhaustive test of the memory, try Norton 2002 or download a test program suitable for Win2k.. a complete test will take a long time so be patient. Try this one: http://download.cnet.com/downloads/0-10102-101-4386308.html?tag=dlntl Paul Graham [EMAIL PROTECTED] wrote: yeah, I got a similar memory error on my Nikon 8000 with W2K Ed couldnt track it down and told me it must be my system... (ahem) I tried everything, but cant crack it either so I cant use vuescan just yet for big MF scans till this is solved. glad to hear any suggestions Herm Astropics http://home.att.net/~hermperez Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe' in the title or body _ Chat with friends online, try MSN Messenger: http://messenger.msn.com Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe' in the title or body
[filmscanners] Fw: Re: filmscanners: VueScan dust removal artifacts
Forwarded by list admin due to server transfer. Apologies for the delay Forwarded Message Received: from mail.cix.co.uk (UIDL=0:_lHC.uosI8.sulphur) by tsphoto (VPOP3) with POP3; Fri, 21 Dec 2001 06:00:41 - Received: from sulphur.cix.co.uk (localhost [127.0.0.1]) by sulphur.cix.co.uk (8.11.3/CIX/8.11.2_BM26) with ESMTP id fBL5ZeX08644 for [EMAIL PROTECTED]; Fri, 21 Dec 2001 05:35:40 GMT Received: from ns1.otenet.gr (ns1.otenet.gr [195.170.0.2]) by sulphur.cix.co.uk (8.11.3/CIX/8.11.3) with ESMTP id fBL5ZcC08622 for [EMAIL PROTECTED]; Fri, 21 Dec 2001 05:35:39 GMT X-Envelope-From: [EMAIL PROTECTED] Received: from koumou (rhod530-a200.otenet.gr [212.205.209.200]) by ns1.otenet.gr (8.11.6/8.11.6) with SMTP id fBL5ZTR14037 for [EMAIL PROTECTED]; Fri, 21 Dec 2001 07:35:31 +0200 (EET) Message-ID: 01c189e1$eb40bd60$c8d1cdd4@koumou From: koumou [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Fri, 21 Dec 2001 07:23:50 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary==_NextPart_000_0003_01C189F0.6FF02510 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Envelope-To: [EMAIL PROTECTED] X-UIDL: _lHC.uosI8.sulphur Subject: Re: filmscanners: VueScan dust removal artifacts This is a multi-part message in MIME format. --=_NextPart_000_0003_01C189F0.6FF02510 Content-Type: text/plain; charset=windows-1253 Content-Transfer-Encoding: quoted-printable I use Vuscan 7.3.6 and the CanonFs4000,and I also find that the IR clean = does not work very well.There seems to be some sort of misalignment of = the IR scan and the actual image scan. Koumou --=_NextPart_000_0003_01C189F0.6FF02510 Content-Type: text/html; charset=windows-1253 Content-Transfer-Encoding: quoted-printable !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META http-equiv=3DContent-Type content=3Dtext/html; = charset=3Dwindows-1253 META content=3DMSHTML 5.50.4134.600 name=3DGENERATOR STYLE/STYLE /HEAD BODY bgColor=3D#ff DIVFONT size=3D2I use Vuscan 7.3.6 and the CanonFs4000,and I also = find that=20 the IR clean does not work very well.There seems to be some sort of = misalignment=20 of the IR scan and the actual image scan./FONT/DIV DIVFONT size=3D2/FONTnbsp;/DIV DIVFONT size=3D2Koumou/FONT/DIV/BODY/HTML --=_NextPart_000_0003_01C189F0.6FF02510-- -- Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe' in the title or body
Re: filmscanners: Vuescan + Infrared
This is very interesting information. Does Canon's software work consistently in dust removal, or do they have the same problem? It does make some sense that the IR channel be refocused, since we know that IR light has a different focal point than does visible white light, and this is often indicated by the little red line or dot on camera lenses to show the offset from white light focus, for those using IR film. I have heard reports of FARE (Canon's IR dust removal system being either very good and causing no softening of the image, to not as effective as dICE. Perhaps this explains it in part, that being, some scans work well, others are less effective in registering properly. Art [EMAIL PROTECTED] wrote: In a message dated 12/18/2001 11:44:29 PM EST, [EMAIL PROTECTED] writes: Does Vuescan use the same technique with infrared passes on all scanners, Yes. and therefore any difference between say an LS30 and FS4000 in the OEM software are avoided. The problem with the FS4000 is that there are two passes to get the RGB and Infrared data, and these passes use different focus positions. VueScan has problems aligning the two passes, so the infrared dust removal sometimes doesn't work well on this scanner. Regards, Ed Hamrick .
Re: filmscanners: VueScan 7.3.5 color space bug?
I disagree ... what we end up with in Photoshop should never go thru the gamut funnel you describe above. What we end up in Photoshop should be the result of as few profile conversions as possible, and only one should be needed ... i.e.: sorry, didnt i say that? device space = scanner space . scanner data is corrected in scan program (which is done in some device independent internal space) image is represented in scan program through monitor icm (but which doesnt do anything with the image data) image is saved through whatever space you choose to. conversion (corrected output) from scanner space to working space: scanner space scan program correction saved to working space X or no conversion: scanner space vuescan scans only uncorrected output in scanner space to pshop jan
Re: filmscanners: Vuescan + Infrared
In a message dated 12/18/2001 11:44:29 PM EST, [EMAIL PROTECTED] writes: Does Vuescan use the same technique with infrared passes on all scanners, Yes. and therefore any difference between say an LS30 and FS4000 in the OEM software are avoided. The problem with the FS4000 is that there are two passes to get the RGB and Infrared data, and these passes use different focus positions. VueScan has problems aligning the two passes, so the infrared dust removal sometimes doesn't work well on this scanner. Regards, Ed Hamrick
Re: filmscanners: VueScan 7.3.6 Available
seems that i was fooled by the Adobe RGB/Apple RGB bug. Color spaces look like working ok now. Congratulations. I tested various settings: Result: if i set for monitor space the most proximate match to my image in pshop, then no matter what file space i choose, there is always a pretty good match to the result in photoshop. In my case the monitor space is most proximate to PAL/Secam space. More precise results can be obtained with some large gamut critical test images and by testing with the custom monitor profile , when that setting comes available in vuescan. For now it works pretty good. Thanks Ed. best regards jan albrecht - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 19, 2001 1:43 PM Subject: filmscanners: VueScan 7.3.6 Available I just released VueScan 7.3.6 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3.6 * Set the default monitor color space on Mac OS to Apple RGB * Enabled 14 bit scans on AGFA Arcus 1200 * Increased range of focus values on LS-40, LS-4000, LS-8000 to handle unusual slide mounts * Fixed problem when color space set to Adobe RGB or Apple RGB * Fixed problem with Prefs|Release memory option * Fixed problem scanning negatives on HP 7400C * Fixed problem with locking colors when scanning from disk Regards, Ed Hamrick
Re: filmscanners: Vuescan Strategy
On Thu, 13 Dec 2001 21:49:25 -0800 Robert E. Wright ([EMAIL PROTECTED]) wrote: Many of the recent suggestions make me question the strategy behind = Vuescan. This is certainly up to Ed Hamrick, but my long time = understanding has been that the aim was to create a scanned image file = that gave the maximum image data for adjustment in an image editor. Yup, I agree. One Silverfast is quite enough :) Regards Tony Sleep http://www.halftone.co.uk - Online portfolio exhibit; + film scanner info comparisons
RE: filmscanners: VueScan 7.3.5 color space bug?
Julian writes ... Thanks, Ed. This seems like a good interim solution, until VueScan gets real color management. But I think there may be a bug in there. I set up 7.3.5 to display images in Apple RGB, and to save files in Adobe RGB. The file images, when opened up in Photoshop, are significantly darker than VueScan's preview and scan displays. Just so we're all on the same page ... what is your display calibrated to? Are we talking about the Mac version of Vuescan? I have to ask because what you describe is exactly what I'd expect to see. That is, my display is D65 gamma=2.2 ... since Vuescan doesn't compensate for my display, if I put a preview up in D50 1.8, adjusted the color gamma just right, and than asked to deliver D65 2.2, I'd certainly expect the difference. I believe the key to the problem is Vuescan doesn't compensate for your display, and you should not preview in D50 1.8 unless your display is configured for it (granted ... it may be and I'm all wet ...g...) cheerios ... shAf :o) Avalon Peninsula, Newfoundland
RE: filmscanners: VueScan 7.3.5 color space bug?
Julian writes ... Thanks, Ed. This seems like a good interim solution, until VueScan gets real color management. ... My idea of real color management would be Vuescan's ability to accommodate a scanner's device profile ... but I understand the complexities of Vuescan accommodating LUT profiles. On the other hand ... Ed's implimentation of monitor color space is a mystery. The option implies a device space but instead makes only working spaces available, and what does device RGB imply in this context? sRGB should be my preference ... it is most like my D65 2.2 monitor ... but is not my monitor's color space! While monitor spaces are generally 2D matrix profiles, Vuescan should be able to work with them ... and Vuescan, in this context only, should allow us to choose our specific display profile. my $0.02 cheerios ... shAf :o) Avalon Peninsula, Newfoundland
Re: filmscanners: VueScan 7.3.5 color space bug?
In a message dated 12/17/2001 11:46:30 PM EST, [EMAIL PROTECTED] writes: I have some sample images which demonstrate that 7.3.5 is actually worse than 7.3.4, at least for the above combination of color spaces. http://julianv.home.mindspring.com/color_test/color_test_1.html This is just too complicated for me - there are lots of different color space conversions, screen captures, Photoshop conversions, etc. The simplest thing to do is to preview an image with Color|Monitor color space set to Adobe RGB (gamma 1.8) then preview it immediately again with Apple RGB (gamma 2.2). The gamma 1.8 preview is darker than the gamma 2.2 preview. That's how it's supposed to work. A separate issue is to determine why the Photoshop window looks different from the VueScan Scan window. This is controlled by how you have your monitor profiled, whether you've given the right monitor profile to Mac OS / Photoshop, and whether Photoshop is set up properly. It would be useful if someone could do this same test using Photoshop on Windows. The Scan window in VueScan should look very similar to the image in Photoshop. Regards, Ed Hamrick
RE: filmscanners: VueScan 7.3.5 color space bug?
Ed writes ... ... This is just too complicated for me - there are lots of different color space conversions, screen captures, Photoshop conversions, etc. It really isn't difficult. With regard to the color space you embed to the 'cropped' image, keep doing it like before. With regard to Vuescan's preview and scan presentations, you should associate Vuescan color with whatever we select as monitor space ... and leave it to us to select the color space which best matches our monitor (... but I do wish you'd allow us to select something other than sRGB ... i.e., our actual display profile). All else you'd need consider is no double conversions ... that is, what is in Vuescan's color space (monitor space) is independent of the file color space we choose to embed. I.E., [Vuescan space] == 'device RGB' = 'monitor space' [embedded space] == 'device RGB' = 'file color space' NOT [embedded space] == 'device RGB' = 'monitor space' = 'file color space' ... else, we shall all take up a contribution and buy you an installation of Photoshop ...*smile*... cheerios ... shAf :o) Avalon Peninsula, Newfoundland
Re: filmscanners: VueScan 7.3.5 color space bug?
It would be useful if someone could do this same test using Photoshop on Windows. The Scan window in VueScan should look very similar to the image in Photoshop. Regards, Ed Hamrick I did more or less, as told in a previous post.: i replace here part of my reply in your 7.3.5. anouncement thread -However i do get correct matching between pshop and vuescan when i set both monitor and file space to adobe RGB. That is nice but i dont think it is correct. The custom monitor profile should be selected in the display list which, when the same allover the system, will display all equal. -Or is your Monitor color space in reality a monitor translation of working spaces= working space preview? In order to preview one space and scan to a different space? The scheme should be scannerscanner icmvuescan interface space monitor icm monitor and vuescan interface space file icm file and then file file icm pshop interface space (lab) monitor icm monitor These icm things keeps us confused
Re: filmscanners: VueScan 7.3.5 color space bug?
In a message dated 12/18/2001 11:51:45 AM EST, [EMAIL PROTECTED] writes: However i do get correct matching between pshop and vuescan when i set both monitor and file space to adobe RGB. A more interesting question is whether you get correcting matching between VueScan and Photoshop when you use each of the different Color|File color space settings (except for Device RGB) while leaving Color|Monitor color space set to Adobe RGB. Is your monitor set for gamma 1.8? The scheme should be ... That very well may be. However, it's probably more useful to diagnose how it currently works before discussing how to change it. Regards, Ed Hamrick
Re: filmscanners: VueScan 7.3.5 color space bug?
There are no difference in my MAC between the scan window in Vuescan and later on in photoshop. Mikael Risedal -- From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: filmscanners: VueScan 7.3.5 color space bug? Date: Tue, 18 Dec 2001 09:47:32 EST In a message dated 12/17/2001 11:46:30 PM EST, [EMAIL PROTECTED] writes: I have some sample images which demonstrate that 7.3.5 is actually worse than 7.3.4, at least for the above combination of color spaces. http://julianv.home.mindspring.com/color_test/color_test_1.html This is just too complicated for me - there are lots of different color space conversions, screen captures, Photoshop conversions, etc. The simplest thing to do is to preview an image with Color|Monitor color space set to Adobe RGB (gamma 1.8) then preview it immediately again with Apple RGB (gamma 2.2). The gamma 1.8 preview is darker than the gamma 2.2 preview. That's how it's supposed to work. A separate issue is to determine why the Photoshop window looks different from the VueScan Scan window. This is controlled by how you have your monitor profiled, whether you've given the right monitor profile to Mac OS / Photoshop, and whether Photoshop is set up properly. It would be useful if someone could do this same test using Photoshop on Windows. The Scan window in VueScan should look very similar to the image in Photoshop. Regards, Ed Hamrick _ MSN Photos är det enklaste sättet att dela ut och skriva ut foton: http://photos.msn.se/Support/WorldWide.aspx
RE: filmscanners: VueScan 7.3.5 color space bug?
Ed writes ... In a message dated 12/18/2001 11:51:45 AM EST, [EMAIL PROTECTED] writes: ... The scheme should be ... That very well may be. However, it's probably more useful to diagnose how it currently works before discussing how to change it. ... On my Win2k computer, display configured for D65, 2.2, I see and get what I expect if I configure Vuescan monitor space for 'sRGB' and ask file space to be 'EktaspaceRGB' ... HOWEVER, I say that with a caveat: I cannot inspect the resulting RGB in Phoptoshop (with monitor color) and discern that my EktaspaceRGB did NOT go thru the gamut funnel I mentioned in the previous post. That being said, it looks ok on my computer ... certainly not what sirius describes. Just please tell me that EktaspaceRGB came direct from device RGB in a single conversion(?) shAf :o)
RE: filmscanners: VueScan 7.3.5 color space bug?
sirius writes ... ... The scheme should be scannerscanner icmvuescan interface space monitor icm monitor and vuescan interface space file icm file and then file file icm pshop interface space (lab) monitor icm monitor ... I disagree ... what we end up with in Photoshop should never go thru the gamut funnel you describe above. What we end up in Photoshop should be the result of as few profile conversions as possible, and only one should be needed ... i.e.: device RGB = file space RGB that is: large gamut=small gamut=large gamut is the same as small gamut!!! shAf :o)
Re: filmscanners: VueScan 7.3.5 color space bug?
In a message dated 12/18/2001 1:53:44 PM EST, [EMAIL PROTECTED] writes: Just please tell me that EktaspaceRGB came direct from device RGB in a single conversion(?) That's correct. Regards, Ed Hamrick
RE: filmscanners: Vuescan hangs on scan on ss4000/win2k
I have the same issue. Preview works, but scan runs for about 10 minutes and then aborts. It appears the unit (SS4000) is repeatedly trying to focus but does not do so satisfactorily and keeps repeating the focus process. I am running WinXP and connecting via a SCSI. Version 7.1.25 works okay, but the latest version does not. Please let me know if I can help with the debugging process. Thanks. Andy Anderson
Re: filmscanners: VueScan Histogram
Some lists generate a lot of sudden, surpise laughs. This list doesn't...till I saw this response to the How is it calculated? question. Ed..great response!!! Brad [EMAIL PROTECTED] wrote: In a message dated 12/17/2001 10:46:16 AM EST, [EMAIL PROTECTED] writes: How is the upper histogram calculated? m_hst[3][(306L*pix[0]+601L*pix[1]+117L*pix[2])18]++; Regards, Ed Hamrick
RE: filmscanners: VueScan 7.3.5 Available
I just released VueScan 7.3.5 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: :-) Ed, Any chance you could put the VS executable (sans installer) somewhere on the website? That way, I could set up a scheduled daily download, and always be sure of having the latest download! Keep up the good work (and the offer's still there if you want a slightly slicker Windows installer). Cheers Mark
RE: filmscanners: VueScan Histogram
Philip writes ... *From my observations if you just scan with the WP at 0.1 as default, you can compress the tonal values rather than making sure the image ocupies the full range available. If your image allows a WP of say 0.4 just before clipping then the available range isn't wasted in the 0-0.4 area* ... That's my impression as well. For example, any given photo depending exposure and subject, the scan may be asked to include white without detail into the histogram ... which may sacrifice levels for white with detail. I believe as you force the histogram to include the former and play with the Wp=0-.4 region, you'll notice significant effect on brightness (or apparent gamma). Once you set Wp so as to exclude most white w/o detail you'll see less effect ... and it is here where you should probably set the Wp. A good histogram presentation, which might display a small bump due to specular highlights would be beneficial, and reduce time wasted at guessing. shAf :o)
Re: filmscanners: VueScan 7.3.5 Available
comments on 7.3.5 * Added separate color spaces for Monitor and Files - yes, very nice, when i get how it works ... -my custom monitor profiles dont appear in the monitor spaces list, only official color spaces. Srgb is bad approximation of my monitor. Does the list list what is in the system32/spool/drivers/color folder? Is there a problem with displaying all icm profiles? -What would be the right setting on win 2k: my monitor is calibrated throughout the system. Shouldnt that be device RGB space= noneor my cutom monitor profile in the monitor dropdown list. - I dont have the impression that it it is working right now. When i set the display to sRGB which is nearest to monitor space, and file to AdobeRGB (my working space in Pshop too) the resulting scan is much darker in pshop than in vuescan. -However i do get correct matching between pshop and vuescan when i set both monitor and file space to adobe RGB. That is nice but i dont think it is correct. The custom monitor profile should be selected in the display list which, when the same allover the system, will display all equal. -Or is your Monitor color space in reality a monitor translation of working spaces= working space preview? In order to preview one space and scan to a different space? The scheme should be scannerscanner icmvuescan interface monitor icm monitor and vuescan interface file icm file and then file file icm pshop interface monitor icm monitor These icm things keeps us confused * Keeps histogram visible after preview or scan i still would prefer the thing in a separate draggable window (in order to see preview, color tab and result histo in one view). Fixed interface layouts will please some and others not, whatever layout you choose. In fact i would separate the preview scan tab too in a draggable window, making all combinations possible, so with a 2 monitor setup (like a lot of scanners on this list) you can put histo and settings tabs on one screen and the preview full size on the other. * Added option for histogram type to Prefs tab Wow, all tastes of histo granted!! *The gamma setting disappeared: WHY? I know that brightness is a multiplier, and the gamma was a replacement of workspace gamma. Why cant we keep both? I find the gamma setting more close to something real and recognizable, but that is just a feeling. best regards jan albrecht - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, December 17, 2001 9:47 AM Subject: filmscanners: VueScan 7.3.5 Available I just released VueScan 7.3.5 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3.5 * Added separate color spaces for Monitor and Files * Keeps histogram visible after preview or scan * Added option for histogram type to Prefs tab * Fixed problem with long-running operations failing (i.e. auto-focus on SS4000) * Disabled VueScan on PowerPC G5 Regards, Ed Hamrick
RE: filmscanners: VueScan Histogram
Ed writes ... ... I've made the histogram type an option in the Prefs tab. The options are Linear, Square root and Logarithmic. ... The upper luminosity(?) histogram shows an uncomfortable likeness to the green histogram(?) How is the upper histogram calculated? (... surely not the green weighted grayscale conversion ...) shAf :o)
Re: filmscanners: VueScan Histogram
In a message dated 12/17/2001 10:46:16 AM EST, [EMAIL PROTECTED] writes: How is the upper histogram calculated? m_hst[3][(306L*pix[0]+601L*pix[1]+117L*pix[2])18]++; Regards, Ed Hamrick
Re: filmscanners: VueScan Histogram
Now, even I can understand that!! John. [EMAIL PROTECTED] wrote: In a message dated 12/17/2001 10:46:16 AM EST, [EMAIL PROTECTED] writes: How is the upper histogram calculated? m_hst[3][(306L*pix[0]+601L*pix[1]+117L*pix[2])18]++; Regards, Ed Hamrick
RE: filmscanners: VueScan Histogram
Ed writes ... In a message dated 12/17/2001 10:46:16 AM EST, [EMAIL PROTECTED] writes: How is the upper histogram calculated? m_hst[3][(306L*pix[0]+601L*pix[1]+117L*pix[2])18]++; at 1st guess ... it is weighted green ... a normalized (30.6%RED + 60.1%GREEN + 11.7%BLUE) ... ... and I agree with weighted green being one of the best methods for evaluating the lightness of color ... however, because for white and black, when R=G=B, I have to wonder how useful weighted green is for evaluating how many white pixels how many black pixels(???) (... by no means a criticism, and I thusfar like Ed's implimentation ... but I believe how lightness is calculated is important to properly evaluating Wp Bp ...) shAf :o)
Re: filmscanners: VueScan Histogram
I would second Julian's comments - expecially the part about leaving the histograms in view for the Preview Memory function - that's the first thing I tried to do and was a little frustrated by not being able to see what happened until I had hit the tab again. Ideally leave the old histo there until the moment that it changes - then when we see the actual 'switch' take place I think we will quickly get the hang of the relationship between the numbers and the graph. mark t PS - I find it hard to believe we are all sitting here having our needs/wants met by a software developer, often in hours, let alone months or years.. Ed, I hope you never learn the 'normal' way to develop software... :-) Julian wrote: Looks good so far, Ed. I like the layout, with the combined histo on top, and the RGB histos superimposed. I'm sure there will be a raging torrent of suggestions on more gongs and whistles to add. I would like to see some way of connecting the histograms to the numbers entered in the WP, BP, and gamma settings, but I am not sure about the best way to do this. .. Here's one request that I think makes sense, and which would be easy to implement. If the user is viewing the Prev Hist tab and then executes a Preview or Prev Mem, leave the Prev Hist tab in front, rather than switching to the Preview tab. Chances are, the user wants to see the effects of the new scan on the histogram. Similarly, if Scan Hist is in front, leave it in front if the user does a Scan or Scan Mem. My own preference would be for disabling automatic flipping of the display and histo tabs altogether, and let me choose when to flip them.
Re: filmscanners: VueScan Histogram
In a message dated 12/16/2001 3:34:28 AM EST, [EMAIL PROTECTED] writes: I would second Julian's comments - expecially the part about leaving the histograms in view for the Preview Memory function It's fixed in 7.3.5, which I'll release in the next day or so. Regards, Ed Hamrick
Re: filmscanners: VueScan Histogram
In a message dated 12/16/2001 4:15:12 AM EST, [EMAIL PROTECTED] writes: Just a question, is the y-axis in the histograms linear or log? It's linear. Would people prefer it as a log scale? What scale do other programs use? Regards, Ed Hamrick
Re: filmscanners: VueScan Histogram
On 12/16/01 4:33 AM, Mark T. [EMAIL PROTECTED], wrote: PS - I find it hard to believe we are all sitting here having our needs/wants met by a software developer, often in hours, let alone months or years.. Ed, I hope you never learn the 'normal' way to develop software... :-) Yeah, I think we should clone Ed and send a few copies to Microsoft, Apple, Sun, etc. -- Julian Vrieslander mailto:[EMAIL PROTECTED]
Re: filmscanners: VueScan Histogram
i like it linear, it shows differences in comprehensible proportions. i suppose the histo in pshop is also linear. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, December 16, 2001 10:36 AM Subject: Re: filmscanners: VueScan Histogram In a message dated 12/16/2001 4:15:12 AM EST, [EMAIL PROTECTED] writes: Just a question, is the y-axis in the histograms linear or log? It's linear. Would people prefer it as a log scale? What scale do other programs use? Regards, Ed Hamrick
Re: filmscanners: VueScan Histogram
Ed wrote: I think the best way to do this is for me to just add a histogram and then evolve it using people's suggestions. It's quite possible that a simple histogram of the preview (within the crop window) and the scan will be good enough. I can worry about fancy stuff like movable sliders later. Ed, I've got 7.3.4 and have been trying out the histogram function and I am sure this is going to save me a lot of time. One thing that has struck me is that one may be able to use the 'Prev Hist' and 'Scan Hist' as before and after histograms if the preview and scan are set to the same resolution. This might be of help in guesstimating the numbers to enter as B/W points. It may also be useful in understanding how changes in settings affect the image. I know the above is very much 'by the numbers' rather than being focused (oops, no pun intended) on the image but I do agree with Maris saying 'I want a good image, not a good histogram'. My point is, Ed has given us a tool which helps our scanning and also helps in understanding the effect of adjusting all those options he tries to confuse me with ;) Thanks very much for the histograms Ed. Bob looking for 7.3.5
Re: filmscanners: VueScan Histogram
Colin Maddock [[EMAIL PROTECTED]] wrote on Sat, 15 Dec 2001 10:07:11 +1300 I don't feel the need for a histogram in VueScan either. Setting the black and white clipping levels does all that is needed at the scanning stage, along with control of gamma. How do you know where to clip the black and white points? -- David Gordon [EMAIL PROTECTED]
Re: filmscanners: VueScan Histogram
Julian Vrieslander [[EMAIL PROTECTED]] wrote on Sat, 15 Dec 2001 00:33:41 -0500 Maybe with more experience I will get better at inspecting VueScan's displays and choosing the right values for WP, BP, and gamma. But since these displays are not color managed, I also have to mentally compensate for how the image appearance is going to change when it goes into Photoshop. What I see in the VueScan window is what I get in Photoshop - am I doing something right! -- David Gordon [EMAIL PROTECTED]
Re: filmscanners: VueScan 7.3.4 Available
[EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote on Sat, 15 Dec 2001 10:49:42 -0500 I just released VueScan 7.3.4 for Windows, Mac OS 8/9/X Isn't this mention (on the download page) of something which doesn't exist Please note that the shareware version of VueScan will be disabled on PowerPC G5 processors, and updated product and pricing information for these processors will be announced at a future date. the kind of thing that caused a heap of trouble with Apple and led to your decision to stop supporting the Mac platform recently? ;) I don't want to see you go the way of www.macosrumors.com ! -- David Gordon [EMAIL PROTECTED]
Re: filmscanners: VueScan 7.3.4 Available
In a message dated 12/16/2001 8:17:47 AM EST, [EMAIL PROTECTED] writes: Please note that the shareware version of VueScan will be disabled on PowerPC G5 processors, and updated product and pricing information for these processors will be announced at a future date. the kind of thing that caused a heap of trouble with Apple and led to your decision to stop supporting the Mac platform recently? ;) The existance of the PowerPC G5 is public knowledge. Search www.google.com with PowerPC G5 for confirmation of this. I can't yet say why, but the shareware version of VueScan will be disabled on systems with this processor. Regards, Ed Hamrick
RE: filmscanners: VueScan Histogram
Ed writes ... [EMAIL PROTECTED] writes: Just a question, is the y-axis in the histograms linear or log? It's linear. Would people prefer it as a log scale? What scale do other programs use? Others are linear ... but I have to admit, a log scale would be more accurate as the data approached the Wp and Bp. (... Hmmm, maybe not accurate, but at least visible ...) If we are worried about setting the endpoints accurately and visually, maybe we ought to consider ... either a log scale, or the ability to zoom in on the y-axis(?) shAf :o)
Re: filmscanners: VueScan Histogram
In a message dated 12/16/2001 9:46:17 AM EST, [EMAIL PROTECTED] writes: What scale do other programs use? Others are linear ... but I have to admit, a log scale would be more accurate as the data approached the Wp and Bp. (... Hmmm, maybe not accurate, but at least visible ...) If we are worried about setting the endpoints accurately and visually, maybe we ought to consider ... either a log scale, or the ability to zoom in on the y-axis(?) I've made the histogram type an option in the Prefs tab. The options are Linear, Square root and Logarithmic. I'll release this in VueScan 7.3.5. Regards, Ed Hamrick
Re: filmscanners: VueScan Histogram (should be log?)
Hi! I don't know. My reasoning is that it would be useful to have a log scale, in case where there is only a small fraction of very bright pixels. I think Photoshop uses linear scale and GIMP log scale, but I don't know. I of course have the source code for GIMP and could look if I really wanted. Regards Erik söndagen den 16 december 2001 10.36 skrev du: In a message dated 12/16/2001 4:15:12 AM EST, [EMAIL PROTECTED] writes: Just a question, is the y-axis in the histograms linear or log? It's linear. Would people prefer it as a log scale? What scale do other programs use? Regards, Ed Hamrick -- Erik Kaffehr[EMAIL PROTECTED] alt. [EMAIL PROTECTED] Mariebergsvägen 53 +46 155 219338 (home) S-611 66 Nyköping +46 155 263515 (office) Sweden -- Message sent using 100% recycled electrons --
RE: filmscanners: VueScan Histogram
Ed writes ... I've made the histogram type an option in the Prefs tab. The options are Linear, Square root and Logarithmic. I'll release this in VueScan 7.3.5. What exactly are you plotting on the y-axis? ... e.g., any RGB value 0 255, or some calculated luminosity value? Raw RGB, or color corrected RGB?? (... hopefully knowing I'm clipping (or including) the real whitepoint and blackpoint(?) ...) (Personally, I appreciate asking these types of questions.) cheerios ... shAf :o) Avalon Peninsula, Newfoundland
Re: filmscanners: VueScan Histogram
You cover it all! Maris - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, December 16, 2001 8:47 AM Subject: Re: filmscanners: VueScan Histogram | In a message dated 12/16/2001 9:46:17 AM EST, [EMAIL PROTECTED] | writes: | | What scale do other programs use? | | Others are linear ... but I have to admit, a log scale would be more | accurate as the data approached the Wp and Bp. (... Hmmm, maybe not | accurate, but at least visible ...) If we are worried about setting the | endpoints accurately and visually, maybe we ought to consider ... either a | log scale, or the ability to zoom in on the y-axis(?) | | I've made the histogram type an option in the Prefs tab. The options | are Linear, Square root and Logarithmic. I'll release this in VueScan | 7.3.5. | | Regards, | Ed Hamrick |
RE: filmscanners: VueScan Histogram
I've made the histogram type an option in the Prefs tab. The options are Linear, Square root and Logarithmic. I'll release this in VueScan 7.3.5. Hi Ed, Why not make it selectable in the histogram window? Regards, Austin
Re: filmscanners: VueScan Histogram
On 12/16/01 8:03 AM, David Gordon [EMAIL PROTECTED], wrote: Julian Vrieslander [[EMAIL PROTECTED]] wrote on Sat, 15 Dec 2001 00:33:41 -0500 Maybe with more experience I will get better at inspecting VueScan's displays and choosing the right values for WP, BP, and gamma. But since these displays are not color managed, I also have to mentally compensate for how the image appearance is going to change when it goes into Photoshop. What I see in the VueScan window is what I get in Photoshop - am I doing something right! Maybe you are running on a PC and using sRGB as your color space. If so, a color managed display is less important. I run on a Mac with a gamma 1.8 monitor, and I prefer to use Adobe RGB as my color space. With VueScan set to Adobe RGB, images appear very different than how they appear in Photoshop: the VueScan version is very flat and desaturated. I've figured out a workflow that gives me a somewhat more useful display in VueScan. I set color space to Apple RGB and gamma 1.8 for my first look at the scan. I set crop, exposure, white point, black point, brightness, and filter options, using Prev Mem and Scan Mem to check results in Apple RGB. Then I change to Adobe RGB and gamma 2.2 (keeping other settings the same), and I do a Scan Mem to write the final output file. This two-space two-step takes extra time, and it still does not give a really good match with what I see in Photoshop. But it's the best I can do with the current version of VueScan. -- Julian Vrieslander mailto:[EMAIL PROTECTED]
Re: filmscanners: VueScan Histogram
Could someone explain to me in a few words how to work with a histogram when scanning? I can see it in VueScan but I don´t know what to do with it, because there are no sliders anyway... Thanks in advance, Bernhard
Re: filmscanners: VueScan Histogram
David Gordon asked: How do you know where to clip the black and white points? I always leave black clipping at 0, and white clipping at a minimal amount, perhaps 0.1, so that the VueScan scan contains all the tonal range that was on the neg/slide. Any further clipping of the end points for cosmetic reasons etc can be done as part of the operations in the image editing program, using, say, the Info facility to search the levels. Colin Maddock
Re: filmscanners: VueScan Histogram (explained)
Hi! You probably want to choose White point in such a way that the only a small percentage falls outside the histogram. Setting WP to 0.0 mean that you get everything, but that's probably not what you. Specular highlights should probably not be included in the density range. So you would use histogram to see what you get rid off . Ed essentially said that he puts this feature in Vuescan and let the users tell him how they want it, so I presume we are going to see some significant evolution in this area. Best regards, Erik söndagen den 16 december 2001 18.47 skrev du: Could someone explain to me in a few words how to work with a histogram when scanning? I can see it in VueScan but I don´t know what to do with it, because there are no sliders anyway... Thanks in advance, Bernhard -- Erik Kaffehr[EMAIL PROTECTED] alt. [EMAIL PROTECTED] Mariebergsvägen 53 +46 155 219338 (home) S-611 66 Nyköping +46 155 263515 (office) Sweden -- Message sent using 100% recycled electrons --
Re: filmscanners: VueScan Histogram
Julian Vrieslander [[EMAIL PROTECTED]] wrote on Sun, 16 Dec 2001 12:31:34 -0500 Maybe you are running on a PC and using sRGB as your color space. If so, a color managed display is less important. An outrageous suggestion, you shall be hearing from my lawyers in the morning... ;) I run on a Mac with a gamma 1.8 monitor, and I prefer to use Adobe RGB as my color space. Me to! With VueScan set to Adobe RGB, images appear very different than how they appear in Photoshop: the VueScan version is very flat and desaturated. You seem to have a roundabout way of getting the file into Photoshop! How are your ColorSync settings? I too am using Adobe RBB (1998), when I've finnished fiddling in Vuescan the final preview looks the same as the file when opened in PS. Isn't that the way it's meant to work, Ed? -- David Gordon [EMAIL PROTECTED]
Re: filmscanners: VueScan Histogram
On 12/16/01 4:19 PM, David Gordon [EMAIL PROTECTED], wrote: Julian Vrieslander [[EMAIL PROTECTED]] wrote on Sun, 16 Dec 2001 12:31:34 -0500 Maybe you are running on a PC and using sRGB as your color space. If so, a color managed display is less important. An outrageous suggestion, you shall be hearing from my lawyers in the morning... ;) No problem. The white box on the porch is for subpoenas, the red box is for injunctions, the blue box is for arrest and search warrants. I run on a Mac with a gamma 1.8 monitor, and I prefer to use Adobe RGB as my color space. Me to! With VueScan set to Adobe RGB, images appear very different than how they appear in Photoshop: the VueScan version is very flat and desaturated. You seem to have a roundabout way of getting the file into Photoshop! How are your ColorSync settings? I too am using Adobe RBB (1998), when I've finnished fiddling in Vuescan the final preview looks the same as the file when opened in PS. Do you mean the settings in the ColorSync control panel? I don't see that they have much to do with this. My monitor is profiled (formerly with Adobe Gamma, now with a Colorvision Spyder), and the correct profile is selected in ColorSync CP. Once my scans are in Photoshop 6, my workflow is color managed, including screen displays, file writes, and prints on an Epson 1280. Why do I set VueScan to use Apple RGB color space (with 1.8 gamma)? Because this provides the most accurate rendition of image brightness and saturation on a non-color-managed Mac application driving a 1.8 gamma, 6500K monitor. VueScan's default color space (sRGB) does not match my monitor setup and renders the image too dark. Using Adobe RGB in VueScan makes the image look washed out and desaturated. I switch VueScan to Adobe RGB (and 2.2 gamma) only when I have finished my adjustments in the color and filter tabs, and before writing the TIF file. When I open the TIF file in Photoshop, its calibrated displays show the image with approximately correct saturation and contrast. It's not a perfect match to the appearance i saw in VueScan, using Apple RGB, because VueScan was not using my monitor profile. Are you claiming that your scans look the same in VueScan and Photoshop with both configured for Adobe RGB? When I compare those displays, the difference is huge and unmistakable. If I adjust the image to look correct in VueScan under Adobe RGB, it looks totally wrong in Photoshop. I can only think of one possible explanation. Are you using Photoshop 5 or 5.5, with Display using monitor calibration disabled in the prefs? If so, you have monitor color management disabled, and I would expect the Photoshop and VueScan displays to look similar. -- Julian Vrieslander mailto:[EMAIL PROTECTED]
RE: filmscanners: VueScan Histogram
Adobe RGB has (ironically enough, this is after all a Mac company!) a built-in gamma of 2.2. Therefore on a Mac operating at gamma 1.8, with an application (Vuescan?) that isn't performing any translation of the image from source colour space into monitor colour space, Adobe RGB will look wrong. Not to mention that Adobe RGB also has a larger gamut than monitors can show. So, not only does the image look wrong tonally, but saturation is also incorrect. Obviously, when an image in Adobe RGB is viewed in a profile-aware application, such as Photoshop, a translation to the monitor gamut *and* gamma is performed. So in these circumstances the image will look right. Except there's a chance that some extremely saturated colours (I think yellows are problematic on monitors) will be noticeably wrong. It is simply because the monitor can't cope. Jawed -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Julian Vrieslander Sent: 16 December 2001 17:32 To: [EMAIL PROTECTED] Subject: Re: filmscanners: VueScan Histogram On 12/16/01 8:03 AM, David Gordon [EMAIL PROTECTED], wrote: Julian Vrieslander [[EMAIL PROTECTED]] wrote on Sat, 15 Dec 2001 00:33:41 -0500 Maybe with more experience I will get better at inspecting VueScan's displays and choosing the right values for WP, BP, and gamma. But since these displays are not color managed, I also have to mentally compensate for how the image appearance is going to change when it goes into Photoshop. What I see in the VueScan window is what I get in Photoshop - am I doing something right! Maybe you are running on a PC and using sRGB as your color space. If so, a color managed display is less important. I run on a Mac with a gamma 1.8 monitor, and I prefer to use Adobe RGB as my color space. With VueScan set to Adobe RGB, images appear very different than how they appear in Photoshop: the VueScan version is very flat and desaturated. I've figured out a workflow that gives me a somewhat more useful display in VueScan. I set color space to Apple RGB and gamma 1.8 for my first look at the scan. I set crop, exposure, white point, black point, brightness, and filter options, using Prev Mem and Scan Mem to check results in Apple RGB. Then I change to Adobe RGB and gamma 2.2 (keeping other settings the same), and I do a Scan Mem to write the final output file. This two-space two-step takes extra time, and it still does not give a really good match with what I see in Photoshop. But it's the best I can do with the current version of VueScan. -- Julian Vrieslander mailto:[EMAIL PROTECTED]
Re: filmscanners: VueScan Histogram
- Original Message - From: Colin Maddock [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, December 16, 2001 7:32 PM Subject: Re: filmscanners: VueScan Histogram David Gordon asked: How do you know where to clip the black and white points? I always leave black clipping at 0, and white clipping at a minimal amount, perhaps 0.1, so that the VueScan scan contains all the tonal range that was on the neg/slide. *From my observations if you just scan with the WP at 0.1 as default, you can compress the tonal values rather than making sure the image ocupies the full range available. If your image allows a WP of say 0.4 just before clipping then the available range isn't wasted in the 0-0.4 area* Any further clipping of the end points for cosmetic reasons etc can be done as part of the operations in the image editing program, using, say, the Info facility to search the levels. *Making sure the actual points at just before clipping are fully filling the histogram maximises the image quality output to file etc. I also found before the histograms were implimented that the best visual tonal range on screen ie unclipped whites but not vailed or flat as is often the case with WP 0.3 actually do fill the histogram perfectly. The image editor then can do the 'cosmetics' if required on an image mapped to make use of the full available dynamic range.* Philip Elkin
Re: filmscanners: VueScan Histogram
Michael wrote: Up until the latest versions I always put a hard number (%) in the Wp Bp ... e.g., '0.1' or 0.01%... and because changing this number by minute amount changed the image more than you'd think, I had Vs write a small JPG direct to Photoshop (note ... such a small change in Wp% would never be gleened from visually inspecting a preview histogram). When satisfied, I had Vs write a TIF. Regarding newer versions, I understand Ed has changed what '0' means in the Bp field ... and I have to again evaluate what this means to the histogram. I'm glad to see that we are using a similar process; I haven't read of any other VS user describe their scanning workflow including the use of a histogram. (I get VS to send the full TIF image to VuePrint and look at the histogram there. The trouble with this is the time taken to save the file, change B/W points and rescan until the image fills the range you want makes it impractical for regular use.) Your idea of using a JPG is a good one. That will save time but it still won't be as efficient as a histogram in VS. Agreed that very small changes in B/W points make very big changes in the image. I don't find VS a very intuitive application to use but have spent some time getting to know it. It was this that led me to think that using a histogram was a good way of determining B/W points in VS and so help to get the most from a scan. I certainly don't want or expect VS to be used for image editing. VueScan gives me good results but I just don't have the time to scan the images I want to scan. Bob
Re: filmscanners: VueScan 7.3.2 Available
Hi Ed, I have had several odd problems with VueScan 7.3.2: i can do that, do you want 7.3.2 and 7.3.3 log files ? Also to me the problem began on pressing scan, shouldnt i record scan in the log instead or in addition of point 6) of the procedure you described below? I have the same ss4000 scanner and OS(Win 2k) as patrick, but in my case the rpog hung on pressing scan. and... Uuhps, i think i opened a box full of desires and opinions with this histogram thingsorry about that, Ed, ;-) best regards jan albrecht - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 14, 2001 9:22 AM Subject: Re: filmscanners: VueScan 7.3.2 Available In a message dated 12/13/2001 7:22:54 PM EST, [EMAIL PROTECTED] writes: I have had several odd problems with VueScan 7.3.2: 1) Previews don't always work It would be useful if someone could send me a log file from 7.3.2 capturing the commands when this happens. 1) Delete vuescan.ini 2) Run VueScan 3) Turn on Files|Output log file 4) Exit VueScan 5) Run VueScan 6) Press the Preview button 7) Exit VueScan 8) E-mail vuescan.log to me Thanks, Ed Hamrick
Re: filmscanners: VueScan 7.3.2 Available
In a message dated 12/15/2001 10:14:53 AM EST, [EMAIL PROTECTED] writes: Uuhps, i think i opened a box full of desires and opinions with this histogram thingsorry about that, Ed, ;-) No problem - I appreciate the feedback. I'll be releasing VueScan 7.3.4 with histograms in the next half hour or so. Regards, Ed Hamrick
Re: filmscanners: VueScan Histogram was VueScan 7.3.2
I'm all for having a histogram but I would be just as happy to see the clipped pixels shown with a warning color. I depend more on this feature in Insight than I do the actual histogram. (partly because Insight doesn't allow gamma changes when saving in AdobeRGB) At least with the clipped pixels highlighted I can set WP BP well enough to get a reasonable histogram and finish in Photoshop. James Hill Freelance Photographer Mebane, NC [EMAIL PROTECTED] - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 15, 2001 7:54 AM Subject: Re: filmscanners: VueScan Histogram was VueScan 7.3.2 In a message dated 12/14/2001 12:46:00 PM EST, [EMAIL PROTECTED] writes: Last I heard indicated Ed didn't wants to add a histogram to VS so we may not get a chance to ask him to change it again and again... I think the best way to do this is for me to just add a histogram and then evolve it using people's suggestions. It's quite possible that a simple histogram of the preview (within the crop window) and the scan will be good enough. I can worry about fancy stuff like movable sliders later. Regards, Ed Hamrick
Re: filmscanners: VueScan 7.3.4 Available
Thanks Ed This helps (especially with showing people how to scan). I really like the seperate plots for the combined RGB value and the seperate plots for RGB in the colors. At a quick glance you can see the different color channels. This is something that I have always wanted in photoshop. I have to keep using the drop down to see the different channels and remember what the other channels looked like.
Re: filmscanners: VueScan 7.3.4 Available
This guy is awesome. Thank you ED. I send him a mail yesterday about the fs4000 problem and he released a fix for it today. A lot of those big companies should learn from ED what is costumer support. I just released VueScan 7.3.4 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3.4 * Added histogram for preview and scan * Fixed problem with SCSI on some Windows systems * Fixed problem with some Canon scanners being identified as FS2720 Regards, Ed Hamrick -- Nuno Sebastião Sent through GMX FreeMail - http://www.gmx.net
Re: filmscanners: VueScan Histogram was VueScan 7.3.2
I agree with Hill James: using the histogram is functional when you have feedback on what is going to be clipped. This could be achieved by 1. indicator color on the going to be clipped part of the image (seems complex to me to realize) or by 2. a measurement tool indicating rgb levels in 16 bit and in 8 bit numbers on mouse position. This can be used for the numeric input of clipping point of B and W. (should be easier to implement) A histogram is a big aid, but should be paired with some visual feed back on what pixels in teh image are BP and WP. jan albrecht - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 15, 2001 1:54 PM Subject: Re: filmscanners: VueScan Histogram was VueScan 7.3.2 In a message dated 12/14/2001 12:46:00 PM EST, [EMAIL PROTECTED] writes: Last I heard indicated Ed didn't wants to add a histogram to VS so we may not get a chance to ask him to change it again and again... I think the best way to do this is for me to just add a histogram and then evolve it using people's suggestions. It's quite possible that a simple histogram of the preview (within the crop window) and the scan will be good enough. I can worry about fancy stuff like movable sliders later. Regards, Ed Hamrick
Re: filmscanners: VueScan 7.3.4 Available
you are absolutely stunning, i will try that inmediately. thanks jan albrecht - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 15, 2001 4:49 PM Subject: filmscanners: VueScan 7.3.4 Available I just released VueScan 7.3.4 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3.4 * Added histogram for preview and scan * Fixed problem with SCSI on some Windows systems * Fixed problem with some Canon scanners being identified as FS2720 Regards, Ed Hamrick
Re: filmscanners: VueScan Histogram
I don't think it is necessary to adjust the white/black pts. by moving arrows on the histogram. It would be nice to see the output of the preview as a histogram plot and then continue adjusting using the standard color tab items. I agree, moving arrows are not necessary, but a Vs histogram would really be time saving for those who use to preview, then scan, then look at the histogram inside Ps, then readjust color tabs items and rescan in Vs... Would a Vs preview histogram difficult to build? Best regards. Didier
Re: filmscanners: VueScan Histogram
Looks good so far, Ed. I like the layout, with the combined histo on top, and the RGB histos superimposed. I'm sure there will be a raging torrent of suggestions on more gongs and whistles to add. I would like to see some way of connecting the histograms to the numbers entered in the WP, BP, and gamma settings, but I am not sure about the best way to do this. I like the way it is done in Nikon Scan, with sliders, numeric fields, and a button to toggle between before/after histos. But that's a bit complex. BTW, in my neck of the woods slider is the term we use to decribe greasy hamburgers. Here's one request that I think makes sense, and which would be easy to implement. If the user is viewing the Prev Hist tab and then executes a Preview or Prev Mem, leave the Prev Hist tab in front, rather than switching to the Preview tab. Chances are, the user wants to see the effects of the new scan on the histogram. Similarly, if Scan Hist is in front, leave it in front if the user does a Scan or Scan Mem. My own preference would be for disabling automatic flipping of the display and histo tabs altogether, and let me choose when to flip them. -- Julian Vrieslander mailto:[EMAIL PROTECTED]
Re: filmscanners: VueScan Histogram
Larry wrote: I don't think it is necessary to adjust the white/black pts. by moving arrows on the histogram. It would be nice to see the output of the preview as a histogram plot and then continue adjusting using the standard color tab items. Yes, I agree. Bob
Re: filmscanners: VueScan Histogram was VueScan 7.3.2
michael shafferwrote: I wonder if a problem might be, that such a histogram ... to be more accurate than setting the endpoints at exactly (e.g.,) 0.03% ... would first necessitate an actual scan. That is, a histogram based on a preview will not be as accurate as placing a decimal, as in the example I used. I guess if the preview is done at a different resolution to the scan then their histograms are likely to differ. However, it doesn't take long to rescan from memory if the file isn't saved until the user is satified with the B/W point settings. Of course, this would mean (the option) of separating the scan from the file save function. And, how can you know where to set the B/W points if you don't use a histogram ;) Bob
RE: filmscanners: Vuescan Strategy
This is certainly up to Ed Hamrick, but my long time understanding has been that the aim was to create a scanned image file that gave the maximum image data for adjustment in an image editor. I totally agree with this. I like Vuescan mainly because it seems to give me much better results with minimum intervention - hugely helpful when batchscanning (as I'm doing now). If I want to adjust levels I can do so within Photoshop or whatever later on when I actually use the image. However, as with all these UI decisions, making it an option would please all of the people, all of the time. ;-) Mark
Re: filmscanners: VueScan 7.3.2 Available
Hi Ed, thanks for the reply, I have a client in the snack business(sells pretzels/chips/etc) who had a very old styro pretzel...and wants a few more (new ones) for display purposes. I will shoot a pic of it today and email you a copy along with dimensions for an estimate on production. Andy --
RE: filmscanners: VueScan Histogram was VueScan 7.3.2
Bob writes ... ... And, how can you know where to set the B/W points if you don't use a histogram ;) I have 2 problems with that question: (1) I suppose I don't know exactly what you are trying to do(?) ... (2) a histogram is a visual tool, but it would be extremely difficult to present a truely useful histogram. A case on point is Photoshop's histogram ... for accurately using it, do you pay attention to the visual or do you pay attention to the numbers? (1) It has always been the philosohy for Vuescan ... if there is a better tool in the subsequent RGB editing software, leave Vs to the basics. I believe Vs's present Wp and Bp tools can put ^all^ the RGB into the scan, and make it stretch from one endpoint of the histogram to the other, as well as exclude a certain percentage (which might be considered noise, or specular highlights without detail). Once this is accomplished, Photoshop will do a better job of adjusting your endpoints for subsequent editing artifacts or accommodating the characteristics of your printer. (2) What would you have the histogram show? The preview's pixels or absolutely ^all^ of the pixels? Numeric feedback for 8bit RGB or 16bit? ... each individual RGB channel or some calculated luminosity value? Which luminosity value? ... 'L' of Lab? ... 'B' of HSB? Or, would we ultimately ask Ed for ^all^ options? I don't have a problem with Ed adding a histogram, but I cannot imagine it otherwise being only a visual presentation, and not practically that useful. But let's all decide first on which histogram we want before we ask Ed to change it again ... and again. my $0.02 ... shAf :o)
RE: filmscanners: VueScan 7.3.3 Available
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] I just released VueScan 7.3.3 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: Hi Ed!! I'm on the list since 20 days and in the meantime you've released 7 new release of Vuescan! I spend more money for downloads then for the Vuescan Registration ;))) I'm joking, thank's for all!! Davide Canepa
Re: filmscanners: VueScan Histogram was VueScan 7.3.2
michael wrote: Bob writes ... And, how can you know where to set the B/W points if you don't use a histogram ;) I have 2 problems with that question: (1) I suppose I don't know exactly what you are trying to do? Trying to find out how VS users get the most out of a scan when using VS. (Which begs the question of what 'most' means. You say VS can put *all* the RGB into a scan and make it stretch from one end of the histogram to the other, as well as exclude a certain percentage (which might be considered noise, or specular highlights without detail). I would agree that generally this would be a suitable definition for getting the most out of a scan.) (2) a histogram is a visual tool, but it would be extremely difficult to present a truely useful histogram. A case on point is Photoshop's histogram ... for accurately using it, do you pay attention to the visual or do you pay attention to the numbers? Both. (1) It has always been the philosohy for Vuescan ... if there is a better tool in the subsequent RGB editing software, leave Vs to the basics. I've heard that said and don't disagree with it. (2) What would you have the histogram show? The preview's pixels or absolutely ^all^ of the pixels? Numeric feedback for 8bit RGB or 16bit? ... each individual RGB channel or some calculated luminosity value? Which luminosity value? ... 'L' of Lab? ... 'B' of HSB? A histogram of the scan at the bit level the scanner can produce. Preferably luminosity, if not RGB would do if they were displayed together. I don't have a problem with Ed adding a histogram, but I cannot imagine it otherwise being only a visual presentation, and not practically that useful. But let's all decide first on which histogram we want before we ask Ed to change it again ... and again. VuePrint has a histogram with some numbers but not the numeric detail of Photoshop's histogram. Why would a histogram in VS be 'not practically that useful'? Last I heard indicated Ed didn't wants to add a histogram to VS so we may not get a chance to ask him to change it again and again... Hope this helps you understand what I am trying to do. Do you change B/W points in VS? If so why and how do you decide what they should be? Bob still very confused about scanning
RE: filmscanners: VueScan Histogram was VueScan 7.3.2
Bob writes ... ... Hope this helps you understand what I am trying to do. Do you change B/W points in VS? If so why and how do you decide what they should be? Up until the latest versions I always put a hard number (%) in the Wp Bp ... e.g., '0.1' or 0.01%... and because changing this number by minute amount changed the image more than you'd think, I had Vs write a small JPG direct to Photoshop (note ... such a small change in Wp% would never be gleened from visually inspecting a preview histogram). When satisfied, I had Vs write a TIF. Regarding newer versions, I understand Ed has changed what '0' means in the Bp field ... and I have to again evaluate what this means to the histogram. shAf :o)
Re: filmscanners: VueScan Histogram
I don't feel the need for a histogram in VueScan either. Setting the black and white clipping levels does all that is needed at the scanning stage, along with control of gamma. A separate point. I liked having the picture, preview or scan, occupy the whole screen. It gave a more satisfying first encounter with the scan than the new setup. Colin Maddock
Re: filmscanners: VueScan Histogram
Poor Ed. He can't win. Anything he does, no matter how many wanted it, some others will express disappointment. Personally, I like a histogram, and feel it helps me understand an image, and helps me improve it. And, on the current 7.3 versions, if I let VS have the whole screen, I get a very nice big image in the preview. My only complaint is that I have found the Clean function less effective than it used to be with my PC-based LS-30. I have no idea why. Hersch At 10:07 AM 12/15/2001 +1300, you wrote: I don't feel the need for a histogram in VueScan either. Setting the black and white clipping levels does all that is needed at the scanning stage, along with control of gamma. A separate point. I liked having the picture, preview or scan, occupy the whole screen. It gave a more satisfying first encounter with the scan than the new setup. Colin Maddock
RE: filmscanners: VueScan Histogram
It reminds me of the Insight wars Polaroid was beaten up mercilessly for not having histograms and not just any histogram, it had to have the little sliders on the bottom like Photoshop. When I asked for new features Histograms was ALWAYS on the top of the list. Shit, Ed's getting off easy!! :) David -Original Message- From: Hersch Nitikman [mailto:[EMAIL PROTECTED]] Sent: Friday, December 14, 2001 10:12 PM To: [EMAIL PROTECTED] Subject:Re: filmscanners: VueScan Histogram Poor Ed. He can't win. Anything he does, no matter how many wanted it, some others will express disappointment. Personally, I like a histogram, and feel it helps me understand an image, and helps me improve it. And, on the current 7.3 versions, if I let VS have the whole screen, I get a very nice big image in the preview. My only complaint is that I have found the Clean function less effective than it used to be with my PC-based LS-30. I have no idea why. Hersch At 10:07 AM 12/15/2001 +1300, you wrote: I don't feel the need for a histogram in VueScan either. Setting the black and white clipping levels does all that is needed at the scanning stage, along with control of gamma. A separate point. I liked having the picture, preview or scan, occupy the whole screen. It gave a more satisfying first encounter with the scan than the new setup. Colin Maddock
Re: filmscanners: VueScan 7.3.2 Available
Hi Ed, An on-screen Histogram with the Preview sounds like an excellent idea. Regards, John. sirius wrote: salut Ed, one question: What's new in version 7.3.2 * Added support for RGB exposure on some Epson scanners also on the epson expression 1600 pro? And I am very HAPPY with the again separated preview and scan window (suggestion: can they be made detachable so you can drag them to another monitor? Also i am still wishing some better control of white and BP: a histogram? Please! Please?) thanks a lot jan albrecht
RE: filmscanners: VueScan 7.3.2 Available
I enthusiastically second this request. This is a primary feature I miss in Vuescan that other scanning programs provide. Would defintely make setting BP and WP easier/faster for me. Cheers, Dave E. [mailto:[EMAIL PROTECTED]]On Behalf Of John Rylatt Hi Ed, An on-screen Histogram with the Preview sounds like an excellent idea. Regards, John.
RE: filmscanners: VueScan 7.3.2 Available
Dave E. writes ... I enthusiastically second this request. This is a primary feature I miss in Vuescan that other scanning programs provide. Would defintely make setting BP and WP easier/faster for me. I wonder if a problem might be, that such a histogram ... to be more accurate than setting the endpoints at exactly (e.g.,) 0.03% ... would first necessitate an actual scan. That is, a histogram based on a preview will not be as accurate as placing a decimal, as in the example I used. shAf :o)
Re: filmscanners: VueScan 7.3.2 Available
An on-screen Histogram with the Preview sounds like an excellent idea. Regards, John. Great, I vote! Didier
Re: filmscanners: VueScan 7.3.2 Available
salut A histogram should have enough resolution to make precise settings possiblei would prefer to set the points numerically, but with visual feedback, a densitometer-like tool would be the important companion. It should be available like an option. Best for me would be a double histogram: one representing the raw scan data and a second representing the result when applying gamma, wp and bp. I suppose it is a lot of work to create these tools for Ed Hamrick, but it seems there is a lot of public for these features. I must say that in most cases it works now alright for me, but in some critical images i would really like better/precize control over BP, WP and gamma curve. my main issue is that it works now with percentages instead of exact numbers regards jan albrecht - Original Message - From: sirius [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 13, 2001 5:28 AM Subject: Re: filmscanners: VueScan 7.3.2 Available salut Ed, one question: What's new in version 7.3.2 * Added support for RGB exposure on some Epson scanners also on the epson expression 1600 pro? And I am very HAPPY with the again separated preview and scan window (suggestion: can they be made detachable so you can drag them to another monitor? Also i am still wishing some better control of white and BP: a histogram? Please! Please?) thanks a lot jan albrecht
RE: filmscanners: VueScan 7.3.2 Available
It is worth bearing in mind that percentages give you more fine-grained control than numbers typed into a Levels box. A Level number is an 8-bit thing (from 0 to 255) - well, by convention it is, anyway. BUT, if you turn off the Auto black/white point option, you get to change the black/white point for R, G and B seperately. With numbers that are more fine-grained than the 0-255 scale. I have to say that if one is interested in doing significant changes to R-G-B-combined Levels (e.g. 20 points plus in Photoshop speak - not percent) or gamma changes in excess of about 1.2/0.8-ish then one should think about doing these in LAB mode to avoid causing significant saturation changes. Which means that Vuescan may not be the place to do these kinds of manipulations. Maybe Ed has programmed Vuescan to avoid saturation-type changes when using black-point and white-point percentages. Jawed -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of sirius Sent: 14 December 2001 00:40 To: [EMAIL PROTECTED] Subject: Re: filmscanners: VueScan 7.3.2 Available salut A histogram should have enough resolution to make precise settings possiblei would prefer to set the points numerically, but with visual feedback, a densitometer-like tool would be the important companion. It should be available like an option. Best for me would be a double histogram: one representing the raw scan data and a second representing the result when applying gamma, wp and bp. I suppose it is a lot of work to create these tools for Ed Hamrick, but it seems there is a lot of public for these features. I must say that in most cases it works now alright for me, but in some critical images i would really like better/precize control over BP, WP and gamma curve. my main issue is that it works now with percentages instead of exact numbers regards jan albrecht - Original Message - From: sirius [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 13, 2001 5:28 AM Subject: Re: filmscanners: VueScan 7.3.2 Available salut Ed, one question: What's new in version 7.3.2 * Added support for RGB exposure on some Epson scanners also on the epson expression 1600 pro? And I am very HAPPY with the again separated preview and scan window (suggestion: can they be made detachable so you can drag them to another monitor? Also i am still wishing some better control of white and BP: a histogram? Please! Please?) thanks a lot jan albrecht
Re: filmscanners: VueScan 7.3.2 Available
Hi, yes., i observed some strange behaviour too, with my ss4000 and vuescan 7.3.2, win 2k sp2 there were suddenly problems with the scsi communication and on making the definitive scan the program stopped responding, like the scanner. i had to turn off the scanner to be able to close vuescan. I reverted too back to 7.3.1 and probs were over. jan albrecht - Original Message - From: Patrick M. Florer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 14, 2001 1:21 AM Subject: RE: filmscanners: VueScan 7.3.2 Available Greetings ! I have had several odd problems with VueScan 7.3.2: 1) Previews don't always work 2) Scans don't always save to disk 3) Scans sometimes don't work at all - the unit seems to go through the motions, but nothing else happens. I have a SS4000 unit, Win2k sp2. Dropping back to version 7.3.1 seems to have solved all the problems. Has anyone else had problems with V7.3.2? Regards, Patrick Florer
Re: filmscanners: VueScan 7.3.2 Available
It is worth bearing in mind that percentages give you more fine-grained control than numbers typed into a Levels box. A Level number is an 8-bit thing (from 0 to 255) - well, by convention it is, anyway. well, it shouldnt be like that: if your scan is in 16 bit, then we should have 16 bit precision. that is also why i would like two histograms: raw data, and result which can be 8 bit or 16 bit. Why shouldnt we work in terms of real 16 bit or real 8 bit numbers in vuescan, instead of some translation in percentages, or other type of conversion? Percentages with lots of digits behind the point give a false suggestion of precision if the original data is not so precize.Also percentages express the wp as a fixed part of the image, instead of giving it a fixed value in the shadescale, which should give more repeatable results.(yes i know i can lock down these settings) doing these in LAB mode to avoid causing significant saturation changes. Which means that Vuescan may not be the place to do these kinds of manipulations. lab doesnt seem to be very /hue consistent . On epson-inkjet i think there was a discussion on this issue that lab manipulations suffer from hue shifts. jan albrecht
Re: filmscanners: Vuescan - film types
I would go the Advanced Workflow Suggestions route and lock in the film color, using White Balance. Maris - Original Message - From: P Elkin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 12, 2001 1:44 AM Subject: filmscanners: Vuescan - film types | I rely on the film profiles in Vuescan to get me somewhere near accurate | colours when scanning colour neg, especially as I am partially colour blind. | However I have had some trouble recently using Fuji Superia 400, S-400. I am | finding the Super G 400 G2 profile is quite cold and I am having to use the | Neutral setting instead of White Balance but it is often too warm! I have | tried to scan the film base but with no success - it just ends up being a | grain filled blue/yellow mess - I was hoping to do my own profile and lock | the colour. | | Any guidance or advice would be much appreciated. | | Philip Elkin | |
Re: filmscanners: VueScan 7.3.2 Available
salut Ed, one question: What's new in version 7.3.2 * Added support for RGB exposure on some Epson scanners also on the epson expression 1600 pro? And I am very HAPPY with the again separated preview and scan window (suggestion: can they be made detachable so you can drag them to another monitor? Also i am still wishing some better control of white and BP: a histogram? Please! Please?) thanks a lot jan albrecht
RE: filmscanners: VueScan 7.3.1 Available
I just released VueScan 7.3.1 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: Thanks Ed, you're an absolute star. :-)))
Re: filmscanners: Vuescan not detecting Minolta Scan Multi Pro
In a message dated 12/11/2001 8:08:21 AM EST, [EMAIL PROTECTED] writes: I a using Windows 2000 and followed the release notes instructions to copy dsscan.inf into c:\windows\inf however this directory doesn't exist on my PC It may be called c:\winnt\inf or c:\win2k\inf - whatever your windows directory is called. I use Windows 2000, and it's called c:\winnt\inf on my system. The name of the directory can be specified when you install Windows. Alternatively, use SCSI to access the scanner and install ASPI. In this case, you don't need to install dsscan.inf. Regards, Ed Hamrick
Re: filmscanners: Vuescan not detecting Minolta Scan Multi Pro
Ed I copied the file to c:\winnt\inf, but still no dice. --- [EMAIL PROTECTED] wrote: It may be called c:\winnt\inf or c:\win2k\inf - whatever your windows directory is called. I use Windows 2000, and it's called c:\winnt\inf on my system. The name of the directory can be specified when you install Windows. Alternatively, use SCSI to access the scanner and install ASPI. In this case, you don't need to install dsscan.inf. Regards, Ed Hamrick __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
Re: filmscanners: Vuescan and Portra 400BW
DRP [EMAIL PROTECTED] wrote: To Ed: please think about updating the Kodak negatives list in Vs! AFAIK Ed is limited by the released PhotoCD profiles from Kodak. If Kodak haven't published the profile for Portra, then Ed wouldn't be able to provide one. Rob
Re: filmscanners: Vuescan file overwrite warning
In a message dated 12/10/2001 10:52:52 AM EST, [EMAIL PROTECTED] writes: PLEASE can you add this. I've just noticed that when I re-input my settings after installing v7.3, I forgot to add the 'plus' to the file path. I've lost the last 3 strips worth of film scans (about 1h30m in scanning time) because I didn't get a simple warning to say This file is going to overwrite - are you sure?. I just finished getting this working in 7.3.1, and I'll release it in the next hour or two. Regards, Ed Hamrick
Re: filmscanners: Vuescan file overwrite warning
Thanks, Ed - I've made this mistake, too (thankfully not often) so this will help very much. Maris - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, December 10, 2001 1:10 PM Subject: Re: filmscanners: Vuescan file overwrite warning | In a message dated 12/10/2001 10:52:52 AM EST, [EMAIL PROTECTED] writes: | | PLEASE can you add this. I've just noticed that when I re-input my | settings after installing v7.3, I forgot to add the 'plus' to the file | path. I've lost the last 3 strips worth of film scans (about 1h30m in | scanning time) because I didn't get a simple warning to say This file | is going to overwrite - are you sure?. | | I just finished getting this working in 7.3.1, and I'll release it in the | next hour or two. | | Regards, | Ed Hamrick |
Re: filmscanners: Vuescan file overwrite warning
In a message dated 12/10/2001 10:52:52 AM EST, [EMAIL PROTECTED] writes: PLEASE can you add this. I've just noticed that when I re-input my settings after installing v7.3, I forgot to add the 'plus' to the file path. I've lost the last 3 strips worth of film scans (about 1h30m in scanning time) because I didn't get a simple warning to say This file is going to overwrite - are you sure?. I just finished getting this working in 7.3.1, and I'll release it in the next hour or two. Regards, Ed Hamrick Dear Ed, Thank you, Thank You, Thank You! Bill
Re: filmscanners: Vuescan and Portra 400BW
le 6/12/01 17:54, John Salty Stines à [EMAIL PROTECTED] a écrit : Hi John I posted the same question here a couple of weeks ago. The kodak profile for Portra BW is not implemented yet in Vuescan, somebody suggested me to use the generic color negative profile, but Iwas not satisfied with it. (I must say I'm a newbye in scanning BW, specially chromogenic BW). By the way Portra BW should also be optimized for scanning... Sorry I can't help you more for the moment. So, comments and adds are still welcome on this subject. To Ed: please think about updating the Kodak negatives list in Vs! Regards. Didier (Paris)
Re: filmscanners: VueScan 7.3 Available
That's looking better Ed. Getting more manageable. rob [EMAIL PROTECTED] wrote: I just released VueScan 7.3 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3 * Moved options to left panels, images to right panels * Fixed problem with slide feeder on Minolta Scan Multi Regards, Ed Hamrick
Re: filmscanners: VueScan 7.3 Available
Ed would you change the file name as well please as Gozilla didn't like it as being the same as in 7.2 and I wasn't sure that 7.3 was coming down. Rob [EMAIL PROTECTED] wrote: I just released VueScan 7.3 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3 * Moved options to left panels, images to right panels * Fixed problem with slide feeder on Minolta Scan Multi Regards, Ed Hamrick
Re: filmscanners: VueScan 7.3 Available
In a message dated 12/8/2001 9:42:15 AM EST, [EMAIL PROTECTED] writes: Ed would you change the file name as well please as Gozilla didn't like it as being the same as in 7.2 and I wasn't sure that 7.3 was coming down. I've updated my web page. Regards, Ed Hamrick
Re: filmscanners: VueScan 7.3 Available
Which focus point with normal curved slide film and LS 4000 . The focus point as default are 0.5 0.5.in Vuescan 7.3 I get god results in the middle but not so sharp out against the corner. Tried 2 other focus points 0.3 0.3 and 0.7 0.7 with 2 different results. One sharp in the corner but not so sharp in the middle. This means that I must try out the best focus point depending who much my different film curves. Why cant Nikon build a scanner who are equal sharp regardless of the smal film curvature. Nice work with the software Ed. Mikael Risedal And Ian : No pictures this time From: Op's [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: filmscanners: VueScan 7.3 Available Date: Sun, 09 Dec 2001 01:32:08 +1100 Ed would you change the file name as well please as Gozilla didn't like it as being the same as in 7.2 and I wasn't sure that 7.3 was coming down. Rob [EMAIL PROTECTED] wrote: I just released VueScan 7.3 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3 * Moved options to left panels, images to right panels * Fixed problem with slide feeder on Minolta Scan Multi Regards, Ed Hamrick _ Hämta MSN Explorer kostnadsfritt på http://explorer.msn.se
Re: filmscanners: VueScan 7.3 Available
On Sat, 8 Dec 2001 07:51:22 EST, you wrote: I just released VueScan 7.3 for Windows, Mac OS 8/9/X and Linux. It can be downloaded from: http://www.hamrick.com/vsm.html What's new in version 7.3 * Moved options to left panels, images to right panels * Fixed problem with slide feeder on Minolta Scan Multi Regards, Ed Hamrick Hey, that's nice. Good going! Ken Durling Photo.net portfolio: http://www.photo.net/shared/community-member?user_id=402251
RE: filmscanners: VueScan 7.3 Available
[mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Subject: Re: filmscanners: VueScan 7.3 Available Ed would you change the file name as well please as Gozilla didn't like it as being the same as in 7.2 and I wasn't sure that 7.3 was coming down. I've updated my web page. Ed, would you consider making the Windows version of VueScan also available as a .zip file? That makes it easier to extract to a folder and drive of one's choice. I use the NTFS filesystem on Win2K with 8.3 filenames disabled (performance tweak). So when I install new versions of VueScan there are always extra steps involved. Aside from moving the files there's also a hitch because the installer is a 16-bit application. Thanks for considering this option, Cary Enoch Reinstein aka Enoch's Vision, Inc., Peach County, Georgia http://www.enochsvision.com -- Behind all these manifestations is the one radiance, which shines through all things. The function of art is to reveal this radiance through the created object. ~Joseph Campbell
RE: filmscanners: VueScan 7.3 Available
One small bug, Ed, or maybe it is just me? When I try to *tab* from one field to the next, eg from Black to White Point, the focus jumps to the preview window instead.. Otherwise, I really like the new layout. Well done! mt
Re: filmscanners: Vuescan - Image Brightness
In a message dated 12/7/2001 11:03:55 AM EST, [EMAIL PROTECTED] writes: With the exposure being reduced on the LS30 LS2000 as default in Vuescan, when you increase the image brightness setting say to 1.3 etc, is the scanner actually increasing its exposure or is the software just pushing the curves? Color|Brightness doesn't change the CCD exposure time. It's just a multiplier of the Color|Gamma option. To change CCD exposure time, set Device|Lock exposure and change Device|RGB exposure. Regards, Ed Hamrick
Re: filmscanners: Re: filmscanners: Re: filmscanners: VueScan 7.2.11 Available (new focus test)
Definitely. I agree. Brian -- respond to [EMAIL PROTECTED] - Original Message - From: Rob Geraghty [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 06, 2001 11:05 PM Subject: filmscanners: Re: filmscanners: Re: filmscanners: VueScan 7.2.11 Available (new focus test) Brian wrote: actually polar coordinates might be more applicable in this case. It still comes back to the question of - relative to what? The orientation according to the scanner, or that displayed on the screen? Having a graphical interface with the ability to click on a point is harder to code, but very intuitive for the user. Coordinate systems are not. Rob Rob Geraghty [EMAIL PROTECTED] http://wordweb.com
Re: filmscanners: Re: filmscanners: VueScan 7.2.11 Available (new focus test)
And mathematicians. And as a maverick Aero engineer, I knew about them too. Hersch At 03:55 PM 12/06/2001 +1000, you wrote: Julian wrote: Maybe we should ask Ed to use complex numbers (x +iy) to represent the focus points I doubt that many folks on the list would have heard of imaginary numbers, but I could be wrong - there's a few electrical engineers out there I think! Rob Rob Geraghty [EMAIL PROTECTED] http://wordweb.com
Re: filmscanners: Re: filmscanners: VueScan 7.2.11 Available (new focus test)
actually polar coordinates might be more applicable in this case. Brian -- respond to [EMAIL PROTECTED] - Original Message - From: Rob Geraghty [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 06, 2001 12:55 AM Subject: filmscanners: Re: filmscanners: VueScan 7.2.11 Available (new focus test) Julian wrote: Maybe we should ask Ed to use complex numbers (x +iy) to represent the focus points I doubt that many folks on the list would have heard of imaginary numbers, but I could be wrong - there's a few electrical engineers out there I think! Rob Rob Geraghty [EMAIL PROTECTED] http://wordweb.com
