Did Apple remove support for DNG files generated out of Capture One?

I use Capture One to convert my Leica Dlux-4 RAW files into DNG format and then use Aperture2.1.4 as my photo processing tool.
After I ran the latest OS update - Aperture gives a "Unsupported file format" message for all the DNG files.
Is it possible that Apple removes support for photo formats in the OS updates?
Anyone encountered the same issue and found a solution?
Thx

Go in the adjustment tab, and the first thing you'll see under the histogram is "Raw fine tuning". By default, "2.0" is selected. When importing DNG, you can switch it to "2.0 DNG" this is used to read DNGs from cameras Aperture doesn't support.
Maybe the update made it go back to its default "2.0" while before you where on "2.0 DNG". If I'm right, setting it to "2.0 DNG" will fix the problem.
P.S. sorry if I said "raw precision" instead of "Raw fine tuning" in the first place. My Aperture is in French and the name in French is "Réglage de précision raw" and I did a bad translation.
Message was edited by: Manusnake

Similar Messages

Support for DNG files from Odyssey7Q.

Just upgraded my Odyssey7Q to capture 4K RAW from the FS700. Importing the DNGs into Premiere yields an extremely purple image. The DNGs import fine in After Effects.
Any chance to get this addressed in a Premiere update?

Hi Dave,
I did start the thread over on DVXUser - good to see you're working with Convergent Design on supporting their DNG files :) The odyssey 7Q is an excellent bit of kit and seems to be taking the world by storm!
Are you able to say if support for this will be in the next release and roughly when we might expect to see that?
I'm guessing we're about due for another release? Maybe for NAB time????
Cheers,
Paul.

Support for DNG files?

Will aperture ever support the Adobe generated DNG file format?

No offense and I enjoyed your comments.
Thanks
CCD or CMOS sensitivity to light is non-linear. One
step of processing a DNG is to determine whether to
linearize (i.e. decode) this specific CCD/CMOS
sensitivity to a standard value. Aperture does not
support linearize and I explain why I believe this is
so below.
There are two very different versions of DNG. The
non-linearize one is little more than a wrapper,
which is why Aperture can read these DNG's as the RAW
is embedded. Now you state rightly that DNG
converters must do more than put a wrapper on, and
that is true ... but not for this type of DNG.
The other (linearize) is an interpreted RAW within a
standardized format (wrapper). Blackpoint
compensation (subraction), scaling etc. are also
manipulable variable. Aperture cannot read linear DNG
even if the RAW is supported.
Aperture RAW support is lacking and their support of
DNG is based on non-linear.
Well, then, how do SilkyPix, Lightzone and RAW Developer manage to open non-linear DNG from cameras they don't support and interpret them very well? That's what I want CoreImage to do.
Aperture need
to be vastly better at adding RAW support or telling
us their roadmap, or providing camera manufacturers
the API or ... but something!!!
100% agreed. However, since it is part of the OS we depend on OS updates which are way too slow to follow on the camera market. Moreover, I presume the release manager has other priorities in scheduling OS X updates than those pesky photographers with their marginal second cameras. I think that's a big part of the problem. The release of a RAW update for just the EOS 400 and D80 were due to too much market pressure. It also shows Apple priorities: it is not the pro or consumer status of a camera that will decide ts priority, but only its amrket share. Sorry, but that's a mistake because professional photographers tend to have different cameras and some far less prominent than the Nikon and Canon DSLRs. This is a major win for LR IMHO.
I agree with you that this is close to useless and
the situation is untenable for professionals. Oh, my
next camera is determined by Apple? Humm.
Yes, I really wonder what they are thinking.
Why would Aperture do this? Well, I believe it is
because of their very strict definitions of
"Non-Destructive" workflow. Ans so frankly I don't
see them using DNG more fully because of their
definition. This is how I believe it plays out ...
Sorry to repeat mysel, but if they could do what SilkyPix, Raw Developer and LightZone do, it would be fine.
So although you disagreed with my prior email points
as "untrue" I hope I've clarified. A linear DNG has
been decoded by something, and that something is
proprietary and therefore the resulting DNG data
content is proprietary.
I hope to have similarly clarified what I mean by DNG support
Since RAW is already manipulated data (contrary to
some belief, it is not exactly what light fell on
what pixel but has been demosaiced at the very
least), it makes the most sense to me to have the
camera manufacturer perform the convert to DNG in
camera. That way, my negative is my one, objective
source and I can select my camera on that basis and
make my adjustments on the same basis.
I agree entirely. I think it is futile to hope for major camera manufacturers to initiate a move to DNG because their marketing department probably feel (wrongly) that it comoditize their cameras. So, it is the software industry that has to impose a standard, and DNG is the closest thing we have. And a standard for RAW is needed. In that respect, I find that Apple does the worst job in the photo-related software industry.
This does not prevent me from apeciating the other qualities of Aperture, but, he entire idea being based on RAW files, not supporting them in the first place seems stupid to me.
Cheers.

