Just some stuff about photography

BY TAG

A matter of Exposure

in Product reviews , Saturday, February 18, 2017

In a bit of a fit of retail therapy, the other day I decided to buy a license for Alienskin Exposure 2. This is an application with its roots very firmly in film emulation, but which in recent years has expanded into a full blown digital RAW file processor and - to some limited extent - organiser. In the past I've written a bit about trying out various film emulation methods, and being generally unconvinced. Since I used film extensively, and still do to some extent, I do have a reasonable idea of what I would expect such software to deliver, and I also the real thing to compare against. I'm not really interested any more in trying to emulate film, as such. If I want a Portra look, I'll use Portra. But what does interested me is being able to apply a preset, or whatever you want to call it, to a given batch of photos, thereby giving them a coherent feel, while at the same time being able to speed up the process of all this adjustment stuff and get to the actually interesting part (for me, anyway) of editing and publishing. I tend to get so overwhelmed with the adjustment part, in the limited time I have, that it seems I'll never get to the actual point of it all. I also horrify myself with the sheer quantity of photos I take, even when I'm under the impression that I'm a model of self-restraint. This "preset" approach I find is more adapted to my urban photography than landscape, or whatever you want to call it. Sometime last year I took advantage of a special offer and bought a VCSO film preset package for Lightroom, just to explore it a bit. Clearly it didn't grab me much, as by now I'd practically forgotten about it. However earlier this week, I started working on a smallish set of photos recently taken in Buenos Aires, and decided to try applying the VCSO Portra 400 presets. I quite liked what I was seeing, although the results did seem a little contrasty to me, and VCSO's idea of what the ultimate hipster cliché 2-stop overexposed Portra 400 looks like doesn't correspond at all to what I see on film. I had tried out Exposure a while ago, but at that point felt it didn't offer me anything. But anyway, needing an excuse to spend money to make me fell better, I tried it again. And I'm glad I did. The interesting thing is, when I first put two versions side by side in Lightroom, one processed through VCSO, the other in Exposure 2 and imported, I immediately thought I'd wasted my money. The VCSO version was much more like Portra to my eyes. Then... I realised I had mistaken which was which. So the "good" version was from Exposure 2. Of course this is 150% subjective, and there's no real logic to it. But I repeated the experiment several times, and confirmed my opinion. However, the VCSO versions most definitely have more of that "pop" that people apparently want. But if I wanted "pop" I'd used Ektar, not Portra.
Exposure2vcso

I'm actually not going to say which is which here. But you can probably guess.

So I'm pretty happy with Exposure 2, but working out how to use it is a bit tricky. It can work standalone, including a file/folder based browser (where it recognises Lightroom star ratings, which is handy), or it can work as a plugin. The problem with working as a plugin is that it receives a TIFF file generated by Lightroom with basic processing baked in (e.g. Adobe standard profiles). That isn't an ideal place to start from, which I imagine is one of the drivers behind expanding the reach of Exposure in the first place. The standalone Exposure 2 is actually quite impressive. It doesn't seem to have received much praise or attention, but from a toolset point of view it combines a lot of the better aspects of both Lightroom and Capture One, and adds a twist of its own. The layer methodology, for example is better than either of its two august competitors. Exposure 2 has a lot of tools more specific to customising film emulation, inherited from the older plug-in only versions, and Alien Skin's from Bokeh application seems to be integrated (although that's not something I'm all that interested in). Apparently it also has automatic lens correction. But it doesn't have any chromatic aberration removal that I can see, or any perspective correction. Or, indeed, anything approach a user manual.
Exposure2vcso2

Another example. Again, you decide.

