Adobe dng converter dng available with Capture One 7

Dopo aver convertito in dng i file della Sony A7R non riesco a vederli in Capture One 7.
Qualcuno sa dirmi per favore qual è il problema? E' possibile che Capture One 7 non sia compatibile con i dng ex raw Sony?
Grazie

You can convert a whole folder of raw images in one click. See this quick video tutorial:
You Tube click here for DNG Converter tutorial

Similar Messages

Anyway to share original files from Aperture with Capture One & Lightroom

I would like to use the 10,000 RAW files I have downloaded with Aperture and be able to use them in Capture One and play with Lightroom. I could export the Originals but then I would be doubling or even tripling the space needed to use these 3 programs. All three programs have different advantages and would like to be able to use all three. I'm sure Apple doesn't want anyone to use anything but Aperture but in the real world, Aperture can't do all the things I want to do.
I have found the originals in Aperture (show package contents) but each picture seems to be in a seperate folder and not altogether in a central folder.
Any help would be appreciated.
Thanks,
Jim

Best is way is as Jeff says, use referenced files, then to open a raw file with Capture One simply select it in Aperture's browser, ctrl+click (right click) on it and 'show in finder'. From there drag it to Capture One and done.
To automatically import the result to Apertue you can use a hot folder where the processed file from Capture One should be saved to.
I also need to process sometimes raw images in Capture One, specially those with coloured tungsten lighting. Capture One's white balance is way much better than Aperture's.

Will Adobe ExportPDF convert a pdf with text and images to docx ?

I have tried to convert an adobe pdf, which includes text and images, to a docx file. The Adobe ExportPDF has not been able to do it - comes back with many errors.

Mostly it can do it, though you can't expect a precise match on the layout. What errors do you get?

Problems to use Adobe Flash Media Live Encoder with Capture Card PixelView TV-8000GT2

I want know if Adobe Flash Media Live Encoder have any incompatibility with a PixelView Capture Card, specifically model called TV-8000GT2. And if it can be fixed with a atulization or sothing like that. Nothing more, thanks.

Moving the discussion to Flash Media Forum.
Regards,
Anit Kumar

Is interMedia available with Standard One Edition?

Hi All - I read in the documentation that interMedia is available in the Standard and Enterprise Editions of Oracle, but does this include the Standard One Edition also?
Thanks for letting me know.
oraclemangt

run this (as a dba, or access to the dba_registry view):
SELECT
comp_id,
RPAD( comp_name, 40, ' ' ) component,
status,
version
FROM dba_registryI believe the only difference between Standard Edition and Standard Edition One is the number of processors it can use SE1 = 1, SE = 1 or more. Don't quote me on that though.
chet

Lightroom vs Capture One

I just got a dutch Photo Mag that compared Lightroom 2 to Capture One 4. I was amazed at the conclusion Capture One won the contest, based upon image quality results. I immediately downloaded a 30 day trial and compared LR, PS cS3 and CO side by side on my 30inch HD cinema display. Yes I could see a difference, especially that CO is able to deliver a bit more contrast while still keeping dark areas visible. It's difficult to compare sharpening because values don't match (compared LR 100-0,8 to CO 170-0,8).
Anyone working with Capture One and willing to share experiences?
Thank you.

I did a lot of work on this a while ago - C1 is very popular in the Leica M8 world. Bottom line is that a lot of the perceived difference in color is really a different tone curve. An LR brightness setting of about 35 gives a similar tone curve to C1.
If you want dig into enormous detail around color differences between LR, Aperture and C1, go here:
http://chromasoft.blogspot.com/2008/01/lightroom-aperture-and-capture-one-mini_24.html
Note however that the work above was pre-DNG profiles, it applies to old ACR type rendering.
I also posted some settings on how to get C1-like colors from Lightroom here:
http://www.l-camera-forum.com/leica-forum/digital-post-processing-forum/76171-aperture.htm l#post793752

How to make a synchronous acquisition of two analog signals with a one channel DAQ ?

Hi !
It is the first time I use Labview. I have just made some easy VIs, and now, I do not know how to deal with my problem...
My problem : I have only one acquisition card (DAQ Ni 6034E) and I would like
to acquire simultaneously two analog signals. It seems to be possible, in a quasi-synchronous acquisition if the card acquires one point of the first signal, then the first point of the second signal, then the second of the first signal, and so on ... I thougth that I could made two sequencies with a VI of data acquisition in each sequency, with the AI MULT PT. But with this, I think that I will lose the precision of the sampling frequency. And I have to know the sampling fre
quency ...
Thanks for your help !
Carline

