<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Buttonpusher</title>
	<atom:link href="http://www.buttonpusher.tv/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.buttonpusher.tv</link>
	<description>...posts from the trenches of new media production...</description>
	<lastBuildDate>Tue, 18 Jun 2013 18:44:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<copyright>2006-2007 </copyright>
	<managingEditor>admin@buttonpusher.tv (Buttonpusher)</managingEditor>
	<webMaster>admin@buttonpusher.tv (Buttonpusher)</webMaster>
	<ttl>1440</ttl>
	<image>
		<url>http://www.buttonpusher.tv/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
		<title>Buttonpusher</title>
		<link>http://www.buttonpusher.tv</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle></itunes:subtitle>
	<itunes:summary>...posts from the trenches of new media production...</itunes:summary>
	<itunes:keywords></itunes:keywords>
	<itunes:category text="Society &#38; Culture" />
	<itunes:author>Buttonpusher</itunes:author>
	<itunes:owner>
		<itunes:name>Buttonpusher</itunes:name>
		<itunes:email>admin@buttonpusher.tv</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://www.buttonpusher.tv/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<item>
		<title>I&#8217;ve discovered I have a new allergy</title>
		<link>http://www.buttonpusher.tv/2013/06/11/ive-discovered-i-have-a-new-allergy/</link>
		<comments>http://www.buttonpusher.tv/2013/06/11/ive-discovered-i-have-a-new-allergy/#comments</comments>
		<pubDate>Tue, 11 Jun 2013 13:42:10 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Editorial]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Media Technology]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=1875</guid>
		<description><![CDATA[It came to me last night. In the midst of a back-and-forth comment flow about the newly announced MacPro: I am allergic to people arguing about platforms. I get all itchy when people start railing against a brand based on &#8230; <a href="http://www.buttonpusher.tv/2013/06/11/ive-discovered-i-have-a-new-allergy/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>It came to me last night. In the midst of a back-and-forth comment flow about the newly announced MacPro: I am allergic to people arguing about platforms.</p>
<p>I get all itchy when people start railing against a brand based on some new product announcement. Hearing &#8220;Apple is dead to me,&#8221; causes me to twitch. I break into a cold sweat whenever I hear someone claiming one platform is the best there is and everything else sucks. It makes me ill enough to want to leave the conversation right away.</p>
<p>Are people really basing their loyalty to a brand or product on an announcement of a yet-to-be-shipped product? Seriously?!? So, the newly announced MacPro won&#8217;t allow you to make use of the PCIe expansion cards you are using today? Even though you are working on a 4-year old platform? With a 6-year old technology in PCIe? Even though not a single third party software or hardware developer has announced what their plans are for working with the new platform? Well, <a title="Grant's announcement about the new MacPro and Resolve" href="http://forum.blackmagicdesign.com/viewtopic.php?f=11&amp;t=8898#p56608" target="_blank">Grant Petty from Blackmagic</a> has good things to say, so we&#8217;ll have to see if others will follow.</p>
<p>I&#8217;ve watched this industry struggle through some significant changes and this argument, while changing topics, remains constant &#8211; people can&#8217;t stand change. I read it best in the comment on the Blackmagic thread above, &#8220;it&#8217;s really just the case of people wanting a bigger horse instead of a car.&#8221;</p>
<p>Someone asked me, after voicing my hatred of platform wars, why I continued to bother participating. I had to stop and think. I replied, &#8220;its in my nature to seek out &amp; keep as many tools in my kit as possible. I have to stay informed and up-to-date on the latest info and trends. While it may make my skin crawl, I&#8217;ll be damned if I&#8217;m going to let knee-jerk reactions and opinionated bloviations win the day.&#8221;</p>
<p>&#8220;Oh my god,&#8221; came the response, &#8220;could it be possible that you&#8217;re going conservative in your old age?&#8221;</p>
<p>&#8220;Exactly the opposite,&#8221; I replied,&#8221; I embrace change. I love learning all this new stuff. Bring it on.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2013/06/11/ive-discovered-i-have-a-new-allergy/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Formats &amp; Frame Rates &amp; Codecs, Oh My!</title>
		<link>http://www.buttonpusher.tv/2012/06/13/formats-frame-rates-codecs-oh-my/</link>
		<comments>http://www.buttonpusher.tv/2012/06/13/formats-frame-rates-codecs-oh-my/#comments</comments>
		<pubDate>Wed, 13 Jun 2012 14:03:35 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Media Technology]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=497</guid>
		<description><![CDATA[Last night, I was a panelist at the Women In Film &#38; Video session, &#8220;Formats &#38; Frame Rates &#38; Codecs, Oh My!&#8221; along with Virginia Quesada and Chief Engineer Sam Crawford of Henninger Media Services and moderated by Editor Mickey Green. It was &#8230; <a href="http://www.buttonpusher.tv/2012/06/13/formats-frame-rates-codecs-oh-my/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Last night, I was a panelist at the <a href="http://wifv.org/" target="_blank">Women In Film &amp; Video</a> session, &#8220;Formats &amp; Frame Rates &amp; Codecs, Oh My!&#8221; along with <a href="http://videocult.com/" target="_blank">Virginia Quesada</a> and Chief Engineer Sam Crawford of <a href="http://www.henninger.com/" target="_blank">Henninger Media Services</a> and moderated by Editor <a href="http://www.youtube.com/watch?v=R2rA-yc_UzY&amp;feature=player_embedded" target="_blank">Mickey Green</a>. It was a great evening covering a wide range of technical topics. The turnout was phenomenal. I was surprised and pleased to see a large number of producer-types there. I wondered if maybe the producers had come out, because of something that may be shifting in our industry. Being the Super-Tech-Geek that I am, I have noticed an increasing interest on the part of typically non-technical producers. These are folks who, in years past, have stayed away from the complex technical issues surrounding production and post-production. My theory is that (maybe) many of those folks are coming to the realization that tech is not going away nor is it getting any less complex. Lack of understanding of the technology used in our productions can be directly translated to higher costs and missed deadlines. The energy of last night felt like things were shifting slightly and that even the non-technical folks have a rising interest in getting a grasp on the technical stuff. Its a refreshing thought &amp; I hope I&#8217;m right. WIFV is interested in doing more of these sessions and I hope to be involved again. Stay tuned.</p>
<p>As promised, here are links to some of the items I presented:</p>
<p><a href="https://docs.google.com/presentation/d/1LrC9HQSSAgZ3yPQVnWSpRj1s88fvYFYq1HXtTaaWFfo/edit" target="_blank">Presentation Slides</a> - my slides on Backup Plan and Project Asset Management</p>
<p>The slides on HD formats were taken from a presentation I gave back in 2007. Here is a <a href="http://www.buttonpusher.tv/wp-content/uploads/2007/05/HDFormats.pdf" target="_blank">PDF of those slides</a>. There is more in the PDF than what I covered and (thankfully) most of it is still valid even 5 years later.</p>
<p>Here&#8217;s a direct link to my <a href="http://buttonpusher.tv/wp-content/uploads/2009/03/GenericAssetsFolder.zip" target="_blank">Generic Assets Folder Template</a>. And the post where I explain it all in more detail along with many other Asset Management techniques is <a href="http://buttonpusher.tv/wp-content/uploads/2009/03/GenericAssetsFolder.zip" target="_blank">&#8220;Man Crushed Under Weight of 34Terabytes.&#8221;</a></p>
<p>Thank you Mickey &amp; WIFVers for putting this event together. Thanks to those who attended. And keep your eyes out for info about upcoming events like this, there will be more!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/06/13/formats-frame-rates-codecs-oh-my/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>And we&#8217;re back&#8230;</title>
		<link>http://www.buttonpusher.tv/2012/04/03/and-were-back/</link>
		<comments>http://www.buttonpusher.tv/2012/04/03/and-were-back/#comments</comments>
		<pubDate>Tue, 03 Apr 2012 19:06:15 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Random Thoughts]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=485</guid>
		<description><![CDATA[Just a brief note to say that buttonpusher.tv is back up and running. We got hit with a &#8220;base64 hack&#8220;. It infected every single PHP file on the server that hosts buttonpusher.tv. So its been a pain to get everything &#8230; <a href="http://www.buttonpusher.tv/2012/04/03/and-were-back/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Just a brief note to say that buttonpusher.tv is back up and running.</p>
<p>We got hit with a &#8220;<a href="http://www.rvoodoo.com/projects/the-dreaded-base64-wordpress-hack-and-other-hacks-too/" target="_blank">base64 hack</a>&#8220;. It infected every single PHP file on the server that hosts buttonpusher.tv. So its been a pain to get everything re-installed. The only back up I had was from just after the infection hit on March 15. It did give me a chance to clear out a bunch of old theme and plugin files, but what a hassle.</p>
<p>The site is back online and it looks like I didn&#8217;t lose anything important. I did discover that my favorite theme &#8211; K2 is now only sporadically updated, so I may be in the market for a new WordPress theme later this spring.</p>
<p>Mostly just posting this to see if everything is back in working order. Thanks.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/04/03/and-were-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Avid Studio for iPad &#8211; quick take</title>
		<link>http://www.buttonpusher.tv/2012/02/02/avid-studio-for-ipad-quick-take/</link>
		<comments>http://www.buttonpusher.tv/2012/02/02/avid-studio-for-ipad-quick-take/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 19:50:51 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=474</guid>
		<description><![CDATA[Super quick take on Avid Studio for iPad: - much more intuitive than iMovie on iOS. - it reads ALL media on your iPad. All your music. All you photos. All your videos. And all your iTunes U content (that &#8230; <a href="http://www.buttonpusher.tv/2012/02/02/avid-studio-for-ipad-quick-take/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Super quick take on Avid Studio for iPad:<br />
- much more intuitive than iMovie on iOS.<br />
- it reads ALL media on your iPad. All your music. All you photos. All your videos. And all your iTunes U content (that won&#8217;t last, I&#8217;m sure &#8211; so easy to rip off that content)<br />
-very good set of editing tools &#8211; surprising for a version 1. Good Job Avid<br />
-you cannot (as far as I can tell) take a video with married audio and then cut shots into it without stepping on the audio. (i.e.-no master shot with audio and then cutaways). The only way I see to make it work (so far) is to rip the audio off of a movie and then bring it back in as an audio source. This needs to be fixed.</p>
<p>Very impressed with this first effort though. An editor for $5 that can send projects to a <del>professional</del> desktop editing app&#8230;wow.</p>
<p>UPDATE: So it only sends projects to the PC-version of Avid Studio. But its a step closer.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/02/02/avid-studio-for-ipad-quick-take/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Speak out against SOPA/PIPA</title>
		<link>http://www.buttonpusher.tv/2012/01/17/speak-out-against-sopapipa/</link>
		<comments>http://www.buttonpusher.tv/2012/01/17/speak-out-against-sopapipa/#comments</comments>
		<pubDate>Tue, 17 Jan 2012 22:41:56 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Editorial]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=468</guid>
		<description><![CDATA[While you are waiting for the next part of the &#8220;Faster. Better&#8230;(not necessarily) Stronger&#8221; series, take some time to educate yourself about the Stop Online Piracy Act(SOPA) &#38; The Protect Intellectual Property Act (PIPA). These bills are bad ideas.Â I&#8217;m all &#8230; <a href="http://www.buttonpusher.tv/2012/01/17/speak-out-against-sopapipa/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>While you are waiting for the next part of the &#8220;Faster. Better&#8230;(not necessarily) Stronger&#8221; series, take some time to educate yourself about the Stop Online Piracy Act(SOPA) &amp; The Protect Intellectual Property Act (PIPA). These bills are bad ideas.Â I&#8217;m all for protecting the rights of creators of material but SOPA and PIPA are the result of allowing a group of self-declared non-experts, who are being guided by companies who aren&#8217;t satisfied with only 40%+ market growth over 10 years to legislate something as wild andÂ untamableÂ as the Internet. It is a bad idea.</p>
<p>Educate yourself. Watch this video:</p>
<p><a href="http://www.buttonpusher.tv/2012/01/17/speak-out-against-sopapipa/"><em>Click here to view the embedded video.</em></a></p>
<p>Visit <a href="http://www.killsopa.org" target="_blank">killsopa.org</a> &#8211; The EFF&#8217;s clearing house on what to do to help stop these bills from becoming laws.</p>
<p>Contact your representative and make them aware that you don&#8217;t want these bills to become law.</p>
<p>And check back tomorrow, because we&#8217;ll be here. We aren&#8217;t going dark. We&#8217;ll be posting part 2. Maybe in all that extra time you&#8217;ll have *not* surfing Reddit or Wikipedia, you can drop by here!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/01/17/speak-out-against-sopapipa/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Faster. Stronger. . . (not necessarily) Better. â€“ PART 2</title>
		<link>http://www.buttonpusher.tv/2012/01/17/faster-stronger-not-necessarily-better-part-2/</link>
		<comments>http://www.buttonpusher.tv/2012/01/17/faster-stronger-not-necessarily-better-part-2/#comments</comments>
		<pubDate>Tue, 17 Jan 2012 21:10:54 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Editorial]]></category>
		<category><![CDATA[Media Commentary]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=464</guid>
		<description><![CDATA[A perspective on acquisition workflows. Part 2. <a href="http://www.buttonpusher.tv/2012/01/17/faster-stronger-not-necessarily-better-part-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>If you recall from <a href="http://www.buttonpusher.tv/2012/01/16/faster-stronger-not-necessarily-better-part-1/">Monday&#8217;s post</a>, I related an example of a very complicated and convoluted set of media files related to a one hour-long nature documentary. 10 camera formats. 1080 &amp; 720. 23.98fps. 29.97fps. All delivered on 25 external hard drives.</p>
<p>With all the the recent advancements in cameras and acquisition technologies, the expectation is the process of media production should become faster, easier and more stream-lined. We associate improvement with advancement, right? Â If itâ€™s new then it must be better. As I mentioned in part one of this post, though, as media production has moved into the digital space, it has become bogged down by the plethora of choices available to creators. The work Â feels more complicated and time-consuming, and it doesnâ€™t necessarily result in a better product.</p>
<p><strong><span id="more-464"></span>Why? Why is it like this?</strong></p>
<p>I blame free-market capitalism. No, really. It&#8217;s all about who invents a system, who gets that system patented, and who profits from the licenses of those technologies. It is a free-market system into which millions of marketing dollars are pumped every year. Everyone involved is doing their best to get you to use their system or their workflow. There is very little concern for the long-term impact of the changes these technologies force upon us. There doesn&#8217;t seem to be much concern about the long-term viability of these systems, either. Â Nor does there seem to be much care given to making this any easier to deal with. But, these companies can&#8217;t keep developing new stuff if there isn&#8217;t a market. And making stuff that works with the old stuff means you&#8217;d end up spending less and less over time. That can&#8217;t be, so free-market capitalism has formed this happy relationship with the tech companies to keep it all humming along. It seems to be working just fine&#8230;for them.</p>
<p>But as a user of this technology, I have to ask if we are really better off. Do the endless technological options and advancements lead us to create more successful products for less money and less time? Or does it just create ten new problems for every one it solves?</p>
<p>Letâ€™s look at digital high definition as an example of things can get very complicated very quickly.</p>
<p><strong>Now in Digital High Definition</strong></p>
<p>Even though corporations drive the development of media technology, until recently, they were subject to some very specific and narrow regulations on what passed as Broadcast Quality. The FCC (in the US) and the EBU (in Europe) had very narrow definitions of what qualified as &#8220;<a href="http://en.wikipedia.org/wiki/Broadcast-safe">broadcast safe</a>&#8220;. <a href="http://en.wikipedia.org/wiki/NTSC">NTSC</a> and <a href="http://en.wikipedia.org/wiki/PAL">PAL</a> were mandated by those bodies and anything you wanted to put on the airwaves had to meet those one of those standards. Both of them came in just a few varieties and there was little question if something met specs or not. And because it just wouldn&#8217;t make economic sense to create two-tiers of products, the Broadcast Standards drove the market. (i.e.- the market for video gear that didn&#8217;t work with existing gear was/is very small, hence it never took off).</p>
<p>Along comes HD and a switch from analog over to digital and a need by the governing bodies to re-define specs and standards. The governing bodies, however, aren&#8217;t a bunch of engineers. They are career policy wonks. Additionally, this all came at a time of massive deregulation and relaxation of governmental oversight. In the face of this, the FCC &amp; EBU turned to the technology companies themselves to define the HD standards. On the surface, it seems like a really great thing to let the companies who will build the products define the standards because they know their own limits and boundaries. But . . .</p>
<p>In the U.S., the FCC formed the Advisory Committee on Advanced Television Service in 1987. Out of that came the <a href="http://en.wikipedia.org/wiki/Grand_Alliance_(HDTV)">Grand Alliance</a> &#8211; a group of technology companies with a vested interest in creating the new standards for what would become High Definition as we know it today. Eventually, the HD specs were codified into the <a href="http://en.wikipedia.org/wiki/ATSC_standard">ATSC Standard</a>. When you factor in screen-size, interlacing vs. progressive, &amp; frame rates, there are 79 different possible formats that fall under this standard (57 for HD alone). And of course, once again, North America is on a different standard than much of the rest of the world. For us, it&#8217;s ATSC. For Europe and much of Asia, it is Digital Video Broadcasting (<a href="http://en.wikipedia.org/wiki/Digital_Video_Broadcasting">DVB</a>). Thankfully, both standards can accommodate each other&#8217;s frame rates, so it isn&#8217;t as bad as before.</p>
<p>Basically, a bunch of vested parties created a seat at the table (some would argue they created the table itself) and then proceeded to squeeze in a large number of &#8220;standard&#8221; formats. Expanding the number of standards has only served to confuse matters. In the days NTSC/PAL, you could be fairly certain that material sent to you would work in your show. Todayâ€™s world of mixed resolutions and frame rates, while certainly possible technically, is very messy. I donâ€™t think the intent was to create a mess, but that is what we have. While it isnâ€™t always a given that, as technology advances, things become more simple and efficient; generally thatâ€™s the case. Often there can be unintended effects that ripple around a given advancement.</p>
<p><strong>The Microwave Effect</strong></p>
<p>80 years ago, if you wanted to boil water, you started a fire or lit the stove and you waited. Then, starting in 1970, the microwave oven turned that several minute wait into seconds. It was, undoubtedly, a time saver. The microwave oven has had an unintended effect on its user&#8217;s psyche as well. Back in the days of waiting to watch a pot boil a few long minutes wasn&#8217;t that big of a deal. Today, we find ourselves getting impatient while waiting 30 seconds for that cup of hot water to come out of the microwave. It has eroded our patience. I call it The Microwave Effect. We need instant gratification. This subtle little change to our ability to wait has far-reaching impacts. It reaches right into the world of Media acquisition. Let me explain.</p>
<p>Tapeless cameras have made it possible to shoot hours and hours of footage. It&#8217;s easy. It&#8217;s simple. There&#8217;s no tapes to load or lug around. There&#8217;s no film to load or process. Just shoot and copy it to a hard drive. It all gets recorded as files. Files are what the editor needs to work with to create a show. The editor needs footage, and these cameras can shoot a lot of it. Over shooting is commonplace because there&#8217;s such a low upfront cost. There are costs, however. These costs are hidden or delayed, but they are still there.</p>
<p>Here&#8217;s a hidden cost: more footage means the editor needs more time to go through it all. But the editor doesn&#8217;t have more time in today&#8217;s world. In fact, they have less time because schedules are tighter and turn-around times are shorter. You get the double whammy of more footage, less time, and a demand that the final product be cranked out very quickly. It is The Microwave Effect in full force.</p>
<p>Here is an actual conversation I overheard that sums it up pretty well:</p>
<blockquote><p>Producer, on a conference call with a prospective editor: &#8220;So you&#8217;ll get 2 weeks to cut the show to roughcut stage&#8230;&#8221;<br />
Editor, voice wavering: &#8220;When I cut for you last season, we had 3 weeks per episode.&#8221;<br />
Producer: &#8220;I know. But the network wants a faster delivery this season, so you&#8217;ll just need to cut fast.&#8221;<br />
Editor: &#8220;OK, I guess so.&#8221;<br />
Producer: &#8220;But, this time around we&#8217;re using tapeless cameras! We&#8217;ll have 3 cameras on most shoots, instead of the one or two we had last season. You&#8217;ll have so much more footage to choose from. It should be a piece of cake!&#8221;<br />
Editor: &#8220;More footage? Is an AP going to log it in advance?&#8221;<br />
Producer: &#8220;Hmmmm, I guess we could get an intern on that, but it should all go really quick because it&#8217;ll already be Quicktime files. You can just bring them in and start editing right away!&#8221;<br />
Editor: &#8220;In two weeks instead of three. With more footage per episode. All logged by an inexperienced intern&#8230;Sounds awesome.&#8221;</p></blockquote>
<p>In my memory, I can just hear a microwave beeping in the background right after the editor finished talking.</p>
<p><strong>And <em>what</em> about that editor?</strong></p>
<p>Now, to pile more problems on top of the Multiple Format Standards and Microwave Effect problems &#8211; media acquisition has migrated responsibilities around a bit. What used to be set in place by choices in the field, has now been unceremoniously foisted off to someone else down the line. In the olden days of 2002, you would shoot to tapes. Someone would go through those tapes and load all the best takes and you&#8217;d be ready to start editing. There weren&#8217;t many options because NTSC was just NTSC. You, as the Editor, might even do that loading yourself, because that would give you a chance to Â watch the footage play back, in real time &#8211; A brief pause to collect yourself and get your head around this pile of stuff before setting down to craft something out of it. Ah, the good old days.</p>
<p>You may have heard a new term for a crew position lately: Media Wrangler. This is the person who is responsible for making sure all the media is being backed up and transferred to systems which can interface with the post-production part of the process. Media Wranglers are often younger, less experienced folk who have gained a foothold with their ability to work with computers. They have much to learn, but mostly they are eager and quick to pick things up. But any Media Wrangler who has talent also demands to be compensated. Most budgets don&#8217;t factor in another crew hand, so often the task of wrangling media falls on the Camera Operator, or Audio Operator, or Producer, or a Production Assistant. Because these folks are often doing media wrangling as a second, third, or even fourth duty, the attention to detail and careful consideration of how their work could be creating more work for someone who will come along later often goes by the wayside. Then the task of figuring this out falls on the editor, the one person in this process who already has the biggest responsibility (see below) for creating a polished and professional product. The one person in this chain who is in the least in need of being given more responsibility.</p>
<p>The editor is the person with the second biggest responsibility behind the producer or director or line producer or whoever is actually responsible for making the show. (See? It&#8217;s even gotten so muddled that you can&#8217;t figure out who makes the decisions half the time.) What&#8217;s clear to me, having been in the editor&#8217;s chair and the show creator&#8217;s chair, is that the editor is often The One Who Makes It All Happen. The editor is going to have to figure out how to get all these formats and frame rates and elements to go together and come out as a technically &amp; creatively acceptable product on the other end. It falls to them. And, far to often, blame falls on them as well. Blame for a show that fails to perform. Blame for muddled writing, poor performances, or rough transitions. I&#8217;ve seen editors be the scapegoat for another team member&#8217;s failure to deliver. So, in my mind, the editor is often the one who puts their butt on the line when it comes to bringing a show to completion.</p>
<p>As an editor, I often find myself taking on the following responsibilities: log the footage, edit the show, find the music, conceive/create/design the show graphics, VO talent or engineer, scriptwriting&#8230;well, script-tweaker, footage/stills researcher.</p>
<p>For those of you keeping score, that&#8217;s seven primary responsibilities, a couple of which are full time jobs in and of themselves. You need to be a good listener, a good conversationalist, have an open-mind to try new things, and be able to make many decisions very quickly. It is a challenging position. And this list could easily double or triple in size. My point is that, as editors, the last thing we need to be worrying about is how to convert the 57 different types of footage in to a format that is compatible with our systems. Well, we need to worry about it, but we shouldn&#8217;t be the ones who are forced into dealing with preventable problems from the field. (In other words, call us before you shoot!)</p>
<p>All of that above has left us with the mess we have today. More footage. Less time. And the pressure to deliver immediate results.</p>
<p>And this is where I feel things aren&#8217;t working out quite correctly. I&#8217;m not opposed to new technologies and finding new methods of doing things. Some of these new cameras are amazing. Some of them are not. I just haven&#8217;t decided yet if the way things are playing out is really the best for everyone. It certainly seems, to me, that this stuff is sufficiently complicated that we all may be painting ourselves into a corner without even <a href="http://cultureandcommunication.org/deadmedia/index.php/Main_Page">realizing it.</a></p>
<p>Next time we dive back in with a look at some of the pitfalls of tapeless acquisition from an archival/historical perspective&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/01/17/faster-stronger-not-necessarily-better-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Faster. Stronger. . . (not necessarily) Better. &#8211; PART 1</title>
		<link>http://www.buttonpusher.tv/2012/01/16/faster-stronger-not-necessarily-better-part-1/</link>
		<comments>http://www.buttonpusher.tv/2012/01/16/faster-stronger-not-necessarily-better-part-1/#comments</comments>
		<pubDate>Mon, 16 Jan 2012 20:16:26 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Editorial]]></category>
		<category><![CDATA[Media Commentary]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=450</guid>
		<description><![CDATA[A perspective on acquisition workflows. <a href="http://www.buttonpusher.tv/2012/01/16/faster-stronger-not-necessarily-better-part-1/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>It&#8217;s the whole premise of <a title="The Six Million Dollar Man Opening" href="http://www.youtube.com/watch?v=HofoK_QQxGc" target="_blank">The Six Million Dollar Man</a>:Â &#8221;We have the technology to make him better, stronger, faster than he was before!&#8221; I&#8217;m all for it in most aspects, but some things have become faster and stronger, but not really better. And in some cases, much worse than before.</p>
<p>Take acquisition. I&#8217;m talking about capturing material in the creation of a program. It can be whatever kind of show you&#8217;d like. Developments in digital acquisition have exploded in the last few years. We have such cool toys with which to capture events in 2D or 3D &#8211; Red EPIC, Phantom, Viper, DSLR, P2, XDCAM, F3, AF-100, 5D, 7D, C300, GoPro &#8211; the list goes on and on.</p>
<p>The image quality cannot be denied for many of these new cameras. They are amazing. If you had told me I would be working with HD images at 5K resolution just 5 years ago I would have doubted you. The detail and latitude these new devices provide are incredible.Â But there&#8217;s a downside to it all. A downside I don&#8217;t think anyone really thought through as these new technologies were being proposed, designed and invented. It&#8217;s a downside that many production people don&#8217;t see or even think about. It&#8217;s a downside that foists responsibility onto the last person in the chain of program creation that needs more responsibility.</p>
<p><span id="more-450"></span></p>
<p>I mean no criticism of any individual production company or producer by laying this all out. I see this as a problem of formats, incompatibilities, and vendor choices more than a failure of individual choices. This is the reality many editors face. Something doesn&#8217;t sit right with me about it all. In the midst of all this advancement, the workflows, job descriptions, and mentality surrounding dealing with media hasn&#8217;t kept pace with reality. It is creating problems down the line and these issues are so complex that I don&#8217;t think many comprehend the trouble we&#8217;re about to come up against &#8211; trouble that translates into dollars and time wasted in a market where both things are drying up.</p>
<p>Let&#8217;s take a look at a single show (yes, a single show) I&#8217;ve recently been involved with: This program is an hour long nature documentary. It was shot over the course of 6 months. It got its start as being both a broadcast show and a theatrical release. When the proposition of theatrical release failed to materialize, the show&#8217;s production budget had to be tightened.</p>
<p>What started as a Red EPIC 5k shoot with some Phantom, DSLR &amp; GoPro footage had to switch to a variety of HD cameras: HDX900, 5D, 7D, XDCAM, HVX-200, DVCPRO-HD &amp; CineFlex. This switch seemed to be predicated primarily by what camera operators were available to shoot and when. It went from 4 formats to 10. When all of the camera original backups were delivered it came on 25 external drives. Thankfully most of those were master/backup pairs, so realistically I&#8217;m dealing with 15 drives. Still, that&#8217;s about 20 terabytes of material and it is all over the place.</p>
<p>To start there&#8217;s the issue of resolution &#8211; it&#8217;s a mix of 1080 &amp; 720 now. Obviously, the Red, Phantom and DSLR&#8217;s are capable of higher-than-1080 resolutions, but 1080 is all that is required for broadcast delivery, so that becomes the sweet spot. And of course, there&#8217;s a frame rate issue. Network deliverables call for 1080i60 master. That means 29.97. Much of the above footage is shot at 23.98, but not all of it. Standard fare these days.Â So, everything is being converted to Apple Pro Res 422 1080i30 (or 1080i24 depending on original frame rate). The show will be cut in FCP7 on a 1080i30 timeline.</p>
<p>&#8220;It&#8217;s always something,&#8221; is one of my dad&#8217;s sayings about dealing with technical issues. It&#8217;s become a mantra of mine when dealing with these kinds of projects. &#8220;It&#8217;s always something,&#8221; I find myself repeating as I have to manually organize files or build complicated Terminal batch files via a set of hoop-jumping steps in a text editor.</p>
<p>After getting it all sorted and figuring out what needed to be done to what &amp; in what order, I set to work. The show will begin editing soon and I think all the footage will have been converted to a format that should make the edit go smoothly. I&#8217;m really good when it comes to sorting out ways to solve media conversion issues, even if I do say so myself.</p>
<p>At some point in the process of working through all this footage, I thought, &#8220;why? why is it always something?&#8221; I know a large part of that is the nature of the beast. Media production of any kind is fraught with issues to be resolved and problems in need of fixing. But a portion of this problem is fabricated. It is created by the technological changes to the process of acquisition our field has gone through over the last 5 years. I&#8217;m not sure we have landed in a better place. Higher quality? Yes. Lighter gear? Yes. Faster gear? Absolutely. Cheaper? Yes&#8230;more or less. (there are hidden costs of both money and time). More choices? Yes&#8230;but that&#8217;s not always a good thing.</p>
<p>I remember a funny story I heard from a college friend after I had graduated and begun editing on Avid/1 (as it was called back then). He was working with a small production group as an assistant editor. It was around the time they had finished their first show on an Avid:</p>
<p>&#8220;Yeah, Avid is cool and all,&#8221; he said, &#8221; but it really isn&#8217;t helping get this show done.&#8221;</p>
<p>&#8220;Why not,&#8221; I replied. I was thinking they just didn&#8217;t understand how useful this editing tool was.</p>
<p>&#8220;Well, in the same time it took us to cut a similar show last year on the flatbed,&#8221; he said with the wistful look of a masochist&#8230;I mean&#8230;film-editor who missed his splicing block and processing chemical cologne,&#8221; we cut 4 versions of the show.&#8221;</p>
<p>&#8220;Wait,&#8221; I said, &#8221; you cut 4 versions on the Avid in the same time it took to cut one on film?&#8221;</p>
<p>&#8220;Yeah,&#8221; he replied, &#8220;now everyone&#8217;s fighting over who&#8217;s version is better.&#8221;</p>
<p>And that, right there, is exactly the problem we face: As media production moved into the digital space, it became bogged down by the plethora of choices available to the creators. It&#8217;s a wonder anything ever gets created at all.</p>
<p>Join us next time as we explore the question of &#8220;why is it like this?&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/01/16/faster-stronger-not-necessarily-better-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What about the non-Broadcast arena?</title>
		<link>http://www.buttonpusher.tv/2012/01/11/444/</link>
		<comments>http://www.buttonpusher.tv/2012/01/11/444/#comments</comments>
		<pubDate>Wed, 11 Jan 2012 17:42:51 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Editorial]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Media Technology]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/2012/01/11/444/</guid>
		<description><![CDATA[As a followup to my previous post, I received this question (or something like it) in a few emails: &#8220;do you think this same trend will hit the non-broadcast arena?&#8221; The answer is, it depends. It depends on what kind &#8230; <a href="http://www.buttonpusher.tv/2012/01/11/444/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>As a followup to <a href="http://www.buttonpusher.tv/2012/01/10/weve-been-here-before/" target="_blank">my previous post</a>, I received this question (or something like it) in a few emails: &#8220;do you think this same trend will hit the non-broadcast arena?&#8221;</p>
<p>The answer is, it depends.</p>
<p>It depends on what kind of work you are doing. Final Cut Pro X is not anÂ unusableÂ editor for many folks. Undesirable for some, but it is capable of editing programs together. People who are editing for the web or for DVD delivery, are probably going to have very little cause to think about switching away from FCP-X.</p>
<p>That being said, there&#8217;s alot of stuff that FCP-X does differently than FCP7. It is different enough that, for all intents, it *is* a different NLE application. There will be a learning curve. There will be new ways you will have to learn to handle tasks in a different fashion. Some tasks just don&#8217;t work the same way as they did before. From little things like setting In &amp; Out points on a clip to big things like media management, FCP-X will be a new thing for whoever picks it up.</p>
<p>So, while the main premise of my previous post doesn&#8217;t completely apply to smaller firms (Go big or stay small), I think that there needs to be some serious consideration given to the kinds of work you are currently doing and the kinds of work you might be doing in the near future. You will need to factor that in to your decision. FCP-X just isn&#8217;t going to have the same kinds of support FCP7 does. You won&#8217;t be able to send an FCP-X project to a post-house and have them work with it as-is. Once they receive it, they are going to need to run it through some extra steps in order to get a timeline exported for use in audio or color in anÂ efficientÂ manner.</p>
<p>On the other hand, both Avid Media Composer and Adobe Premiere Pro support many of the same import and export paths that FCP7 does today. So, if you are looking for the closest non-FCP match, then you may want to explore those platforms. Also, FCP7 is probably going to remain a viable editing application for a few more years. It won&#8217;t be updated, but it could probably remain serviceable for some time. What we don&#8217;t know, is if some future update to OSX or to Quicktime will break the functionality of FCP7. If that happens, then in order to maintain an FCP7 system, you will need to have a older installation of OSX and Quicktime running to make it work. In my opinion, that&#8217;s a temporary solution and not something I&#8217;d trust as my primary production platform for very long.</p>
<p>The issues of drive space and hardware purchases are certainly more financially driven than anything else. So if it is a case of planning for upgrades or for planning new purchases for your operation, I think you need to do your research about FCP-X, Avid, Premiere Pro and anything else to see what the future might hold for you if you make a choice to go down a certain path.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/01/11/444/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>We&#8217;ve been here before&#8230;</title>
		<link>http://www.buttonpusher.tv/2012/01/10/weve-been-here-before/</link>
		<comments>http://www.buttonpusher.tv/2012/01/10/weve-been-here-before/#comments</comments>
		<pubDate>Tue, 10 Jan 2012 17:02:37 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Editorial]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Media Technology]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=434</guid>
		<description><![CDATA[Last Friday I came across this bit of news: Avid today announced that renowned television production company, Bunim/Murray Productions, has selected Avid Media ComposerÂ® 6 and Avid SymphonyÂ® 6 editing software for all of its programs beginning in early 2012. &#8230; <a href="http://www.buttonpusher.tv/2012/01/10/weve-been-here-before/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Last Friday I came across this bit of news:</p>
<blockquote><p>Avid today announced that renowned television production company, Bunim/Murray Productions, has selected Avid Media ComposerÂ® 6 and Avid SymphonyÂ® 6 editing software for all of its programs beginning in early 2012. Bunim/Murray joins a growing number of professional users who have returned to using Avid solutions from Final Cut Pro to meet their production workflow requirements. Additionally, as part of this implementation, Bunim/Murray also plans to deploy an Avid ISISÂ® 5000 shared storage system to effectively store and share media across its organization.</p></blockquote>
<p>On the surface it seems like a no-brainer. Apple has forsaken the broadcast editor to release an application that is more in line with the company&#8217;s minimalist approach. In doing so, they have effectively removed the application from consideration by many editors who need things like: deck control, import and export of interchange formats (omf), manual media management and self-determined timeline configuration (i.e. manual assignment of tracks). Editors who don&#8217;t need those things have a very fine tool at their disposal. Editors who do need them, are looking elsewhere. FCP-X may deliver those things in time. Certainly there are third-party solutions that make it serviceable enough now, but that&#8217;s not acceptable to a large operation like Bunim-Murray or to most professional editors, who don&#8217;t want to have to &#8220;roll their own&#8221; features.</p>
<p>Hence a huge production company like Bunim-Murray is going to drop FCP in favor of Avid Media Composer. It&#8217;s going to start happening more and more. FCP-X just can&#8217;t fit into existing workflows for delivery of broadcast material. More companies are going to switch. Many will go to Avid. Some will go to Premiere Pro. There are some production companies out there, however, that won&#8217;t be able or willing to make the switch. And this is the history-repeating-itself part, this switch is going to kill those companies off.</p>
<p><span id="more-434"></span></p>
<p>Keep in mind that this is all speculation and prediction on my part, but I think after spending 5 years in Post Production Management and nearly 25 years in the business, I can see how it is going to play out.</p>
<p>It has happened before: the switch from Linear to non-linear, the upgrade from Avid Nubus to Meridian systems, and the FCP vs. Avid debate earlier this decade (this would be the event that resulted in so many companies constructing an environment based on FCP and XSAN). {Cue <a href="http://www.youtube.com/watch?v=rpqYPBi6iHI&amp;feature=related" target="_blank">Shirley Bassey</a> singing here} These changes have eaten companies or forced them to dissolve, and the people behind them to move on to other ways of staying in the business (or leave the business entirely). Companies that couldn&#8217;t afford to upgrade their systems or wouldn&#8217;t upgrade, often found themselves falling out of the running for contracts to produce the shows the networks need to stay on air. The news above about Bunim-Murray&#8217;s switch is very telling about how the dominoes are about to fall. FCP-X will be only a small part of professional post-production workflows at large facilities. Sure, it will still be used by many smaller firms or one-person operations, but for the large operations, FCP is getting knocked off the hill.</p>
<p>This has some deeper significance than it appears at first glance. There are financial and technical issues that will help to enhance the business-killing aspect of this switch. These aspects will greatly affect how things proceed into the future. I suspect that there&#8217;s a good chance, that the kind of revolution that the rise of FCP (pre-FCP-X) brought about won&#8217;t happen again for a long time, if at all.</p>
<p>To set the scene, you have to understand the flimsy foundation that most modern production companies are built upon: basing 100% of your business revenues on income from broadcast cable programming is an unsustainable premise. The executives of these networks know this to be true. They watch companies try and try to make it work, knowing full-well that it isn&#8217;t sustainable. One of them even told one of my bosses that very thing: &#8220;we know our shows aren&#8217;t profitable for a company like yours, but we string you along long enough to make us look good and when your company tanks, there are 3 or 4 more new ones waiting to fill the gap&#8230;and at half the cost per half-hour show.&#8221; The companies that have survived have often branched out to include over-the-air broadcast or other areas of diversification, but many haven&#8217;t and they are no longer around. More will follow in light of this switch.</p>
<p>Several of the successful companies have based their infrastructure on Final Cut Pro and they did it at a time when Final Cut Pro made it artificially affordable.</p>
<p>In the few years prior to FCP&#8217;s dominance, a non-linear editing system cost, in the neighborhood of $30,000-$50,000. That was an Avid system, capable of uncompressed with enough storage to edit a medium-length program. That price didn&#8217;t include a broadcast video deck, which ran you at least $5,000 for a used BetaCam-SP or $60,000 for a new Digital BetaCam. New HDCAM decks (released in the late 90&#8242;s &amp; early 00&#8242;s) could run over $100,000.<br />
Then, along came Final Cut Studio. Only $1,000 for the application. I put together my first FCP system, capable of uncompressed and with more storage than the Avid system mentioned above AND a J3 Digital BetaCam Player for $25,000. It was a revolution. Take out the Digital BetaCam deck and you could get the system under $15,000. Purchase fewer drives and you could get a system under $10,000. All of which could do the same thing as a $50,000+ Avid system. Sadly, that undercutting hurt Avid, which struggled for a few years. Happily, it meant that the cost of entry to broadcast editing was cut by as much as four-fifths. It made it super-affordable for production companies to rapidly expand and bring costly pay-by-the-hour editing in-house where it could be paid for at (effectively) flat rates and the costs could easily be amortized over several series.</p>
<p>So, the story thus far, is that broadcast cable networks need production companies to churn out ever cheaper work and cost-of-entry into post-production dropped by 80%. It was a perfect storm of opportunity for cable to get what it wanted: cheap shows that delivered record profits &amp; production companies to fool themselves into thinking that buying a system on the cheap meant that they had solved the problem of meeting the technical requirements for broadcast delivery. It was (and still is) a sticky situation because a) technology isn&#8217;t static &amp; b) as the old saying goes, &#8220;the bitterness of poor-quality lingers long after the sweetness of low-cost has faded.&#8221;</p>
<p>FCP is great editor right out of the box, don&#8217;t get me wrong. It has a great interface, a good suite of tools, and easy media management (compared to the alternatives at the time, yes it was much easier to manage). But there were certainly things that didn&#8217;t work properly from the start. Things that could be related to a corrupt media file, or the size of your FCP project file, or even the speed of your media drives. Many of these items often were attributable to user error and Apple was loathe to offer support for something so quirky and variable as an FCP system with a bunch of third-party add ons. However, it did about 80% of what it needed to do really well. The other 20% is where it completely failed. (I find, this formula applies to most apps in the editing/motion design field.)</p>
<p>Now along comes this speed-bump: one NLE application has given up on the features that The People Who Edit For A Living need in an attempt to force a complex task like editing into the Apple-centered view of things. It&#8217;s perfectly evident when you apply this <a href="http://www.therussiansusedapencil.com/post/12290002370/jony-ive-on-simplicity">Johnny Ive quote</a> to the approach Apple has taken with FCP-X:</p>
<blockquote><p>â€œWhy do we assume that simple is good? Because with physical products, we have to feel we can dominate them. As you bring order to complexity, you find a way to make the product defer to you. Simplicity isnâ€™t just a visual style. Itâ€™s not just minimalism or the absence of clutter. It involves digging through the depth of the complexity. To be truly simple, you have to go really deep. For example, to have no screws on something, you can end up having a product that is so convoluted and so complex. The better way is to go deeper with the simplicity, to understand everything about it and how itâ€™s manufactured. You have to deeply understand the essence of a product in order to be able to get rid of the parts that are not essential.â€ -from <a href="http://www.amazon.com/Steve-Jobs-Walter-Isaacson/dp/1451648537/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1320344503&amp;sr=1-1">&#8220;Steve Jobs&#8221;</a> by Walter Isaacson</p></blockquote>
<p>Sure he&#8217;s talking about the design of physical products, But if it&#8217;s a company-wide philosophy to make things more minimal and simpler, then that is really what they&#8217;ve tried to do with editing. I don&#8217;t see how it can work though. Everything is either going to look exactly the same or very, very basic. Simplifying editing is like painting any kind of scene only with one set of stencils &#8211; technically it *is* still painting. Now imagine giving the same set of stencils to Titian, Renoir, Picasso, Van Gogh, and Banksy.</p>
<p>So the people who require complete control over their editing environment now are faced with a decision &#8211; where to go next? The companies that hire them are faced with the same decision. Â Where it goes will depend on the financial fortitude of those folks to upgrade and switch. It isn&#8217;t a simple prospect and it will certainly be the beginning of the end for some companies.</p>
<p>Previous iterations of FCP were so attractive because of their low-cost and that they did about 80%-90% of what needed to be done in your given realm of editing (for broadcast, web, or internal use, etc.). But that low-cost has created a situation where there now isn&#8217;t a fully-formed infrastructure in place to allow for a change of direction.<br />
Any company thinking of switching away from FCP, must consider these (potentially) hidden issues that could make a mess of things:</p>
<p>1. XSAN &amp; Avid Media Composer are not compatible&#8230;.well, not in a simple way. Avid MC wants to use the entire drive for its media files. XSAN gives each user the entire drive. That&#8217;s the problem. Each Media Composer accessing the XSAN volume is going to try and manage it as though it were only attached to that specific MC system. There would be a constant battle of media files database creation by all those systems. The only way I see that it could work would be to run your XSAN more like a Unity system &#8211; creating volumes that only one Media Composer system can access at a time.</p>
<p>2. Third-Party capture cards not fully supported. This is changing, but it will still create problems for some. Until there are working drivers for all cards on the market to be compatible with Avid &amp; Premiere, some companies that invested in the unsupported cards will be forced to replace those cards with ones that work.</p>
<p>3. Learning curve for FCP-only editors. There&#8217;s a cadre of editors out there that have grown up editing on FCP only. They are going to have trouble switching to Avid. Maybe this will be short-lived, but at least the older editors who used to be stymied by knowing Avid instead of FCP will get more work. Of course, Avid MC and Premiere Pro can be configured to have the keyboard work the same as FCP, but that&#8217;s going to limit your abilities with the new program &#8211; the FCP Way isn&#8217;t the only way.</p>
<p>4. Compatibility of older FCP systems and media. Again this is becoming less of a problem, but still requires people on-board who understand the desired end goals and the limitations of the systems. Files will need to be converted. Projects will become inaccessible for future revisions (at least to work with the original media).</p>
<p>5. Insufficient technical knowledge from the top-down. For some companies, this won&#8217;t be a problem. They&#8217;ve acknowledged that keeping up with the tech is best left to someone they can hire. They&#8217;ll be fine. The companies that are in the most danger in this area are the companies who consider their existing FCP/XSAN environment to be &#8220;good enough&#8221; and they forego upgrading or switching. Owning equipment is a roller coaster ride. Once you step on, you cannot get off without a major upheaval. Companies and people who (at any point) think that they&#8217;ve got just what they need today, will be crowded out by the companies who stay current with tech trends and stay on top of where things are going. (You might be one of those stay-on-top-of-it-people if you&#8217;ve made it this far into this post. <img src='http://www.buttonpusher.tv/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> )</p>
<p>Who is going to come out on top?</p>
<p>After things settle a little bit, I&#8217;m not sure who is or isn&#8217;t going to come out of this successfully. Obviously, companies like Bunim-Murray have the capital and knowledge to upgrade their way through sea-changes like this. Other companies can&#8217;t or won&#8217;t be able to make a shift. My advice would be to get smart about this now. Learn about it now or hire someone who can educate you about where you should be heading.</p>
<p>If you are thinking of starting or growing a production company, I think you have two options: 1)Go Big. Really big. You&#8217;ll need a huge SAN, multiple systems. You&#8217;ll need a large centralized facility with adequate power and cooling to handle a medium-sized server room and multiple suites. You&#8217;ll need to bring in-house, all the gear you need to deliver content to your clients (that includes the fiddly broadcast bits like waveform/vector scopes, legalizers, and decks). Oh, and hire the right people (and enough of them) to keep it all running. Or 2), you&#8217;ll need to stay small. Keep your technical footprint minimal and farm out your work to many of your favorite editors, who are setting up single suites in their basements or small offices or revisit a relationship with a post-production facility. Let someone else worry about staying up in the technical side and work out a rate structure that is favorable for you both. Make sure everyone understands how to work remotely &#8211; it can be done. Of course, you&#8217;ll need to hire a few technically knowledgeable people to co-ordinate all the media management and standardize content delivery. If you go small, you will be decentralized and less dependent on a single vendor&#8217;s only NLE application. You need to be flexible and savvy about technology and stay on top of trends in cameras, computers, and digital content delivery.</p>
<p>Wherever it all goes, I think it&#8217;s going to look different than it does today. FCP had a good ride. Apple has decided to go a different direction. And, as Bunim-Murray&#8217;s decision shows, that&#8217;s fine, as long as you can afford to make the switch.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2012/01/10/weve-been-here-before/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>WIFV &#8211; NLE Demo &amp; Petting Zoo</title>
		<link>http://www.buttonpusher.tv/2011/09/20/wifv-nle-demo-petting-zoo/</link>
		<comments>http://www.buttonpusher.tv/2011/09/20/wifv-nle-demo-petting-zoo/#comments</comments>
		<pubDate>Wed, 21 Sep 2011 02:57:05 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Media Technology]]></category>
		<category><![CDATA[Resources]]></category>

		<guid isPermaLink="false">http://www.buttonpusher.tv/?p=421</guid>
		<description><![CDATA[On Tuesday, Sept. 20th, I gave a talk at the Washington D.C. Women In Film &#38; Video NLE Demo &#38; Petting Zoo. It was a good talk and I think a lot of information was exchanged. I&#8217;m sure it raised &#8230; <a href="http://www.buttonpusher.tv/2011/09/20/wifv-nle-demo-petting-zoo/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>On Tuesday, Sept. 20th, I gave a talk at the Washington D.C. Women In Film &amp; Video NLE Demo &amp; Petting Zoo. It was a good talk and I think a lot of information was exchanged. I&#8217;m sure it raised a bunch more questions than it answered, but that&#8217;s what happens next &#8211; here or Twitter or at the next event. Thanks for coming. If you missed it, here is the Presentation I gave:</p>
<p><iframe src="https://docs.google.com/present/embed?id=df6cdgxc_31d4fn7jdp" frameborder="0" width="410" height="342"></iframe></p>
<p>(And the <a href="https://docs.google.com/present/view?id=df6cdgxc_31d4fn7jdp" title="Google Presentation" target="_blank">link</a> in case the embed doesn&#8217;t work)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.buttonpusher.tv/2011/09/20/wifv-nle-demo-petting-zoo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.617 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-06-19 04:38:21 -->

<!-- Compression = gzip -->