Shared Links

Flickr Photos

  • Latest Photos
    www.flickr.com
    chuqui's photos More of chuqui's photos
  • Random Photos
    www.flickr.com
    chuqui's photos More of chuqui's photos

Badges

  • View Chuq Von Rospach's profile on LinkedIn

Powered by FeedBurner

Blog powered by TypePad

Google Analytics


« August 2007 | Main | October 2007 »

56 posts from September 2007

September 30, 2007

speaking of photo-realism...


Working on the photos from the Oregon trip, and ran into a classic example of the power (and potential abuse) of the digital darkroom.

Behold, the Columbia River Gorge:

Columbia River Gorge, Oregon

The first day up in Portland, fall arrived as we did, leaving it rather grey and drippy. To me, that's a perfect time to go do photography in the gorge, because there are some gorgeous photos to be made, better, I think, than sunny days. Now, if it's really wet and nasty, no. But the gorge gets very moody and can look very much like a pastel or a water color painting, just standing there. This was taken from the Portland's Women's Forum Scenic View (aka Chanticleer Point).

The above photo was very close to how it looked in person. But as I was working on the photo, I made some changes that brought the clouds out and really changed the tone and impact of the photo:

Columbia River Gorge, Oregon

I frankly like that one better -- but I like both. Is one "right" or "wrong"? This is the "manipulation" debate in a microcosm, whether that debate is about cropping or HDR or whatever. In this case, the differences are primarily managing exposure and contrast, really minor things that are pecfectly do-able in a wet darkroom -- except that film is much less likely to have as much information on it to make adjustments with...

Have a preference for one or the other, or some other comment? Feel free...

Oh, if this photo looks vaguely familiar, it's a re-imaging of one of my favorites from way back:

Sun, Nov 11, 2001 10/41/54 AM.jpg

That photo is actually a photo-CD scan of an older shot, probably with Velvia. It's nice to be able to re-do it in digital for future use and personal amusement...

September 29, 2007

Lincoln's Sparrow


Lincoln's Sparrow
Originally uploaded by chuqui.

Golden-crowned Sparrow, Palo Alto Baylands, CA


Common Yellowthroat, Palo Alto Baylands, Ca


Digital manipulation of photos....

Remarkable - O'Reilly Digital Media Blog (by Harold Davis):

These file versions go a long way to confirm my contention that digital photography is an entirely new medium, one part photography and one part digital manipulation. Photographers who ignore the “digital painting” aspect of this new medium do so at their own peril, as do digital technicians who ignore the need to take great photos in the first place. Those who critique the new medium based on the aesthetic of the inviolate unmanipulated negative are truly lost in this brave new world.

All I can say is -- Amen.

Back when I was shooting film, in the days B.D. (before digital), one of the arguments going on among nature photographers was "real" wildlife photography versus shots taken under controlled circumstances (i.e. in zoos or preserves).

I think the argument (which, now that I think about it, is still going on today in some places) has relevance here, because it shows up part of the conflict that can happen between what's important to the photographer (vision, intent, technique) and what's important to the viewer of the photo. If you're Art Wolfe and you spend a week tracking a pack of wolves to get a shot, only to lose a cover sale to someone who flew to Washington and hired a wolf for an afternoon at a reserve to snarl on command -- I can understand being a bit miffed. But if you're the person buying the photo, does it really matter? (answer; maybe - the answer is very different if the publication is National Geographic, Discover or Time because of the assumptions -- or lack of them -- the readers bring to viewing the photo).

Now, we're moving that same philosophical argument over to the digital space. I was a bit surprised to see there are people on flickr talking about cropping -- and flagging their photos as cropped or not cropped. I mean, seriously, I crop pretty much everything, and I did back in high school when I was developing Tri-X and printing it out, and I always will. Cropping is a basic tool for helping to improve a photo and help a viewer see your intent and vision. Which version of this photo is better?

Lincoln's Sparrow

or this?

Lincoln's Sparrow (uncropped)

to me, it's a no-brainer.

But this is all a slippery slope. Where do you draw the lines? What's acceptable and what's not?

Personally, I look to the history of art and painting here. Think about it -- Renoir, Dali, Miro, Picasso. Every time a movement breaks ground, people who like the old ways, or who's career is based on it, is going ot hate the new stuff. Some movements succeed, some fade and don't survive the test of time. Those in the moment generally argue about it but don't know which side will win (many times, both do...)