Hi Carline,
A PCI-6034E is a low-cost board, which only has one Analog to Digital Converter (ADC).
With only one ADC you can't acquire different channels at the same time. That's why you find a multiplexer before the ADC in this type of board. This enables you to acquire multi-channels at the same rate quasi simultaneously. The samples of the different channels will be interleaved as it is explained in the following knowledge base :
- http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/9379ea091c264b7c86256bc90082ca5d?OpenDocument.
With this method, the sampling frequency is the same for all channels. The sampling frequency of one channel is determined with the "scan rate" parameter. There is only a small delay between the samples
of each channels. When you perform an interval scanning acquisition, this delay depends on the "sample rate" that you specify. To have more informations about this terminology, please refer to the following KBs :
- http://digital.ni.com/public.nsf/websearch/4D1435DF82EF494186256D8A006DD6D4?OpenDocument.
- http://digital.ni.com/public.nsf/websearch/4D1435DF82EF494186256D8A006DD6D4?OpenDocument.
To easily perform such a multi-channels analog acquisition, you can use the VI named "AI Acquire Waveforms.vi". You also can use an example provided with LabVIEW. You just have to browse the NI Example Finder in "Harware Input & output >> Traditional NI-DAQ >> General".
Best regards,
Benjamin
National Instruments France

Capture One DB and Pro v3

I'm considering the upgrade, but not confident about the compatiblity of the OS with Capture One. Does anyone have feedback as about the performance of the application on 10.6?

In the past when I've used the Nikon View / capture; it under performed. Either plagued with bugs or ran slow.
The PhaseOne folks don't guarantee the Capture One v3 to work on OS 10.6. But the v4 should.

Teathered Capture Module or Capture One Raw Data Importer

In many commerical professional studios people like to use Capture One Pro in a teathered environment because it works with most cameras, its got an interface that is productive as images stream in (ie- updating white balance, checking focus, checking color number exposure thresholds, overlaying comps) and it's much faster at loading previews than capturing into a hot folder situation like Lightroom has it now. All in all, Capture One is better for live capture teathered environments.
There is a giant problem with capture one, that is that the raw image data created through adjustments in capture one is propietary to capture one and can't be imported into Lightroom for archiving without losing that valuable data. Therefore, i'm either requesting that you either create a Capture Module that is as quick, effiecent and has all the productive tools that capture one has so that we can ditch the glitchy program or create a way to import raw files from capture one to lightroom and maintain the same image appearance.

I agree, C1 pro 5 has made leaps and bounds in the last few years from 3.7. I like it as a capture program but not as a method for organizing and archiving my images. I wish the two could communicate better in a fashion that doesn't require a work around. It's a real workflow issue.

Request: Capture One Style Teathering Module

In many commerical professional studios people like to use Capture One Pro in a teathered environment because it works with most cameras, its got an interface that is productive as images stream in (ie- updating white balance, checking focus, checking color number exposure thresholds, overlaying comps) and it's much faster at loading previews than capturing into a hot folder situation like Lightroom has it now. All in all, Capture One is better for live capture teathered environments.
There is a giant problem with capture one, that is that the raw image data created through adjustments in capture one is propietary to capture one and can't be imported into Lightroom for archiving without losing that valuable data. Therefore, i'm either requesting that you either create a Capture Module that is as quick, effiecent and has all the productive tools that capture one has so that we can ditch the glitchy program or create a way to import raw files from capture one to lightroom and maintain the same image appearance.

There is a feature request forum
here

I'm considering buying CC LR/PS package. My camera is Sony a7 - raw ARW. I've been editing using PSE10 and ver 8.7 of the external Adobe DNG converter. Will I be able to open the DNG files in LR with the edits preserved? Will I be able to open the PSD fil

I'm considering buying CC LR/PS package. My camera is Sony a7 - raw ARW. I've been editing using PSE10 and ver 8.7 of the external Adobe DNG converter. Will I be able to open the DNG files in LR with the edits preserved? Will I be able to open the PSD files in LR with the edits preserved? Any import/catalog etc issues between PSE10 and LR?

Lightroom has no problem reading DNG files. Whether the edits you have done to the DNGs you have originally edited in Photoshop Elements 10 I'm not sure. ACR edits made to DNGs are saved in the DNG file itself, as apposed to a XMP sidecar file, so LR should see those edits. At the worst you will get an exclamation mark in the upper right hand corner of the imported DNGs and clicking on that exclamation mark you will get a dialog box asking you to either import settings from disk or overwrite settings. you would select import settings from disk.

I can't open nikon D750 NEF files with adobe dng converter 8.7

I have downloaded adobe dng converter 8.7 to open NEF files from my new nikon D750 but it not works. The program do not recognice the files. Do you know how solve this problem?

You have to launch and run the Adobe DNG Converter on each batch of raw files you want to convert to raw DNGs.
You have to point it to the folder containing your raw files. It does NOT work on individual raw files; it simply won't see them. It works only on folders.

NEF vs. DNG : Different renderings in Capture One 4

I've just observed that -- when I convert a D200 NEF > DNG, and then import both to Capture One 4, the renderings are slightly different ... both of them with default settings.
I select ICC profiles for NEF > D200 Generic , DNG > Neutral.
DNG is darker than NEF.... not uniformly daker, but just some parts... like different curves applied.
Same Kelvin values (WB) applied to both files give different results -- DNG needs lower Kelvins degrees to look like the NEF.
NEF Reds are orang-ish in DNG. DNG yellows are orang-ish in NEF.
Something I'm not sure how to describe, but it looks like differences in color brilliance between the two files.
If I select ICC profile for DNG > D200 Generic , then the same applies, only that now DNG looks more saturated than NEF.
For reference, Lightroom renders both files exactly identical.
So ... is this something related only to how C1 renders both files (C1 not knowing how to manipulate a DNG), or is it related to the DNG conversion itself (adobe playing god with the raw data) ?

