Slashdot Mirror


Linux Alternatives To Apple's Aperture

somethingkindawierd writes "An experiment focusing on open source tools for Ubuntu Linux to compete with Aperture on the Mac. The author didn't think he would find a worthwhile open source solution, but to his surprise he found some formidable raw processing tools. A good read for any Linux fan or photographer looking for capable and inexpensive tools"

271 comments

  1. Linux alternative to aperture: by A+beautiful+mind · · Score: 4, Funny

    Hi, I'm GlaDoS, how may I help with your photo proooooocess-ss-ing needs?

    --
    It takes a man to suffer ignorance and smile
    Be yourself no matter what they say
  2. It's too bad Adobe got their hands on RawShooter by DanWS6 · · Score: 4, Interesting

    So far it's the best tool I've found. It's lightweight and very fast. I love how easy it is to adjust the exposure and color temps. It's easy to find blown highlights and get rid of them. The downside is getting it to work with my new XSi was a pain. I had to use a hex editor on the executable and convert my CR2 files into DNG files. The extra steps are annoying. I tried out Lightroom, but there's no way I'd pay $300 for that bloated crap. I'm definitely going to check out rawtherapee.

  3. Here's a Summary! by Kamineko · · Score: 5, Informative

    F-Spot, The default photo editor that comes with Ubuntu 8.04, was quickly discarded. [FOSS]

    Picasa, Really liked the application overall. I crop all my photos to the golden ratio of 1.62:1, so this limitation is unacceptable. [NOT FOSS]

    LightZone, very similar to both Aperture and Adobe's Lightroom. Costs $200 and is not open source. No online support forum.
    Bibble, very fast and it only costs $130. It does not however have any photo-management capabilities. No tagging, project management, or meta data editing. [NOT FOSS]

    Raw Therapee, raw photo processor, free. It does not, however, run on Mac OS X. Does not manage projects. And it does not work with anything but raw photos, so it will not allow for processing jpegs or tiffs

    Qtpfsgui, another useful application. HDR tool for Ubuntu Linux, Macintosh, and Windows.

    The result:

    There isn't an all-in-one package that will do the trick, but by combining Ubuntu's file manager Nautilus for project management, Raw Therapee for raw processing, and the Gimp for non-raw processing, just about everything I do in Aperture can be done on Ubuntu Linux using free and open source solutions.

    1. Re:Here's a Summary! by E+IS+mC(Square) · · Score: 3, Informative

      The discussion is not about specific photo editing tools, its about managing workflow (organizing, tagging, editing raw as well as compressed pictures). Author did mention GIMP, and intends to use it as part of his workflow.

      As far as GIMP interface is concerned, let's just say its different than, er, Photoshop. It has been discussed and beaten to death already anyways, and offtopic here.

    2. Re:Here's a Summary! by Anonymous Coward · · Score: 1

      How about Digikam? I like it for basic photo management and then I open in Gimp for more advanced editing. Seems to work pretty smoothly for my needs.

    3. Re:Here's a Summary! by Anonymous Coward · · Score: 0

      What about it? RTFA and you will see that it is mentioned in the conclusion.

    4. Re:Here's a Summary! by Anonymous Coward · · Score: 4, Informative

      The GIMP is disqualified for not being like Aperture at all, but like Photoshop.

      Aperture and its Adobe competition, Lightroom, are metadata-based editors with very powerful RAW processing engines. They draw upon the power of metadata for everything from nondestructive editing (pixels are not touched until export) to project organization (through EXIF data and IPTC keywords).

      They also both use a streamlined, task oriented interface, instead of the random collection of tools that is GIMP or Photoshop. Some "power user tips" that take a long sequence of steps in GIMP or Photoshop have been intelligently condensed into single sliders in Aperture and Lightroom, for easier use by everyone.

      GIMP is still basically a destructive pixel pusher, like Photoshop. I don't think it has any RAW capability unless you tie it to dcraw. Therefore GIMP does not play in this sandbox.

      Someone once said that the failure of Open Source office suites was their slavish imitation of Microsoft Office, and that what was really needed was a fresh new approach. The same could be said of why GIMP fails against Photoshop. The fresh new approach is being provided by Adobe and Apple's metadata-based image editors.

    5. Re:Here's a Summary! by Em+Adespoton · · Score: 3, Informative

      I didn't realize GIMP handled RAW (NEF and suchlike) formats and allowed adjusting of whitepoints, etc. I thought it was purely a raster image editor/tweaker.

      This is the whole reason Aperture exists and people don't just use Photoshop (which incidentally does all of that too) for RAW processing.

    6. Re:Here's a Summary! by beh · · Score: 4, Insightful

      But that's part of the shortfall...

      Lightroom and Aperture are so good BECAUSE they are integrated.

      There is nothing really in Lightroom that you can't do with Photoshop - but the way it's integrated and how it's able to work with / organise large collections of photos makes Lightroom one of the most run Apps on my Mac.

      As long as Linux doesn't offer a good competitor to Lightroom / Aperture, I will keep doing my photography stuff on the Mac...

    7. Re:Here's a Summary! by UNIX_Meister · · Score: 1

      One nice feature of f-spot is the ability to open up a picture with gimp, and have your changes be versioned inside f-spot. I realize that there is more that the proprietary apps do with the integration, but it can be this simple too.

    8. Re:Here's a Summary! by Sparr0 · · Score: 4, Interesting

      I didn't realize GIMP handled RAW (NEF and suchlike) formats and allowed adjusting of whitepoints, etc. I thought it was purely a raster image editor/tweaker.

      Glad we could set you straight on that. I love the RAW tools in GIMP, they simplify my workflow significantly.

    9. Re:Here's a Summary! by Fred_A · · Score: 3, Informative

      There's also digikam which does a *lot* of things including management, basic editing and raw processing (although I do that last bit in Bibble). It's Qt but will run fine on a Gnome desktop.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    10. Re:Here's a Summary! by harry666t · · Score: 3, Funny

      > Qtpfsgui

      Holy crap, how does one spell that? o_0

      How did the author come up with this name? Did he smashed the keyboard with an enraged basement cat or what? Or is it "Cthulhu" reversed and triple-ROT13'd?...

    11. Re:Here's a Summary! by Draek · · Score: 5, Informative

      Raw Therapee, raw photo processor, free. It does not, however, run on Mac OS X. Does not manage projects. And it does not work with anything but raw photos, so it will not allow for processing jpegs or tiffs

      Huh? out-of-the-box it can't, but you just click on Preferences > File Browser, uncheck Show only RAW files, and there ya go. Can't understand why "doesn't run on MacOSX" would be a con in an article about *Linux* alternatives to Aperture either, but oh well.

      Ohh, and about Lightroom, the older (v2.x) versions used to be free (as in $0) on Linux, plus they ran on non-SSE2 CPUs, so Linux users strapped for cash may want to search the 'net for them instead.

      --
      No problem is insoluble in all conceivable circumstances.
    12. Re:Here's a Summary! by BrokenHalo · · Score: 1

      Well, GIMP doesn't actually support RAW formats, and for good reason. They are both unnecessarily manifold and proprietary.

      Even the most basic cameras generally offer support for uncompressed images (usually in some sort of TIFF encapsulation), and if this is what you need, then use it.

      I have read so many posts on Slashdot dinging the GIMP for its interface, which I (as a latecomer to Photoshop) find perfectly intuitive and comfortable. The presence (or absence in the GIMP's case) of CMYK support is of no moment unless you are into hard copy publishing or have a printer that supports it.

    13. Re:Here's a Summary! by phoenixwade · · Score: 1

      > Qtpfsgui

      Holy crap, how does one spell that? o_0

      How did the author come up with this name? Did he smashed the keyboard with an enraged basement cat or what? Or is it "Cthulhu" reversed and triple-ROT13'd?...

      Not exactly from the project website -
      Qtpfsgui at sourceforge
      Why this name?
      Qt: the program uses Qt4 to show its graphical widgets.pfs: the main backend library and original sourcecode base.
      gui: this stands simply for graphical user interface.

      --
      A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort.
    14. Re:Here's a Summary! by Goaway · · Score: 3, Insightful

      Well, GIMP doesn't actually support RAW formats, and for good reason. They are both unnecessarily manifold and proprietary.

      That's not "good reason". That's just lacking capability.

      Even the most basic cameras generally offer support for uncompressed images (usually in some sort of TIFF encapsulation), and if this is what you need, then use it.

      You really don't know what raw files are even used for, do you? Very few cameras these days support TIFF, and that's because TIFF has none of the benefits of raw CCD data files, and is even larger than them.

      (Technically, DNG raw files are TIFFs, but those are not in any way widely supported yet.)

    15. Re:Here's a Summary! by afidel · · Score: 4, Informative

      If you don't know why RAW is needed then don't comment on it please. There's nothing like being able to simply reshoot a photo by changing the WB from the raw, adjusting layers in a JPG/TIFF doesn't accomplish anywhere near the same thing. I have a picture of my nephew blowing out his birthday candles that came out very overexposed (sun suddenly came out from behind a cloud), manipulating the JPG output was worthless because it made things too dark while trying to darken the overexposed area, throw the NEF into Lightroom, drop down two EV and adjust some levels and suddenly a white blurry mess becomes an ok shot of my nephew at his birthday.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    16. Re:Here's a Summary! by Anonymous Coward · · Score: 0

      And, I might add, RAW files are a poor photo archiving format. Among the camera vendors, their RAW format changes with subsequent release of new cameras.

    17. Re:Here's a Summary! by RNelson · · Score: 1

      > Qtpfsgui Holy crap, how does one spell that? o_0

      Off the top of my head, I'd guess q-t-p-f-s-g-u-i.

    18. Re:Here's a Summary! by beh · · Score: 2, Informative

      Yes - sure, but for one thing, Lightroom allows the same (even allowing two different apps to be called from within lightroom -- in my case, these would be Photoshop and DXO (for which, I think, there also isn't a linux alternative).

      But the 'trick' is more about not needing most of the programs for most of the time; or being able to batch-use them (like DXO, which I can run once every new import or so to work on all new pictures in one go).

      Just as a bit of background - for someone 'occasionally' shooting photos, the whole gimp + various other things for different jobs might work fine. On the other hand, my photo library is about 20.000 photos - many of these still need to be sorted/sifted through to filter it down further, but if I wouldn't have a well integrated package like lightroom, I would probably have given up on it long ago. Thanks TO apps like lightroom, I'm much less hesitant to take LOTS of photos, because I know sorting/ordering/filtering/pruning is going to be both quick and easy. When I say lots, I do mean take several images of the same shot (often with bracketing) and then look through afterwards deciding which to take.

      Regarding calling gimp / photoshop, it's a nice feature to have, but for the most time, I won't need it - Photoshop mostly comes into play for filtering options Lightroom doesn't have - e.g. perspective correction. For most photos, the various development options in lightroom are more than enough.

      (the above is just as valid for Aperture - I think both Lightroom and Aperture are on about equal footing; I just happen to prefer lightroom (after using each separately for a while).

    19. Re:Here's a Summary! by ti1ion · · Score: 2, Informative

      That's Lightzone that was available free for Linux, not Lightroom.

    20. Re:Here's a Summary! by fluffman86 · · Score: 4, Informative

      Gimp can support RAW with the DCRAW addon, as well as CMYK with Separate+

    21. Re:Here's a Summary! by retzkek · · Score: 5, Funny

      It certainly allows for some creative pronunciations... Cutey-puffs-gooey?

    22. Re:Here's a Summary! by Anonymous Coward · · Score: 5, Funny

      As far as GIMP interface is concerned, let's just say its different than, er, Photoshop. It has been discussed and beaten to death already anyways, and offtopic here.

      In my opinion, it hasn't been beaten to death enough.

    23. Re:Here's a Summary! by Fri13 · · Score: 1

      And if you are smart, you know that all those applications works on Linux and not just on ubuntu. Ubuntu is nothing more than one distribution among others distributions! If you use Ubuntu, you use linux!

    24. Re:Here's a Summary! by leenks · · Score: 1

      If the format is documented then it is a great archiving format. Any conversion from RAW to an RGB format is lossy, and there will be advances in conversion methods over time.

    25. Re:Here's a Summary! by ladoga · · Score: 1

      Author seems to be concerned in reproducing the workflow he has with Aperture or just looks for some general purpose all-in-one program for converting his raws.

      Maybe that's why the article has no mention of UFRaw, which works standalone or as a plugin for the GIMP. It uses the superb dcraw as it's backend and reproduces camera white balance settings for my Olympus E-510 ORF files better than other raw conversion tools out there. It works fine for me as I use raw editors/converters only for adjusting exposure and white balance and then do the most of actual image manipulation in the GIMP.(right tool for the right job, eh?)

      Photography is one area where Linux has many tools. So far I've tried LightZone (very slow and bloated), Rawstudio (promising, but has no clue of my camera white balance and is still somewhat buggy) and RawTherapee. Now all that I (and many others) still want is 16-bit per channel colors support in GIMP. I know about Cinepaint, but I would miss all the other things that GIMP can offer.

    26. Re:Here's a Summary! by Bryansix · · Score: 1

      Actually no. That is completely wrong. That is just Adobe's line they use to get support for DNG yet no camera shoots in DNG so it's lame. I'm not processing every file to DNG to archive it. I can archive the CR2 RAW files and I EXPECT Adobe to support them forever.

    27. Re:Here's a Summary! by Bryansix · · Score: 1

      Isn't the Jpeg format closed? How about Gif? Not supporting formats (be they actual formats or containers like RAW files) is dumb. It's not done for a good reason, it's done because they just haven't gotten around to adding in the support yet. The GIMP should very much support RAW files from every manufacturer.

    28. Re:Here's a Summary! by Goaway · · Score: 1

      No, it does not. A few camera makes have changed raw formats a few times.

      You're confusing the inability of software to read raw files from new cameras with a change in the format. Software can't read the new files because each camera needs its own bayer grid and filter coefficient parameters, and these can vary arbitrarily between camera models.

      It would certainly be better if cameras would write these parameters to the files they produce, but by and large they don't. That's a shortcoming of the format, certainly, but it does not mean the format is changing in any way.

    29. Re:Here's a Summary! by sootman · · Score: 4, Insightful

      ... Qtpfsgui ...

      OK, it's been a joke/cliche/truism for years about OSS packages with crappy names, but... damn. I think we have a winner. 6 consonants in a row and two vowels at the end. No one will over beat that. It looks like someone's cat walked over the keyboard just as the owner was clicking 'create new project' on SourceForge.

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    30. Re:Here's a Summary! by EvanED · · Score: 1

      Even the most basic cameras generally offer support for uncompressed images (usually in some sort of TIFF encapsulation), and if this is what you need, then use it.

      TIFF != RAW!

      Figure out a way to losslessly change the white balance your TIFF file was shot at and we'll start discussing again.

    31. Re:Here's a Summary! by AaronW · · Score: 1

      Bibble does support tagging and IPTC meta editing under the edit menu.

      I have been using it for years on Linux. It's also well supported and they are generally responsive to bug fixes and updates.

      It's the best $130 I've spent. When I got my new D-SLR with a new raw format it didn't take more than a few weeks until support was added, in part since the raw converter is based on the open source dcraw. It does an excellent job handling the RAW photos, plus I also bought a license to Noise Ninja which is integrated into it.

      It may not be FOSS, but I have yet to find a FOSS equivalent.

      The workflow support took some getting used to with the Pro version, but it's well worth it. I can crank through hundreds of photos very quickly with it.

      I've also tried out the other packages like Digikam and Picasa. Picasa still has not added support for the Nikon D300 RAW format (which was released in November). None of them come anywhere close.

      --
      This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    32. Re:Here's a Summary! by AaronW · · Score: 1

      And Gimp is a POS when it comes to editing photos due to its poor color support (only 24 bit). Most professional packages use 48-bit internally for editing. Heck, the images from my camera are in either 36 or 42-bit RAW mode, which comes in handy for adjusting curves, fixing whitebalance and highlight and shadow recovery.

      Gimp can't handle the basic stuff I tend to do, plus I've found the UI to be horrible, and forget any workflow support in Gimp.

      --
      This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    33. Re:Here's a Summary! by Anonymous Coward · · Score: 0

      Picasa still has not added support for the Nikon D300 RAW format (which was released in November).

      I've had a D300 for six months and have yet to find a single FOSS program that can reliably open a 14-bit NEF. Last I checked, dcraw and ufraw have nothing.

    34. Re:Here's a Summary! by Sir_Lewk · · Score: 1

      Qt (as in the tool kit) Photo Files Suite GUI maybe? dunno.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    35. Re:Here's a Summary! by Draek · · Score: 1

      Ugh, you're obviously correct, my brain must've been on temporary vacation when I wrote that part. Thanks for the correction.

      --
      No problem is insoluble in all conceivable circumstances.
    36. Re:Here's a Summary! by drinkypoo · · Score: 1

      Get QGtkStyle and Qt apps will look like GTK+2 ones. Qt 4.3 or later is required. I made a PPA package for Ubuntu Hardy (my PPA is under ~martin-espinoza)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    37. Re:Here's a Summary! by Zeddicus_Z · · Score: 1
      --
      Janie took my gun...
    38. Re:Here's a Summary! by JohnVanVliet · · Score: 1

      i find i use nip2 for a lot of my work . when built from source it can import all of the formats that image magick can and works with 8 bit /chan, 16 bit/chan and 32bit/chan images . but i manly use it to import a .fits image exported from ISIS of the Cassini imaging data ( iss)

      --
      "I don't pitch OpenSUSE Linux to my friends, i let Microsoft do it for me
    39. Re:Here's a Summary! by Anonymous Coward · · Score: 0

      You are right to some extent. Total integration may make work flow in some places a bit smoother than separated applications. However, you should try it first and see. You'll find with proprietary applications that the boundary between one application and another is very strong because application authors see each other as competitors and don't want to cooperate beyond the basics standardised in the operating system. In free applications, often non-integrated programs will work directly together and the developers even cooperate. For example gimp calls directly into ufraw and back. They are separate, but you don't really notice the boundary.

      This separate but integrated attitude ends up much better because

      • now you can swap one program for another better one later.
      • the "almost integrated" connection now extends to many other applications
      • you tend to have more choice about ways to do things (*)

      you should try to get used to this.

      * that you can do the same thing in different ways is not always a benefit. Beginners find it harder, experts more flexible.

    40. Re:Here's a Summary! by Anonymous Coward · · Score: 0

      That summary is about as good as the article. It doesn't seem he's really used the tools enough.

      I've evaluated all these tools, and have ended up with Bibble. It has proper workflow, profiling, useful plugins, batch processing, and produces the correct results on screen and for printing.
      Only limitation I've found with it is I occasionally hit the limit of how much memory it can use (being 32bit).

      Also the article missed DigiKam. It's useful for tagging organising files. However it has a big limitation in that the information is stored in an XML file. Not great if you want multiuser access to tagging/organising.

      It's database backend store wasn't working last time I tried it. I looked at the code to see if I could add to it but it relies on KDE's database (kexi?) libs which I'm not familiar with.

    41. Re:Here's a Summary! by BrokenHalo · · Score: 1

      If you don't know why RAW is needed then don't comment on it please.

      I call bullshit. If you can't take a simple family snap without ballsing it up, you have no business commenting on the format.

    42. Re:Here's a Summary! by Em+Adespoton · · Score: 1

      If you don't know why RAW is needed then don't comment on it please.

      I call bullshit. If you can't take a simple family snap without ballsing it up, you have no business commenting on the format.

      The point is that if you're shooting RAW, you aren't ballsing it up -- you haven't adjusted exposure, limited colorspace or set whitepoint yet (you do it yourself, the camera doesn't automatically do a "best guess" for you and then downsample the result to a JPEG).

      RAW is pretty much what your camera's sensors sense, translated into a flat file. Getting from there to JPEG involves a bunch of postprocessing done by the computer built into your camera; usually the built-in computer gets it right, but not all the time. People who want fine grained control over what images they record tend to like RAW.

      Personally, I prefer to take lots of pictures and save in JPEG; I just flip through multiple whitepoint settings and exposure rates as I fire off 3 photos per second for 10 seconds or so and then select the best shot after I've uploaded the images to the computer. But people using RAW just need to take a couple of pictures to get the same results, especially if they know what they're doing.

    43. Re:Here's a Summary! by Em+Adespoton · · Score: 1

      Isn't the Jpeg format closed? How about Gif? Not supporting formats (be they actual formats or containers like RAW files) is dumb. It's not done for a good reason, it's done because they just haven't gotten around to adding in the support yet. The GIMP should very much support RAW files from every manufacturer.

      The GIF and JPEG formats are open standards; they're just patent encumbered (although GIF isn't anymore and JPEG has a very liberal license). Most RAW formats are company trade secrets, as the format is a direct representation of how their hardware and firmware works in the company's photosensing devices; the details are given out under NDA to third parties who can then incorporate closed RAW handling code into their software or RAW handling libraries.

  4. Linux needs system-wide color management by ehack · · Score: 4, Interesting

    Color management means an image is shown the same on every screen, and as close as possible on paper. You cannot do serious photo work without integrated color management, but unfortunately even Winsh*t still leads Linux by ten years here. It's time the Linux guys moved their efforts to desktop app integration - the server is done - you hear me, guys ? the server is done, move to improving the desktop !

    --
    This is not a signature.
    1. Re:Linux needs system-wide color management by serviscope_minor · · Score: 2, Interesting

      the server is done - you hear me, guys ? the server is done, move to improving the desktop !

      So far, I have not been impressed with the efforts to "improve" the desktop. With every new iteration of the various popular distributions, it seems like more and more functionality is tied to GNOME and/or KDE with fewer and fewer features available through the command line.

      I think it would be better if people kept their hands off the desktop.

      Oh, and I can't do serious photo work, because I'm not any good at photography, so I'm not missing anything :)

      --
      SJW n. One who posts facts.
    2. Re:Linux needs system-wide color management by iamwhoiamtoday · · Score: 4, Interesting

      I LIKE IT that less and less features are tied into the command line. It's a lot easier for me to use a computer via GUI then via obscure command line commands. I run Ubuntu on two different computers at home, 3D acceleration, COMPIZ, WINE, all work extremely well. And I didn't have to use the command line to set any of them up. The average person who uses a computer (Example: My Mother) can now use Ubuntu, because the average person depends on a GUI instead of memorization of a bunch of command line commands. Most people don't CARE what Operating System they are using, as long as it is simple, as long as the UI is friendly. Look at OS X. It's rather user friendly. Linux is heading the same way, while Vista.... well, it's Vista. ;)

    3. Re:Linux needs system-wide color management by plasmacutter · · Score: 1

      the server is done - you hear me, guys ? the server is done, move to improving the desktop !

      So far, I have not been impressed with the efforts to "improve" the desktop. With every new iteration of the various popular distributions, it seems like more and more functionality is tied to GNOME and/or KDE with fewer and fewer features available through the command line.

      When last I checked commands were not "either-or".

      Additionally, That's kinda the point...

      I don't want to have to drop to a shell every time I want to do file management because every graphical manager lacks a "sudo" dialogue.

      2 other important things on my wishlist besides this and color management, an OSS version of "column view" from finder, and I want gnome to integrate true next style navigation. In an era where vertical real estate is at a premium, slapping a menubar into each window is a huge waste. Additionally, many websites use the browser "pallet" as DRM to keep you from accessing certain addresses or viewing source. True mac menubars allow quick, easy access to those functions.

      --
      VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
    4. Re:Linux needs system-wide color management by Anonymous Coward · · Score: 0

      and more and more shit is linked to gnome libs and x11 stuff. want to install some of the system-config- stuff for text use- gotta have x11, gnome, etc.. people making these packages are like "oh, cool, there's a --with-obscurelib and look, it's in yum!" and so they make it a requirement. yeesh. I like CentOS/RHEL, but it's getting more and more rediculous for a headless server. Do I really need wireless_tools and bluez on my server? Even if I customize the installation 100% and go through the very vague limited lists and uncheck everything, it still installs crap because of hidden dependencies. I miss SGI's inst tool.

    5. Re:Linux needs system-wide color management by larry+bagina · · Score: 1

      GNUStep's is ahead of the pack here, since OpenStep included color management. Obviously, it needs work to get up to Apple quality, and some of that depends on X.org, but the foundation is there today, whereas gnome color support will be an attrocious hack if it's ever added.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    6. Re:Linux needs system-wide color management by Eli+Gottlieb · · Score: 2, Interesting

      Ummmm... DBus? You can open up a text editor and write a program that scripts your desktop (ie: GUI-based) applications in C++, Python, C, Java, or basically any other language. Then you can run that script from the command line.

    7. Re:Linux needs system-wide color management by kwalker · · Score: 2

      Seeing as how most of that color-management some want so badly is patented by various for-profit companies, and considering that patent lifetime is (currently) 17 years, and finally if Windows is "ten years" more advanced than Linux, then it's as much as 7 more years (Barring a patent lifetime extension being rammed through Congress) before those patents expire and Linux distros can finally start integrating those technologies legally.

      For the time being, there are ways to get color management in Linux depending on how much effort the user is willing to put in. I have always used high-quality displays (A Hitachi CRT previously and now a Samsung LCD) which haven't required much tweaking to get the displays I want for my own photo management.

      --
      ... And so it comes to this.
    8. Re:Linux needs system-wide color management by fork_daemon · · Score: 3, Insightful

      A line needs to be drawn somewhere..

      Us geeks like the CLI even today because we know that the CLI is much more efficint for the kind of task that we do. It is quicker to do many tasks from the CLI than the click>wait app to launch> Click the Tab> Select The Option> Apply> Close. But we need to remember that the population of average user outruns the population of us geeks.

      The developers need to continue designing better GUI apps without compromising on the CLI bundle that we still use.

      By the way I havent seen any distro that has been dumping any CLI feature in favour of GUI.

    9. Re:Linux needs system-wide color management by samkass · · Score: 3, Insightful

      Speak for yourself, and don't try to speak for "us geeks". There are a lot of geeks who use the GUI for almost everything. Yes, I like to have tcsh available on my MacOS Terminal (I know some prefer bash), but the idea that preferring a GUI costs me geek cred (finally!) died over a decade ago.

      --
      E pluribus unum
    10. Re:Linux needs system-wide color management by JerkBoB · · Score: 1

      A line needs to be drawn somewhere..

      Us geeks like the CLI even today because we know that the CLI is much more efficint for the kind of task that we do.

      Oh please. Get over yourself.

      A GUI, when designed well and used appropriately, is zillions of times faster than a CLI for performing certain classes of tasks.

      A concrete example? Wi-Fi management. On my Ubuntu 8.04 laptop, I click the little network icon in my upper panel, choose a wireless network, and enter a password if necessary. Then I wait for both green lights to come on, and I'm done!

      I know how to do all of that in the CLI (did it for YEARS... since the late 90s), but it's by no means faster to do it that way.

      No one is arguing that the Linux Desktop should go the way of Windows, in which the only way to do some kinds of things is via GUI. Even in Windows, though, there is a pretty powerful scripting interface. I wouldn't say it was fun to work with, but I was able to get some pretty complicated stuff done with a bunch of Perl scripts (IIS provisioning, etc.)

      Anyhow, I'm guessing you're young yet. It's good that you're putting in the time to learn the plumbing and other innards, but don't denigrate the efforts of those who are working on making Linux more open and accessible to those who can't or won't take the time to learn how to use a CLI.

      --
      A host is a host from coast to coast...
      Unless it's down, or slow, or fails to POST!
    11. Re:Linux needs system-wide color management by jedidiah · · Score: 1

      Until the GUI tools are comprehensive (they just aren't, on anyplatform) there will always be the need to have CLI tools.
      Fortunately, there is really nothing forcing those to go away.
      Package managers make it trivial to add things that aren't
      installed by default and simpler CLI tools (and even some GUI)
      tools don't require any fancy installers. You can just pick up
      a binary and use it.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    12. Re:Linux needs system-wide color management by harry666t · · Score: 1

      What about the guys who'd like the $FUNCTIONALITY on *both* GUI and CLI?

      I've been trying to control Amarok with DCOP && ssh from another room, but this isn't really a sane solution...

    13. Re:Linux needs system-wide color management by ehack · · Score: 1

      This is typical Linux FUD. All the basic stuff has been made generally available by the various people who defined the ICC profile standards. There are no royalties attached. There are some excellent CMS packages under Linux (argyll, lcms) , but system-wide support is missing because of the fragmented nature of the community - read they cannot make up their minds where to put the config files, I'm not joking.

      --
      This is not a signature.
    14. Re:Linux needs system-wide color management by serviscope_minor · · Score: 1

      I LIKE IT that less and less features are tied into the command line.

      The problem is that features are becoming tied to the GUI, so the command line is not an option.

      It's a lot easier for me to use a computer via GUI then via obscure command line commands.

      Well, its a lot easier for me to type commands at a prompt than dig through obscure menus.

      I run Ubuntu on two different computers at home, 3D acceleration, COMPIZ, WINE, all work extremely well. And I didn't have to use the command line to set any of them up.

      Ubuntu installed fine for me without any commandline interaction as well.


      The average person who uses a computer

      On the one hand, I don't care about the average person. I've spent much of my life learning and using computers. I don't see why I should be limited to an "average" experience.

      (Example: My Mother) can now use Ubuntu, because the average person depends on a GUI instead of memorization of a bunch of command line commands.

      And I taught my mother how to use the very basics of the commandline. It makes phone support much easier for me.

      Most people don't CARE what Operating System they are using, as long as it is simple

      Firstly, simple is in the eye of the beholder. Secondly, if they don't care, then why are they using linux?

      , as long as the UI is friendly. Look at OS X. It's rather user friendly.

      Not to me it isn't. I find it unfriendly and unintuitive.


      Linux is heading the same way, while Vista.... well, it's Vista. ;)

      Which is a shame. Linux will never be a better OSX than OSX, because Apple have a particular vision and lots of resources. Linux, on the other hand can offer so much more. Unfortunetaly, some prominant projects seem to be engaged in a rapid race to the bottom, to see who can emulate all the broken misfeatures as well as possible.

      Example:

      Computers I used to own would work fine with hotplugged external storage. The OS would create a mountpoint named correctly (using the name embedded in the filesystem). It would also create a nice entry in /etc/fstab. If you ran GNOME or KDE, then they would mount the storage for you, automatically. If you didn't, you could simply mount /media/whatever and then umount it at the end. It was a nice system which provided working hotplug storage regardless of the desktop environment. Both Ubuntu and Redhat no longer do this. Now, you can only get nice hotplug storage if you use GNOME or KDE. This just like OSX, where you can't umount anything in /Volumes. This is not good. Now if you like the commandline, it's back to reading dmesg, /proc/partitions and sudo or custom fstabs in order to mount USB storage.

      --
      SJW n. One who posts facts.
    15. Re:Linux needs system-wide color management by kaizokuace · · Score: 1

      Everyone complains about GUI this CLI that. Why cant we just always have both? it will make life work for everyone!

      --
      Balderdash!
    16. Re:Linux needs system-wide color management by FictionPimp · · Score: 1

      This is what I liked about gentoo. You can usually decide what libs are included and not (as long as the program can be compiled with or without the support).

      Most normal distros just pick what is best for the most people.

    17. Re:Linux needs system-wide color management by Mprx · · Score: 1

      Gentoo's USE flags are designed to solve exactly this problem. You'll only get the obscure optional dependencies if you explicitly request them. USE flags are the real reason Gentoo is a great OS, beyond the minor speed boost from compiling for your specific hardware.

    18. Re:Linux needs system-wide color management by Tom9729 · · Score: 1

      The developers need to continue designing better GUI apps without compromising on the CLI bundle that we still use.

      Agreed.

      Might be a bit OT, but last time I checked The GIMP actually had a CLI. I don't know who would use it for much besides (maybe) really advanced batch photo editing though.

      I use ImageMagick for most things. The "convert" and "resize" programs are incredibly useful when editing folders of images.

    19. Re:Linux needs system-wide color management by AnyoneEB · · Score: 1

      No, really, you don't. You mean, you like that you can avoid command line and do everything via GUIs easily. That is a good goal, but it should not be accomplished by making monolithic GUI programs. That goes against an important part of the Unix philosophy which is sorely missing from many modern GUIs: "Write programs that do one thing and do it well." If the CLI uses the same code as the GUI (or the GUI is just a fancy frontend for the CLI as is the case for some CD/DVD ripping programs I have used on Linux), then you have less duplication of effort, and therefore instead of different GUIs spending their time reimplementing the same functionality they could spend time perfecting their interfaces.

      --
      Centralization breaks the internet.
    20. Re:Linux needs system-wide color management by Kizeh · · Score: 1

      I tried setting up a SMB file share in Ubuntu 8.04. I still haven't figured out how to do so. I haven't figured out how to browse to other SMB shares without the "Connect to server" from scratch every single time. I haven't figured out how I can mount a new hard drive through any of the tools. Video acceleration on my ATI 9600 card was not simple to set up, but not impossible. Too bad it broke video so I had to back out of it. Many video players fail horribly in panning xvid content, and I experience frequent crashes and hangs with video players, audio players and Nautilus. I've been quite unimpressed by all of this, especially in comparison to CentOS which I use daily at work and just seems to work without a glitch.

    21. Re:Linux needs system-wide color management by PitaBred · · Score: 3, Insightful

      You aren't much of a geek, then. Preferring the GUI for CERTAIN TASKS is a good thing. But the GUI is simply not the best interface for everything. There are some things that are much better done with the CLI, which is what I think the GPP was getting at. Don't stop development of the command-line interface and tools simply because we want to appeal to grandmas and other people scared of the command line.

    22. Re:Linux needs system-wide color management by burner · · Score: 1

      Try out the gksu extension for nautilus for (1).

      --
      MRSH-Recording device, corned beef sandwich with kraut, seafaring bird, and the foamy top of a beverage.
    23. Re:Linux needs system-wide color management by PitaBred · · Score: 1

      That's because they moved to udev, I believe. If you want the "old" functionality, you can probably tweak the udev rules yourself. It's not terribly difficult or hard to figure out. Probably just write a script, or hell, create persistent mountpoints since you likely only have a few hotplugged devices that you use.

    24. Re:Linux needs system-wide color management by yanos · · Score: 1

      What are you talking about? In the last few years, some very noticeable work has been done in improving the desktop experience, and none of them are GUI only. you know about hal, dbus and udev? You know, the things that let you press the goddamn eject button of dvd drive and, *gasp*, opens the drive tray, even if said drive is mounted? Or notify you via the systray that you just have plug an usb thumb drive? All of that is 100% command line friendly. GNOME and KDE just integrate the functionality so you don't *have to* switch to command line for simple, day to day operation.

    25. Re:Linux needs system-wide color management by Bryansix · · Score: 1

      This things you need to learn to be good at photography are the same kind of technical things you need to learn to be good at computers. Once you understand the concepts and how the camera works then it all flows naturally from practice. Just buy the book "Photography" written by London. I love the title of the book; it says it all.

    26. Re:Linux needs system-wide color management by Sir_Lewk · · Score: 1

      the server is done - you hear me, guys ? the server is done, move to improving the desktop !
      I have an idea, and it may seem radical to you but so be it. I'm happy with where the Linux desktop is at. I think it's fine, I have a very hard time placing my finger on things that need to be improved. Furthermore I see no reason to stop improving servers. I don't see Linux as some sort of conquest, I don't care if other people think other software is better, I care about what *I* like. The main objective (at least not to everyone) is not to steal the other guy's userbase so stop acting like it is.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    27. Re:Linux needs system-wide color management by E+IS+mC(Square) · · Score: 1

      As for Amarok, not sure if this helps, but you can have this script run a web server after which, you just need a browser on your other pc, and control it over your local network. http://www.kde-apps.org/content/show.php?content=36970

    28. Re:Linux needs system-wide color management by drinkypoo · · Score: 1

      the minor speed boost from compiling for your specific hardware.

      Unless you have a K6, in which case the boost is tremendous.

      Those few people who still have a K6 owe it to themselves to run something actually built for it (-march, not just -mcpu.) It truly polishes the turd.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    29. Re:Linux needs system-wide color management by ehack · · Score: 1

      I meant to say that server-side needs, eg. rock solid and fast file systems have been addressed in Linux for the past few years. However, desktop needs like color-management for applications (so you see the same color in Gimp, in Firefox and in any other app) have nto been addressed.

      As other posters have noted the tools exist and individual applications have made great efforts at color management. However a systemic approach is missing. It's a bit as if every database app had to reimplement a file system. Can be done but not the best way to get it done.

      --
      This is not a signature.
    30. Re:Linux needs system-wide color management by harry666t · · Score: 1

      Wouldn't work too well over text-only terminals. Also, Amarok is somewhat heavyweight. All of this adds up with the fact that 100% of the hardware @ my home is old crappy junk - practically only one box is able to smoothly run a normal X11 desktop :)

      The whole issue is why I'm currently developing a console music player that speaks stdio, has a shell-like cmdline interface with readline and completion, an audio library, lastfm support, a flexible plugin architecture, etc. So far I've only got the cmdline interpreter working flawlessly :P

    31. Re:Linux needs system-wide color management by E+IS+mC(Square) · · Score: 0, Offtopic

      I see. In my case, I had gotten hold of some old Dell 512MB machine which I wanted to convert into a music server. Amarok manages to work - but just, and hogs up everything available on the machine. This means I can not do anything else on that box, but then, I never intended to - as long as it plays my 20GB+ collection of music (its attached to my sound system directly). And now I can control music from my other Ubuntu/XP/anything with the web server.
      Good luck with your efforts. It's a good beginning :-)

    32. Re:Linux needs system-wide color management by Jasonjk74 · · Score: 1

      I LIKE IT that less and less features are tied into the command line. It's a lot easier for me to use a computer via GUI then via obscure command line commands. I run Ubuntu on two different computers at home, 3D acceleration, COMPIZ, WINE, all work extremely well. And I didn't have to use the command line to set any of them up. The average person who uses a computer (Example: My Mother) can now use Ubuntu, because the average person depends on a GUI instead of memorization of a bunch of command line commands. Most people don't CARE what Operating System they are using, as long as it is simple, as long as the UI is friendly. Look at OS X. It's rather user friendly. Linux is heading the same way, while Vista.... well, it's Vista. ;)

      That is just silly. How are OS X or Ubuntu more user friendly than Vista? I know it's popular to bash Vista here, but how is it any harder to use. Is there a more enlightened way to click on icons in those OS'es?

  5. Aperture: what we've learned by minginqunt · · Score: 1, Funny

    Please note that we have added a consequence for using proprietary software. Any contact with proprietary software will result in an 'unsatisfactory' mark on your official testing record followed by death. Good luck!

  6. Aperature not as good Lightroom by tjstork · · Score: 1, Interesting

    My wife is a pro-photographer and takes like, 500+ images per job, and, we had the $3000 dual G5 Mac and Aperature and Aperature yakked and we lost a year of work because Aperature's doesn't generate unique filenames for its images across subdirectories and when you export it overlays them...

    Since then, she's switched to a WinPC and Lightroom, and Lightroom is both stable for her, and reliable and does more and she will never touch a Mac again. The moral of the story is that Adobe Lightroom is the real target, not Aperature... even the feature sets of Lightroom have her not missing her Mac...

    --
    This is my sig.
    1. Re:Aperature not as good Lightroom by Selfbain · · Score: 4, Insightful

      You didn't run a backup for an entire year?

      --
      Well, it has never been successfully tested.
    2. Re:Aperature not as good Lightroom by An+anonymous+Frank · · Score: 5, Informative

      Aperture's "library" is just a folder; Use "Show Package contents" from "Get Info" and copy all the originals wherever you want.

    3. Re:Aperature not as good Lightroom by carou · · Score: 3, Insightful

      we lost a year of work because Aperature's doesn't generate unique filenames for its images across subdirectories and when you export it overlays them...

      Why didn't she just restore from the backups you've been helping her keep?

    4. Re:Aperature not as good Lightroom by Ford+Prefect · · Score: 1, Informative

      Since then, she's switched to a WinPC and Lightroom, and Lightroom is both stable for her, and reliable and does more and she will never touch a Mac again. The moral of the story is that Adobe Lightroom is the real target, not Aperature... even the feature sets of Lightroom have her not missing her Mac...

      Why did she get a new computer?

      There's a MacOS X version of Lightroom, and it seems to work just fine - I specifically chose it over Aperture after evaluating the trial versions of both last year...

      --
      Tedious Bloggy Stuff - hooray?
    5. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      Time Machine ftw.

    6. Re:Aperature not as good Lightroom by Blakey+Rat · · Score: 1

      My wife is a pro-photographer and takes like, 500+ images per job, and, we had the $3000 dual G5 Mac and Aperature and Aperature yakked and we lost a year of work because Aperature's doesn't generate unique filenames for its images across subdirectories and when you export it overlays them...

      I agree that's a terrible bug, and Apple should be chided for it.

      But you didn't back up the files for an entire year? WTF! That's some weapons-grade FAIL right there.

    7. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      Clearly just flamebait given the incorrect spelling of Aperture, and mentioning buying a whole new PC for the next application that also runs on the Mac.

    8. Re:Aperature not as good Lightroom by tjstork · · Score: 1

      But you didn't back up the files for an entire year? WTF! That's some weapons-grade FAIL right there.

      She used the firewire drive that had her backup to copy the contents of the folder over, thinking, that, she was, in effect, making a backup. Then we put a copy onto my linux box from the firewire drive. She checked the results of the folder and saw the names were the same, the file counts were same, and a spot check of the images showed that there some there, then, she blew away the Mac drive.

      --
      This is my sig.
    9. Re:Aperature not as good Lightroom by mcgeeb · · Score: 1

      You are aware that lightroom is available for OSX as well?

    10. Re:Aperature not as good Lightroom by rootphreak · · Score: 0

      Since then, she's switched to a WinPC and Lightroom, and Lightroom is both stable for her, and reliable and does more and she will never touch a Mac again.

      Hah. The real trouble won't be with Lightroom, but with numerous other things on that PC.. *wink wink* AFAIK Lightroom is also for OS X. I hope she didn't forget to install an antivirus suite, firewall program, antispyware program, registry monitor, backup utility, and a professional drive defragger (Diskeeper) so she can keep that PC going.

    11. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      Right, blame Aperture puking on the mac itself. Lightroom runs on OS X, by the way. Seems kinda silly to invest so much in a powermac, only to switch platforms in order to use an app that's already availible for the mac, doesn't it?

    12. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 1, Informative

      I have never had such a problem with aperture with 600+ images per job (even some 2000+ jobs). My complain with it is that it is too slow.

      OTOH, Lightroom + Photoshop work pretty fine on my G4 machine.

      As for Open Source, my main complain is that it is not as productive as the Lightroom + Photoshop setup. I do like RAW Studio. I love The Gimp. But they do stand in my way of setting up lots of images.

      In a simple math, RAW Studio + Gimp is a work day more than Lightroom + Photoshop. And I'm more used to GIMP's interface than Photoshop's one, as GIMP was one of the first image manipulation programs I ever used (circa 1998).

    13. Re:Aperature not as good Lightroom by tjstork · · Score: 1

      Why did she get a new computer?

      The biggest reason, really, was that there are a lot more plugins available for Photoshop on PC than there are for Mac. When she does digital "art", as opposed to weddings and events, she likes to push the envelope in manipulation as much as she can and there's just more out there for Windows. Plus, of all things, she actually prefers the stupid XP Start bar to the Mac OS/X dock. Incidentally, we both actually like the Gnome bars on Linux best of all, and she'll use my Linux box to surf and chat with... but she's not jumping into Linux just yet for her work because the applications aren't quite up to scratch on it yet.

      I looked into it actually and it turns out a big problem with it is Canon, whose when I checked last, only made their SDK available for Windows and it was a closed source product. I tried plugging her camera into the trusty Linux box last with OpenSuse 10, and it was like flying into total darkness. Now that you've jogged my memory a bit, I'll have to try it now that I'm onto Ubuntu.

      --
      This is my sig.
    14. Re:Aperature not as good Lightroom by dosun88888 · · Score: 1

      Nah, she didn't, and she only took 374 photos for her last job.

      Nice use of reflection near the nightstand, by the way.

    15. Re:Aperature not as good Lightroom by Penguin+Follower · · Score: 2, Insightful

      All the more reason to use time machine it seems. ;)

    16. Re:Aperature not as good Lightroom by UNIX_Meister · · Score: 1

      I looked into it actually and it turns out a big problem with it is Canon, whose when I checked last, only made their SDK available for Windows and it was a closed source product. I tried plugging her camera into the trusty Linux box last with OpenSuse 10, and it was like flying into total darkness. Now that you've jogged my memory a bit, I'll have to try it now that I'm onto Ubuntu.

      Interesting - I've plugged two different Canon models into both gthumb and f-spot and had them work (the second was a Rebel XTi) perfectly.

    17. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      we had the $3000 dual G5 Mac and Aperature and Aperature yakked

      Your software was trampled by Himalayan oxen?

    18. Re:Aperature not as good Lightroom by moosesocks · · Score: 1

      Huh?

      You do know that Lightroom runs on both Windows and Mac, right?

      Actually, though, one of my favorite things about Lightroom is that it automatically makes backups of your database.

      One of my least favorite things about it is that I've had to use these backups on several occasions, because the 'working' database became corrupted. Aperture apparently isn't much better in this regard.

      In any event, shame on you for not making backups! If your livelihood depends on your data, there's absolutely no excuse not to.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    19. Re:Aperature not as good Lightroom by jintxo · · Score: 1

      Yeah my recent experience with Canons is the same, I've seen them "just work" most of the time.

      But I am sure it wasn't that way a while back, so that's probably why the parent had a bad experience.

      Cedric

    20. Re:Aperature not as good Lightroom by admactanium · · Score: 1

      You do realize that Lightroom is also available for Macs? In fact, it was available first on Macs. I use it on my MacPro. Not sure why she switched to a completely different computer and OS just to change one app that is available on both.

    21. Re:Aperature not as good Lightroom by _Swank · · Score: 1

      Any reason she didn't just stay with a Mac and switch from Aperture to Lightroom?

    22. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      mac fanboi?

    23. Re:Aperature not as good Lightroom by remmelt · · Score: 3, Insightful

      Not only that, he also blames the OS for it.

    24. Re:Aperature not as good Lightroom by Blakey+Rat · · Score: 1

      If it was over-writing files, how could the file-count possibly have been the same as the original?

      Or are you saying that Aperture had already over-written the files when it imported in the first place? But then how didn't she notice the missing images during daily use?

      I know, it's off-topic, I'm just curious to find out what happened here.

    25. Re:Aperature not as good Lightroom by mcgeeb · · Score: 1

      Oh, please. He's blaming the OS for the failures of the app. I fully admit Aperture isn't the greatest. I just don't see the point in purchasing an entirely new system to run an app that you could run on your existing machine. So, come again?

    26. Re:Aperature not as good Lightroom by tmtm · · Score: 1
      For other Aperture users, you can "Export" your master or versions. They are various settings for this (like including the date, some other metadata, etc). You can also 'relocate' the master also to move your files. These ways you can avoid 'over-writting'.

      Aperture has also Vaults to help on the backup. It has its faults, but for the specific issue you faced, it offers some options.

    27. Re:Aperature not as good Lightroom by Fred_A · · Score: 1

      I tried plugging her camera into the trusty Linux box last with OpenSuse 10, and it was like flying into total darkness. Now that you've jogged my memory a bit, I'll have to try it now that I'm onto Ubuntu.

      You do know that you'd get much higher transfer speeds with a card reader (which incidentally always works on anything) ?

      --

      May contain traces of nut.
      Made from the freshest electrons.
    28. Re:Aperature not as good Lightroom by Fred_A · · Score: 1

      My wife is a pro-photographer and takes like, 500+ images per job, and, we had the $3000 dual G5 Mac and Aperature and Aperature yakked and we lost a year of work because Aperature's doesn't generate unique filenames for its images across subdirectories and when you export it overlays them...

      Is this Aperture or the camera ? Most cameras can be set to number their files sequentially or to renumber them from 0 on every new card.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    29. Re:Aperature not as good Lightroom by Ford+Prefect · · Score: 1

      Actually, though, one of my favorite things about Lightroom is that it automatically makes backups of your database.

      One of my least favorite things about it is that I've had to use these backups on several occasions, because the 'working' database became corrupted. Aperture apparently isn't much better in this regard.

      Oh, that's what it's for!

      I'd assumed it wanted to backup absolutely everything to an external disk - which was already happening with Time Machine. So after being annoyed by Lightroom's prompting, I switched that feature off, not realising all it wanted to verify and copy (to a subdirectory of the catalogue stuff) was simply the catalogue data itself.

      I've re-enabled that feature so it'll run every week - and the 'local' backup will get copied to my external disk automatically through Time Machine.

      Thanks!

      --
      Tedious Bloggy Stuff - hooray?
    30. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      True, but you don't have to store your images in the Aperture library. Based on tjstork's post, I suspect that his wife is storing images in separate folders as referenced files. That would cause a problem.

      However, you should still be running regular backups of your work if that's your primary use of the machine, Wintel, Mac, or otherwise. Furthermore, Ap2.0 has the vaults to aid in this regard.

    31. Re:Aperature not as good Lightroom by paanta · · Score: 1

      Most cameras rollover every 10K images and start re-using the old file names. Totally annoying.

    32. Re:Aperature not as good Lightroom by CatOne · · Score: 1

      Dude... USER ERROR. And BTW you have the choice to rename files that you manage in Aperture as you see fit. You're just using the camera default names.

      It's easier to blame the computer for your idiocy, though.

    33. Re:Aperature not as good Lightroom by jedidiah · · Score: 1

      "you export it overlays them"

      Sounds like a logical backup to me.

      If the tool can't dump out and reload it's own data without screwing it up, that's just pathetic.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    34. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      What do you want from him? His wife is a professional photographer, and he cannot even spell "Aperture"?

    35. Re:Aperature not as good Lightroom by zenster · · Score: 2, Informative

      Aperture doesn't generate filenames. It uses the filenames generated by your camera. I'm guessing you have your camera set to restart the numbering for each memory card. I'm not sure exactly what you did to delete your files but don't blame Aperture for your mistake, it will only do what you tell it to and will prompt you if you want to replace a file with another of the same name.

      I'm betting that you still don't have a backup. When you lose files next time are you going to blame Lightroom and the PC and switch to Linux? Seems like a lot of work when you could just admit to yourself that you screwed up and change the way you work to include a backup.

    36. Re:Aperature not as good Lightroom by jamrock · · Score: 1

      I don't have any mod points, but that was "Insightful". And I agree, that was a textbook case for Time Machine. What will she do if her PC crashes and she still hasn't backed up?

    37. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      Bad user made a bad mistake, this is nothing new.

      Gratz on not using the built-in backup system on a year's worth of photography.

    38. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      Your wife needs to be creating the unique filenames herself. For example an assignment shot today would be:
      080710-Whatever-001.cr2
      080710-Whatever-002.cr2
      etc.

    39. Re:Aperature not as good Lightroom by FictionPimp · · Score: 1

      Time machine totally saved my ass last week. I accidentally deleted a few very important files. Time machine made it about a 5 second process to recover them.

    40. Re:Aperature not as good Lightroom by tjstork · · Score: 1

      You do know that you'd get much higher transfer speeds with a card reader (which incidentally always works on anything) ?

      She uses the card reader with her PC. I honestly never tried the card reader on ubuntu.

      --
      This is my sig.
    41. Re:Aperature not as good Lightroom by atrus · · Score: 1

      Interestingly enough, the Lightroom database is an SQLite 3 file. :)

    42. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      She might be pro, but she's pretty fucking stupid :) But I guess she sucks a mean dick, so thats allright.

    43. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      >My wife is a pro-photographer ...

      She is not a professional because...

      >we lost a year of work

      She caused this completely unprofessional situation.

    44. Re:Aperature not as good Lightroom by greed · · Score: 1

      It may be annoying, but they have to stick with that stupid 8.3 naming thing for hysterical raisins. Things that read camera cards aren't required to understand FAT32....

      Having multiple cameras, I gave up on the whole unique-number thing and have the camera re-set for each card. (Actually, what mine do, is they take "highest picture number on card +1" when you insert the card and count from there. Which is handy if you put the same card in multiple cameras.)

      Why anyone would expect files in different folders to guaranteed to have different names is beyond me, though. I know of no system API or operating convention that would provide that.

    45. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      Your wife is a photographer, and you have never seen the correct spelling of "aperture"? Or did you just never pay attention? Or do you just pay as much attention to the spelling as you did to proper backups?

    46. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      In Aperture's Export dialog box, there is a "Name Format" dropdown menu. You can select output naming formats like "Version Name with Date/Time" and "Version Name With Sequence" to get unique file names for each image. I'm sorry to hear that you lost your data; maybe next time you should (a) have backups, and (b) understand how to use the programs you are using.

    47. Re:Aperature not as good Lightroom by leenks · · Score: 1

      Why on Earth is this marked troll?

    48. Re:Aperature not as good Lightroom by afidel · · Score: 1

      You don't use an integrated workflow app like Lightroom/Aperture because you want to rename each file, you use it because you want to batch process the photos that come out of your camera. The app should be doing the name mangling in its own repository automatically!

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    49. Re:Aperature not as good Lightroom by Bryansix · · Score: 1

      Granted not making backups is not very smart but your using it as an argument is really just deflection from the main point. The main point is that Aperture overwrites files without permissions and could lead to data loss. THAT is unacceptable.

    50. Re:Aperature not as good Lightroom by Fred_A · · Score: 1

      It may be annoying, but they have to stick with that stupid 8.3 naming thing for hysterical raisins. Things that read camera cards aren't required to understand FAT32....

      I sometimes wonder if centuries from now people still won't have to make do with 8.3 files popping here and there because of some stupid FAT compatibility leftover.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    51. Re:Aperature not as good Lightroom by drinkypoo · · Score: 1

      When a program doesn't prompt you to ask if you want to overwrite files, that's bad. We have force flags and such to do that on the command line, it shouldn't happen automatically from the GUI either.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    52. Re:Aperature not as good Lightroom by g0at · · Score: 1

      Not only that, he doesn't know how to spell the common word or the name of the program he used for so long. ("Aperature"?)

    53. Re:Aperature not as good Lightroom by Anonymous Coward · · Score: 0

      Time machine totally saved my ass last week. I accidentally deleted a few very important files. Time machine made it about a 5 second process to recover them.

      It's genius. The HDD in my MBP died. I shoved a new disk in, started installing the OS, it automatically detected my Time Machine backup disk and restored everything. Since I'd been at lunch when it died & the backups were every 30 mins, I'd lost nothing. Genius.

    54. Re:Aperature not as good Lightroom by Jasonjk74 · · Score: 1

      My wife is a pro-photographer and takes like, 500+ images per job, and, we had the $3000 dual G5 Mac and Aperature and Aperature yakked and we lost a year of work because Aperature's doesn't generate unique filenames for its images across subdirectories and when you export it overlays them...

      Since then, she's switched to a WinPC and Lightroom, and Lightroom is both stable for her, and reliable and does more and she will never touch a Mac again. The moral of the story is that Adobe Lightroom is the real target, not Aperature... even the feature sets of Lightroom have her not missing her Mac...

      Finally! A story on /. about someone switching to Windows from Mac.

  7. Golden ratio? by martinw89 · · Score: 2, Insightful

    I have to admit, even though Picasa could probably use more crop aspect ratios, I immediately subconsciously discredited the author when he stated that the golden ratio was a requirement.

    1. Re:Golden ratio? by CRCulver · · Score: 1

      While the Memoir class manual is mainly of interest to LaTeX users, its opening chapters have an enlightening introduction to the history of book publishing, including the long use of the golden section. The concept is certainly relevant to DTP.

    2. Re:Golden ratio? by dsginter · · Score: 5, Funny

      I immediately subconsciously discredited the author when he stated that the golden ratio was a requirement.

      Apparently, your subconscious also posted this to slashdot.

      --
      More
    3. Re:Golden ratio? by gEvil+(beta) · · Score: 3, Interesting

      The golden ratio is certainly important, but no, automatically cropping everything to it is a bad idea.

      --
      This guy's the limit!
    4. Re:Golden ratio? by 5pp000 · · Score: 1

      I don't understand. Why shouldn't I be able to crop to any arbitrary aspect ratio? Even archaic `xv' does that. Okay, the use of the golden ratio specifically is a bit unusual, but so what??

      --
      Your god may be dead, but mine aren't!
    5. Re:Golden ratio? by martinw89 · · Score: 1

      It bubbles up here and there :)

    6. Re:Golden ratio? by E+IS+mC(Square) · · Score: 0, Offtopic

      Well, I too do not really care about Golden ratio, but everybody has his/her own preferences.
      His point is partially valid too - while Picasa does let you crop pictures manually, there is no way to specify a ratio you want - Golden or any other.

    7. Re:Golden ratio? by MadMidnightBomber · · Score: 1

      Particularly when it's a transcendental number, and thus unachievable on any image which has, like a whole number of pixels. Dur!

      --
      "It doesn't cost enough, and it makes too much sense."
    8. Re:Golden ratio? by hey! · · Score: 1

      Ah, but the subconscious, unlike the unconscious lies beyond the reach of consciousness. All subconscious behavior is unconscious, but only some unconscious behavior is subconscious, because nothing stands in the way of becoming aware of it.

      When you mindlessly set down your keys without noting where they are, you do so unconsciously. When you deliberately (on a deeply buried level) deliberately put your keys where you won't find them, because the phallic shape arouses the deep seated and unbearable desire to castrate yourself and live as a woman, you are doing so subconsciously.

      In this case, you clearly are capable of becoming conscious of dismissing the article's author, so that much is merely unconscious. However, the energy of subconscious urges, such as the urge to castrate yourself and thus appease the wrath of your father by taking your mother's place, cannot be "bottled up". They appear in surprising ways; you might find yourself intending to type ":-)", but instead typing something else symbolic of the suppressed wish. Clearly, you have not blocked the awareness of your irrational dismissal of the author based on his peculiar preference for the golden aspect ration; however you do seem to have a block about distinguishing "un-" from "sub-" conscious. This probably indicates you have no suppressed issues with photographers dabbling in mathematics, but you might have an issue related to Greeks doing so.

      I'm glad I could clear that up for you. :// =>

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    9. Re:Golden ratio? by martinw89 · · Score: 1

      All sarcasm aside, that was actually pretty informative. And it gave me a good laugh. Thanks!

    10. Re: Golden ratio? by Anonymous Coward · · Score: 0

      The so-called golden ratio/section has been debunked, look it up. And it was *never* relevant to DTP. The Memoir may be perfectly fine for some of its technical tips, I don't know, but the author says some stupid things in it. "For many years it was thought that it was impossible to fold a sheet of paper, no matter how large and thin, more than six times altogether." I'm stopping reading it at this point, it is wasting my time.

      I'm with the GP. When someone off-hand says something stupid, flags go up.

      The summary someone posted saved me from reading the whole article. IMHO it's pretty dumb to talk about non-free and non-FOSS software and say "I can cobble together something that will work". Aperture and Lightroom are cool in large part because of their integration.

    11. Re:Golden ratio? by Bryansix · · Score: 1

      The Golden Ration is what leads to the "Rule of Thirds". While I like to think of it as just another compositional option instead of a rule it is a major component of most photography.

    12. Re:Golden ratio? by drinkypoo · · Score: 1

      The golden ratio is certainly important, but no, automatically cropping everything to it is a bad idea.

      Please explain why it is a bad idea.

      Please include in your explanation why it is a worse idea than it is a good idea if it helps this wacko create his desired results.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  8. What a tool by jonnythan · · Score: 4, Insightful

    I stopped caring when the author said that he crops "all" his photos to the same (non-standard) ratio.

    Closed, done. Sorry.

  9. huh? by Mr.+Slippery · · Score: 1

    Sorry, I'm an idiot. I shoot the occasional digital photo and edit it up in the GIMP, that's the extent of my photography knowledge. Can someone explain to me what Aperture is, what a "raw photo editor" is, and how a "photo manager" differs from a "file manager"? Thanks.

    --
    Tom Swiss | the infamous tms | my blog
    You cannot wash away blood with blood
    1. Re:huh? by SQLGuru · · Score: 4, Informative

      The RAW image is the one straight from the camera (basically a RAW dump of the CCD output).

      Photo Management includes more than just folders (a good example is tagging -- I want to find all images tagged "Outdoors" or tagged "Porn" or tagged both "Outdoor" and "Porn"). Of course, like folders, tags are only as good as you make them.

      Layne

    2. Re:huh? by blankaBrew · · Score: 4, Insightful

      It also allows you to rate your photos which is immensely important when you come back from a shoot with lots of photos. It also allows you to group and stack photos...their thumbnails are literally stacked and you can unstack them and restack them, along with promoting photos within a stack. A file manager is no substitute for a photo manager when you are a photographer.

    3. Re:huh? by blankaBrew · · Score: 4, Informative

      I forgot to mention that the biggest feature of Aperture or Lightroom is the ability to make non-destructive edits. The original RAW file is left untouched and it is accompanied by a "recipe" that contains all of the changes to your image. You can cycle through your changes or revert back. Plus, it saves HD space by never duplicating the image.

    4. Re:huh? by bestinshow · · Score: 1

      A photo manager is to digital images what iTunes is to media files.

      It manages them, including the files on disc.

      This is desirable for many because the application takes the photos from the camera, and the user never needs to worry about what's going on on the file system.

      It's not so good when you have to use that application to email a file because you don't know the filesystem location of said file. Having to go through export to file wizards is a hassle. Some photo managers will at least have a sensible folder layout once you find it, in the same way that iTunes' folder layout is actually quite sane.

    5. Re:huh? by UNIX_Meister · · Score: 1

      There is a lot of metadata associated with photos, such as date/time, shutter specifics, camera model, etc. that are stored in the EXIF (and other) sections of the file (jpeg, raw, tiff, etc.).

      Keeping track of this, plus adding your own custom metadata (captions, tags, etc.) is the job of the photo management software. If you have thousands of photos (like my professional photographer wife does) it becomes essential to use some sort of manager, and Aperture is Apple's version.

      One feature that typically has been missing from linux programs is the ability to handle raw format files, though there has been progress on this front.

    6. Re:huh? by BlackPignouf · · Score: 0

      We're all idiots/noobs in some fields!

      This website : http://www.dpreview.com/learn/?/Glossary/ could answer your questions and some more.

    7. Re:huh? by Ford+Prefect · · Score: 2, Informative

      Can someone explain to me what Aperture is, what a "raw photo editor" is, and how a "photo manager" differs from a "file manager"? Thanks.

      Screenshots might help - basically it's a file manager with additional sorting, filtering and whatnot designed for organising photos. Here's Lightroom's library view as an example - I've filtered to show only photos I've given three stars or more, and selected one so you can see all the keywords and other metadata assigned to that photo. All searchable, sortable, filterable and so on!

      With regard to editing, here's a screenshot from the develop view. All the edits are non-destructive - you can see a history on the left. 'RAW' refers to the image from the camera being in an unprocessed, raw-data-from-image-sensor format, which gives you a bit more latitude in tweaking white balance, contrast, exposure and the like.

      (I don't normally shoot 'RAW', but my once-in-a-lifetime shipyard visit coincided with some utterly horrendous weather - getting just the right exposure in unlit, semi-derelict Eastern European industrial buildings at 7am on a cold, dark, wintry morning proved a little tricky at times... ;-] )

      --
      Tedious Bloggy Stuff - hooray?
    8. Re:huh? by mpapet · · Score: 1

      Aperture and whatever Adobe calls theirs, are acquisition and cataloging tools for digital photos. Do not confuse those tasks with editing.

      Check out digikam. It was omitted from the review for unknown reasons. It's excellent! It'll give you a good idea of why one would want to separate acquisition from editing.

      --
      http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    9. Re:huh? by brassman · · Score: 5, Informative

      "RAW" photos are a lossless capture, which means they are larger files (bad) but with few of the artifacts produced by JPEG compression, and thus your editing options are greatly increased (good).

      The exact details of the format depend on the make and even the model of camera you're using; a low-end "point and shoot" camera seldom provides RAW output (see recent Slashdot article on FOSS firmware that adds RAW support to higher-end Canon P&S cameras, however).

      A modern digital camera will also add a nice chunk of metadata to each image, giving the details of its exposure. The main difference between a FILL manager and a PHOTO manager is the latter's awareness of, and ability to use, this metadata in a "workflow."

      By "workflow" we mean the situation where a professional photographer will routinely generate thousands of images at a wedding, and will want to pick through them to find images worth further refinement, apply a set of transforms (crop, tweak the exposure, sharpen 0.02%, yada yada) to them in large batches, but SELECTIVELY, to produce a finished body of quality work.

      Managing those images only with a file manager would be nightmarish; being able to select just the images that were shot with Lens A to apply a certain transform means you can automate the process, go have pizza while the mass of bits gets twiddled, then come back and get creative with the results.

      --
      "Ain't no right way to do a wrong thing."
    10. Re:huh? by brassman · · Score: 1

      FILE manager, not FILL manager. Duh.

      --
      "Ain't no right way to do a wrong thing."
    11. Re:huh? by ColdWetDog · · Score: 1

      The RAW image is the one straight from the camera (basically a RAW dump of the CCD output).

      Photo Management includes more than just folders (a good example is tagging -- I want to find all images tagged "Outdoors" or tagged "Porn" or tagged both "Outdoor" and "Porn"). Of course, like folders, tags are only as good as you make them.

      You missed the Big Picture. Aperture is everything. It's Ansel Adams incarnate. It's the second coming. It's cool and whizzy. It takes twenty podcasts, three books and two keynote presentations to Grok. It's the photographic kitchen sink, darkroom, living room, outhouse and solarium. Not to mention the battery powered Hummer in the six car garage.

      I've played with Aperture a couple of times and I still can't figure out why people like it. To make it short and inaccurate: Professional digital photographers and persons of similar persuasion tend to shoot lots and lots of images. All of the time. That's all good fun, but the problem comes to roost when you have to figure out which 5 images of the 10,000 you shot over the weekend you are going to show to your editor.

      You have to offload them from your flash cards, organize them in some sort of reasonable fashion. The 250 pictures of the midget having sex with a horse on a fire hydrant might get the keyword tags "midget", "sex", "horse", "hydrant" and perhaps a couple of others that I will leave to your depraved imagination. It might get tagged with the GPS coordinates of the shoot (in this particular instance for really unclear reasons). You might want to arrange the pictures in some sort of order best-worst (??).

      Then you'll want to save them somewhere (your neighbor's hard drive for instance). You might want to polish up a couple by adjusting contrast, white balance, color and artistically crop the image. You will then want to put the carefully groomed photos (not the horse) in a contact sheet or web page to give to your editor.

      Aperture does this things, and of course, many many more. Which is why you need the keynote files and podcasts.

      It puts Photoshop to shame for complexity. So there it is, Aperture in a nutshell.

      Anybody who actually uses and likes the program should feel free to chime in. I'm afraid I'm a bit jaundiced.

      --
      Faster! Faster! Faster would be better!
    12. Re:huh? by VGPowerlord · · Score: 4, Funny

      Aperture Laboratories is a computer-aided enrichment center to test the Aperture Science Hand-held Portal device.

      More information is available in a video.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    13. Re:huh? by Anonymous Coward · · Score: 0

      You mean don't confuse those tasks with RETOUCHING? Editing is the thing a photo editor does- pick through lot of photos to find the desired few. Retouching is manipulation of those chosen photos.

    14. Re:huh? by mario_grgic · · Score: 1

      Yes, but very few people know that Mac Finder will let you tag photos (or any other file for that matter). And the spotlight will let you search on that meta data as well.

      Spotlight can already search for all pictures with some pattern in the name and that were created on some date range, and that were taken on some date range at some aperture, specific lens, shutter speed, camera etc...

      It's pretty powerful, and it searches images anywhere on any drive.

      This is a lot like Aperture or Lightroom. Except I like it better, since I can do spotlight searches on the CLI with

      mdfind -interpret "some complex query like above"

      and then execute complex command on the results, to archive, open for editing, etc. The possibilities are endless.

      --
      As the island of our knowledge grows, so does the shore of our ignorance.
    15. Re:huh? by poached · · Score: 1

      I shoot with a Nikon D50. It's an old DSLR, but takes all Nikon lenses and it was cheap on the used market. After I got the camera I did some tests to see how good the jpeg engine is. I shot RAW and jpeg then converted the RAW to jpeg in Lightroom and compared to the jpeg from the camera. Result was I found a big difference in quality. The jpeg from the camera had more artifacts and the colors looked washed out. Consequently I have been shooting RAW and let my computer with Lightroom handle the jpeg conversion in post process. I've been very happy with that decision ever since.

    16. Re:huh? by QuestionsNotAnswers · · Score: 1

      FOSS firmware that adds RAW support to higher-end Canon P&S cameras

      The CHDK project - open source firmware to add pro features (such as capturing to raw format) and geeky features (movement capture) to Canon A###, S# and IXUS### point+shoot model cameras. The firmware boots from the SD card (the internal firmware is not changed).

      Useful links are features and supported models (from the FAQ) and examples of results (see samples on right) using CHDK.

      It is like getting a pro upgrade to your camera (Aside: I have a PowerShot TX-1 which I love and recommend to anyone who wants a P&S camera).

      --
      Happy moony
    17. Re:huh? by drinkypoo · · Score: 1

      All of this kind of functionality could be implemented in nautilus, though, especially when combined with tracker and/or beagle.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    18. Re:huh? by Keen+Anthony · · Score: 1

      I maintain a very large collection of photos from well over a hundred digital cameras, and I use this as my reference when making camera suggestions for people. For this purpose, Mac Finder and Spotlight are great. However, neither allows me to work on actually developing the shot. I need to eyeball every shot out of the hundreds I'll take in an weekend.

      But for a while, while I was still learning Lightroom and discovering that all my meta data was being wiped out during exports, I relied extensively on command line tools such as exiftool. As you said, the possibilities are endless.

      For me the perfect digital dark room is still a combination of workflow software for developing my shots and separate specialized tools for archival.

  10. digiKam? by Anonymous Coward · · Score: 5, Informative

    What, has no-one mentioned digiKam yet?
    What a terrible omission from the review.

    Take a look, it's really good.

    1. Re:digiKam? by UNIX_Meister · · Score: 1

      Maybe I'm missing something, but one thing I like about some of the other programs (even F-Spot) was the ability to version files, and it seems that digiKam doesn't do it. Or is there a kipi plugin for that?

    2. Re:digiKam? by Anonymous Coward · · Score: 0

      installing KDE software is beyond the wit of most gnome users (and if the author has been using nautilus, he's presumably a gnome user). Desktop Darwinism at its finest.

    3. Re:digiKam? by MMC+Monster · · Score: 4, Informative

      Totally agree.

      I prefer Digikam to iPhoto for many reasons. The most important to me is that I can keep a folder organization that makes logical sense on disc and have it reflected in digikam.

      One thing it gets right that other photo managers get wrong: Selecting photos and moving them to another photo will bring up a small dialog asking if you want to copy or move the files. Stupid and irrelevant for /.'ers, but great for those that forget that holding down the shift or control keys are how this is generally done in other applications (like my dad, who constantly screws up his iPhoto folders by copying when he thinks he is moving, or vice versa).

      One slight gripe: It follows the KDE standard of a single click opening a photo instead of selecting it (easily changed by installing kcontrol in ubuntu and changing the mouse property).

      --
      Help! I'm a slashdot refugee.
    4. Re:digiKam? by TruthfulLiar · · Score: 1

      I actually installed digiKam last night to take a look at it, but it looks like you have to import your stuff into their album management. I'd rather keep my files organized by the filesystem, not organized by some program that I may or may not be using five years from now. Is it possible to open up a raw file and just edit it? Can I at least say "here's the root directory of the pictures, let me look at them but don't put any special databases anyway, just treat them like files"?

    5. Re:digiKam? by MMC+Monster · · Score: 1

      (Yes, I'm responding to the troll...)

      If you use any of the standard ways of installing digikam on Ubuntu, you don't have any issues. The package managers will automatically download and install the necessary parts of KDE without changing your desktop from gnome to KDE.

      The only way you'll realize that it's a KDE app is that it installs a lot of dependencies and that left-clicking on a photo will open it (KDE default) rather than selecting it (Gnome default), and to change that option you have to install kcontrol.

      --
      Help! I'm a slashdot refugee.
    6. Re:digiKam? by MMC+Monster · · Score: 3, Insightful

      Actually, no.

      You point digikam to the root folder of your photos. It will create a single file there consisting of it's database.

      No importing of folders necessary. :-)

      Maybe you had it confused with f-spot?

      Give it a try. You'll really love it and never go back. :-)

      --
      Help! I'm a slashdot refugee.
    7. Re:digiKam? by MMC+Monster · · Score: 4, Informative

      To clarify. If you move a photo in digikam to another folder, it will move that file to the corresponding folder on the disk (just as you would expect it to).

      The purpose of the database file is (I believe) just to keep track of thumbnail images it creates.

      I'm not sure about RAW file support. According to this web page ( http://www.digikam.org/drupal/node/344 ), RAW is supported with a standard plugin.

      --
      Help! I'm a slashdot refugee.
    8. Re:digiKam? by jmodule · · Score: 1

      I think it's a future enhancement still. Maybe scheduled for release 0.10

      --
      The jModule
    9. Re:digiKam? by nairb774 · · Score: 1

      Not to nitpick - but as you point out it is a KDE level option. I was waiting for someone to point out digiKam as it is my favorite but I have never run into the one-click-opens action. Though I have double click opens a folder/file/... as the default setting. Just waiting for Qt4 to be used with digiKam and we might have something worth showing mac/win people... It is the one program I wish I could have on my vista laptop, mac book, and my linux desktop.

    10. Re:digiKam? by TheQuantumShift · · Score: 1

      If you like KDE apps, which I don't. There's just something about the interface and menus and what not that I just can't stand. Oh well.

      Back on topic, I personally use rawstudio to import from my camera do some basic adjustments and then export to gimp. And mono be damned, F-Spot is a perfect iPhoto replacement. I've played with lightroom and aperture on vista and leopard respectively and find both work well, but just don't justify their pricetag for me.

      There are plenty of options, and they should all be available in most distro's repos, so just try them all (even the KDE stuff). I used synaptic and searched "camera" and installed anything that looked decent. I found dcraw liked my camera better than ufraw even though ufraw lists my model as supported and dcraw does not... So as always, YMMV.

      --

      Shift happens. Fire it up.
    11. Re:digiKam? by Anonymous Coward · · Score: 0

      I vote for digikam. I've been using it for over a year now. Very nice for tagging and management.

    12. Re:digiKam? by the_womble · · Score: 1

      RAW support depends somewhat on your camera. With my Panasonic FZ-18 Digikam 0.3.9 works fine with kipi-plugins installed. I have not tried without kipi plugins. One gotcha is that if you upgrade, the thumbnails of images in previously unsupported RAW formats are not automatically updated.

    13. Re:digiKam? by worf_mo · · Score: 1

      Re your slight gripe: single clicking on the photo's caption will select it, clicking on the thumbnail will open it.

  11. Definition of the Golden Ratio from Wikipedia by Anonymous Coward · · Score: 0, Flamebait

    At least since the Renaissance, many artists and architects have proportioned their works to approximate the golden ratioâ"especially in the form of the golden rectangle, in which the ratio of the longer side to the shorter is the golden ratioâ"believing this proportion to be aesthetically pleasing.

    Now, aside from disliking an Apple product, how is he a tool?

    "non-standard" ahhhh, that's funny. We're talking about digital photography here; not analog. And even then, the masters, such as Adams, would trim their photos to look the way he wanted them: sometimes trimmed them to "non-standard" sizes - gasp!

    1. Re:Definition of the Golden Ratio from Wikipedia by Anonymous Coward · · Score: 0

      You don't hear about Ansel refusing to publish anything not conforming to the particularly bullshit-laden Golden Ratio, do you? The problem I see is that this tool relies on a magic number to make his pictures aesthetically pleasing. I prefer the old fashioned way, SHOOT SOMETHING NICE.

    2. Re:Definition of the Golden Ratio from Wikipedia by jonnythan · · Score: 2, Insightful

      It's non-standard because no camera sensor or standard print size uses that ratio.

      I don't care if he dislikes any Apple products. In fact, he seems to be quite fond of Apple products, since he uses them.

      No halfway decent photographer shoehorns absolutely all of his work into ONE nonstandard aspect ratio. Different compositions require different aspect ratios.

      The only reason to use one aspect ratio on all of your compositions is that you're simply not good or talented enough to know any better.

    3. Re:Definition of the Golden Ratio from Wikipedia by Anonymous Coward · · Score: 0

      "Different compositions require different aspect ratios." Me think you discuss this with the photo paper manufacturers. ...and while you are researching pointless things (like paper sizes) you may read about the golden ratio.

    4. Re:Definition of the Golden Ratio from Wikipedia by Iberian · · Score: 1

      Going to play advocate here but maybe (and this is one of those 1 in 6 billion maybes) he is a really really good artist and using this golden ratio of his he has created a masterful collection that he will soon release and the world will hail him as the new Ansel Picasso.

    5. Re:Definition of the Golden Ratio from Wikipedia by Draek · · Score: 1

      Well, I've seen plenty of "halfway decent" photographers limiting themselves to a given aspect ratio for part of their artistic careers (though it's usually 1:1 or 5:4 instead of ~1.62:1) and if he's doing that, who are *we* (let alone Picasa) to decide otherwise, or to discriminate against him for that?

      No offense meant, but your original comment struck me as close-minded as the old "OMG he's still using film? so pathetic!" comment you often hear from young wanna-bes.

      --
      No problem is insoluble in all conceivable circumstances.
  12. A happy LightZone user by Anonymous Coward · · Score: 0

    I have purchased LightZone for Linux after using a free beta version for 2 months. For early adopters there was a $50 discount :-)

    There _are_ support forums http://www.lightcrafts.com/support/forums/index.html

    I find LightZone an excellent product. It is quite adequate for making your photos look good quickly. A choice of tools is somewhat limited, but they all have built-in feathered selection/regions. The ZoneMapper and Relight tools are unique. There are very nice learning videos, see http://www.lightcrafts.com/learning/index.html

    There were discussions on LightZone forums of how this product compares to Bibble, and most users prefer LightZone. Bibble 5 might change that, but then again there will be probably a new version of LightZone released soon.

    I am a very happy LightZone user and can highly recommend it.

  13. Re:What a tool by ColdWetDog · · Score: 1

    I stopped caring when the author said that he crops "all" his photos to the same (non-standard) ratio.

    Oh, I gave him that one - artistic expression and all that. What killed me was the smilies.

    Real reviews don't use smilies. Ever.

    --
    Faster! Faster! Faster would be better!
  14. Mod Parent Wrong by mpapet · · Score: 1

    1. Gimp 2.4 color manages very nicely thank you.
    2. The KDE desktop has monitor profile and gamma adjustment support. GNOME? Dunno.

    Applications worth noting:
    xcalib

    liblcms (excellent)
    argyle (for you color geeks)
    scribus
    digikam

    You will find most commercial profile generators place restrictive covenants on the icc profiles created by their software. I don't know if it is legal to redistribute sRGB or AdobeRGB profiles, but I doubt it.

    It's also worth noting that Aperture's sole purpose is rapid acquisition and cataloging. Do not concatenate acquisition/cataloging with editing.

    Lastly, Digikam works very nicely for me.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Mod Parent Wrong by Guido+von+Guido · · Score: 1

      "It's also worth noting that Aperture's sole purpose is rapid acquisition and cataloging. Do not concatenate acquisition/cataloging with editing."

      Did you mean "primary purpose?" Because I could buy that. However, since you can use Aperture to adjust exposure, contrast, saturation and make other adjustments like sharpening and dodging and burning, you can certainly use Aperture to edit your photos.

      Its editing capabilities are limited compared to Photoshop or the GIMP, but then again it is (as you said) intended as more of a cataloguing/workflow tool.

  15. Extensis Portfolio by UNIX_Meister · · Score: 1

    Has anyone tried to run this under wine? The wine app db only has old entries for this media management package.

  16. Open, but perhaps not Free by bill_mcgonigle · · Score: 2, Informative

    F-Spot, The default photo editor that comes with Ubuntu 8.04, was quickly discarded. [FOSS]

    Maybe change that to [fOSS].

    It's open source, for sure, but since F-Spot is built on mono, a port of Microsoft .NET, it probably contains Microsoft intellectual property, the licensing of which may be dependent on which distro (e.g. SUSE) you're running, so 'Free' is debatable.

    It could be a patent trap ... or not. That uncertainty is certainly disconcerting.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:Open, but perhaps not Free by tqft · · Score: 1
      --
      The Singularity is closer than you think
      Quant
    2. Re:Open, but perhaps not Free by bill_mcgonigle · · Score: 1

      What a great idea. Do you know if somebody has done the RPM version yet?

      I was a GNOME proponent for the better part of a decade, and dumped the whole thing when they went Microsoft.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  17. Yeah, but try explaining it to your someone! by Saint+Stephen · · Score: 1

    I used to have these awesome perl scripts that selected some random FLAC files that hadn't been selected lately, decompressed them and converted them to mp3 on the fly, and copied them to my sandisk player. "It does everything itunes can do!" Then I tried showing it to somebody (a chick) - got all flustered, and f*cked it up. "Just use iTunes" I said in defeat :-)

    1. Re:Yeah, but try explaining it to your someone! by jedidiah · · Score: 1

      How does iTunes do with the non-Apple media player BTW?

      Given that iTunes doesn't even like non-Apple mp3 files, I can't imagine it being pretty.

      "The one true interface" probably doesn't do the multiple device management either, or the at-will compression.

      It sounds like the perl script is not "doing everything itunes can do" but is "doing what itunes can't".

      That's usually why people have perl scripts: The "shiny happy people" never thought of it.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Yeah, but try explaining it to your someone! by gordyf · · Score: 1

      Given that iTunes doesn't even like non-Apple mp3 files

      What are you talking about?

  18. These are the tools I use on Ubuntu : by flar2 · · Score: 2, Interesting

    I do all my photoprocessing on Ubuntu.

    -I use gthumb for organization and importing from the camera (way better than f-spot, which I've never liked)
    -I use ufraw with the GIMP plugin to process raw files
    -I use GIMP for further processing
    -I use Hugin and its associated tools for panoramas

    That's all I need, and I sell photos every week, however, I'll be looking into some of the tools mentioned in the article.

  19. Raw Therapee can handle JPEG/TIFF by smably · · Score: 5, Informative

    I don't know why the author thinks that Raw Therapee can't process JPEGs or TIFFs. Just go into the preferences screen, uncheck "Show only RAW files", and you're set.

    Also missing from the comparison: Rawstudio and UFRaw.

    If you're interested in RAW processing on Linux, there's an excellent blog called Linux Photography about this very subject.

    --
    I couldn't possibly fail to disagree with you less.
    1. Re:Raw Therapee can handle JPEG/TIFF by EvanED · · Score: 1

      UFRaw, while a fine program, isn't really a photo management program, "just" an editor.

  20. Wrong about LightZone by pauljlucas · · Score: 1
    From TFA:

    I am a bit disappointed that there is no online support forum.

    Then what's this?

    --
    If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
  21. Re:What a tool by kestasjk · · Score: 2, Funny

    But it's the golden ratio: the most perfect of ratios!

    --
    // MD_Update(&m,buf,j);
  22. Square peg, round hole by kwalker · · Score: 4, Informative

    Since the author of the blog post is asking for an Aperture clone for Linux, the answer will pretty much always be "no". If the author were to ask "Can I do my photo processing, from importing RAW files to storing the finished picture and printing?" the answer is yes.

    Here's how I do it:

    1. gthumb-import (Which uses gphoto) to talk to the camera and bring in the RAW files. It even imports the .mov or .avi files for videos shot from the camera.
    2. gthumb for photo organization. You can do some basic photo manips (Rotation) right from here, as well as tagging, categorization, and creating collections.
    3. gimp (with ufraw-gimp to decode the RAW structure and doing some initial tricks like exposure-compensation and white balance) for more advanced photo manipulation, cropping, rotation (For anything other than 90-degree-increment rotations), perspective correction, red-eye removal, HDR, de-noising (Using GREYCstoration-gimp), workflow-automation (It's scriptable in Perl, Python, and others) and finishing after running through other programs like...
    4. hugin for panoramic creation. Photo-stitching is pretty easy. It helps with reference-point creation, FOV calculation, and final panorama "projection" (rectliniar, square, wrap-around, etc).

    Just save all projects in .xcf or .xcf.bz2 and export finished product to .png.

    One last thing, for all the haters who whine about ONLY having 16.8 million colors to work with, even without your help GIMP is integrating GEGL which will bring 16bit integer and 32bit floating point per component.

    --
    ... And so it comes to this.
    1. Re:Square peg, round hole by flar2 · · Score: 1

      This is exactly my setup. Works great.

    2. Re:Square peg, round hole by Lincolnshire+Poacher · · Score: 1

      > gthumb-import (Which uses gphoto) to talk to the camera and bring in the RAW files.

      Not being familiar with this tool, what is the advantage of just rsyncing the files over USB mass storage? Seems to be adding a layer of complexity for no realy gain.

    3. Re:Square peg, round hole by jockm · · Score: 2, Insightful

      8BPP is fine for viewing images, or just making a few edits. But having only 256 steps in each channel becomes a liability very quickly if you need to apply a few filters, touch up a bit, do a little dodging, etc. You quickly loose the subtly.

      I am very excited that GIMP is integrating with GEGL. Of course I have been waiting 6 years for this (not kidding that is when the effort to go beyond 8BPP started), and it still isn't out yet. So I am not going to hold my breath until it comes out.

      But even when it does GIMP is still going to be lacking compared to Photoshop, Aperature, LightRoom, and ZoneEdit when it comes to nondestructive editing. So even with CEGL it is still going to be a hard sell for me to consider GIMP

      --

      What do you know I wrote a novel
    4. Re:Square peg, round hole by kwalker · · Score: 1

      Not all cameras show up as usb-storage devices. Some speak "PTP" (Photo Transfer Protocol) which gphoto understands.

      If you're running a modern GNOME desktop, when you plug in your camera, gthumb-import auto-launches and asks if you want to import, so it's actually easier than opening a terminal and rsyncing (Especially if you don't have a script to handle most of the mundane details for you). Plus it auto-launches gthumb on the newly imported directory (generally named the date-time of the import, so as to avoid stomping on existing images) for easier photo management.

      Not being a KDE user, I don't know if it has anything like this, but I imagine it probably does.

      --
      ... And so it comes to this.
    5. Re:Square peg, round hole by kwalker · · Score: 1

      Um, from the GEGL website:

      GEGL provides infratructure to do demand based cached non destructive image editing on larger than RAM buffers. Through babl it provides support for a wide range of color models and pixel storage formats for input and output.

      So UFraw won't been necessary, assuming GEGL supports as many formats.

      --
      ... And so it comes to this.
    6. Re:Square peg, round hole by UnknowingFool · · Score: 1

      I think though the author wants one package or at least, well integrated products to handle all of it. It's not Linux apps can't do what Aperture and Lightroom does. Ten years ago if you asked how to play MP3s from CDs, the answer would have been something like 1) Rip the audio from your CD using this ripper program, 2) Encode into MP3 using this encoder program, 3) Load MP3 into your audio player program, and 4) If you need add things like lyrics or tags like song name, album, use this other program. Eventually it evolved to where 1 application handles all of it. If there is a need for Aperture/Lightroom Linux substitutes, they will come along eventually.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    7. Re:Square peg, round hole by Eponymous+Bastard · · Score: 1

      One last thing, for all the haters who whine about ONLY having 16.8 million colors to work with, even without your help GIMP is integrating GEGL which will bring 16bit integer and 32bit floating point per component.

      They've been "integrating GEGL" for at least a year and very little progress has been made. I've looked at the source, straight from SVN, and the documentation to see if I could help move things along and there is zero documentation on how GEGL is going to be integrated with the layering and rendering of the Gimp.

      The only integration so far is to allow GEGL operations to be used as a plugin/filter for manipulating a layer, and to define some Gimp tools (Levels, etc) as GEGL ops. I've seen no progress on the actual integration. The last I saw was the development of some infrastructure to save tool presets more easily (that's a high priority feature???)

      Since there is close to zero documentation on the Gimp's internals, any attempt to help with the project is likely to be abandoned. And no, Doxygen-generated docs from comment-free files don't count as documentation. The same info can be gathered from the header files much more efficiently.

      If you can point to some document describing how the gimp composites layers (not just the tiling part), and what the plan is for changing that to use GEGL I might be able to help (Though my free time is now being used differently). Heck, I'd be happy with just some global documentation on the design. Am I allowed to use the widgets in /libwidget when developing tools or just the ones from /app/widgets? How is composition done? How are the horrible tool dialogs handled so I can change them to a more sane UI? How do I add a shortcut to bring up thedialog toolbox like ctrl-L brings up layers? Hint: IRC or mailing lists does not count as documentation.

      Something I learned from looking at the Gimp. Rather than a large flagship open source project with hundreds of quick contributors, it's a project with about 5 developers and so badly documented it's unlikely anyone else will help. Good luck getting it to compete with more serious software.

      I'm currently using a SVN-compiled Gimp since they finally merged in the change to allow for transparent transforms that was submitted to bugzilla a couple years ago. I guess they finally gave up on waiting for GEGL integration to handle that.

    8. Re:Square peg, round hole by Anonymous Coward · · Score: 0

      I find it hilarious that you FOSS idiots have to manage 4 different applications (with 1 depency app and 2 plugins) to do the work of 1 single proprietary app.

    9. Re:Square peg, round hole by martyros · · Score: 1

      Personally, I think if gthumb had gimps "Levels" and "Curves" dialog, and a quicker way to open a file in Gimp, I'd probably use that for my main snapshot processing. My wife is a semi-pro photog who loves Lightroom, but I'd be much happier in Linux. :-)

      If I had time, I'd pull the functionality over myself.

      --

      TCP: Why the Internet is full of SYN.

    10. Re:Square peg, round hole by Anonymous Coward · · Score: 0

      Just so you know, although you may be merging differently exposed photos and tonemapping them, with 8-bit colour depth you aren't actually capturing the High Dynamic Range. You're tonemapping and merging, you aren't doing HDR.

      Also there's a difference between whining about gimp not supporting xyz, and stating that the reason you use [tool that isn't gimp] is that it supports features xyz, while gimp doesn't.

      Oh, and they've been talking about implementing GEGL for just about a decade now, just so you know.

  23. Cinelerra, the heroinewarrior.com version by heroine · · Score: 1

    Cinelerra does raw .cr2 decompression & all the processing in floating point. Useful for stacking hundreds of astrophotography images. Only for build system masters of course.

  24. Digikam works great for a JPEG workflow by BigJim.fr · · Score: 3, Informative

    I have used many Linux image browsers and editors along with a stable of home grown bash scripts. Even though I still use my scripts out of habit, I must say that Digikam can replace most of them and provide a seamless JPEG workflow in a state of the art environment. There are still some small things I would appreciate, such as a better curves dialog, but overall I have been a very happy user. Some tools such as the crop tool with framing aids are the best I have ever seen, and overall I have seen my photo editing time almost halved by using Digikam. It is not a general graphics editor - for retouching you still need something else, but for the basic editing (everything that touches the whole image) it fills the need perfectly. And it is the best IPTC tagger I have used so far.

    1. Re:Digikam works great for a JPEG workflow by Anonymous Coward · · Score: 0

      I can only second this: Digikam is a great photo organizer and editor including RAW support for everything that dcraw digests. I manage my almost 40'000 photographs entirely with Digikam.
      A new version for kde4 is in the make (alpha just published) that provides for the best search algorithms out there (searches in EXIF, XMP and IPTC data, fuzzy search, geolocation search doubles, similars etc.). It's the only one that supports full GPS metadata with automatic track correlation and kml export to Googleearth. A good article on photo management with Digikam is here.

  25. Lightroom runs on Mac too... by mario_grgic · · Score: 2, Insightful

    And how is disappointment with one program (it's spelled Aperture by the way), translates into not liking the OS and the hardware?

    This is just silly. If you are using the Mac, then you don't need aperture nor lightroom, since both try to be image database first and image editing software second.

    Mac OS's spotlight does everything Aperture does, and if you create regular backups you are fine.

    --
    As the island of our knowledge grows, so does the shore of our ignorance.
  26. Lightroom wins by Boarder2 · · Score: 2, Interesting

    I've fought this same battle for a few years. Originally I used Canons software to process RAWs, it was terrible and I needed an alternative.

    I tried Pixmatic Raw Shooter when it was free and that worked ok for me, and ran in Wine with minimal issues.

    I switched to Picasa when it became available for Linux and supported RAW. It had much better album management, but looking back, the photos it produced looked terrible.

    Eventually I switched to Capture One's software. I had to pay money for it, but it worked and it worked pretty well.

    Recently I'd been getting fed up with them, their website is terrible to try to get updates from and there's not really a good way to manage albums of photos.

    I gave the Aperture demo a shot as I'd just recently gotten a Macbook Pro. I found it very hard to use. Stuff just wasn't intuitive, the interface was cluttered and confusing.

    Somewhere along the line I'd tried Lightroom v1 and thought it was very good. I was going to purchase it when it came out officially. I stalled when it came out and waited too long and missed it at the $99 launch pricing. I never did end up buying it and went back to Capture One.

    Recently Adobe started up the Lightroom 2 Beta, I'm in the extended beta which will function until it's officially released and I can say with absolute certainty that I will be purchasing this when it's done. Everything about it is miles better than everything else. The interface is easy to use, and easy to get out of your way when you want to concentrate on what the photo looks like. It's got all the tools I feel I need to make it a one stop shop from import to web/print. I can't say enough good stuff about Lightroom 2 to do it justice. I guess my suggestion is that if you're really serious at all about your photos, stop screwing around with trying to find something Open Source and get Lightroom.

    Of course YMMV, and that's why there's a demo/beta. Good luck, and good shooting!

  27. Re:It's too bad Adobe got their hands on RawShoote by afidel · · Score: 3, Interesting

    Dude, RawShooter sucks horribly by comparison to Lightroom. I tried the last free version of RawShooter and it put me off so badly I almost didn't try Lightroom thinking it would be a slightly upgraded version. It was like night and day, the workflow in Lightroom just makes sense and doing slightly more complicated than simple conversion is a breeze. There's a guy out there that edited 2,000 wedding photos in three hours using Lightroom and a custom macro package, try doing that in RawShooter!

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  28. Windows FTW by reidconti · · Score: 1

    Too bad there's not an advanced app like Lightroom available for the Mac.

    Oh, wait...

  29. Absolutely! by Anonymous Coward · · Score: 0

    I am looking forward to seeing your implementation.

  30. Re:It's too bad Adobe got their hands on RawShoote by roguetrick · · Score: 4, Funny

    I'll choose Raw The Rapee for 1000. Haw haw.

    --
    -The world would be a better place if everyone had a hoverboard
  31. Exporting NEVER overwrites files by SuperKendall · · Score: 1

    I don't know what you did wrong but I do know one thing - Aperture will NEVER overwrite a fle on export, it uses the standard OS convention of using the same name with (1), (2), etc after it.

    In fact that is one of my only annoyances, that if I re-export an image I must make sure to remove the previously exported version...

    If you had used a Vault, or Time Machine, none of that would have happened. Or you could have recovered the deleted contents of the drive. There's no way to had to loose what you did.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  32. Foolish assumptions. by tjstork · · Score: 1

    Oh, please. He's blaming the OS for the failures of the app. I fully admit Aperture isn't the greatest. I just don't see the point in purchasing an entirely new system to run an app that you could run on your existing machine. So, come again?

    Where did I say that we got rid of the computer because of the Aperture? We got rid of it because it couldn't run all the Photoshop plug ins that Windows could, and Windows PCs were faster. You will note that Jobs did switch Apple to Intel shortly after we unloaded our G5.. so I guess Apple agreed!

    --
    This is my sig.
    1. Re:Foolish assumptions. by drinkypoo · · Score: 1

      G4 was faster for a while, G5 was faster for a moment, Core Duo was a champ, Core 2 Duo is even faster. Arguably Apple could have gotten more price/performance by going AMD, but that's an argument we could have for eternity and never resolve. Certainly intel became the TDP masters with Core 2.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  33. THAT'S RETARDED. by tjstork · · Score: 2

    Aperture doesn't generate filenames

    No, that's retarded. Whenever any system maintains a repository of any kind, you expect it to place its own names on things. Anything other than that is simply unacceptable. You don't buy a product like that to worry about filenames. ... you buy it do to things right..

    Secondly, why are you so moronically assuming that I switched because of Aperture? Aperture might keep me from switching back because the hole in the repository design made me lose my faith in Apple, but the real problem was that there are more Photoshop plugins for windows than there are for mac, so she switched.

    Why don't you read, instead of assume?

    --
    This is my sig.
    1. Re:THAT'S RETARDED. by zenster · · Score: 1

      Retarded? Hole in the repository? You deleted a year of your wifes professional work then lied about it and blamed the computer. Then you invent some arbitrary rules that the program should have followed to prevent you from screwing up.

      I'm not assuming that you switched because of Aperture at all. I'm assuming you are a dumbass.

  34. GQview is my choice of viewer by Anonymous Coward · · Score: 0

    What I use to view my photos is http://gqview.sourceforge.net/

    I personally prefer it greatly to e.g. F-spot. It's got more degrees of freedom and it's way faster. I think people should and will pick up the development.

  35. Been using Bibble Pro for years now by JasonB · · Score: 1

    I have been using Bibble Pro from Bibble Labs for years now, and have been very very happy with the results. I want my photo editor to be a dedicated to the task of just editing photos - I don't need it to be an all-purpose graphics tool or a file manager. In this task, Bibble really excels. It is geared towards users with higher-end needs, such as very broad raw file support, multi-threaded batch processing, and bulk workflow tools.

    Well worth the $130.

  36. He is confused by skeeto · · Score: 3, Informative

    This experiment focuses mainly on Aperture and what tools, if any, exist for Ubuntu to replace my Aperture workflow with something cross-platform and open-source that I can use on Mac OS X and Ubuntu.

    And then what he looks at,

    • F-spot
    • Picasa - proprietary
    • LightZone - proprietary
    • Bibble - proprietary
    • Raw Therapee - proprietary
    • Qtpfsgui

    He stated a criteria ("open-source"), then 4 out of 6 had nothing to do with that criteria. Nice work on consistency there, pal.

    1. Re:He is confused by jetxee · · Score: 1
      He also missed:
  37. My photo workflow by jetxee · · Score: 1

    Having tried some free, Free and non-free tools, I settled to relatively simple solutions. I just organize photos per shooting session manually.

    Directories:

    /year
    /year/YYYYMMDD-album or session name
    /year/YYYYMMDD-album or session name/subject (dups set or set of photos for a panorama stitching)

    Having preview in most file browsers helps (I am using Nautilus). GQview or EoG launches quickly if I want to view the details.

    Then I convert RAWs using UFRaw or GIMP UFRaw plugin (having file association). It is quite handy and just one click away. I save the retouched image with a different name: dscfXXXX.raf -> dscfXXXX_subject.{tif,png,jpg}. Bad shots are deleted. Dups get moved to a separate directory.

    Special needs: Hugin + autopanosift + enblend for panoramas. Qtpfsgui for HDR (I am not particularly fond of). Exposure Blend GIMP plugin for HDR imitation (I like it) or enfuse. GREYCstoration GIMP plugin is usable for noise reduction, but non-free NeatImage performs better and works in Wine. Inkscape is superb for over-the-photo writing, adding speach-bubbles, notes etc.

    This approach is flexible, cross-platform and does not depend on any particular tools (any may be substituted). Directory tree is easy to backup and filenames are easy to search. I can always distinguish good from bad, original from the retouched version etc.

    Recently I have also given another try to digiKam. It turned out to be perfectly compatible with my photo archive structure (album == folder). A really good tool for navigating in a archive, running a slideshow and photo tagging. Also it saves tags and other metadata in IPTC (nice!) and has a bunch of useful plugins. Its editing features are not bad, but I find using UFRaw/Gimp/Hugin more convenient.

    There are some other tools to consider: F-spot (too slow for me and insufficient editing tools), Blue Marine (even slower), gThumb (actually I used it and liked it a lot, it's a pity it does not save metadata in IPTC, Picasa (good interface, but proprietary, did not support UTF-8 until recently, metadata saved in a proprietary format, rather slow)

  38. Just few words about colour management by jetxee · · Score: 1
    I forgot to mention, but recent versions of GIMP and EoG do support colour management. Unfortunately I do not have colour calibration device, nor colours on may laptop cannot be adjusted. So I do not have experience in this area.

    If someone can tell how he includes also colour management into his photo workflow in GNU/Linux, it would be interesting.

  39. Command line tools by Anonymous Coward · · Score: 0

    My $0.02 here...

    If you are not afraid of the command line...

    'xv' works great for quick viewing of images, cropping, simple manipulations, etc. It supports numerous image formats. A very lightweight gimp-like tool. (Caveats: Shareware. Been around forever.)

    Package 'libjpeg' provides jpegtran, cjpeg, djpeg, etc. Useful for lossless rotations of jpeg images.

    Package 'ImageMagick' provides identify, mogrify, montage, composite, animate, etc.

    A quick perl script will let you produce thumbnailed images + HTML, letting any web browser quickly look over all your photos.

  40. OT: How do you get more control settings in KDE? by KWTm · · Score: 1

    easily changed by installing kcontrol and changing the mouse property

    Please pardon my asking this rather unrelated question about KDE, but I've been looking for some sort of excuse to ask this for a while now.

    In a KDE setup like Kubuntu, one can open the System Settings program, and it will have icons for various settings you can control, like "Mouse" or "Desktop" or "Printers".

    I used to have one called "Desktop Effects", for setting Compiz-KDE settings. When I clicked it, it would open a dialogue for tweaking the Compiz-KDE settings.

    But later, it disappeared! (I had messed around with some KDE config files in trying to re-establish previously saved KDE settings.) The icon was no longer there. I found that the icon linked to a file called "Desktop Effects.desktop" (or something like that); when I click on this "Desktop Effects.desktop" file, it opened the dialogue for tweaking the Compiz-KDE settings, exactly as before. The only problem is that I can no longer use the System Settings program to get to this particular dialogue.

    There must be some config file that says which icons appear in System Settings, right? Could someone please help me find it? Grep doesn't seem to find anything. Any help would be appreciated. Sorry about the OT post.

    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  41. Re:What a tool by Bryansix · · Score: 1

    Why not? Actually to print he would need to add on whitespace around the image to restore it to a standard ratio but the point is it could be trimmed and mounted like that. If I want to print something in a 27:2 ratio I should be able to. That Picassa doesn't allow it makes me sick.

  42. Re:It's too bad Adobe got their hands on RawShoote by Anonymous Coward · · Score: 0

    Could you email me? I tried to do the same thing (I had an unencrypted version of the last rawshooter pro package) search and replaced in a hex editor all 350d to 450d, tried all the options in the Adobe dng converter, etc., and it did not work. uaksas{at}gmail.com

  43. Some cameras do . . . by Champ · · Score: 1

    Pentax/Samsung DSLRs can shoot in DNG, and there may also be others.

    1. Re:Some cameras do . . . by Rangataua · · Score: 1

      According to Adobe, the list of cameras that natively produce DNG files is:

      Hasselblad
              H2D

      Leica
              Digital-Modul-R
              M8

      Pentax
              K10D
              K20D
              K200D

      Ricoh
              GR Digital
              GR Digital II

      Samsung
              GX-10
              GX-20
              Pro 815

    2. Re:Some cameras do . . . by Bryansix · · Score: 1

      Hasselblad and Leica are great but too expensive for 99% of users. All the other manufacturers listed are behind the curve on camera design and adoption. They might have good lenses but crappy bodies or good bodies but crappy lenses.

    3. Re:Some cameras do . . . by Keen+Anthony · · Score: 1

      Ricoh is hardly behind the times on camera design and adoption. In fact, the GR Digital and Digital II are amazing cameras. Pentax is hardly behind the times either. The K20D is also quite an amazing camera. Pentax has one of the few consumer SLRs on the market that doesn't have a kit lens that's useless.

    4. Re:Some cameras do . . . by Bryansix · · Score: 1

      I've never read a review on a Ricoh so I wouldn't really know but considering I'm a photographer in my off time and I didn't even know they made anything more then copier machines doesn't bode well. That's the adoption part of my argument.

      Pentax did come out with a few new bodies this year but before that their offerings were about a year behind the big two (Canon and Nikon). In addition Sony had better offerings as well. Pentax does have nice lenses but it's their bodies where it falls short. Does Pentax have a camera that compares to the "Canon 1Ds MarkII"?

    5. Re:Some cameras do . . . by Keen+Anthony · · Score: 1

      I'm not sure where the Pentax K20D compares with the 1DS. Pentax has pretty much withdrawn to the consumer and pro-sumer market. I would easily say that the Pentax cameras beat out Canon's Rebel line, especially when you factor in the ability to use K-mount lens going all the way back. I use a Super Tak and a Jupiter 9 whenever I can.

      Ricoh actually makes great lenses. I prefer the lens in this generation of Ricoh over what's use in the Leica D-Lux 3 line. Ricoh is harder to get in the US though. One thing to note about the GR-Digital, it's a prime lens. Really nice wide, great for B&W. I'm a street photographer, so the Ricoh would be of great use to me, though right now I shoot Canon and Pentax. I don't know if the Ricoh's feature set is something that would be useful to your photography.

      I have a Pentax K100D Super. The body on it pretty good. I like the viewfinder better than on the Rebel XTi. I also like the image stabilization system better. The K100D doesn't have the all-weather protection of the K10 (and I believe K20 as well), but it's a nice job. Of course, it loses on the pixel count. I haven't had a chance to shoot Sony, but I'd enjoy hearing a fellow slashdot shutterbug's opinion on it.

    6. Re:Some cameras do . . . by Bryansix · · Score: 1

      I know the XTi (and not XSi) do not stack up (although I own an XT and bought my work an XTi because I'm poor). The 40D by Canon would be a better comparison to the K100D Super. It has a bigger viewfinder and more rigid construction compared to the XTi and the like. Canon also makes some nice primes. I own a 50mm f/1.8 I picked up for $80. I also just bought a 100mm F/2 prime that's somewhere between New York and Los Angeles right now on it's way to me.

      The Sony is nice. I have not personally shot one but a friend of mine has one. She has the Alpha 100 and she likes it so far. She looked at both Canon and Nikon and settled on Sony. Sony made out like a bandit by taking over the Konica Minolta line of cameras and the newer Alpha 700 makes me drool. Plus word has it the old lenses from the KM days still work on it.

  44. ufraw is terribly slow by jnelson4765 · · Score: 1

    It's a nice enough engine, with some quirks, but having to process 300 pictures with it from an event sucks. A lot. Aperture lets me get it done in a tenth the time. It was trying to process 50 pictures from a shoot that made me give up on Linux for serious photo editing - ufraw is good for the occasional shot, but it's too slow and clunky for someone who has to justify the time spent on the software.

    --
    Why can't I mod "-1 Idiot"?
  45. No, that's not it by Estanislao+Mart�nez · · Score: 1

    "RAW" photos are a lossless capture, which means they are larger files (bad) but with few of the artifacts produced by JPEG compression, and thus your editing options are greatly increased (good).

    That, while strictly true, is not the correct answer. RAW images are the raw data from the camera sensor, with little if any processing. That raw data must be processed to generate a raster image like a jpeg, tiff or png.

    Nearly all cameras come set up so that the RAW -> JPEG conversion happens on the camera. This conversion, in a good camera, results in two things:

    1. Loss of information--JPEG only supports 8 bits per color channel per pixel; camera sensors often have more dynamic range than that.
    2. RAW -> JPEG conversion performs interpolation, which adds information not present in the raw data.

    Setting your camera to output RAW and processing the RAW files in your computer allows you to control the raw conversion. A RAW converter in your computer can sometimes get more detail, and most usefully, allows you to compensate for under or overexposure to some degree.

  46. I see a few missed apps listed here. by UncleRage · · Score: 2, Informative

    But I'm a bit surprised to see that no one has mentioned BlueMarine.

    Granted, I'm just beginning to examine how such applications address me needs (not sure if they do, yet... Adobe Bridge seems to be all I need), but I do like the way that BlueMarine works.

    Any thoughts?

    --
    #SickNotWeak
  47. Working with 16-bit files by antipode · · Score: 1

    Last time I looked at it, Gimp could not work with 16-bit TIFF files (it could open them, but then converting to 8-bit). This was Gimp's big shortcoming as far as serious photo editing is concerned. Perhaps the situation changed.

    --
    Arcady Genkin
  48. Canon 1ds raw tiff file by TechwoIf · · Score: 2, Interesting

    I've been playing with Linux software and not had any success in getting Canon 1ds, not mark II or mark III, *.tif file recognized. Each program that claim raw support only loads up the tiny jpeg thumbnail in the *.tif, not the raw data itself. Has anyone found a solution for this?

    1. Re:Canon 1ds raw tiff file by pauljlucas · · Score: 1

      LightZone correctly handles Canon 1DS RAW TIFF files. (It was rather silly of Canon to put raw data into a file having a .tif extension.)

      --
      If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
  49. Why Aperture sucks by tjstork · · Score: 1

    Then you invent some arbitrary rules that the program should have followed to prevent you from screwing up.

    I'm sorry that you feel that these are arbitrary rules, but really, this is consistent, standard practice in computers.

    Every repository of any kind must impose its own keys on data. It's really simple. You can't be relying on someone else's external key because in general you can't assume that is unique, particularly when you start mixing information from a variety of sources.

    XML, C#, Java, C++, all have namespaces. Name spaces allow you to mix in multiple sources into your data, program, or even a web page, all which must deal with the problem of aggregation. In all cases, you have a foreign sort of data you are integrating, and a way for the consumer of that information to organize that into namespaces.

    More directly, in document management systems, dating all the way back to big systems used by the government to many systems used by corporations, every document, regardless of its file path and place of origin, receives a unique name on import. This not only makes it easier for the developers of those systems to attach meta-data to the document being imported, but it also allows the repository to function as an aggregation tool. For example, you could, take a bunch of documents from many sources, ram into a document management system, and then, export those documents back out into a single folder, and the resulting documents would be uniquely named because the repository correctly managed the names.

    Or, you could easily and consistently make URIs for them on web pages. Even better blogs do this by default, although it is admittedly not as important because we do have a sort of assumption that a good URI is unique.

    In any case, this practice is so pervasive that relational database vendors ALL follow a similar pattern to support the inclusion of images and documents into their database. They can either link to a document, store the document directly, or, allow the developer to store the originating path as a field. Regardless of which approach is adopted, the DBA will invariably create his own key on that document table, and use that key as a primary key. This is often an integer and is often autopopulated by the database engine using either autonumber in SQL Server or sequences in Oracle. I tend to prefer Oracle sequences as I think they are easier to work with, but, to each his own.

    It is interesting to note then, that the file system is actually not very good at managing names and this is actually a good reason for why they fail. Why do you have to have the same name for something in two different places on the computer? In a perfect world, a filename ought to be unique by itself, and, where it is stored in a file system would be only an organizational convention, but not an identifying one. Then you wouldn't need stupid things like PATHs at all, and all the security holes that they open up, a problem with, incidentally, that this very message board takes its name from!

    With all that said, it was reasonable to think that a very expensive product like Aperture would, in fact, do the right thing with its images, which is why I bought for my wife. Apple is a damned good software company and they, of all people, should know better as they have been wrestling with namespace problems since the inception of personal computers, but, in the case of Aperture, they blew it. And, no, I didn't sell the Mac because Aperture screwed up. Aperture screwed up as she was exporting images out AFTER we sold the thing. There's no lie, only disappointment in a product. It's no different than someone who buys a Ford, loses a tranny, and then never buys a Ford again. In my case too, my Apple "hatred" really isn't hatred. I still admire Apple's service and I like Macintosh, I really do. But I think Linux is a better operating system for server applications and that's where all the money is that these days. Now, I might still get a Mac to write a game for, bu

    --
    This is my sig.
    1. Re:Why Aperture sucks by Keen+Anthony · · Score: 1

      I take it the titles you use were pulled from the filename of your exports. I gave up on Aperture a while back when I couldn't get support for my cameras. Under Lightroom, when exporting I am presented with an option to adjust the custom naming convention I use for exports generally. I would expect Aperture to do this as well.

      Now Mac is a different OS on commodity hardware, and I don't see much of a point.

      You mentioned writing a game for Macintosh. If you wanted to do that, a Macintosh would be the better platform to work from as opposed to porting from another. There's several great tools at your disposal; Xcode, OpenGL, ClanLib, SDL is a great combo. You can do the development on Linux just as easily, but I really have enjoyed Xcode. You might too.

    2. Re:Why Aperture sucks by Katchina'404 · · Score: 1

      Let's see, there are many ways to backup your Aperture files :
      * OS X Time Machine (system-wide incremental backup).
      * Aperture Vault (Aperture's own incremental backup).
      * Manually copying the Aperture Vault directory (yes it's a directory, no it's not an evil black box).
      * Selecting ALL files from ALL projects in Aperture and exporting the master (raw) files to a "flat" directory. It's kind of a bummer that, according to you, Aperture overwrites similarly named files when doing this although I find it hard to believe. But Aperture lets you decide the exported file names so using something like %originalname%_%dateandtime% would probably have been enough.

      I am amazed that of all these methods you have chosen the most tedious one, and certainly one that is not put forward by the software developer (Apple in this case).

      As you say "You don't buy a product like that to worry about filenames" and I would even broaden this to "You don't buy a product like that to worry about files". But still, you decided you'd worry about files anyway, and failed to make sure that you were doing it properly, and only found out about it the hard way. Too bad, I can understand that you're mad, but don't blame others...

      --
      Ceci n'est pas une signature
  50. meta data by Anonymous Coward · · Score: 0

    For meta data management (i.e. adding & searching), I find MaPiVi
    most satisfying.

  51. Lightzone Linux binaries were time limited by Anonymous Coward · · Score: 0

    The last releases of lightzone for Linux were time limited in that they would not run after a given date. I don't know if the 2.x versions were time limited.

  52. Re:OT: How do you get more control settings in KDE by drinkypoo · · Score: 1

    I know under GNOME you install simple-ccsm to tweak detailed compiz settings, and you use alacarte to edit menus. Hope this helps you at least find some good search terms. If you ran Ubuntu instead of Kubuntu, you'd be home now :D

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  53. Combination of tools by Builder · · Score: 1

    Any solution that uses a combination of tools has completely missed the point of Aperture and Lightroom. The amount you can do just within these apps is what makes them so great.

    My old workflow used to consist of the following tools / processes:
    - Adobe Bridge (tagging, selecting, correcting RAW)
    - Adobe Photoshop (curves, colour correction, sharpening, print sizing, etc.)
    - Noise Ninja if required

    Every single photograph went through at least the first two steps, and I had to manually manage files so as to have originals to revert to - none of the above gave me non-destructive editing. This meant that creative fiddling took so much longer.

    Today, my workflow consists of
    - Lightroom (tagging, stacking, levels, curves, exposure, colour correction)
    - Photoshop (selective sharpening, creative bits)

    This isn't even getting into the timesaving issues of having presets to match my camera settings available for Lightroom.

    My average time to process a standard image for stock use has gone from about 10 minutes to around 3, just by purchasing lightroom. That means I can process 3 images in the time it used to take 1. That's worth a couple of hundred pounds to me !

  54. I'll take on GlaDoS any day by Anonymous Coward · · Score: 0

    Look at you, hacker. A pathetic creature of meat and bone, panting and sweating as you run through my corridors. How can you challenge a perfect, immortal machine?

  55. Actually, Mac might be easier for games than... by tjstork · · Score: 1

    You mentioned writing a game for Macintosh. If you wanted to do that, a Macintosh would be the better platform to work from as opposed to porting from another. There's several great tools at your disposal; Xcode, OpenGL, ClanLib, SDL is a great combo. You can do the development on Linux just as easily, but I really have enjoyed Xcode. You might too.

    Actually, if I did write a game for a *nix, it probably would be for Mac. Only because, while SDL + OpenGL for Linux is pretty solid, the sound situation seems up in the air for me because it looks like there are so many different sound solutions out there for it. On the other hand, the Mac is a standardized platform. I've heard a lot of good things about XCode and I couldn't be a self respecting Geek without giving it a shot.

    --
    This is my sig.
    1. Re:Actually, Mac might be easier for games than... by Keen+Anthony · · Score: 1

      I enjoy it myself. There are other kits out there as well for the Mac platform, one made by Popcap (Bejeweled, Zuma). I only recommended the standard FOSS considering the neighborhood. :D

  56. Re:What a tool by Zebedeu · · Score: 1

    Picasa allows it, it's the "Manual" option on the crop menu.
    Of course it requires a good eye and stable hands, but is *is* possible :-)

  57. Re:What a tool by Bryansix · · Score: 1

    But why be approximate when you can be exact? Even programs that don't allow you to set ratios still let you put in dimensions and then hold that ratio as you expand the selection to crop. That is what I consider "Manual". Just drawing a free-select crop is lame. Plus I'm sure Picasa lacks the ability to then expand the canvas back out to the right ratio to print the damned thing.

  58. Re:What a tool by Zebedeu · · Score: 1

    I was kidding, man :-)

    The manual crop is a joke. It doesn't even give you any information on the size of the crop (pixels would be nice), and, as you say, it should be possible to type either exact pixels or a ratio, like Gimp does.

  59. Re:What a tool by poopdeville · · Score: 1

    A sentence fragment. The author did not think.

    --
    After all, I am strangely colored.
  60. Bibble Pro HAS in-the-image tagging that pros use, by Anonymous Coward · · Score: 0

    and EXIF.

    If you're looking for a database-of-images that are tagged-in-the-database, then that's different.

    http://www.bibblelabs.com/

    PS: Bibble Pro is $130, the Bibble Lite, without batch processing etc, is, oh, Less(tm)... :)