I'm quite comfortable with Lightroom these days. I appreciate the integration with things like Lr Mobile, and Adobe Spark, both of which allow me to make better use of my commute time. Lightroom, unfortunately, is an awful organiser /editor, but it is less awful than anything else on the market. There's no point any more lamenting Aperture, PhaseOne seem totally clueless on what to do with MediaPro, so Lightroom will have to do. And since organising and editing is a core part of my creative process, Lightroom is as well. So, the compromise is to use Exposure 2 standalone to generate alternative versions, and import them into Lightroom for any final tweaking and management. It would be nice if Alien Skin could add the kind of "slingshot" feature in Iridient Developer, which when receiving a TIFF from Lightroom, instead looks for and loads the associated RAW, and then when saving overwrites the TIFF, leaving Lightroom none the wiser to the sleight of hand. I'm also a bit puzzled why Exposure 2 does not include modern Portra 400 emulation, but just 400NC and 400VC. 400NC is close enough, but still, I would expect currently available films to be emulated. Otherwise, I'll repeat what I said earlier - Alienskin Exposure 2 is actually a pretty good piece of software, and not only for film emulation. I'm surprised it doesn't get more coverage.
Posted in category "Product reviews" on Saturday, February 18, 2017 at 05:00 PM

Hell freezes over

in Product reviews , Sunday, August 30, 2015

I have spent a huge amount of time and effort over the years, not to mention a little money, trying to avoid using Adobe Lightroom. The various reasons for this include that I don’t much like the GUI (compared to Aperture, RIP), I don’t much like the library (compared to Aperture, RIP), and I’m uncomfortable with the Adobe subscription model. I also have a certain sense of antipathy towards the rather over the top, uncritical, fawning cheerleading which comes from so many on-line self-appointed gurus, all of whom have their book, or video, or workshop to sell, and all of whom have contributed, thanks to killer marketing skills from Adobe, to Lightroom’s supremacy. A successful symbiotic community, but not one which has done much service to the world of digital photography in general.

But is Lightroom itself actually all that bad? Well, no, it isn’t. It’s pretty good actually, but it is neither the Second Coming, nor is it without faults, nor is it as overwhelmingly superior as the shill wolf pack would have you believe. But looking at the combination of requirements that I have personally, I have to admit, finally, that avoiding it is like cutting off my nose to spite my face. So I’ve finally admitted that resistance is not only futile, but counterproductive as well.

Lrgrab

I certainly wasn’t expecting to be looking at this, a few weeks ago.

The quality of the output from the Develop module tends to get widely derided these days on the interwebs, especially compared with CaptureOne. I’m not entirely sure why, but I suspect there is more than a grain of anti-Adobe sentiment behind this. The difference in quality, measured as resolution and definition, between all Raw converters on the market, is generally minimal. To my eyes Iridient Developer has a slight edge, but that may be down to its superlative sharpening tools. Yes, there are differences in colour rendition, but if you drill down a bit to understand why, then generally you can pretty much neutralise them. If utmost, 200% pixel peeping brick wall cat’s whiskers photography is your thing, then probably Lightroom or Adobe Camera Raw is not what you need. But otherwise, the combination of features and sheer completeness of Adobe’s offering is difficult to ignore.

The Lightroom user interface still looks to me like it has overall design philosophy. Different modules, even tools within modules, look like they were designed and integrated by different people with little communication between themselves. Indeed, the different Modules behave more like separate applications linked together through a common launcher than parts of the same application. The essential weakness of the cumbersome modal design is betrayed by the Develop Module leaking into the Library Module by way of the Quick Develop tools. It’s a pity that either stubbornness, not-invented-here syndrome, or, most likely, be-suited MBAs clutching their ROI and P&L spreadsheets is preventing a major UI overhaul. And, think of all the income from the new editions of books, videos, etc!

But on balance the experience is positive. Compared with CaptureOne, the only real advantage that I find there is that the image adjustment tools are more intuitive and faster to use, and certain features such as perspective correction (especially), highlight recovery, and clarity control, are better. On the other hand Lightroom has far better support for camera calibration, and the sharpening tools are better. I prefer CaptureOne’s layer approach to Lightroom’s edit points, and I preferred Aperture’s local edits approach to both of these, but in the end the functionality is much the same.