Honestly, I can infer from your posts by SIMPLE READING only that you are confused and speculating a lot.
I try to put the results in cleartext:
1. C1 creates result A from the native raw file.
2. C1 creates result B from the DNG file converted from the raw. B is different from A.
3. C1 created result C from the modified DNG file. C is different from A AND from B.
If the above is right, then we can say, that
a. C1 CAN work with the pure DNG data, which includes the color conversion Adobe's way. The modified DNG differs from the original DNG in that the camera name (maker and model) has been changed, AND the MakerNote tag has been made unaccessible, and this file has been accepted by C1.
This is in contrast to some other raw processors, which accept a DNG file only if they know the camera's characteristics; see the thread "Is DNG a universal raw format?" down below.
b. C1 DOES take some information from MakerNote if available, otherwise these two version would yield the same result.
The originating question was, why the "native" and DNG result are different. Based on the above test, I can not answer it with certainty, it is not clear, what C1 uses from MakerNote.
Now, to the question of "DNG - standard or not".
The DNG specification tries to put many aspects of a raw image in a uniform shape. However, there are two distinct areas posing problems:
1. Camera specific options. The Exif specification provides for a way of recording sharpness, contrast, saturation and white balance, but the specification has been created very short-sightedly and became useless. Other options, like Picture Style has not been envisioned at all. Such options are coming in series, the DNG specification does not cover them.
These options are available in the native raw file as well as in DNG, but programs have to make extra gymnastics to extract them from DNG; NOT DNG is to blame in this point.
Some raw processor go the extra way, others don't. ACR does not make anything, which can not be seen in DNG format as well, i.e. it does not support these options.
2. The other problem area is the color transformation. There is *no* generally accepted way to describe the sensors' behaviour. Most raw processors adopted camera and model specific solutions; Adobe defined a way in DNG, which is an *approximation*. Others don't share the enthusiasm, with some justification. It is not by chance, that camera makers' own converters give the best colors of their cameras.
So, a raw processor can process a DNG file using the hard-coded knowledge of the sensor - like Aperture does - or going ACR's way of color transformation.
C1 may take some setting(s) from the native raw file, while not doing so with a DNG, even if the data is available (but differently). This may be the reason for the difference between the results of the NEF and DNG conversion.
Note, that it is not necessary to access the MakerNote for identifying the camera.

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

Adobe DNG Converter can't recognize any files

Hi All!
I'm new here and would very much appreciate help.
I am running a Mac OS X 10.04.11 and would like to open .CR2 files (native file from my Canon 500D) in PS4      / Bridge CS4. My problem is that although I have downloaded the Adobe DNG Converter and Camera Raw 5.1 update as described here: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4057, the DNG Converter can't recognise any files at all (they are greyed-out when I go to select any folder). I also followed these steps from the aforementioned link (well at least I hope I did it right, I found the reference to step 4 slightly confusing):
To install with Adobe Creative Suite 4 or Photoshop CS4:
Automated installation on Mac or Windows®:
1. Select "Updates..." from the Help menu
2. Follow the on-screen dialogs to download and install the latest available Camera Raw update
Manual installation on Mac:
1. Exit Photoshop CS4 and Adobe Bridge.
2. Open the Finder.
3. Navigate to the root of the local disk (not the user's home folder).
4. Navigate to: (Please read directory carefully)
Library/Application Support/Adobe/Plug-Ins/CS4/File Formats
5. Move the existing plug-in to another location (for example, a new folder on your desktop). Ensure you keep this version in case you need to revert back.
6. Copy the Camera Raw plug-in, Camera Raw, from the download into the same folder as in Step 4.
7. Launch Photoshop CS4 or Adobe Bridge.
Is that version the right one for CS4?
Only Finder and the Canon Software can preview my .CR2 files, Photoshop still gives the message: "Could   not complete your request because Photoshop does not recognise this type of file." and   Bridge only shows me a generic RAW thumbnail. This message also appears in PS when I double-click on the Camera-RAW.plugin. I also restarted my computer, but that didn't fix it.
Can anyone help me out please? I'd urgently need a solution.
Thanks in advance!

I now uninstalled the older 5.1 version and instead installed the DNG Converter 6.3 separately and it works perfectly.
About the Camera Raw 5.6 update: I also downloaded the plug-in (which I think should be the last version CS4 supports) and can now open my .CR2 files in PS, Bridge previews them too. :-)
Is it advisable to keep both, .CR2 as well as .DNG files? Why is it that my .DNG files are lighter than the native .CR2?
Thanks again!

Adobe dng converter dng available with Capture One 7

Similar Messages

Maybe you are looking for