Interesting! Can you please provide a source for more information about how to open a camera file in Vuescan? Thank you.
Interesting! Can you please provide a source for more information about how to open a camera file in Vuescan? Thank you.Yes, there is. I have used it (Vuescan) just for this - scans from a DSLR. But my results with RawTherapee have generally been better.
I guess most of us were looking for ways to easily and quickly digitize large libraries. And (almost) everyone has a Digicam
Digicam scanning is cheap, fast and anyone can do it.
You are forgetting about the noise/dynamic range. Scanner users believe they're looking at grain, but in fact they're looking at a grain+noise mixture. Some even invented a term "grain aliasing" to describe the difference between their scans and prints. Camera scans are cleaner.
That's silly. DSLR users operate at another level. We scan a 36exp roll in three minutes and we do not need ICE because camera scanning does not attract dust.
It's very simple. When I start Vuescan, File -> Input -> Source -> File -> Files lets me select a a file for input (click the button with an "@"). It doesn't seem to matter whether the file comes from a camera or a scanner.Interesting! Can you please provide a source for more information about how to open a camera file in Vuescan? Thank you.
For a newbie like me, pm's are not allowed. But I was inspired by your post to look at Matlab – well, really Octave - and was surprised and delighted to find a good-looking image processing package. So far, I'm struggling with the matrices. But for starters, may I just ask a question about the orange mask of color negatives? Is getting rid of it just something like subtracting one matrix (NxMx3) from another? A linear operation?I am using my own workflow based on a self-written Matlab script.
.................................................
Feel free to pm me if you want more details.
That is exactly how Negative Lab Pro complicates my workflow in Lightroom.
I digitize film with my digital camera, and import the camera's RAW files into Lightroom. If I don't duplicate the NLP-converted file as a TIFF/JPEG, then normal Lightroom tools work backwards, so further editing with Lightroom tools is difficult or impossible. I use Lightroom's local adjustment tools a lot - adjustments which are impossible using the NLP module. So, using NLP really forces me to duplicate the RAW files as a TIFF/JPEG.
But copying the RAW file as a TIFF/JPEG means having two different versions of the same photo in my Lightroom catalog to keep track of. And if I want to use 16-bit TIFFs for maximum editability, then my storage requirements are doubled.
Hrm. Apparently I'm not arrogant enough to qualify as a DSLR user.
.... right.
So... which is flatbed, and which is dslr?
View attachment 273186 View attachment 273187
One was scanned with an Epson V800 @ 3200 PPI (14.5 MP), with ICE, manually cleaned up.
One was imaged with an EOS 90D (28 MP), manually cleaned up (it had been in the same room as the Epson, so it was dusty.).
Both have had mild color tweaks, and a bit of sharpening done in post, and then resized to 1920x1280. No, I did not spend the time to make the colors identical.
Actually once you have done the conversion using NLP, you no longer need to keep the original scanned image RAW in your catalog. For a scanned image, a "RAW" file isn't really a true RAW file unless you do DSLR scanning.That is exactly how Negative Lab Pro complicates my workflow in Lightroom.
I digitize film with my digital camera, and import the camera's RAW files into Lightroom. If I don't duplicate the NLP-converted file as a TIFF/JPEG, then normal Lightroom tools work backwards, so further editing with Lightroom tools is difficult or impossible. I use Lightroom's local adjustment tools a lot - adjustments which are impossible using the NLP module. So, using NLP really forces me to duplicate the RAW files as a TIFF/JPEG.
But copying the RAW file as a TIFF/JPEG means having two different versions of the same photo in my Lightroom catalog to keep track of. And if I want to use 16-bit TIFFs for maximum editability, then my storage requirements are doubled.
I can understand the colours not being identical, but when one is so far off into the green spectrum - after your mild tweaks - I'm not sure what the point here is.
The one on the left looks better because the colours aren't all messed up. Did you create your own profiles for the green one?
Yes it is indeed as easy as that. Not subtracting, but dividing:For a newbie like me, pm's are not allowed. But I was inspired by your post to look at Matlab – well, really Octave - and was surprised and delighted to find a good-looking image processing package. So far, I'm struggling with the matrices. But for starters, may I just ask a question about the orange mask of color negatives? Is getting rid of it just something like subtracting one matrix (NxMx3) from another? A linear operation?
My digital camera copies are RAW files. And if I delete the RAW file, then I will no longer have the option to redo the conversion with NLP, right? I think there is a very good chance that either the software, or my skill using the software will improve, so it's quite possible I may want to reconvert the file in the future. Or use it as starting point for a manual conversion. Make sense?Actually once you have done the conversion using NLP, you no longer need to keep the original scanned image RAW in your catalog. For a scanned image, a "RAW" file isn't really a true RAW file unless you do DSLR scanning.
Thank you. I was able open a RAW file from my Fuji camera in Vuescan. However, the preview did not look at all normal, and I was not able to do anything practical with it. Maybe because it is a Fuji X Trans file and not Bayer? I was hoping to see if Vuescan could be used to do the color conversion to positive, using a RAW camera copy of a color negative - but apparently, not?It's very simple. When I start Vuescan, File -> Input -> Source -> File -> Files lets me select a a file for input (click the button with an "@"). It doesn't seem to matter whether the file comes from a camera or a scanner.
Of course, I don't have a scanner at all. Maybe things are more complicated if one does have a scanner?
Agree with your point about your RAW files, but from the perspective of LR, you might want to keep the true RAW files outside of LR, and keep in the LR catalog only the files processed with NLP, since they are the starting point for all normal DEVELOP actions.My digital camera copies are RAW files. And if I delete the RAW file, then I will no longer have the option to redo the conversion with NLP, right? I think there is a very good chance that either the software, or my skill using the software will improve, so it's quite possible I may want to reconvert the file in the future. Or use it as starting point for a manual conversion. Make sense?
My copy of Vuescan tells me Fuji RAF (*.raf) files are accepted. Unfortunately, I'm not at all familiar with Fuji's formats. Are there several? Both Canon and Nikon have two entries on Vuescan's list of formats accepted, but there is only one for Fuji.Thank you. I was able open a RAW file from my Fuji camera in Vuescan. However, the preview did not look at all normal, and I was not able to do anything practical with it. Maybe because it is a Fuji X Trans file and not Bayer? I was hoping to see if Vuescan could be used to do the color conversion to positive, using a RAW camera copy of a color negative - but apparently, not?
That looks simple, indeed. But how does one determine the mr, mg, mb values?Yes it is indeed as easy as that. Not subtracting, but dividing:
let's assume R(m,n), G(m,n) and B(m,n) are your matrices representing the red, green and blue values of your pixels, each normalized so that the values of each pixel are within the 0 (dark) .. 1 (bright) range.
If the color of the mask is represented by the mr, mg, mb values you can remove the orange mask by computing
R(m,n) / mr
G(m,n) / mg
B(m,n) / mb
This may become my post #20, which should make me eligible for private messages...Too bad about pm, let me try to send you one from my side, you can take it from there if you wish to discuss more in pm.
Interesting. I will research this more.My copy of Vuescan tells me Fuji RAF (*.raf) files are accepted. Unfortunately, I'm not at all familiar with Fuji's formats. Are there several? Both Canon and Nikon have two entries on Vuescan's list of formats accepted, but there is only one for Fuji.
I had the DSLR frame set up a bit wider than the picture itself, so as to include part of the unexposed negative.That looks simple, indeed. But how does one determine the mr, mg, mb values?
One of the complaints I've always had with Lightroom (and Darktable) is that they feel you should have exactly *one* "catalog" that contains every single photo you've ever worked with or wanted to. I'd love to have separate collections such as "Masters", "archival", etc..
Not following. Several people, myself included, have "identified" several programs that do an excellent job, with full-sized examples, in this very thread. Why do you keep wishing?
You can have any number of LR Catalogs sitting on harddrive...each one with a unique name, but only ONE of them is ACTIVELY in use by LR! File Open (catalog selected by user)
Thanks for pointing this out. Gotta go back and re-read your posts in this thread.Maybe it got lost in the comments, but Negmaster and Negative Lab Pro both deserve a closer look for inverting color. I have provided both the endorsement and full-sized sample scans you can evaluate.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?