X-Rite Passport Plugin

My Xrite passport plugin has stopped working. When I attempt to create a profile I get the error message
"The profile could not be created" nothing else.
My operating system is Windows 7 64bit
My Lightroom is 4.4 with Camera Raw 7.4
Can anyone tell me how to fix this.
Jim

Is it for every photo you’ve tried, recently, including ones that used to work, or is it just for a particular photo, where maybe it can’t find the chart for some reason?   Or have you not used it for a while and now when you try it’s not working.  Have you tried re-installing the Passport Software from X-Rite?
You could try posting the ColorChecker photo, here, via www.dropbox.com or similar so others can check if it works of them or not.

Similar Messages

  • How to add ColorChecker Passport plugin to LR 5?

    I loaded this software from the X-rite's CD (it said "successfully"). In the Applications folder, I clicked on the icon - it allowed me to upgrade to the latest version (again "successfully"). When I opened LR 5 and opened Plugin Manager, it wasn't there. I pressed Add and found ColorChecker, but it was grayed out. I cannot "ungray" it.
    What to do?
    BTW, I have iMac w/version 10.8.4.
    --- Rion

    MarkJH wrote:
    "Could you explain "I am now trying to re-create the catalogue". Is the previous catalog not available?"
    No.  It is available - I have a catalogue based on all my photos on the external 2TB HDD.
    My photos were growing too much for the 2TB external HDD, so I thought I'd move them to a NAS.
    I have simply transferred the files/folders from the external HDD to the (4TB) NAS and am trying to re-build the catalogue from the NAS.
    So far, no luck.
    I believe the question was asking ... what steps are you following to try to re-build the catalog? Which you apparently haven't answered.
    If the previous catalog is available, no rebuilding is necessary.
    Thus the confusion and questions from DdeGannes.

  • LR5 and X-Rite Passport issue

    New files for camera calibration with Xrite Passport do not appear on the drop down window in Camera Calibration/Profiles.  They do appear on LR4 and on the User file folder.
    I have updated DNG, removed and re-install X-Rite program.   I am using a Mac.   Thank you in advance.

    In reply #10 on the web-forum, the respondent describes using the X-Rite DNG Profile Manager to manipulate the profiles and after which they showed up. 
    To get the DNG Profile Manager you need to register your CCPP as the following page describes, and  after registering you'll get an e-mail with a link to the software installer you can download:
    http://blog.xritephoto.com/?p=2083
    On Windows I have never had trouble with using the profiles as long as I am working with a raw or dng image, but on the Mac the path to the custom profiles changed and it is possible that an obsolete version of the creation software is putting them in the wrong (old) location on the Mac where LR cannot find them.  I've also seen users enter in the last folder in the path with a space in it, which might be a just a typo or perhaps the path is created incorrectly: "Camera Raw" vs "CameraRaw".
    Make sure you're using the newset DNGPE 1.0.4 software and the latest X-Rite CC PP 1.0.2 software (on the Support tab on X-RIte's page for the CCPP), though X-Rite's is quite old, so perhaps doesn't work with the new location correctly.  On Wnidows things work ok because the location has not changed, so I cannot give more definitive information since I don't have any experience with a Mac.
    Mac: http://www.adobe.com/support/downloads/detail.jsp?ftpID=5493
    Win: http://www.adobe.com/support/downloads/detail.jsp?ftpID=5494
    http://xritephoto.com/ph_product_overview.aspx?ID=1257&action=support

  • X-Rite Color Checker plugin fails to complete profile...

    Whereas I'm able to get the desktop version of the Color Checker profile maker to work fine, the X-Rite Lightroom plugin consistently fails to complete a profiling operation--quitting with  the message that it "is unable to locate the color checker crop marks" in my image. In one such
    "failed" image, the (in focus) color checker occupies about 75% of the frame!
    I'm using LR 3.6, Mac OS X 6.8. Latest versions of the X-Rite software. Is this a common problem (making the plugin pretty useless)?
    Phil

    Yes,  the  desktop (standalone) version of the software is able to complete a profile--although it does ask me identify the crop marks (btw, the color pattern is in-focus and more than a stop below clipping the white patch).
    I can understand that the plugin might fail to detect the crop marks when the pattern is only a small fraction of the frame, or blurred and/or poorly exposed; however the plugin is failing (for me) with a very large pattern--a majority of the frame area---sharp focus and good exposure.
    **************update!
    Hmmm. As I got ready to post this reply, I tried using the X-rite LR plugin one more time, and...it worked! Can't explain why or what I might have done differently. I had used the desktop profile maker (with another image)  a little earlier and then had restarted LR; that restart seemed to have helped(?) even though I'd restarted LR a couple of times yesterday after installing the X-rite plugin. Anyway, the problem is gone now...
    Phil

  • Colorchecker Passport not working in Lightroom 5.6

    I have been using the colorchecker passport while photographing my art for about a year now and have not had problems with it until recently.  Now Lightroom 5.6 will not show my profiles in the camera calibration area nor will it create a new profile.  When I try to create a new one it says it cannot be generated.  When I run a report I get this message:
    Plug-in error log for plug-in at: C:\Users\Joshua\AppData\Roaming\Adobe\Lightroom\Modules\XRiteColorCheckerPassport.lrplugi n
    **** Error 1
    This plug-in’s post-processing task did not finish successfully.
    XRUtility.lua:86: <AgErrorID>canceled</AgErrorID>
    I tried creating a new profile with the x-rite Camera Calibration Software and got the same report.  I don't know if the problems in with the OS, Lightroom, or x-rite.  Here is what I am using:
    Windows 8.1
    Lightroom 5.6
    ColorChecker Passport Adobe Lightroom Plug-in (3/15/2011)
    Color Checker Camera Calibration 1.0.2 (6/22/2010)
    I also tried removing all the x-rite software (both the plug-in and stand along software) and reinstall it, but that did not fix anything.
    Any ideas?

    If you can figure out how to upload your newest DNG to Dropbox I may be able to help you analyze what is wrong, otherwise, I can only guess from what you've said.  A partial substitute for uploading the DNG would be to post a screenshot of what it looks like as you did, originally so at least a judgment can be made about whether it is shot correctly or not.
    The DNG you linked from Dropbox gives me a reasonable error message, yet it seemed to give you something else.  This is what I don't understand, unless you're using the older CCPP app, rather than the slightly newer one, so first, make sure you've downloaded the 2010 version of the software and the 2011 version of the plug-in that interfaces with the software,  in case what you've installed from the disk is the original version.
    One of these links appears to be just the plug-in and one has both the software and the plug-in as separate items.  I assume the plug-in is the same for both but I'm including both links just in case one is newer.  Since the one that is just the plug-in mentions Windows 8, I assume it is the most up-to-date.
    ColorChecker Passport Adobe® Lightroom® Plug-In N/A
    X-Rite ColorChecker Passport – X-Rite Photo – X-Rite Passport
    Secondly, if you still have them try profiling the original NEFs instead of the DNGs.
    Thirdly, if you must make DNGs, it can matter what the Compatibility Level is and try an older one, since the CCPP software hasn't been updated in several years.  This doesn't seem to matter for some cameras but it does for others.

  • Using colorchecker Gretagmacbeth in LR

    Hi!
    I have done a cameraprofile and would like to continue i LR with setting the rest.
    I found a video http://www.youtube.com/watch?v=eMDgNNnW074&NR=1  where they explaned it all but in camera raw.
    But in LR the numbers for RGB are different. They only go up till 100 in LR but i need to work with 1-255.  I can do it with holding down the alt key and so on but find this seams like a more thourough way to do it.
    Many Thanks!
    Åsa

    What you said in your original post is "the color values (of the ColorChecker Passport) are never the expected LAB (or RGB) colors of the target." I was trying to explain to you why it is difficult to make accurate measurments of the color patches in LR and/or PS. The technical information at these links may explain it better:
    http://www.rmimaging.com/information/ColorChecker_Passport_Technical_Report.pdf
    http://forums.adobe.com/message/3604458
    http://www.pixiq.com/article/rgb-conversion-chart
    sandro.franchi wrote:
    Hi trashner, thanks for your answer. I'm aware of the Tone Curve (I'm using a lineal one and adjusting points to the ColorChecker expected luminance values) and exposing for the 50% gray patch.
    The Adobe Standard and Camera Standard profiles provided by Adobe in LR are very color accurate profiles, at least for the specific camera body they were created with. The primary purpose of ColorChecker camera profiling is to correct for minor image sensor batch differences that occur with ALL integrated circuits during manufacturing. The ColorChecker can also be used on-location to create site and lighting condition specific camera profiles, to correct for unique lighting and/or atmospheric conditions.
    There is no need to "measure" and "adjust" the patch values of your ColorChecker images before creating the camera profile. The X-Rite ColorChecker Passport application and/or Lightroom plugin use the "unmodifed" original RAW image file for measuring the target patches and creating the camera profile. You can use the Adobe DNG editor to create your own profiles, but be aware there are many issues involved in creating an acurate profile this way:
    http://forums.adobe.com/thread/869538
    I suggest using the X-Rite LR Plugin, let it create the new camera profile, and then establish the correct white balance using the 80% gray scale patch on the chart next to the white patch. You can also use the larger white balance card on the reverse side of the ColorChecker for this purpose, but I find the 80% gray patch works best. This is the only "measuring and adjusting" that is required to create an accurate and useable camera profile with the ColorChecker Passport.
    If I'm still missing your point please provide more details concerning the issues you are having with your pictures, not the ColorChecker images.

  • Lightroom can't 'see' Network drive

    Ok, for the past two years of using lightroom I've had my RAW files stored on an xserve RAID that's networked to my editing station.   Nothing about this set up has changed and has worked very well until Monday (that was a monday for sure)
    Monday, after installing the x-rite color checker passport plugin, I decided to reboot my machine as it was getting sluggish having just worked on several large files in Photoshop.  Lightroom wanted to do its weekly catalog backup so I let it.   Fast forward several hours later, lightroom was locked up for sure.  So I had to force quit and restart.
    Upon restart lightroom gave me ?  on most of the folders on my network drive, only one folder was showing normal.  I checked the drive and permissions everything is fine there.   I tried one of my many catalog backups with the same results.     I didn't have time to monkey around so I erased lightroom prefs and folder in app support and proceeded to re-install lightroom.    After I had the same result.  At this point I also noticed on the import screen it only saw that one folder on the drive...    At that point I made an entirely new catalog based on just this years images(24k or so compared to 43k in my other catalog) and left that going overnight.  everything imported fine and created preview images, however this brand new catalog has the same issue!
    please help! 
    Note, I've just tried lightroom on another machine and it sees the folders fine.

    interesting,  
    When I made the new catalog there was just the one folder in 'Select a source'  for that network drive(there are 12 folders on the first level of that drive) when I made the new catalog, the only way I could add images was by dragging and dropping them on the lightroom icon in the dock.   As well only that one folder was available in the 'destination'.  
    Today now all the folders I imported yesterday via drag and drop are available in the source and destination areas.   Such odd behavior, since the 'new' catalog is still having the issue I made a new test one and imported just a small number of images and it seems to be working, both through the import dialog selecting the source and drag and dropping.
    Going to restart my computer just to be sure it continues to function properly.   If so, I guess it is half fixed enough to be usable. I would prefer to know the underlying cause and a better fix for this since I no longer have use of my old catalogs even though I've diligently backed them up and there are some edits I've done that are in the catalog and not saved in the DNG file. I can't save that info if the program can't 'see' the files when using those catalogs. 

  • Mailto not working in FF 5 & 6

    Mialto: would not work in FF 5, then it updated to FF 6 and still no worky? Boo hoo! Trying to send to Gmail by the way. Oh yeah and why won't my Google toolbar work too?

    If you can figure out how to upload your newest DNG to Dropbox I may be able to help you analyze what is wrong, otherwise, I can only guess from what you've said.  A partial substitute for uploading the DNG would be to post a screenshot of what it looks like as you did, originally so at least a judgment can be made about whether it is shot correctly or not.
    The DNG you linked from Dropbox gives me a reasonable error message, yet it seemed to give you something else.  This is what I don't understand, unless you're using the older CCPP app, rather than the slightly newer one, so first, make sure you've downloaded the 2010 version of the software and the 2011 version of the plug-in that interfaces with the software,  in case what you've installed from the disk is the original version.
    One of these links appears to be just the plug-in and one has both the software and the plug-in as separate items.  I assume the plug-in is the same for both but I'm including both links just in case one is newer.  Since the one that is just the plug-in mentions Windows 8, I assume it is the most up-to-date.
    ColorChecker Passport Adobe® Lightroom® Plug-In N/A
    X-Rite ColorChecker Passport – X-Rite Photo – X-Rite Passport
    Secondly, if you still have them try profiling the original NEFs instead of the DNGs.
    Thirdly, if you must make DNGs, it can matter what the Compatibility Level is and try an older one, since the CCPP software hasn't been updated in several years.  This doesn't seem to matter for some cameras but it does for others.

  • Custom Camera Profile Disables External Editing?

    I'm using Lightroom 5 and Photoshop CS5.  The problem is that if I apply a custom camera color profile created by X-Rite Passport Color Checker, I can no longer use an external editor, such as Photoshop, to edit my photos.  Before I apply the custom profile, the external editor function works just fine.  If I apply a custom profile in the Camera Calibration panel, then the ability to use external editors no longer works.  There is no error message, but nothing happens when I try to edit in an external editor.  If I go back and turn off the custom profile and go back to Adobe Standard, then the external editor function works again.  What is going on?  Is there a way to make it possible to apply a custom profile in Camera Calibration and still be able to use the external editors?

    A suggestion: it sometimes happens that the main "edit in PS" function gets.. a bit confused. I agree with the other posters that it's critical which program is to render your image to an editable state (ACR, or LR)... which also means, whether PS is going to simply open up an already-saved file from disk, or be passed instructions to have ACR make it an unsaved image in memory.
    Perhaps there is some issue with ACR seeing the folder where Passport is saving its special camera colour profiles via LR - the more standard ones are located in a structure shared by both programs, the same as with lens profiles. This will only be a difficulty, if it is ACR which is trying to do the job of rendering the image.
    Just to clarify: normally when we say LR version such-and-such is compatible with ACR version such-and-such, we are assuming that the latest available Process Version is being used within Lightroom. For any individual image which happens to be set to an earlier Process Version, the compatibility with ACR operates, as if an earlier version of LR was being used. So (for example) one image using PV 2012 would get necessarily rendered by LR when you selected "Edit in PS" with PS CS5, because that is known not to support PV2012. But another image using PV2010 might get sent directly to CS5's ACR within the same setup (provided not earlier than 6.7), without giving the option, since that version of ACR IS known to support that generation of image adjustments.
    To troubleshoot whether external editing is or is not possible, it can be helpful to set up Photoshop manually as a LR external editing preset (I find this useful anyway). This is done within the lower, "additional" part of the External editing tab in LR Preferences. By browsing direct to the Photoshop executable, you can specify whether 32-bit or 64-bit, also set up the bitdepth and colourspace, and explicity name that. When this name is then selected against an image from the "Edit in..." context menu, it is definitely Lightroom that renders the image - you can be sure that ACR is not involved.
    If Lightroom cannot render an image under such an external editing preset, save it to disk / add a new imported image version, and have PS open that, when a {Passport profile is selected - but those things can happen when (say) Adobe Standard is selected, then AFAICT that narrows down on LR's ability to use the profile which Passport has made. I'd still have expected some kind of a warning message.
    Even if PS was for some reason unable to open the image, but LR had definitely been the one told to render it - I would not expect to have "nothing" happen. I would expect to see a new image version in LR stacked with the original - named (by default) either [Imagename]-edit.tiff or [imagename]-edit.psd - which looked exactly the same as the current LR edits, only hard-rendered into a flat pixel file.
    regards, RP

  • What is the rationale behind the "Adobe Standard" color calibration profile?

    Hi! I'm trying to figure out how to make the most of the various color calibration profiles Adobe offers for my cameras with Lightroom 5. I do understand the purpose of the camera-specific options--they're designed to help approach camera JPEG processing mode colors. And they work wonderfully--they're very helpful!
    But I don't really understand the purpose of the "Adobe Standard" calibration option. What is it for? Why does it look the way it looks? Has it been designed to ease certain processing goals? To enhance certain colors or tonal combinations? Is it designed to be more accurate than the manufacturer profiles in some way? What can I do with "Adobe Standard" that I can't do with one of the camera-specific calibration options?
    I would find it *extremely* helpful if someone who's involved with the engineering behind Lightroom's color (or anyone else who's especially knowledgeable about Lightroom's design) might talk a little bit about why "Adobe Standard" looks the way it looks. What's it for? To what purposes can I leverage it?
    Thanks so much!

    MarkJoseph wrote:
    I would find it *extremely* helpful if someone who's involved with the engineering behind Lightroom's color (or anyone else who's especially knowledgeable about Lightroom's design) might talk a little bit about why "Adobe Standard" looks the way it looks. What's it for? To what purposes can I leverage it?         
    Adobe Stadnard is the name for the individual profiles Adobe builds for each camera it receives. A new camera ships, Adobe gets their hands on one and builds a profile with that sample. It isn't suppose to mimic the in-camera JPEG settings, I don't believe it's supposed to mimic anything but instead produce what is (and quotes are super important in this context) the most 'accurate' color response from the target they use to create the profile. But here's the rub. Not all cameras from the same make and model behave identically. Adobe simply can't get piles of the same body and build then average that response. So they provide a means for you to build your own custom DNG camera profile and for differing illuminates. So if you want to leverage it, you'd get a target (MacBeth 24 patch, X-rite Passport) and build your own custom profile. It can really help depending on how your sensor deviates from the sensor Adobe got to build their profiles.
    For more info on DNG profiles and rolling your own:
    In this 30 minute video, we’ll look into the creation and use of DNG camera profiles in three raw converters. The video covers:
    What are DNG camera profiles, how do they differ from ICC camera profiles.
    Misconceptions about DNG camera profiles.
    Just when, and why do you need to build custom DNG camera profiles?
    How to build custom DNG camera profiles using the X-rite Passport software.
    The role of various illuminants on camera sensors and DNG camera profiles.
    Dual Illuminant DNG camera profiles.
    Examples of usage of DNG camera profiles in Lightroom, ACR, and Iridient Developer.
    Low Rez (YouTube):
    http://youtu.be/_fikTm8XIt4
    High Rez (download):
    http://www.digitaldog.net/files/DNG%20Camera%20profile%20video.mov

  • A D300-Work Orange (And My Apology To Adobe)

    For a long time now, I've been noticing the reds in my D300 photographs have been kinda orangy. And, I incorrectly thought Lightroom was the problem, and even got a little uppity about it on this forum, if you can imagine. After further consideration, I've realized the problem is with the D300, not Lightroom. I've been comparing raws + jpegs of a Canon G12 against the Nikon D300, and reds-wise, the G12 is spot-on, whereas the D300 captures them orangy - in both NX2 and Lightroom, raw and/or jpeg, neutral and otherwise...
    My apology for previously blaming Adobe...
    Rob

    Thanks Butch,
    Ya know, I messed with the DNG Profile Editor a while back but never integrated it into my "daily" photography workflow. I found the profiles I created with the X-rite passport checker so close to ACR 4.4 that I just started using ACR 4.4 when I want a linear profile. Anyway, its hard to tell from your example whether the reds have an orange bias since there is nothing to compare it to. Comparing my D300 to my Canon G12 (and to real objects) is what really drove the point home to me.
    Its my hope that Adobe will eventually make "DNG Profile Editor - Like" color adjustments available on a photo-by-photo basis from within Lightroom proper, so its more convenient.
    Presently I use HSL presets (both relative and absolute) to make the reds redder, when I notice oranginess, which sometimes is quite good enough, and other times doesn't quite cut it... I probably should get used to that DNG Profile Editor...
    I was just about to post some example comparisons but decided just to report verbally: The Adobe Standard profile renders the reds almost exactly the same on the D300 as the G12 - both of which match reality almost exactly. Its the one profile I hadn't tried on the D300 because I find it often renders the non-Reds a little too Magenta-y for my taste and so I usually don't use it. Anyway, I guess the D300 reds/orange bias thing is maybe more of a Nikon color preference thing than a "sensor recording" thing, although I thought Neutral was supposed to be "closest to reality color-wise, albeit a little flat...", on my D300, it seems off, reds-wise... (NX2 as well as Lightroom...)
    Oh well & hmmm......
    Rob

  • Colour issues LR3

    I shoot ijn Camera RAW on a Canon 5D2 in LR3 and I'm having colour issues; skin tones are often purple/magenta tinted and very difficult to correct. I usually set the WB to Custom and shoot a grey card and set the picture style on the camera to Neutral (why does the WB affect RAW images anyway, I thought it only operated on the jpgs?)
    On import, pics often look ok then resolve into higher contrast, garish colour versions which are less pleasing - have I set a preference incorrectly or am I missing something else?
    All help gratefully received
    Ian

    maninahat wrote:
    On import, pics often look ok then resolve into higher contrast, garish colour versions which are less pleasing - have I set a preference incorrectly or am I missing something else?
    When you first import, you see the small embedded JPEG the camera generates. This matches what you see on the LCD but is based on having the camera do the conversions which you're not doing. LR therefore has to build it's own high quality previews but more importantly, that is based on it's current default settings using it's own engine. So just forget what you initially see, you'd not get that unless you set the camera for JPEG.
    The key is setting up a custom default you prefer. You could pick a general DNG profile, move any of the sliders around etc and the, if you option click in Develop, the Reset button toggles to allow you to create a new default. From there you can of course adjust to taste. You'll still have to white balance and so forth but you should try to get a decent 'starting point' from Import on. For WB, might want to set the camera for Auto WB. Note this setting has no effect on your raw data! It's only a suggestion you can accept or alter. With Auto WB, you'll probably find more images come in looking closer to what you want then say forcing Daylight (which would look butt ugly IF those images were shot under Tungsten). Auto IS NOT PERECT by a long shot but since the setting doesn't affect the data, might as well try for something that gets you in the ball park.
    Using any card to WB (and you should use a white, not gray card) again is often just another starting point. You seasson to taste using Tint/Temp. And of course, if you shot a scene at sunset and did this, you'd kill the color expected at that time of day. Bottom line is, when you capture raw, the WB can be anything you wish, anything you think looks good. That would not be the case with a JPEG. If you set it, you're then kind of stuck with that rendering.
    Lastly, creating one or two custom DNG camera profiles can work wonders. Check out the X-rite Passport product. You'll end up with a really great target for balancing as well.

  • Loss of white balance correction

    I just returned from a dive trip. In addition to cropping, adjusting the exposure and cropping, I use the white balance feature to correct the color of photos taken without a flash at depth. I uploaded my cards to my MacBook Pro (both the laptop and my Mac Pro are running Aperture 2.1.3), and edited these images. When I got home, I exported the project (like I always do), and imported it into my main Aperture library on my Mac Pro.
    When I review these images, the color-corrected previews are seen in the Browser. When I click on an image, the color-corrected preview is shown in full size on my second, 30" Cinema Display while the RAW image is loading. However, once the full image is loaded, the white balance reverts to the original - but the levels and cropping are maintained! I can re-do the white balance correction, but once I quit and restart Aperture again, the white balance correction is again lost - but not my other edits! Thus, not only were the white balance corrections done on my laptop lost when I exported/imported the project, the repeat corrections done on my MacPro are lost when I quit and restart Aperture.
    Curiously, after I've re-done the white balance on several images and quit, when I restart Aperture there is no indication that there are any images or projects that haven't been backed up in a vault.
    This has never happened before when I would import a project; the last time I successfully imported a project with all of its adjustments maintained was February (I don't recall when 2.1.3 came out). I've searched this forum to no avail; has anyone else experienced this?

    I've the x-rite passport and I can say only a thing:
    Color correction seems to be an opinion!
    With Aperture (and Canon RAW) with only white balance you will get an image very very close to the result with x-rite calibrated DNG and Adobe Camera Raw, but...
    In both case Colors are very outside of reality!
    Adobe Camera RAW and Canon DPP give other different "crazy opinion" on blues reds and greens, and the only program that I found go very closer to reality seems to be CaptureOne.
    In my tests I've used two 5600°K Bowens lights to take a photo of x-rite passport and I've tried to compare it with the official datasheets from xrite:
    http://xritephoto.com/phproductoverview.aspx?ID=1257&Action=Support&SupportID=5159
    Seems very difficult to get real colors from the same RAW file, and every software give a personal opinion from the same data (?!)

  • White Balance Correction using Color Cecker?

    Hi,
    I have been looking at a number white balance cards and also at cards used for color correction cards, such as "Color Checker White Balance 18% Gray Card 16:9 format" (see http://cgi.ebay.com/Color-Checker-White-Balance-18-Gray-Card-16-9-format-/150465 201169?pt=LHDefaultDomain0&hash=item23086cc411). Is there a way of using these cards (automatically) for color correction when importing images or using a not too time-consuming process after the import?
    Thanks!

    I've the x-rite passport and I can say only a thing:
    Color correction seems to be an opinion!
    With Aperture (and Canon RAW) with only white balance you will get an image very very close to the result with x-rite calibrated DNG and Adobe Camera Raw, but...
    In both case Colors are very outside of reality!
    Adobe Camera RAW and Canon DPP give other different "crazy opinion" on blues reds and greens, and the only program that I found go very closer to reality seems to be CaptureOne.
    In my tests I've used two 5600°K Bowens lights to take a photo of x-rite passport and I've tried to compare it with the official datasheets from xrite:
    http://xritephoto.com/phproductoverview.aspx?ID=1257&Action=Support&SupportID=5159
    Seems very difficult to get real colors from the same RAW file, and every software give a personal opinion from the same data (?!)

  • Camera Calibration Profiles do not show in Develop Module LR5 / Windows 7

    I have selected three specific camera profiles (Nikon D300, Nikon D700 and Canon G12) and placed them into:
    c:\Users\{me}\AppData\Roaming\Adobe\CameraRaw\CameraProfiles\{Nikon D800}
    I restarted Lightroom 5 and viewed a RAW photo (not jpg or tif).
    But my Nikon D800 or the other two camera profiles do not show up in the Develop Module Camera Calibration drop down menu, nor in the Presets drop down in the Navigator panel.
    What am I doing wrong?

    DdeGannes wrote:
    It is possible to have third party software providers create profiles for your camera that simulate other camera profiles. I have had that done for my Olympus E520 and E300 cameras so that I have dozens of option available.
    Yes (to a degree). You can build your own custom DNG camera profiles, that's a good first start. Then you could edit them using the free DNG Profile Editor from Adobe. I'd start with custom profiles for each camera and see if that produces an acceptable match among them.
    This may help too:
    In this 30 minute video, we’ll look into the creation and use of DNG camera profiles in three raw converters. The video covers:
    What are DNG camera profiles, how do they differ from ICC camera profiles.
    Misconceptions about DNG camera profiles.
    Just when, and why do you need to build custom DNG camera profiles?
    How to build custom DNG camera profiles using the X-rite Passport software.
    The role of various illuminants on camera sensors and DNG camera profiles.
    Dual Illuminant DNG camera profiles.
    Examples of usage of DNG camera profiles in Lightroom, ACR, and Iridient Developer.
    Low Rez (YouTube):
    http://youtu.be/_fikTm8XIt4
    High Rez (download):
    http://www.digitaldog.net/files/DNG%20Camera%20profile%20video.mov

Maybe you are looking for