<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Travelling Matt</title>
	<atom:link href="http://mattdavis.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://mattdavis.wordpress.com</link>
	<description>Making web movies around Europe for pleasure &#38; profit</description>
	<lastBuildDate>Mon, 06 May 2013 22:02:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Roll on the dead cats by Kevin</title>
		<link>http://mattdavis.wordpress.com/2013/05/06/roll-on-the-dead-cats/#comment-668</link>
		<dc:creator><![CDATA[Kevin]]></dc:creator>
		<pubDate>Mon, 06 May 2013 22:02:35 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/?p=640#comment-668</guid>
		<description><![CDATA[very nice analysis]]></description>
		<content:encoded><![CDATA[<p>very nice analysis</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BVE2013 &#8211; Did the dead cat just bounce? by BVE2013 &#8211; The Aftermath&#8230; &#124; defril</title>
		<link>http://mattdavis.wordpress.com/2013/02/26/bve2013-did-the-dead-cat-just-bounce/#comment-666</link>
		<dc:creator><![CDATA[BVE2013 &#8211; The Aftermath&#8230; &#124; defril]]></dc:creator>
		<pubDate>Wed, 24 Apr 2013 07:58:41 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/?p=635#comment-666</guid>
		<description><![CDATA[[...] and audio consultant&#160;Nick Way&#160;-&#160;www.nickway.co.uk).&#160;Incidently,&#160;Matt has an excellent post on BVE2013 on his blog.  Unfortunately, the room was less than a third full, partly, it seems because the brochure [...]]]></description>
		<content:encoded><![CDATA[<p>[...] and audio consultant&nbsp;Nick Way&nbsp;-&nbsp;www.nickway.co.uk).&nbsp;Incidently,&nbsp;Matt has an excellent post on BVE2013 on his blog.  Unfortunately, the room was less than a third full, partly, it seems because the brochure [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About by Denes Ujvari</title>
		<link>http://mattdavis.wordpress.com/about-2/#comment-665</link>
		<dc:creator><![CDATA[Denes Ujvari]]></dc:creator>
		<pubDate>Tue, 23 Apr 2013 05:37:29 +0000</pubDate>
		<guid isPermaLink="false">http://mattdavis.wordpress.com/about-2/#comment-665</guid>
		<description><![CDATA[Editing is a journey from chaos to order. It defies the second rule of thermodynamics which says everything must turn to chaos. 

That is GOLD, really like the web site
cheers
Denes]]></description>
		<content:encoded><![CDATA[<p>Editing is a journey from chaos to order. It defies the second rule of thermodynamics which says everything must turn to chaos. </p>
<p>That is GOLD, really like the web site<br />
cheers<br />
Denes</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blade and a J-cut, two bits! by Matt Davis</title>
		<link>http://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-213</link>
		<dc:creator><![CDATA[Matt Davis]]></dc:creator>
		<pubDate>Thu, 29 Sep 2011 18:56:26 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-213</guid>
		<description><![CDATA[Guys, owe you all virtual beer for this. Will practice until it&#039;s muscle memory.

BTW, any chance of a vision dissolve that doesn&#039;t touch audio? (grins, ducks, runs)]]></description>
		<content:encoded><![CDATA[<p>Guys, owe you all virtual beer for this. Will practice until it&#8217;s muscle memory.</p>
<p>BTW, any chance of a vision dissolve that doesn&#8217;t touch audio? (grins, ducks, runs)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blade and a J-cut, two bits! by Alex</title>
		<link>http://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-212</link>
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Thu, 29 Sep 2011 15:20:59 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-212</guid>
		<description><![CDATA[Chris Phrommayon reminded us (via Twitter) of the Shift-\ shortcut to select expanded audio edits. You can then use the  keys to roll the edit. Pity the trim tool can&#039;t be used to do this.]]></description>
		<content:encoded><![CDATA[<p>Chris Phrommayon reminded us (via Twitter) of the Shift-\ shortcut to select expanded audio edits. You can then use the  keys to roll the edit. Pity the trim tool can&#8217;t be used to do this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blade and a J-cut, two bits! by Scott Simmons</title>
		<link>http://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-211</link>
		<dc:creator><![CDATA[Scott Simmons]]></dc:creator>
		<pubDate>Thu, 29 Sep 2011 13:50:58 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-211</guid>
		<description><![CDATA[I think this post and the comments trying to explain how to do it shows that the magnetic timeline leaves something to be desired when it comes to BASIC editorial things we have to do over and over and over again. It goes back to my early argument that while a lot of FCPx technology is GREAT the app wasn&#039;t designed by editors who edit every day. That&#039;s its biggest overall fault.]]></description>
		<content:encoded><![CDATA[<p>I think this post and the comments trying to explain how to do it shows that the magnetic timeline leaves something to be desired when it comes to BASIC editorial things we have to do over and over and over again. It goes back to my early argument that while a lot of FCPx technology is GREAT the app wasn&#8217;t designed by editors who edit every day. That&#8217;s its biggest overall fault.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blade and a J-cut, two bits! by Alex</title>
		<link>http://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-210</link>
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Thu, 29 Sep 2011 12:57:42 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-210</guid>
		<description><![CDATA[So that&#039;s &#039;do your radio edit, expand all clips and use the trim tool to roll the video edits a little later&#039;

When clips are expanded, you can ripple the video and audio separately, but you can only roll video. 

As expanding clips makes the audio look like it becomes a set of connected clips, the FCP X magnetic timeline metaphor requires that you cannot roll audio edits, because independent connected video clip boundaries can&#039;t be rolled.

I propose then that the trim tool can be used to roll any edit - including two new cases - when editing audio in expanded clip mode and rolling the finish and start of adjacent connected clips or storylines.]]></description>
		<content:encoded><![CDATA[<p>So that&#8217;s &#8216;do your radio edit, expand all clips and use the trim tool to roll the video edits a little later&#8217;</p>
<p>When clips are expanded, you can ripple the video and audio separately, but you can only roll video. </p>
<p>As expanding clips makes the audio look like it becomes a set of connected clips, the FCP X magnetic timeline metaphor requires that you cannot roll audio edits, because independent connected video clip boundaries can&#8217;t be rolled.</p>
<p>I propose then that the trim tool can be used to roll any edit &#8211; including two new cases &#8211; when editing audio in expanded clip mode and rolling the finish and start of adjacent connected clips or storylines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blade and a J-cut, two bits! by Martin Baker</title>
		<link>http://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-209</link>
		<dc:creator><![CDATA[Martin Baker]]></dc:creator>
		<pubDate>Thu, 29 Sep 2011 10:26:37 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/2011/09/25/blade-and-a-j-cut-two-bits/#comment-209</guid>
		<description><![CDATA[It&#039;s easier than that. 

If you&#039;ve edited a sequence (sorry project...) for dialogue timing and want to work through and delay some video cuts, then the easiest way is to choose 
View &gt; Expand Audio/Video Clips &gt; For All
Then you can just select the trim tool and quickly delay any video edits you want without affecting the audio timing.

Alternatively if you&#039;ve edited for video timing and want to pull the incoming audio earlier so it starts on the outgoing video clip, then expand the clips as above, select the trim tool (don&#039;t forget you can temporarily select the trim tool by holding down T and clicking on an edit) and adjust the incoming side of the video only. I&#039;d say this trimming operation is actually easier in FCPX than it was in FCP7. No clip collisions to deal with.

The Apple help doc doesn&#039;t really help much because it shows an unusual example where a different number of frames are being trimmed off the incoming video and the outgoing audio.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s easier than that. </p>
<p>If you&#8217;ve edited a sequence (sorry project&#8230;) for dialogue timing and want to work through and delay some video cuts, then the easiest way is to choose<br />
View &gt; Expand Audio/Video Clips &gt; For All<br />
Then you can just select the trim tool and quickly delay any video edits you want without affecting the audio timing.</p>
<p>Alternatively if you&#8217;ve edited for video timing and want to pull the incoming audio earlier so it starts on the outgoing video clip, then expand the clips as above, select the trim tool (don&#8217;t forget you can temporarily select the trim tool by holding down T and clicking on an edit) and adjust the incoming side of the video only. I&#8217;d say this trimming operation is actually easier in FCPX than it was in FCP7. No clip collisions to deal with.</p>
<p>The Apple help doc doesn&#8217;t really help much because it shows an unusual example where a different number of frames are being trimmed off the incoming video and the outgoing audio.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on FCP-X &#8211; from &#8216;the editor&#8217;s NLE&#8217; to &#8216;the content creator&#8217;s editor&#8217;? by Matt Davis</title>
		<link>http://mattdavis.wordpress.com/2011/04/13/fcp-x-from-the-editors-nle-to-the-content-creators-editor/#comment-200</link>
		<dc:creator><![CDATA[Matt Davis]]></dc:creator>
		<pubDate>Fri, 15 Apr 2011 07:04:55 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/2011/04/13/fcp-x-from-the-editors-nle-to-the-content-creators-editor/#comment-200</guid>
		<description><![CDATA[Firstly, remember this was a sneak peek, not an official launch, so details are sketchy and still subject to change. Frustrating, but it&#039;s the way it is.

That makes it hard to be specific on how FCP X will implement metadata. Adobe Premiere &#039;gives good demo&#039; on this front, specifically using a transcript to tie into video. MP4 does have &#039;text containers&#039; within its file structure, and this should be a source of searching. I don&#039;t want to use words like &#039;should&#039; here, but again, that&#039;s reality at the moment.

Metadata can also mean things like &#039;shot markers&#039; and &#039;essence markers&#039; - Sony cameras can insert these markers both on a shot by shot and a moment by moment basis, but FCP7 and below chuck this info out. I can insert useful metadata like the name and affiliation info of an interviewee into the QT-wrapped MXF, viewable in QT Player. FCP 7 and below ignores this info, FCP X should - &#039;SHOULD&#039; - pick this up.

Will the metadata fill in the Google/YouTube forms? Maybe, though I sincerely hope there&#039;ll be more to it than that. I&#039;m still playing with YouTube subtitles for a bit of video specific SEO, and I hope there will be more space for transcripts and so on.]]></description>
		<content:encoded><![CDATA[<p>Firstly, remember this was a sneak peek, not an official launch, so details are sketchy and still subject to change. Frustrating, but it&#8217;s the way it is.</p>
<p>That makes it hard to be specific on how FCP X will implement metadata. Adobe Premiere &#8216;gives good demo&#8217; on this front, specifically using a transcript to tie into video. MP4 does have &#8216;text containers&#8217; within its file structure, and this should be a source of searching. I don&#8217;t want to use words like &#8216;should&#8217; here, but again, that&#8217;s reality at the moment.</p>
<p>Metadata can also mean things like &#8216;shot markers&#8217; and &#8216;essence markers&#8217; &#8211; Sony cameras can insert these markers both on a shot by shot and a moment by moment basis, but FCP7 and below chuck this info out. I can insert useful metadata like the name and affiliation info of an interviewee into the QT-wrapped MXF, viewable in QT Player. FCP 7 and below ignores this info, FCP X should &#8211; &#8216;SHOULD&#8217; &#8211; pick this up.</p>
<p>Will the metadata fill in the Google/YouTube forms? Maybe, though I sincerely hope there&#8217;ll be more to it than that. I&#8217;m still playing with YouTube subtitles for a bit of video specific SEO, and I hope there will be more space for transcripts and so on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on FCP-X &#8211; from &#8216;the editor&#8217;s NLE&#8217; to &#8216;the content creator&#8217;s editor&#8217;? by video4marketing</title>
		<link>http://mattdavis.wordpress.com/2011/04/13/fcp-x-from-the-editors-nle-to-the-content-creators-editor/#comment-199</link>
		<dc:creator><![CDATA[video4marketing]]></dc:creator>
		<pubDate>Fri, 15 Apr 2011 01:14:48 +0000</pubDate>
		<guid isPermaLink="false">https://mattdavis.wordpress.com/2011/04/13/fcp-x-from-the-editors-nle-to-the-content-creators-editor/#comment-199</guid>
		<description><![CDATA[I was thinking along those lines too.

Just one question; does it mean now, with metadata, that video uploaded on You Tube for example will be indexed by Google by looking into those metadata as text, what video was lacking so far (at least that’s my understanding)?

Or, I got it wrong, and metadata is simply just to help in collaboration between applications in post production environment?]]></description>
		<content:encoded><![CDATA[<p>I was thinking along those lines too.</p>
<p>Just one question; does it mean now, with metadata, that video uploaded on You Tube for example will be indexed by Google by looking into those metadata as text, what video was lacking so far (at least that’s my understanding)?</p>
<p>Or, I got it wrong, and metadata is simply just to help in collaboration between applications in post production environment?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