The killer features in Lightroom are the Library, and, surprisingly, Lightroom Mobile. The Library is almost as good as Aperture’s. It is fast, smooth, and there are plenty of well designed metadata tools. The implementation of Stacks is a half-baked copy of Aperture’s (and really, it is, just look at when it was released in Lightroom), albeit more powerful than CaptureOne’s Versions, and the Smart Collections are weak compare to Aperture’s Smart Albums, but on balance, it is - now - the best on the market. Overall, compared with CaptureOne’s improving, but incomplete and laggy Catalog, Lightoom’s Library is much easier to use. And the other major plus for me, at least, is full support for large Photoshop and TIFF files, which means I can catalogue my film scans together with my Raw files. Aperture let me do this as well - indeed, the fact that Lightroom 1 had serious file size limitations was one major factor leading me to switch - but Lightroom actually is smoother.  The only “orphan” files I have now are Sigma Merrill Raws, but nobody supports those. The workaround of cataloging a proxy JPEG and using that to launch the X3F in Iridient Developer works just as well in Lightroom as in Aperture, or indeed CaptureOne.

I think that the dependence on a physical file structure in the Library is pretty prehistoric, compared to Aperture’s fully virtual organisation, but the geek contingent could never live with the loss of explicit control that the virtual approach required, so we’re stuck in the past.  On a side note, recently I completely restructured my physical file organisation, to try to make it more convenient to PhotoSupreme’s needs.  Aperture didn’t skip a beat: together with MacOS, it noticed that the referenced files had moved, and just adjusted itself. CaptureOne, or Lightroom, would have just given up and died. But thanks to Apple shifting lock stock and barrel in to the luxury personal accessory market, we’ve lost all that innovation.

Ironically, my file structure is actually quite clumsy. This is due to an earlier period when I was using Lightroom 1, for about a year, until moving to Aperture 2.  I had to live with the file organisation imposed by Lightroom. Since this basically has never changed, re-importing into Lightroom CC was not a big deal. I did try the Aperture Importer: it’s not as good as CaptureOne’s by a long way, but not as bad as people say it is - it does actually work, albeit very, very slowly.  However, since all it really does is carry over some metadata, and that can just as easily be accomplished by writing metadata to original files or XMP sidecars, there’s little point in it. Takes forever and a day too, and the workflow is very badly designed.

I wasn’t expecting much from Lightroom Mobile, because it doesn’t do what I thought I wanted, i.e. remote editing and curation of the Library. It also gets a poor press, because it doesn’t do what a lot of people want, i.e. act as a front-end mobile file importer. What it actually does do is give you access to selected parts of your library which you have already created on the desktop, and, via “cloud” synchronisation, it then allows you to review and rate these, and to apply quite a high degree of image manipulation. On my new iPad Air 2, this works very well indeed, and actually, it turns out it is pretty close to what I wanted. Keywording would be nice to have, but what it does give me is enough to keep me constructively engaged during daily train commutes. Also, Lightroom Mobile supports importing and synchronisation of photos taken with iDevices. I haven’t tried that yet, but it is interesting. However, it does seem to conflict with a lot that Mylio provides. Mylio does do things that Lightroom Mobile does not, for example importing new files in the field and synchronising them with home and backup destinations, but several key things that it does do, and Lightroom does not, for example key wording, it does rather weakly.  I’m not really sure yet if Mylio is really needed in a Lightroom-centric workflow.

Finally, a CC subscription to Lightroom also brings Photoshop CC 2015, which has some useful additions for working with film scans, not the least being the Camera Raw plugin. I’d heard vaguely about this, but I didn’t really realise how useful it could be to be able to use ACR adjustments on a layer for film scans. Sure, there are other ways of doing everything in Photoshop, but the ACR toolset is specifically designed for photography, and makes everything much faster. And the fact that it swallows a 350Mb 16 bit XPan scan without a murmur is pretty impressive.

So, over the last months, I have invested a lot of time successively in PhotoSupreme, CaptureOne, and Mylio, and at this point pretty much discarded all of them in favour of Lightroom (maybe not Mylio, I may still have a use for that, but development seems to have slowed). It’s completely against current trends to switch FROM CaptureOne TO Lightroom, which, given my track record and general disposition, is probably as good a reason for doing it than any. Switching to Lightroom and writing a nice review about Jeff Schewe in the same month ? I must be going soft in the head.

 

