[VueScan Pro 9.6.32 DC Crack Mac Osx
Tilo Chopin
I've noticed that Vuescan allows the saving of custom named ini profiles - these are assigned a shortcut in the drop down menu. Tapping the short cut key for the relevant profile (eg F1, F2 etc) before scanning the preview should reload your setup.
68 months ago(permalink)
I never use the default. I have a series of saved profiles (with appropraite names) that I switch between. Makes it so much easier to keep things how you want them and seems to work fine across versions, you just need to load the appropriate profile before you start your first scan..
67 months ago(permalink)
it is always possible to backup the .ini file or copy it to another location.
Other thing: Do you install Vuescan in the same folder which holds the ini file? It could help installng vuescan as Administrator in a separate folder. On running vuescan as regular user, the .ini file will be created in the personal appdata folder and thus preserved when updating vuescan. Sorry, can't say yet which folder exactly since I'm on Linux and not on a MicroSnoop system :-)
67 months ago(permalink)
Thanks for all the responses. Having been a VueScan user for many years (since Version 4 I think) I am aware of the facility to create custom ini files and have always made use of this.
My problem is that with recent versions these files are always over ridden after an update to the basic, presumably default, settings. This never happened before.
Yes, I do keep copies of my custom ini files elsewhere but having to copy these over each time there is an update becomes tedious and shouldn't be necessary in my opinion.
Updating almost all of my other software over the top of previous versions invariably retains my existing preferences etc as did VueScan once.
67 months ago(permalink)
Short joy btw. I did the latest update and kaboom, vuescan doesn't recognize my scanner ;-(
About Mac > system report > FireWire, I see my RATOC FireWire adapter but not Vuescan.
Hamrick said, something is broken. Well...
Anyone know how to complete reset Vuescan ? TIA
41 months ago(permalink)
My impression is that all of VueScan's state is saved in your vuescan.ini file, which is in your Pictures/VueScan folder. Remove (or rename) that and you should be good to go. You might try finding the old version (the one that worked), either from your own TimeMachine backup if you have it, or online, and seeing if it's a version thing.
41 months ago(permalink)
I think you should try again. For color negative, do this: uncheck all "lock" settings. Calibrate scanner. Preview a piece of clear leader - the whole frame need not be clear, in fact things may work more intuitively if it isn't. Click "lock exposure". Preview again, click "lock film base color". At this point (unless you select "white balance: none"), if you previewed a piece of film that is completely clear, the preview will appear pink(ish) and the scan histogram will span the whole range of values - that is normal, vuescan will by default choose the black/white points such that the histogram will span the whole range. Try selecting "white balance: none" in the Color tab to get rid of the (overcorrecting) behaviour. Irrespective of what your preview looks like, the film base color is selected correctly and locked in. At this point it doesn't matter at all whether the frame borders are selected or not - they let in less light than the emulsion, so the emulsion will be used for base color calculation.
You can now preview a frame with a normal image in it. If you want to lock white balance and brightness, click "lock image color" after you previewed the frame. You can adjust the black and white points for all three primary colors with image color locked and the changes should be applied to all subsequent scans. I write should because there appears to be a bug in the UI that does not apply the changes to previews, which is quite annoying (I contacted Ed Hamrick about it several times, to no avail).
If you want to be able to scan the borders (i.e., film carrier), I strongly recommend choosing a reference frame and doing the above "lock image color" on it. If the image color is already messed up by borders, select a small part of the image, then carefully select most of the image but leave borders out (small changes of cropping will not trigger recalculation of colors, but large changes will - that's why you need to select a small area, then enlarge to a big one). Also note that there is a setting in the "Prefs" tab (IIRC) that allows you to specify a buffer at the borders that will be ignored for color calculations - you can use this to make sure the borders are never included in the calculation.
Lastly, my preferred and recommended method of scanning negatives is to scan the leader, lock exposure and base color, then scan all frames into raw files. After I'm done with the physical scanning, turn the scanner off and restart vuescan; read in the raw scan of the clear leader to lock film base color, preview all image scans, select one with neutral grey, lock color on that, save settings, quit and restart vuescan (this because of the above mentioned bug), preview everything again (now the color lock has been applied to all previews), adjust colors and scan from raw to tiff. This way my scans have a correct base color, consistent (though perhaps not best) white balance and are extremely easy to touch up in your favorite image editor.
Steven beat me to it: upping your buffer percentage to around 15% will instruct Vuescan to ingore that percent of the edge. I believe it used to default to 15%, but it might have been revised to default to 0%. 0% is good only if you're dealing with raw files that are already cropped. Otherwise, and as long as there is a black surround on your images, you *need* to raise this percentage.
BTW, I've more or less given up on Vuescan for color negative film, and instead just scan as a slide with my scanner's OEM software, *only* ensuring nothing is clipping, and then invert and adjust through auto levels and a constrast enhancing curve in Photoshop. I might give it another try but I've found Vuescan very frustrating: color casts the norm, at least with my scanner.
From Peter's answer: "Lastly, my preferred and recommended method of scanning negatives is to scan the leader, lock exposure and base color, then scan all frames into raw files." Does locking the base color do anything during scanning into raw files? I thought such files contain the straight CCD output, unmanipulated in any way (most importantly, by any of the settings in the "Color" tab). Locking the exposure makes sense, but I'm not so sure about base color.
FWIW, I have the same issue after upgrading to Ubuntu 16.04 when everything worked fine on 15.10 with my Brother MFC-J485DW. However, the only reason I used VueScan in the first place was that I couldn't get Simple Scan or XSane to work over the network for some reason. However, I've gotten both to work with the Brother drivers on 16.04 installed via the "Driver Install Tool" downloaded from the Brother website. Just make sure you set up your scanner with a static IP address (I used the router configuration with a static DHCP lease to do this) and you should be good to go. Granted, this doesn't really answer your original question (or mine), but it provides two alternatives, hopefully.
First on the router, you must assign a fixed IP to your multifunction printer. Once this is done, you need to open the firewall ports on your PC.Open the terminal and enter the following rule:"sudo ufw allow from xxx.xxx.xxx.xxx" without the quotes.Where in place of the X you have to put the real IP of your multifunction printer.Now vuescan will work.Then to delete the rule always from terminal type:"sudo ufw delete allow xxx.xxx.xxx.xxx"
Now I'm not going to proclaim that these theories of scanning with VueScan are right or wrong. But based on the number of issues I've had while scanning; these were the resolves. I'm a huge supporter of scanning your own film: saves money, more control, and creates self-reliance.
Step 1: If you are going to use any of the Lomo scanning masks; you can't have it pushed to the top of the scanner. Vuescan will try to scan by making a bunch of stop-and-go sounds; then fail.
Solution: Push the mask to the bottom of the scanning bed, it keeps it level. There is a drawback, part of your image area will be lost. You can always just flip it around when you get to that end of the roll; or use something to space the bottom of the scanner from the mask but it should be something that is perfectly leveled.
Step 3: If you are only posting photos on Lomography or just sharing them. I would say use a lower DPI. I find 1200 dpi does it for me: plenty of quality and workable file sizes. When I first started scanning my own photos I would jack the DPI as high as it would go. Well if it's a 120mm shot you are going to end up with 50mb to 60mb image and it will take over an hour to scan each frame.
Step 5: 'Filter'. This was something that was giving me the worst headache and I had no idea that's what it had been. The issue I had with it was a drop box called Infrared cleaning. I was getting: weird distortion exaggerated grainy look, and underexposure. I drove myself mad and couldn't figure it out. Now it doesn't affect most photos; that was the crazy part.
Step 6: The 'Color' tab. Go to the color balance drop box and switch it to manual. There are a ton of sliders here; some you will use and others you will not. Focus just on: Black point, White point, Curve low and high, and Brightness. You will have to tweak these to get your desired results. I find I need just a tab of White point for all my photos; like .02 at least.
Step 8: No because I am using the photoshop plug-in; when I hit the last page my photo is taken straight from VueScan and dropped into photoshop. In Photoshop I do my last few adjustments: rotate, maybe a curve, then take it from a 16bit image to an 8bit, and save it as a jpeg.
795a8134c1