<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6000509243771454610</id><updated>2011-07-30T16:14:21.635-07:00</updated><title type='text'>Content Inside</title><subtitle type='html'>Thoughts from the trenches of content creation. What we deal with as we try and make engaging content for over a million visitors a year.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>27</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-1620925561192667553</id><published>2011-01-21T13:31:00.000-08:00</published><updated>2011-01-21T13:32:08.525-08:00</updated><title type='text'>The geek in me loves this stuff</title><content type='html'>&lt;div&gt;Well not quite remote control but I love viewing a video, approving it, then having a server somewhere else take the source file, render it for distribution, then copy it to a folder on the network all because of a workflow I designed.&lt;/div&gt;&lt;div&gt;I&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-1620925561192667553?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/1620925561192667553/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=1620925561192667553' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/1620925561192667553'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/1620925561192667553'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2011/01/geek-in-me-loves-this-stuff.html' title='The geek in me loves this stuff'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-9104221283470325600</id><published>2010-03-02T15:46:00.001-08:00</published><updated>2010-03-02T15:49:11.928-08:00</updated><title type='text'>Things I'd like to steal</title><content type='html'>Yep, I'd love to steal this idea for an application on our website, but something tells me we don't even have a fraction of the money to do anything with the stolen idea.&lt;br /&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;a href="http://vimeo.com/9194146"&gt;Crazy vimeo salsa take over the page video&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-9104221283470325600?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/9104221283470325600/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=9104221283470325600' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/9104221283470325600'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/9104221283470325600'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2010/03/things-i-like-to-steal.html' title='Things I&amp;#39;d like to steal'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-2680202095431332418</id><published>2009-09-22T08:58:00.001-07:00</published><updated>2009-09-22T11:21:13.774-07:00</updated><title type='text'>It's a conversation, not a service</title><content type='html'>We're getting ready to launch our Arctic Questions (poor name I know, but what can I say, working title becomes title) exhibit and I'm starting to field a lot of questions about it.&lt;br /&gt;&lt;br /&gt;A partner recently asked me about Questions exhibit, which is basically a message board or forum that is on the exhibit floor, presented beautifully and linked to the web and iphone.&lt;br /&gt;&lt;br /&gt;It's a neat implementation of some pretty standard technology, but as far as I know, no one has really done it this way in a gallery before.&lt;br /&gt;&lt;br /&gt;Anyway, this partner asked me whether or not someone from the Aquarium would be on this board to answer the questions. The answer is "sort of". But the real thing is the way in which this person was looking at this exhibit. They were looking at it as a service. The Aquarium would provide a service for answering questions. And that's not really true. The Aquarium would provide a platform. A place where, if all goes well, discussions happen and these discussions answer questions, solve problems, or serve as a steam release system.&lt;br /&gt;&lt;br /&gt;So my take away was that I didn't just have to explain that the crowd was going to answer questions, I had to explain the underlying concept and change the POV that our exhibit was a service.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-2680202095431332418?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/2680202095431332418/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=2680202095431332418' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/2680202095431332418'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/2680202095431332418'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/09/its-conversation-not-service.html' title='It&apos;s a conversation, not a service'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-355080863919574628</id><published>2009-08-25T20:17:00.000-07:00</published><updated>2009-08-25T20:37:25.911-07:00</updated><title type='text'>Please step away from the camera</title><content type='html'>The thing about this whole social media thing, is that people who do not understand media, but understand social, have convinced the world in general that everyone, given a chance, is a great storyteller.&lt;br /&gt;&lt;br /&gt;This is simply not true. Most people are terrible storytellers. Most social media is not insignificantly awful, it is awful at a very significant level.&lt;br /&gt;&lt;br /&gt;Cheap cameras are now really cheap and the refrain of citizen journalism floats on the wind. This is a very dangerous situation. It leads to temptation, the temptation to buy cheap cameras and send them to citizens. It's like that deal where you park illegally for just a second while you run into the store, you know you could get burned with a ticket but you take the risk anyways because you can save a few cents.&lt;br /&gt;&lt;br /&gt;You get the ticket and you owe forty bucks. Same with cameras.&lt;br /&gt;&lt;br /&gt;Faced with a massive budget and the denial of that budget, we tried to cheat things by sending cheap cameras to people to record the stories for us. We did the pre-interviews. We prepared training documents, and we hoped we wouldn't get caught. We got caught.&lt;br /&gt;&lt;br /&gt;I'd give our attempt a 30% success rate. With work, 30% of the footage will be usable, the rest, not so much.&lt;br /&gt;&lt;br /&gt;The people we sent the cameras to appeared to try very hard to do a good job, but the truth of it is that you can't replace professional storytellers with a canon in a pelican case and 3 sheets of instructions.&lt;br /&gt;&lt;br /&gt;And I'm thankful for the work they did for us, and I think for some, if we'd keep sending them cameras they'd get better and better as they learn the craft, but then that's kind of like training professionals isn't it?&lt;br /&gt;&lt;br /&gt;I equate what we tried to do with many social media efforts, same idea, pros aren't needed when amateurs, or neverteurs are willing.&lt;br /&gt;&lt;br /&gt;1. Social media only works because you don't expect it to do anything other than whatever it wants to. Once you have expectations, then you are doomed.&lt;br /&gt;&lt;br /&gt;2. Social media only works because with 8 billion people an hour submitting videos to youtube an hour, 1 or 2 of them are going to be naturally gifted, or uniquely strange enough to draw eyeballs.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-355080863919574628?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/355080863919574628/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=355080863919574628' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/355080863919574628'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/355080863919574628'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/08/please-step-away-from-camera.html' title='Please step away from the camera'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-7806697076489001595</id><published>2009-08-17T15:27:00.001-07:00</published><updated>2009-08-17T15:27:03.011-07:00</updated><title type='text'>Are Screens Killing Museums?</title><content type='html'>&lt;a href="http://blog.orselli.net/2009/08/are-screens-killing-museums.html"&gt;Are Screens Killing Museums?&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Shared via &lt;a href="http://addthis.com"&gt;AddThis&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;I don't really think I agree with this post but it is something worth thinking about. Even though we support 45, soon to be 60 screens, not all of them are used properly. We're moving to fix that.&lt;br /&gt;&lt;br /&gt;There is a lot of bad screen design everywhere you look (not in our place heh). Screens are put up with 10 minute long videos on them. Screens are loaded with text. Screens have amazingly primitive, straight out dumb games put on them so they appear interactive and it is wrong and nobody benefits.&lt;br /&gt;&lt;br /&gt;It's like a checklist approach to digital design. People that do no know what they are doing watch TV, so they think they know how screens work. People that design for screens, want to be getting credits in TV so they build for TV. Both groups lead people down the wrong path.&lt;br /&gt;&lt;br /&gt;The checklist comes in when they look at the exhibit and they say we want some interactive stuff and we want screens, screens are great, we'll put lots of info on them.&lt;br /&gt;&lt;br /&gt;So then they get some games, or some standard button pushing, and check, they have their interactive. They get some five minute profiles, or talking head interviews, and they are delivering a whole lot of info through their 65 inch plasma. Check and check, interactive and lots of info. Everyone gets a commemorative mug and a hug. Job well done.&lt;br /&gt;&lt;br /&gt;Their checklist has led them astray. Their is no accounting for visitor interaction and visitor satisfaction. They built for a spec sheet checklist instead of a visitor experience. Screens will always fail under that approach&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-7806697076489001595?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/7806697076489001595/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=7806697076489001595' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7806697076489001595'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7806697076489001595'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/08/are-screens-killing-museums.html' title='Are Screens Killing Museums?'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-4503411943545573960</id><published>2009-08-15T17:55:00.000-07:00</published><updated>2009-08-15T17:59:56.298-07:00</updated><title type='text'>How to make video play smoothly on video wall</title><content type='html'>Well I think I finally cracked it. Forty plus renders down the line it's a good old-fashioned codec that saves the day.&lt;br /&gt;I've been struggling to get video to run smoothly on our quad screen setup. It has been dropping about half the frames. It turns out that good ole MPEG 2 is the winner for rendering 2560x1440 smoothly at 30 frames.&lt;br /&gt;&lt;br /&gt;Everyone just scales 1080p, but I don't want to do that. We're compositing a bunch of photos with the video and I don't want them scaled I want them at 1:1 pixel mapping. It's really quite dramatic.&lt;br /&gt;&lt;br /&gt;I was starting to feel like there is a reason that nobody does it that way, the reason being that it doesn't work. But now I know it works with MPEG2. 35megabit MPEG2 works like a charm.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-4503411943545573960?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/4503411943545573960/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=4503411943545573960' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/4503411943545573960'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/4503411943545573960'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/08/how-to-make-video-play-smoothly-on.html' title='How to make video play smoothly on video wall'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-7767448342179073166</id><published>2009-08-12T15:07:00.001-07:00</published><updated>2009-08-12T15:07:51.006-07:00</updated><title type='text'>setting up a matrox m9120 card and video wall</title><content type='html'>This wall is going in our Arctic exhibit, and if I deliver on promises it will look very good. The catch is I have to deliver on promises.&lt;br /&gt;&lt;br /&gt;There are so many numbers in making this work optimally that it hurts my brain.&lt;br /&gt;&lt;br /&gt;Screens are 1366x768&lt;br /&gt;Card can drive 4 screens but can't drive the native resolution of 1366x768&lt;br /&gt;Card can drive the screens at 1360x768 and the screens look good&lt;br /&gt;Total screen resolution is 2720x1536&lt;br /&gt;Video resolution is 1280x720&lt;br /&gt;Total video resolution is 2560x1440&lt;br /&gt;So what should the digital signage software drive things at? 2720x1536 or 2560x1440?&lt;br /&gt;I can't get four streams of video to run in sync and I don't want to scale a single 1080p stream so that leaves me with building probably a 2560x1440 stream and having something somewhere along the way scale it. It's nasty.&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-7767448342179073166?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/7767448342179073166/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=7767448342179073166' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7767448342179073166'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7767448342179073166'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/08/setting-up-matrox-m9120-card-and-video.html' title='setting up a matrox m9120 card and video wall'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-6581419300536251977</id><published>2009-07-29T15:16:00.001-07:00</published><updated>2009-07-29T15:16:32.582-07:00</updated><title type='text'>RFP's, multi-touch and a building full of beasts</title><content type='html'>It just doesn't stop. We have two multi-touch tables in development. A major quad HD screen, 3 interactive kiosks, 2 RFP's out, a digital signage software review, a new 4d theater, a new harbour porpoise, a xserve with final cut server that is out of space and it is 34 degrees out. &lt;br /&gt;And I've been here since 4:30am and should really go home.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-6581419300536251977?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/6581419300536251977/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=6581419300536251977' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/6581419300536251977'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/6581419300536251977'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/07/rfp-multi-touch-and-building-full-of.html' title='RFP&amp;#39;s, multi-touch and a building full of beasts'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-2693806047475924620</id><published>2009-01-06T15:56:00.001-08:00</published><updated>2009-01-06T15:57:17.939-08:00</updated><title type='text'>server woes solved</title><content type='html'>Well courtesy of the Apple support discussions I have an answer.&lt;br /&gt;It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.&lt;br /&gt;&lt;br /&gt;So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-2693806047475924620?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/2693806047475924620/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=2693806047475924620' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/2693806047475924620'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/2693806047475924620'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/01/server-woes-solved_06.html' title='server woes solved'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-3335568969943060061</id><published>2009-01-06T15:56:00.000-08:00</published><updated>2009-01-06T15:57:03.949-08:00</updated><title type='text'>server woes solved</title><content type='html'>Well courtesy of the Apple support discussions I have an answer.&lt;br /&gt;It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.&lt;br /&gt;&lt;br /&gt;So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-3335568969943060061?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/3335568969943060061/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=3335568969943060061' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/3335568969943060061'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/3335568969943060061'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/01/server-woes-solved.html' title='server woes solved'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-7692094864701766482</id><published>2009-01-06T15:52:00.001-08:00</published><updated>2009-01-06T15:56:34.924-08:00</updated><title type='text'>Server, Final Cut Server, Drobo woes solved</title><content type='html'>Well courtesy of the Apple support discussions I have an answer.&lt;br /&gt;It turns out we had a power failure in which the server was protected but the drobo went down. That means it was not unmounted correctly which means OS X created a volume, with the drobo name on it on the system drive and started filling it up with footage that I was trying to archive.&lt;br /&gt;&lt;br /&gt;So restored all that footage courtesy of a file list provided by IS, then they deleted that folder and renamed the drobo drive that had the appended name. Now all is well.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-7692094864701766482?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/7692094864701766482/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=7692094864701766482' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7692094864701766482'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7692094864701766482'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/01/server-final-cut-server-drobo-woes.html' title='Server, Final Cut Server, Drobo woes solved'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-7139167690017482825</id><published>2009-01-05T11:36:00.001-08:00</published><updated>2009-01-05T11:39:54.196-08:00</updated><title type='text'>Arctic Strategy? Digital content plan? Nope, Server woes</title><content type='html'>Today was another of those days that I had blocked out for all kinds of creative strategy. But, first I figured I'd do a little Final Cut Server house-cleaning. All was well until about 150 error messages popped up on my screen. Much "okay" clicking ensued followed by a server check that shows the servers system drive is entirely full.&lt;br /&gt;&lt;br /&gt;Not a good thing.&lt;br /&gt;&lt;br /&gt;Whatever files are there are hidden and bad things have happened. Either it is a coincidence or FCSvr decided that the system drives was suddenly a great place to write files.&lt;br /&gt;&lt;br /&gt;It looks like OS X server doesn't index the system drive so searches are useless. First the snow, then the power failure, now the server "failure". Something doesn't want me to plan out 2009.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-7139167690017482825?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/7139167690017482825/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=7139167690017482825' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7139167690017482825'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/7139167690017482825'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2009/01/arctic-strategy-digital-content-plan.html' title='Arctic Strategy? Digital content plan? Nope, Server woes'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-9057111951668593912</id><published>2008-12-15T20:40:00.000-08:00</published><updated>2008-12-15T20:46:13.312-08:00</updated><title type='text'>How little things with Final Cut Server ruin your day</title><content type='html'>The day was going along pretty well today until I decided to do a small tweak on FCSvr.&lt;div&gt;I'm freeing up room on our expensive drives by archiving to cheap drives.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;That was going just fine. What happens is it copies the file from the main media drives, on to the archive device, checks that it is there, then deletes the file from the main media drive.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Worked like a charm until inexplicably it started refusing to delete from the main drive.  That's weird I thought. But then, considering who uploaded the video, I thought to myself "weird stuff always comes from his computer...probably his fault" &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;So as a nascent server admin I immediately blamed a user. It felt really good to do that. Unfortunately it didn't help me.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;So I updated the xserve to the lates pro-app and OS upgrade. The server hung during the update, so I pulled the power on it and plugged it back in. It's one of those moments where you pause and think to yourself, this will either work, or I won't see much of my family this week.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It worked. Still couldn't delete though.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Finally I called up the folders on the media drive and compared them to others and sure enough, the permissions weren't set right.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;FCSvr is an admin. admin did not have read/write permission on those rogue folders.  Problem solved. Change permissions and it works like a dream. Even better I still get to blame the user because they created the folders in the first place so it is probably their fault.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; Score.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-9057111951668593912?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/9057111951668593912/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=9057111951668593912' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/9057111951668593912'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/9057111951668593912'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/12/how-little-things-with-final-cut-server.html' title='How little things with Final Cut Server ruin your day'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-6959546798174135350</id><published>2008-12-15T20:37:00.000-08:00</published><updated>2008-12-15T20:40:11.764-08:00</updated><title type='text'>I used to just work on story</title><content type='html'>That used to be my gig, having good creative ideas and making them into entertaining stories. Now I do that, and I'm a server admin. Go figure. I'm about the most dangerous server admin you can get. &lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Updates without backup....check.&lt;/div&gt;&lt;div&gt;Just pushing the power button when hung...check&lt;/div&gt;&lt;div&gt;Blindly entering commands in terminal just because some website tells me so...check&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-6959546798174135350?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/6959546798174135350/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=6959546798174135350' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/6959546798174135350'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/6959546798174135350'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/12/i-used-to-just-work-on-story.html' title='I used to just work on story'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-8710641986990105184</id><published>2008-12-08T16:15:00.000-08:00</published><updated>2008-12-08T16:22:23.944-08:00</updated><title type='text'>Working with signage software</title><content type='html'>Even the name itself "signage software" should be enough to scare you away. "signage" ... what a terrible word.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The software is made to sell people things using moving pictures in waiting areas. Waiting for a bus, waiting for a plane, waiting to buy a bag of chips and a slurpee. The software is about as mundane and inspired as those places.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;If you want a nice stock ticker (because that's what busy people demand) and a brightly coloured billboard suggesting the soup and sandwich special at the "transportation station snack bar" then this software for you.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;This software is decidedly not for public galleries driven by an education and conservation mandate using HD footage.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It works but barely. Whatever you want to do, it will do, but it will make you work for it. Of all the things I want to time on, making presentation software work is not one of them.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Right now we have a touchscreen and a plasma running off of one computer. To get the touchscreen to update the plasma is pretty much impossible. I can do it in the omnivex (yeah I'm calling you out Omnivex) architecture but it's going to make me work for it. Basically it will take about 5-6 hours to set up, then every change thereafter will take about an hour. I don't want that. I want to be able to do it quickly. I want to be able to update often. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I want the ease of putting a 7 day weather report in there. Thankfully the software makes weather reports easy, unfortunately our cichlid exhibit is not currently in need of weather reports.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-8710641986990105184?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/8710641986990105184/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=8710641986990105184' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/8710641986990105184'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/8710641986990105184'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/12/working-with-signage-software.html' title='Working with signage software'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-4998679720070126936</id><published>2008-11-17T09:27:00.001-08:00</published><updated>2008-11-17T09:34:26.026-08:00</updated><title type='text'>Threads n' granules</title><content type='html'>Sounds like a great breakfast cereal but it's part of a strategy document I'm working on. It's all about multi-platform media development. I think a lot of places get this whole multi-platform thing wrong. They think that it means develop one item for multiple platforms. I think you have to develop many different items for many different platforms. It sounds onerous but if you build them all from the same source, ye olde threads n' granules, then you are okay.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Here's part of what I'm writing...&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;Traditional approach to multi-platform meant adapting TV for the web i.e.—distribution of “television-type” video content through media such as the web or gallery screens. The DCL is an evolution of that original idea that goes beyond by recognizing the variety of platforms available to us, the uniqueness of these platforms, and delivering custom content to each of those platforms. The custom content is not a force fit of one format into a different format; rather it is the ground up creation of specific content for specific platforms. Blog content is different from Youtube content, which is different from exhibit content and is different from media b-roll content but they all evolve from the same source media granules and messaging threads.  The outputs are multiplied but the work required to feed those outputs is not correspondingly increased because the work is done in parallel.&lt;/blockquote&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-4998679720070126936?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/4998679720070126936/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=4998679720070126936' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/4998679720070126936'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/4998679720070126936'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/11/threads-n-granules.html' title='Threads n&apos; granules'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-162470607176480682</id><published>2008-11-14T13:29:00.001-08:00</published><updated>2008-11-14T13:29:35.683-08:00</updated><title type='text'>So far Drobo = Love</title><content type='html'>We're out of room on our xraid. Too many media files. A new promise vtrack array will cost us somewhere in the area of 16k. &lt;br /&gt;I bought a little drobo with 4TB and droboshare for about $1600. The thought is we can delay our array purchase for another year if this works. &lt;br /&gt;&lt;br /&gt;The plan is to use the drobo as an archive device on Final Cut Server. Media that we don't access all that often will get archived to the drobo. We can still search for it in FCSvr and view the proxies, it's only when we retrieve it will it take a bit longer.&lt;br /&gt;&lt;br /&gt;I haven't tried it yet because I need IS to come up with a backup strategy in case something goes terribly wrong.&lt;br /&gt;&lt;br /&gt;The drobo, which is fully protected storage, has got to be one of the easiest installs I've ever done of any hardware. Seriously. No tools. Just slide the drives in, install the dashboard and away it goes.&lt;br /&gt;&lt;br /&gt;It's actually living on our network quite happily without any problems. So far I'm impressed.&lt;br /&gt;&lt;br /&gt;We're going to run it for a bit before we formally attach it to FCSvr.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-162470607176480682?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/162470607176480682/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=162470607176480682' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/162470607176480682'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/162470607176480682'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/11/so-far-drobo-love.html' title='So far Drobo = Love'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-5603381830812346500</id><published>2008-10-26T21:44:00.001-07:00</published><updated>2008-10-26T21:44:18.641-07:00</updated><title type='text'>What is the experience</title><content type='html'>Right now we do this in the big sense. We ask of our galleries what the big experience is. In each exhibit we kind of ask what the experience is. I don't know if we go all the way though. We think about the hook, the core messaging, and what "walk-away" success would be, but I don't know if we ever talk about the experience at that detail level.&lt;br /&gt;If someone plays with one of our interactives, or looks at our video wall, what do they experience?&lt;br /&gt;I can tell you what I hope they walk away with. Sometimes it's success if they walk away with even the lightest grasp on the challenges facing a certain animal. If it is a multi-layered message it can be great if they pick up any of the layers, as long as they get at least one. &lt;br /&gt;&lt;br /&gt;But when it comes to the experience they had at the spin-browser, or the experience they had the video-wall or the experience they had at one of the habitats, I don't know if we really put it all together to consider that. I think we should.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-5603381830812346500?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/5603381830812346500/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=5603381830812346500' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/5603381830812346500'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/5603381830812346500'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/10/what-is-experience.html' title='What is the experience'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-8229720553640481524</id><published>2008-10-25T17:01:00.001-07:00</published><updated>2008-10-25T17:01:51.070-07:00</updated><title type='text'>How to interview now with more text</title><content type='html'>Alternate sides of the camera you ask the questions from. Just keep switching sides every time you do an interview. When you edit you'll be able to cut between people on different sides of the frame instead of everyone stuck to the same side.&lt;br /&gt;&lt;br /&gt;Ask open ended questions for interesting responses.&lt;br /&gt;&lt;br /&gt;Do not ask any question that can be answered with a yes or no.&lt;br /&gt;&lt;br /&gt;Train the people to restate the question or answer in a complete sentence. Instead of "yeah Dave totally does that" you'll get "Dave is totally the guy that screws around on his girlfriends". Much better.&lt;br /&gt;&lt;br /&gt;Tape off or turn off your tally light so they don't know when you are recording.&lt;br /&gt;&lt;br /&gt;Wrap the interview, tell them you are done, physically relax then compliment them on something they said or say "i though you were going to talk about x, thank god you didn't". The trick is, the camera is still recording.&lt;br /&gt;Then they start talking in a super casual manner about all sorts of stuff in an amazingly relaxed tone. Some of the best clips ever come from that trick.&lt;br /&gt;&lt;br /&gt;Also just start rolling at the beginning, before you say lets get started. It's not so much about tricking people into saying bad things, as it is about tricking them into being relaxed and themselves in front of the camera.&lt;br /&gt;&lt;br /&gt;This is a stupid one, but listen. It's amazing how many don't listen, don't engage in a real conversation, and don't ask the follow-up question.&lt;br /&gt;&lt;br /&gt;People often hint at stories that they won't volunteer on their own, but will willingly give up if you ask them directly.&lt;br /&gt;&lt;br /&gt;Write your questions down. You don't need to stick to them, but at least you know where you came from and where you are going.&lt;br /&gt;&lt;br /&gt;Look them in the eye and be interested.&lt;br /&gt;&lt;br /&gt;Don't ever interrupt them.&lt;br /&gt;&lt;br /&gt;Let silence hang. Often they will jump in and fill the silence in an effort to make things less uncomfortable.&lt;br /&gt;&lt;br /&gt;Nod while talking to them, but don't say anything unless you need to. Their voice is important, not yours.&lt;br /&gt;&lt;br /&gt;Always encourage them that they are giving the best interview ever.&lt;br /&gt;&lt;br /&gt;If you aren't getting what you need, and you are trying to get something out of them, and you've been at it for awhile, and they are getting nervous, tell them to relax. They already gave you some great answers which now gives you the luxury of getting picky and more in depth. Lies, but it will make them feel comfortable.&lt;br /&gt;&lt;br /&gt;There you go. That's over 1000 interviews for camera's worth of experience for you in a lowly, less travelled SA forum.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-8229720553640481524?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/8229720553640481524/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=8229720553640481524' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/8229720553640481524'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/8229720553640481524'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/10/how-to-interview-now-with-more-text.html' title='How to interview now with more text'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-4379456021929586994</id><published>2008-10-24T14:34:00.001-07:00</published><updated>2008-10-24T14:34:11.675-07:00</updated><title type='text'>Too/to bold?</title><content type='html'>When to use bold and when not to, it's this afternoon's office discussion. &lt;br /&gt;We've just finished new screens for the beluga underwater and we have a nifty new design. It looks good. However, for design sake several words of each phrase are bold, and several are normal font. &lt;br /&gt;It looks good, but the discussion is, why are we bolding those words?&lt;br /&gt;In a full sentence we don't do that because if you need to bold a word to call attention to it, maybe you should just rewrite your sentence to present the concept better instead. If one word is more important than others, maybe you should lose the other words.&lt;br /&gt;&lt;br /&gt;However in a phrase like "Grey patch behind dorsal" is it bad if you bold "grey patch"?&lt;br /&gt;It looks good and the non-bold words are still important so we can't get rid of them but do we break our own rules?&lt;br /&gt;When does design trump content? Is that a neutral action? Does design only hurt or help content?&lt;br /&gt;Do we overthink this kind of stuff? All valid questions.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-4379456021929586994?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/4379456021929586994/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=4379456021929586994' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/4379456021929586994'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/4379456021929586994'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/10/tooto-bold.html' title='Too/to bold?'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-1898714046431149757</id><published>2008-10-24T08:34:00.000-07:00</published><updated>2008-10-24T08:40:18.942-07:00</updated><title type='text'>I NEED MORE SPACE</title><content type='html'>12 Terabytes for only 20k what a deal. I think it is going to be a hard item to get through the budget this year. Buying storage is not sexy. &lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;We're 500 GB from using up our 10TB of storage. That means we need more room. I'm sure we have a bunch of crap on there, but really we chew up space at the rate of a gig a minute for footage. We need big chunks free, not just a file here and there.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I figure we can keep ourselves to 2.5 TB stored footage per year. That should give a lifespan for the 12 TB array of 3 years or so (RAID 5). So I'm going to have to make sure people understand the yearly cost is about 6K. They are still not going to like that number so I'll also need to explain about falling drive costs. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;With any luck that will convince people. In all fairness I did say that storage costs would be an ongoing expense.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-1898714046431149757?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/1898714046431149757/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=1898714046431149757' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/1898714046431149757'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/1898714046431149757'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/10/i-need-more-space.html' title='I NEED MORE SPACE'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-3679219650272636592</id><published>2008-10-06T12:41:00.001-07:00</published><updated>2008-10-06T12:41:29.392-07:00</updated><title type='text'>The workflow of it all</title><content type='html'>Final Cut Server really is an amazing piece of software. It remarkably customizable and though complex, even a hack like myself can start to move around it pretty easily. &lt;br /&gt;&lt;br /&gt;That said, the real complexity is not even in the software. The real complexity lies in your workflow and the personalities that drive it. &lt;br /&gt;&lt;br /&gt;Right now I'm trying to figure out what our workflow is (it's pretty much all over the map) and what it should be.&lt;br /&gt;&lt;br /&gt;The problem with an awesome, strategic, comprehensive workflow is people. People actually have to do the things you want them to. They have to enter the right data, in the right spots in a consistent manner.&lt;br /&gt;&lt;br /&gt;That is the tricky bit and that is human nature. You have to design a path that will actually be walked. If you do anything else, and you kid yourself that you'll make people stay on the path, you're in for a surprise. You can't make anyone stay on the path, they have to decide to stay on the path.&lt;br /&gt;&lt;br /&gt;We had a huge control vocabulary that would bring our cataloguing up to library standards. I slashed and burned the thing. There is no way anyone would ever go to that level of detail when uploading data. They'd go around it and we'd have a totally flawed system.&lt;br /&gt;&lt;br /&gt;So I've simplified. Hopefully the simplified system will work out. It doesn't ask for much effort, just consistent effort. We'll see how well that works.&lt;br /&gt;&lt;br /&gt;After all the system to have all our stories have a simple 3-4 word title that is consistent from raw footage to final delivery, is hardly a success, and that is about as easy as you get.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-3679219650272636592?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/3679219650272636592/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=3679219650272636592' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/3679219650272636592'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/3679219650272636592'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/10/workflow-of-it-all.html' title='The workflow of it all'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-5454606513845744276</id><published>2008-09-24T12:17:00.001-07:00</published><updated>2008-09-24T12:17:59.181-07:00</updated><title type='text'>quit emailing me</title><content type='html'>So I thought I'd be smart and have FCSvr email me  whenever someone submitted a master for review. It worked. Wooo.&lt;br /&gt;&lt;br /&gt;Except that FCSvr emails me about 10 times for every one piece that is submitted. It's very excitable this Final Cut Server.&lt;br /&gt;&lt;br /&gt;It appears that once I have FCSvr email me about one status change, it emails about every status change. There is no email once and stop.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-5454606513845744276?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/5454606513845744276/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=5454606513845744276' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/5454606513845744276'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/5454606513845744276'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/09/quit-emailing-me.html' title='quit emailing me'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-2064609589101568750</id><published>2008-09-23T14:17:00.001-07:00</published><updated>2008-09-23T14:17:10.661-07:00</updated><title type='text'>Update breaks final cut server</title><content type='html'>Well, go figure, the update of awesomeness that is supposed to fix everything no problems ended up breaking things. Go figure. &lt;br /&gt;&lt;br /&gt;Yesterday I submitted a project for upload just as I was leaving, thinking it would run overnight. Welp, no such luck.&lt;br /&gt;&lt;br /&gt;FCSvr stopped creating video proxies for the uploaded footage and left me in the lurch. What good is having video in there if you can't view a preview. &lt;br /&gt;&lt;br /&gt;The old e_sum_param error which no one has ever heard of didn't really help me troubleshoot compressor.&lt;br /&gt;&lt;br /&gt;That was last night and the reason I was late for dinner. &lt;br /&gt;&lt;br /&gt;However this morning, with a clear head and a stick-it note left by me on monitor saying "check server" I checked the server and found the problem.&lt;br /&gt;&lt;br /&gt;During the update it changed the render cluster to nothing. Nothing was selected for that. This morning I changed it to "this computer" and just like that, proxy heaven.&lt;br /&gt;&lt;br /&gt;Now I don't have any idea what I really told it to do. I think I said rather than sitting there wondering where you should be rendering this, go ahead and use your own cpu and get 'er done. &lt;br /&gt;&lt;br /&gt;A lifetime of closed fist button mashing has prepared me well for my FCSvr admin duties...Just keep pressing buttons and restarting things until it works or you've really, really, really broken it.&lt;br /&gt;&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-2064609589101568750?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/2064609589101568750/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=2064609589101568750' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/2064609589101568750'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/2064609589101568750'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/09/update-breaks-final-cut-server.html' title='Update breaks final cut server'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-245384424294672469</id><published>2008-09-22T16:02:00.001-07:00</published><updated>2008-09-22T16:02:51.362-07:00</updated><title type='text'>But wait there is more Final Cut Server craziness</title><content type='html'>At this point I feel as though I'm accelerating along my descent into madness that Pro Training book so eagerly embraces.&lt;br /&gt;&lt;br /&gt;Another word for word quote from the Advanced Administration chapter:&lt;br /&gt;&lt;br /&gt;"With greater control comes greater complexity, so it's best to caffeinate heavily before diving into these pages"&lt;br /&gt;&lt;br /&gt;Good lord. What am I in for? I do like the honesty of this book though. No messing around pretending everything is going to be okay. It states it pretty clearly that you are on a likely suicide mission, but if by some chance you survive there will be great reward. &lt;br /&gt;&lt;br /&gt;I consider myself warned.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-245384424294672469?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/245384424294672469/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=245384424294672469' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/245384424294672469'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/245384424294672469'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/09/but-wait-there-is-more-final-cut-server.html' title='But wait there is more Final Cut Server craziness'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-6598585357640828118</id><published>2008-09-22T14:25:00.001-07:00</published><updated>2008-09-22T14:25:14.653-07:00</updated><title type='text'>Final Cut Server is hilarious</title><content type='html'>Clearly someone was losing their mind in the course of writing the Pro Training book for Final Cut Server.&lt;br /&gt;&lt;br /&gt;I'm dutifully going along, reading the book, trying to figure out what the hell I'm doing and how I'm going to deliver what I promised when I come across this word for word gem...&lt;br /&gt;&lt;br /&gt;"Now that users can log in, and assets are beginning to show up in the client application, you can take advantage of all the distracted oohing and aahing to knuckle down and design the true gems of your already thankless job: automations."&lt;br /&gt;&lt;br /&gt;I don't know what it seems like to you, but to me it sounds like that giddiness that starts to creep in when over-tired and facing punishing deadlines.&lt;br /&gt;&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-6598585357640828118?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/6598585357640828118/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=6598585357640828118' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/6598585357640828118'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/6598585357640828118'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/09/final-cut-server-is-hilarious.html' title='Final Cut Server is hilarious'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6000509243771454610.post-1515068591991921550</id><published>2008-09-08T23:48:00.001-07:00</published><updated>2008-09-08T23:53:11.300-07:00</updated><title type='text'>Content Inside</title><content type='html'>Content, content, content. Lots of content. Just spray it around, fill some buckets with it and do it fast. &lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It's a word that is thrown around so casually. "We'll just put the content in there" or "We need some content".   Many people look at content like it is a coat of paint. You build the thing, then just decide on the paint and slap it up. Content doesn't work like that, as much as people think it does.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I had someone upset with the time it was taking to come up with the right message for something. Their response to us taking so long was to grab some facts off wikipedia and slap them together...done. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;It's hard to get someone to recognize what it is you do when basically many consider the job a matter of finding and replacing all the "Lorus ipsum" with some of them english language words.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6000509243771454610-1515068591991921550?l=contentinside.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://contentinside.blogspot.com/feeds/1515068591991921550/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6000509243771454610&amp;postID=1515068591991921550' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/1515068591991921550'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6000509243771454610/posts/default/1515068591991921550'/><link rel='alternate' type='text/html' href='http://contentinside.blogspot.com/2008/09/content-inside.html' title='Content Inside'/><author><name>Jeff Heywood</name><uri>http://www.blogger.com/profile/10473102653853720890</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
