enginebrainstorms

ozan (oz) yigit's noteblog at sun. all my text and photography is released under a cc attribution-noncommercial-noderivs license. all my poetry requires explicit permission.



20050525 Wednesday May 25, 2005

harley dreams [multiple exposures in digital] harley dreams

if you do not have a multiple-exposure capable DLSR (fuji s2 pro, nikon d2x), there are several things you can do: you can synthetically create the multiple exposure from a single exposure in photoshop [or gimp or digital darkrooom of your choice] or you can be a purist like me and actually make many exposures to be combined into one image, as you would do with film.

harley dreams multiple

here is a harley davidson police edition engine block, in both kinds of multiple exposures. a synthetic multiple exposure [left image] is a simple multi-layer operation, a bit tedious for its mechanics, but quite entertaining for its results:

  • copy n layers out of a single image
  • for each layer do:
    • shift, rotate, resize or otherwise transform a layer
    • set visibility to lighten
  • crop the result appropriately for composition and clean edges

the example on the right is just a double exposure, one regular image, and another image made out of focus for specular highlights. [this one is for lee schlais. nikon d70, nikkor 105mm f/2.8D]

[musical suggestions while gimping along: dead can dance, a passage in time, beggars banquet music, 1998.]

(2005-05-25 20:34:46.0) Permalink Comments [1]

raw flaw openraw logo

michael reichmann and jurgen specht have published a good essay about the camera raw problem, recently inflamed by nikon's unfortunate decision to encrypt NEF white balance information. [this essay is more or less a summary of what many photographers have been writing; nikon has already lost d2x sales as a result of its decision]

[this line from the article does not work]

But, in the US at least, with the Millennium Copyright Act, the game has changed. Simply put, anyone that cracks encrypted or otherwise protected intellectual property is subject to criminal prosecution. And, since it possibly can be argued that the code (not content) in an encrypted or "protected" RAW file belongs to its creator (meaning the camera maker), any company or programmer breaking that code needs have liability concerns.

this is a confusion over the creator of the intellectual property and the content vs its container. how do we seperate the two cleanly [if we can at all], and what rights does the photographer have over the container, the digital equivalent of mylar and silver halide crystals? i think there is a good argument that says every bit of information [eg. white balance] carried in the container for the unrestricted recreation of the image is a part of the intellectual property and it cannot be kept from its creator. as I have suggested before, hiding any of this information is an intolerable bit of idiocy, and is good grounds for a legal action against a manufacturer.

[musical recommendation: grant green, the latin bit, blue note]

(2005-05-25 08:15:27.0) Permalink Comments [0]

Calendar

« May 2005 »
SunMonTueWedThuFriSat
1
5
7
8
9
12
13
14
15
16
18
19
20
21
24
27
28
29
    
       
Today

Search

RSS Feeds

XML
All
/books
/design
/general
/humor
/java
/music
/opensource
/photography
/poetry
/programming
/sf
/skeptic
/tools

Links





Get OpenSolaris

Recent Entries


Navigation



Referers

Today's Page Hits: 186