Posted in category "Product reviews" on Sunday, August 30, 2015 at 08:26 PM

The Digital Print, by Jeff Schewe

in Book Reviews , Thursday, August 20, 2015

I’m firmly of the belief that a photograph isn’t finished until it is printed. And yet I make very few prints. The reasons for this include a lack of time, a lack of space to hang them on the walls, a lack of people to show them to - nobody I know is interested - and not forgetting pure unadulterated sloth. And then, when I do decided to settle down and do some printing, stuff always goes wrong. Either the printer comes up with one of it’s various ruses to frustrate me, or I forget to set something up correctly, or the colour profiles have mysteriously corrupted themselves. And then when it does work technically, the print seems to lack a certain something. A couple of days ago, I was trying to print a photo taken back in June in Norway, and on paper it just looked flat and lifeless.

Drm 2015 06 04 P6042591 1

Flat & lifeless in Norway

It was mainly to address the last point that, pretty much on a whim, I decided to buy the eBook version of Jeff Schewe’s “The Digital Print”. A successful and award-winning commercial advertising photographer, Jeff Schewe has become a well-known and larger than life figure in the world of digital imaging. He’s a very strong advocate of all things Adobe, having been closely associated with the company since very early versions of Photoshop. While earning a lot of well-deserved respect he has also cultivated an abrasive online personality especially on the forums of the Luminous Landscape. To say he doesn’t take fools gladly - or indeed anybody expressing a divergent opinion - would be as much of an understatement as to say he quite likes Lightroom. Having followed his curt, rude dismissals of all and sundry over the years, I’d decided I couldn’t stand him. Ironically, a quick glance at pretty much any personnel report on me over the past 300 years will say pretty much exactly the same thing. And that’s in person, not online. Anyway, I refused to buy his two books “The Digital Negative” and “The Digital Print” because (a) I didn’t like “forum Schewe”, and (b) I was anti-Lightroom. Well, that was a serious case of cutting off my nose to spite my face.

As it turns out, “The Digital Print” is probably the best book on digital photography I’ve ever read. It has immediately made a significant improvement to the quality of the prints which I’m able to make. Rather than just provide a dry set of instructions, it has the knack of encouraging the reader to think about how to make a good print, of what it actually means to represent a digital image on paper, and then concisely and clearly provides the technical information you need. It focuses squarely on Adobe Photoshop and Adobe Lightroom, and mainly on Epson printers, although Canon gets a look in. I have an Epson printer and I use Photoshop to print, but generally I wouldn’t touch Lightroom with a bargepole. Apple (may they rot in corporate hell) forced me to abandon Aperture, and I now use Capture One, with round trip to Iridient Developer for top picks. But the presentation of Lightroom Print Module in “The Digital Negative” is the most persuasive argument I’ve ever seen to switch. Comparing a sharp ORF file with all sharpening turned off in Camera Raw and Capture One shows noticeably more detail in Capture One. But frankly it’s unlikely to be significant in a print. Still, another migration is too painful to contemplate, and in fact a large part of the content of the book is applicable to most imaging software.

“The Digital Negative” is written in a very accessible and concise style. There is humour (sorry, “humor”), but it’s never forced, like in so many of these books. And there is no padding, although the depth of the section on Colour Theory might seem a touch excessive. Really, I think most photographers just want to know how to setup colour management and get good printer profiles. The nuts and bolts under the hood are all very well, but frankly, about as relevant as a Photoshop binary dump to most people. But the rest, covering not only preparing and printing the file, but also selecting paper, displaying and storing prints is captivating. The very detailed section on managing Epson printer settings is worth the price on its own. I’ve found out some secrets about my Epson 3800 which I have eluded me over than five or six level six years that I’ve owned it. The end result is a big smile on my face and a lot of fun making prints.

So as you can tell, if you’re at all serious about printing digital images (and that includes scanned film, by the way), I thoroughly recommend this book and herewith will consume copious amounts of crow. I should probably buy Jeff Schewe a drink or five.


