Trevis Rothwell's weblog

Should Digital Photos Aspire to Look Like Film?

17 February 2014

I received an email from B&H Photo yesterday, advertising some new products and sales. After years of doing my minimal photo post-processing in Apple iPhoto, the reduced price on Adobe Lightroom 5 caught my attention. Reading the details more carefully, I was intrigued by the statement:

You can add … simulated film grain to images, great for breathing analog life into digital photos.

In the music production world, I’ve heard a lot of people talking about the virtues of running tracks through analog equipment to maintain or capture “analog warmth” in the face of sterile digital perfection. There are debates as to how needful an analog signal chain actually is, and some producers seem fine with totally digital production, but there are enough adherents to analog audio gear to suggest that there’s some legitimate basis to the claim. Several manufacturers sell analog summing mixers, to do a task in the analog realm that digital computers ought to be excellent at doing (adding things together).

While I’ve heard some photographers share a preference for working with film, I believe this is the first time I’ve seen a major vendor suggest that there might actually be something superior about film photography that digital photographers should consider simulating. So what exactly does this simulated film grain feature do?

I found an example from Mark at Digital Photo Buzz, showing the difference between an unaltered digital photo, the same photo processed in Adobe Photoshop to add “noise”, and the same photo processed in Adobe Lightroom (version 3) to add “film grain”. The processed photos appear at first glance to be blatantly inferior to the original, but then again, after looking at the processed photos for a bit, the original seems almost artificially perfect.

I’ve never done an explicit A/B test between my digital and film cameras, but I happen to have several similar shots taken on two separate trips to Cambridge, Massachusetts, one time with film and the other with digital:

Falafel Truck on Kodak 400 film

Falafel Truck on Canon 5D digital

Harvard University Library on Kodak 400 film

Harvard University Library on Canon 5D digital

(All photos taken with a Canon 50mm/1.4 lens. The film photos were taken with standard off-the-shelf Kodak 400 print film.)

The film photos, as presented, are higher contrast. This could be adjusted in post-processing if desired. I don’t really see anything significant that I would attribute to “film grain” in the film photos; the grain certainly isn’t as obvious as in the simulated grain photo produced in Adobe Lightroom. The digital photos, when viewed full-size, are more detailed, and generally seem like closer representations of what the scene actually looked like (as I recall).

But is one flat-out better than the other? Aesthetically, I kind of like the look of the film photos better. The digital photos may be more perfect, but the film photos seem to have some imperfections that come across well, maybe similar to the color added to sound running through a tube preamp. It’s hard to beat the convenience of digital over film, but perhaps I’ll start pulling my ancient Canon EOS-3 out more often…

Government-Mandated Flame-Retardant Mattresses

23 January 2014

Two days ago we received delivery of a new mattress. Upon initially lying down to go to sleep on it, I detected a strange odor and reasoned that it must be emanating from either the new sheets, the new mattress cover, or the new mattress, but was too tired to think much about it. The odor became increasingly bothersome throughout the night, and in the morning I determined that it was most likely coming from the mattress itself.

Some web searching suggested that this was not unusual, and that common wisdom was to let the mattress air out for a day or two (or four) before sleeping on it. This was the second mattress we had purchased from the same shop, and nobody had mentioned anything about this to us. The first mattress, though, was left unused for several weeks before we moved into the house, so it likely had time to air out on its own.

My web searching also turned up some unexpected information on the potential toxicity of mattresses.

In 1972, the United States federal government decided to help prevent burning cigarettes set mattresses ablaze by issuing 16 CFR Part 1632, Requirements for Mattresses and Mattress Pads. Accompanied by a prescribed test procedure, this government mandate required mattress manufacturers to construct their mattresses to be able to endure limited exposure to burning cigarettes without catching on fire themselves. Since traditional mattress materials were not inherently flame-retardant, manufacturers complied by adding flame-retardant chemicals.

In 2006, the government decided that guarding against burning cigarettes was insufficient, and expanded their mattress construction criteria to include guarding against various open flames in 16 CFR Part 1633, Standard for the Flammability (Open Flame) of Mattress Sets. The new test criteria involves exposing the mattress to open flame generated by a burner device for a total of 30 minutes. (Details are listed within 16 CFR Part 1633 itself.) Manufacturers complied to this demand of enduring a half-hour of fire by adding yet more flame-retardant chemicals.

