<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for Nice Dissolve Blog</title>
	<atom:link href="http://blog.nicedissolve.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nicedissolve.com</link>
	<description>digital cinema production</description>
	<lastBuildDate>Tue, 31 Jan 2012 20:55:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Apple does the iteration thing with FCP X by Marcus Samuel-Gaskin</title>
		<link>http://blog.nicedissolve.com/2012/01/apple-does-the-iteration-thing-with-fcp-x/#comment-2851</link>
		<dc:creator>Marcus Samuel-Gaskin</dc:creator>
		<pubDate>Tue, 31 Jan 2012 20:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1157#comment-2851</guid>
		<description>&lt;p&gt;Apple&#039;s doing its &quot;Roll&quot;-ing thing that Daring fireball talked about. Just as I and any reasonable person in the Postproduction world would have expected..Nice update.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Apple&#8217;s doing its &#8220;Roll&#8221;-ing thing that Daring fireball talked about. Just as I and any reasonable person in the Postproduction world would have expected..Nice update.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple does the iteration thing with FCP X by Chris Kenny</title>
		<link>http://blog.nicedissolve.com/2012/01/apple-does-the-iteration-thing-with-fcp-x/#comment-2850</link>
		<dc:creator>Chris Kenny</dc:creator>
		<pubDate>Tue, 31 Jan 2012 19:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1157#comment-2850</guid>
		<description>&lt;p&gt;Claiming that Apple updated FCP 7 &quot;a few times&quot; and then killed it is basically trolling. Apple maintained the product for 12 years and then replaced it when the underlying technical realities (the need to move to Cocoa + 64-bit and add better GPU and multicore optimization) required it to be rewritten.&lt;/p&gt;

&lt;p&gt;Shake was an outside acquisition. I agree that Apple&#039;s track record with maintaining those long-term is spotty. You&#039;ve got Logic on one side, Color and Shake on the other. If there&#039;s an app you really like and Apple buys it, you should probably worry. But this isn&#039;t strictly relevant to FCP X.&lt;/p&gt;

&lt;p&gt;And not to put too fine a point on it, but the &quot;too little too late&quot; is precisely the sort of short-term nonsense Apple should (and does) ignore. The idea that a significant number of people making an NLE decision in five years (or even 18 months) will care about FCP X&#039;s rocky introduction isn&#039;t very plausible. Most people aren&#039;t paying attention to the Internet drama; they&#039;ll buy based on what product offers what they deem to be the best price/features/interface when they&#039;re ready to buy, and once video monitoring comes out of beta and various third parties support FCP X&#039;s XML a little better, there are few users for whom FCP X won&#039;t be right there in the mix.&lt;/p&gt;

&lt;p&gt;As for Apple leaving FCP 7 importing to third parties... 7toX is a great effort, and seems to be a really useful tool, but look at the limitations. A lot of these are an unavoidable consequence of conceptual differences between how FCP 7 and FCP X work. It&#039;s fairly clear, given these limitations, why Apple might not be comfortable including this as an official feature.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Claiming that Apple updated FCP 7 &#8220;a few times&#8221; and then killed it is basically trolling. Apple maintained the product for 12 years and then replaced it when the underlying technical realities (the need to move to Cocoa + 64-bit and add better GPU and multicore optimization) required it to be rewritten.</p>

<p>Shake was an outside acquisition. I agree that Apple&#8217;s track record with maintaining those long-term is spotty. You&#8217;ve got Logic on one side, Color and Shake on the other. If there&#8217;s an app you really like and Apple buys it, you should probably worry. But this isn&#8217;t strictly relevant to FCP X.</p>

<p>And not to put too fine a point on it, but the &#8220;too little too late&#8221; is precisely the sort of short-term nonsense Apple should (and does) ignore. The idea that a significant number of people making an NLE decision in five years (or even 18 months) will care about FCP X&#8217;s rocky introduction isn&#8217;t very plausible. Most people aren&#8217;t paying attention to the Internet drama; they&#8217;ll buy based on what product offers what they deem to be the best price/features/interface when they&#8217;re ready to buy, and once video monitoring comes out of beta and various third parties support FCP X&#8217;s XML a little better, there are few users for whom FCP X won&#8217;t be right there in the mix.</p>

