Aperture support for unsupported raw formats

I was doing some tests with Aperture to see if it could fit my workflow. My concern was support of old files from a Nikon Coolpix 5400, raw (thanks to firmware update at the time) as well as a recent Nikon DSLR. No problem with the DSLR. 5400 was not supported. After some internet research I found out there is a pref file (Raw.plist in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources) that has info about all supported cameras. This add raw support for the cameras listed in the file for Preview, iPhoto, Aperture (system-wide). Same list that Apple provides as camera compatibility list.
In that list I chose to duplicate the NIKON-E8400 array and renamed it NIKON-E5400. Didn't change any value in the array. To my surprise, even without rebooting, this added support for the Nikon Coolpix 5400 images. The image looks pretty much the same with these default settings (when opened in Preview for example) than it does in ACR in CS2. The only odd difference is the image size loosing 10 vertical pixels (from 2592x1944 opened in ACR CS2 to 2592x1934). I have no idea why it does this but it is no big deal really as it is no scaling, just loss of pixels.
I am a bit concerned of course about the possibility to carry on this tweak in the next OS updates.
I guess any raw from any camera could have support this way.
Just need to name the array in Raw.plist properly. For mine I just opened a raw in text edit and saw first line the name of camera, was "NIKONE5400". I compared the format of this name to other names in the array and decided to add the "-" to look like others so "NIKON-E5400", and that was it. Now I was lucky the default setting for the 8400 I used as a base worked for the 5400, apparently. It could have not been the case and then I would have had to play with the values in the array. Quite a few so a long process I am afraid, but possible.
The deal would be to release a little utility software that would let us play with these values easily and see a result live on a sample image, and once satisfied it would modify this Raw.plist file. This way people could add support to their own raws.
If anyone in the know sees a big issue in doing what I did please tell.
Of course playing with this Raw.plist file is at your own risks so keep backup and bee careful.
The tweaking of this raw.plist file had been talked about in different forum in the past concerning the support of Canon 3xxD that had a different US name Rebel something. The change of name of the corresponding array added support before an OS update did it for everyone.

I also modified my Raw.plist file to import RAW files from my Olympus C-5050Z. But that doesn't make Aperture import a type of RAW file it didn't support before. It just turns out that your Nikon 5400 RAW files are the same format as the Nikon 8400 files except for size, just as my Olympus C-5050 files are substantially similar to the Olympus C-7070 files. I think the Raw.plist file used by ImageIO contains hints on how to treat the data and color in the images and as long as the cameras don't behave too differently, substituting one model with another will work.
The RAW.plist file is a standard plist file that can be examined and modified with the Property List Editor. What I would like to see is documentation of the parameters so that we can more easily add support for cameras that aren't supported out of the box.
MacBook Pro Mac OS X (10.4.7) 2.16GHz 2GB RAM 256VRAM

Similar Messages

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

Workflow for unsupported RAW files

Aperture doesn't recognize RAW images from my Leica D-Lux 2 so I will need to use ACR to convert the files. I'm wondering what other people have set up in terms of workflow for unsupported RAW files. I'm thinking I will have to open in PS, convert, save as TIFF, and then import into Aperture--keeping the original RAW files classified somewhere on my hard drive. Anyone have a better workflow idea?

Aperture doesn't recognize RAW images from my Leica
D-Lux 2 so I will need to use ACR to convert the
files. I'm wondering what other people have set up in
terms of workflow for unsupported RAW files. I'm
thinking I will have to open in PS, convert, save as
TIFF, and then import into Aperture--keeping the
original RAW files classified somewhere on my hard
drive. Anyone have a better workflow idea?
If you like using ACR this is a great thread for how to do so easily:
http://discussions.apple.com/thread.jspa?threadID=260641&tstart=0
I myself am in the same boat (unsupported RAW), what I've been doing is saving 16-bit TIFFS from my RAW editor and importing those into Aperture. I just batch convert first and load them in all at once.
When Linear PNG's are supported that is the option I will favor for import I think (until my camera's RAW format is supported, but I think linear RAW will come first).
Powermac G5 1.8GHz DP Mac OS X (10.4.3) Radeon 9800 Pro Mac Special Edition, dual monitors

Aperture support for Nikon 1 AW 1

Is there Aperture # support for Nikon 1 AW 1 .nef file format??

Frank
The AW 1 became available about the first of November.
I'm running Aperture 3.5, OS X Mavericks 10.9, and Digital Camera RAW Compatibility Update 5.01
What is surprising is that I understood that the AW 1 contained the same sensor etc of the V2. It was the waterproof shockproof body that was the big change.
Thanks for the quick response.
Bill

Does Photoshop Elements 13 support Nikon D7100 Raw format?

Does Photoshop Elements 13 support Nikon D7100 Raw format?

