DNG converter 6.4 and DNG codec 1.1 for Win7 32 & 64bits released!

The DNG converter 6.4 has been released, http://www.adobe.com/products/dng/ with support for many new cameras, including:
Canon EOS 600D (Rebel T3i / Kiss X5 Digital)
Canon EOS 1100D (Rebel T3 / Kiss X50 Digital)
Fuji FinePix S200 EXR
Fuji FinePix F550 EXR
Fuji FinePix HS20 EXR
Fuji FinePix X100
Hasselblad H4D-40
Kodak EasyShare Z990
Nikon D5100
Olympus E-PL1s
Olympus E-PL2
Olympus XZ-1
Samsung NX11
Note that it is the last version to run on Power PC Macs: http://blogs.adobe.com/lightroomjournal/2011/03/dng-converter-6-4-last-to-support-powerpc- mac-systems.html
Also released today: The DNG codec 1.1 that now supports the 64bits version of Windows 7, but does not support Vista anymore.
http://labs.adobe.com/wiki/index.php/DNG_Codec
Finally, the DNG Profile Editor beta 3 is out too, and has also been updated to address bug fixes and support DNG files utilizing the updated DNG 1.3 Specification.

I just downloaded and installed this version on Windows 7 Home Premium 64bits.
I can report it works great with my Raw DNG files, from camera: Pentax K-m/ K2000.
Probably also with all other Pentax camera's.
Jan (Netherlands)

Similar Messages

Driver(s) to print on HP Laserjet 4000n and HP Deskjet 722C printers for Windows 7 (64bit)

I'm introducing a Windows 7 64bit) computer in a network of Windows XP (32bit) computers.
How do I find driver(s) to print on HP Laserjet 4000n and HP Deskjet 722C printers in a network that uses Windows 7 (64bit) and Windows XP (32bit)? Printer sharing is done using a Windows XP (32bit) base computer.
Should I load a 64bit driver on the 32bit XP computer for the benefit of the Windows 7 computer or will that mess up the XP computer?
Thanks

Hello, the HP laser jet 4000n you install the drivers via windows update procedure. The HP 722C is not supported under Windows 7 due to it's age.
Say thanks by clicking the Kudos Thumbs Up to the right in the post.
If my post resolved your problem, please mark it as an Accepted Solution ...
I worked for HP but now I'm retired!

Raw, Adobe DNG codec, LR Beta 3, frustration...

As an advanced amateur photographer, I decided that my New Year's resolution would be to stop shooting JPEG plus supplementary Raw on my Nikon DSLR, and to use only Raw. Also decided to try LightRoom Beta 3 (not a LR user previously; I use Windows Live Photo Gallery). Finally, also decided to use DNG instead of NEF to facilitate cross-application compatibility (ie, I like the idea of a non-proprietary datafile format) and to avoid creating sidecar (XMP) files for keywords. I use Windows 7 Pro and Home Premium on an Acer Netbook and Dell Inspiron notebook computer, although I've only created the DNG files on the netbook so far.
It's been a sinkhole of time to get working.
Once I had created some DNG files from the NEF files using LR3, the computer performance deteriorated completely. Eventually found that CPU was pegged at 100% utilization, and that SearchFilterHost.EXE was the culprit. MUCH sleuthing revealed that going into Windows Control Panel > Indexing Options > Advanced, and unchecking the DNG file type allowed the indexing to proceed to completion. When the DNG files WERE allowed for indexing, then the Indexing Options dialog box showed that the indexing stalled at some point; if the DNG files were DISALLOWED, the the indexing completed normally.
Secondly, when I opened Windows Live Photo Gallery, it showed that it was creating thumbnails (presumably the DNG files), but that it was proceeding at about 1 file per 30 seconds. The CPU was pegged at 50% during this time. Eventually all the thumbnails were completed, and CPU utilization dropped to a few percent.
In both cases, Windows Resource Monitor revealed that Adobe's DNGCodec was associated with the stalled/slow process.
I installed the latest DNG converter from Adobe, but the DNG Codec remained unchanged (version 1.0.0.2, dated from 2008). The DNG codec does not appear to have a recent version on the Adobe website.
Next, I uninstalled the Adobe DNGCodec, and downloaded and installed the third party codec from http://www.ardfry.com/dng-codec/Download.htm. The thumbnails in Windows Live Photo Gallery were generated at a rate of several per second, and the Windows Indexing Options proceeded without hanging up, although it was slow. It's definitely working better with the third party codec.
Searching the forums reveals that lots of people are dissatisfied with the lack of a 64-bit DNG codec from Adobe. This problem seems to have existed for over a year, maybe even two years. I don't use 64-bit Windows, but the codec problems are in 32-bit, too. How can Adobe expect users to adopt DNG as a standard when they provide such poor support? It's crazy that end-users should have to seek out, download, purchase, and install a codec from a third-party supplier in order to get reasonable performance.
Adobe: please fix your DNG codec.

