DNG Profiles with 32bit Tiff images

I am wondering what the correct procedure for creating these new 32bit HDR Tiff files in LR4.1 is, when you also want the image to have custom DNG profiles that were created from the XRite color checker. I know how to take 6 images, merge them to HDR in photoshop, save the image as a 32bit tiff. But how can I be sure my DNG profile went with the image over into PS. Also, do each of the images going into the HDR have to have the exact same whitebalance. Does lightroom secretly create tiff files before sending them to PS, or is it sending PS the RAW files to combine? Any help would be much appreciated! Thanks Rick

Hi Eeric, Having so many control points was in a effort to match the profile to the output of Capture NX, so that I could integrate all my workflow into Photoshop. I could not do without the use of as many control points because as you could see, so many hues of green were off. we should find a way around this problem. either like developing a set methodology of aproaching color adjustment or something else. I also suggest having a "Color Curve" probably something on the lines of the tone curve with input and output values of Hue.
I feel that there should also be a way to adjust the color range that each color control point can influence. That way there will not be a need to put too many control points close together.
Anurag

Similar Messages

  • DNG profile with Fuji X100s raw files...

    Hi,
    I'm trying to make a dng profile for my Fuji X100s (I did the same recently for my Canon 5dII).
    Because I shoot architecture and interiors, I profiled for daylight, tungsten, and flourescent light (I also did this for the Canon with success, much improved color, sepecially in fllourescent light).
    With the Fuji x100s, the daylight profile was good, the tungsten seemed very desaturated, and the profiler kept giving me an error message for the flourescent light saying there was an extreme color cast on the grey patch and it couldn't create a profile (I tried 2850, 6500, and "both tables"). The grey patch on the flourescent card was reading (aprox) 3200K and +50 Magenta, so not off the charts, so to speak....
    Why is this? Is it to do with the type of sensor in the camera (Xtrans CMOS)?
    Thanks,
    Alan.

    JPGs are relatively small, and raw files relatively big, so if there is an issue writing data to the card where it corrupts after a certain amount is written, then the raw file could be the only file with enough data written to it thing that is corrupt.  If every single raw file is corrupted the same way and none of the JPGs seem to be then it may be something else related to raw files on the computer, like the computer memory, or the drive that the camera-raw cache is on, or even a virus-scanner locking a file at the wrong time when it is written or read.  The other thing to watch is that the raw files have an embedded JPG preview in them that may be ok, as well, and only when LR interprets the raw data will the corruption be visible.  The embedded JPG preview is what you see in the Import panel grid and is also what you see momentarily just after you’ve imported, before LR has a chance to recompute a preview from the raw data.
    To see both raw and jpgs in LR then you need enable the LR preference to treat raw and jpg files separately, for future imports so what you’ve already imported will stay the same, until you do a Synchronize on the folder Once you enable that preference then you can synchronize the folder to have LR reimport just the new (newly visible) JPGs. 
    The most important initial test to do is transfer the same set of files from the card to the computer more than once—you’ll have to disable the duplicate checking temporarily—and check if they have precisely the same corruption in each copy of the image or if it looks different.  If it is the same then the data is likely bad on the card.  If it is different, then the photos may be ok on the card and something in the transfer process or the computer, itself, may be bad, and there is hope you can mitigate the problem and get the uncorrupted raw data, somehow.

  • JAI(Java Advanced Imaging) Problem with splitting TIFF images

    Hi
    I am getting problem with height when I use this program to split TIFF images
    ImageDecoder decImage = ImageCodec.createImageDecoder("tiff", inStr,
    null);
    Then it creates RenderedImage page by page and encodes them to file:
    String outFileName = "";
    OutputStream outStr;
    TIFFEncodeParam encParam = new TIFFEncodeParam();
    encParam.setCompression(TIFFEncodeParam.COMPRESSION_PACKBITS);
    for (int i=0,n=this.getPageCount(); i < n; i++)
    outImage = this.decImage.decodeAsRenderedImage(i);
    outFileName = "C:\\Temp\\Split" + i + ".tif";
    outStr = new FileOutputStream(outFileName);
    BufferedOutputStream bOutStr = new BufferedOutputStream(outStr);
    encImage = ImageCodec.createImageEncoder("tiff",bOutStr,encParam);
    encImage.encode(outImage);
    bOutStr.flush();
    bOutStr.close();
    }The images are shrinking when I split . I need a solution to this problem.
    Thanks for any help in advance
    Sudheer.

    Hi
    Did you get a solution for your problem. I am also trying to split a TIFF file.
    Thanks in advance
    Antony

  • Problems with placing Tiff images in CS2

    When placing a Tiff image in CS2 the file crashes or a memory warning appears. I am able to place much larger EPS images, so image size is not necessarily a factor Saving the file as an EPS in PhotoShop is not a solution as I am placing GeoTiffs which must retain their geographic reference file. The OS is Windows XP 32 - a quad core proc. - Radeon HD 6350 graphics controller with 512mb (dedicated)

    No - it is possible to place a geotiff in illustrator - I have been able to do it. However, now I have a new PC and am unable to place the same types of tiff images I previously was able to in an older PC.

  • Adjustment brush auto mask broken for 32bit TIFF image

    Hello,
    I am using Lightroom 4.2 (updated today) on Windows 7 64bit. I have an issue using the adjustment brush with the option "Auto Mask" within a 32 bit TIFF file: the Auto Mask magic there does not work.
    I've created 32 bit TIFF files using the "merge to HDR Pro in Photoshop" workflow, where the resulting TIFF is automatically added back to Lightroom. There, I edit the TIFF just in the same way as I edit any other picture in Lightroom. Some of my TIFF files have very clear edges with high contrast. Example:
    I assume you agree with me that the adjustment brush Auto Mask must be able to detect this particular edge between the blue sky and the almost black wall of a building. However, when I use the adjustment brush on this edge (no feather, 100 density and flow, show selected mask overlay in green), it does not detect the transition:
    When I do the same in one of the RAW pictures that contributed to the TIFF above, Auto Mask works as expected:
    I tried this with various edges in various TIFF and RAW files. In the RAW files, basically all edges are detected, while  the Auto Mask feature entirely fails in my TIFFs. I've first observed this in Lightroom 4.1. Then I updated to 4.2 which did not change the behavior.
    Is there something I can do wrong? Note that in this tutorial: http://tv.adobe.com/watch/the-complete-picture-with-julieanne-kost/quick-tip-creating-32bi t-hdr-images-in-lr-41/ Julieanne Kost is doing exactly this: first she merges a set of pictures to a HDR TIFF and then she uses the adjustment brush with Auto Mask in the resulting TIFF. In the video it looks like the edge detection works properly for her.
    Any suggestion is welcome. Thanks!

    +1 vote.
    Auto-mask has great potential, but is not quite there yet...
    I'd like to see a little more control - what exactly you are trying to mask, and what not... - ya now: some tolerances/thresholds for color and luminosity and texture... - and maybe the ability to enhance the edges after the fact.
    R

  • How do I associate a scanner's icc profile with the TIFF files from scanning old slides?

    I profiled my slide scanner and have an icc profile for that scanner. In Photoshop I can assign that profile to those files obtained by scanning slides in that scanner. Can I do something functionally equivalent inside Lightroom?

    This is totally off on a tangent, so feel free to ignore:
    After struggling with slide scanning on an Epson V500 for years, and generally getting lousy results (loads of chromatic aberration, poor detail resolution despite plenty of pixels, and bad color) - I decided to try to photograph them. The setup is simple. D800, Micro-Nikkor 105mm with extension tube (but any macro that goes 1:1 should do), small piece of diffusing plastic, flash backlight. And some tape to hold it all together.
    Wow.
    The result is razor-sharp with all the fine detail I have always missed, totally clean from CA, and with a few quick Lightroom adjustments it's there. Previously I had to bring them into Photoshop and spend hours.
    The scanner is outside my window if anyone needs it...

  • Removing Color Cast with TIFF images?  (PSE 8)

    Hello,
    Hoping someone can help.  I'm trying to "remove color cast" with TIFF images and I'm not seeing the option as available.  It works fine when I try to use it with JPEG images.
    To be clear....I'm using PSE 8...after opening a picture (of course), on the top menu "Enhance", then "Adjust Color".  When I'm working with a TIFF image the option "Remove Color Cast" is not available/active.  It works fine with JPEG images.
    What am I missing?
    Thanks,
    Rich

    Alternatively if you want to keep the file at 16 bit click File >>Open As >>Camera Raw
    Then use the temperature and tint sliders to edit your tiff.
     

  • DNG profile management

    Is it possible to create and use a shoot-specific custom DNG profile to process a set of images for a given shoot, and then archive that DNG profile for safekeeping but removed from view of Lightroom's Camera Calibration panel, without compromising Lightroom's ability to still work with that shoot's images - say, to make further develop refinements, virtual copy variations, prints, etc.?
    Asked slightly differently, when in Lightroom's Camera Calibration panel you select a specific DNG profile to apply to a given raw image, does the profile data from within that DNG profile become image-specific metadata of the target image and get stored along with the rest of the image-specific metadata in the Lightroom catalog itself (and subsequently in the DNG raw image file when I save the Lightroom data to that image file)? Or, instead, is only the IDENTITY of the selected DNG profile saved as image-specific metadata, with the DNG profile itself needing to remain "installed" in order to carry out any future Lightroom work on that raw image?
    Using the X-Rite ColorChecker Passport in conjunction with Lightroom, it is quite easy to imagine creating custom DNG profiles specific to a given shoot's unique lighting conditions. Creating DNG profiles specific to a given shoot, the collection of shoot-specific DNG profiles for a given camera body could grow to be quite large over time, making it tedious to wade through that collection in Lightroom's Camera Calibration panel to select the particular profile for the shoot being processed. X-Rite makes the "DNG Profile Manager" available to registered users of the ColorChecker Passport to assist with this very problem. It's great that this utility allows us to "Disable" DNG profiles, allowing us to keep our Lightroom Camera Calibration "Profile" menu manageable. But, if you use the X-Rite DNG Profile Manager to do this, does "disabling" a given DNG profile interfere with any further work in Lightroom on images for which that given DNG profile has ALREADY been applied?
    PLEASE do not speculate on this response. If you do not know for certain, please allow someone who does (an Adobe engineer, perhaps?) to enlighten us.
    Thanks in advance,
    /eddie

    Thank you to those who have offered responses.
    Please do not get confused. As the most recent response clarifies, this is not about storing profiles within original raw files, or the differences between DNG files and original raw files. In fact, at it essence, my real concern is not even about DNG files at all, really, although it includes them by association.
    My original question can really be answered in consideration of Lightroom alone: When a custom DNG profile is selected for an image by using the Camera Calibration panel of Lightroom's Develop module, does Lightroom itself internalize that DNG profile selection by recording into the Lightroom metadata database only the IDENTITY of that DNG profile assignment, or the actual DNG profile data contained within that DNG profile? If Lightroom records into the Lightroom database only the identity of the assigned DNG profile, then Lightroom would of course need to go back into that DNG profile later for the actual DNG profile data in order to do any subsequent development processing of the image for which that DNG profile was assigned. If, however, selection of a DNG profile using the Camera Calibration panel of Lightroom's Develop module causes Lightroom to record into the Lightroom database the actual DNG profile data contained within the selected DNG profile, then Lightroom would have no need to go back into that DNG profile later for the profile data, and the DNG profile itself could be safely "un-installed" ("Disabled" by the X-Rite DNG Profile Manager) without adversely affecting Lightroom's ability to properly process that image using the selected DNG profile's information. DNG image files themselves are not even really involved in determining the answer at this level.
    The interplay with the associated raw image's DNG image file occurs when Lightroom-maintained metadata for the image is saved out into the DNG image file itself, either automatically or manually, and, yes, I was being very specific to discuss DNG raw image files in that context. I understand from the response provided by "ssprengel" that saving the actual DNG profile data out into the associated DNG image file only happens when using "Update DNG Metadata & Preview" and does not happen through the more common routes of automatically or manually saving image metadata back to the DNG image file. Why this more robust ("complete"?) level of image metadata preservation out to the DNG image file only occurs through a more obscure mechanism is a mystery to me, but that is not the topic of this discussion.
    So, my real question really still remains. Combining the ideas from both of the paragraphs above, if Lightroom only saves DNG profile data out to the associated DNG image file using this more obscure mechanism, then does that mean that Lightroom does not normally retain the DNG profile data within the Lightroom database at all -- that it really only retains the identity of the selected DNG profile, and that only when this obscure mechanism is explicitly invoked does Lightroom deem it appropriate to actually read the profile data out of the selected DNG profile and pass that profile data along to the associated DNG image file, and that even then Lightroom itself does not retain that profile data internally? If this is the case, then the DNG profile cannot be "Disabled" without adversely affecting normal Lightroom processing of the associated image [by "adversely", I mean without having Lightroom revert to the Adobe Standard profile or any other unintended side effects]. However, if Lightroom actually does retain this profile data internally upon original DNG profile selection, even if it doesn't bother to save it to the associated DNG image file except through the use of the obscure function, then it would be safe to "Disable" the DNG profile after initial profile selection and not interfere with Lightroom's normal ability to process the associated image using that profile.
    Taking the obscure function awareness into account, I guess this now has the possibility of making this subject much more complex. If Lightroom does not store DNG profile data within the Lightroom database (which would require continued availability of the DNG profile for processing associated images), BUT Lightroom provides this obscure mechanism for "forcing" save of assigned DNG profile data out to the associated DNG image file, then what happens when the DNG profile is "Disabled" and Lightroom goes to process that image? Does it look into the associated DNG image file to determine if actual DNG profile data has been saved there and go ahead and use it if it exists? Or does Lightroom ignore DNG profile data saved to a DNG image file in all contexts, and unconditionally always require the assigned DNG profile to remain available in order to carry out normal Lightroom development or rendering processing of the associated image?
    This is admittedly a lot of words to discuss a simple desire: I want to shoot with shoot-specific DNG profiles, assign them to the shoot's images and develop them, and then archive off ("Disable") the DNG profiles from that shoot so that my Camera Calibration "Profile" listbox does not become unmanageable. Period. If I absolutely must go back and re-Enable a specific DNG profile later to make a print of one of those images a year from now, then I guess that's what I have to do, but that seems a real shame when all other image-assigned "edits" store those "edits" as image-specific metadata, and profile assignment is just another "edit" (although saving the profile data, rather than just the profile identity, may not be included in this "edit"). Whatever works out to be the simplest, most straightforward course to accomplish my objective is what I need to do. Ideally, that would be painless if Lightroom records into the Lightroom database the actual DNG profile data when the profile is assigned to an image using the Camera Calibration panel's Profile selector.

  • Displaying TIFF images in Oracle Forms 6i

    Hello, friends!
    I am working in Oracle Forms 6.0.8 (that ancient tool) and encounter a problem with displaying TIFF images.
    I have a number of scanned images and some of them are displayed and some are not. I've tried both extracting them from the database or from the file system (using READ_IMAGE_FILE). Sometimes I am getting just blank field in my image item and sometimes (after using READ_IMAGE_FILE) I get the error FRM-47100 (cannot read image file). Of course I've checked that all the files are displayed using standard tools for displaying TIFFs.
    Basically the question is what kind of TIFF is considered valid and readable by Oracle Forms.
    Analyzing TIFF tags actually gave me nothing: I have a pair of files with tags different only in image width/length and a number of rows/strip (but even those values are close), and one of the file is displayed correctly while the other is not. The thing I noticed is that invalid files are using compression type of CCITT Group 4.
    Possibly Oracle Forms follows TIFF specification only to certain extent and does not support all the extensions, while sometimes the problems are not visible to user.
    As a result of my work I need some automatic tool that converts undisplayable TIFF files to displayable ones but firstly I am to determine where the problem is. And it would be very good to have a prooflink that approves my decision.
    Looking forward to any help! Thanks in advance.

    Thanks to everybody, but I'm afraid my files don't contain any EXIF tags (although TIFF seems to support them). The file doesn't contain any tags with IDs greater than 0x7FFF but only core TIFF tags (with IDs of lower numbers). Moreover I have a file with exactly the same set of tags (but the values are a bit different) which is displayed properly.
    I've shared the issued file (nondisplayable) on the following link: [https://rapidshare.com/files/3137807470/2.tif]
    If anyone could tell me why isn't it displayed in Forms I would be very grateful.

  • Are selfmade DNG profiles referred to the cameras serial nr. (et al.)?

    Need a quick help, because I'm just writing an article about the DNG profile editor...
    When I make my own DNG profile with the DNG PE, is this profile referred to the cameras serial#? If you have more than one camera of the same model, you should be able to make a separate profile for every body. If you have different profiles for different cameras of the same model - are the right profiles automatically referred to the corresponding camera in ACR? Or do I have to use different profile names to select them manually?
    When I have assigned the different profiles to the corresponding cameras in ACR and I fix this as a standard ("Save new camera raw standard"), will the right profiles be assigned correctly by ACR from now on? Only if "Align standards at the cameras serial number" in the ACRs settings is active? (Sorry, I don't know the correct option names in english, because I only have the german version of PS...)
    Unfortunately I can't try this by myself, because I own some digital cameras, but not two of the same model... :-(
    Is there anybody who knows this? Or is there an owner of "camera tweens" who can figure this out for me?
    Another question: If I have already made a camera calibration with ACR (modified the red, green and blue primaries), can I transfer these values (without change) to the DNG profile editor to save and use this calibration as a profile? (I know I have to set the calibration to 0 in ACR in this case, because instead it is applied twice.) My question is: Do same values of the calibration in ACR and PE produce exactly the same result?
    I just tried this: It is not the case. Why not? I compared the two results with the difference-mode, they are not exactly equal (differences up to six 8-bit integer values).
    What about the "Hue (dark tones)" slider in ACRs camera calibration? Why is it missing in the PEs Color Matrices window?
    Thx a lot for your answers
    Marius

    So far as I am aware, DNG camera profiles do not store camera serial numbers, only camera model. Application can, if they want, associate a particular profile to a camera with a particular serial number.
    As regards differences between PE and ACR calibration sliders - I don't think the Adobe people have ever had it as a design goal for PE and ACR to be exactly the same in that regard. But only someone on the inside like Eric Chan would know for sure.
    Sandy

  • Fetch .tiff image via URL

    Hi,
    I am trying to fetch an image using the CL_HTTP_CLIENT class. My coding looks something like this:
      TRY.
          " Create the HTTP client
          CALL METHOD cl_http_client=>create_by_url
            EXPORTING
              url                = lv_img_url
            IMPORTING
              client             = lo_client
            EXCEPTIONS
              argument_not_found = 1
              plugin_not_active  = 2
              internal_error     = 3.
          IF sy-subrc = 0.
            " Set header fields.
            CALL METHOD lo_client->request->set_header_field
              EXPORTING
                name  = '~request_method'
                value = 'POST'.
            CALL METHOD lo_client->request->set_header_field
              EXPORTING
                name  = '~server_protocol'
                value = 'HTTP/1.1'.
            CALL METHOD lo_client->request->set_header_field
              EXPORTING
                name  = 'Content-Type'
                value = 'image/tiff'.
            "send and receive
            lo_client->send( ).
            lo_client->receive( ).
            "get status
            lo_client->response->get_status( IMPORTING code = lv_return_code ).
            "get the response as binary data
            lv_img_xstring = lo_client->response->get_data( ).
            "close connection
            lo_client->close( ).
          ENDIF. "sy-subrc = 0
        CATCH cx_root.
      ENDTRY.
    The code is working fine when the url is pointing to a .jpeg file (and removing the set_header_field part). However, with an .tiff image url it does not work. Any help is greatly appreciated.
    I am using the code in an assistance class to get the xstring representation of .tiff images. The xstring is converted using IGS and finally displayed in Web Dynpro ABAP.
    Thanks.

    Hi again,
    this is one of the questions that I would have liked to avoid posting. It turned out that my links where copied from another system and therefore there was no document/image behind the link. Unfortunately, some of the jpeg images were real in the development system and that caused the differing behaviour.
    The answer is therefore that the coding posted in this question works fine with .tiff images.

  • DNG Profile Editor not working with new Profiles from LR 3.6?

    I'm noticing that DNG Profile Editor is not really able to work with profiles from newly supported cameras, like the X10. Apparently the profile spec has been updated. Has DNG Profile Editor been abandoned or will it be updated to work with the new spec? I really hope it is!

    Thanks.  I am looking forward to editing the v4 profiles for the D700 - I just want to change a few colors in the existing profiles.  I think the existing v4 profiles do an excellent job of matching the Nikon colors, but I don't like a few of the Nikon colors.  Some colors have too much Red, but Red is too Orange. 
    I have selected a number of images that have colors I want to change.  I selected the Camera Neutral (v0) and Camera Portrait (v0) and using the latest DNG Profile Editor I select the 18 colors from the Color Checker Chart.  I then use the images that have the colors I want to change and determine which of the 18 points I selected from the Color Checker are close.  I then edit those points - only 6 points.  I only need to change the Hue by 5 units or less.  I don't change any of the other selected points of the Color Checker, but feel that by selecting them I locked in the exisiting colors.  Hope this is a good aproach. 
    I wish Nikon would do something equivalent to the DNG Profile Editor for their Picture Control profiles so they could be edited and loaded into the camera.  

  • Need help urgently with conversion of tiff images(.odm) to pdf files...

    Hi Friends!!
    Currently we are working on a project which involves conversion of tiff image files to Pdf files. We are able to convert .tif files to .pdf files.(We are using iText libraries for this..)
    But the only problem we are facing is ---
    We have some .odm files which are multipage tiff files. But we are unable to convert them into .pdf files.
    Note:- Please note .odm is a proprietary extension given by Optix Document Management and Workflow Systems. We figured out that .odm works as a collection of .tif images.
    I searched a lot on the net but couldn't find any help, so, if anyone has any idea of how to go about doing this please let me know...
    Please email any suggestions to [email protected]
    Thanks in advance for your help,
    Rita

    I'm afraid I can't help much with your problem, but I think I can offer some advice on how to get better, faster answers here at this forum:
    First, don't flag your question as urgent, even if it is for you. Claiming urgency is very likely to be counter-productive: most forum regulars will simply ignore such messages as rude and selfish attempts to elicit immediate and special attention.
    Besides, unless the Symbionese Liberation Army is about to chase you over the edge of a cliff, your problem probably isn't as urgent as you think. :o)
    Second, don't ask people to reply by private email. Most Forum regulars believe solving problems should be a public, transparent process during which a first try at an answer can and should be corrected if someone more knowledgeable notices that it is incomplete or incorrect. Also, they get some of their reward for being respondents from being seen to be competent and knowledgeable by their peers (not to mention the possibility of collecting some of those precious Duke Dollars).
    Good luck!

  • Tiff image with JPEG compression

    How does photoshop handle RGB and YCbCr as photometric interpretations of tiff image with JPEG compression?
    Are they same?

    Got no idea but here is a website with a adobe pdf answer.
    http://www.ask.com/web?q=How+does+photoshop+handle+RGB+and+YCbCr+as+photometric+interpreta tions+of+tiff+image+with+JPEG+compression%3F&search=&qsrc=0&o=0&l=dir

  • Elements 10 canvas not working with tiff images; works fine with jpegs. What to do?

    Elements 10 canvas not working with tiff images; works fine with jpegs. What to do? It does not allow me to add a colored canvas, only a blank canvas.

    Perhaps some of the tiffs are already layers.
    In other words, since jpegs don't support layers, they all ways open with one locked background layer, but the tiff format does
    support layers so the tiffs don't have to have a locked background layer and can already be a regular layer that supports transparency.
    For the tiffs you could add a new color fill layer below and use the color you want the enlarged canvas to be.
    On pse 10 look at the bottom of the layers panel for the new adjustment of fill layer icon

Maybe you are looking for