2010-01-16 Melanie’s Bday

From a previous article, I finally found a way to work in Aperture again. But since I’m also trying to pick up photography again, I thought it’d be fun to write a little bit showing a few experimental images taken from that day.

This will be a way to test out a new WordPress plugin I just wrote to do mouseovers. As long as you’re on this blog article, you can run your mouse over the image to see the pre-processed original image.

The specials are…
Mission Beach Cafe, The Mission, San Francisco, California

Olympus E-P2, M. Zuiko Digital ED 14-42mm 1:3.5-5.6
1/5sec @ ƒ3.9, iso 1600, 17mm (35mm)

I arrived a little late as usual, but just in time to order dinner with everyone else.

This was actually the first image I used to test out whether the workflow works. Because of that, the DNG output was 8-bit, not 16-bit. That may have accounted for the overaggressive smoothing, or it could be the lack of dynamic range in an ISO 1600 µ4:3 CMOS sensor (roughly 1/4 the size of a 35mm frame). Then again, maybe it’s the setting on Topaz Adjust plugin. In any case, it does have the painterly look that you get when you start remapping dynamic range of an image. Not too sure if I can still call this a photograph.

If you mouseover the image, you may be wondering how I pulled color from the black-and-white original. The original is the JPEG, but the image was generated from the RAW. For documentary photography, on cameras which resemble rangefinders like the Leica M8 and the Olympus E-P2, I prefer black-and-whites previews, which force me to concentrate on tone and not color—but it’s always nice to be able to grab the color channels from the RAW if I change my mind.

This exposure tests the outer-limits of the kit lens: 1/5 of a second at a borderline too-high-for-this-camera ISO at the largest aperture for this 35mm EFL. Had I my old 17mm pancake, I’d have gotten a full stop faster. Still, it got focus-lock and the in-body image stabilization allowed me to shoot handheld braced against elbows on the table. Yeah!

More photos in later pages…

Pages: 1 2 3 4 5

Posted on February 9, 2010 by tychay 4

Unsupported RAW workflow in Apple Aperture

One of the most annoying aspects of Apple Aperture is that there is no API for RAW plugins. This means that you’re stuck with Aperture’s RAW rendering—and Apple has been slow to update support for the latest cameras. For instance, the Olympus E-P1/E-P2/E-PL1 series has been out since August, selling like hotcakes, but there is still no RAW support for these models, even though the E-30, which is supported, uses the same basic RAW file format.

Well finally my workaround seems to work for my satisfaction. Whee!

Morgan
Martuni’s, The Mission, San Francisco, California

Olympus E-P2, M.ZUIKO Digital ED 14-42mm 1:3.5-5.6
1/3sec, iso 160, 14mm (28mm)

For those too lazy to read forward here is the step-by-step:

Select images in Aperture and choose “Edit with…” Catapult.
Read and save images in your favorite converter (for me and the E-P1 it is Adobe Camera RAW).
Reimport images within Catapult and close the box.

Continue reading about How to convert after the jump.

Pages: 1 2

Posted on February 8, 2010 by tychay 11

LH-3 Lens hood for the 35mm F1.2 NOKTON

Someone on a forum asked what the LH-3 lens hood accessory looks like on the 35mm NOKTON.

Hooded Nokton
San Francisco, California

Nikon D3, Nikkor 85mm f/1.4D, Canon 500D diopter
1/60sec @ ƒ4, ISO560, 85mm

Continue reading about short description after the jump

Posted on February 4, 2010 by tychay 2

Faster PHP fo shizzle—HipHop for PHP

[This post is in progress. There may be a number of errors. Please comment below with corrections and I’ll update this article.]

Facebook announced the release of HipHop for PHP today.

Haiping Zhao
Facebook, Palo Alto, California

Sony DSC-WX1
1/80sec @ ƒ2.4, ISO400, 4.2mm (24mm)

When I left Plaxo, Haiping was the server architect there. Today, he works at Facebook and announced HipHop for PHP. It’s nice to see the world recognizing his talents.

Since apparently, I was the first person to ever publicly spill the beans on HipHop, I need to do penance by clarifying what HipHop is and what it means for PHP.

For those of you who don’t have time to read the rest, here is what HipHop for PHP is:

HipHop is a PHP-to-C++ cross-compiler. What this means is it takes PHP code and translates it into C++ code for further compiling. It is not another language. It is not a just-in-time compiler (JIT).
HipHop will be open-sourced by Facebook under the same licensing as the respective PHP codebase it sets to mirror. Facebook hopes that the community will improve HipHop and add extensions to HipHop that mirror PHP functionality. Also, it hopes that future PHP core development will code features that would be more amenable to optimizations that HipHop does.
HipHop was the current survivor of a number of projects over the years at Facebook to improve the performance of the site. Facebook, as the second largest trafficked website in the world, is built mostly on PHP. HipHop is currently running side-by-side next to many LAMP PHP servers at Facebook and they are claiming an average of 2x increase in performance on those machines.
HipHop accomplishes this by surveying the entire codebase of your PHP-based application with a parser and then building out a C++ project based on it. The C++ project then compiles and runs as its own web server. Because of this, Apache and the PHP Zend engine are completely bypassed.
In order for this to work, some features of the PHP language are no longer supported. Also, C-specific PHP extensions will need to be translated to HipHop C++ extensions in order for them to run.
The benefit in speed is mostly due HipHop’s static analyzer which parses your PHP code looking for ways to optimize dynamic parts into static maps. Because of this, your performance gain may vary — more structured code is rewarded with larger performance boosts.