p.s. - Jeff, “tirer” in French also means “to print”. A photographic print is “un tirage”. I guess 27 million people have already told you this.

 

 

Posted in category "Book Reviews" on Thursday, August 20, 2015 at 08:34 PM

Down in the details

in Photography , Tuesday, July 28, 2015

Back in June 2006, several geological eras ago in Internet years, I wrote a blog post which started out like this:

Following earlier posts about this, today I managed to find time to evaluate Iridient RAW Developer 1.5.1 against CaptureOne Pro 3.7.4, for Olympus E-1 RAWs. The results are clear: RAW Developer is extracting more detail and more neutral colour than CaptureOne

Now over 9 years later, I’m repeating the same loop. In recent months I unhappily emigrated from Aperture, and eventually settled on returning to CaptureOne as the best compromise. I painstakingly exported my Aperture library and watched CaptureOne painfully, sluggishly import it. It didn’t do too bad a job - better than Lightroom anyway - and I was more or less able to recreate my Aperture projects within the approximation of MediaPro which has been bludgeoned into CaptureOne. And I diligently set about getting back up to speed with C1, helped by the ample, free tutorial material on Phase One’s website.

I managed to convince myself I (still) quite liked the default “Film curve”, and I was and am impressed by the exposure controls and the layer adjustments, in particular to apply local white balance.  I am a lot less impressed by the total lack of luminosity, or indeed luminance curves/levels.  But I guess I can live with that with some help from the saturation sliders.

But more and more I started getting a feeling that things didn’t look quite right when taking a closer look. I’m no pixel peeper, but even so, once I’ve noticed something at 100% magnification I find it hard to ignore. I was seeing a disturbing “plastic” look in low frequency areas, and lack of definition in high frequency detail like foliage. First I thought it was just a limitation of the small sensor in the Olympus camera I mainly use, or maybe the less than top-level lenses. But then I started down the rocky road of comparing Raw developers. Yet again.

The following nondescript postcard shot from Norway provides a good example - shot with an Olympus E-P5 and 17mm f1.8 lens (actually quite a good lens) at f8.0 (which, yes, is a slightly suboptimal aperture if you’re a pixel peeper), handheld. So it’s hardly a technical masterpiece, or indeed an artistic one.

Drm 2015 06 01 P6012469

Within this photo, I’ve compared two areas at 100%, one processed with Capture One 8.2, the other with Iridient Developer 3.0.3.  The differences, at least to me, are obvious.

Iridient Developer 2

Left: Iridient - Right: Capture One

Iridient Developer

Left: Iridient - Right: Capture One

For the Iridient images, I have used default settings, including the Iridient Reveal sharpening mode and default noise reduction. On the Capture One side, I have used default settings, but with Pre-sharpening 2, and noise reduction disabled. Leaving camera default noise reduction on is a real disaster. I cannot for the life of me imagine why people say Capture One has good noise reduction. And I have tried very hard to fine tune it, I really wanted to be able live with it.  At the same time I briefly tried comparing with Adobe Camera Raw (Photoshop CS6) and Aperture 3. Abobe Camera Raw gave pretty much identical results to Capture One. Aperture was marginally better. But Iridient is miles ahead.

Iridient has one other ace up it’s sleeve, the Lab mode curves. Being able to apply contrast with no colour shift using the luminance curve is very nice. It’s also very good for highlight recovery, which is just as well, as Iridient “Extreme Highlight Recovery” slider is not one of it’s strong points. The sharpening and noise reduction are industry-leading, and the general level of control is outstanding.  Of course, there are no layers, no local adjustments, none of that fancy stuff. But that’s what Photoshop is for.

All this really only holds for my personal experience with Olympus micro-four thirds cameras. I daresay Capture One might handle my Ricoh GR better, but that’s out of scope here. I’m sure it does an excellent job with digital backs and high-end DSLRs, but I really don’t think Phase One has much focus on us “little people” - although they’re happy to take our money.

Probably before long I’ll have changed my mind again, but for the time being I’m fully committed to an Iridient-centric workflow. 

 