So our mattresses are very unlikely to engulf us in flames. But what about the chemicals being added to the mattresses? Are these safe for us to sleep on night after night? Since the government cares so much about us not setting our beds on fire, surely they would have interest in what chemicals are employed to fire-proof the mattresses?

They did conduct some thorough research on the extent to which the various chemicals used in mattress construction could be absorbed by its users, but when it comes to actually making a decision on what chemicals go into the bed, they leave that up to the mattress manufacturers. The 16 CFR Part 1633 Questions & Answers document explains:

Empty Index Entries in Texinfo

7 November 2013

Working on a book formatted with GNU Texinfo, I ran into a mysterious error when processing the Texinfo source through TeX (via texi2pdf):

(Variable Index) [145] (Concept Index) [146] (./c.cps

./c.cps:1: Extra }, or forgotten \endgroup. l.1 , 145}

I saw no related error or warning out of Makeinfo, and TeX was unhelpfully not saying anything about which Texinfo source line the error was coming from. Other clues suggested that the error has to do with indexing, and that it has to do with an index entry pointing to page 145 or maybe 146.

Looking at the PDF output, I backtracked to the relevant portion of the Texinfo source, and saw something like this:

@cindex function pointers

@cindex

A normal-looking index entry followed by an empty index entry! I removed the empty index entry and reran TeX; all was fine.

Evidently empty index entries are not handled well in Texinfo or texi2pdf or TeX or wherever the actual failing is coming from. A more helpful error message would be nice, but in the meantime, remember to avoid blank index entries!

Book Review: The Children’s Machine

21 September 2013

This past spring I read Seymour Papert’s Mindstorms as part of the MIT Media Lab Learning Creative Learning course. Having been delighted with that book, I just finished reading Papert’s follow-up book, The Children’s Machine (Rethinking School in the Age of the Computer).

Published in 1993, this book comes across as technologically more modern than 1980′s Mindstorms, though still obviously dated. For me, it is dated in an especially nostalgic way, as it was around the late 1980s / early 1990s that I was first learning about computer programming, and I can personally identify with some of the stories and concepts that Papert discusses here.

Broadly, this book might be viewed as a refinement of Mindstorms, whereby Papert had over a decade of additional experience and observations with which to form stronger, clearer opinions and gather more data and anecdotes. But while Mindstorms seemed to focus more on the specific idea of creating virtual educational worlds on the computer in which students could more easily learn abstract ideas, the present book steps back even further to look at understanding learning itself better.

Papert advances the term mathetics for describing the study of learning, as opposed to pedagogy, the study of teaching. Are there methods we can use ourselves, or encourage in students, to identify what needs to be done on the learner’s side in order to learn better? To rely on “being taught” without exerting enough effort on “learning” puts things out of balance.

This concept of mathetics is woven into accounts of using computers to improve how learning takes place, especially through creative learning techniques of building virtual things with computers, and through the notion of learning a concept better by teaching it to the computer via programming. For example, we read some stories about the development and usage of the Logo programming language and the Turtle programming system that was developed with it, and how this grew into a form of cybernetics controlling robotic Legos. Here’s a short example, in this instance about using Mitch Resnick’s multi-turtle Logo variant, *Logo:

Two high school students who had recently received their driver’s licenses decided to use *Logo to show cars moving on a highway. The students started by creating several dozen turtles, each representing a car. The program consisted of two simple rules. If a car sensed another car ahead of it, it slowed down. If it didn’t sense another car, it speeded up. With this simple program the students did not expect much to happen, but when they ran it, the cars bunched into a realistic-looking traffic jam. … It is worth noting that the students appreciated the self-organizing nature of the traffic jam only because they had written the programs themselves. Had they been using a packaged simulation, they would have had no way of knowing the elegant simplicity of the programs underlying the jam.

The front cover quotes School Library Journal as saying, “Educators with a vested interest in the status quo will hate this book. It is about their demise.” Indeed, there are numerous points brought up for consideration about how the educational system could be improved, including scathing criticism of attempts to nationally standardize education and judge student development based on standardized tests. Along these lines, Papert poses an interesting query for educational administrators:

[O]n my reckoning, the fraction of human knowledge that is in the [school] curriculum is well under a millionth and diminishing fast. I simply cannot escape from the question: Why that millionth in particular?

If you must limit yourself to reading only one Papert book, Mindstorms came across to me as more fresh and exciting, but the creative learning aficionado will get valuable insight from reading both. The paperback edition is available at Amazon. No electronic edition appears to be available.

Book Review: Privacy on the Line

11 September 2013

I just finished reading Privacy on the Line: The Politics of Wiretapping and Encryption. With all of the information being revealed and confirmed recently about United States government surveillance on personal communications, I wanted to be more educated on the issues.

Going about our day-to-day lives, how much privacy do we really have? The authors explain:

From video cameras that record our entries into shops and buildings to supermarket checkout tapes that list every container of milk and package of cigarettes we buy, privacy is elusive in modern society. There are records of what we do, with whom we associate, where we go. Insurance companies know who our spouses are, how many children we have, how often we have our teeth cleaned. The increasing amount of transactional information — the electronic record of when you left the parking lot, the supermarket’s record of your purchase — leaves a very large public footprint, and presents a far more detailed portrait of the individual than those recorded at any time in the past. Furthermore, information about individuals is no longer under control of the person to whom the information pertains; such loss of control is a loss of privacy.

What about U.S. government surveillance? The authors provide chapters of fascinating details, including:

Beginning in 1940 and continuing until 1973, FBI and CIA agents read the private mail of thousands of citizens. … Without warrants and without congressional or clear presidential authority, intelligence agents opened and perused the mail of private citizens, senators, congressmen, journalists, businessmen, and even a presidential candidate.

Numerous other examples include the FBI’s excessive surveillance of Martin Luther King, Jr., authorized wiretaps being left activated beyond their official period of use, the FBI seeking information on who has borrowed unclassified scientific and technological books from public libraries for the purpose of identifying possible Russian spies, and more. In some cases, the FBI admitted that their surveillance tactics exceeded legal limits; in other cases, evidence against the FBI magically disappeared. Either way, it appears that if government agents wish to violate the law when it comes to surveillance, there is little (if any) actual oversight of their actions.

While government surveillance has been expanding by leaps and bounds, the authors make the case that not only is the huge amount of surveillance not commensurate with the relatively small amount of criminal or violent activity that it helps prevent, but even in situations where surveillance has been credited with helping to prevent undesirable outcomes, the surveillance tactics may not have been necessary.

It is important to apply common sense to the issue of terrorist investigations and to think clearly about which acts can be prevented and which cannot (Heynmann 1998, pp. xxi-xxiii). Timothy McVeigh’s attack on the federal office building in Oklahoma City was the work of a group of three people. … Unless the United States moves to a surveillance society on the scale of the former East Germany, the country will never be able to protect itself fully against attacks by “lone warriors” such as McVeigh.

To be clear, the authors do not claim that surveillance is useless against criminal or terrorist behavior; rather, it is of limited usefulness, and we need to appropriately balance legitimate surveillance needs with the privacy of the citizens.

On a more practical level, should we use encryption to protect the privacy of our emails and other communications? The authors seem generally in favor of it, but also warn us that:

One strategy followed by many pieces of intercept equipment should be a caution to anyone using cryptography: if an intercepted message is found to be encrypted, it is automatically recorded.

Since most emails are presently not encrypted, the very act of encrypting yours may draw attention to yourself. But at the same time,

as the use of cryptography increases, the privacy of everyone’s traffic benefits.

In light of the recent disclosures about the NSA’s methods of circumventing encryption, the book’s concluding chapter offers some especially interesting thoughts:

By building the machinery for surveillance into the US communication system, we overcome the largest barrier to becoming a surveillance society on a possibly unprecedented scale.

Once past that barrier (a place we may already have arrived at), it is much easier for laws and policies to fall into place in accordance with what is technologically possible.

This book is tightly packed with well-sourced information; I’ve only hit a few highlights here. It is available both in printed form and for Amazon Kindle, but if you don’t want the NSA to know that you bought this book, and if you don’t want Amazon to know how you read it, you might want to pay cash at the MIT Press Bookstore in Cambridge…