Thanks to you, jackfrombc, for for proofing my concerns about why indexing loads my CPU so much after I install some new soft, and DNG codec among it. Now I'm able to switch indexing back on on my combuters not being afraid of it eating laptops' batteries.
Thank you, again.
ps. sorry for poor english, in advance.

ACR 8.4RC DNG conversion can create files that crash Adobe DNG Codec 2.0

If I use the ACR 8.4 DNG converter to convert a raw file from my newly acquired Fuji X-T1, and I use the default compatibility option of ACR 7.1, the resulting DNG file causes Windows Explorer to crash whenever I navigate to the folder that contains the file.
I believe that this is happening because Adobe DNG Codec 2.0 is trying to create a thumbnail for the file, and it is not capable of dealing with DNG files that require the Camera Raw 7.1 demosaicing algorithm.
If I convert the same raw files and ask for ACR 6 compatibility, I don't have any problem navigating to the resulting folder. However, the resulting DNG files are much larger. Moreover, I understand that those files have already been demoasiced, which means that any future improvements in demosaicing algorithms will be moot.
My question, then, is whether the DNG Codec will be updated any time soon to handle files produced by the 8.4 DNG converter.

I’m on Windows 7 SP1, 64-bit version. So far as I know, I’m current on windows updates.
A sample image can be found at https://www.dropbox.com/sh/izcl857d37fmtdc/sGj2wuG3LF
Of course, it is possible that some other codec on my computer is the cause of the crash. However, I know for certain that
When I uninstall DNG Codec 2.0, I get no thumbnails for these images and no crash.
When I (re)install DNG Codec 2.0, Windows Explorer crashes the moment I navigate to the folder that contains these images.
I have found no problem with DNG files created from other manufacturers’ raw files.

DNG Codec Not Working On Win Vista 32Bit

Having real problems with this DNG Codec I installed onto my Windows Vista 32 Bit system and this is what's happening. Yea, I can now see my DNG raw files through picture viewer and windows explore without going through PS. Unfortunately, when I decide to close down picture viewer the program crashes every time and the computer freezes up. Then I have to choose one of the error solutions to close out the program and the computer reverts back to a normal state after that. Also there is one other quirk it has caused and that is related to the "recycle Bin". When I delete a Raw file into the recycle bin and then want to empty the bin it goes into a non-stop operation of trying to delete the files without actually doing it, go figure and anybody else having similiar problems? Oh, by the way I uninstalled the Codec to see if my computer goes back to its normal behavior and guess what, everything is working as it should so its the Codec that has a major problem.

