Re: Panned Weekend Gaming

Chris Whitworth wrote:
On 2008-02-29, DBSnappa <davidjboughton@xxxxxxxxxxxxxxxxxxx> wrote:
Chris Whitworth wrote:
On 2008-02-29, Chris Whitworth <usenet.chris@xxxxxxxx> wrote:
On 2008-02-29, deKay <andyk@xxxxxxxxxxxxxxxxxx> wrote:
My 360 is dead, so I do mean Panned.

I'll be playing:
Lost Odyssey (X360) - "Open with high tempo, fight with speedy! High tension
of fight that combined with aiming system - composed item activate by using
Trigger button. And GC system - guard members who stand back in formation!"

Professor Layton and the Curious Village (DS) - My solved puzzles count stands
at around 70 so I figure I must be over halfway by now. Hopefully I can finish
this off this weekend.

That'll probably be it. I've got guests on Saturday and I'm busy ALL DAY on
sunday. Mental note: Buy DI box...
Oh, and the arrival of a 500GB Western Digital MyBook and Adobe Lightroom means I'll be spending a lot of time archiving and indexing my photos.

Let me know how you get on with it.

I've been playing with the trial for a few days, and since my wife is a teacher
she can get the full thing for 80quid. So far I'm liking it as a better option
than full-blown Photoshop for RAW processing, and it's far better than Canon
Digital Photo Professional at organising and tagging and stuff (which is what
I'd been using for RAW processing before). Lightroom's RAW processing uses
Adobe Camera RAW, which is considerably more flexible than Canon's effort,
although the built-in sharpening is a bit weird and tends to give a sort of
posterised effect in detailed areas.

Is that at 1:1 or just preview size. I find it can do weird stuff with how images appear on screen regardless of how accurate you think your set up is, so it's always worth zooming in or outputting samples to a printer just to check you haven't completely broken the contrast or saturation for instance. Also, I think things like sharpening are handled better if done very incrementally in several passes, a little like how I do interpolation to increase an image's size. If you do multiple increases of small amounts rather than one big hit, it tends to be less noticeable.

Fundamentally, apart from a fairly substantial amount of crossover to the point that having all of them isn't necessary I really like the Photoshop/Bridge/RAW/Lightroom integration.

The plan is that I move my "active" photo collection onto the external drive
which will mostly live on the desktop next to my desktop box, but can also
be plugged into the laptop for when I'm on holiday or visiting family or
something; Lightroom appears to manage collections fairly sensibly and it
looks like you can have multiple collections and merge/split them and all that
sort of thing.

A lot of what I do I don't usually need to keep, because of the repetitive nature of the pictures and the volume of shots as well means that I would need several terabytes of storage if I wanted to keep everything. Also, a lot of stuff has close to no resale value, so I've got into the habit of binning quite ruthlessly any excess, particularly from big shoots where it's quite feasible to shoot 6-700 20Mb raw files.

What I'd really like for it to do is to figure out which .JPGs are associated
with which .CR2s and automatically collapse them into stacks for me - I
assume Lightroom can do this, but I've not investigated fully yet.

I am a self confessed lazy *** when it comes to fully exploring the capabilities of any piece of software unless I really have to, so the plethora of clever archiving features that Lightroom use have barely been looked at by me. The processor functions I know back to front though ;) One thing I would like is the ability to set up multiple export processes in one box rather than having to set them up individually - not a biggie as Lightroom seems to be very happy running concurrent processes without freaking out. I think the most I've had is five sets of Tiffs and lo-res jpgs running out at the same time.
.

Quantcast