Posted in category "Photography" on Tuesday, July 28, 2015 at 08:55 PM

Aperture gets the boot

in Apple Aperture , Saturday, June 28, 2014

So, Apple has admitted, in some roundabout way, that Aperture is finished. It hasn’t been announced on their website, indeed, it is still promoted and up for sale. No, somehow the news has been leaked in a very uncharacteristic way.

Nobody should be surprised by this. If Apple is consistent about anything, it is in dropping products or complete product lines without any second though for its customer’s investments. But with Aperture, it’s worse. Much worse. With Aperture, it’s customers are not just financially invested, but also creatively invested. This is the drawback of both non-destructive editing and proprietary digits asset management: you need to be able to trust that the software supplier you depend on is committed to long-term support. It was always a risky bet with Apple, and now it has proven to be the case. Apple is focused purely on short-term gain in increasingly dumbed-down disposable consumer electronics, and is fundamentally an untrustworthy partner. It is telling that the company has made no formal statement on its website, and shown absolutely no concern at all for its customers’ plight, and instead offers the insulting idea that it’s a fair swap to lose years of work for some rubbish piece of iCrap gloss in “the Cloud”. And in some cases, those customer’s entire business model rested on trusting Apple as a reliable partner.

I’m pretty sure that within the Aperture team there are people who well realise just how badly customers have been let down, but with Apple’s corporate Iron Curtain firmly in place, we’ll never know. And for the rest, from Tim Cook and all his anonymous MBA cohorts, we’re collateral damage. Long term I suspect it will be their loss.

So what went wrong ? When Aperture hit the market in 2005 it was unexpected and revolutionary. It was also a massive resource hog, and expensive - $599 - and that didn’t help it gain early market share. People assumed it was a Photoshop rival, and perhaps even Steve Jobs did too, with his antipathy towards Adobe, but it wasn’t. It was something completely new, an application designed specifically for the needs of photographers in the digital age. Looking at it as a Photoshop rival obscured the real marvel of Aperture, its photo management and cataloging tools. There’s still nothing to beat it on that front, in fact as far as I know, nothing even comes close.  Then there was the non-modal UI, which some people had (and still do have) a really hard time getting their heads around.  Basically, with Aperture, you choose the context to work in (Project, Album, Book, Website, Light table, Print) and all editing and management tools are available at all times. This is quite the reverse to all other applications, including Lightroom, where the workflow is firmly object(photo)-centric.

Aperture 2

This is a key and unique feature in Aperture: here, as I lay out a selection of images on a light table, perhaps to plan a print series, I can tweak each photo’s settings in-situ as I work. The UI is completely non-modal. Were it not for the Apple Iron Curtain, whoever devised this would be celebrated in the design community. And no, it wasn’t Jonny bloody Ive. Or indeed St Steve.

So Apple had a fantastic application on their hands. But apart from high profile launch events, they essentially put no effort at all into explaining it, or marketing it. When Adobe brought out their rival application, Lightroom, which was certainly a major step forward from Photoshop for digital photo workflow, but much, much less imaginative and ambitious than Aperture, they rolled out the full force of their marketing tools, including getting legions of industry stars and opinion-formers on board, they kept up contact between engineers and users - hell, we even knew who the key engineers were - and they maintained open Beta programs for each new version. Aperture, crippled by general Apple arrogance towards customers, had no chance. The few opinion-formers they got on board seemed to be used solely as marketing mouthpieces, whereas Adobe avoided the whole control-freakery scene. As time went on, Lightroom got caught up in the Adobe bean counters insistence on yearly upgrade fees, and so started to acquire bloat and useless features, without much improvement to the core application. Also, anybody coming to Lightroom from Aperture cannot help but feel manacled by the step-by-step workflow, which reminds me of the 1990s UI “room” concepts championed by Kai Krause. Nothing like Aperture’s unconstrained creativity. Lightroom felt like an engineer’s idea of what photographers wanted. Aperture felt like a photographer’s invention which could maybe do with a touch more engineering input, especially at version 1.

