ACR calibrate tab and Vuescan DNG

Having ordered a Nikon Coolscan V ED scanner to digitize ektachrome slides, I am now busy reading and thinking about how to best to include scanned pics in my workflow. Note that one key element of my workflow is to do as much as possible in ACR per the teachings of Bruce Fraser, Jeff Schewe and others. The current ACR 4.x is more than just a raw converter.
I realize that I can make a custom profile for my scanner. However, ACR does not use scanner profiles or camera profiles. Instead, ACR provides the calibrate tab to accomplish the same purpose. Has anyone calibrated their scanner as follows and if so, do you have any tips/suggestions to share?
1. Use Vuescan professional to scan an it8 target. One source for reasonably priced targets is Wolf Faust, http://www.targets.coloraid.de/
2. Tell Vuescan to output the scan as a DNG. Yes, I know this is not a true raw image.
3. Open the DNG in ACR and go through the calibration process. If you are not familiar with this process, here is a description by the late Bruce Fraser. http://www.creativepro.com/story/feature/21351.html
Of course Bruce was describing the process for using ACR to calibrate a camera, not a scanner. Fortunately, the principles are the same. The color patches on an it8 target are supposed to conform to a standard and you receive a file stating those color values when you buy the target. The goal then is to scan your target and then use the ACR calibrate tab to tweak the colors of the scanned image so they are as close to the standard colors as possible.
4. To help with step 3, Rags Gardner has posted a CS script for it8 targets at http://www.rags-int-inc.com/PhotoTechStuff/ColorCalibration/
This script does not do the calibration for you but instead it reads the color values in your scanned target and produces a report showing the color values in your scanned target and the standard color values you are trying to get close to via the calibration process.
5. Save the result of the scanner calibration and recall it whenever using ACR to process DNGs produced by the same scanner and Vuescan.
Does this make sense?
Anyone tried it?
Can the ACR calibrate process work with a Vuescan DNG?

Joseph,
My first reaction is that I would recommend traditional profiling for scanners and skipping ACR completely. That said, I enabled TIF scanner support as a result of a request from another user. He indicated he was satisfied with the results. The ACR calibration script does calibrate. With the proper target datasheet, it can be used with negatives. The read colors script merely reports the target/image differences. The DNG step should be unnecessary.
Since this is somewhat new territory with CS3, I would be willing to work with you offline to see if we can accomplish something that fits your workflow. Contact me via my web site.
As a TIF image, I would expect ACR to honor whatever image profile was already tagged on input. Thus, ACR could be used simply for aesthetic tweaking and things like cropping. I must admit I have not tested this thoroughly. It might be treating it as untagged raw values? If so, I have a lot of questions about what ACR does with JPG images.
If ACR is ignoring the TIF profile, it could explain why Vuescan is not giving you the results you expect. Have you run a target through Vuescan profiling, saved it as TIF, then just run read colors to evaluate the results? Then do the same after opening in ACR with everything defaulted.
Cheers, Rags :-)