What's acceptable? Brightness? contrast? cropping? sharpening? Dodging and burning or using masks? color correction? color replacement? All of these are standard techniques of a "classic" or "wet" darkroom. I mean, seriously, in my senior portrait for high school, I was wearing chromed frames and the photographer thought gold would be warmer and look better (he was right) -- so he fixed it. That was 30+ years ago. Nothing new under the sun, kids.

What about HDR? Isn't that really just an automated form of some of those techniques above? Is it okay to do HDR if you do it manually, but not if you tweak buttons? And if so, why don't we hold the same standard to sharpening?

Think back to that list of artists: Renoir, Dali, Miro, Picasso. It holds the answer here: an artist (and digital photographers are artists, as were film photographers; tools and techniques vary, but the intent is the same: to generate a response in the viewer and to properly display the vision of the artist). NONE of these techniques are invalid, they are, effectively, all different schools within the discipline, and different ways for artists to create the vision and statement they're trying to make. If they connect with their viewers, that artist and their school succeeds, no matter what the other schools of thought think.

Personally, I try to stay in the "my digital photos are still photos" school. Make them the best photo they can be, but they need to be photorealistic representation of what the photographer saw that transmits the vision and emotion the photographer is sharing.

This is a problem I have with a lot of HDR photos today -- well, I have two problems. First problem is that people are running around flagging things as HDR, in a "see what I can do?" way. Like cropping, I don't think it should matter, these are geeks speaking to geeks, not to their viewers. As a viewer, I don't care HOW the photo was processed, I care whether or not it's a good photo (as a geek, if as a viewer I am curious about the technique or location, I'll ask!) -- people are still lost in the technique, not in the result.

The other, more major one, is a problem we all suffer with new techniques or as new accolytes: the belief that if some use of something is good, more of it is better. Photos aren't being done to make them great photos, but to show off HDR, and here's a lot of "see how this looks when I turn the knob to 11!" going on. It's natural, its inevitable, but it makes for photos that look to me more like shots of mars than of landscapes from this reality, and I don't for a minute believe it looks like what the photographer really saw, it's almost a parody of what they see because everything is kicked up to extremes.

Don't take that to mean that I think HDR is an appropriate or useful technique; I don't currently use it, but I expect that to change at some point. But it's being used too often ("we can, so we will"), and to extreme (process for kowabunga, not quality). A lot of that is simply people figuring out how to use the tools well; it hearkens back to the early days of desktop publishing, and the "my god, I own 50 fonts and I'm going to use them all" enthusiasm -- it generated an amazing amount of crap, but it taught us how to use the technologies and adapt traditional typography for the digital age...

And I'm not immune from the "kowabunga" factor, either. Take, for example, this shot:

IMG_2167.jpg

which at one point was something I thought was one of my best. I now look at it, and see an over-saturated mess ("the sky must be BLUER! The forest must be REALLY GREEN!"), where I simply kept turning the knobs not to maximize quality, but to maximize the saturation. I really need to create a new edition of that photo, it's core is solid, but the details aren't...

compare that to this, same location, same time. the colors are much more natural, but it still has challenges and deserves a re-edit, too, but -- it's a much better shot because I didn't try to hit people over the head with the saturation slider...

IMG_2177.jpg

and compare both of those to this:

Yosemite Valley from Tunnel View

same location, a year later, and actually fairly similar weather conditions, but a year's practice at shooting better (and more patiently), and a year's improvement in post-processing practice.

For me, it's not about the technique, but the final result; hence, you don't see me talking about crops or HDR, since I think those things that really aren't important, except to the photographer and a few fellow geeks. If you think about it, my mom doesn't care if a program is written in C or Java or Perl; she cares that she can read her email easily and balance her checkbook. I don't mind telling people what I did if they care, but the process is not the reason for the photo; the photo is the reason for the photo.

So you won't see those kind of disclosures on my work. The one main exception -- since I do a lot of wildlife (or more correctly, semi-wildlife, since I'm not spending weeks out in the wild doing this *grin*) photography, and I also love shooting at zoos and wildlife facilities, I try to be careful to document my "captive" photos from my "natural" ones, because in some situations, that is significant to people. But beyond that, to me it's whether or not it's a good photo, and whether or not it's an honest representation of what I saw that matters.

