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.

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.

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

I can no longer access a password protected Numbers file with the correct password. Error message only says the file "cannot be opened."

I'm using Numbers version 3.2.2.
Suddenly I cannot access my password protected Numbers file with the correct password. I have the correct password written down so I know I haven't made a mistake.
The response box that pops up says that the file cannot be opened. There are no other options for me to choose from.

Also, I tried to open it through an older version of Numbers but it sent this error message.

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

Color space support for png files

kindly suggesting :
color space support for png files, requiring the support (read/write) of the chunks: iCCP, cHRM, gAMA, sRGB

Hi ChrisT,
Thanks for the suggestion. I went to:
http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=4148...
Which is the software update page for my model. I see 10 items under Software Solutions, 8 of which are just video tutorial updates, not actual application updates (and none of those are for the Photo App). The two application updates are:
HP TouchSmart Recipe Box Application Update
HP Support Assistant Application Update
So, are you saying that PNG file types are supported in some versions of the Photo App and I don't have the correct version? Or in other words, what am I missing?
Cheers,
D

Support for Growing files (DNxHD wrapped in MXF) from EVS in Premiere Pro?

We are using Premiere CC Pro on the Mac-plattform against a shared storage soulution. We need to be able to open growing files from an EVS system to edit soccer-highlights while the matches are still playing. The problem is that the codec is DNxHD 120 and the wrapper is MXF op1a. This works fine with a QT-wrapper, but not with a MXF-wrapper. It is not possible for us the change the wrapper on the EVS system, so we need to do something on the editing side. We have tested it, and confirmed that this works fine in Final Cut Pro and Avid, but we want to use Premiere Pro. Can you provide us with a solution? Please do not say that the solution is to use FCP... ;-) Thanks in advance for all help!

Hi Peter!
Latest version. Cc 2014 with all updates.
Mac OSX 10.10.2 Yosemite.
Error during opening. As soon as the file is closed, it opens fine.
Mvh
Marius Borge
Sendt fra min iPhone
Den 10. feb. 2015 kl. 18.40 skrev petergaraway <[email protected]<mailto:[email protected]>>:
Support for Growing files (DNxHD wrapped in MXF) from EVS in Premiere Pro?
created by petergaraway<https://forums.adobe.com/people/petergaraway> in Premiere Pro - View the full discussion<https://forums.adobe.com/message/7181513#7181513>

Feature request: Slideshow module support for video files

I'm very excited about your MTS support!
Feature request: Slide show module support for video files...
Say you have 10 takes to choose from. Are you able to almost like SLIDESHOW view the 10 clips full screen so you can decide, like a playlist? Or rate them as they play? It would also be great, like SLIDESHOW to be able to export a MP4 with a title, the 10 clips you are working with, and maybe add an end title and a song, just like SLIDESHOW.
I have found editing stills like this in slideshow far faster than in any other editing program.
Basically, I just need a fast means to view or export an MP4 of a set of video clips to review. You are almost there.
great job!!!
Max

I was also disappointed that video is not supported in the slideshow module -I currently have to use another solution when I want stills mixed with videos, would be great to be ablo to keep it all in LR!

"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

Will Premiere Pro CC support Cinema DNG files?

Will Premiere Pro CC support Cinema DNG files?

That would be nice, but my guess is that if support was built in, Adobe would have made mention of it as a new feature.
Given that Blackmagic is releasing a $1000 DC camera that records CinemaDNG to SD cards, it sure would be nice if PP cold work with them natively. People, please keep filing that feature request.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Symantec Endpoint Protection (SEP) adds support for Windows 10 with 12.1.6 MP1.

Hello Everyone,
Symantec Endpoint Protection (SEP) adds support for Windows 10 with 12.1.6 MP1.For Symantec Endpoint Protection 12.1, a maintenance patch has been released on July 29, 2015. Customers will need to be current on maintenance to receive the maintenance patch update. For more information, visit our SEP 12.1 Windows 10 Knowledge Base.You can upgrade to Windows 10 with Symantec Endpoint Protection 12.1.6 MP1 installed. You must uninstall earlier versions of Symantec Endpoint Protection. The operating system upgrade stops if it detects an earlier version of Symantec Endpoint Protection.The following operating system upgrade paths are supported with 12.1.6 MP1 installed:Windows 8.1 to Windows 10Windows 8 to Windows 10Windows 7 to Windows 10For more details check the following article:http://www.symantec.com/docs/INFO2746SEP...
This topic first appeared in the Spiceworks Community

Hello,
Just to give an update. We were able to make this work but we used Symantec Protection Engine for Cloud Services instead. Also, for anyone having problems with the parameters - we used the exact same parameters listed in Peoplebooks or on the delivered virusscan.xml file, just update the IP address. We also saved the xml file on both the Portal.war and PSIGW.war directories.

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

IOS Newsstand app, add support for .folio files

Hello!
We have an iOS Newsstand app to provide our issues to our clients, and we use a PDF reader.
We would like to add support for .folio files in the app, by using a folio reader in our app.
Searching around, I've only found the specifications for the .folio files and the Adobe Content Viewer app.
Is it possible to have some more specific information on how we can make something like the Adobe Content Viewer app that we can integrate in our app?
For example how we would parse the xml files, what views/controls to use (eg. UIWebview?) etc.
Thank you very much!

Neil let clear something:
- After the .folio specification became public (with license off course) the "This really isn't possible to do" is not truth.
I believe that what people need to know is that: "Are we allowed to build a viewer?" / "Does Adobe allow programmers to give it a go?"
Before March this wasn't allowed but since the spec became public we all hope (and I believe Adobe too) that this format will have an industry standard acceptance - like the PDF. In this case many people will try to create viewers, software, builders etc.
The DPS is a great platform but VERY EXPENSIVE. Companies around the world have developed and are in a position to develop great experiences and great apps. Sharing the .folio is big and this is what we need to clear - and not the number of staff working on the DPS Viewer.
Thank you in advanced.

Support for DNG files with lens corrections?

Similar Messages

Maybe you are looking for