Major BUG in DNG conversion of Fuji x100s raw files.

I use an imac with latest os10.8.4 and I converted RAF =raw files from fuji x100s to dng format with DNG Converter 8.1.0.43.
I have never seen such a horrifically bad problem in 15+ years. PS user of very long time.
I attached 2 image files to the problem given by another member who was trying to use xrite.
I am posting here as it is a problem of interest to anyone who is using the x100s or considering it.
http://forums.adobe.com/message/5634178#5634178

The compatibility options are really to indicate which version of ACR you intend to use to read the raw file.  Then the DNG Converter can decide whether it needs to do any additional processing to the file so that the (older) version of ACR can read it properly. 
In the case of the Fuji X-Trans sensor with its 6x6 mosaic pattern (which requires a specialized interpolation routine for high quality results), the key distinction is whether DNG Converter performs the interpolation routine, or the older version of ACR performs the interpolation routine.  If you choose "Camera Raw 7.1 and later" compatibility, then you're indicating that you plan to process the image using Camera Raw version 7.1 or later (e.g., ACR 7.4, ACR 8.1, etc.).  These newer versions of ACR contain specialized interpolation routines for the X-Trans sensor, so the DNG file that is produced with "Camera Raw 7.1 and later" compatibility will be stored in the original mosaic form.  When you read these files in ACR 7.1 and later, the specialized X-Trans interpolation routines will be used to process the files.
If you choose "Camera Raw 6.6 and later" compatibility, then you're indicating that you plan to process the image using CR 6.6 and later (e.g., ACR 6.7, ACR 7.0, ACR 7.1, etc.).  Some of these older versions of ACR (such as ACR 6.7) do not have specialized interpolation routines for the X-Trans sensor.  The DNG Converter understands this, and therefore performs the X-trans specific interpolation itself to produce linear RGB data, which is then stored into the DNG.  So, the DNG file produced in this case does not contain the original mosaic data, but instead contains interpolated linear RGB data.  The older ACR versions (like 6.7) can open this linear RGB data in the DNG directly, without having to perform any specialized X-Trans demosaicing (remember, this is important, because ACR 6.7 doesn't contain that specialized logic).  This is also why the DNG files in this case are significantly larger in size compared to the images in the first case: they contain linear RGB data (3 color channels) instead of mosaic data (1 channel).

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.

  • Fuji x100 RAW compatibility?

    I read on the Aperture 3 support page that it supports Fuji x100 RAW photos.  But when I just imported some, while it showed thumbnails during the import process, when the images themselves were imported, each and every one showed as a black box saying "unsupported format."
    Any advice?
    Thanks
    jhbeckman

    What version of Aperture and what version of the OS?
    The Fujifilm FinePix X100 ws included in Digital Camera Raw update 3.7

  • Fuji RAF (raw) files

    How do I use Fuji RAF (raw) files? What file do I need to download for my Photoshop CS5?
    Message was edited by: backlash2

    This is for the benefit of others who might find this thread.
    There is a list of the latest Camera Raw versions that can be used with a particular major release of Photoshop or Photoshop Elements here, in the Camera Raw FAQ:
    http://forums.adobe.com/thread/311515?tstart=0
    The Camera Raw versions listed in the FAQ (e.g., Camera Raw 6.2 for Elements 8) are the latest that can be installed in a particular editor version. 
    If that Camera Raw version is lower than the one listed at the link Trevor supplied above, then you'll need to either use the free DNG converter to convert your files to the DNG format before opening them in your image editor, or upgrade your image editor.
    -Noel

  • Proper support for Fuji EXR Raw Files

    There is still no proper support for Fuji  EXR Raw files.  On any Fuji X-series camera, the in-camera raw processing, including specifying options always outputs a far superior image that Adobe Camera Raw 6.  I've been using an X100 for some time now, and have really gathered some great images with it. But Adobe Camera Raw fails miserably to understand how to process these files.
    This is more of a complaint and feature request than a question, because I already know the answer. Adobe has not worked close enough, or at all, with Fuji to develop a Raw processor for the EXR pixel layout.
    The EXR pixel arrangement offers new possibilities, especially the ability to take an HDR image of a moving subject, and without a tripod. The elimination of the low-pass filter allows for more sharpness, and finally the noise pattern is much more "film-like".
    I've been using Adobe Photoshop for processing images for years, but have no compelling reason to upgrade without a proper conversion for Fuji RAW files.
    Adobe: Please work with Fuji to bring world-class support for EXR Raw images.
    Thank you,
    William

    Good day!
    Adobe has not worked close enough, or at all, with Fuji to develop a Raw processor for the EXR pixel layout.
    There seems to be a reason why Adobe has to reverse engineer RAW formats – the camera manufacturers don’t want their customers to use Adobe (and other) software to process their RAW files. (If their proprietary software gets better results then that’s understandable, but for how long are they going to support their own software?)
    Now maybe Fuji is more cooperative than others, but do you know that for certain?
    I've been using Adobe Photoshop for processing images for years, but have no compelling reason to upgrade without a proper conversion for Fuji RAW files.
    If the new/improved features of Photoshop CS6 have no significance for the way you process, manage, edit and touch-up photographs feel free to stick with whatever version of Photoshop you use currently, but be aware that hardware/OS changes on your side may some day make that version inoperable on your set-up.
    Also the upgrade path has been cut down to one version, if I understand correctly.
    Anyway, this is a beginners Forum, feature requests might be better posted over at
    http://feedback.photoshop.com/photoshop_family
    Regards,
    Pfaffenbichler

  • Elements 10 and Fujifilm X100s raw files.

    Hi! How can I make Elements 10 to open my Fujifilm X100s raw files?

    As far as i know pse 10 will never be updated to open the FinePix X100s files since the camera is pretty new and even pse 11 won't open them until the new version of camera raw 7.4 ships.
    However you could download the
    DNG Converter 7.4 Release Candidate
    and convert your X100s files to dng copies which pse 10 should open in the pse 10 editor.
    It's very important that you get the DNG Converter and not the plugin (the plugin won't work in pse 10)
    http://labs.adobe.com/downloads/cameraraw7-4.html

  • Fuji XT1 RAW files

    Has anybody any idea how soon Fuji XT1 RAW files will be able to be processed in Aperture 3

    In the meantime let them you know you want the support by going to Apple - Aperture - Feedback
    Don't know if it helps but can't hurt.
    regards

  • Fujifilm X100s RAW file (RAF) support in Aperture

    Any chance of an ETA for Fujifilm X100s RAW file (RAF) support in Aperture?

    To download here:  Digital Camera RAW Compatibility Update 4.05
    as Update 4.05 to Aperture 3
    that is a bit ambigous - reads like the long yearned for release of Aperture 4

  • Fuji X100 RAW conversion

    Hello all,
    I have noticed that the RAW files from the Fuji X100 when opened in Aperture (v. 3.5), compared to the in-camera processed JPEGS:
    1) are significantly more saturated, especially in the BLUE channel (but also in the red one)
    2) show a noticeable vignetting
    3) show chromatic aberration (while the in-camera JPEG don't)
    Did anybody else notice that?  It seems clear that Aperture does not correct for vignetting and chromatic aberration (which is NOT good), but also tends to blow out the saturation for the blue....
    thanks for any comment
    giuseppe

    What should be have been changed, Leonie?
    The over saturated colors. I did not expect lens correction to be added by a simple raw compatibity update, but we have seen problems with oversaturated colors been caused by faulty raw updates, for example  Camera Raw update (4.08) : 
    See My 2012 iMac is on acid NEF files stopped being displayed on iPhoto and Preview, and all pictures are turning red in my library for examples.
    This problem was fixed with Camera Raw update (4.09), but it may have introduced a problem with oversaturated colors, as seen in the examples above, that is why I have been asking -hoping that a new raw compatibility update might solve any such problems.

  • DNG Conversion for Fuji X-Pro 1

    I just tried the new DNG converter from Adobe to convert the Fuji X-Pro 1 files into DNG and then import into Aperture.  I just did this recently with the D800E and I didn't have any issues.  This was before Aperture support the D800E files.  The X-Pro 1 files however still come up unsupported.  Does anyone have any idea what I might be doing wrong or why?

    I'd recommend reading Apple's article on baseline DNG support. Like the Foveon sensors mentioned in the article, the X-Pro1 uses a sensor very different than the Bayer sensor used in 99% of digital cameras. There's no telling when or if Apple will support X-Pro1 raw files.
    —Andreas

  • Home view major bug: Home view navigation not available in Common File Dialog Box (i.e. Java, Adobe Photoshop etc)

    Homeview major bug: Homeview navigation not available in Common File Dialog Box (i.e. Java, Adobe Photoshop etc)
    Hi
    All though provisioning somewhat more flexsible and pointing forward ... things are starting to go wrong here ... i.e. pointing to a very potential lack of success introducing users to the new Home namespace/concept ...
    0) Situation if you do not fix 1 + 2:
    You can not release the Homeview feature like this - without fixing 1 + 2.
    If not 1 +2 is fixed you might just as well leave the release of the Homeview feature out of the roadmap for Windows 10. I.e. not ready for use ... or promotion in the UI
    1) How come Homeview has not been included - like other namespaces i.e. Libraries into the Common File Dialog Box?
    How can such a trivial thing to do be missed? I.e. like forgetting to include Homeview into Explorer (would be absurd).
    If not included into the Places Bar of the Common File Dialog Box ... Home View will be unusable - because some very visible applications like Java, Photoshop will not be able to navigate that space easily at all.
    2) Finally, please fix obscure situation in the UI namespace in Explorer
    Please fix obscures like having Home view, Favorites and Libraries (side-by-side complexity and confusion obscuring usability) - all similar concepts but on a different evolutionary step. I.e. have Favorites and Libraries
    hidden - and add i.e. view control like to small buttons whatever to unhide/show the legacy concepts.
    In any case - Home view already seem to migrate/move links from Favorites to the Homeview container.
    Additionally, Home view should migrate links from Libraries to Home view - and provide similar and better functionality.
    Thus going the evolutionary way from Libraries > Favorites > Home - with the later concept of Home providing links to the cloud. Even better, sync relation ships could then later (extended features for Home) be set up among the pins - i.e. concerning
    cloud/network syncing.
    The UI should always reflect the 1 essentional concept - and not under the hood technologies or different evolutionary stages of the same basic/essential concept (technology/implementation free - abstract: "Home with pining of user data space"
    - was previously favorites or libraries (thus obsoleted)). Now the name for that concept is Home. Have it include the technology that replaces Libraries too - i.e. categorization/nesting ... and some whitespace inbetween the nesting (alike some whitespace
    already there inbetween the namespaces in the Explorer UI ... provides easy "modular" reading)

    Hi,
    Please clarify the following:
    * "X: is a network drive, but it's actually a network drive on my machine." - Is "X" a mapped drive to one of your shared folder on network?
    * What is the project directory structure with respect to WEB-INF/web.xml? Are you able to see the three pages (from web & pages folder) in NitroX Editor?
    * Does the modified content appear in "Design view" of index.jsp upon restarting NitroX?
    Ex:
    - modify one of the pages in "web" folder > save the file (alert appears)
    - restart NitroX, does index.jsp display the modified content of included page?
    * If possible please send the test case project which exhibits the behavior to [email protected]
    Thanks,
    M7 Support

  • Fuji X100 raw support ?

    Fujiguys on twitter indicate that there is no plan to bring X100 (.raf) raw support in Aperture, but only to 3rd party Mac software. Why that ? Does Apple has plans to bring this support to Aperture users ?

    I hope Apple and the other lot get their act together soon.
    I believe Fuji has to make the specs available first in order for others to support the format. And although it was announced back in September, those specs weren't final until the first production units started shipping - this month. From what I've seen and read the Silkypix based software that comes bundled with the camera is far from perfect - I've seen serious problems with highlights on one example. So for me it's a question of getting it right and not simply getting it out the door.
    I agree the jpg's from it are impressive, but they don't give you the raw file.
    Totally agree with you. To me, shooting JPEG only is like throwing away negatives. But it's nice to know they've done such a good job internally. It makes the camera that much more interesting and the wait a little more bearable. RAW+JPEG a must though.
    This camera is a game changer in the bigger scheme of things, and will be used by a lot of influential photographers.
    Looks that way but time will tell. I for one am totally sold and can't wait to pick up my pre-order. I haven't been this excited about a camera in a long time.

  • Fuji x100s RAW photos

    Please could someone tell me how to get Elements 11 to accept RAW photos from my Fuji x100s? KentishRob

    Hi,
    Have you updated your Camera Raw plug-in?
    In the editor, go to Help -> About Plug-in -> Camera RAW
    You need version 7.4
    To update, got to Help -> Updates and that should download and install the updates.
    If is still doesn't work, please tell us which operating system you are using.
    Brian

  • Fuji X10 Raw Files

    Is it posible to find out if Apple intend issuing an update to Aperture 3 to process Raw files from a Fuji X10 camera.

    Yes, you will lose a lot of resolution by using Adobe DNG or any other third party Raw Converter.
    For best results, use the in-camera Raw Converter.
    I suggest that you read and digest the following:
    The dpreview Fuji X10 Review
    http://www.dpreview.com/reviews/fujifilm-x10/
    Extract;
    We appreciate in-camera Raw conversion in any camera, but with the X10, this control is absolutely crucial. Why? Because third party support for the X10's raw files is far from universal among the more popular raw converters on the market. And even worse, among the raw converters that do support the EXR sensor, the results are disappointing.
    The inevitable downside to a non-standard sensor design is that it requires a different set of demosaicing algorithms for optimum results. In the raw converters we've used - including the SilkyPix version that ships with the camera - image resolution and fine detail are significantly worse than the X10's in-camera JPEGs. The converted Raw files appear very soft and are clearly not displaying the best image quality the sensor can produce. You can see this for yourself on both the Raw mode and studio comparison pages of this review. As it stands, you get significantly better image quality in terms of sharpness and resolution from processing Raw files in-camera than you do with external software.
    Try using the X10 settings recommended in this article:
    http://www.dpreview.com/articles/9060476058/fuji-x10-exr-camera-suggestions-for- optimum-performance.
    Regards,
    iPentax

  • Raw conversion: open EOS 70D Raw files in Elements 8?

    I have a Windows 7 operating system, and Photoshop Elements 8. I have a new Canon EOS 70D and want to find
    an adobe Raw converter which will allow appropriate processing, and connecting finished results to Elements 8 for conversion  to routine JPeg or PSD? Any reccomendations?

    The EOS 70D was first supported in Adobe Camera Raw (ACR) 8.2
    http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    ACR8.2 is only compatible with Elements 11 and 12. Not Elements 8 so you cannot open Raw files from the 70D in Elements 8.
    Your choices:
    Upgrade to Elements 12, OR
    Download the free Adobe DNG converter and convert all 70D Raw files to DNGs. That adds an extra step to your workflow each time you shoot more pictures. Then edit the DNGs in Elements 8.
    http://www.adobe.com/products/photoshop/extend.displayTab2.html

Maybe you are looking for