Support for DNG files with lens corrections?

Aperture 3.0.1 with the RAW Compatibility Update 3.1 now supports the lens corrections in my Olympus E-P1's native RAW format. yay!
unfortunately, since Aperture didn't support the camera for six months, I began a switch to Lightroom. consequently, I now have several thousand images that have been converted from the EP-1's native RAW format (ORF) to Adobe's so-called open RAW format (DNG). these DNGs don't load in Aperture (RAW format unsupported errors) because Aperture doesn't support DNGs with lens corrections.
Apple, can you please advise if lens corrections you support in native RAW files will also be supported in DNG conversions sometime soon? if so, I'll know it's safe to switch back to Aperture and recover the last six months of photos when the next RAW Compatibility Update happens.

Aperture 3.0.1 with the RAW Compatibility Update 3.1 does not support lens corrections. If you want lens corrections in Aperture you have to use Plugins like PTlens.
To my knowledge Aperture ignores all lens correction data in the original RAW files, just like it does with all the settings of the camera.

HT2905 Did Apple remove the Find Duplicates feature in iTunes 11?

Did Apple remove the Find Duplicates feature in iTunes 11? I don't see it in the File menu any more.

Apple says it will come back in a future update, but no time frame has been given. For now, you'll need to either find them manually or use a third-party script or utility such as Dupin.
Regards.

HT6055 Request to Apple: restore support for older codecs

I used Quicktime extensively for my research before upgrading to Mavericks, and now that these older codecs have been removed, none of my experimental videos taken over the past 5 years will play in Quicktime. This is extremely disappointing.
I'd like to gather as much user support as possible to request that Apple restore support for these older codecs.
PLEASE RESPOND ON THIS THREAD BY ADDING YOUR REQUEST FOR APPLE TO RESTORE SUPPORT FOR OLDER CODECS.
FYI, my video files were .avi format, recorded by a Nikon D300s and a Zeiss EVO 55 scanning electron microscope.

