Saturday, 4 July 2009
Not the weather for printing
Now that all the book making is over, I've been turning my attention to running some prints and tweaking some of my favourites for paper output. This is an activity nicely timed to coincide with a spell of hot, humid weather. This is not conducive to print making. The humidity seems to cause the printed surface to absorb moisture, causing wrinkling of the paper and that is also leading to some long drying times, despite the heat. How do people in warm climes cope with this stuff?
On the positive side, I'm really happy with the output from my recent work. There are a few tricky images with subtle tones and colours that are taking some effort but most are coming straight out very nicely. My whole process is now driven from Lightroom using the custom profiles I built for my printer/paper combos.
Posted by
doonster
at
13:05
1 comments
Friday, 3 April 2009
Lightroom: nearly but not quite
Regular readers will probably be aware that I've been a long-term Lightzone user but recently have been writing about Lightroom.
Lightroom has almost completely taken over my photo-editing and management duties. It has many features to commend it - simple to use, pretty quick for most tasks, great organising features and solid printing system. However, it is just a few notches short of being quite all there.
First, as Kjell has noticed, are the problems with local adjustments. I'm sure that'll get fixed in time. Most of the time I only want small amounts of local adjustment for which it's great.
Next, and a big one for me, is the handling of sharpening. I use high radius, low amount (hiraloam) sharpening on a lot (if not, most) of my work for local contrast enhancement. I find Lightroom is not so good for that - clarity is a bit heavy-handed and I can't fine tune its effect. And I'm not enamoured of the sharpening tool in the details section. Again, not the control I'm used to with USM (or PWP's excellent advanced sharpen). This is particularly bad for scans (which usually take much more aggressive sharpening). I'm finding I have to take most images elsewhere for sharpening adjustments.
I'd also like to have support for advanced plug-in in the way Photoshop does. I've tweaked my workflow to deal with this but it does mean some back-and-forth.
I could add a list of other things I'd like to see, but then it would move Lightroom away from the things that make it good.
So what about Lightzone? Well, I do still use it but for limited applications. It is still has the best shadow recovery tools anywhere. The ability to do selective white balance is invaluable as is the ability to white balance processed files. I still it has the best masking system around especially after I discovered the clunk that is Lightroom masking. And Lightzone is still my favourite black and white converter: selective masking by area, colour, tone means I can apply multiple filter effects in lots of subtle ways. There are a couple of B&W things I do that I can't do any other place.
But Lightzone is quite rough around the edges: generally slow, memory inefficient and a host of other niggles. Development doesn't seem to be going anywhere and they are lagging behind the competition.
I think my perfect editing tool would have the layering and tools of Lightzone, integrated into the Lightroom workflow. Now that would be a powerful product. No, I don't think using Lightzone as an external editor from Lightroom fixes that. It would be nice to have a develop panel in Lightroom for Lightzone, running it as an engine underneath, controlled from the same xml file format that Lightroom uses. That would get me to the core differentiator in Lightzone (the adjustments engine) without having to suffer the niggles.
Saturday, 28 February 2009
Lightroom tip: selective masking
Lightroom 2.2, Windows XP
Read my tips intro if you're new.
Why is the brush tool so slow?
I've been doing quite a bit of brush work with Lightroom recently, especially playing with selective desaturation. I was getting frustrated by system slowdown and hang-ups so I went off to find out what's going on. what follows are some of the details, skip down to the Advice section for the what-to-do part.
In general, for small curves, limited regions and editing only a few images with the brush in a session, Lightroom 2.2 is very responsive. If, however, I start running large areas, many images in sessions or lots of changes, problems jump up.
How does Lightroom create the mask?
This is the central part of the problem, I think. When a mask is created, each stroke of the brush is saved as a separate multi-point curve. you can check this by saving the metadata to and .xmp file and opening it. the Mask has the form:
the bit in bold shows two sets of points for two strokes but for a single region. Here I've replaced all the xmp <> with [] so it doesn't get screwed up by Blogger.[crs:PaintBasedCorrections]
[rdf:Seq]
[rdf:li rdf:parseType="Resource"]
[crs:What]Correction][/crs:What]
[crs:CorrectionAmount]1.000000[/crs:CorrectionAmount]
[crs:CorrectionActive]true[/crs:CorrectionActive]
[crs:LocalExposure]0.000000[/crs:LocalExposure]
[crs:LocalSaturation]0.600000[/crs:LocalSaturation]
[crs:LocalContrast]0.000000[/crs:LocalContrast]
[crs:LocalClarity]0.200000[/crs:LocalClarity]
[crs:LocalSharpness]0.000000[/crs:LocalSharpness]
[crs:LocalBrightness]0.000000[/crs:LocalBrightness]
[crs:LocalToningHue]356.000000[/crs:LocalToningHue]
[crs:LocalToningSaturation]0.000000[/crs:LocalToningSaturation]
[crs:CorrectionMasks]
[rdf:Seq]
[rdf:li rdf:parseType="Resource"]
[crs:WhatMask/Paint][/crs:What]
[crs:MaskValue]0.900000][/crs:MaskValue]
[crs:Radius]0.023269[/crs:Radius]
[crs:Flow]1.000000[/crs:Flow]
[crs:CenterWeight]0.000000[/crs:CenterWeight]
[crs:Dabs]
[rdf:Seq]
[rdf:li]d 0.321572 0.469314[/rdf:li]
[rdf:li]d 0.326572 0.462008[/rdf:li]
[/rdf:Seq]
[/crs:Dabs]
[/rdf:li]
[rdf:li rdf:parseType="Resource"]
[crs:WhatMask/Paint][/crs:What]
[crs:MaskValue]0.900000[/crs:MaskValue]
[crs:Radius]0.023269[/crs:Radius]
[crs:Flow]1.000000[/crs:Flow]
[crs:CenterWeigh]t0.000000[/crs:CenterWeight]
[crs:Dabs]
[rdf:Seq]
[rdf:li]M 0.891740 0.296029[/rdf:li]
[rdf:li]M 0.894016 0.305266[/rdf:li]
[/rdf:Seq]
[/crs:Dabs]
[/rdf:li]
[/rdf:Seq]
[/crs:CorrectionMasks]
[/rdf:li]
[/rdf:Seq]
[/crs:PaintBasedCorrections]
If you create a large mask (as I did for the whole leopard in the shot above) then you can end up with many lines, each with thousands of points. If you really want to get anal, these can be edited down with a text editor. Easily half the points can be removed (alternate points). tedious, and not recommended.
The more you edit, the more points are generated. If you have to go back over sections, you end up with lots of overlapping lines, and repeated work being done. I think, by experiment, that Lightroom is set up to interpret each line independently, which then goes to defining the area for applying the adjustments for a give brush mask. If you've got thousands of points, that's going to take time. So I suggest using some care, and good painting technique to improve things.
Advice
So here is my advice, particularly for large areas, in this order:
1. Use the mask overlay to show the mask as you paint (key O)
2. Start with a large brush and smooth continuous strokes for large areas.
3. Use the lowest flow you can get away with (cuts the number of points generated). Faster brush work needs a higher flow.
3. Avoid reworking areas
4. Zoom in and use a smaller brush for details and edges (generally with a lower flow, and slower brush strokes).
That should help cut down the number of points generated, and the number of line segments, which should maximise performance.
Posted by
doonster
at
06:25
2
comments
Saturday, 7 February 2009
Safari workflow
I thought it would be worth writing about my workflow while I was on safari. There are a couple of reasons for this, firstly I was using a fairly unusual set-up and secondly it generated quite a lot of interest from my fellow travellers.
The hardware
I was using my new Asus Eee PC netbook, a pair of external hard discs (Freecom Mobile Drive XXS) and a basic card-reader.
The software
Normally my primary download software is Breeze Systems' Downloader Pro. Due to user error (I forgot to update the license) I only had use of it for 1 day.
I also had Lightroom 2.2 installed.
OS is Windows XP Home.
My process
As I carried a limited amount of cards (16GB of CF), I needed to download all my images daily. Ideally that would all happen through Downloader Pro so I get automatic renaming. My normal alternative renaming software is RenameMaster but I've not installed it yet (another oversight on my part).
What I actually did was to use Windows Explorer to copy of the cards and Lightroom to rename & catalogue. I tried a few options but the one that worked best was to create a new catalogue for each day for the cataloguing and then merge that with a trip catalogue once all the pictures were sorted. My overall trip catalogue was broken down into daily folders for ease of selection.
As my Eee PC only has a 16GB SSD, all downloading was to a mobile drive. Once all downloads and naming was complete, I ran AllwaySync to back-up to the second drive. I only plugged in the second drive for the period of the back-up, this in order to minimise any risk of corruption etc.
How did it all perform
Downloader Pro is definitely the most efficient download & rename route. It seems to run faster than Explorer for downloading and automatically renames in that time. I certainly noticed a difference after the first day when I was no longer able to use it. Lightroom is a bit slow, because it is generates the catalogue and previews as it goes. I tried, briefly, to use it for the downloading as well - that was a complete disaster. the whole process took more than twice as long that way. As it was, the entire process, from initial download to back-up and card reformatting took about 1.5-2h each evening. I would let Lightroom do its thing during dinner.
The Eee PC is just about powerful enough for all this. The SSD makes it seem much faster that the processor spec. Even with all the extras running (card reader, hard discs) I get about 6h battery life. This meant I could use either the power tent, or run from my own tent. I ended up doing my preliminary shot ranking after dinner in my own tent. When running without USB devices or WiFi, I get a good 8h battery life.
Lightroom runs acceptably fast on the netbook. It does require a little more patience in scrolling through lots of images and I did no editing, just cataloguing. Even so, it never hung-up or failed even on battery power. The install size I quite modest, which makes it ideal for travel like this. Using a separate catalogue for each day's download seemed to speed things up. It was a trivial task to then merge with the main catalogue. Had I not needed Lightroom for renaming, I would have skipped this step.
As ever, AllwaySync just got on and did it's thing. It's fast and reliable. I tended not to run it as a background process as I do at home so that I got maximum performance out of every application at each step.
What would I do different
For sure, I'll make sure Downloader Pro is good to go in future. Lightroom is just too slow for downloading and renaming.
I would also be tempted to have many more CF cards. That way I could use the CF as the primary storage and the hard drive(s) as back-up. That would mean carrying around 100GB for such a trip. Even if I didn't have a full complement of CF cards, it would mean I could run cataloguing every second day.
Obviously, carrying any form of computer requires access to reliable power. Having a generator in the camp helped a lot. I won't be getting rid of my mobile viewer, it's invaluable for more remote travel.
Tuesday, 20 January 2009
Lightroom tip: advanced custom curves
Lightroom 2.0, Windows XP
Read my tips intro if you're new.
How do I create my own curve profiles?
I previously posted on setting a Lightroom preset to do a basic tone curve inversion. You'll need to understand that, before reading on. I then wanted to go further, introducing my own custom curves, especially for my 35mm black and white scans.
I always scan my black and white as a positive and then invert in software. For a good explanation why you'd ever want to do this, read the post Matt Alofs wrote on the subject. When a negative is scanned as positive it usually compresses all the tones into the lower half of the spectrum, so on inversion it all ends up at the top. For me, the original positive scan rarely goes to more than 128 on a 255 scale (of course I'm scanning to 16 bit output files, not 8 bit).
After inversion, the first thing I want to do is apply a levels adjustment to bring the shadows back down into the lower tones. That meant a trip to Photoshop after importing into Lightroom to get a levels adjustment. I can, in fact, combine the 2 into one Lightroom preset. Here's how. The key is to set the "black point" of the inversion to a different point, close to the maximum scan value. So, instead of my black point origin being at 255,0, I want it at 130,0 so that the maximum scan value of 128 is just above the black point (so I can tweak later).
Here's what the preset file looks like with the change.
s = {
id = "498D92B2-EB89-4054-AAA2-46D3207AB652",
internalName = "Tone test",
title = "Invert 2",
type = "Develop",
value = {
settings = {
ConvertToGrayscale = false,
EnableGrayscaleMix = true,
ParametricDarks = 0,
ParametricHighlightSplit = 75,
ParametricHighlights = 0,
ParametricLights = 0,
ParametricMidtoneSplit = 50,
ParametricShadowSplit = 25,
ParametricShadows = 0,
ToneCurve = {
0,
255,
130,
0,
},
ToneCurveName = "Linear",
},
uuid = "8422BC3B-D8AA-4981-9F69-C350D56D935E",
},
version = 0,
}
I can now import into Lightroom applying the preset to the entire batch and get pretty good results from the off. This minimises the amount of work I need to do in other software. Of course, results may vary with film, scanner and exposure technique, so you might need to tweak the values for you own set-up.
If you're not good at reading negatives (and thus scan everything to check the best ones) this should speed things up considerably for you.
But there's more. What if I want a custom conversion curve to cover standard contrast or gamma adjustments? Well that can also be done (for positive or negative), by including extra points into the ToneCurve section of the preference. Here's a (rather stupid) example:
In fact, Lightroom curves can take any number of arbitrary x,y points to define the curve, you just have to open a text editor to get at the function.
So now, if you can translate multiple curve effects into a single curve they can be applied in Lightroom. A bit fiddly, but possible. Once the technique is known, the possibilities are endless.
Rather begs the question, if this ability exists in the software, why not expose it in the GUI?
Saturday, 13 December 2008
Lightroom tip: invert tone curve
Lightroom 2.0, Windows XP.
read my tips intro first.
How do I invert the tone curve?
I've seen a few utilities available online and a lot of questions on how to, but nowhere that showed you how. So here it is. I'm assuming you know how to create a development preset.
First you need to know a bit more about Lightroom presets. They work as formatted text files, which makes them very editable. In Windows XP they're stored at: C:\Documents and Settings\%username%\Application Data\Adobe\Lightroom regardless of software install directory (for example, I've got Lightroom installed on the G:\ drive). For this you'll need to get into the \Develop Presets\User Presets sub-folder.
But first, it's easiest to create a blank tone curve and save as preset, with a name you can remember (easier than editing from scratch). If, for eample, you created a preset called invert, go to the prest directory and open invert.lrtemplate. The text should look like this:
s = {
id = "498D92B2-EB89-4054-AAA2-46D3207AB652",
internalName = "Tone test",
title = "Invert",
type = "Develop",
value = {
settings = {
ConvertToGrayscale = false,
EnableGrayscaleMix = true,
ParametricDarks = 0,
ParametricHighlightSplit = 75,
ParametricHighlights = 0,
ParametricLights = 0,
ParametricMidtoneSplit = 50,
ParametricShadowSplit = 25,
ParametricShadows = 0,
ToneCurve = {
0,
255,
250,
0,
},
ToneCurveName = "Linear",
},
uuid = "8422BC3B-D8AA-4981-9F69-C350D56D935E",
},
version = 0,
}
Note the line title, which is what shows up in the presets list in Lightroom. The important bit here, however, is the bit labelled ToneCurve. This lists the end points for the curve. We're going to reverse them from {0,0:255,255} to {0,255:255,0} thus:
There it is, a basic straight line inversion curve for Adobe Lightroom. I actually do something a bit different, changing the black point instead, thus:ToneCurve = {
0,
255,
255,
0,
},
I could also change the white point by setting the first pair to 0,250.ToneCurve = {
0,
255,
250,
0,
},
I'm going to come on to a fancier use of this in another post.
Lightroom tips: an introduction
Now that I've been using Adobe Lightroom for a while, I realised that there were quite a few things that I've needed to work out how to do. Apart from learning the new tools and what all the buttons do, there are a few features that seem to be either missing or undocumented.
I come at most software from the angle of asking myself "How do I do...?" and then trying to find out how to do it. I tend not to learn all the features and then work out how to put them into practice.
From this standpoint, I thought it would be useful to others to put together some posts with tips on things I've worked out how to do. These are often questions asked out in web-land without satisfactory answers. Certainly the things I'm going to write about I've not been able to find documented anywhere, including in books.
Each of the posts will start with the basic "how to" question I was asking myself and maybe reveal a few other aspects along the way. Each post will also refer to the Lightroom version and operating system platform. The latter is really related to file locations etc. If you read the posts and know the specifics for other OS, drop a comment which will make the posts more complete.
Posted by
doonster
at
07:07
0
comments
Monday, 10 November 2008
Black and white shootout: Lightroom and Lightzone
As I mentioned at the end of this post, I've been using Lightzone as my main black and white conversion software for sometime. It produces really pleasing results with lots of control and minimum effort. This is where the underlying linear colourspace and the ease of the Zonemapper come into their own.
With the funky new tools, I thought I'd take a crack at using Lightroom in a sort of shoot-off. This won't be a long post because, quite frankly, there was no contest. Lightroom is very clunky and fiddly to use in comparison. Sure, it's got all the fine tuning possibilities in every part of the spectrum and masking etc. But with Lightzone I get that same power, with far fewer clicks. Plus I can stack tonal adjustment layers in Lightzone, which isn't possible in Lightroom (limited to a single curve tool).
Even for tweaking monochrome scans, I find Lightzone better, largely because I'm so tuned into the Zonemapper, but in these cases it's a closer call. I'm using Photoshop for scans mostly, anyway.
So for black and white, Lightzone wields the single stone that slays the Lightroom Goliath
Friday, 7 November 2008
Lightroom for book mock-up
I've been using Lightroom a lot since I first installed it a few weeks ago. I'm finding it great for bulk file handling around my various workflows. This week I started the process of producing a second edition of my Kristiansund book that I put together for SoFoBoMo. Originally I had very few shots from which to choose and pretty much all the decent ones ended up in the book. A pretty good effort for a few hours works and relatively easy to do by hand.
Well now I've got a summer's worth of picturing and a whole lot more shots to choose from. My first rough-cut got me down to 120 plus covers and I'm aiming for 50-60. Enter Lightroom and some nice features.
Here's what I've been doing:
Key to this process has been the use of a Collection. The original files are stored in a varity of locations on my system. The Collection enables me to gather them all in one place without moving or copying the originals.
Once I created the collection, I ran a print of contact sheets to plain paper to eliminate the obvious edits - all those that are not up to the job, duplicates, subjects that don't fit etc.
Next, back to Lightroom to remove those and start ordering the rest. I can easily click & drag the images in the Collection organiser to sort into the chapters and start the basic sequencing. This helps me identify further shots that don't fit, understand the overall story I want to tell and hone in on the best.
I'm not yet done with this process but was able to get from 120 down to around 90 in under an hour, together with having all of the images grouped by chapter. Now it is a question of balancing the chapters & getting to the images that tell the story succinctly.
Using Lightroom in this way is really speeding up the whole process of mocking up the book, especially the difficult task of trimming the selection down to a manageable number of images. I can see this leading to me putting together more books in the future.
Posted by
doonster
at
00:15
0
comments
Labels: Lightroom, Photobooks, Workflow





