If I recall something I read recently, doesn't PEF make use of a different profile by default than DNG? One may look better than another, especially in ACR where the K5 is now explicitly supported.

Dunno.. I dropped mine from over meter several years ago. Not a problem for the tank that is the DA*50-135. Although it accidentally fell out of the camera bag recently and an internal element popped loose.

You'd think they could make the thing sustain a few little bumps for crying out loud.

Honestly, quite a nice lens. More sturdy than I would have expected as well.

Using a wired remote does not turn of SR.
Using Mirror lockup, 2 second timer and using the IR remote will all turn off SR be default.

For 2 second timer and Mirror lockup, there should be no need for SR ( unless you're doing something wrong). The whole point is that your tripod is more stable than the camera parts that these settings are trying to compensate for.
Although it might be nice if IR remote allowed SR to be enabled.

Probably of people making a mess of our house, something like this.

Most likely you had inserted a SD card with existing images on it. The camera will pick up with the highest number found.

Is this new behavior? I do not recall that happening and lots of people seem to be asking now.
Maybe just a lot of users upgrading by now??

OMG that has to be the saddest thing I've seen in a long time.
Time to head for that mead, or after that, perhaps the bottle of developer...

I got; an Xmas tie, PJs, and deodorant. (not really sure what thats trying to say)...

But I also got a big bonus at work, so I went and picked up a 27" iMac quad core i7 with 16GB memory.

Beyond the nice speed increase, the monitor can actually dim down to be profiled at 6500K. The colorimiter always registered my old LCD monitors wayyy too high and I had to manually adjust brightness of each photo before each printing to compensate. Color tracking seems to be much better than the older iMacs from two years ago as well.

Also, bottled my Christmas Black Cherry mead on Christmas Day.

So it was a good day.

LR3 is so much faster than LR3 as far as catalog handling. I had posted a chart some time ago with startup times. For 50,000 photos I could view the top level for All Photos, LR2 was something like 30 seconds, LR3 was 12 (cannot remember the exact values, but it was somewhere in that range).

Full sized previews has slowed a little bit, probably due to more and more accurate processing?? but everything else seems faster.

Whether you'll notice a problem with 2GB of memory probably depends on how many images you have in any given collection or catalog. It will also be affected by the number of images that might have several adjustments made (brush, noise reduction, etc..)


It is a memory hog (for good reason). With 6GB of memory, it often goes right to taking 2GB right off the bat. With 4GB of memory it is more conservative (just moved from a 6GB machine to a 4GB machine -- waiting on the 16GB in the mail). I suspect with 2GB it will still be smart and not use more than it absolutely needs to use but you probably won't want to run other applications.
I also suspect when I get 16GB in there that LR3 will grab closer to 4GB right away.

Memory is relatively "cheap". From OtherWorldComputing, I just got 16GB for $240 for my iMac!!
If you can in any way afford the memory and your motherboard handles it, I would go for 4GB. (I think all quadcores should handle 16GB, so I would suggest 16GB as the price difference from 4 to 16 is just not that great!)

An easier solution is to simply take photos of scenes with lots of detail and color contrast.
Stay away from clear skies and plain backgrounds. Problem solved... for free.

Just be careful with the above tips if you're not familiar with how they work...
You'll soon find these tools do not work well on *all* photos.
i.e. automatically spot healing someone's face can make for an interesting result.

Not sure how I missed your point. You seemed to confirm my questions and statements.
- If you have Win7 working, why run it under XP, especially under a VM?
- VMs can have issues with USB devices. We run into such issues on a regular basis with the software we write and have to periodically verify against actual hardware.

Are you saying since you added VirtualPC and XP mode that it no longer runs natively under Win7?
That sounds problematic, but some reason I'm not surprised. Win7x64 has lots of issues with devices (not Win7 or Microsoft's fault - as easy as it would be to blame them - but x64 has some strict requirements for drivers that just might not be completely supported. Still, if it was working on Win7x64 to begin with, not sure why it would have stopped.