But essentially Aperture was completely out of place in Apple’s product line-up. A deep, non-glitzy application that demanded, but rewarded, serious commitment on the behalf of its users. Certainly no iOS or AppStore fluff. Indeed, although the Iron Curtain lets out no whispers, I really wonder if Aperture’s genesis lies outside of Apple, much like Final Cut. Perhaps Aperture also was initially a Macromedia project, and therefore might even share some DNA with Lightroom. Pure speculation, and I guess we’ll never know. Or care.

So now what ?

Well, Aperture is still working, and Apple has committed to maintenance support for at least one further OS X iteration. But the end is irrevocable, and that means that any work expended from now on in Aperture is wasted. There’s much talk of migrating to Lightroom, or whatever, but let’s be clear: you can migrate your metadata - ratings, stars, keywords - but that’s it. You cannot migrate any develop settings, or your whole library structure, your projects, albums, smart albums, light tables, books, etc. You might be able to migrate your keyword hierarchies, which for power users is a big deal. Certainly you can migrate these to Media Pro. I have 51,225 photos in Aperture. If I were to set aside the time to recreate all the non-destructive edits in Lightroom, I might as well give up photography.

So what are the alternatives ? I’ve tried most of them: my mainstream history goes something like this: Olympus Studio -> Adobe Camera RAW 1.0 -> CaptureOne 3.6 -> Iridient Raw Developer -> Lightroom 1 -> Aperture 2 -> Aperture 3. Along the way I’ve tried out pretty much all other options available on the Mac At present I use Aperture 3 for everything, except for Sigma Merrill files which I develop in Iridient Developer (which has indeed recently become much closer integrated with Aperture).  Prior to Lightroom, indeed prior to digital, I used what was called iView MediaPro, and is now called PhaseOne MediaPro, to catalog and manage my library. I’ve carried on using it for scanned files and Sigma files alongside Aperture, and I still consider a great tool. Indeed, many years ago I speculated that a merger between CaptureOne and MediaPro would be a combination to beat. Eventually PhaseOne did acquire MediaPro, but frankly they haven’t done a lot with it.

To replace Aperture 3 we need to consider two aspects (at least). RAW development, and Digital Asset Management. There are only two real options which cover both parts. Lightroom, which is fully integrated, and CaptureOne/MediaPro, which is more like a bunch of bits flying roughly in the same direction. Although I have no particular axe to grind with Adobe, and indeed have used (and paid for) Photoshop since v2.0, InDesign since v1.0 (and Pagemaker before that, indeed before Adobe acquired it), and a whole host of other Adobe apps, I just don’t find Lightroom very inspiring. But I can’t deny that it does the job, and is probably the sensible choice. CaptureOne, on the other hand, seems to be more driven by photographers than marketing, and v7 has a management component which clearly inherits conceptually from MediaPro, although just how C1 and MediaPro are supposed to be “integrated” still puzzles me. CaptureOne went through a very bad patch after v3.x. Version 4 was very late, all-new and something of a disaster. But now at v7 it seems to have matured.

I guess in the coming weeks, I’ll try the latest versions of both on a small library and make my choice based on what I actually see, which is how I came to choose Aperture. Ill write more about this in the coming days / weeks, maybe.

But what about Apple? I’ve been an Apple customer for over 20 years. I bought my first Mac (a Powerbook Duo) on a university discount scheme. I’ve never been a fanboy, although I got close to it in the dark years of the 1990s, and I’ve always seen pros and cons to buying Apple. These days it’s more through inertia and have a considerable investment in software and peripherals that I stick with Apple. And on the whole, indeed it does “just work”. In Management Powerpoint Bullshit speak, companies talk of being in a stakeholder, partnership relationship with their customers. Apple are not. Apple, in 2014, see customers purely as cash machines. Their total wall of secrecy and refusal to engage - and it was not always so, not by a long way - makes them, as a company, amoral and totally untrustworthy. Unfortunately the whole industry is going that way. We’re a long, long way from the Revolution In The Valley.

Posted in category "Apple Aperture" on Saturday, June 28, 2014 at 03:39 PM

Page 1 of 3 pages  1 2 3 >