Similar Messages

  • ACR 3.7 is showing as ACR 2.4 in Calibrate Tab

    Hello,
    I apologize if this has been answered before but I just can't find it.
    As way of background, at one time I was using Elements 3.  Later on I installed CS and subsequently updated to CS2.  My camera is a Nikon D70s.
    Over time, I installed the updates for ACR and have been using version 3.6 pretty much since it was released.  But whenever I would click on the Calibrate tab in bridge it would always show ACR 2.4.  I never understood why that was so, but I essentially ignored it.  Today I finally decided to update ACR to 3.7 and have removed the prior version to another folder.  But when I open Bridge, the calibrate tab still shows ACR 2.4.  A few minutes ago I shot a few new pictures and downloaded them to my machine on the chance that maybe the older files had retained prior data, but even with the new pictures, the  Calibrate tab is still showing ACR 2.4.  I know that the file I'm using is ACR 3.7 becasue it has all of the characterisitics of ACR 3.7, so why is the Calibrate tab still showing ACR 2.4?
    This is now bugging the heck out of me and if anyone can help me get this resolved I would be most appreciative.
    Thank you.
    Mitch

    According to the Camera Raw ReadMe.pdf files, support for the Nikon D70s didn't come until ACR 3.2.  The D70 was supported as early as ACR 2.4 (or maybe even earlier), but not the D70s, so it seems that the Calibrate tab should at least be showing ACR 3.2, not ACR 2.4.
    [Edit] I should further add that ACR 2.4 is intended for CS whereas it is the ACR 3.x numbering that was created for CS2, so it's making even less sense to me that the Calibrate tab for my CS2 software is showing ACR 2.4.

  • Lr/ACR edits missing when opening dng to Ps

    hello,
    I´m using latest CC versions from Lightroom and Photoshop. Recently I have been having these issues with Photoshop opening file which don´t show basic edits done in Lr or ACR. Ps opens an original file.
    I have also Nik plugins, could that be an explanation for this? On the other hand, I have had those plugins over a year and this missing edits issue came out just couple of days ago. I´m using .dng files and I´m opening file from Lightroom to Ps by "edit in photoshop" command.
    I have reseted Ps and from Lr preferences "reset all warnings" has been done.
    Any thoughts?

    Lightroom 5 uses the equivalent of ACR 8.x and the Latest ACR Plugin available for PS CS5 is version 6.7.
    When you use the "edit in function" from Lightroom you should be getting a warning dialog that offers the choice of "Render using Lightroom" or "open anyway". If you wish all the edits done in Lightroom you need to choose "render using Lightroom" if you choose "open anyway" then ACR 6.x may not be able to apply all the edits done by Lightroom.
    If you do not see the missmatch warning it is because it was turned off in a previous session. From the Lightroom main menu bar go to ""Edit >Preferences >General tab > under Prompts select Reset all warning dialogs""

  • Vuescan DNG problem

    Hi all,
    I am having a problem with DNG's generated in Vuescan. I have a substantial amount of scans saved out as Vuescan DNG.
    I now know this is not very wise if you want to postprocess in ACR and LR, because vuescan DNG's are not real raws. They are rendered untagged files, this is why you don't want to process them in ACR and LR.
    Not wanting to rescan many strips of film I decided to open them in Vuescan and save them out as tagged (prophoto and gray(for B&W)) TIFFs for postprocessing in ACR/LR.
    However here comes the problem, the DNG's show up in Vuescan as only 300dpi (originally scanned at 4000dpi) and the resulting TIFF is very tiny and unusable (pixilated). These DNGs have been opened before in ACR and/or LR.
    According to Ed Hamrick, the author and maintainer of Vuescan, once opened in ACR/LR a tag is written into the DNG, c716 for ACR and c717 for LR alongside a low res preview (despite rendering a 1:1 preview). This is causing Vuescan to only see a low res preview at 300dpi (my ACR workflow setting). Ed is not able to give a solution and regards these DNG's as being manipulated. Maybe Vuescans implementation of DNG is defying the purpose of DNG being an archival file format, but that is not solving my problem right now.
    Is there a way to strip off all the tags and preview(s) written into the DNG to return the Vuescan DNG into its pristine state before opening into ACR/LR, because these untouched DNG properly show up as 4000dpi files in Vuescan.
    Any help is greatly appreciated
    Regards,
    Jaap

    Hi Sandy,
    Thank you for your answer. I ll give it a try.
    The reason you don't want to process vuescan dng's in ARC/LR is that these dng's are rendered files as opposed to real raw files which have te be demosaiced in the raw converter.
    Vuescan dng's behave much like a tiff, but they are untagged and ACR/LR assumes sRGB when the file is opened and with all under the hood conversions the result is not what you would get if you open proper tagged TIFFs.
    I remember Andrew Rodney explaining this very clearly but unfortunately i m not able to recall where i once read it.
    Jaap

  • Lightroom doesn't recognize ACR 5.5 and my D300s RAW images

    Lightroom 2.4 does not recognize my Nikon D300s RAW images. I downloaded ACR 5.5 and after install both Bridge and Photoshop CS4 handle the D300s RAW images but my Lightroom 2.4 will not import them saying that it is a damaged or unrecognized file type. I have rebooted my entire Vista system and the problem persists. Any suggestions on how I might make Lightroom recognize ACR 5.5 and my D300s RAW images? Thanks in advance.
    Harry Campbell

    Harry Campbell wrote:
    Any suggestions on how I might make Lightroom recognize ACR 5.5 and my D300s RAW images?
    You don't want Camera Raw 5.5 (unless you want to use Photoshop CS4), you want the DNG Converter 5.5 which can convert the D300 raws into DNGs that are compatible with Lightroom 2.4. The next version of Lightroom (presumable 2.5) will have the support built in without needing the DNG Conversion...

  • Cautionary note re ACR 4.4 and Lightroom 1.4

    On the Adobe blogs, Tim Hogarty writes that ACR 4.4 and Lightroom 1.4 are being taken down:
    http://blogs.adobe.com/lightroomjournal/2008/03/important_lightroom_14_and_cam.html

    Try reading the blog...
    >The Lightroom 1.4 update for Mac and Windows has been temporarily removed from the Adobe.com web site....
    >....For those not in immediate need of the updated camera support available in Camera Raw 4.4 or the DNG 4.4 Converter, it's recommended that you also continue working with the 4.3.1 versions.
    There is nothing about ACR or DNG 4.4 being removed.

  • Profiles ACR 3.3 and ACR 4.4 missing?

    I have Photoshop CS4 installed with ACR 5.3.  I ran the camera profiles installer that accompanied the ACR plugin module in the update download. (Though the download was labeled ACR and DNG, the DNG installer was missing in action.) Presently I'm awaiting a second (replacement) 5D Mark II, but meanwhile I noticed that if I open a RAW file from the 5D in ACR, I have the ACR 3.3 and ACR 4.4 profiles listed in the Camera Profiles pop-up menu along with the 'camera' profiles, as I'm used to. But when I open a Mark II RAW file, the ACR 3.3 and 4.4 profiles aren't listed. Can anyone say why they're not accessed along with the camera profiles in the latter case?

    Bishop10 wrote:
    Can anyone say why they're not accessed along with the camera profiles in the latter case?
    Sure...since the 5D MII was not supported in any earlier versions of Camera Raw, the first version to support it was ACR 5.3.
    Since ACR 5.2, the DNG Profiles are the primary profiles for any new cameras added AFTER ACR 5.2. As a result, there will _NEVER be any earlier profiles for new cameras that ship after the release of the DNG Profile update. So, the Adobe Standard is now the primary default profile and the other vender matching profiles are also supplied.
    There will never be any earlier profiles because Adobe isn't profiling cameras that way any more (which most people think is a really good thing).

  • ACR conversion of CR2 to DNG = 14-bit Not 16-bit :Why?

    If I open one of my Canon 5D Mark II CR2 raw files (several in different folders and taken at different times were tested) in ACR (7.2) and save it as a DNG file (with no ACR edits) Bridge shows the DNG as being a 14-bit file whereas if I save it as a PSD file it has a 16-bit depth. Exactly the same thing happens if I convert the CR2 file to DNG using the Adobe DNG Converter (7.2 version). You might answer that as a raw file, it does not yet have a bit depth because it has not been rendered, and the 14-bit description really has no meaning. But if that is the case then Bridge's reporting that all my original CR2 files are 16-bit is also meaningless.
    Why is there a difference in the reported, and presumeably actual, bit depths?
    Interestingly, if I then open the "Bridge reported"14-bit DNG file in Ps (CS6) and save it as a PSD, the new PSD is shown, presumeably correctly, as being 16-bit.
    Please help a poor confused soul.

    Andrew_Hart wrote:
    But that can't be the whole story.
    Well, as it relates to Bridge, is is...as Eric said, the bit depth reported to Bridge is non-standard unless the file has been processed as DNG.
    Andrew_Hart wrote:
    So if the DNG shows the correct bit depth stored in, as you say, "the standard TIFF header location", why can't the CR2, now rendered as a TIFF, do the same?
    Because...Bridge isn't reporting the correct info (which I tried to explain and you seem to refuse to accept)...
    Andrew_Hart wrote:
    This logic seems to me to be strengthened further by the fact that, as we all know, there is no viewing of a raw file without rendering. So when viewing a preview/thumbnail of a DNG in Bridge, you aren't actually viewing the DNG at all, you are viewing a preview/thumbnail of something which has been demosaiced, had a tone curve applied to it, et cetera, namely, I presume, another TIFF. If that TIFF can report its correct bit depth to Bridge, then why not the TIFF rendered from the CR2 as well?
    Because, well, the headers are not standard and Bridge kinda reads the wrong thing with many raw/rendered files (unless you convert to DNG).
    Not sure why this is so hard to understand...Bridge is a browser app that tries (but often fails) to display the "right thing". But often can't due to the file's metadata.
    This really is not a thing to dwell on...you may think there is a tempest is a teapot, but it means nothing. Again, these are not the droids you were looking for (do you even understand the reference-Google it).
    This whole thing is a red herring...you may as well give it up. Seriously, you are not getting anywhere here...raw is raw and you should generally ignore Bridge for most reports...because, well, Bridge isn't accurate because the standards for reporting bit depth are not standard...that's what is causing the differences. [Edited to keep this thread a friendlier place.]
    Message was edited by: TerriStoneCHL

  • Somtimes Firefox loads a blank page; the Tab says "New Tab" and the URL is always "about:blank". What's up with that?

    Using Dogpile, I search and a list of URLs comes up. I select and click on one and Firefox opens a new tab. It responds promptly with a blank screen. The Tab says "New Tab" and the URL says "about:blank". The last one came up slowly in IE and turned out to be nothing more than a large pdf. Can you help me figure out what is happening and how to fix it, please? It is happening far too often. Running the virus, etc. software has not stopped this problem. Thank you very much for your help! Hutchy

    Using Dogpile, I search and a list of URLs comes up. I select and click on one and Firefox opens a new tab. It responds promptly with a blank screen. The Tab says "New Tab" and the URL says "about:blank". The last one came up slowly in IE and turned out to be nothing more than a large pdf. Can you help me figure out what is happening and how to fix it, please? It is happening far too often. Running the virus, etc. software has not stopped this problem. Thank you very much for your help! Hutchy

  • I want Firefox to open to my homepage every time after it crashes. I do not want it to return to the tabs and applications that caused the crash. I am willing to lose information. How do I do this?

    Firefox crashes or seizes up when there are too many tabs and applications open, and causes my computer to crash or seize up. I use task manager to close Firefox or I restart my computer. Then, when Firefox restarts again, it automatically re-opens all the tabs and applications that caused the computer to seize or crash in first place. This is a waste of my time. I want Firefox to reopen to my homepage even if it crashes. I am willing to lose information to have Firefox reopen to a low-memory homepage. How do I do this?

    Set the Integer pref browser.sessionstore.max_resumed_crashes to 0 on the about:config page to get the about:sessionrestore page immediately with the first restart after a crash has occurred or the Task Manager was used to close Firefox.
    * http://kb.mozillazine.org/browser.sessionstore.max_resumed_crashes
    That will allow you to deselect the tab(s) that you do not want to reopen, but will allow to reopen other tabs.
    See:
    * http://kb.mozillazine.org/Session_Restore#Restoring_a_session_after_a_crash
    * http://kb.mozillazine.org/Browser.sessionstore.max_resumed_crashes
    See also:
    * https://wiki.mozilla.org/Session_Restore#Preferences
    To open the <i>about:config</i> page, type <b>about:config</b> in the location (address) bar and press the "<i>Enter</i>" key, just like you type the url of a website to open a website.<br />
    If you see a warning then you can confirm that you want to access that page.<br />
    *Use the Filter bar at to top of the about:config page to locate a preference more easily.
    *Preferences that have been modified show as bold (user set).
    *Preferences can be reset to the default via the right-click context menu if they are user set
    *Preferences can be changed via the right-click context menu: Modify (String or Integer) or Toggle (Boolean)

  • I can't restore a previous session (it instead recovers the session before) of my Tabs and my home page keeps being reset to firefox

    Hi,
    Over the last few days (since i updated to the newest version of firefox) i've been having problems. I usually keep open quite a few tabs that are invaluable to me that I need, they contain vital information i've been needing for research and I can't afford to keep losing them!. I'm used to exiting firefox when i turn off my computer and them saving for my next session when I open firefox back up. For some reason now, if i turn off my computer, when i turn on again and go into firefox to restore my previous session. it will restore the session prior to my previous session but not my previous session.
    My default setting was to resume the Firefox session from where it was when I last exited Firefox that I set. The settings are all the same as they was before I updated firefox and I had this problem, so it is set to remember my history. I'm really not that tech savvy so i really don't know if it was teh update that caused it but it seems around the same time. Also, every single time. it sets my home page to firefox (it is usually google)) it will only remain google if i change it back and remain for the day until i restart my computer.
    I'd be most grateful to any hint that might solve this problem. Thank you for your attention. I really appreciate the input! thanks everyone in advance!
    Details:
    I have windows 7 64 bit home premium
    Latest version of firefox

    You can check for problems with the sessionstore.js and sessionstore.bak files in the Firefox profile folder that store session data.
    Delete the sessionstore.js file and possible sessionstore-##.js files with a number and sessionstore.bak in the Firefox profile folder.
    *Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
    *http://kb.mozillazine.org/Profile_folder_-_Firefox
    *http://kb.mozillazine.org/Multiple_profile_files_created
    Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost and you will have to recreate them (make a note or bookmark them if possible).

  • How to stop multiple auto-switching to address bar every time I open a new tab and try to type something anywhere outside of address bar?

    How to stop multiple auto-switching to address bar every time I open a new tab and try to type something anywhere outside of address bar? Like something just wants me to use that embedded search when u type something not-web-address in address bar and hit enter. And the most ridiculous thing is that it happens repeatedly on like every second, like I just move down from address bar and start typing again, but then again it switches me to address bar, and 3, 4 times like that. And the result is also that I can't see the address of that page.
    I think its has something to do with my AVG antivirus, because this started the same time some AVG Nation started to appear in every new tab i open (and thats also irritating me, I read about it here on support.mozilla.org and it seems that the only solution is to completely reinstall Firefox, but I dont want to lose all my settings) but when i type something in address bar and hit enter it opens the search results in Google.
    Please try to help me, I like Firefox but I must switch to Chrome until I fix this problem.
    Thanks in advance

    First, please update to Firefox 32. 22 is no longer support nor is it secure. Then let us know if you still have this problem. [[Update Firefox to the latest version]]

  • Minefield just would not open pages, whatever I tries to type in the addressbar the URL just stayed there and nothing happened. Even if I opened a new tab and put a new url again it did not even start loading the page. This is happening since the last upd

    Minefield just would not open pages, whatever I tries to type in the addressbar the URL just stayed there and nothing happened. Even if I opened a new tab and put a new url again it did not even start loading the page. This is happening since the last updates from today or yesterday. I already removed minefield and installed it again
    == This happened ==
    Every time Firefox opened
    == today ==
    == User Agent ==
    Mozilla/5.0 (Windows; Windows NT 5.2; Win64; x64; rv:2.0b3pre) Gecko/20100728 Minefield/4.0b3pre ( .NET CLR 3.5.30729; .NET4.0E)

    Create a new profile as a test to check if your current profile is causing the problems
    See [[Basic Troubleshooting|#Make_a_new_profile|Basic Troubleshooting: Make a new profile]]
    There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins"
    If that new profile works then you can transfer some files from the old profile to that new profile (be careful not to copy corrupted files)
    See http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
    See also http://kb.mozillazine.org/Browser_will_not_start_up
    You can discuss issues with Namoroka 3.6 and Minefield 4.0 nightly and alpha/beta builds at the MozillaZine Firefox Builds forum.
    That forum is better suited to discuss such issues.
    You need to register on the MozillaZine forum site in order to post at that forum.
    See http://forums.mozillazine.org/viewforum.php?f=23

  • Tabs and window restore only restored one of many open windows from last session. I hate this!!

    Tab and window restoration has FAILED after version 13.01 installation! Out of 7 windows open with multiple tabs, only ONE BROWSER WINDOW OPENED with NO reference to what happened to the normal session that had been in the previous version of FF. I've read about this and I DON'T LIKE IT. It is reverse engineering. WHY would you scrap someone's research for the sake of making your browser open more quickly? DAMMIT MAN I don't have time to study a browser. I may not endure this version! I don't see a way out of this ff trap, other than go to previous version which is always a bitch. Dammit!

    You need to use "Firefox/File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit") to close Firefox if you are currently doing that by clicking the close X on the title bar to close Firefox with all open windows at once. Otherwise only the last closed window will be restored. If this did happen then check History > Recently Closed Windows to see if any are listed (default is 3).

  • When I open up Firefox I get 2 windows one with my tabs and the other is ad on manager how do I stop the second window if I try to close it both windows clos

    This problem just started when I start up Mozilla fire fox it opens 2 sessions or something the first one has my tabs form the previous session the other one is blank except for the 2nd window only has add on information, but when I try to close the second window it automatically closes the whole thing and I have to start all over again, what can I do

    You can check for problems with the sessionstore.js and sessionstore.bak files in the Firefox Profile Folder that store session data.
    Delete the sessionstore.js file and possible sessionstore-##.js files with a number and sessionstore.bak in the Firefox Profile Folder.
    *Help > Troubleshooting Information > Profile Directory: Open Containing Folder
    *http://kb.mozillazine.org/Profile_folder_-_Firefox
    Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost, so you will have to create them again (make a note or bookmark them).
    *http://kb.mozillazine.org/Multiple_profile_files_created

Maybe you are looking for