<p>As for Apple leaving FCP 7 importing to third parties&#8230; 7toX is a great effort, and seems to be a really useful tool, but look at the limitations. A lot of these are an unavoidable consequence of conceptual differences between how FCP 7 and FCP X work. It&#8217;s fairly clear, given these limitations, why Apple might not be comfortable including this as an official feature.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apple does the iteration thing with FCP X by Jonah Lee Walker</title>
		<link>http://blog.nicedissolve.com/2012/01/apple-does-the-iteration-thing-with-fcp-x/#comment-2849</link>
		<dc:creator>Jonah Lee Walker</dc:creator>
		<pubDate>Tue, 31 Jan 2012 19:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1157#comment-2849</guid>
		<description>&lt;p&gt;Apple does not usually play the long game on pro software. They update a few times and then kill it, like they did with Shake, and now Final Cut Pro 7. Yes it is great that they are adding some of their promised features to FCP X, even if some are only in beta, but I think it is too little too late for much of the professional market.&lt;/p&gt;

&lt;p&gt;And yes I am glad that you can import FCP 7 projects, but it is through a third party application and via XML, well I can already do that into Premiere Pro without a 3rd party application.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Apple does not usually play the long game on pro software. They update a few times and then kill it, like they did with Shake, and now Final Cut Pro 7. Yes it is great that they are adding some of their promised features to FCP X, even if some are only in beta, but I think it is too little too late for much of the professional market.</p>

<p>And yes I am glad that you can import FCP 7 projects, but it is through a third party application and via XML, well I can already do that into Premiere Pro without a 3rd party application.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on How unclear use of language has caused two weeks of panic about FCP X by Hans Charles</title>
		<link>http://blog.nicedissolve.com/2011/07/apples-focus/#comment-2389</link>
		<dc:creator>Hans Charles</dc:creator>
		<pubDate>Wed, 14 Dec 2011 20:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=873#comment-2389</guid>
		<description>&lt;p&gt;John,  I&#039;m going to post you response to my students so they can have a brief and amusing history on editing and a peek into the future.  Thank you for your contribution.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>John,  I&#8217;m going to post you response to my students so they can have a brief and amusing history on editing and a peek into the future.  Thank you for your contribution.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on The magnetic timeline and reasonable defaults by Luke</title>
		<link>http://blog.nicedissolve.com/2011/07/the-magnetic-timeline-and-reasonable-defaults/#comment-2054</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Wed, 19 Oct 2011 01:29:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=831#comment-2054</guid>
		<description>&lt;p&gt;It&#039;s been ages since this post, when can we expect some articles about the post-FCPX debacle. Also, I wouldn&#039;t mind an in-depth summary of the first major update! If that&#039;s not too much to ask... :P&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It&#8217;s been ages since this post, when can we expect some articles about the post-FCPX debacle. Also, I wouldn&#8217;t mind an in-depth summary of the first major update! If that&#8217;s not too much to ask&#8230; <img src='http://blog.nicedissolve.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by Nivardo</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1621</link>
		<dc:creator>Nivardo</dc:creator>
		<pubDate>Thu, 28 Jul 2011 04:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1621</guid>
		<description>&lt;p&gt;@Chris&lt;/p&gt;

&lt;p&gt;&quot;... I agree that Apple’s primary focus is not on film and TV editors, but it never was. This didn’t stop FCP from becoming a very compelling tool for our market, and I don’t think it will stop FCP X from becoming one.&quot;&lt;/p&gt;

&lt;p&gt;Are you saying that this was all a coincidence?&lt;/p&gt;

&lt;p&gt;http://www.youtube.com/crazyproapple&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Chris</p>

<p>&#8220;&#8230; I agree that Apple’s primary focus is not on film and TV editors, but it never was. This didn’t stop FCP from becoming a very compelling tool for our market, and I don’t think it will stop FCP X from becoming one.&#8221;</p>

<p>Are you saying that this was all a coincidence?</p>