And no, I don't think everyone needs to -- or should -- sign up to do things the way I am doing them. Everyone needs to find their own style and voice. In fact, I've become a huge fan of Davis's low light (or in many cases, "no light") photography and the results he gets; they in no way represent a scene as he saw it, and they are not scenes as they'd be seen on a film camera (it's really a new way to use digital to envision the un-seeable). they are, however, many times stunning photos with strong emotional impact that tell a powerful story about the scene, even if it's not a scene you'd see with your own eyes.

For instance, this shot. Or this one. Wow.

There are, ultimately, many ways to skin cats. The end result is what matters, not how you skin it, right?

September 28, 2007

Is the Apple TV officially a flop?

Is the Apple TV officially a flop? (Or: How to fix Apple TV) | Crave : The gadget blog:

Author Scott Woolley calls the Apple TV "a flat-out" failure, claiming that it's sold less than 250,000 units in six months. Among the supposed sins of the product: the lack of a built-in DVR and a "parochial and proprietary approach" to online video content. He also highlights a variety of on-demand video competitors, including Vudu, TiVo (via Amazon Unbox), and Xbox 360 (which offers rentals and sales of TV shows via the Xbox Live Marketplace)--while glossing over many of their shortcomings. Still, is he right? Is the Apple TV dead in the water?

Hmm. Apple has sold ONLY 250,000? And it failed?

But -- if you look at the first six months of Slingbox or Tivo from earlier this year, what volume do we have? Oh, about 35,000 units.

Yet slingbox is the darling of many of the geeks, so it's great, right?

Burningbird » Coreless

Burningbird » Coreless:

My iPod's battery is dying, and it irks me that the only way I can replace the battery is getting out my old soldering iron, or sending it in to Apple and paying $65.00 dollars and getting a re-furbished replacement back. This isn't what I expect when I spend that kind of money, especially when other MP3 players are a fifth the price.

This is a time when I like iResq. They'll turn around a battery replacement in 24 hours using overnight express each way for $54. Or if you feel like doing it yourself, they'll send you a replacement battery for $25. I've used them both ways over time, plus their laptop service, and been happy with it every time.

Halo 3 breaks records, $170 million in 24hrs - Xbox 360 Fanboy

Halo 3 breaks records, $170 million in 24hrs - Xbox 360 Fanboy:

Exciting news fanboys, Halo 3 has officially become the highest grossing entertainment launch in history pulling in a whopping $170 million in its 24 hour launch window.

Think about that number for a second, and compare it to the money movies are bringing in these days (resident evil: extinction topped the list last week @ $24mm).

If you haven't noticed before now, video games are now a huge part of the entertainment landscape -- budgets and revenues rivaling Hollywood.

Wow.

(I get my copy today. if the blog goes dark, I'll be back. or dead...)

The iPhone: Irreparable damage... to software?

Technovia: Irreparable damage... to software?:

No, wait, it's software. It's code. By definition, "damage" to software can be undone, which is why it's "soft" rather than "hard". You might end up with it having to be restored to its factory state, but that's not "irreparable", is it? And yes, even if it's "firmware" it's re-flashable. That's why it's "firm" - it's held in hardware, but can be re-flashed.

Either Apple doesn't know the difference between software and hardware, or its definition of "irreparable" simply means "we're not going to do it for you, buster", which isn't exactly the dictionary definition. I can't fix a broken window, but that doesn't mean it's "irreparable" and I should just sit here with a draft blowing through the house for the rest of time.

In fact, of course, Apple is just lying. It's not irreparable. It voids your warranty, it makes you ineligible for any help from Apple, but it's not irreparable. Apple is simply pointing out that you have been a bad person, and it will try and punish you for disobeying His Steveness.

Do you want to do business with a company which treats its customers like that?

[....]

It's strange that Apple thinks that it's right that people want to own their music, but wrong that people want to own a device which they've paid $399 for.

[....]

To make matters worse, Apple seems to be bricking phones with this update which have had no hacks applied to them at all. So the ones who seem to be causing "irreparable" damage aren't the hackers, but Apple. Maybe Apple should hire some of the hackers. After all, they seem to know more about its software and hardware than it does.

I mostly agree with Ian, but...

Remember that some of the early unlock hacks did involve whacking hardware. And even though it's software, if someone borks that firmware in a way that borks the ability to download and update the firmware -- which is very possible -- Idon't blame Apple for washing their hands there.

What Ian's missing is that what Apple says and does here are different things. I don't blame them for taking a hard line here. Sort of like an auto maker doing a "if you reprogram your car's computer for better gas mileage and it blows a piston, don't expect the warranty to save you" -- it's a hard sell on "don't do that!" But the reality seems to be that bricked iPhones are being reset or replaced -- Scoble's mentioned that already.

So Apple seems to be taking a hard line in their statements (good to discourage folks from doing this, good from drawing a line in the sand legally over warranty liabilities, making the lawyers happier) -- but they're taking a more case-by-case look at it down in the trenches.

Which is good, and how it ought to be. It doesn't hurt (ahem) that this update is causing bricks that weren't unlocked, because it means there's more ambiguity over the bricking problem, but the reality is, the support guys (Wizards, etc) are going to take a softer line than the PR side here. It's all part of the game (and Ian's been around long enough to know about this dance....)

And this update bricking things? One of the reasons I've said all along that I was waiting to buy an iPhone. My view of it from the outside? Completely new technology, coming out at the worst possible price/performance for early adopters, and it was clear that Apple was struggling to get it out the door -- to the point they delayed Leopard and put more people on finishing up the iPhone. That indicated to me there was likely going to be a bit of a shake-out period, probably moreso than usual for something this new/different/revolutionary. To be honest? the iPhone's been better, and more stable, sooner than I expected -- so give Apple (and Steve and the geeks who did it) credit for not not shipping it too early just to get the revenue stream rolling.

At the same time, though, this seems to be one of those speedbumps that I figured might show up in the product early on, and while parts of me ARE in fact lusting for an iPhone, the rest of me is happy someone else is paying the product premium to shake those bugs out. When I get around to buying one, it'll be a much better product for it for me...

September 26, 2007

Facebook's free lunch is over... Now the fun begins.

Web Community Forum » Blog Archive » Facebook Falls Prey to MySpace’s Sex Offender Problem:

I remember when Facebook was considered a safe environment for students to share personal information. But now the same problems that have plagued MySpace are cropping up on Facebook. The New York Times reports that New York Attorney General Andrew Cuomo’s office is investigating sexual predators on Facebook:

But about a week after an investigator from Mr. Cuomo’s office set up a profile for a fictitious 14-year-old girl on Aug. 30, a 24-year-old man sent a message through Facebook asking her for “nude pics,” Mr. Cuomo said.

The investigator, also posing as the fictitious girl’s mother, sent an e-mail message to Facebook complaining about the man’s request. Facebook responded that it would review the message and remove any posts that violated its rules. But in his letter, Mr. Cuomo said that Facebook had taken no action as of yesterday, and that the 24-year-old man’s profile was still on the site.

And while this is still a rumor (as far as I know), if there's any truth to it, there's the potential for all sort of hell for Facebook:

Rumor: Facebook Security Breach Results in Lawsuit - The Unofficial Facebook Blog:

I have been tipped off that there will be a major lawsuit announced in the coming days regarding security at Facebook. Much of this revolves around Facebook’s lack of privacy controls within their company and that significant data has been leaked. As published on the Jobmatchbox blog, according to a Facebook insider, “privacy controls at Facebook are non-existant.” Any employee within the company has full access to your messages and account information. Technically, they can even login as you and impersonate you. This is not going to bode well for Facebook.

Bottom line: when you're too small to worry about, you can get away with a lot of stuff -- and if you don't realize that the "grace period" will end at some point, you don't put the controls and systems in place to protect yourself -- and then when people start calling you on it, how do you respond?

The predator problem, to me, is more publicity than problem (and frankly, where Cuomo is concerned, that seems to happen a lot -- he doesn't seem to be as interested in solving serious problems as sending press releases about problems that generate lots of publicity...), but if the lack of data access is remotely correct, Facebook has a massive privacy problem -- and trust me, if it's remotely correct, I'll be cancelling my Facebook account until I know they have it solved (and maybe beyond).

And if they didn't design access controls into their system and database (where is their security team? their privacy officer? their support team? their freaking DBA's? the LAWYERS? All sorts of people should have been yelling about this problem...), it's not going to be an easy fix -- and they won't have much time to deal with it.

It's an easy thing to think you can implement later, but later never seems to come, at least until the lawyers start scheduling meetings and bringing out the bullwhips. And then, it's too late. For teh Really Big System I built for that Company I Used To Work for, these kind of data access issues were designed into release 1.0, and there was only one person with access to "everything", and that was the god-DBA, aka, well, me. And I actually signed special, "beyond the standard employment NDA" that promised that if I did something wrong, Steve would own parts of me I happen to be rather fond of...

If Facebook didn't get their internal privacy set up before now -- that's not just bad, that's potentially fatal.

But as I noted, still a rumor. Hopefully a wrong one. But something in my gut tells me that there's something inside the smoke here... If you don't have people involved who are sensitive to privacy issues, it's really easy to ignore them until the crisis hits...