Should Apple punt with RAW and/or DNG support ?

Question

It seems that Apple is taking a very detailed approach to profiling cameras before adding support to Aperture. Consequently Aperture may always be later than others apps to add new camera support. Also there will always be legacy or specialty cameras deemed not worth the trouble that don't get added too. I wonder if rather than asking Apple to support every camera made past and present it wouldn't be better to punt and ask for feature changes that make it easier to integrate other RAW developers into an Aperture workflow.
Further for a few of my most valuable images, maybe 1 out of 1000, no matter how good Aperture's RAW conversion I will always want to try other RAW developers to see if they might do slightly better on a top select image. An professional app that wants to host my entire photo archive must logically offer a workflow that supports any camera past or future that I may use even once.
The tools already exist to export a master and develop it with other RAW converters also to manage different master files of the same image using stacks. All that Apple would need to do to make the unsupported camera workflow in Aperture a useable alternative is make a few minor changes to already existing features:
1. In the RAW + JPEG workflow the JPEG is the second class member. You can expose it and have it stacked with the RAW master but you have to manually make it the stack pick. Otherwise when you close the stack you see only the unsupported master file which means nothing. It's not a problem restacking one image and not thinkable with thousands of images. I haven't found a way to get around this with Automator/Applescript. MAYBE: If the JPEG were the first image in the stack then I could still use Aperture for sorting, DAM, keywords, rating, etc. and just process my unsupported images with an external application.
2. I can use Export Master to save out a master file but the process of doing that then reimporting the master file and stacking it with the original is a tedious manual effort. Again Automator/Applescript can help here but more would be needed. MAYBE: If I could duplicate a master file inside a project or stack and if Aperture had an 'Open Master file with external editor" command then it would be easy to have a duplicate master file stored by Aperture that might be used with any other RAW processing application.
3. When I use 'Export Master' now to process some images with ACR or Nikon Capture then I can reimport the TIFF file or JPEG that I create but I can't easily associate them as versions or as externally edited files with their proper masters. MAYBE: There should be a way to link master files with the rendered versions of those files created by external RAW processors.
4. I started my photographic life with film. Most current 'pros' did the same. If I want to have one home for all my photo archive then it has to support film scans of larger sizes and export them to an external editor in something other than Adobe RGB. Automator and Applescript are will make this work in v1.5 but just barely. MAYBE: Give me a way to have my hi-res film scans stored in Aperture and send them to Photoshop without compressing them to Adobe RGB or downsampling to fit Aperture's current filesize (aprox. 250MB) limitation.
I can't imagine having many different databases and apps for unsupported images from a camera I may only use once. If Apple would just streamline and tweak a few features that exist in v1.5 then Aperture could be the home to all my digital images even if some of them had to be developed by another program.
I can't imagine a better workflow than using Aperture with any of it's supported cameras. That shouldn't stop Apple from opening the door for making use of Aperture's great database and DAM features with unsupported cameras too.
Pro Mac 2.66Ghz/8GB/250GB + 1TB RAID 0 wi SoftRAID in bays 2,3/X1900   Mac OS X (10.4.8)   MacBookPro 2.16Ghz/2GB/100GB 7200rpm

Answer 1

Eric: Great, Aperture 3 might be out by spring 2010? That's only 6 months or so from now. [/sarcasm]
I appreciate the pointer to the AI article, but personally I'm more interested in whether Apple is working on adding additional RAW support for Aperture/Mac OS X any time soon, and certainly before Aperture 3 is out. Both Aperture 2 and Lightroom 2.5 are more than capable for my workflow and editing needs.
This week only added to my dismay re: Aperture v. Lightroom update likelihood and frequency; still radio silence from Apple, and Adobe releases a public beta of Lightroom 3, even as Lightroom 2 was released subsequent to Aperture 2 and has had more updates since its initial release than Aperture 2.
Brian, can you elaborate on the DNG conversion process that worked for you? Having tried every possible profile (I believe) in the latest release of the DNG Converter app, I have to say I'm skeptical that there's a setting that works with the GF1. But I'm ready to be pleasantly surprised!