<p><a href="http://www.youtube.com/crazyproapple" rel="nofollow">http://www.youtube.com/crazyproapple</a></p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on On risk, failure, and the future of Final Cut Pro by Taylor</title>
		<link>http://blog.nicedissolve.com/2011/07/on-risk-failure-and-the-future-of-final-cut-pro/#comment-1597</link>
		<dc:creator>Taylor</dc:creator>
		<pubDate>Sun, 17 Jul 2011 20:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=842#comment-1597</guid>
		<description>&lt;p&gt;I totally understand that some features are missing, and that is typical of the 1.o release. That&#039;s a given.&lt;/p&gt;

&lt;p&gt;However, the amount of professional features lost, combined with the immediate removal v7.... That&#039;s irresponsible, nay, adversarial to the user base it has built up in the last decade. All the money invested in hardware and software, MILLIONS, and Apple treats it&#039;s base of customer like this? No thanks Jobs. I&#039;ll stick with my avid. It still is a better editor.&lt;/p&gt;

&lt;p&gt;And Avid must be thrilled, because all the professional jobs are going back to them. Maybe a few obscure smaller houses moving to premiere for the integration.&lt;/p&gt;

&lt;p&gt;Personaly, I&#039;ve used X. I reccomended it to my gf, so she cut cut cutesy lil home projects. But I would be unable to recommend it for anything else. It&#039;s not a 1.0 that was ready for release. It probably needed a full other year.&lt;/p&gt;

&lt;p&gt;And some actual editors trying it out.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I totally understand that some features are missing, and that is typical of the 1.o release. That&#8217;s a given.</p>

<p>However, the amount of professional features lost, combined with the immediate removal v7&#8230;. That&#8217;s irresponsible, nay, adversarial to the user base it has built up in the last decade. All the money invested in hardware and software, MILLIONS, and Apple treats it&#8217;s base of customer like this? No thanks Jobs. I&#8217;ll stick with my avid. It still is a better editor.</p>

<p>And Avid must be thrilled, because all the professional jobs are going back to them. Maybe a few obscure smaller houses moving to premiere for the integration.</p>

<p>Personaly, I&#8217;ve used X. I reccomended it to my gf, so she cut cut cutesy lil home projects. But I would be unable to recommend it for anything else. It&#8217;s not a 1.0 that was ready for release. It probably needed a full other year.</p>

<p>And some actual editors trying it out.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting inside the magnetic timeline&#8217;s head by BenB</title>
		<link>http://blog.nicedissolve.com/2011/06/getting-inside-magnetic-timeline/#comment-1593</link>
		<dc:creator>BenB</dc:creator>
		<pubDate>Sun, 17 Jul 2011 03:37:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=725#comment-1593</guid>
		<description>&lt;p&gt;You can also Connect the audio clip below/above the Primary Storyline, and make it a Secondary Storyline, if you need the magnatism in more than one line of clips.  You can also make Compound clips to keep a set section in tact so it won&#039;t get messed up.  There&#039;s a dozen ways to do it, once you understand how the tools work.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You can also Connect the audio clip below/above the Primary Storyline, and make it a Secondary Storyline, if you need the magnatism in more than one line of clips.  You can also make Compound clips to keep a set section in tact so it won&#8217;t get messed up.  There&#8217;s a dozen ways to do it, once you understand how the tools work.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting inside the magnetic timeline&#8217;s head by Nice Dissolve Blog &#124; The magnetic timeline and reasonable defaults</title>
		<link>http://blog.nicedissolve.com/2011/06/getting-inside-magnetic-timeline/#comment-1591</link>
		<dc:creator>Nice Dissolve Blog &#124; The magnetic timeline and reasonable defaults</dc:creator>
		<pubDate>Sat, 16 Jul 2011 18:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=725#comment-1591</guid>
		<description>&lt;p&gt;[...] to make it easier to edit, but in the process it removes control from the editor. Well, I&#8217;ve already addressed how this is not really quite accurate with respect to its clip collision behavior. But what about [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] to make it easier to edit, but in the process it removes control from the editor. Well, I&#8217;ve already addressed how this is not really quite accurate with respect to its clip collision behavior. But what about [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting inside the magnetic timeline&#8217;s head by Oren Shomron</title>
		<link>http://blog.nicedissolve.com/2011/06/getting-inside-magnetic-timeline/#comment-1586</link>
		<dc:creator>Oren Shomron</dc:creator>
		<pubDate>Fri, 15 Jul 2011 23:16:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=725#comment-1586</guid>
		<description>&lt;p&gt;You can move the connection point to the end of the music track instead of the beginning. Select the track and CMD-OPTION-Click at the new connectio point. Now you can rearrange earlier clips to your heart&#039;s content, and the ending will remain in sync.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You can move the connection point to the end of the music track instead of the beginning. Select the track and CMD-OPTION-Click at the new connectio point. Now you can rearrange earlier clips to your heart&#8217;s content, and the ending will remain in sync.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting inside the magnetic timeline&#8217;s head by Chris Kenny</title>
		<link>http://blog.nicedissolve.com/2011/06/getting-inside-magnetic-timeline/#comment-1583</link>
		<dc:creator>Chris Kenny</dc:creator>
		<pubDate>Fri, 15 Jul 2011 12:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=725#comment-1583</guid>
		<description>&lt;p&gt;M: put your music clip in the primary storyline. Place video clips above it as connected clips, grouped into secondary storylines if appropriate.&lt;/p&gt;