Ok, I seem to have got around the first issue using this http://bit.ly/mpWcuy
The new box has 16 cores on the cpu whereas the old box only had 4 so I had to up AWE_WINDOW_MEMORY registry entry to 1.2GB (as the calculated 1.07GB wasn't quite enough and the suggestion was to just up it to 1.2GB!)
However, I am now getting a different issue when trying to open the database!
C:\>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Fri Jun 17 12:16:43 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 2.2330E+10 bytes
Fixed Size 1414384 bytes
Variable Size 1027722000 bytes
Database Buffers 2.1299E+10 bytes
Redo Buffers 2129920 bytes
Database mounted.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00600: internal error code, arguments: [kcbvmap_1], [], [], [], [], [], [],
Also, though at this stage it doesn't matter as I can't open the database, I can't push DB_BLOCK_BUFFERS past 2600000 even though the server has 72GB RAM. 2600000 uses just 22GB of ram (including the os and everything else on the box)
Edited by: bobonacus on Jun 17, 2011 12:20 PM
Edited by: bobonacus on Jun 17, 2011 12:21 PM

DNG codec doesn't support descriptive tags in Windows 7

I installed the Adobe DNG codec yesterday which does indeed make it possible for Windows Explorer, Windows Media Player, Windows Live Photo Gallery and Windows Media Center to display DNG files (as thumbnails and as full sized images). I discovered however that descriptive tags are not supported. I use descriptive tags to organize my JPG photos. Descriptive tags are fully supported with JPG files in Windows 7. Windows Explorer exposes them for viewing and editing in the metadata pane along the bottom of the window. Windows Live Photo Gallery exposes them for editing and in the tree structure that is used for navigation. Users in Windows Media Center can choose to view their photos by descriptive tags, or date, or folder. Without descriptive tags, my photos would be a disorganized mess. I'd like to switch to storing my photos as DNG's rather than as JPG's, but it just isn't feasible without descriptive tag support in the codec. Any chance the DNG codec will support descriptive tags in a future release?

Hello shyamananda,
I have checked the drivers for your Deskjet 1180c and Windows 7 Ultimate 32 bit.
Unfortunately they are not compatible.
Here is the link to show you that it is not compatible: HP Products - HP Products Not Supported in Windows 7
I hope this answers your question.
Regards,
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

DNG Codec - 64bit Win7

Creating a thread for 64bit Windows7 users to post in regards to support for the DNG codec on 64bit-Win7.
Currently 64bit nor Win7 is supported for the RC codec. Adobe supports 64 bit, in CS4, LR 2.x and LR3 beta. I expect 64bit and Win7 for the codec.
For those who want to play with the unsupported RC codec on 64bit win7, it would be great to get comments on this thread with your experiance.

www.gnu.org - free developement tools
www.adobe.com/products/dng/pdfs/dng_spec.pdf - freely available DNG specifications
Cost: $0
Now you are all set to write your own free DNG codec
Joke aside, Adobe is under no obligation to supply anything for free, where is the logic behind that claim? The Word and Excel document formats are open and, unlike DNG, actual international standards (see ECMA-376 and ISO/IEC 29500), does this means that Microsoft Office should be free? Microsoft makes free readers but it's entirely at their discretion, and the same goes for Adobe.
As for 3rd parties filling niches and charging for their work, what's wrong with that? What FPV and Ardfry charge is pocket change compared to the work involved with writing stable and well-performing codecs, and as David implied is certainly also pocket change compared to the cost of any photographer's kit.
Axel,
Imaging software and codec author
www.fastpictureviewer.com

Problems with DNG codec

I have installed the DNG codec on my laptop. Restarted, but afterwards couldn't see any thumbnails for my DNGs (DNGs created with the Adobe DNG convertor from an EOS 10D, and also DNGs created with CaptureOne 4, same camera).
On top of that, thumbnails of other file formats weren't shown anymore, either. Most of the time when browsing to a folder, the correct thumbnails blinked up for a moment, and then most of the images showed the generic image icon, while a few (mostly 2 or 3 out of a folder of 10-20 images) still showed the thumbnail.
After deinstalling the codec, everything went back to normal.
Oh, forgot to mention: The OS is Vista Business 32.

My issue is that the codec appears to be Read Only. I would really like to be able to geotag my DNG files using the Microsoft Pro Photo Tools that were released in the Spring.

A DNG Codec for Win7 64bit...Please?

Seriously, It's high time that Adobe
released a salient codec for Windows 7.
Yes...I do like to see pictures rather than some silly icon in Windows Explorer colorspace be damned.
But absent that...Anyone got a line on a free (non-trial) DNG codec for Windows 7 64-bit?
And, Adobe, Microsoft, Y'all play nice now.

Well I downloaded and installed the (latest?) 'dngcodec_r2_042711.exe' codec today ....and it didn't work.
Windows Explorer used to show a basic 'DNG' icon for each file ...Now it just shows generic 'picture' icons instead. Not a lot of help.
I have win7 64-bit, Lightroom 4 etc. and used the 'Make copy as dng' menu option to generate DNGs from Nikon NEF (raw) files, already present on the hard drive, as I wanted to get away from the cumbersome additional 'sidecar' files generated by the ACR engine but it seems I am stuck with them until someone (Adobe, can you hear this?) comes up with a suggested fix or something.
Anyone any ideas?

DNG Codec makes Vista Indexing very slow?

Hi,
I recently installed the DNG codec to preview my photos in Windows and I let Vista Search index all my storage. It was taking weeks and the number of indexed files was barely moving. I wasn't sure what it was so I started excluding folders from the index one by one. Eventually I realized that it was the Pictures folder which contains roughly 60GB of mixed JPG and DNG photos. I uninstalled the DNG Codec and now indexing is finished, including the Pictures folder, several hours later.
Vista Home Premium, 32-bit, 4GB RAM, Core 2 Duo 2.66MHz.
Regards,
Pavel

I've got:
4GB memory
Page File (virtual memory) is 7326M
2.4GHz P8600 Dual core processor
105 GB available disk space
video card is a NVIDIA Quadro NVS 160M
Those stats should surpass the minimum requirements with flying colors.
I've just noticed that ever since I've got Windows Vista, any menial task of moving (cut & paste) a 100KB file from one folder to another folder on my local PC could take minutes instead of milliseconds. Unzipping items also takes a ridiculous amount of time. I was thinking this slow vista file management might be causing the slow Oracle install.
I was hoping someone else might have see this issue before and can tell me where the "go-faster" flag is located.
Thanks!
-Joe

Imported DNGs generated in ACR for Windows only show thumbnails

Hi,
Today I imported DNGs from pictures I've created with my 350D through the last year or so. Some of these work completely fine, but others won't show the full-resolution image; they only show a small 256 x 171 thumbnail version.
There is a pattern to whether it's working correctly or not: the DNGs that display correctly were converted on my old iBook - in other words using Adobe Camera Raw for Mac - and the ones that don't work were the pictures I processed on my Windows PC, thus using the Windows version of ACR.
Another thing I've noticed is that apparently the changes made to the pictures in ACR are not recognized by Aperture - is this to be expected?
Does anyone have any idea what I could do to make my pictures work as they should? Thanks in advance.

UPDATE
My solution works but I would suggest a few things to avoid a problem I encountered (see THE PROBLEM below):
- Copy your Aperture Library File to the desktop (after backing it up to your vault), then reload Aperture. Your Library should now be empty.
- Then import your DNGs in batches to this new library
- As each import batch is successful, export the project to a file on the Desktop.
- When they have all been successful, copy your original Aperture Library file back to its original location (after deleting the new one you created)
- Then import the projects you saved to the Desktop one by one
The above steps mean that you don't have to go through the process of restoring your library (and all the thumbnails) should Aperture spit the dummy and crash during a DNG import. If it does, you won't be able to fix it without restoring the library... A pain in the A
THE PROBLEM
I was having a problem with a handful of DNGs which seemed to cause Aperture to crash and exit. I couldn't work out what was going on but now I think I have an answer.
The problem seemed to be with DNGs created with the newer versions of the Windows DNG Converter. Converting them with the latest Mac DNG Converter (v3.4) did not resolve the issue.
So, I downloaded the Mac DNG converter v3.1 and converted the existing troublesome DNGs v3.1.... and it works. I can now import even the troublesome DNGs into Aperture now without a hitch.
There seems to be no way of telling which DNG converter version was used to create an individual DNG although I found that it was related to all DNGs after a certain date (ie. the date I started using the newer DNG converter!)
I hope this of help to everyone and that it has answered the question.
Cheers,
Paul Martin
www.paulnika.com

Quicktime Pro and Indeo Codec 5?

I have a Casio Exilim camera and my .avi movie files do not play on QuickTime 7 on my Mac OS X. I have sound but no video output. I tried downloading a variety of players/codecs and converting the files to other video file types (.mov, mpeg) but the files ended up only playing successfully on the VLC media player. Unfortunately, I'm still unable to upload my movie files to iMovie - no video, only sound -(which is frustrating because one of my main reasons for getting a mac was for its video editing capabilities). I read that the codec that supports Casio .avi files is an old one called Indeo 5. I also read that Quicktime Pro supports this codec but not for Mac OS X.
Can anyone confirm whether or not Quicktime Pro supports Indeo 5 on a Mac OS X before I drop $30 for it?

I read that the codec that supports Casio .avi files is an old one called Indeo 5. I also read that Quicktime Pro supports this codec but not for Mac OS X.I don't see it listed on the Official Support Page for QT Pro. Some Indeos may been ported for use with OS 9, but I don't believe any were for OS X.

What's a good solution for cataloging DNG raw photo files for creative teams?

Does anyone know of a good solution for cataloging DNG raw photo files for creative teams? I'm looking for something that will extract previews as well as be searchable by category and keywords?

Does anyone know of a good solution for cataloging DNG raw photo files for creative teams? I'm looking for something that will extract previews as well as be searchable by category and keywords?

Editing/Converting M2T PAL and MXF NTSC

Hi,
I am working on a project that will involve AVI M2T PAL files shot on a Sony Z7 at 25fps. I will also be bringing in footage that is DVCPROHD MXF NTSC (most likely to be shot at 24fps or 29.97) from a Panasonic HVX-200.
My final product will need to be NSTC at either 24fps or 29.97.
What is the best (most efficient and high quality) way to work with both types of formats?
If I convert them to an intermediary codec (in FCP you would convert to Pro Res), which one would you recommend for Premiere Pro?
I know you can typically work with different video formats on one timeline in Premiere, but perhaps this is too extreme (the difference in FPS)? And I would prefer not to slowdown my workflow while editing (and not have to render more frequently).
Thanks.

I am working on a project that will involve AVI M2T PAL files shot on a Sony Z7 at 25fps.
Which is it: AVI or M2T? I assume you mean HDV M2T, but just checking...
What is the best (most efficient and high quality) way to work with both types of formats?
Edit them as they are. They won't get any better from what they already are, so you'll needlessly waste time, space, and quality converting them. Just pick the frame rate/timebase that makes the most sense; it doesn't sound like you've settled on what one of your sources will be, or your output, so you can weigh those into the equation once you get that sorted.
If I convert them to an intermediary codec (in FCP you would convert to Pro Res), which one would you recommend for Premiere Pro?
None; see the above.
I know you can typically work with different video formats on one timeline in Premiere, but perhaps this is too extreme (the difference in FPS)? And I would prefer not to slowdown my workflow while editing (and not have to render more frequently).
Nope; it's not. In Premiere Pro, dropping a video with one frame rate into a sequence with another frame rate is pretty trivial from a computational point of view--it simply plays the file back at its source frame rate. When it comes time for export, those differences will have to be rectified, but that's not a big deal either. There's only so much you can do in your case--you're working with video from two distinctly different video systems that don't have a common factor when it comes to frame rates. Typically, it's better to go to a greater frame rate than a lesser one--Premiere Pro will simply pad/interpolate the required frames to meet the greater frame rate, whereas going to a lower frame rate will involve throwing away frames.
And with a decent computer, you probably won't have to render--at least if all you're talking about is editing. When you start dropping effects--particularly non-accelerated effects--into your sequence, then rendering may become an issue. But with the two video formats you've listed, any system built within recent history (in computer terms) will handle them easily.

Convert smart quotes and other high ascii characters to HTML

I'd like to set up Dreamweaver CS4 Mac to automatically convert smart quotes and other high ASCII characters (m-dashes, accent marks, etc.) pasted from MS Word into HTML code. Dreamweaver 8 used to do this by default, but I can't find a way to set up a similar auto-conversion in CS 4. Is this possible? If not, it really should be a preference option. I code a lot of HTML emails and it is very time consuming to convert every curly quote and dash.
Thanks,
Robert
Digital Arts

I too am having a related problem with Dreamweaver CS5 (running under Windows XP), having just upgraded from CS4 (which works fine for me) this week.
In my case, I like to convert to typographic quotes etc. in my text editor, where I can use macros I've written to speed the conversion process. So my preferred method is to key in typographic letters & symbols by hand (using ALT + ASCII key codes typed in on the numeric keypad) in my text editor, and then I copy and paste my *plain* ASCII text (no formatting other than line feeds & carriage returns) into DW's DESIGN view. DW displays my high-ASCII characters just fine in DESIGN view, and writes the proper HTML code for the character into the source code (which is where I mostly work in DW).
I've been doing it this way for years (first with GoLive, and then with DW CS4) and never encountered any problems until this week, when I upgraded to DW CS5.
But the problem I'm having may be somewhat different than what others have complained of here.
In my case, some high-ASCII (above 128) characters convert to HTML just fine, while others do not.
E.g., en and em dashes in my cut-and-paste text show as such in DESIGN mode, and the right entries
    –
    —
turn up in the source code. Same is true for the ampersand
    &
and the copyright symbol
    ©
and for such foreign letters as the e with acute accent (ALT+0233)
    é
What does NOT display or code correctly are the typographic quotes. E.g., when I paste in (or special paste; it doesn't seem to make any difference which I use for this) text with typographic double quotes (ALT+0147 for open quote mark and ALT+0148 for close quote mark), which should appear in source code as
    “[...]”
DW strips out the ASCII encoding, displaying the inch marks in DESIGN mode, and putting this
    "[...]"
in my source code.
The typographic apostrophe (ALT+0146) is treated differently still. The text I copy & paste into DW should appear as
    [...]’[...]
in the source code, but instead I get the foot mark (both in DESIGN and CODE views):
I've tried adjusting the various DW settings for "encoding"
    MODIFY > PAGE PROPERTIES > TITLE/ENCODING > Encoding:
and for fonts
    EDIT > PREFERENCES > FONTS
but switching from "Unicode (UTF-8)" to "Western European" hasn't solved the problem (probably because in my case many of the higher ASCII characters convert just fine). So I don't think it's the encoding scheme I use that's the problem.
Whatever the problem is, it's caused me enough headaches and time lost troubleshooting that I'm planning to revert to CS4 as soon as I post this.
Deborah

DNG converter 6.4 and DNG codec 1.1 for Win7 32 & 64bits released!

Similar Messages

Maybe you are looking for