X3F Grayscale Bug

When I import into Lightroom 2.1 an X3F raw file previously adjusted in Sigma Photo Pro to have "grayscale" white balance, Lightroom refuses to let me adjust it as a color image. It interprets the raw file as having no color data. I can work around this problem by going back into SPP and changing the X3F's white balance to "daylight" (or any other non-grayscale preset), but would like Lightroom to deal with this more intelligently.

I can confirm this is an issue with LR 2.1 RC:
I downloaded some color X3F RAW files from here:
http://www.rytterfalk.com/2007/04/15/raw-sigma-sd14-raw-for-download/
I downloaded SPP 2.5 Windows from here:
http://www.sigma-sd14.com/software/spp/
Before I started, I put the originals in a subfolder called Color, and copies of the same files in another sub-folder called BW and adding a _bw suffix to avoid the duplicate warning.
I opened the BW folder in SPP, then double-clicked on the first photo to open the Adjustments panel, then Ctrl-B to adjust the WB setting, and changed it to Monochrome, then went to the Next photo, until all were done.
When opening the photos in LR, the initial thumbnails are color for both sets, but the ones adjusted to Monochrome in SPP eventually render as B/W previews, and all the color-specific controls are disabled in Library and Develop.
This is not a case of the default of Grayscale being selected in LR and being able to switch back to Color mode; instead, it is a case of LR not understanding the photos are actually color with a flag set in the header that says Monochrome and refusing to allow switching back to color or changing WB or HSL/Color/Grayscale or even Camera Calibration.
It seems that at most LR should select Grayscale as the default, but perhaps it should have two camera profiles, one as the Color and one as Monochrome for the Sigma RAWs.
Comparing the BW and the Color versions there are less than a dozen bytes different and these happen to be the zero-terminated string that represents the white-balance setting...the RAW data is identical in both files:
C:\phototemp>fc /b bw\SDIM7405_bw.X3F color\SDIM7405.X3F
Comparing files BW\SDIM7405_bw.X3F and COLOR\SDIM7405.X3F
00000028: 4D 41
00000029: 6F 75
0000002A: 6E 74
0000002B: 6F 6F (added for clarity)
0000002C: 63 00
0000002D: 68 00
0000002E: 72 00
0000002F: 6F 00
00000030: 6D 00
00000031: 65 00
Monochrome / Auto
Comparing files BW\SDIM7560_bw.X3F and COLOR\SDIM7560.X3F
00000028: 4D 43
00000029: 6F 75
0000002A: 6E 73
0000002B: 6F 74
0000002C: 63 6F
0000002D: 68 6D
0000002E: 72 00
0000002F: 6F 00
00000030: 6D 00
00000031: 65 00
Monochrome / Custom