&lt;p&gt;This is not some crazy workaround. It makes sense conceptually for a music video, because the music is what drives the timing of the entire edit, the same way, on another type of project, interview footage in the primary storyline might drive the timing of cutaways attached as connected clips.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>M: put your music clip in the primary storyline. Place video clips above it as connected clips, grouped into secondary storylines if appropriate.</p>

<p>This is not some crazy workaround. It makes sense conceptually for a music video, because the music is what drives the timing of the entire edit, the same way, on another type of project, interview footage in the primary storyline might drive the timing of cutaways attached as connected clips.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting inside the magnetic timeline&#8217;s head by -M</title>
		<link>http://blog.nicedissolve.com/2011/06/getting-inside-magnetic-timeline/#comment-1582</link>
		<dc:creator>-M</dc:creator>
		<pubDate>Fri, 15 Jul 2011 10:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=725#comment-1582</guid>
		<description>&lt;p&gt;Ok.. well, I&#039;ve been using FCPX almost exclusively since it arrived (despite my upset) so this is not a knee jerk reaction and I can tell you I still don&#039;t like the mag.timeline.  Yes I want control.  Explain to me how I can (for a music video) add an audio track that I never want to move, but my associated (related) clips might get moved and therefore can easily adjust my audio or delete my audio etc etc.  Its just annoying and unnecessary.  And this is just a minor example.  Lets say I have built my ending exactly where my audio, graphics etc.. and then mix my earlier clips.. well know everything just got screwed up.  How&#039;s that for cool.  And no the &quot;P&quot; tool doesn&#039;t help a dang bit here.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ok.. well, I&#8217;ve been using FCPX almost exclusively since it arrived (despite my upset) so this is not a knee jerk reaction and I can tell you I still don&#8217;t like the mag.timeline.  Yes I want control.  Explain to me how I can (for a music video) add an audio track that I never want to move, but my associated (related) clips might get moved and therefore can easily adjust my audio or delete my audio etc etc.  Its just annoying and unnecessary.  And this is just a minor example.  Lets say I have built my ending exactly where my audio, graphics etc.. and then mix my earlier clips.. well know everything just got screwed up.  How&#8217;s that for cool.  And no the &#8220;P&#8221; tool doesn&#8217;t help a dang bit here.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by AmyBG</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1574</link>
		<dc:creator>AmyBG</dc:creator>
		<pubDate>Thu, 14 Jul 2011 00:15:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1574</guid>
		<description>&lt;p&gt;Well said Chris, I have been following the reaction to FCP X for my work as an editor and it is really refreshing to see this perspective voiced so eloquently.&lt;/p&gt;

&lt;p&gt;I haven&#039;t used FCP X yet, so I can&#039;t say for sure exactly what I think, but after looking at how each new features works I think it is revolutionary and that&#039;s part of what also makes it frustrating for people. You get used to doing something one way, so when someone comes out with a different way of doing it there is bound to be adjusting (or criticism).&lt;/p&gt;