What HipHop means

If you use some open-source PHP applications on your hosted website, the answer is nothing. You don’t have the ability to compile HipHop, you don’t have access to server restricted ports, etc.

If you are developing a PHP application that currently can be run on two servers or less (or virtual servers in the cloud) the answer is nothing. You don’t have the scale for this to be worth your time.

If you do not have a separate development and deployment environment, don’t have a developer who knows C/C++, or use any PHP libraries where the source is not available (thankfully the encoded scripting market is small to non-existent in the PHP world), then the answer is nothing. You don’t have the development model that can support HipHop. Also note, HipHop has bugs, and—given the state of APC development as a model—will never have true compatibility with PHP. You’ll need some resources to either recode around those bugs or fix HipHop.

If you are a developer of an open-source PHP application, then the answer is not much. Most PHP applications will be deployed in a shared-hosted environment. They won’t be using HipHop.

If you are a shared hosting company, the answer is not much. This is because the HipHop parser needs access to all the PHP in an application in order for it to create a working project. The exception is if you provide software as a service that you maintain (say a static build of WordPress, or a custom site tool written in PHP). You can have HipHop optimize this and get the performance increase.

If PHP is not the operational bottleneck of your web application (your app spends a lot of time waiting on the database, disk, a 3rd party Web API call, etc.), the answer is not yet. At this time, there’s no point in getting a performance gain in PHP. If you don’t know what I’m talking about, your bottleneck is the database. 😉

If you have an application already scaled across many machines, a significant number of them running PHP in processor-intensive tasks, have separate development/deployment, have your entire PHP source code, have modest C/C++ resources, then the answer is possibly. It wouldn’t hurt for a developer there to try a hand at cross-compiling the PHP into HipHop and seeing if it runs. An operational deployment will return about 50% of those machines to a pool for other uses or future growth—or, put differently HipHop will basically double that processing on the same hardware/power.

If you make a turnkey application based on PHP, the answer is somewhat. These are rare, but now you can shrink-wrap PHP into a binary. This isn’t the intended use of HipHop, so some development might have to be done to get this fully supported. Also this is a true binary, not an op-code compile—it cannot run across platforms.

If you are developing a PHP framework, the answer is some. If your framework can compile and run successfully in HipHop, then it should be a good selling point to enterprises in case their application becomes bottlenecked on performance.

If you have highly-cohesive parts of your architecture that fall into above requirements and those parts are weakly-coupled (via API?) to the rest of the system, then the answer is a lot. Those parts can probably benefit from HipHop, and it should be relatively easy to try it.

If you are making a decision on which web language to build your site in, the answer is a heck of a lot. Arguing against PHP for performance reasons no longer holds water. PHP under HipHop will probably now out-benchmark Perl, Python, Ruby and possibly even Java and C#. In practice, you can get the advantages of having a scripting language without operational costs. Moreover, because the target is C++ which is more easy to integrate as a library, if you have a multi-language support, you can now provide C++, Python, and other languages with access to components that have before only been written in PHP (without resorting to a web API).

If you are making an argument to recode your entire site from PHP to some other language, the answer is you just lost that argument. (I never bought the argument of recoding an entire site from another language to PHP.)

There are language features, for better or for worse, that PHP must support and HipHop must not. Because of it’s unique approach to compiling, HipHop will never replace the Zend Engine. Because it doesn’t supersede PHP user-space syntax, HipHop does not and will never change PHP development (much).

HipHop is a showcase. With it the PHP world can point to Facebook as being the busiest site built in a scripting language in the world.

Continue reading about A deeper explanation of HipHop after the jump

Pages: 1 2 3 4 5 6 7 8

Posted on February 2, 2010 by tychay 61

Counting lenses

Phil Greenspun asks us to guess how many Canon EOS lenses have been made.

I guess…

Continue reading about My guess after the jump

Posted on February 2, 2010 by tychay 2

The Olympus E-Pnext

Olympus launched a teaser site for the next E-Pnext:

When I first saw this yesterday, it said “You can’t hide creativity…” and it’s since been changed to the unimanginative, “YOUR next camera is coming soon…”

For reference, I decided to see if I could glean it for MY last camera which came last month… the E-P2

MY last camera came last month…
San Francisco, California

Nikon D3, Nikkor Nikkor 85mm f/1.4D
1/5sec @ ƒ4, ISO200, 85mm

I didn’t have a 17mm pancake like in the picture and my “man-hands” are blocking some of the details, but the E-P2 extends out to my palm, while the photo shows the next one extending out to the woman’s knuckles. The length of my hand should be about right so it’s at most about an inch smaller and just as tall.

