DNG/RAW file type problem

I routinely download and convert my files to dng.
The Metadata Browser correctly identifies these as Digital Negative (DNG) - at least for files downloaded by LR 1.0 and LR 1.2. However, files downloaded by LR 1.1 seem to be identified as Raw even though the file extension remains .dng.
Can someone please tell me how change Raw back to DNG?

First, save all metatdata to the DNG files (Ctrl+S).
Second, remove the images from the Lr catalog. Do not delete from disk, just remove from the catalog.
Third, import the DNG files. Set Develop Settings and Metadata to None in the import dialog.

Similar Messages

  • Plans to enable import of Cinema DNG (RAW) files from the Blackmagic POCKET Cinema Camera

    Are there plans to enable import of Cinema DNG (RAW) files from the Black Magic POCKET Cinema Camera into Adobe Premiere Pro CS6?

    There won't be any new features introduced in CS6, only some bug fixes if ever. All new features go into CC. Rumour has it that Camera RAW will be added into PrPro (sooner or later).
    Off topic question: have you tried to convert BMPCC CinemaDNG files into DNG via Adobe DNG Converter? Resulting files are about 15% larger, so I hope that is what constitutes uncompressing them and making possible to import into PrPro CC natively (I'm not on CC, hence can't test, but I'm curious).

  • CS1 and CS2 InDesign file type problems and Tiger

    Dual 2.7GHrz G5, 2GB RAM, OSX 10.4.5
    Previously, InDesign 3 (CS1 version) was installed on this Mac. I needed to install the full CS2 package. Everything installed just fine. The problem I am having is the file type associations. The Mac now sees CS1 InDesign files as Indesign CS2 files. I got info on a file I knew to have been created and saved in InDesign CS1. I changed the "open with:" to InDesign CS and it worked until I hit "Change all". It then reverts back to a CS2 file type. On other sites I found some different things to try like rebuilding or deleting the LaunchServices pref files, checking to see if their was a CFBundleIdentifier, etc. Anyway, what I seem to have found is that Tiger gets confused when the Type and Creator are the same in the info.plist files. Panther, however, does not seem to have this same problem. We have 10+ other G5's of similar hardware specs as the one listed above, running Panther 10.3.9, have CS1 and CS2 installed, and we are not having the same file type problems.
    As a test, I modified the CFBundleIdentifier to be different than the one found in the CS1 info.plist, and it let me "change all" the CS1 files to CS1. Of course, CS2 files could not be associated with CS2 now.
    Is there a fix for this? Or, is there a patch being worked on that will fix this problem? We really need to keep both versions of the software installed, and I don't want to have to rely on users making the decision about what version they are working in.
    Tom

    If Get Info shows both app versions (& it should) as "Open with:" choices, you can at least still set individual docs to open with the preferred version. Instead of having to open Get Info windows, you can do the same thing a bit more easily with the contextual menu that pops up when you right (or CMD) click & hold on a Finder document icon.
    Normally, the "Open with >" choice in this menu is a one time thing, but if you hold down the option key, it changes to "Always Open With >" & makes the new app choice permanent as it opens the doc, all in one step.

  • Preview has taken over RAW file type binding from Photoshop

    Preview v 3.0.4 has taken over as the default program with which to open RAW files. Double-clicking a RAW file in OS 10.3.9 or earlier (?) used to automatically open RAW files into the latest Photoshop version installed (be it 7, CS, CS2).
    After purchasing a new Dual 2.7 G5 with Tiger 10.4 or 10.4.4, ALLL RAW ICNS have changed to a PREVIEW.app's icon for RAW images, and RAW files now default to Preview when double-clicked, instead of the Photographer's choice of Photoshop, as it has been for years.
    These and other file type bindings (PDF) have been captured by Preview in the new OS.
    What is going on? What to do? How do I regain the original file binding of RAW files to an intelligent and professional program (PHTOSHOP CSx), instead of this NEWBIE nearly unusable PREVIEW application?
    Simply remove all PREVIEW resources? Then it's usefulness for browsing large numbers of images will be lost.
    I simply want PREVIEW to leave my professional digital world alone and let me continue working efficiently.
    Any help? Ideas?
    Thanks a bunch,
    jes360

    Simply select one of your crw files, do GetInfo (command-i) on the file and in the Open With section choose Photoshop. Click the Apply to All button. From now on all crw files will open in Photoshop. I suspect the default changed because Preview can now open many many raw files, and not everyone has Photoshop.
    Francine
    Schwieder

  • Raw file rendering problems with Canon EOS 5D in Aperture 3

    Since upgrading to Aperture 3, I have had serious problems with the rendering of Canon EOS 5D (not Mark II/III) RAW files. With Aperture 2, both the preview and full-sized images looked basically the same as the original images as displayed on the camera's display, without any adjustments.
    With Aperture 3, each preview images initially look fine after import, but when Aperture re-renders it from the RAW file (e.g. when displaying the full-size image), the colors are drastically intensified, and the hue is shifted generally towards green/blue. I've checked the RAW Fine Tuning, and it is set to the defaults. If I turn the default RAW Fine Tuning settings all the way down, the image is still not at all like the preview from the camera - it becomes much darker and stays too blue/green, with washed-out colors.
    A friend with a Canon EOS 5D MkII also recently upgraded her Mac from Aperture 2 to 3, and hasn't experienced any problems. We've tried importing RAW files from my (non-MkII) camera to her Mac (with the default RAW Fine Tuning settings), and get the same results as with my own Mac (i.e. strange colors), so the problem seems to be related to the camera model.
    I've also noticed that scanned greyscale tiff images (including images that were originally imported under Aperture 2) are changed when first displayed by Aperture 3 - they become darker and more contrasty, with lots of information lost in the shadow areas.
    I've also tried removing Aperture preferences, Aperture itself, and re-installing from download, with no change in the problem. (Aperture is the current latest version, 3.3.2.)
    Has anyone experienced similar problems?

    I'm having the same problem.
    iMac running Mac OS X Lion 10.7.4 and Aperture 3.3.2.  Workflow is importing through Canon's DPP and then using referenced images in Aperture.  The images look great in LR4, or Canon's DPP but are flat and dingy in Aperture.
    There's a free preset that goes part way to fixing it at http://theapertureblog.com/2011/02/10/my-aperture-workflow-for-working-with-cano n-5d-mark-ii-files/
    but as good as this fix is, it doesn't quite do the trick. [not being a hater, and not saying I can do better]
    I just got back from shoooting 1,500 images with a 5DMii and a T2i using Canon 24-105L IS, 70-200 2.8L, 50 1.8 and a Sigma 120-400 and the T2i images are not just better, they're in a different league.
    I've tried shooting in Faithful, Neutral and also toggling these presets in different ways and still can't get Aperture to match what I see on the camera's screen or in other Apps.  I love the interface and DB of Aperture, but what's the point of using it if it doesn't produce and awesome image in the end?

  • Olympus RAW Files Preview Problems

    Hi,
    I have started using Lightroom as my photo editor and organiser and have taken on board the advice to convert RAW files to DNG. Unfortunately I have discovered that Finder (I operate an IMac, Mavericks 10.9.2) will not preview these DNG files. I use an Olympus EM1 and have been reliably informed that Apple does not support Olympus RAW files converted to DNG, but they do support Canon and Nikon. I would appreciate everyone's support in trying to get Apple to recognise Olympus and I would be grateful if you would take a few minutes of your time to copy the following few sentences and post them onto the Apple Feedback web page, which I have also provided. Thanks in anticipation.....
    "Hello,
    I use an Olympus camera and convert the RAW (ORF) files to DNG in Lightroom. Unfortunately Finder preview does not preview these files, although I believe that Canon and Nikon camera files are previewed. Would it possible for Apple to enable previews in Finder of Olympus RAW files converted to DNG?
    Thanks."
    http://www.apple.com/feedback/macosx.html

    In PSE 11, have you checked whether you have the latest plugin for your camera?  If not then it is not a bad idea to do it now by going to:
    Help >> Updates
    You may also want to check if the files are saved in your default location normally "MyPictures" in XP or in Libraries >> Pictures in Windows 7 machine.  See this picture:
    Hope this helps if not please post back explaining clearly what do you see on the screen.
    Good luck.

  • BSD file type problem install

    Using my Cube's internal DVD I am trying to install Tiger 10.4 (full install disc) on to an external 80G HDD connected to the Cube by firewire.
    The disc check finished and the install starts, but instead of a successful install I get a report of an "error" and asked to restart.  Upon restart I first run Disc Utilities to verify the HDD and get --
    Invalid BSD file type
    Volume Bit Map needs minor repair
    The Volume Cube-1a (HDD name) needs to be repaired.
    -- all these on a brand new, just partioned & checked, HDD
    What is happening here - Faulty install disc ? Faulty HDD ? Faulty computer ?

    I'm thinking jumper settings. Here is an article on upgrading a Cube hard drive:
    http://cubeowner.com/kbase_2/index.php?page=index_v2&id=132&c=5
    Note it says "cable select" is not appropriate for Cubes, and that most new ATA drives ship preset to cable select.
    That entire site is devoted to the Cube. Probably some good stuff there!
    AJ

  • Camera Raw file download problem

    Downloaded Camera RAW Images recognised in PS5 Bridge prior to download (thumbnails visible) but after download, no thumbnails visible, only icons, which when double clicked, the following error message appears "Could not complete your request because Photoshop does not recognize this type of file".
    Other previously downloaded files can be opened, and a test picture I just took, downloaded and opened up fine. Looking at the files that won't open, I noticed that the metadata is missing, so I am wondering if during the download process, the files somehow became corrupted. Can any one help with this problem please? Thanks.

    The files were the correct size after downloaded them and I used the PS5 Bridge program to dowload directly from my camera.  I have spoken to Nikon and Adobe about this problem and both seem to agree that the files became corrupted during the download process.  Nikon suggested using third party software to recover the files from the SIM card, which I have now done, but out of 120 files, there were still 6 or 8 files that I couldn't do anything with.  the strange thing is that I could view all the files with the Nikon NX2 software, but as soon as I tried to do anything with them, like converting them to a jpg, I got a meaasage saying that the file was not recognised!   So panic over for this particular issue, but I am still curious to know if this is a common problem.  I suppose if nothing else, I have learned a valuable lesson, which is not to delete pictures from the camaera until after they have been successfully transfered to the computer.  Thanks for your interest in my tail of woe!

  • RAW file rendering problems with Pentax-k5

    Since a few weeks I have serious problems with the raw rendering in aperture 3.4. I have done everything to solve this problem, but until now without succes. I have upgrade with mountain lion OS X 10.8.2 and I use the latest version of aperture 3.4.3 RAW 402 build 672.6.
    Does anyone have this problem to? Or do you know how to solve this problem?
    Regards
    Jan K.

    Jan,
    that may be the same problem as discussed in this thread. Do you use in-camera settings to enhance your pictures? these will not be captured in the raw processing that Aperture does, but the pentax software understands the in-camera settings:
    Image Previews In Aperture 3 - Canon 5D MK2
    Regards
    Léonie

  • CS3: PNG File Type Problems

    I can import PNG files without a problem, but when i drag one
    onto the
    stage, it is always a very small size and not the size it
    should be. JPG
    and GIF, etc don't do this. If I drag one onto the stage from
    the library,
    they are the size they should be, but not so with PNG files.
    I can change
    the size in the property inspector just fine and the image
    will appear as
    crisp and clear as it should. But why is this happening?
    Thanks
    Aziz Peregrino-Brimah
    Bezworks Design
    www.bezworks.com

    The files being imported into Flash are files that I first
    exported out of
    Photoshop. If I export a jpeg file from photoshop and into
    Flash, there is
    no problem, but then I don't have any transparency.
    Aziz Peregrino-Brimah
    Bezworks Design
    www.bezworks.com
    "Aziz" <[email protected]> wrote in
    message
    news:f5jiam$sui$[email protected]..
    >I can import PNG files without a problem, but when i drag
    one onto the
    >stage, it is always a very small size and not the size it
    should be. JPG
    >and GIF, etc don't do this. If I drag one onto the stage
    from the library,
    >they are the size they should be, but not so with PNG
    files. I can change
    >the size in the property inspector just fine and the
    image will appear as
    >crisp and clear as it should. But why is this happening?
    >
    > Thanks
    >
    > --
    >
    > Aziz Peregrino-Brimah
    > Bezworks Design
    > www.bezworks.com
    >
    >
    >

  • File type problem with email attachments

    Hi,
    I'm using SO_DOCUMENT_SEND_API1 to send email with an attachment. This attachment is a random file uploaded by the user on an ITS web site and sent to my FM.
    It is all working fine as long as I tell SO_DOCUMENT_SEND_API1 that the doc_type is 'PDF'. When I say it's 'JPG' I get an error "Message cannot be processed as it cannot be converted".
    It's not the actual file that is the problem, I can send jpg-images or any other file as long as I say t_packing_list-doc_type   =  'PDF'. However this leads to the attached file being called *.PDF instead of *.JPG, and the receiver has to rename it.
    The relevant code is
      t_packing_list-doc_type   =  ld_format.
      t_packing_list-obj_descr  =  ld_attdescription.
      t_packing_list-obj_name   =  ld_attfilename.
    where
    - ld_format is the file extension (e.g. 'jpg', 'pdf', ...)
    - ld_attdescription = ' ' (1 space)
    - ld_attfilename is the file name without extension (e.g. 'image001')
    My FM has to work with any file extension. It receives the file name and the file extension (jpg, pdf, doc, whatever) as an input parameter along with the file, and I just need to be able to email this file with the originale file name and extension no matter what that extension is. Any suggestions? Tia.

    hi Filip Camerman,
    i am giving you the sample code try this as such.
    it_packing_list-transf_bin = 'X'.
    it_packing_list-head_start = 1.
    it_packing_list-head_num = 1.
    it_packing_list-body_start = 1.
    it_packing_list-doc_type = 'PDF'.
    it_packing_list-body_num = tab_lines.
    it_packing_list-doc_size = tab_lines * 255.
    APPEND it_packing_list.
    Regards,
    Balaji E.

  • Importing Arri DNG raw files into Premiere Pro CC

    Any suggestions on how to do this?

    Hi MarkU,
    What are you having trouble with? I assume you mean ARRI Raw. Check out this video, perhaps it will help you:
    If you mean Cinema DNG, support for that is coming in the next release.
    Thanks,
    Kevin

  • File Type Problem

    I'm new to compressor.
    I sent a FCP file to compressor and it appeared as a job.
    I then chose a setting which was H264 from the QT drop down in settings.
    My Destination I chose as my desktop.
    The encoding seemed to take a long time.
    However my file appears as a .compressor file and can only be opened by compressor.
    What happened to my QT H264 file?
    What did I do wrong?
    Thanks for any help!
    Steve.

    I am not sure if you are running into a variation of this bug, but try changing extension to .mov and also use the technique described to set "Open With" properties.
    If that does not help, if you have some more details on the set-up, computer, OS, version of FCP etc. it may help

  • HT4757 Is there a way to find out when a raw file type will be supported?

    I have a Fuji X-Pro1.  It hit the market in January/Febrary 2012.  It's RAF file is different than the X100 which is supported. 
    Also- I like to use NITF 2.1.  Is there any committment for this format?
    Is there a forecast or product roadmap for digital imagery sensors from the different camera makers or does it take inquiries from forums like this to attract product marketing attention?
    For those not familiar - The National Imagery Transmission Format (NITF) is a principal standard format for digital imagery, metadata and imagery-related products for the United States, International Standards Organization (ISO), American National Standards Institute (ISO/ANSI) and North Atlantic Treaty Organization (NATO) (STANAG-4545). 
    The X-Trans sensor of the Fuji, the Foveon sensor of the Sigma, 3-CCD cameras, and a few others do not use the standard 2x2 Bayer (1976) filter on the sensor.  And I haven't decomposed the X-Pro1 file set to see how closely it follows the ISO 12234-2, better known as TIFF/EP.
    I don't know if this or other collateral RPC metadata are evaluated items by the Apple product managers.   This impedance being a possible source of resistance to support new radiometric sensor data profiles and sensor models. 

    You might want to submit feedback to Apple since we are all users here just like you - that might be the best way to let Apple know.
    http://www.apple.com/feedback/

  • Convert RAW Files in Your Aperture Database to Adobe DNG Files

    The following describes how to convert all the RAW images in your Aperture database from manufacturer formats, such as Sony's ARW and Canon's CR2, to Adobe's DNG while retaining all the Adjustments already applied to your RAW files.  In the example below I am assuming that your Aperture Library has ARW and CR2 files.  These steps work with the latest version of Aperture, being Version 3.3, and have not been tested with earlier versions (in fact, it probably will not work because the database structure changed in 3.3 - however, this means that the steps below can also be applied to your iPhoto library).  The steps are:
    1. Within Finder select the Aperture Library and Secondary Click to bring up the Shortcut Menu.  From this select "Show Package Contents"; this will open a Window showing all the files/directories contained within your Aperture Library.
    2. Drag the "Masters" folder out of the Package and place it on your Desktop.  The purpose of this step is so that Applications, such as Adobe DNG Converter, can "see" the "Masters" folder, which they cannot do if it is located within the Aperture Library Package.
    3. Run the Adobe DNG Converter, select the above "Masters" folder with the "Select Folder" button, make sure you have selected the option "Save in the Same Location", it is also a good idea to select the option "Skip source image if the destination already exists", check your Preferences then select the "Convert" button.
    4. Adobe DNG Converter will now convert all the RAW files to Adobe DNG files and save them in the same location as your existing RAW files.  Once complete, take a note of (a) the number of files converted and (b) the types of files converted, such as if the conversion includes ARW, CR2, NEF files etc.  In this example I will assume that the converter only found ARW and CR2 files; if your system is different then modify the steps below to make sure it covers all the RAW file types converted in your particular system.
    5. Select the "Masters" folder and in the Finder Window Search Field search for all the files that end in .ARW and .CR2 (this filename search list should match the types of files found by the Adobe DNG Converter in step (4)(b) above).  The number of files returned by the search must match the number of files recorded by the Adobe DNG Converter in step (4)(a) above.  Do NOT put the .DNG files in your search criteria.  Select all the files found in the search and move them to the Trash.  This will delete all the original manufacturer's RAW files from your Aperture Library leaving behind all the new DNG files.
    6. Move the "Masters" folder on your Desktop back to the root directory of the Aperture Library Package Content directory.
    7. Select the Finder Window containing the Aperture Library Package Contents.
    8. If there is a file called "ApertureData.xml" then open it with a text editor.  Search and Replace ".arw" with ".dng", ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (note, do not use the " marks in your search).  Make sure you cover all the file types incorporated in your particular system.  Save the "ApertureData.xml" file.
    9. Traverse to the Database/apdb directory.  Select the "BigBlobs.apdb" file and open it with a Hex editor.  In this example I will use Hex Fiend by Ridiculous Fish (see http://ridiculousfish.com/hexfiend/).  Once the file is open perform a Find and Replace ensuring you are finding and replacing Text and not Hex.  In Hex Fiend this means selecting Edit/Find from the menu and then selecting the "Text" button to the top/left of the window.  In your Find/Replace field you will need to find ".arw" and replace it with ".dng", make sure you select "Replace All" (note, do not use the " marks in your search).  Do exactly the same for ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (and whatever particular RAW files were in your system).
    10. Perform exactly the same steps in (9) for the files "History.apdb", "ImageProxies.apdb", "Library.apdb" and "Properties.apdb".
    That is it, your Aperture Library now contains DNG files instead of your original manufacturer files while still retaining all the Adjustments originally made in Aperture to those manufacturer files.  Of course, you can repeat the same step and replace your DNG files with the original RAW manufacturer files if you wish.  This process works because:
    1. Aperture does not store the Adjustments in the RAW files, it keeps these in its internal SQLite database.
    2. By using a Hex Editor you (a) don't have to play with SQLite to gain access to Aperture's data and (b) because you are replacing text that has exactly the same number of characters you are not invalidating the format of the underlying data file - this is why you use a Hex Editor instead of a simple text editor.
    Think of Aperture as being a repository that holds Adjustments which then link to the original RAW source.  Therefore, the above process simply replaces your RAW source and therefore all the Aperture Adjustments are still valid; same Adjustments, new source.  In case you ask, no, you cannot transfer Adjustments in and out of Aperture because there is no standard to transform adjustments between different photographic applications.

    A rather involved method, David.
    I am sure it works, and compliments for figuring it out, but I think one critical step is missing in your workflow: Before you begin - backup, backup, backup!
    And I think, all the edits in your database that you are doing so diligently, is what you bought Aperture for to do for you, why do it yourself?
    I convert selected raw files this way - without manually patching the Aperture Library:
    Export the originals of the raw images that I want to convert.
    Run dng-converter.
    Import the converted originals back, flag them,  and move them to the project they came from.
    Sort the project by capture date, so that identical images are show side by side.
    Then I use the Lift&Stamp tool to transfer all adjustments and tags from the original raw to the dng copy. I check, if some edits are left to do, then delete the original.
    It may take a little longer than your method, but this way all edits in the library are done by Aperture, and I am protected from accidental slips when editing the property list files. That requires a very careful work.
    Patching the database files inside the library may be justified as a last ressort, when you need to fix and recue a broken Aperture library, and none of the provided tools is working, but not as a routine operation to do batch conversion of image files. It is very error prone. One wrong entry in the library files and your Aperture Library may be unreadable.
    Regards
    Léonie

Maybe you are looking for