&lt;p&gt;I can&#039;t see it being widely used in the industry for years, but I bet we will start to see other software adapting or building on elements of FCP X.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Well said Chris, I have been following the reaction to FCP X for my work as an editor and it is really refreshing to see this perspective voiced so eloquently.</p>

<p>I haven&#8217;t used FCP X yet, so I can&#8217;t say for sure exactly what I think, but after looking at how each new features works I think it is revolutionary and that&#8217;s part of what also makes it frustrating for people. You get used to doing something one way, so when someone comes out with a different way of doing it there is bound to be adjusting (or criticism).</p>

<p>I can&#8217;t see it being widely used in the industry for years, but I bet we will start to see other software adapting or building on elements of FCP X.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking: Final Cut Pro X is an Apple product by Steve</title>
		<link>http://blog.nicedissolve.com/2011/06/breaking-final-cut-pro-x-is-an-apple-product/#comment-1567</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 12 Jul 2011 05:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=675#comment-1567</guid>
		<description>&lt;p&gt;Apple is obviously going for the millions of wanna be indie filmmakers with the cheap fcpX rather than the thousands of pros. Just as Panasonic, Sony and Canon whip out latest greatest low cost cameras for that market it is Apple&#039;s intent to cash in too. I&#039;ve been with apple from day one, defending them against the PC clowns, but I&#039;ve got to tell you that I hate apple for disrespecting me and the other pros.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Apple is obviously going for the millions of wanna be indie filmmakers with the cheap fcpX rather than the thousands of pros. Just as Panasonic, Sony and Canon whip out latest greatest low cost cameras for that market it is Apple&#8217;s intent to cash in too. I&#8217;ve been with apple from day one, defending them against the PC clowns, but I&#8217;ve got to tell you that I hate apple for disrespecting me and the other pros.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by Steve</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1565</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 11 Jul 2011 21:25:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1565</guid>
		<description>&lt;p&gt;Exactly.  Too many people don&#039;t seem to understand what it means to &quot;start over.&quot;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Exactly.  Too many people don&#8217;t seem to understand what it means to &#8220;start over.&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by Steve</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1564</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 11 Jul 2011 21:10:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1564</guid>
		<description>&lt;p&gt;Are you not also teaching your students the uncertainty that riddles the many parts  of this industry?  There are always ways around problems like this.  FCP7 can still be used (which many seem to forget) and there are plenty of jobs freelance jobs out there for it (WAY more than Premiere could ever dream of).  No matter what you teach your students, if you teach the FCP well, they&#039;ll learn Avid from a book with few problems.  If you teach them Avid and Apple does in fact become the future of post, the opposite will work out just as smoothly.  If learning FCP right as something like this happens were to dishearten a graduate enough that they can&#039;t bear to learn another program and decide instead on another profession, the problem doesn&#039;t lie with the NLE.  If the student or graduate loves what they&#039;re doing, they will work with the tools they are given.  They&#039;re not even overly invested in software at that point.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Are you not also teaching your students the uncertainty that riddles the many parts  of this industry?  There are always ways around problems like this.  FCP7 can still be used (which many seem to forget) and there are plenty of jobs freelance jobs out there for it (WAY more than Premiere could ever dream of).  No matter what you teach your students, if you teach the FCP well, they&#8217;ll learn Avid from a book with few problems.  If you teach them Avid and Apple does in fact become the future of post, the opposite will work out just as smoothly.  If learning FCP right as something like this happens were to dishearten a graduate enough that they can&#8217;t bear to learn another program and decide instead on another profession, the problem doesn&#8217;t lie with the NLE.  If the student or graduate loves what they&#8217;re doing, they will work with the tools they are given.  They&#8217;re not even overly invested in software at that point.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by Chris Kenny</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1563</link>
		<dc:creator>Chris Kenny</dc:creator>
		<pubDate>Mon, 11 Jul 2011 20:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1563</guid>
		<description>&lt;p&gt;People keep conflating &quot;Apple aimed at market X&quot; with &quot;Market X was Apple&#039;s primary focus&quot;. Yes, Apple added quite a few features to &#039;classic&#039; FCP over the years to support film/TV editors. But these features were added only after more mainstream workflows. &lt;i&gt;Early&lt;/i&gt; versions of FCP heavily focused on MiniDV workflow, at the time the emerging consumer/prosumer/event video standard, essentially unheard of in film/TV circles.&lt;/p&gt;