Similar Messages

  • Pattern on a path in Grayscale mode: bug?

    I watched Julieanne Kost's video on Hidden Gems in Photoshop cc, and was delighted to learn about the ability of Photoshop to "fill" a path with a pattern. But i couldn't repeat Julieanne's results. Then, after much frustration, I switched from the Grayscale mode to the RGB mode. The problem went away.  Can anyone repeat my experience? If so, someone should tell Adobe about this.

    See Julieanne's video:
    http://tv.adobe.com/watch/the-complete-picture-with-julieanne-kost/hidden-gems-in-photosho p-cc-142/
    Here's what she does:
    Draws a path, then: Edit>Fill>(Use Pattern, Scripted Patterns, Script: Place Along Path)
    In my case, I get an oddly colored result when the file is in the grayscale mode.
    In RGB, I get the expected result.

  • Bug or User Error - Virtual Copy

    All,
    I'm still on 1.3.1 (still too much dust flying on 1.4.1), Mac OS X 10.4. The situation is as follows: Took a standard RAW image file from Canon 40D.
    1. Made a virtual copy of the original, crop aspect set to 8x10, made adjustments, etc. including some spot removal, etc.
    2. Made a virtual copy of the virtual copy, converted to Grayscale, "assumed" the crop value and spot removals came with it. Instead, the second virtual copy is showing up with a crop value of 4x5 and the spots removed in the first virtual copy, return.
    It is very repeatable, and not associated with a specific image file. I haven't tried it on Windows XP yet.
    Jay S.

    Hal,
    I've been doing a little more with this. In Develop module, if I make a Virtual Copy of an image where I've used a Metadata preset to add some data to the image, that metadata preset is refected in the virtual copy as well, if I do the same exact thing with the same exact image in Library mode, the metadata is set to None, as opposed to the Preset I used with the original.
    I know this is different from what I originally stated but seems odd. Also I'm not sure why you don't consider it a bug, small as it may be. I set the original to 8x10, if I wanted the lower ratio of 4x5, I would have set it to that. If 8x10 didn't matter to Adobe then why have it as an option. In my mind the Virtual Copy should reflect the same choice made on the original.
    Jay S.

  • Color Shift Happening When Exporting - Bug in Acrobat Export?

    Hi, we are using InDesign CS3 and trying to output a file to send to a printer. We are desiring to have all colors converted to the printer's CMYK color space upon exporting (they sent us their ICC profile).
    But we are getting a bizarre bug that I cannot figure out. It seems like it's actually a software bug, not an issue with settings. I'll try to describe the issue here:
    Upon using 'Convert to Destination (Preserver Numbers or Not)' in the PDF export dialog in InDesign (using PDF/X-4 setting), using the 'Document CMYK' profile, there is a shift in color for 1 particular element. We have a grayscale image of a bunch of dots (black dots on solid white background) that is placed in a frame in InDesign. This image is 'colorized' in InDesign by setting an image color and a frame color (the image color appears as the 'foreground' and the frame color is the 'background'). We've been doing this all the way back to the Quark days (many years). But if the 'background/frame' color is a combination of C+M+Y (with no black), the Magenta and Yellow values are shifted to the Yellow and Black channels (for example - 52c, 5m, 10y, 0k becomes 52c, 0m, 5y, 10k).
    I have never run into this before, and we've run this job with the same element many times now over the last couple years. But I have always used 'No Color Conversion' in my PDFs in the past. So it has something to do with the 'conversion'.
    So far I've tried:
    - Creating new document with just the single element, also created from scratch. So it's not an error in the file.
    - Starting with different profiles (to make sure the profile wasn't corrupt).
    - Choosing 'Preserve Numbers' or not when outputting PDF.
    - All sorts of color combinations. It also appears that if there is black in the color, this value gets shifted to the magenta channel, then the magenta & yellow bump down.
    - Checked the grayscale image to make sure it was flat, and using pure black & white colors. It is.
    I've also tried printing to Distiller (we have Acrobat 8 Pro), but the settings are a lot different here so I'm not sure if I set it up properly. I made a duplicate of the default PDFX3 2002 profile, then edited the color settings to 'Convert Everything to CMYK' and set our printer's profile as the CMYK Color Space. But images are converted to 'DeviceCMYK' and not the profile I put.
    - ANYBODY have any ideas or even know where I would start???
    THANKS. This job needs to go out, but I'm also trying to get a solid workflow down for the future.

    Looks like the issue in the CM thread.
    I'm trying to replicate the issue but haven't done it yet. Still grasping at straws
    1. Did the ID doc ever undergo Convert to Profile?
    2. In Swatch Panel do "Add unnamed colors". Make sure the grayscale is colored with swatches, not colors created in the Color Picker
    3. Do the color values in the swatches have crazy decimal values? Is the color mode of the swatches CMYK?
    4. What format are the grayscale links - TIFF or PSD?
    5. Make certain they are links, not embedded (I'm sure they are links though)
    6. The colorization - are there tints applied to the object colors, or are they 100%?

  • Submit Bug?

    Doesn't seem to be any easy place to just submit a bug report, so I thought I would just post it here thinking a moderator would submit it for me.  I found an unusual flaw while working with images in Illustrator.  Wondering if everyone else sees the same as I do.  If you follow these steps exactly, you should see what we see.
    1) Create an image file (RGB, CMYK or Grayscale, doesn't matter), and save it (PSD or TIFF, doesn't matter).
    2) Create a new CMYK or RGB document in Illustrator CS5.
    3) On the default layer (normally called "Layer 1"), "Place" the image you created as a "Link".
    4) Create a shape and apply it as a clipping mask to the linked image.
    5) Create a new layer (by default it's called "Layer 2").
    6) In a different location, "Place" the image you created as a "Link" again.
    7) Make another shape and apply it as a clipping mask to the second linked image.
    8) Save the file as an AI or Illustrator compatible PDF (doesn't matter).
    9) Close the file and reopen it in Illustrator.  You'll notice that the artwork appears to be what you created.
    10) This time, lock the bottom layer, which should be called "Layer 1".
    11) Save the Illustrator file, and close it.
    12) Reopen the file and look at your images now.  You'll notice in the "Links" window that there's more images than you originally placed, and at least one of the images is in the wrong location.  You will probably see three images when you had only placed two, and one of the images has a white preview in the "Links" window.
    *This is the main flaw of the program.  It only happens when the same image is placed on two different layers and only when the bottom layer is locked.
    **After step 12, if you unlock "Layer 1" and save/close the file, the next time you open it, the images appear normal again.  However, it still leaves an extra image in one of the clipping mask, which you can identify from the "Links" window.
    ***When saving the file as Illustrator PDF and this problem occurs, the document appears accurate when opened in Acrobat, even though it is not correct in Illustrator.
    Give it a try and let me know if I'm crazy here!  Must fix this problem!!!!  Thanks all!

    Hopefully you can see from these screenshots.
    Here is the normal AI file with the links on two separate layers and the layers both unlocked.
    This is what happens when we lock the bottom layer, save and close the file, and then reopen the file. 
    We are using MAC version, and it occurs on both of our MAC's, two different OS.  We do run Esko Plugins, so if you don't see the same thing we are, I will be submitting a support ticket with them next.  I really appreciate any other confirmations.  Thanks much!
    I have this sample file, the image file, and a PDF of my screenshots in a ZIP file which can be downloaded HERE.  Just open the AI file, lock the bottom layer, save and close, then reopen the AI file.

  • Convert "Grayscale I16" to "RGB U64"

    Hello, 
    I need to convert an image from Grayscale I16 to RGB U64, but it doesn't work (I have joined a zip file).
    I think there is a bug in the NI Vision, or it's not implemented because I have no problem to do it from Grayscale U8 to RBG32. 
    Can you help me to find a solution to do that? 
    I need to use ReplaceColorPlane function or equivalent because I have to perform various treatments on each layer (RGB).
    Thanks
    Solved!
    Go to Solution.
    Attachments:
    tests.zip ‏217 KB

    Hi Badgones73,
    The U64 image is composed of four U16 values (R, G, B and alpha). LabVIEW represents 16-bit images as an I16. When the IMAQ Extract Color Planes is called, the U16 value must be converted into I16 values. This is done by converting all values with a MSB of 1 to a value of 0. This means all the values from 32,768 to 65,535 are now 0. To avoid using losing these values, you must read the image into LabVIEW without using the vision functions.
    Once you have extracted the U16 values, they can be converted from U16 images to I16 images. Once this is done, you will be able to use all of the Vision functions.
    Also, i invite you to read the information on our website:
    How Do I Convert a Color Image to Grayscale?
    http://digital.ni.com/public.nsf/allkb/ED42C55C29B9B34C862570A60079952E?OpenDocument
    Regards,
    Rémi D.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> Les rencontres techniques de NI - Mesures et acquisition de données : de la théorie à la mise en ...

  • Iphoto 9.6 rotation of grayscale images

    If I import grayscale images into iPhoto 9.6 (under Yosemite, in this case) (either Tiff or JPEG, 8- or 16-bit), iPhoto corrupts the images if I rotate them in iPhoto.
    To see it happen, I merely:
         Create a grayscale image (I use vuescan, but it will also happen if I save an image out of Photoshop CS6 as grayscale).
    Import it into iPhoto 9.6
    Rotate it (command-R).
    Now either toggle between thumbnail and full-size view or edit the image (again, I use photoshop here).
    The resulting image will be corrupted (probably either all-black or all-white, but it can show up other ways as well).
    Anyone else have this problem? The workaround is to import RGB files, but of course that's not ideal if your source files

    Thanks, Leonie; these are indeed taken with a photographic camera, but are single-channel. Previous versions of iPhoto have had complete support for grayscale images, and this version attempts to do the rotation but corrupts the image, so I interpret that behavior as a bug, rather than one of no support.
    Have you really been able to work with single channel gray scale images?  I know, that iPhoto and Aperture can work with gray scale images, as long as the gray scale is part of the color profile or an EXIF tag, but at least in Aperture you cannot do much with single-channel images, other then import and export them, or view them. The same goes for PSD files, or any file format with alpha channels and layers. As soon as transparency is involved, it cannot even be displayed correctly. That is even mentioned in the technical specifications. http://www.apple.com/aperture/specs/
    Aperture maintains but does not display layer and alpha channel information in PSD files.
    I suspect, that iPhoto has the same limitations, because both applications are sharing code and the unified photo library format.

  • PDF export in Grayscale or BW

    Hello,
      WeI have notice that PDF export from CrystalReports XI creates black color with Cyan, Magenta, Yellow and black color (ex. cyan 70%, Magenta 68%,  Yellow 68% and black 90%, if you check for color separation in Adobe Acrobat prof.). So we have a big trouble with this export (for our partner black color must be black not generated with other colors). Is there any way to force PDF export to export in BW or grayscale??
    Best regards,
       Robert
    Edited by: RobertR on Nov 20, 2009 10:41 AM

    Yes, I created a new report with only ONE text object (in page Header section). 
    Font properties are:
      Font Arial, Style Bold, Size 22, Color Black,
      everything else is set to default.
    When I run export (in crystal reports) Ii get the result that black color is not black (generated with help of Cyan, Magenta and Yellow). If I print that report to PDF printer (primoPDF) I get a black color. PrimoPDF has some setting how to create PDF (must be black and white printing). The most interesting is PDFCreator (printer) which creates black color on color printing.
    To me looks like nasty bug in export to pdf module. It looks like every PDF export is generated in color.
    Any other ideas???

  • Exporting as grayscale PDF

    I am using WinXP, InDesign CS2. Whenever I design a document, with all grayscale objects, and I want to export as a pdf. The document becomes RGB. It need it to stay a true grayscale. How do I make this happen?

    In my understanding - I'm not a native English
    speaker - the word Grayscale refers mainly to gray
    raster images which were saved by one channel.
    I had copied some text from a Word file (trying to
    identify the source of the bugs) and pasted into a
    new ID doc.
    Then I had used Export to PDF with 'No Color Conversion'.
    According to 'Output Preview' it's a K-only file.
    Loaded in Photoshop as CMYK it appears as 100% K-only.
    Loaded in Photoshop as Grayscale it appears by a
    CMYK-interpretation in the Info Palette as a 4-plate
    'rich black' file - obviously a misleading interpretation.
    Alternatively I had used Print as Composite Gray to PDF.
    The result was the same.
    In my humble opinion it would be very helpful to use
    the word 'Grayscale' only for gray raster images.
    Vector graphics and text may be gray, but they should be
    defined by CMYK = 0 0 0 K.
    Sources from Word had caused trouble in the past (but not
    in the actual test). Anyway - the text can be selected and
    converted into K-only.
    For further discussions it would be useful to explain, by
    which tools the final PDF had been interpreted (e.g. Photoshop
    or Acrobat Pro or Quite a Box of Tricks).
    Peter,
    good points: Text as Black, and the accurate measurement.
    In Photoshop one needs one-point-sampling instead of averaging.
    Best regards --Gernot Hoffmann

  • Missing Grayscale profiles for export

    I have began to use LR2 for my scanned B&W images. When I export them, the only profile choices are color profiles. So I click Other..., a window pops up with the text "Choose profiles to appear in Custom Profile popup:"
    But there is no way to choose profiles - the only option is "Include Display Profiles", which is not what I want - I'm looking for Gray Gamma 2.2.
    So I have to export with a color profile, then convert back to Gray 2.2 in Photoshop - not excactly non-destructive.
    I'm not sure if this is a bug or a feature? Or am I missing something?

    > ... Am I correct, from your postings that you must export in color to Photoshop CS3, ...
    You can create the grayscale image in Lr, but realise that it is still a RGB image, and only Ps can convert it to a "true" grayscale" image. Also realise, that the 2 are entirely equivelent, even if the RGB image file size is 3x larger. Therefore, a RGB grayscale with sRGB embedded is absolutely equivelent to a grayscale image with the "gray 2.2" profile embedded.

  • Exporting to jpeg with grayscale images on the page crashes Indesign

    Hi,
    I have noticed a bug in Indesign CS4.
    When I have grayscale psd images on a page the export to jpeg crashes.
    - R

    That's been happening to me too, but I didn't realize it was just the grayscale .psd causing it, since I never use the feature in the real world and was only trying to confirm a posted behavior.
    Report it here: http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

  • Bug Fix Lament

    Adobe: It does not bode well for Lightroom to have relatively-easy-to-fix bugs persist, release after release.
    I highly recommend finding a way to get more of them out between releases.
    In my opinion, one should almost be able to assume certain bugs are not there since they were reported well in advance of latest release - just like we can assume certain popular new cameras will be supported...
    If I remember correctly, there was precisely one item on the "known issues" list of the 3.3 release - hiding them does not make them go away.
    Rob

    Lightroom 3.3 Bugs Fixed below (these are probably the major bugs, and there may be many more minor ones not listed).  It would seem that they weren't exactly sitting on their hands.
    Bug fixing is about priority and risk.  If a bug fix has a high risk of creating other bugs and a low priority because of few users affected or easy workarounds, then it might be better to leave it alone.  It's also possible that bugs that seem easy to fix actually require a near entire rewrite of entire sections of code.
    Edit in PS CS4 from LR 3.2 did not give option to render to TIFF/PSD
    Process Version defaulted to PV 2003 when Lightroom’s installed Develop Presets are applied on Import
    All Auto-ISO values were not properly handled for the Nikon D3s
    An error could be generated when sorting by “User Order” in Collections
    There was an incorrect Profile Name tag for Canon 18-55 and 17-40 lens profiles
    Facebook album selection only displayed up to 25 albums
    Lightroom 3 could fail to launch Photoshop CS5 if Photoshop CS4 was uninstalled after the Photoshop CS5 installation
    Numerous cloning or healing spots could have caused Lightroom to become unresponsive
    Lightroom could have crashed when the metadata filter is selected and the grid is displaying all images in the catalog
    Lightroom 3.2 could have failed to import all of the images from an iPhone 4
    Some Sigma X3F raw files were rendering incorrectly
    Choosing the “Make a second copy to” option on import would result in incorrect folder structure for the second copy
    Resetting the crop angle by double-clicking the Angle slider removed a custom aspect ratio
    A tooltip for the Japanese language version of Lightroom 3 displayed the wrong keyboard shortcut for “Flag as Pick”
    Paste Settings did not apply to all images in the Develop module Filmstrip
    Smart collections in Lightroom 3 did not use the same definition of  “All Searchable Metadata” previously available in Lightroom 2
    Text watermarks or portions of text watermarks could have failed to be applied to images on export
    SmugMug publish collection dialog included a mixture of English text  when using a language setting other than English
    Lightroom would not import files from the Panasonic LX5 that were shot with the iZoom Function set to above 90mm
    Choosing the Limit File Size option in the export dialog could have stripped certain EXIF fields from the exported file
    The Targeted Adjustment Tool may have performed slowly in the Lightroom 3.3 release candidate
    A single image published to multiple collections for a single publish service did not display comments properly
    Updating an existing Develop preset with all settings could have failed under certain conditions
    The watermark drop shadow settings behaved differently in Lightroom  3.2 when compared to Lightroom 3.0.  They have been returned to the  Lightroom 3.0 behavior.
    The YYYYMMDD file renaming option was not available when the Lightroom language setting was set to Dutch
    An existing Smart Collection updated to filter for all photos with “Ratings is Zero” would show all images in the catalog
    Publishing an empty category to SmugMug would cause an error
    JPEG exports in the Lightroom 3.3 Release Candidate were significantly slower than the same export process in Lightroom 3.2.
    A graphical Identity Plate included in output was not correctly color managed
    Deleting all images in a Flickr photoset could have caused Lightroom to return an error message
    Changing the sort order to “User Order” while in Survey View on the Mac may have caused an error to appear
    Lightroom could have failed to respond when viewing an image containing numerous cloning or healing spots at 1:1 view
    RGB values were not displaying properly in the white balance tool
    The Smart Collection criteria “Folder starts with” was not working properly
    The navigator panel in the Develop module would incorrectly display  threshold information when holding down the alt or option key and  applying adjustments
    Applying a flag, star or label setting to an image via the toolbar  in the Develop module while in auto-advance mode would result in an  incorrect setting display for the subsequent image
    The application of color noise reduction at low color temperatures  (e.g., tungsten or candlelight) could have provided results below our  quality standards

  • New photoshop cc seems to have a bug wrt the toolbar's foreground and background squares.

    New photoshop cc seems to have a bug wrt the toolbar's foreground and background squares. When I pick a color to use as a fill the squares show gray and the fill is gray rather than the color picked. Never had a problem with this in previous version of PS. Could something be set up or initialized to cause this state of affairs?

    Change your document from Grayscale to RGB, or change the selected channel to the RGB data instead of a mask.

  • Watermark bug in DVDSP 4.2

    I need to bug a project with a logo... I can get the logo into the project as a .tif or .pict (grayscale), position it on the subtitle track, force it to stay there, etc. The problem is during the build... it gives me this:
    Starting DVD Build ABC...
    Compiler Initializing...
    Precompiling Project ABC
    Compiling VMG Information...
    Created 8 PGCs in VTSM1
    Created 8 PGCs in VMG.
    1 Menu(s) will be created...
    Compiling Menu PGCs...
    Compiling Menu#1 (Menu 1)...
    Rendering Menu:Menu 1,Language:1...
    Generating Transition: VTSM #01, VOB #1...
    Writing VIDEO_TS.VOB
    1 VTSs and 1 Titles will be created...
    Compiling VTS#1 (FF 217)...
    Preparing Subtitles...
    Muxing VTS011.VOB
    Video File Read Error
    It's a simple project with an m2v and an aiff file at an acceptable bitrate.
    Any successes? Please don't suggest I bug and render a 30 minute series style program in FCP!
    Thanks!

    Try changing the audio to AC3 as an aif. Also do you have any other subtitles (you may be going over total rate for the track it sounds like) What was your video encoding rate?
    Lastly, you may be better off using either Final Cut or Compressor when encoding to m2v to add a watermark as oppossed to the subtitle method, not sure if you are worried about people removing the watermark or not.

  • Very Minor Bug 1.4.1 Presets & Sync

    Probably more of an oversight that a bug in 1.4.1. Color Noise Reduction setting is not available (no check mark) when saving a preset or syncing when you are doing it from a grayscale image. Probably something left over from the previous version that did not allow Color Noise Reduction in grayscale images.

    Color Noise Reduction settings are available for grayscale images in the Lr2 beta.

Maybe you are looking for