Yes.
Try for free foe 30 days from this link and validate with your 24 digit serial number if you then decide to buy - click here for PSE downloads

Will ACR support the different RAW formats of digital cinema cameras like REDCODE or ARRIRAW?

Will ACR support the various formats produced by digital cinema cameras like REDCODE, ARRIRAW and the other ones?
Support for Cineform RAW would be also welcome of course.
The RAW converters supplied by the manufacturers are no comparison IMHO to what ACR offers in terms of sheer image quality, tonal control (especially highlight recovery and rolloff) simple usability and lack of stuff like lens correction just to mention the most important things.
Coming from a photo background I would love to be able to process everything in ACR as a first light correction. :-)
I don't know if this is just a question of implementing it, maybe there are legal reasons aswell why REDCODE for example isn't supported?

Jim, I know ACR was designed to be a still image RAW developer, but it would be a waste not to use it for many still images (a video is not more than that).
But since more and more video cameras are capturing RAW data a debayering suite like ACR will be necessary for video too. Instead of having an importer for every file format, ACR could substitute them with its superior quality and controls, since it already has almost everything that is needed for processing RAW video it would be unwise not to use it (I see use for compressed video from DSLRs for example too).
The only things that I can see that need to be changed are the denoising (needs a good temporal option aswell) and the ability to scrub through a clip and the possibility to create keyframe for the development settings.
I use ACR for timelapse (video) all the time, apart from the slow processing speed (which won't be a problem with future computers) basically everything is already there.
The next step would be directly apply rotobrushes to the RAW data, but even with a computer with the speed you would expect in a couple of years that is probably a bit farfetched (taking into account, that resolution will also at least slightly increase for video).
Premiere should have gotten still frame ACR support with CS6, some might even argue that it should have been in PP since CS5.5.

When will Aperture support Fujifilm Xpro1 raw files??

Does anybody knows when will Aperture support Fujifilm Xpro1 raw files?? It have been pendning for a while already, really hope there will be an update soon. Thanks.

I firmly disencourage people to purchase Aperture these days.
To everyone asking me for advise as a Pro photographer.
Apple attitude on this issue is of abandonement and ignorance of users needs.
Unfortunately, the feeling is that this is going to be the permanent standard.
They are not providing translations, not providing support to models such as X-Pro1 that has received inmediate reaction from major developers, neither do care for users that openly claim for RAW support for an extended model as X-10.
This is somehow another sign of apple arrogance in term of market predominant coompany.
If Apple do not begin to lose sales and an importan market share this is going to be worse and worse.
Best way: Ignore Aperture.
Adobe is nowadays the ONLY option for photographers.
I don't like Lightroom so I must select my shots with Photo Mechanic, or Xnview and then go to photoshop.
Sick of Apple.

Just bought a Nikon d750 and confused about adobe LR4 and PS6 support for the RAW files. I have DNG 8.7 but wondering if LR and PS will import direct soon Thanks for any advice

Just bought a Nikon d750 and confused about adobe LR4 and PS6 support for the RAW files. I have DNG 8.7 but wondering if LR and PS will import direct soon Thanks for any advice

Support for the Nikon D750 was introduced in the latest version of LR 5.7 and ACR 8.7 on Novemder 18th 2014.
Further updates to LR 4 were stopped when LR 5 was released on June 9th 2013. No further updates for bug fixes and new camera support.
Nada, LR 4 will never support Nikon D750. The Nikon D750 was introduced into the market in September 2014 some 15 months after further development of LR 4 was discontinued.
You can use the Adobe DNG program (free download for the package) to convert the Nef (raw) files from your Nikon D750 to the Adobe DNG format which will permit you to import those into LR 4. This is the crutch provided by Adobe to allow for the processing of raw files with outdated versions of LR and ACR.
You can also update the ACR plugin for PS CS6 to version 8.7 which can also work with the raw files from the D750. For direct support in Lightroom you will need to upgrade (paid) to version 5.7.

Ld: file was built for unsupported file format...for architecture armv7

hi:
I recently developed a project with custom ANE and I get this error msg when compile ipa since I upgraded the sdk from 3.5 to 3.8.
ANE compile CMD:
adt -package -storetype pkcs12 -keystore ane.p12 -storepass 1234 -target ane yund.ane extension.xml -swc yunding.swc -platform iPhone-ARM -platformoptions platform.xml IDS.framework library.swf libIslandIDSANE.a
platform.xml:
<platform xmlns="http://ns.adobe.com/air/extension/3.5">
     <sdkVersion>6.1</sdkVersion>
     <linkerOptions>
                    <option>-w</option>
        <option>-ios_version_min 4.2</option>
                    <option>-framework Foundation</option>
                    <option>-framework StoreKit</option>
                    <option>-framework AdSupport</option>
                    <option>-framework QuartzCore</option>
                    <option>-framework UIKit</option>
                    <option>-framework CoreGraphics</option>
                    <option>-framework SystemConfiguration</option>
                    <option>-framework Foundation</option>
                    <option>-lz</option>
     </linkerOptions>
             <packagedDependencies>
                    <packagedDependency>IDS.framework</packagedDependency>
          </packagedDependencies>
</platform>
msg:
ld: file was built for unsupported file format ( 0x56 0x65 0x72 0x73 0x69 0x6f 0x6e 0x73 0x2f 0x43 0x75 0x72 0x72 0x65 0x6e 0x74 ) which is not the architecture being linked (armv7): C:\Users\timoo\AppData\Local\Temp\139d9782-79fd-422a-8c15-da1da2da8c53/IDS.framework/IDS for architecture armv7
Compilation failed while executing : ld64
help me
thx

Have you Found the way to solve this problem yet?
I have got the same problem. Here is the error log when building the IPA:
ld: warning: ignoring file /var/folders/c0/m8m1_z5915qblkj9d_7jhmcw0000gn/T/3cb383e9-0092-4b1c-909f-5c219b2fbcd4/Par tytrack.framework/Partytrack, file was built for unsupported file format ( 0x56 0x65 0x72 0x73 0x69 0x6f 0x6e 0x73 0x2f 0x43 0x75 0x72 0x72 0x65 0x6e 0x74 ) which is not the architecture being linked (armv7): /var/folders/c0/m8m1_z5915qblkj9d_7jhmcw0000gn/T/3cb383e9-0092-4b1c-909f-5c219b2fbcd4/Par tytrack.framework/Partytrack
ld: warning: CPU_SUBTYPE_ARM_ALL subtype is deprecated: /Users/apple/Documents/flexsdk/flex3.9/lib/aot/lib/libDebugger1.arm-air.a(avmplusDebugger .cpp.o)
Undefined symbols for architecture armv7:
"_OBJC_CLASS_$_Partytrack", referenced from:
      objc-class-ref in libcom.haibin.extension.PromotionAPI.a(partyTrackAPI.o)
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64
My platformoption.xml content is：
<platform xmlns="http://ns.adobe.com/air/extension/3.8">
    <sdkVersion>7.0</sdkVersion>
    <linkerOptions>
        <option>-ios_version_min 4.3</option>
        <option>-framework CoreData</option>
        <option>-framework UIKit</option>
        <option>-framework Foundation</option>
        <option>-framework Security</option>
        <option>-weak_framework AdSupport</option>
    </linkerOptions>
    <packagedDependencies>
        <packagedDependency>Partytrack.framework</packagedDependency>
    </packagedDependencies>
</platform>
And my build command are:
<target name="package" description="Create the extension package">
<exec executable="${FLEX_HOME}/bin/adt" failonerror="true" dir="${basedir}">
<env key="AIR_SDK_HOME" value="${FLEX_HOME}"/>
<arg value="-package"/>
<arg line="-storetype pkcs12"/>
<arg line="-keystore testkey.p12"/>
<arg line="-storepass 123456"/>
<arg line="-target ane"/>
<arg value="../${ANE_NAME}.ane"/>
<arg value="extension.xml"/>
<arg line="-swc ../swc/${ANE_NAME}.swc"/>
<arg line="-platform iPhone-ARM -platformoptions platform.xml -C ../iPhone-ARM/ . "/>
<arg line="-platform Android-ARM -C ../Android-ARM/ ."/>
<arg line="-platform default -C ../default/ ."/>
</exec>
</target>
File "Partytrack.framework " is in the directory "iPhone-ARM"

HT201071 Please add support for Camera RAW Canon PowerShot G2

Please add support for Camera RAW Canon PowerShot G2,
it may be ancient, but there are still a lot of G2s out there, and it's annoying to have a different workflow for pictures from them...
best,
case

You are not writing to Apple here. This is a user to user help forum.
Instead, send your comments or suggestions directly to Apple via Mac OS X Feedback.
You are unlikely to get a direct response from your "Fedback", but you can be certain that the responsible Apple people will see your input for consideration in future product development.

Captivate 3 support for Open Document format?

Hi,
Does anyone know about support for Open Document Format in Captivate 3? (OpenOffice presentations)
Is it possible to save OpenOffice presentation in open document format or does it have to be saved as microsoft power point file?
What about Captivate 4? Any improvement?

On the OpenOffice.org site, look under projects, and there's an Open Document Toolkit for Java. I've no idea of its status though.

Aperture support for fuji X-T1 raw files

How quickly does aperture update for raw files for a recently released camera?

Thanks for the link, William. However, from the Aperture site, they don't seem to be in any hurry. The X-E2 isn't even listed there. It's hard to know which direction to go with Adobe costing so much more than it used to. Since I use layers and masks quite a bit, I need to update my raw converter, since I use CS5.

How to handle an unsupported RAW format (Canon EOS T2i/550D)

I just got the Canon EOS T2i Digital Rebel today. I wasn't expecting Aperture to support its RAW files yet and it doesn't. My plan is to shoot RAW + JPEG until RAW support arrives. I've noticed some strange things happening during import. At first only a few files showed up in the import window. Checking/unchecking the import duplicates box did nothing. Eventually somehow all the photos showed up. I couldn't tell you what I did that made any difference.
The camera writes separate CR2 and JPG files to the card. The first time I imported I set the RAW + JPEG Pairs setting to "Both (JPEG as Master)". For some reason only the CR2 was imported and as expected it showed the unsupported icon. I couldn't see any JPEGs. I did the import again and now all the files are there but the CR2 and JPEGs are not linked in any way. I guess I don't understand how this should work.
Does anyone have any experience with RAW+JPEG shooting?

On a retry, the import seems to be working correctly with RAW + JPEG pairs. The first time I tried this I was using an SD card formatted and used (with images on it) from a Canon EOS T1i. Maybe that was confusing Aperture.
I formatted the card with the T2i, reshot some images and re-imported with the setting of Both (JPEG as Master). The imported images have the "J" badge which means RAW + JPEG pairs with JPEG as master. If there was an "R" badge it means the RAW file is the master. When you right click the images there's a new menu entry for "Set RAW as master". Selecting that menu item shows the RAW file with the unsupported image icon.
Once Apple delivers RAW support for the T2i I can just select the "Set RAW as master" menu item to start using the RAW file.

KonicaMinolta D7 - no support for ".MRW" raw

There does not appear to be any support for the KonicaMinolta D7 ".MRW" raw format. Support is available in iPhoto.
Does Apple intend to provide support for this product in Aperture?
PM

This is more of a reply to the thread then just the first poster.
First, the D7 is a different camera then the 7D, confusing isn't it.
Further more their is also the newer 5D.
All have the .MRW format.
Pre 10.4.3 OSX supported .MRW files from on of minoltas non-SLR cameras. 10.4.3 added the 7D support.
The problem with OSX is it doesn't support formats in a logical way. The problem here is the same as the problem with the Canon Rebel XT/350D . Basically instead of seeing it as a .MRW and giving it a go. It looks to see what camera it came from in the meta data, if not on it's pre-selected list, OSX rejects the file, even if in reality if it tried, it would open it right up. Also not unlike how Aperture won't run on lots of hardware, but it's just because the app has a list saying what it will and won't run on, not anything based on actually trying to run. Thus why aperture is locked out of FX5200 video cards and power mac G4s for no real reason.
Anyways, you can go in and find the Raw.plst and add a entry for some cameras not supported and poof, they work.
If you own a KM 5D, which is just a smaller cheaper re-package of the 7D, by default OSX won't work with it, or DNG files made from it. But if you go in and add a entry for a 5D, (just copy the 7D entry and change the name) poof, things start working. I was able to get it to at least open DNG files made from 5D files by doing this. No luck with the MRW files yet. I don't have aperture to see if for some reason they will work there. Aperture uses the same foundation as the rest of the OS for open raw and dng files.
With some luck in the future apple will change this practice and just have OSX see a file as its raw format, not as what device if came from, and give it a honest effort to try and open it, not just ignore it because it's not on the magical list.

Support for DXO DNG format

I recently upgraded to Version 4.1 of the DxO package and it seems that images saved as DNG's by DxO are not supported by Aperture. Has anybody else had this experience and does anyone know if this is likely to change?

Hi Tony from London, Brit in exile here!
If the camera RAW is supported by Aperture, then the DNG should be ... provided it is saved in DxO as "non-linear."
My assumption (and assertion to a degree) is that Aperture's non-destructive RAW workflow means they idealize starting with RAW. Non-linear DNG is essentially RAW in a different (and standard) file format.
Linear DNG has been decoded by a 3rd party utility and therefore does not fit the Aperture "non-destructive" RAW dictat.
BTW, to test this, compare a linear DNG out of ACR with that from DXO. I am pretty darn sure you will see differences. All RAW converters are proprietary, whcih is their value prop. of course. But they are different and the output results are different.
Assertion time. Equally, consider running the same RAW image through DXO in the future. Assuming DXO has updated its sw, my assumption is the resulting DNG will look different (hopefully even better). Oh, the digital negative from DXO version x is not the same as that from version y? Can I therefore consider it my negative?
So my suspicion is that the Aperture team determined they would look after the RAW, and never ever touch it. This allows updated RAW conversion (v1 or v1.1 so far) to be run or re-run at a whim and for us to decide which to use.
G.

Aperture support for unsupported raw formats

Similar Messages

Maybe you are looking for