&lt;p&gt;Apple is following the same pattern with FCP X: shipping a release with features in place for a more mainstream market first, and then proceeding to add features for film/TV editors. Except this time, based on what they&#039;ve said, they seem to be planning to add those features more quickly than they did last time around.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>People keep conflating &#8220;Apple aimed at market X&#8221; with &#8220;Market X was Apple&#8217;s primary focus&#8221;. Yes, Apple added quite a few features to &#8216;classic&#8217; FCP over the years to support film/TV editors. But these features were added only after more mainstream workflows. <i>Early</i> versions of FCP heavily focused on MiniDV workflow, at the time the emerging consumer/prosumer/event video standard, essentially unheard of in film/TV circles.</p>

<p>Apple is following the same pattern with FCP X: shipping a release with features in place for a more mainstream market first, and then proceeding to add features for film/TV editors. Except this time, based on what they&#8217;ve said, they seem to be planning to add those features more quickly than they did last time around.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by Shane Ross</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1562</link>
		<dc:creator>Shane Ross</dc:creator>
		<pubDate>Mon, 11 Jul 2011 20:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1562</guid>
		<description>&lt;p&gt;Robert, story telling is one thing, but working with all the tools in the shop is another.  Yes, I can tell the same stories with iMovie as I do with FCP, but broadcast and film standards demand that I mix audio with a professional using certain tools, and that I color correct nicely and properly so that I not only meet broadcast specs, but so that I can highlight certain areas, and push the colors as far as I can. iMovie doesn&#039;t allow that, so I need a tool that does.  FCP X doesn&#039;t do that, so I stick to the tools that do.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Robert, story telling is one thing, but working with all the tools in the shop is another.  Yes, I can tell the same stories with iMovie as I do with FCP, but broadcast and film standards demand that I mix audio with a professional using certain tools, and that I color correct nicely and properly so that I not only meet broadcast specs, but so that I can highlight certain areas, and push the colors as far as I can. iMovie doesn&#8217;t allow that, so I need a tool that does.  FCP X doesn&#8217;t do that, so I stick to the tools that do.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by Shane Ross</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1561</link>
		<dc:creator>Shane Ross</dc:creator>
		<pubDate>Mon, 11 Jul 2011 20:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1561</guid>
		<description>&lt;p&gt;&quot;Dylan, I agree that Apple’s primary focus is not on film and TV editors, but it never was.&quot;&lt;/p&gt;

&lt;p&gt;Bullpucky.  Then why did Apple have a PRO PAGE on the website featuring FCP?  Showcasing Bunim/Murray as a large installation with over 100 seats...working on broadcast shows?  And showcasing David Fincher and ZODIAK...Walter Murch and Cold Mountain...the Coen Brothers?  It TOTALLY targetted the pro market.  And showed off the fact that it HAD the pro market.  &quot;Hey, look, if these hot shots can use FCP for TV and feature film, just imagine what you can do with it!&quot;  If it didn&#039;t want the pro market, it wouldn&#039;t have fixed OMF export to include levels and pans, it would have left people to use Automatic Duck.  It wouldn&#039;t have included EDL export/import.  It wouldn&#039;t have bought Color and implimented it into the Studio package.  It wouldn&#039;t ONLY work with professional broadcast frame rates, like 23.98, 29.97, 59.94...25 and 50.  It would allow people to work at 10fps, 15fps.&lt;/p&gt;

&lt;p&gt;No, Apple totally aimed at the professional market...but then realized that that isn&#039;t where the money is, so they went after the larger market...web video producers, DVD makers...people editing family video.  They could care less about professionals.  Not the buying and killing of SHAKE...COLOR...DVD Studio Pro.&lt;/p&gt;

