<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>O&apos;Reilly Digital Media Blog</title>
<link>http://blogs.oreilly.com/digitalmedia/</link>
<description>O&apos;Reilly Digital Media Blog</description>
<language>en</language>
<copyright>Copyright 2008</copyright>
<lastBuildDate>Thu, 02 Oct 2008 12:06:56 -0800</lastBuildDate>
<generator>http://www.sixapart.com/movabletype/</generator>
<docs>http://www.rssboard.org/rss-specification</docs>

<item>
<title>Business Tips for Creative People</title>
<author>
<name>David Battino</name><uri>http://digitalmedia.oreilly.com/pub/au/2032</uri>
</author>
<description><![CDATA[<div class="ap_r" style="width:148px;"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/10/linndrum-ii-3.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/10/linndrum-ii-3.jpg" alt="linndrum-ii-3.jpg" title="Click to enlarge" width="148"/></a><div class="apcaption">Lots of beautiful noise in the LinnDrum as well....</div></div>

<p>Drum machine inventor <a href="http://www.rogerlinndesign.com" target="_blank">Roger Linn</a> once told me, "A creative mind is a <em>loud </em>mind. It has lots of thoughts popping up in different directions." </p>

<p>For creative people, focusing can be difficult. That's why I was intrigued by Michael W. Dean's recent essay, called simply "<a href="http://viralvideowannabe.com/professionalism/" target="_blank">Professionalism</a>." It's an outtake from his upcoming O'Reilly book with Alan Lastufka, <em><a href="http://oreilly.com/catalog/9780596521141" target="_blank">YouTube: An Insider's Guide to Climbing the Charts</a>.</em> </p><p>

Michael's head must be loud indeed; he's constantly sending me article ideas, and we've <a href="http://www.oreillynet.com/pub/au/3220#Articles" target="_blank">published</a> many of them here. But somehow, he has the ability to achieve as well as conceive, and these <a href="http://viralvideowannabe.com/professionalism/" target="_blank">straightforward tips</a> explain why.
</p>
]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/10/business-tips-for-creatives.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/10/business-tips-for-creatives.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Creativity</category>


<category domain="http://www.sixapart.com/ns/types#tag">business</category>

<category domain="http://www.sixapart.com/ns/types#tag">creativity</category>

<category domain="http://www.sixapart.com/ns/types#tag">production</category>

<pubDate>Thu, 02 Oct 2008 12:06:56 -0800</pubDate>
</item>

<item>
<title>OpenOffice.org 3 Release Candidate 3: No X11 Needed</title>
<author>
<name>Todd Ogasawara</name><uri>http://ogasawalrus.com/</uri>
</author>
<description><![CDATA[<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/ooo3rc3_menu.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/ooo3rc3_menu.png" alt="ooo3rc3_menu.png" title="Click to enlarge" width="148"/></a></div>
I took a close look at the OpenOffice.org 3 Beta release back in May (<a href="http://blogs.oreilly.com/digitalmedia/2008/05/openoffice-30-beta-with-native.html">OpenOffice 3.0 Beta with Native Mac Aqua Interface (Finally!)</a>). <a href="http://download.openoffice.org/680/">Ooo 3 is now in a Release Candidate 3</a> stage. Since, it should be close to production quality by this stage, I decided to revisit it. I tested it on a first generation MacBook with a 2GHz Core Duo processor and 1GB RAM.

<p>OOo 3 looks like it starts faster than OOo 2 since it doesn't require starting X11 first. However, opening any kind of document file (even a simple HTML file) seems to take a bit longer than I expected at this stage of the game (Release Candidate 3).</p>

<p>Although I never use word processors to edit HTML or XML files, I brought in this blog item into the OOoeditor. Why? I simply wanted to see what its HTML editor looked like. I was shocked to find that it behaved like Microsoft Word and the now defunct Microsoft Frontpage by actually modifying even the simplest tags like the paragraph tag without asking. Then, it automatically saved the changes to the file, again, without asking. I had a backup of this file (which happened to be this blog entry). So, it wasn't a disaster.</p>

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/Ooo3rc3_ppt.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/Ooo3rc3_ppt.png" alt="Ooo3rc3_ppt.png" title="Click to enlarge" width="148"/></a></div><br />
The main point of OOo 3 from the Mac point of view is that it is now a native application using the native graphical interface style. You can see the OOo Presentation view with an old PowerPoint 2003 slide deck opened. As you can see, it has the general look and feel of other Mac applications.</p>

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/ooo3rc2_dialogoptions.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/ooo3rc2_dialogoptions.png" alt="ooo3rc2_dialogoptions.png" title="Click to enlarge" width="148"/></a></div><br />
OOo 3 does, however, give you the option to switch conventional OOo dialog boxes instead of the familar Mac style dialogs. If you are a long time OOo user or switch between a Mac and Windows or Linux, this might be a desirable option.</p>

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/ooo3rc3_bullets.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/ooo3rc3_bullets.png" alt="ooo3rc3_bullets.png" title="Click to enlarge" width="148"/></a></div><br />
The conversion issues I noted in the OOo 3 Beta release remain in RC2. For example, you can see the result of importing a relatively simply formatted Word 2007 DOCX file. The bullets used in Word were the default bullets but did not translate in OOo 3. This paricular document also had a number of comments between me and the article's editor. OOo does not provide editorial commenting features. So, the comments were simply added as ordinary text on each page.</p>

<p><br />
However, I'm not going to dwell on compatibility with Word, Excel, or PowerPoint. The main points is that it looks like OOo 3 is nearing a production release and that its long awaited native Mac interface looks good and seems to work well after a couple of weeks of use (I started with RC2 and then updated to RC3 after its release).</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/10/openoffice-3-release-candidate.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/10/openoffice-3-release-candidate.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Mac</category>


<category domain="http://www.sixapart.com/ns/types#tag">open source</category>

<category domain="http://www.sixapart.com/ns/types#tag">openoffice</category>

<pubDate>Wed, 01 Oct 2008 04:00:00 -0800</pubDate>
</item>

<item>
<title>My iPhone feels Orange</title>
<author>
<name>FJ de Kermadec</name><uri>http://fjdekermadec.com</uri>
</author>
<description><![CDATA[<p>When in France, do as Orange does. For the past few weeks, iPhone 3G users in France have suffered intermittent voicemail glitches, often in the form of erroneous outgoing messages. As time goes on, it appears the light at the end of the tunnel is, as my computer would have said a few years ago, the headlamp of a fast approaching train.</p>

<p>While most users may not be affected by the issue, those who are will not necessarily notice. Why? Because one rarely calls one's own voicemail, and check whether the outgoing message is the right one. My natural tendency to paranoia means I have a daily reminder to do just that, and it proved an excellent decision.</p>

<p>The day after switching to my iPhone 3G, my voicemail decided I was no longer the CEO of <a href="http://webstellung.com">Webstellung</a>, but rather of Antonia Communication &mdash; my company's former, now long forgotten name. Upon calling up Orange I was informed that I was "lucky" as some voicemail accounts had not only been associated with old, long deleted messages, but with messages that did not even belong to their owners!</p>

<p>Since then, voicemail messages have come and gone randomly. Today, I was greeted by Orange's own syrupy voice, while yesterday it was the right recording indeed. </p>

<p>Of course, none of the officially sanctioned methods to save, remove or alter a recording work: neither the buttons on the iPhone, nor the voicemail's own menu options do anything. As for Orange.fr, it's as helpful as always.</p>

<p>On a side note, here is a trick, if you are affected. While you cannot prevent the default recording from kicking in once in a while, you can probably replace the part where your own name is played by something accurate. That doesn't make it any less frustrating, but at least you may be able to erase the name of the number's previous owner.</p>

<p>Now, might you ask, what is Orange doing? We shall never now, but probably nothing at all. I have been twice informed that they've "brought it up with Apple," which, knowing how fast both Apple and Orange work when customer satisfaction in the French market is involved, doesn't bode too well.</p>

<p>After all, voicemail messages flow in normally once the wrong recording has played, so it's merely cosmetic and the situation offers an ideal opportunity for both parties to hold the other responsible until the end of time.</p>

<p>For the time being, and for lack of a better option, I will be keeping my fingers crossed. Apart from that, I hear MobileMe speeds from Europe will soon be worked on too, right after that foul-smelling Mac Pro issue is taken care of.</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/10/my-iphone-feels-orange.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/10/my-iphone-feels-orange.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Mac</category>


<pubDate>Wed, 01 Oct 2008 02:38:35 -0800</pubDate>
</item>

<item>
<title>Apple&apos;s Software User Guide Diet</title>
<author>
<name>Jochen Wolters</name><uri>http://www.oreillynet.com/pub/au/2663</uri>
</author>
<description><![CDATA[<p>Apple's handheld devices are an example for miniaturization at work: with every new release, iPods have gotten a little smaller, and "incredibly thin" is the new "insanely great." Unfortunately, Apple has also miniaturized some of their software user guides.</p>

<p>Back in 2003, Apple introduced Keynote. The first release of this presentation software shipped in a "full-size" carton box, and inside that box you would find a well-written, 97-page user manual that covered every feature of the software. As a complement to that manual, the box also contained a four-page reference card with lots of full-color screenshots.</p>

<p>In 2005, Apple debuted the Pages word processor and combined it with Keynote to create the iWork office "suite." The software shipped in a slightly smaller box (whose graphic design sparked quite a few debates) and, consequently, the printed user documentation was printed on slightly smaller-size paper as well, but it still consisted of comprehensive user guides and reference cards, one each for Keynote 2 and Pages. It did not really make much of a difference that the reference cards did not feature screenshots anymore; what did make a difference, though, was that Apple decided to also reduce the font size for the printed manuals, making them a bit harder to read for people with vision problems.</p>

<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/AMOD_iWork.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/AMOD_iWork.jpg" alt="AMOD_iWork.jpg" title="Click to enlarge" width="148"/></a><div class="apcaption">Packages and enclosed core documentation for Keynote, iWork '05, and iWork '08: ever-smaller boxes and ever-smaller user guides.</div></div>

<p>Fast forward to iWork '08, and the box in which the software -- now also including the Numbers spreadsheet application -- is sold has been reduced to the size of roughly two stacked CD jewel boxes. Which, of course, is also reflected by the size of the user guide inside the box and, again, by further reducing the font size used inside that guide. Yes, <em>the</em> guide, because only one printed manual remains, and instead of extensively covering all features of all three applications, it presents introductions to each application's core features, filling less than 150 pages total. If you want to learn all the ins and outs of Keynote, Pages, and Numbers, you are referred to PDF files  on the installer CD, the largest of which is comprised of some 300 pages.</p>

<p>Reducing the size of the carton box makes a lot of sense: it keeps storage and shipping costs low; reduces the use of natural resources for creating as well as shipping each box; and it makes the box look sleaker and more elegant. But this comes at the price of reduced usability of the enclosed documentation.</p>

<h3>The usability of software documentation</h3>

<p>The concept of usability applies to a software program's user documentation just as it applies to the program itself. Here are five suggestions for attributes by which the usability of a user guide may be judged. Please note that this is specifically about user guides, not online help systems, which differ in some respects.</p>

<ol>
<li><p>Designed for the target audience</p>

<p>The user guide should reflect the complexity and depth of the application as well as the expertise levels of the average user. Consequently, a configuration guide for the Apache webserver will differ considerably from a manual for iPhoto in terms of tone-of-voice, usage of technical terms, number of screenshots, verbosity of instructions, etc.</p>

<p>That aspect of tone-of-voice is important, and even more so when writing beginner guides: no-one likes being talked down to, so it's essential that the author of the guide takes the user seriously, and that the focus for the user is in enjoying the discovery of new software features and gaining new skills in using those features, instead of having the feeling of not knowing anything about an application yet re-inforced by the way the user guide is formulated.</p></li>
<li><p>Comprehensive, yet concise</p>

<p>A user manual should be comprehensive by covering every feature in the application. A software developer or user guide author should not try to guess what the user may already know about the  software. When keeping #1 in mind, a user guide could address different levels of expertise by special entry-level chapters that an advanced user could simply skip.</p>

<p>Comprehensive does not necessarily mean verbose, though, and it definitely does not mean that there is room for excessive marketing speak. A user guide is not an outright sales brochure. </p></li>
<li><p>Easy to navigate</p>

<p>A well-designed manual can serve both as a tutorial and a reference.</p>

<p>The best manuals I have seen present their material in such a clear structure that you can work through the book from beginning to end to familiarize yourself with the software as a whole, and yet easily find information on a specific feature if you need help while working with the application.</p>

<p>For printed manuals, a cleanly-structured table of contents and a comprehensive index make finding what you are looking for simple despite the lack of an active search function as found in online help systems or PDF viewers.</p></li>
<li><p>Optimized for display medium</p>

<p>The requirements for printed manuals differ quite a bit from on-screen guides distributed as PDFs, and the design of each should be optimized for the respective characteristics of the medium.</p>

<p><em>For printed manuals</em>, a page size should be chosen that can be comfortably handled physically. The font-size must be big enough to read even for users with less than 20/20 vision, and screenshots and graphics need to show enough contrast for the same reason. Some white space next to the text is handy for scribbling down some notes while working through the manual. As a minor, yet crucial detail, a binding that allows the book to lie flat without having to break that binding first, is a major relief for anyone who is driven up the wall by a book that just won't lie flat.</p>

<p><em>For on-screen manuals</em>, screen space is a precious resource. It should not be wasted by excessive white space on the user guide's pages even if that would look good in a printed copy.  The user should be able to navigate and read the guide without too having to scroll individual pages when viewing the document at 100% zoom. At full zoom, the font size should allow for easy reading of all text -- including, e.g., tables and explanations in screenshots -- and the font should not become distorted or fuzzy too easily even when viewed at smaller zoom settings. Where appropriate, hyperlinks can help the user navigate the document.</p></li>
<li><p>Include printed manuals for screen-hogging software</p>

<p>As mentioned earlier, given the economical and ecological costs of printed manuals, it makes sense to reduce the amount of printed documentation that ships with software applications. However, there are some software programs for which resorting to an on-screen manual is just not a viable option.</p>

<p>When running an application that uses hardly any screen space -- think Calculator or iChat --, there is always ample room left for reading a PDF manual on-screen, so one can easily justify scrapping a printed guide. This is, however, not the case when working with an application of the "never enough screen space" type. If you have ever launched a higher-end media editor like Final Cut Pro, Logic, or ProTools, you will know that, no matter how big your computer's monitor, you will always use the application at full screen and still complain that you could always use another one of the nifty 30" Cinema Displays. For these kinds of applications, I consider an un-abridged printed manual a must-have feature.</p>

<p>Even when a printed manual is included, also throwing in an electronic version -- that is optimized for on-screen reading -- is a good idea, as it makes the complete reference materials available even when traveling with a laptop.</p></li>
</ol>

<h3>What about Apple's user guides, then?</h3>

<p>So what about Apple's user guides: how do they fare with regards to these five criteria?</p>

<p>The iWork '08 manuals are too small in more ways than one: physical size, font size, screenshot resolution, and content. The full PDF manuals that ship on the CD are comprehensive, but they waste much screen real-estate with white space, require scrolling when viewed at the original size on a MacBook, and when zoomed-to-fit, the font is hard to read. And, as you can see in the screenshot, the iWork applications also are an edge case with regards to "screen-hogging."</p>

<div class="ap_c"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/AMOD_CrammedPages.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/AMOD_CrammedPages.jpg" alt="AMOD_CrammedPages.jpg" title="Click to enlarge" width="400"/></a><div class="apcaption">Electronic user guides do not work well for applications that use up a lot of screen real-estate.</div></div>

<p>Unfortunately, the same criticism even applies to at least one of Apple's Pro apps: Aperture. The printed manual that ships with Aperture is titled "Exploring Aperture." While this book provides a very well-designed, easy-to-follow, and fun introductory course to the software, it shares the same size issues found with the iWork '08 manual. Unlike iWork '08, though, Aperture is not an edge case when it comes to screen-hogging: software of this type should definitely ship with a full-size and complete <em>printed</em> manual.</p>

<div class="ap_c"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/AMOD_BookVsBooklet.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/AMOD_BookVsBooklet.jpg" alt="AMOD_BookVsBooklet.jpg" title="Click to enlarge" width="400"/></a><div class="apcaption">The miniature "Exploring Aperture" booklet vs. the full-size Logic 8 reference guide book. The image does not do the difference in font-size justice: reading the Aperture booklet is much more tiring than working through the Logic book.</div></div>

<p>Contrast this to the documentation that is included with the Logic Studio audio editing and recording suite: the two main manuals -- one on the application itself and another one on the instrument and effects plug-ins -- offer a luxurious 1,900+ pages' and almost 3 inches' worth of fine reference material.</p>

<p>I would hope that the powers that be at Apple will change their criterium for defining the required minimum size packaging for software products from the current "that installation CD must still fit in there" to "a useable printed manual should fit in the box." At least for complex, functionally "deep" applications like iWork, Aperture, etc., proper printed documentation is not a nice add-on, it's an essential part of the overall product. And with the in-house benchmark of the Logic Studio user guides, the required expertise for designing that proper printed documentation is definitely available.</p>
]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/apples-software-user-guide-die.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/apples-software-user-guide-die.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Mac</category>


<category domain="http://www.sixapart.com/ns/types#tag">documentation</category>

<category domain="http://www.sixapart.com/ns/types#tag">manuals</category>

<category domain="http://www.sixapart.com/ns/types#tag">software distribution</category>

<category domain="http://www.sixapart.com/ns/types#tag">usability</category>

<pubDate>Tue, 30 Sep 2008 07:00:00 -0800</pubDate>
</item>

<item>
<title>Reality Leaves a Lot to the Imagination</title>
<author>
<name>Rick Sammon</name><uri>http://www.oreillynet.com/pub/au/3255</uri>
</author>
<description><![CDATA[<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/hdr%20workshop.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/hdr%20workshop.jpg" alt="hdr workshop.jpg" title="Click to enlarge" width="148"/></a></div>

<p>"Reality leaves a lot to the imagination" is one of my favorite John Lennon quotes. Think about it and you'll realize that it's true. I was thinking about this quote when I was photographing a pond near my house. I was trying to envision how the pond would look if I used Photomatix Pro from <a href="http://www.hdrsoft.com/">HDR Software</a> on a set of seven pictures (each taken at a different exposure setting).</p>

<p>I was trying to Imagine (envision) the possibilities that awaited me in Photomatix when I photographed the scene - which had a very high dynamic range. Sure, with the 11-f-stop range of my eyes, I could see into the shadows and see details in the clouds at the same time - but my digital SLR, with its 5-stop range, cold not capture what I was seeing.</p>

<p> Photomatix to the rescue.. with a bit of standard<a href="http://store.apple.com/us_smb_78313/product/MB673Z/A?cid=OAS%2DUS%2DKWG%2DSMB%2DUS"> Aperture 2</a> adjustments  (selective enhancements using the Dodge & Burn tool (which I talk about in this<a href="http://www.pcphotomag.com/how-to/quick-fix/quick-fix-adventures-in-aperture.html"> PCPhoto </a>article).</p>

<p>The next time you are shooting in a high contrast situation, think about John Lennon's quote - and HDR. Your reality is only limited by your imagination.</p>

<p>By the way, check out Hydra, one of many<a href="http://www.apple.com/aperture/resources/plugins.html#editing"> Aperture Plug-ins</a>. It lets you create HDR images without leaving Aperture.</p>

<p>Rick <br />
P.S. I am offering one-day<a href="http://www.ricksammon.com/Workshops_Seminars.html">, HDR classes</a> in Croton-on-Hudson, NY - one hour from NYC. Drop me an email to get on the schedule: ricksammon@mac.com.</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/reality-leaves-a-lot-to-the-im.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/reality-leaves-a-lot-to-the-im.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Photography</category>


<category domain="http://www.sixapart.com/ns/types#tag">digital photography</category>

<category domain="http://www.sixapart.com/ns/types#tag">HDR</category>

<category domain="http://www.sixapart.com/ns/types#tag">high dyanmic range</category>

<pubDate>Mon, 29 Sep 2008 18:17:47 -0800</pubDate>
</item>

<item>
<title>Audio Performance at 120 MPH!!!</title>
<author>
<name>David Javelosa</name>
</author>
<description><![CDATA[<p>Ok, it&rsquo;s been 11 months since I&rsquo;ve written in this blog. But  guess what? I&rsquo;m a new dad! If that isn&rsquo;t life changing enough I&rsquo;m not sure what  is; except the following techno tale I have to tell. Through a strange  intersection of factors, I was personally involved with a pretty interesting  audio experiment, digital or otherwise.

<div class="ap_c"><a href="http://www.oreillynet.com/digitalmedia/blog/images/burning%20nuria.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://www.oreillynet.com/digitalmedia/blog/images/burning%20nuria.jpg" alt="burning nuria.jpg" title="Click to enlarge" width="400"/></a></div>
</p>

<p>Let me crank back to where I was just after my last entry. I  was teaching full-time at SMC, taking an on-line class in serious 3D gaming,  and waiting for the baby to arrive. She hit my life like a hurricane November  8, 2007. I barely recovered in time for the Game Developer&rsquo;s Conference in  February, and I've been sleepwalking ever since.</p>

<p>In my lucid hours, I  have had time for two loves:  electronic music and skydiving. How on  earth could these two passions  ever intersect  than in my wacky life. The baby has continued to grow and my  wife and I thought it would be cute to take her camping. And then it all came  together&hellip;.. <a href="http://www.burningman.com/">Burning Man</a>!</p>

<p>I had been musing about the great desert art festival for a  few years. How would I rig a performance set-up that would withstand the heat,  the dust, and the lack of electricity? Not to mention the acoustic challenge of  being outside,  in the sun or in the cold of night. I thought immediately of  the <a href="http://www.korg.co.uk/products/dance_dj/kaossilator/kaossilator.asp">Korg Kaossilator</a> (mentioned in this column previously) as one of the most  versatile music boxes of recent time. It is by nature small, portable, and  battery powered.</p> 

<div class="ap_c"><a href="http://www.oreillynet.com/digitalmedia/blog/images/DSCN1958.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://www.oreillynet.com/digitalmedia/blog/images/DSCN1958.jpg" alt="" title="Click to enlarge" width="400"/></a></div>
 
 <p>A quick tap on the pad can kick it into a loop of sound just  perfect for the trance like experience of the festival. I then matched it with  a pair of portable guitar amps by <a href="http://www.smokeyamps.com/">Smokey</a>. These devices are  cigarette-package-sized, practice amps of the most minimal utility. One jack in  for the instrument, and one out to pass the pre-amp to a bigger system. The  speakers are durable, loud and crunchy, considering that there is no volume  control other than your instrument. Distortion is part of the charm! The Kaossilator  also has no volume control on its main outputs, so plugging them together meant  I just had to deal with the resulting grunge. So how would I use such an  extreme performance set-up in this extreme environment?</p>

<div class="ap_r"><a href="http://www.oreillynet.com/digitalmedia/blog/images/DSCN1963.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://www.oreillynet.com/digitalmedia/blog/images/DSCN1963.jpg" alt="DSCN1963.jpg" title="Click to enlarge" width="148"/></a></div>

<p>  <p>This brings us to passion #2. As friends will recently  attest to, I have changed in the past few years. I have gone from techno-freak  to extreme-sport-super-freak. I jump out of airplanes for fun. Maybe not JUST fun. I  do compete for skill points, and then there is that saving-one&rsquo;s-life thing with  the parachute. But this is a long story for a different blog.</p></p>

<p>So, I&rsquo;m at Burning Man, the big art/performance festival in  the middle of the no-where desert. And this is my contribution: I tape the Kaossilator  to my chest, under my jumpsuit. </p>

<p>I tape the Smokey amps to my ankles (right and  left channels!) and run the cable up my legs. Zip up the jumpsuit, don my  parachute rig, and ride an art car out to the Black Rock City airport. After checking my  batteries, I board the plane. On the way up to altitude, I&rsquo;m doodling on the Kaossilator  to the annoyance of the other jumpers  until I create an interesting loop. I pause it and keep my finger over the play  button as I prepare to exit the aircraft 10,500 ft. over the playa floor.  (14,500 ft. above sea level). I push the button, take my turn, and jump&hellip;

<div class="ap_c"><a href="http://www.oreillynet.com/digitalmedia/blog/images/IMG_2149.JPG" class="highslide" onclick="return hs.expand(this)"><img src="http://www.oreillynet.com/digitalmedia/blog/images/IMG_2149.JPG" alt="Image" title="Click to enlarge" width="400"/></a></div>
</p>
  
<p>The plan in <a href="http://en.wikipedia.org/wiki/Parachuting">laymen terms</a> was to meet up with another jumper  in free fall, separate around 7,000 ft. and open my chute by 6,000; giving me  5,000 feet of canopy time above the sprawling campsite of 50,000 people (about  10 minutes of gliding), before landing. After my chute opened, I actually could  hear the synth loop in the air, AND through my full-faced helmet. I knew it was  loud but would it be loud enough? The ride down was stunning and I soon forgot  I was blasting music out of my ankles. Swooping over the temporary city was just unreal. 

<div class="ap_c"><a href="http://www.oreillynet.com/digitalmedia/blog/images/burning-man-aerial-photos.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://www.oreillynet.com/digitalmedia/blog/images/burning-man-aerial-photos.jpg" alt="Burning Man Aerial Photos" title="Click to enlarge" width="400"/></a>
</div></p>

<p>I set up my landing in an open stretch just above the main center  of camp and hoped someone would hear the sound. I was rushed by a couple of  &ldquo;burners&rdquo; asking me how the view was, and then they said it. &ldquo;Is that music  coming from you? Are you listening to music skydiving?&rdquo; I didn&rsquo;t have the heart  to say it was for them; evidently the entire performance was for the two people  that I met on the ground.</p>
  
<p>What did I learn? Well the first thing is that the  amplification needed to be louder for people on the ground to hear me from the  air. The entire set-up was also almost too distracting for me to feel safe  jumping out of a plane; meaning I probably would not do it again with  anything larger or more involved. Thankfully, there was no volume control to think  about! And finally, I would have had just as much fun with any of the three  activities by themselves: skydiving, playing music, and being at Burning Man.  So what the hell am I going to do next year?</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/audio-performance-at-120-mph.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/audio-performance-at-120-mph.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Audio</category>


<category domain="http://www.sixapart.com/ns/types#tag">korg</category>

<category domain="http://www.sixapart.com/ns/types#tag">music</category>

<category domain="http://www.sixapart.com/ns/types#tag">performance</category>

<pubDate>Mon, 29 Sep 2008 18:07:14 -0800</pubDate>
</item>

<item>
<title>Waikiki Apple Store Grand Opening</title>
<author>
<name>Todd Ogasawara</name><uri>http://ogasawalrus.com/</uri>
</author>
<description><![CDATA[<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/applewaikikitshirt.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/applewaikikitshirt.jpg" alt="applewaikikitshirt.jpg" title="Click to enlarge" width="148"/></a></div>
Honolulu's third Apple Store opened this morning. The newest Apple Store is in the heart of Waikiki in the <a href="http://www.royalhawaiiancenter.com/">Royal Hawaiian <s>Shopping</s> Center</a>.  Traffic near there was nutty this morning. So, I bypassed it and got metered parking along the beach.

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/applestorewaikikientrance.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/applestorewaikikientrance.jpg" alt="applestorewaikikientrance.jpg" title="Click to enlarge" width="148"/></a></div><br />
Couple of trivia items. First, this is the only Apple Store in Honolulu that does not have free parking. That probably explains why they still had t-shirts available even though I actually arrived after the doors had opened. Second, this is the only Apple Store in Honolulu that fronts a street. The other two are in the inner part of the shopping malls.</p>

<p><br />
<object width="400" height="300">	<param name="allowfullscreen" value="true" />	<param name="allowscriptaccess" value="always" />	<param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=1829099&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" />	<embed src="http://vimeo.com/moogaloop.swf?clip_id=1829099&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="300"></embed></object><br /><a href="http://vimeo.com/1829099?pg=embed&amp;sec=1829099">Waikiki Apple Store grand opening</a> from <a href="http://vimeo.com/user351442?pg=embed&amp;sec=1829099">Todd Ogasawara</a> on <a href="http://vimeo.com?pg=embed&amp;sec=1829099">Vimeo</a>.<br />
Please accept my usual apology for my "Blair Witch" style video. And, FYI, footage near the Apple Store starts at 1:21 if you want to skip footage of my walk through the Waikiki beach area.</p>

<p>A friend of mine, Ryan Ozawa, was at the store before dawn. He took a lot of great photos. You can find his photos linked to the sample photo below.<br />
<a href="http://flickr.com/photos/hawaii/"><img src="http://farm4.static.flickr.com/3135/2893133320_12b300843a.jpg?v=0"></a></p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/waikiki-apple-store-grand-open.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/waikiki-apple-store-grand-open.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Mac</category>


<category domain="http://www.sixapart.com/ns/types#tag">apple store</category>

<category domain="http://www.sixapart.com/ns/types#tag">hawaii</category>

<category domain="http://www.sixapart.com/ns/types#tag">waikiki</category>

<pubDate>Sat, 27 Sep 2008 19:42:01 -0800</pubDate>
</item>

<item>
<title>Katie Rose in Chiaroscuro</title>
<author>
<name>Harold Davis</name><uri>http://www.digitalfieldguide.com/blog/</uri>
</author>
<description><![CDATA[<p><a href="http://www.digitalfieldguide.com/blog/1371">Katie Rose</a> was sleeping upstairs. The room was dark, except for a low-watt lamp that illuminated part of her face. I shot this handheld, high ISO (ISO 1,600) photo in low light conditions to take advantage of the wonderful chiaroscuro light (not to mention the angelic baby).</p>

<p>Chiaroscuro refers to a lighting situation in which there is an extreme contrast between light and dark areas.</p>

<p><a href="http://www.flickr.com/photos/harold_davis/2885684529/" title="Katie Rose in Chiaroscuro"><img src="http://farm4.static.flickr.com/3228/2885684529_f16b9bea42.jpg" class="flickr-photo" alt="Katie Rose in Chiaroscuro" /></a><br />
<br /><br />
<font size="0.8em"> <a href="http://www.flickr.com/photos/harold_davis/2885684529/">Katie Rose in Chiaroscuro</a>, photo by <a href="http://www.flickr.com/photos/harold_davis/">Harold Davis</a>. View <a href="http://farm4.static.flickr.com/3228/2885684529_f16b9bea42_b.jpg">this image larger</a>.</font></p>

<p>In Adobe Camera Raw (ACR), I made several passes on the RAW file to exaggerate the chiaroscuro effect. I combined these different exposures from the same RAW file in Photoshop as layers.</p>

<p>It would have been pretty easy to process the noise out of this high ISO image. In fact, I made no effort to process the noise inherent in the photo. Instead, I converted the noise to simuated film grain using the NIK filter set. Next, I partially converted the image to black and white, using two Photoshop black and white adjustment layers, one set to maximum white and the other to maximum black. The point of the multiple black and white adjustment layers was to partially desaturate parts of the photo while continuing the chiaroscuro.</p>

<p>[Nikon D300, 18-200mm VR zoom lens (with image stabilization engaged) at 105mm (157.5mm in 35mm terms), 1/25 of a second at f/5.6 and ISO 1600.]<br />
</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/katie-rose-in-chiaroscuro.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/katie-rose-in-chiaroscuro.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Photography</category>


<category domain="http://www.sixapart.com/ns/types#tag">chiaroscuro</category>

<category domain="http://www.sixapart.com/ns/types#tag">grain</category>

<category domain="http://www.sixapart.com/ns/types#tag">high ISO</category>

<pubDate>Sat, 27 Sep 2008 10:26:40 -0800</pubDate>
</item>

<item>
<title>Skin Your Synth (etc.)</title>
<author>
<name>David Battino</name><uri>http://digitalmedia.oreilly.com/pub/au/2032</uri>
</author>
<description><![CDATA[<p>I have exactly one <a href="http://blogs.oreilly.com/digitalmedia/2008/08/kaossilator-4-bar-loop-hack.html" target="_blank">yellow musical instrument</a>, and since the moment I unboxed it, I've dreamed about somehow painting it a different color without damaging the controls. Now comes something much slicker.<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/Kaossilator-StyleFlip.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/Kaossilator-StyleFlip.jpg" alt="Kaossilator StyleFlip skin" title="Click to enlarge" width="148"/></a></div></p>

<p>At <a href="http://www.StyleFlip.com" target="_blank">StyleFlip.com</a>, you can design your own adhesive vinyl skin for a variety of music gear &#8212; turntables, CD players, DJ mixers, drum machines, keyboards and more. (The company says the skins are removable and leave no residue.) The site's Flash-based interface is easy to suss out, and the previews look dramatic. </p>

<p>I stopped short of buying a sticker, as it seemed rather pricey, but I was impressed that a StyleFlip rep called me personally within minutes to answer a technical question I'd emailed.</p>

<p>With so many mass-produced instruments out there, it's great to have an easy way to add some personality. Sure, it's only skin-deep, but even small customizations can change the way you feel about your instruments, deepening your music.</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/skin-your-synth-etc.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/skin-your-synth-etc.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Audio</category>


<category domain="http://www.sixapart.com/ns/types#tag">design</category>

<category domain="http://www.sixapart.com/ns/types#tag">graphics</category>

<category domain="http://www.sixapart.com/ns/types#tag">synthesizers</category>

<pubDate>Fri, 26 Sep 2008 11:50:25 -0800</pubDate>
</item>

<item>
<title>Canon 5D Mark II &#8212; The Coolest Video</title>
<author>
<name>Rick Sammon</name><uri>http://www.oreillynet.com/pub/au/3255</uri>
</author>
<description><![CDATA[<p>Hey All</p>

<p>You gotta see <a href="http://www.usa.canon.com/dlc/controller?act=GetArticleAct&articleID=2086">this</a>.  </p>

<p>How totally cool! Vincent is the man. I will be adding Canon 5D workshops (shooting and editing) to my 2009 <a href="http://www.ricksammon.com/Workshops_Seminars.html">schedule</a>. Hope you can make one!</p>

<p>Rick<br />
</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/canon-5d-mark-ii---the-coolest.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/canon-5d-mark-ii---the-coolest.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Photography</category>


<category domain="http://www.sixapart.com/ns/types#tag">Canon 5D Mark II</category>

<category domain="http://www.sixapart.com/ns/types#tag">digital photography</category>

<category domain="http://www.sixapart.com/ns/types#tag">digital SLRs</category>

<category domain="http://www.sixapart.com/ns/types#tag">HD</category>

<category domain="http://www.sixapart.com/ns/types#tag">HD still/video</category>

<pubDate>Thu, 25 Sep 2008 14:53:54 -0800</pubDate>
</item>

<item>
<title>How Important is a Caption?</title>
<author>
<name>Rick Sammon</name><uri>http://www.oreillynet.com/pub/au/3255</uri>
</author>
<description><![CDATA[<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/vf5.jpg" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/vf5.jpg" alt="vf5.jpg" title="Click to enlarge" width="148"/></a></div>

<p>In talking about the important of a caption for photograph, my friend Dick Zakia, author of <a href="http://www.amazon.com/Perception-Imaging-Third-Photography-Seeing/dp/0240809300/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222300439&sr=1-1">Perception and Imaging</a>, sent me this short story:</p>

<p>Blind man with no legs is sitting in a park begging.   </p>

<p>Sign beside him reads,  "Have Compassion.  I am blind."  People walk by and pretty much ignore the man, sign and hat for the coins.</p>

<p>A well-dressed businessman walks past him then turns around, stands in front of the man.  He picks up the sign, writes something on the back and places the sign back where it was but with what he wrote showing.</p>

<p>People continue to walk by but now are dropping coins and bills into the hat.  The blind man is thrilled and collects the coin.</p>

<p>The businessman returns and the blind man inquires as to what he wrote on the sign.  The businessman replies, "Today is a beautiful day and I cannot see it."<br />
--------<br />
Dick, a former RIT professor, adds: "I always reminded my students that a caption is<br />
part of the photograph, part of the gestalt--just as the choice of mat and<br />
frame, and the size of the print and the surface of the paper, etc."</p>

<p>Comments? Post here!</p>

<p>And, if you have a caption for my photograph of a man I photographed in Hong Kong, which is one of my favorites in my new book,<a href="http://www.amazon.com/Face-Sammons-Complete-Photographing-People/dp/059651574X/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1222300796&sr=1-1"> Face to Face,</a> send that, too!</p>

<p>Thank you,<br />
Rick</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/how-important-is-a-caption.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/how-important-is-a-caption.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Photography</category>

<category domain="http://www.sixapart.com/ns/types#category">Photography</category>


<category domain="http://www.sixapart.com/ns/types#tag">digital photogrpahy</category>

<category domain="http://www.sixapart.com/ns/types#tag">photogrpahy</category>

<pubDate>Wed, 24 Sep 2008 16:50:34 -0800</pubDate>
</item>

<item>
<title>LightZone 3.6 Basic Edition: A Photo Experimentation Tool</title>
<author>
<name>Todd Ogasawara</name><uri>http://ogasawalrus.com/</uri>
</author>
<description><![CDATA[<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_browser.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_browser.png" alt="lightzone_browser.png" title="Click to enlarge" width="148"/></a></div><br />
<a href="http://www.lightcrafts.com/products/">LightZone 3.6 Basic Edition</a> from Light Crafts is a $129.95 photo processing application. I bought it as part of the recent <a href="http://mupromo.com/">MacUpdate Promo Bundle</a> for $49.95 (for the entire bundle). Light Craft also produces what they call a Full edition that permits multi-image editing and batch processing. I've been pretty happy using <a hre"http://www.pixelmator.com/">Pixelmater</a> and the Open Source The GIMP image editors. So, I wasn't sure I needed or wanted to add another image editor to my toolkit. However, since it came as part of the bundle, I decided to take a look at LightZone and I'm glad I did now.</p>

<p>The browser has, perhaps, the simplest and easiest to use navigation system I've seen on a Mac. It basically shows you the top of the directory tree and lets you drill down to where you want to go without much effort. I was able to quickly browse through large thumbnails of JPG, PNG, and RAW image files. The RAW photos were created using either a Canon PowerShot G3 or G9.</p>

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_editor.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_editor.png" alt="lightzone_editor.png" title="Click to enlarge" width="148"/></a></div><br />
The editor view is well laid out with the preset Styles in the left menu bar and modifications for each setting in the right menu bar. I suspect, though, that LightZone is one of those apps where I can do 90% of what I need knowing only 10% (or less) of what the application can actually do. Here are the few things that I did need to know about its interface. The thumbnail at the top left provides a quick preview of a Style without actually committing the chagne. The thumbnail at the top right that shows zone areas can also display color mask, histogram, and what they call Sampler information. Sampler provides information about the specific pixel under the cursor: XY position, RGB color, saturation, etc. The right sidebar builds control panels as you apply each style. The interesting thing here is that you can adjust any of the applied style independent of when each one was applied. This is quite different from the other editors that require you undo the most recent changes before going back to a previous modificiation type.</p>

<p>The Orig button in the top menu bar shows the original image before any Style changes were applied. And, speaking of the original image, it is important to note that LightZone never changes the original file. The modified image is saved out to a new file with a _lzn appended to the part of the file name that precedes a period. For example, if you brought in a photo from your camera named IMG_1234.JPG, LightZone would save the modified file to IMG_1234_lzn.JPG.</p>

<p>Here are a few photos I used to learn more about LightZone.</p>

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_candy.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_candy.png" alt="lightzone_candy.png" title="Click to enlarge" width="148"/></a></div><br />
The candy was photographed without removing the plastic cover. The blurred bands at the top and bottom are the frosted part of the plastic cover. I used this to learn the different ways LightZone could emphasize colors.</p>

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_treebark.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_treebark.png" alt="lightzone_treebark.png" title="Click to enlarge" width="148"/></a></div><br />
I though the tree bark should more textured and 3D. So, I used this photo to learn more about LightZone's sharpening and dynamic range styles.</p>

<p><br />
<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_rabbit.png" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/lightzone_rabbit.png" alt="lightzone_rabbit.png" title="Click to enlarge" width="148"/></a></div><br />
I neglected to turn on my flash for this photo of my daughter's rabbit. So, I used it when playing with LightZone's dynamic range and color tone styles to try to correct it a bit.</p>

<p><br />
The main thing I learned is that LightZone does not "compete" with my other tools (Pixelmator or The GIMP). It probably doesn't do anything I couldn't do with Pixelmator or GIMP. But, its relighting tool and various Styles let me quickly experiment with the look of each photo. Each single change in LightZone probably would have required a dozen individual tweaks in my other photo editing tools. I'm still using Pixelmator and The GIMP for day-to-day photo tweaks and screen capture manipulation for my various blogging/writing projects. But, LightZone is the tool I'm probably going to turn to when I want to figure out how to make a photo look the way I remember a scene (or to improve on it). I don't use Apple Aperture or Adobe Lightroom. But, I suspect users of those photo management apps might want to give LightZone a try too.</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/lightzone-36-photo-experiement.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/lightzone-36-photo-experiement.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Mac</category>


<category domain="http://www.sixapart.com/ns/types#tag">editor</category>

<category domain="http://www.sixapart.com/ns/types#tag">Photography</category>

<pubDate>Wed, 24 Sep 2008 04:00:00 -0800</pubDate>
</item>

<item>
<title>Firefox 3.0.2 Fixes Three Mac Specific Issues</title>
<author>
<name>Todd Ogasawara</name><uri>http://ogasawalrus.com/</uri>
</author>
<description><![CDATA[<p>Firefox notified me that it had updated itself to version 3.0.2 and wanted to be restarted. So, I took a look at the <a href="http://en-us.www.mozilla.com/en-US/firefox/3.0.2/releasenotes/">3.0.2 release notes</a> and found it had several Mac specific fixes. Here's the language from the release notes:</p>

<p>Fixed Mac-specific issues:<br />
- Keyboard shortcuts would stop working in some cases.<br />
- Japanese, Korean, Chinese and Indic characters can not be entered (using IME) into text fields in Flash objects (bug 357670)<br />
- Firefox 3.0.1 could not be used when the user profile is stored on an AFP directory (bug 417037)<br />
</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/firefox-302-fixes-three-mac-sp.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/firefox-302-fixes-three-mac-sp.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Mac</category>


<category domain="http://www.sixapart.com/ns/types#tag">firefox</category>

<pubDate>Tue, 23 Sep 2008 23:15:09 -0800</pubDate>
</item>

<item>
<title>Between Earth and Sky</title>
<author>
<name>Harold Davis</name><uri>http://www.digitalfieldguide.com/blog/</uri>
</author>
<description><![CDATA[<p>On our way home from a <a href="http://www.digitalfieldguide.com/blog/1388">sunset-to-night hike</a> on the <a href="http://www.digitalfieldguide.com/blog/804">Tomales Point</a> fork of Point Reyes, <a href="http://www.digitalfieldguide.com/blog/851">Mark</a> and I stopped at the wreck of the <a href="http://www.digitalfieldguide.com/blog/1207">Point Reyes fishing trawler</a>. Many people like to photograph this <a href="http://www.digitalfieldguide.com/blog/1222">trawler</a>, which is easily accessible outside of Inverness, California.</p>

<p><br />
<a href="http://www.flickr.com/photos/harold_davis/2879368059/" title="Between Earth and Sky"><img src="http://farm4.static.flickr.com/3193/2879368059_520ab852b1.jpg" class="flickr-photo" alt="Between Earth and Sky" /></a></p>

<p><font size="0.8em"> <a href="http://www.flickr.com/photos/harold_davis/2879368059/">Between Earth and Sky</a>, photo by <a href="http://www.flickr.com/photos/harold_davis/">Harold Davis</a>. View <a href="http://farm4.static.flickr.com/3193/2879368059_520ab852b1_b.jpg">this image larger</a>.</font></p>

<p>The week before, at my <a href="http://www.digitalfieldguide.com/blog/1380">Point Reyes night photography workshop</a>, I'd been stymied in my idea of <a href="http://www.digitalfieldguide.com/blog/1367">stacking photos to produce circular star trails</a> (stymied because <a href="http://www.digitalfieldguide.com/blog/1383">it was cloudy</a>). But this time it was clear. The stars were bright, although a little less than on Tomales Point, probably because of the ambient light pollution.</p>

<p>I pointed the camera north, and used a digital fisheye lens to maximize the celestial rotation of the star trails.</p>

<p>First I tested the light with a one minute exposure at ISO 800 at f/3.5. Then I made an eight minute ISO 100 exposure (with in-camera long exposure noise reduction enabled) for the foreground. This image in its entirety is found below (I think it is interesting in its own right, with the still stars at the center and circular star trails around the edges).</p>

<p>Next, I turned noise reduction off, and programmed my <a href="http://www.digitalfieldguide.com/blog/839">Nikon MC-36 remote</a> for twenty exposures, each capture at four minutes, ISO 100, and f/5.6.</p>

<p>It was damp and a bit chilly in the dark, and for a while Mark and I left my camera on autopilot and sat some distance away in my car, listening to the superb and eerie music of <a href="http://www.amazon.com/exec/obidos/ISBN=B000UMQDHC/bearhomecom/" target="_new">Alison Krauss and Robert Plant</a>. After twelve exposures (about 48 minutes) our patience wore out and weariness won. Mark had a plane to catch in the morning for a business meeting, and I've been going on fumes since <a href="http://www.digitalfieldguide.com/blog/1265">Katie Rose was born</a>. I stopped the automated exposure process, and packed it in.</p>

<p>This morning, I combined the thirteen images in Photoshop using the Statistics script, choosing Maximum as the method for combination. An airplane trail in one of the captures made it into the stack, and I decided to keep this apparent visual anomaly. Finally, I layered in the longer exposure for the detail in the foreground and boat.</p>

<p>[Above: Thirteen captures, all captures Nikon D300, 10.5mm digital fisheye, tripod mounted; one capture 8 minutes at f/3.5 and ISO 100; twelve captures 4 minutes at f/5.6 and ISO 100; star trails created by statistical stacking of 13 exposures; foreground created by layer with the 8 minute exposure using a gradient and layer mask. Below: Nikon D300, 10.5mm digital fisheye, 8 minutes at f/3.5 and ISO 100, tripod mounted.]</p>

<p><a href="http://www.flickr.com/photos/harold_davis/2879194095/" title="Point Reyes Trawler at Eight by Harold Davis, on Flickr"><img src="http://farm4.static.flickr.com/3207/2879194095_f3117b62e4.jpg" width="500" height="332" alt="Point Reyes Trawler at Eight" /></a></p>

<p>View <a href="http://farm4.static.flickr.com/3207/2879194095_f3117b62e4_b.jpg">this image larger</a>.</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/between-earth-and-sky.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/between-earth-and-sky.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Photography</category>


<category domain="http://www.sixapart.com/ns/types#tag">night photography</category>

<category domain="http://www.sixapart.com/ns/types#tag">stacking</category>

<category domain="http://www.sixapart.com/ns/types#tag">star trails</category>

<category domain="http://www.sixapart.com/ns/types#tag">statistics</category>

<pubDate>Tue, 23 Sep 2008 16:48:17 -0800</pubDate>
</item>

<item>
<title>Photoshop CS4 - Elegant Engineering</title>
<author>
<name>Derrick Story</name><uri>http://www.oreillynet.com/pub/au/54</uri>
</author>
<description><![CDATA[<p>I'm sitting here with the official <em>Reviewer's Guide</em> for Photoshop CS4, and application that has been my constant companion for the last three months. As I'm flipping through the guide, I'm thinking, <em>"Oh, yeah, that's nice. And yes, I like that too."</em> But it doesn't get to the heart of this application.</p>

<p>And this version has heart. It's not often in the world of software that we get to enjoy something so complicated and refined at the same time. Working in CS4 is like driving a top-tier German sports car. It's responsive, elegant, handsome, and yes, very enjoyable. </p>

<p>But that's not an easy pitch for software in today's economy. You can't just put <em>"CS4 Is Friggin' Remarkable"</em> on a bumper sticker to make it a hit. You actually have to use it, and I mean use all of it: Photo Downloader, Bridge, ACR, and Photoshop. They work together like gears and pistons.</p>

<p>I'll be specific about some of these joys:</p>

<ul>
<li>When you make your first Collection in Bridge, you'll smile.</li>
<li>When you discover the Graduated Filter tool in ACR, you'll want to show your friends.</li>
<li>You'll become addicted to Open GL zooming and rotating.</li>
<li>The first time you use the Targeted Adjustment tool in a Curves layer that CS4 created automatically for you, you'll feel like an expert.</li>
<li>And if you don't try the new Auto Align and Auto Merge technologies, you're missing a true technology treat.</li>
</ul>

<div class="ap_r"><a href="http://blogs.oreilly.com/digitalmedia/upload/2008/09/psc_cover_for_web.gif" class="highslide" onclick="return hs.expand(this)"><img src="http://blogs.oreilly.com/digitalmedia/upload/2008/09/psc_cover_for_web.gif" alt="psc_cover_for_web.gif" title="Click to enlarge" width="148"/></a></div>

<p>So there's a mere scratching of my CS4 surface. You can learn more about this release in many ways. I'd start with a few including Deke's latest dekePod, <a href="http://digitalmedia.oreilly.com/2008/09/23/dekepod-buy-or-die.html" target="_blank">Buy or Die: Photoshop CS4</a> and my podcast, <a href="http://www.thedigitalstory.com/blog/2008/09/top_10_photoshop_cs4.html" target="_blank">Top 10 Photoshop CS4 Features</a>.</p>

<p>And then there's my pride and joy, the book that covers my Photoshop CS4 approach <em>just for photographers</em> and no one else: <a href="http://oreilly.com/catalog/9780596521936/index.html#top" target="_blank">The Photoshop CS4 Companion for Photographers</a>. If you read this book, you'll see why I'm so excited about this release of Photoshop.</p>]]></description>
<link>http://blogs.oreilly.com/digitalmedia/2008/09/photoshop-cs4---elegant-engine.html</link>
<guid>http://blogs.oreilly.com/digitalmedia/2008/09/photoshop-cs4---elegant-engine.html</guid>

<category domain="http://www.sixapart.com/ns/types#category">Photography</category>


<category domain="http://www.sixapart.com/ns/types#tag">adobe</category>

<category domain="http://www.sixapart.com/ns/types#tag">photoshop cs4</category>

<pubDate>Tue, 23 Sep 2008 10:53:29 -0800</pubDate>
</item>

</channel>
</rss>