Skip to Content/article-new/2012/05/iphoto_icon.jpg?lossy "iphoto_icon.jpg"){kind=icon}
Apple today released Digital Camera RAW Compatibility Update 3.14, bringing RAW image support to Aperture and iPhoto for several new cameras.
This update adds RAW image compatibility for the following cameras to Aperture 3 and iPhoto '11:
- Canon EOS Rebel T4i / 650D / Kiss X6i
- Sony Alpha SLT-A37
Full details on RAW support are included in an Apple support document.
Digital Camera RAW Compatibility Update 3.14 checks in at 7.9 MB and requires Mac OS X 10.6.8 or OS X 10.7 or later.
Apple Fitness+ and Peloton offer polished workout routines delivered by enthusiastic instructors and accompanied by motivating music playlists.
Rumored design changes include shorter stems like current AirPods Pro, but without advanced features like active noise cancellation.
Updated AirPods Pro could see some design changes like elimination of the stem.
Tile-like Bluetooth tracking device designed to be attached to items like keys and wallets, letting you find them right in the Find My app.
Top Rated Comments
RAW means everything from the Image Sensor is saved, and it's completely lossless, Jpg is for lulzy tards, Raw is the future.
----------
Exactly!
Why don't they implement dynamic updating capabilities (i.e. maintaining a constant connection to the update server for these updates, so the user doesn't have to concern themselves with manually installing, and they install automatically when iPhoto/Aperture is re-launched)?
Add upon that what they do for printer drivers, when one is connected, detect what kind it is & download the appropriate software. This way, you don't get the software for boatloads of other cameras.
So assuming that you get a RAW image format, with some magic byte file header (your OS doesn't know anything about it yet) and some random extension *.foo.
Now your OS could ask you each time it discovers such a file format it doesn't know nothing about it - and in fact, OS X does just that, too! - e.g. by looking up *.foo in some global database and offering you the appropriate app in the App Store. And/or recognise in some magic way that *.foo is in fact an image format and that you're better off with the appropriate image IO plugin (such that any Cocoa application is able to open that file!) instead.
Or you just get a bunch of common RAW format plugins once in a while and be done with that. Don't get bothered each time you try to open a *.bmp ("I don't know about this image format yet, but there is an image plugin available. Do you want me to download it?"), *.tiff ("I don't know about this image format yet, ..."), *.jpg ("I don't know..."), *.pef ("... do you really want me to...") or *.dmg ("... Really, I could just download the appropriate plugin just now...!").
Or do you really care how many USB device drivers are lingering on your OS X installation which are likely to never be used by any hardware, because you simply don't own such a device, and never will? Ever wondered why OS installations are counted in Gigabytes (YES, that's 1024 MEGAbytes!) these days? I remember times when an OS was delivered on 2-3 floppy disks (those had capacities counted in KILObytes...). Oh and yes, almost every device required you to install the device driver yourself by hand...
Well, yes, one could care about waste of disk space - but do we really care? :rolleyes: We just became to lazy and expect an OS to immediatelly recognise and support the connected device - or open the given camera file "out of the box".
Cheers
----------
Ever wondered how many other device drivers are burried in your OS X installation, for devices that you'll never be a proud owner of? :D
Besides, image plugins don't require you to actually own a camera of that format! There are other situations where one might want to display/edit such a RAW image - well, maybe not you personally anyway...