Continue reading about Guesses about the next Pen from Olympus after the jump

Posted on February 1, 2010 by tychay 2

What (entry) dSLR (to buy)? [The entry kit dSLR Part 4]

(Article continued from part 3)

Unlike in the article four years ago, I’ll be covering specific models. I’ll cover them in the reverse order to my original article, because I felt I gave the less popular brands a short shrift last time.

Pentax

The Pentax K-x ($550 from Adorama, B&H, Amazon)

The Pentax K-x is available in 100 color combinations in Japan.

Four years ago, I stated that Pentax makes shooter-centric cameras at a great value. In fact, I mentioned that Pentax was the first entry in this dSLR price category, and this was in line with Pentax’s history: to bring those people on a budget a quality camera.

Continue reading about Pentax, Sony and Olympus entry dSLRs after the jump

Posted on February 1, 2010 by tychay 13

Minimal wallet

Since everyone is on a minimalism kick recently, I decided that my Costanza wallet had to go:

Hlaska Nominal Merge Wallet
San Francisco, California

Nikon D3, Nikkor 50mm f/1.4G and Nikkor 85mm f/1.4D, Canon 500D
8 exposures, 1/60sec @ ƒ5, ISO200, 50mm and 85mm

This was taken inside a light tent with my SB-800 flash pointed backwards and an LED light array underneath. No real setup, just some overzealous light bouncing around.

When we were in their flagship store on the Filmore, I had flackette pick out my wallet. When I got home I realized she picked out the same one that I bookmarked a year and a half ago. If you don’t live in the Bay Area, you can also purchase their goods online at various design stores.

I didn’t think to take any photos of the place while I was in the store. I should have since they do their cash register is an executive desk with an iMac 19″ embedded below the desk surface running a copy of Windows in order to do the point-of-sale software. It looked like a big old ergonomic mess, and I asked if it was as stylish-yet-unfunctional as it that seemed. Apparently, according to the clerks, my hunch was right. I guess someone saw Tron too many times.

The wallet has a magnetic money clip and could hold about 8 cards if you really try hard—I have four in there and it’s pretty tight. The animal skin is ostensibly from Italy, but it’s stitched in China. Since the stitching is done with a machine, the threads are pretty tight—not as nice as my Hirano camera case, but what is?

People always ask me about the metal thing is the center of my wallet—It’s a Wallet Pen. I highly recommend them, though I replace the ink with a Fisher universal multi-pen refill.

We’ll see how long I last without membership cards, change, and gum wrappers.

Posted on January 30, 2010 by tychay 11

What dSLR (not to buy)? [The entry kit dSLR Part 3]

(Article continued from part 2)

I wrote an article about purchasing an entry dSLR four years ago. What it so surprising is how much of it has stood the test of time—only small details and features have changed: Nikon autofocus now has more points than Canon (as well as better coverage and the use of color); Olympus no longer is the only company with Live View (even Pentax does it), nor the only company with dust shake (all the others, starting with Canon, now offer it); Sony is not the only company with sensor-shift image stabilization.

Still, the essence is still true: Canon and Nikon remain among the last three holdouts adamantly against sensor-based image stabilization. Canon settings are still bulletproof; Nikon still is light focused: with the best autoexposure system and the best high ISO performance. Olympus and Panasonic are still cramming the coolest tech into the smallest space, Sony is proving their engineering chops, and Pentax is still putting photographic value first.

Nikon D5000 w/AF-S Nikkor 50mm f/1.4G
South of Market, San Francisco, California

Olympus E-P2, M.ZUIKO Digital ED 14-42mm 1:3.5-5.6
1/6sec @ ƒ5.2, iso 800, 36mm (72mm)

It’s still best to forego the kit and stick a fast-wide-cheap prime on your camera. This Nikkor 50mm f/1.4 lens is not cheap, but Nikkor 35mm f/1.8 DX lens is the 50mm equivalent for Nikon APS-C and costs about the same as a kit lens. I’ll talk about lenses in a later section.

The rounded right side of the camera is actually an extremely well thought out way for resting smaller these smaller cameras in your palm. It’s a tiny detail, I’ve not seen in the other Nikon models, but it’s just one of the reasons why people rave about Nikon small body dSLR ergonomics.

The advice hasn’t changed: When you buy a first dSLR, it is still the best to forgo the kit lens and plaster on a cheap, fast prime. Lenses still get more expensive, and bodies still get cheaper. Every manufacturer makes a camera for your budget with a negligible price difference…

And the problem is all the cameras are still too good.

In fact, the most significant difference from four years ago is only that the “entry level dSLR” has dropped below $700 for an entire kit, (in addition to) the $1000 “body-only” category—redefining the latter as an “enthusiast” category. Not only that, in many cases, manufacturers have issued multiple models in this sub $700 category, all offering at least one full kit below $550. Three of these sell kits for less than a Canon G11 pocket camera!

Continue reading about The mistake not mentioned after the jump

Posted on January 29, 2010 by tychay 9

The Woodwork

You tell that other boy, not to touch the woodwork