&lt;p&gt;Sorry, you are wrong here.  Apple made FCP X for the amateur filmmakers and very low end professionals.  While Avid and Adobe do make changes...and faster now that they see that people demand change faster...yet don&#039;t leave behind features that professionals rely on.&lt;/p&gt;

&lt;p&gt;But, Apple doesn&#039;t care that they lost the professional market.  We are the smallest blip on their radar.  BUT, what they did do is move a lot of us back to Avid, or over to Adobe, and that will help those companies survive, and thrive.  Because they are ONLY focused on the professionals, and not on selling iPads.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&#8220;Dylan, I agree that Apple’s primary focus is not on film and TV editors, but it never was.&#8221;</p>

<p>Bullpucky.  Then why did Apple have a PRO PAGE on the website featuring FCP?  Showcasing Bunim/Murray as a large installation with over 100 seats&#8230;working on broadcast shows?  And showcasing David Fincher and ZODIAK&#8230;Walter Murch and Cold Mountain&#8230;the Coen Brothers?  It TOTALLY targetted the pro market.  And showed off the fact that it HAD the pro market.  &#8220;Hey, look, if these hot shots can use FCP for TV and feature film, just imagine what you can do with it!&#8221;  If it didn&#8217;t want the pro market, it wouldn&#8217;t have fixed OMF export to include levels and pans, it would have left people to use Automatic Duck.  It wouldn&#8217;t have included EDL export/import.  It wouldn&#8217;t have bought Color and implimented it into the Studio package.  It wouldn&#8217;t ONLY work with professional broadcast frame rates, like 23.98, 29.97, 59.94&#8230;25 and 50.  It would allow people to work at 10fps, 15fps.</p>

<p>No, Apple totally aimed at the professional market&#8230;but then realized that that isn&#8217;t where the money is, so they went after the larger market&#8230;web video producers, DVD makers&#8230;people editing family video.  They could care less about professionals.  Not the buying and killing of SHAKE&#8230;COLOR&#8230;DVD Studio Pro.</p>

<p>Sorry, you are wrong here.  Apple made FCP X for the amateur filmmakers and very low end professionals.  While Avid and Adobe do make changes&#8230;and faster now that they see that people demand change faster&#8230;yet don&#8217;t leave behind features that professionals rely on.</p>

<p>But, Apple doesn&#8217;t care that they lost the professional market.  We are the smallest blip on their radar.  BUT, what they did do is move a lot of us back to Avid, or over to Adobe, and that will help those companies survive, and thrive.  Because they are ONLY focused on the professionals, and not on selling iPads.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Apple is worth defending by Paul Wojciechowski</title>
		<link>http://blog.nicedissolve.com/2011/07/why-apple-is-worth-defending/#comment-1555</link>
		<dc:creator>Paul Wojciechowski</dc:creator>
		<pubDate>Sun, 10 Jul 2011 04:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nicedissolve.com/?p=1027#comment-1555</guid>
		<description>&lt;p&gt;One thing I know about the film industry is that they are not a patient bunch.  They want everything f#@$ing yesterday.  So if you really think film companies are going to wait and be patient for FCP to &quot;evolve&quot;, you&#039;ve got another thing coming.  They have no time for &quot;shortcomeings.&quot;  And if I were Avid and Premiere right now I would be licking my chops and saying &quot;OK boys, here&#039;s our opportunity. Let&#039;s make FCP 8 and put our name on it.  Maybe FCP will meet expectations in the future, but I wouldm&#039;t be surprised if  Hollywood will have moved on.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>One thing I know about the film industry is that they are not a patient bunch.  They want everything f#@$ing yesterday.  So if you really think film companies are going to wait and be patient for FCP to &#8220;evolve&#8221;, you&#8217;ve got another thing coming.  They have no time for &#8220;shortcomeings.&#8221;  And if I were Avid and Premiere right now I would be licking my chops and saying &#8220;OK boys, here&#8217;s our opportunity. Let&#8217;s make FCP 8 and put our name on it.  Maybe FCP will meet expectations in the future, but I wouldm&#8217;t be surprised if  Hollywood will have moved on.</p>]]></content:encoded>
	</item>
</channel>
</rss>