Some things can be converted without transforming the data. I have data in Excel spreadsheets that is identical to the data in the Lotus Symphony spreadsheets in which I entered the data in 1986. Converting video does involve data transformation which is undesirable unless it comes to a point where it is unavoidable. Speaking as a research scientist, one is obligated to try to preserve original data to a reasonable extent. In this case the video is not "dead". It can still be played. It's just Apple's behavior that anything older than about 4 years is old-fashioned and to be forgotten that's mandating stepping outside Apple software to do so. Yes, it would be a good idea to convert so when future upgrades mean no old codecs will play at least the data are available to some degree. I still would not get rid of the old files since they are the original data, and if the person spends 30 seconds installing VLC player they can still view the original data for another 10 years at least (if they keep the computer that long -- my computer is 12 years old and I can still run applications on it dating from the early 1990s).
By the way, you can still buy VHS players. I agree they will not be around forever, and if it's a family video you want to play 20 years from now then you may as well convert it now, but then that's not research evidence.
Optical media are dead at Apple, but still extensively used outside Apple. I agree in 20 years it will be hard to find a DVD player but visit right now any store selling movies or music, or a public library, and optical media are still around. Apple can force the issue where their hardware is involved, especially as regards to installing Apple software, and of course by pushing online media sales (if you buy from the iTunes Store, which I don't).

I woke up this morning and my Bookmarks is working different. Has a setting changed, or did Apple change it for me and how do I get it back?????????

I woke up this morning and my bookmarks are functioning different, and the tool bar has changed. Instead of opening the bookmarks in a page on Safari, I get a menu on the side of the page. Then I have to go click on the bookmark icon again to get rid of the menu. Has a setting changed or did Apple change it for me and how do I get it BAAAAAAACK????????????

The first G4 models were basically a repackaged/upgraded G3 & came in 350 & 400MHz models. This design was called PCI version. The next G4 models were AGPs. This link http://www.everymac.com/systems/apple/powermac_g4/index-powermac-g4.html has the specs/pictures of all the G4 models.
Power Mac G4: How to Differentiate Between Models
http://docs.info.apple.com/article.html?artnum=58418
Power Mac G4: How to Differentiate Between Models (Part 2)
http://docs.info.apple.com/article.html?artnum=42739
Using these links, you should be able to determine which model you have.
Removing the battery causes all settings in the internal memory to be reset, just like resetting the PMU/CUDA. See Mac PRAM, NVRAM, CUDA/PMU & Battery Tutorial
 Cheers, Tom

Why is there no support for RTF files in Pages?

Why is there no support for RTF files in Pages?
This is nuts!

You are not alone.
Actions speak louder than words, but Apple does manage to still distract many from what is self evident before them.
I am astonished by those who swear that non-existent features, or features that pre-exist the current version make Pages 5.2 a major upgrade.
An affect that does seem to wear off with familiarity, as each version of Pages 5 gets a boost in the App Store, only to see the disapproval rating surge back again.
Pages was always one of the top purchases in the App Store, now it doesn't even rate.
Peter

OS X support for offline files

Dear all,
I have a mixed environment of workstations running both OS X and Windows that connect to file shares hosted on Windows file servers. In order to be able to manage the storage space effectively, tape based archiving was implemented using Symantec's Enterprise Vault for File System Archiving. EV and many other archiving solutions use the Windows Offline file attribute to mark a file that has been archived off and install a filter driver into Windows so that archived files can be recalled directly from Windows Explorer without requiring additional software (this is also known as a reparse point). Please note that this is different from how Microsoft intended offline files to be used for synchronising between a roaming laptop and a network share (see KB 312717).
OS X does not have any support for offline files natively, both for how Microsoft intended it to be used and for use with archiving software as a reparse point. There are a couple of offerings on the market which add the required functionality to OS X, but recent updates to OS X have rendered these offerings non-functional:
10.6.7 - I understand that Apple replaced the SMB/CIFS modules with their own code. At this point, it no longer became possible to recall archived files using said software offerings, when connecting to a Windows file server via SMB. See Apple bug ID 10836961.
10.7.4 - a kernel update is included which means said software offerings are now not able to block the icon preview in Finder. The icon preview in Finder causes archived material to be recalled which we do not want it to do (imagine the problem when using tape as the archiving platform - this will cause a huge recall job on the tape drives)
This is going to cause significant difficulties as it effectively means that we can't use archiving with OS X to manage our storage costs.
I'm writing this as I'm hoping that someone will know of a product or solution that is able to work around the 2 difficulties noted above, or that someone from Apple is going to read this and realise that this is a serious problem. The ideal that is required is to add support for the offline files, in particular reparse points, directly into OS X.
Many thanks.
A frustrated storage engineer.

Hi Richard,
We are looking at file archiving here and have the same potential issues. We haven't evaluated this product, but it claims to solve the problem:
http://www.grouplogic.com/enterprise-file-sharing/mac-file-archiving-system/
Good luck
Mark

Why did Apple discontinue iPhoto for iOS?

Why did Apple discontinue iPhoto for iOS?
This app offered great features such as the ability to format your pictures and journal and, add comments and context.
It's disappointing to be forced to migrate away especially when this is a paid app ($4.99). Many other companies may stop supporting paid apps, but at least you can still use the apps.

Apple did not say why, so we can only speculate.
But have a look at what has changed in iOS 8. http://www.apple.com/ios/developer/
The basic frameworks, that support image editing apps and any graphics apps have been completely replaced by newer frameworks, for example PhotoKit. Also, the Photos.app and its library are very different, with the Camera Roll being replaced by the "Recent Activity" album.
iPhoto used "Photos" to access all photos on the device and did not them separately. The code would have needed to be completely rewritten. Probably, Apple did not want to develop iPhoto a second time, in addition to the new "Photos", but is relying on the third party developers to supplement Photos with extensions:
PhotoKit
Developers can enable their photo apps to edit photos directly in the Camera Roll without having to import them first.
Photo Editing
Developers can embed their filters and editing tools directly into the Photos app. So you could apply third‑party effects to images without leaving the app where you view your photos.

Where is Aperture support for raw files from Leica X Vario?

Where is Aperture support for raw files from Leica X Vario?

It doesn't appear to exist, at this time:
http://www.apple.com/aperture/specs/raw.html

"Embedded" camera profile for .dng file?

Why does Lightroom 5 show "embedded" as an option for camera profile for .dng files created by my pentax k-30? I thought that "embedded" profiles did not apply to .dng files?

A JPG can contain color profile data not just a reference tag containing the name, although other Google results indicate that the APP2 segment is only has 65533 bytes of data and if the profile is too large for that then it is either chunked somehow or written into an XMP segment:
http://docs.oracle.com/javase/6/docs/api/javax/imageio/metadata/doc-files/jpeg_metadata.ht ml#color
“If the ColorSpace of the image is based on a non-standard ICC Profile, then that profile is embedded in an APP2 marker segment. If the ColorSpace is not based on a non-standard ICC Profile, but an app2ICC node appears in the metadata, then an APP2 marker segment is written with the appropriate standard profile. Note that the profile must specify an RGB color space, as the file must be JFIF compliant.”
EXIFtool can extract and embed a profile:
http://cpanforum.com/threads/2873

Why O Why did Apple removed the sidebar colors?

Why O Why did Apple removed the sidebar colors in the new Aperture update? I used those colors to organize my workflow.
Everything is Greyscale now. Isn't Photography all about colors? If I wanted a greyscale user interface I would have bought a PC ...

It's the new design since Lion - Iphoto already has gone gray before Aperture See these links:
Re: After updating to Aperture 3.3 all my icons appears in Black and white. This includes the inspect button, photo stream button, the Facebook / flicker share button. Could you please help here ?
How to bring back the color: (for experienced users only)
Re: Have today loaded the 3.3 up date on Aperture. After the up date the colour of the Menu Bar and all icons showing projects / albums etc are now grey. Any thoughts on how to reestablish the colours.
Regards
Léonie

How to add support for new file type.

Using the ESDK, I would like to add support for new file type ( a new extension). this new extension will function like any other non visual code editor but will have specific syntax highlighting, code folding and explorer.
I am trying ot figure out if I need to create a new editor or use existing JDeveloper code editor and add support for new file type. Does anyone have a high level outline on how to do this using the ESDK that is specifically targeted at adding new file type support for a text based code editor?
I have looked at the Samples and keep going in multipe directions. It would be cool if there was an example that was how add syntax higlighting for new file type.
Thank you

Brian, thank you. I looked at this extension and it answered a lot of questions for me. I was going in the right direction but needed a little help and bost of confidence, this is just what I needed. I created the LanguageSupport, LanguageModel, Addin, Node and TextDocument that are specific to the new file type. I was getting hung up on how to hook this into the JDevelpoer editor. I keep thinking I have to create a custom editor but it looks like I don't have to and it looks like I can associate this file support with the editor framwork, for version 10.1.3.2, with the following in the Addin Initilize() method.
Recognizer.mapExtensionToClass(MY_EXTENSION, MyNode.class);
CodeEditor.registerNodeType(MyNode.class, MY_EXTENSION);
LanguageModule.registerModuleForFileType(new MyLanguageModule(), MY_EXTENSION);
I have done this but still not able to recognize the new file type.
At this point, I just want to be able to recognize the new file and display it's associated icon or display a messare to the message log. I put a System.out.println("test") in the Initilize() method of my addin. then I registered MyAddin in the extension.xml. JDeveloper sees this new extension and it is loaded but I have not been able to show the test message or display the new icon when I open the new file type.
extension.xml
<?xml version="1.0" encoding="windows-1252" ?>
<extension xmlns="http://jcp.org/jsr/198/extension-manifest"
           id="teisaacs.jdev.myext.MyAddin" version="1.0.0" esdk-version="1.0"
           rsbundle-class="teisaacs.jdev.myext.resources.MyResBundle">
    <name rskey="EXTENSION_NAME">My Code Editor</name>
    <owner rskey="EXTENSION_OWNER">Me</owner>
    <dependencies>
        <import version="10.1.3">oracle.jdeveloper</import>
    </dependencies>
    <hooks>
        <jdeveloper-hook>
            <addins>
                <addin>teisaacs.jdev.myext.MyEditorAddin</addin>
            </addins>
        </jdeveloper-hook>
        <feature-hook>
            <description>My Code Editor</description>
            <optional>true</optional>
        </feature-hook>
        <document-hook>
            <documents>
                <by-suffix document-class="teisaacs.jdev.myext.model.MySourceDocument">
                    <suffix>my</suffix>
                    <suffix>MY</suffix>
                </by-suffix>
            </documents>
        </document-hook>
        <editor-hook>
            <editors>
                <editor editor-class="teisaacs.jdev.myext.editor.MyEditor">
                    <name rskey="EXTENSION_NAME">My Editor</name>
                </editor>
                <mappings>
                    <mapping document-class='teisaacs.jdev.myext.model.MySourceDocument">
                        <open-with editor-class="teisaacs.jdev.myrext.editor.MyEditor"
                                   preferred="true"/>
                        <open-with editor-class="javax.ide.editor.CodeEditor"/>
                    </mapping>
                </mappings>
            </editors>
        </editor-hook>
    </hooks>
</extension>
public class MyAddin implements Addin {
    public static final String MY_EXTENSION = "my";
    public void initialize() {
        System.out.println("MyEditor Constructor");
        new MyLanguageModule();
        Recognizer.mapExtensionToClass(MY_EXTENSION, MyNode.class);
        CodeEditor.registerNodeType(MyNode.class, MY_EXTENSION);
        LanguageModule.registerModuleForFileType(new MyLanguageModule(), MY_EXTENSION);
}I have added and removed the editor hook along with many other modificaitons to the extension.xml but still not recognizing the new file extension.
Todd

After updating my IOS TO 8.1 (12B411) on 10/23/14, I went to update my blood sugar level in the IHealth app. And now after the new IOS update I'm unable to find the blood glucose option in the IHealth app. Did Apple remove it or just mess up AGAIN?

fter updating my IOS TO 8.1 (12B411) on 10/23/14, I went to update my blood sugar level in the IHealth app. And now after the new IOS update I'm unable to find the blood glucose option in the IHealth app. Did Apple remove it or just mess up AGAIN?

Apple removed blood glucose until further notice. The reason behind this is that it gave a distorted picture in countries where the medical world used other measuring units. I suspect it will be available again in a future update.

Did Apple remove support for DNG files generated out of Capture One?

Similar Messages

Maybe you are looking for