<?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:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Final Cut Pro &#8211; Wade Tregaskis</title>
	<atom:link href="https://wadetregaskis.com/tags/final-cut-pro/feed/" rel="self" type="application/rss+xml" />
	<link>https://wadetregaskis.com</link>
	<description></description>
	<lastBuildDate>Fri, 23 Jan 2026 02:51:13 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://wadetregaskis.com/wp-content/uploads/2016/03/Stitch-512x512-1-256x256.png</url>
	<title>Final Cut Pro &#8211; Wade Tregaskis</title>
	<link>https://wadetregaskis.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">226351702</site>	<item>
		<title>Cross Dissolve only the video, not the audio, in Final Cut Pro</title>
		<link>https://wadetregaskis.com/cross-dissolve-only-the-video-not-the-audio-in-final-cut-pro/</link>
					<comments>https://wadetregaskis.com/cross-dissolve-only-the-video-not-the-audio-in-final-cut-pro/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Fri, 23 Jan 2026 02:51:10 +0000</pubDate>
				<category><![CDATA[Howto]]></category>
		<category><![CDATA[Cross Dissolve]]></category>
		<category><![CDATA[Final Cut Pro]]></category>
		<guid isPermaLink="false">https://wadetregaskis.com/?p=8689</guid>

					<description><![CDATA[When you drop a Cross Dissolve transition onto a clip in Final Cut Pro it applies the transition to both video and audio. That&#8217;s great &#8211; typically that&#8217;s what you want &#8211; but sometimes you don&#8217;t want that. Contrary to what you might read online or what the dumb robots might tell you (because they&#8230; <a class="read-more-link" href="https://wadetregaskis.com/cross-dissolve-only-the-video-not-the-audio-in-final-cut-pro/" data-wpel-link="internal">Read more</a>]]></description>
										<content:encoded><![CDATA[
<p>When you drop a Cross Dissolve transition onto a clip in Final Cut Pro it applies the transition to both video and audio.  That&#8217;s great &#8211; typically that&#8217;s what you want &#8211; but sometimes you <em>don&#8217;t</em> want that.</p>



<p>Contrary to what you might <a href="https://www.reddit.com/r/finalcutpro/comments/q9fwlr/how_do_i_cross_dissolve_the_image_but_not_the/" data-wpel-link="external" target="_blank" rel="external noopener">read online</a> or what the dumb robots might tell you (because they just plagiarise it from those same Reddit threads and YouTube videos), you can&#8217;t simply &#8220;Expand Audio&#8221; and apply the Cross Dissolve to just the video lane<sup data-fn="fe74553d-2443-42af-bf51-d9dc058a400d" class="fn"><a href="#fe74553d-2443-42af-bf51-d9dc058a400d" id="fe74553d-2443-42af-bf51-d9dc058a400d-link">1</a></sup>.  You <em>can</em> detach the audio entirely, but that&#8217;s heavy-handed and may make your life much harder downstream (since Final Cut Pro will then treat the separated audio and video as completely independent clips).</p>



<p>Actually, there&#8217;s a simple &#8216;hack&#8217; which works:</p>



<ol class="wp-block-list">
<li><strong>Drag the Cross Dissolve (or similar) onto the clip</strong>.</li>



<li><strong>Select the clip and &#8220;Expand Audio&#8221;</strong> (from the Clip menu, contextual pop-up menu, or by pressing ⌃S).  This is really just to get access to the audio track that&#8217;s otherwise hidden under the Cross Dissolve.</li>



<li><strong>Carefully drag the audio fade-in handle to the edge of the clip</strong>, to <em>exactly</em> where the tooltip says the offset is zero.  Don&#8217;t go too far &#8211; if you go over the end of the clip it&#8217;ll re-install the audio fade!</li>
</ol>



<p>It <em>feels</em> like that shouldn&#8217;t work &#8211; like it&#8217;s actually a subtle bug where Final Cut Pro actually intends to ignore your zero-duration fade-in and reset it back to the full length, like it does if you drag just a pixel too far.  But hey, thank goodness for some bugs!</p>



<figure class="wp-block-video"><video height="248" style="aspect-ratio: 774 / 248;" width="774" autoplay loop muted preload="auto" src="https://wadetregaskis.com/wp-content/uploads/2026/01/How-to-apply-a-Cross-Dissolve-to-only-the-video-of-a-clip-not-the-audio-in-Final-Cut-Pro-AV1.mp4" playsinline></video></figure>


<ol class="wp-block-footnotes"><li id="fe74553d-2443-42af-bf51-d9dc058a400d">Maybe this did work in an earlier version of Final Cut Pro, but it definitely does not in 11.2. <a href="#fe74553d-2443-42af-bf51-d9dc058a400d-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>]]></content:encoded>
					
					<wfw:commentRss>https://wadetregaskis.com/cross-dissolve-only-the-video-not-the-audio-in-final-cut-pro/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">8689</post-id>	</item>
		<item>
		<title>Better image stabilisation in Final Cut Pro using Object Tracking</title>
		<link>https://wadetregaskis.com/better-image-stabilisation-in-final-cut-pro-using-object-tracking/</link>
					<comments>https://wadetregaskis.com/better-image-stabilisation-in-final-cut-pro-using-object-tracking/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Sun, 18 Jan 2026 20:22:54 +0000</pubDate>
				<category><![CDATA[Howto]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Final Cut Pro]]></category>
		<category><![CDATA[Object Tracking]]></category>
		<category><![CDATA[stabilisation]]></category>
		<guid isPermaLink="false">https://wadetregaskis.com/?p=8656</guid>

					<description><![CDATA[This is basically a short written set of instructions derived from Cody Wanner&#8216;s YouTube video on the topic, refined a little for simplicity and updated for the newer GUI in more recent versions of Final Cut Pro. So feel free to view that video if you prefer that medium. I just find I need to&#8230; <a class="read-more-link" href="https://wadetregaskis.com/better-image-stabilisation-in-final-cut-pro-using-object-tracking/" data-wpel-link="internal">Read more</a>]]></description>
										<content:encoded><![CDATA[
<p>This is basically a short written set of instructions derived from <a href="https://www.youtube.com/@RCodyWanner" data-wpel-link="external" target="_blank" rel="external noopener">Cody Wanner</a>&#8216;s <a href="https://www.youtube.com/watch?v=JstYyYT4OzM" data-wpel-link="external" target="_blank" rel="external noopener">YouTube video on the topic</a>, refined a little for simplicity and updated for the newer GUI in more recent versions of Final Cut Pro.  So feel free to view that video if you prefer that medium.  I just find I need to reference this sporadically and it&#8217;s easier to just re-read written instructions that re-watch a whole video.</p>



<div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained">
<p><strong>Background</strong>: Final Cut Pro&#8217;s built-in image stabilisation is a bit unreliable.  Sometimes it works perfectly, just like you&#8217;d expect.  Most of the time it requires manual tweaking and futzing in order to get good-enough results.  And sometimes it just <em>does not work</em>, no matter what you do, for reasons that are beyond me.  The technique shown here is annoyingly laborious to execute, but it works not just more reliably but also often just better (if your objective is <em>complete</em> stabilisation, at least).</p>
</div></div>



<p>Steps:</p>



<ol class="wp-block-list">
<li>Duplicate the clip (option-drag it in the timeline view) and place the duplicate above<sup data-fn="6883a475-8404-4bfe-a857-098915a99cc4" class="fn"><a href="#6883a475-8404-4bfe-a857-098915a99cc4" id="6883a475-8404-4bfe-a857-098915a99cc4-link">1</a></sup> the original.  Ensure it&#8217;s perfectly aligned on the timeline&#8217;s X (time) axis, otherwise it won&#8217;t show up as a tracking source in step 3.2.</li>



<li>On the duplicate clip (make sure it&#8217;s selected and your playback position is within it so that you can see what you&#8217;re doing!):
<ol class="wp-block-list">
<li>Invert the scale (e.g. make it -100% instead of the default 100%).</li>



<li>Invert the X &amp; Y offsets (if necessary &#8211; if they were non-zero beforehand).</li>



<li>Add an Object Tracker (the + icon to the right of the &#8220;Tracker&#8221; titlebar at the bottom of the Video Inspector (right-hand pane)).</li>



<li>A white grid &#8211; your anchor section &#8211; should appear over your clip.  Move and resize it to have it cover an appropriate part of the clip (a subsection that&#8217;s contrasty and contains object(s) that are stable &#8211; in appearance and position &#8211; within the world space of the scene, and ideally are never obscured by anything during the clip).
<ul class="wp-block-list">
<li>☝️ You can adjust the timeline position of the clip to find the optimum frame in which to identify your anchor section.</li>
</ul>
</li>



<li>Click Analyze.
<ul class="wp-block-list">
<li>⚠️ This will sometimes not work if certain other operations are outstanding, such as dominant motion analysis for the clip &#8211; you have to either cancel those background tasks or wait for them to finish. One of Final Cut Pro&#8217;s many irritating bugs.</li>



<li>⚠️ Watch carefully as it works through the clip (forwards from your starting point, then backwards, as necessary), for:
<ul class="wp-block-list">
<li>Your anchor section being intruded upon by any moving objects within the scene.  If that happens, try to go back and refine your anchor section placement so that it won&#8217;t be intruded upon.  If that&#8217;s impossible, you can proceed but be aware that the results may be subpar.</li>



<li>The anchor section changing in position and size &#8211; the more it &#8216;wobbles&#8217;, the worse the final results are likely to be.  Consider different anchor section placement, or try a different analysis method (in the Video Inspector, for your Object Track, change the Analysis Method from the default, &#8220;Automatic&#8221;, to another option &#8211; note that you must click Analyze again after changing this, for it to take effect).</li>
</ul>
</li>
</ul>
</li>
</ol>
</li>



<li>On the original clip:
<ol class="wp-block-list">
<li>Open the Transform viewer (the rectangle icon in the &#8220;Transform&#8221; titlebar in the Video Inspector).</li>



<li>Click the downward chevron next to &#8220;Tracker&#8221; text on the Tracker tab button (at the top of the video preview view), to bring up the configuration pop-up:
<ul class="wp-block-list">
<li>Set Tracker Source to your duplicate clip.</li>



<li>Set Tracker to the Object Tracker (or whatever you renamed it to).</li>



<li>Set the axes you want stabilisation to apply to (the Apply Tracker To checkboxes).</li>
</ul>
</li>
</ol>
</li>



<li>Disable the duplicate (e.g. V key while it&#8217;s selected).
<ul class="wp-block-list">
<li>☝️ You cannot have it disabled before you select it as the Tracker Source, as it won&#8217;t show up in the pop-up menu while disabled.</li>
</ul>
</li>



<li>On the original clip:
<ol class="wp-block-list">
<li>Set the scale to -100%.</li>



<li>Adjust the X &amp; Y positions to correct the framing, if necessary (if your X &amp; Y position were both 0 on the original clip, this shouldn&#8217;t be necessary).  Note that this usually isn&#8217;t a simple sign inversion as in similar previous steps.</li>
</ol>
</li>
</ol>



<p>Optional sixth step:  file a bug report or suggestion with Apple asking for them to make their built-in image stabilisation work better, and/or make the object tracker GUI easier to use (it could be just one or two clicks, to enable it and say &#8220;lock this part of the scene in place&#8221;).</p>


<ol class="wp-block-footnotes"><li id="6883a475-8404-4bfe-a857-098915a99cc4">Technically it doesn&#8217;t matter if it&#8217;s above or below, I just find it slightly more convenient when it&#8217;s above as usually it&#8217;ll be disabled (showing the original, now-stabilised version from below) but I access it easily by simply enabling it (V key), such as if I want to adjust the tracking. <a href="#6883a475-8404-4bfe-a857-098915a99cc4-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>]]></content:encoded>
					
					<wfw:commentRss>https://wadetregaskis.com/better-image-stabilisation-in-final-cut-pro-using-object-tracking/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">8656</post-id>	</item>
		<item>
		<title>How to disable automatic project backups in Final Cut Pro</title>
		<link>https://wadetregaskis.com/how-to-disable-automatic-project-backups-in-final-cut-pro/</link>
					<comments>https://wadetregaskis.com/how-to-disable-automatic-project-backups-in-final-cut-pro/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 23 Jul 2025 23:22:17 +0000</pubDate>
				<category><![CDATA[Howto]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[Final Cut Pro]]></category>
		<guid isPermaLink="false">https://wadetregaskis.com/?p=8517</guid>

					<description><![CDATA[Apple does provide these instructions, although they were annoyingly hard to find (in no small part because the page title is only incidentally related to the task). In short: My projects are already covered by Time Machine and other backup mechanisms, and I tried to tolerate Final Cut Pros built-in backup system, but the damn&#8230; <a class="read-more-link" href="https://wadetregaskis.com/how-to-disable-automatic-project-backups-in-final-cut-pro/" data-wpel-link="internal">Read more</a>]]></description>
										<content:encoded><![CDATA[
<p>Apple does provide <a href="https://support.apple.com/en-au/guide/final-cut-pro/ver7db6ffe77/11.1/mac/14.6" data-wpel-link="external" target="_blank" rel="external noopener">these instructions</a>, although they were annoyingly hard to find (in no small part because the page title is only incidentally related to the task).</p>



<p>In short:</p>



<ol class="wp-block-list">
<li>File &gt; Library Properties (⌃⌘J).</li>



<li>Click &#8220;Modify Settings&#8221; next to &#8220;Storage Locations&#8221;.</li>



<li>Set the &#8220;Backups&#8221; option to &#8220;Do Not Save&#8221;.</li>
</ol>



<p>My projects are already covered by Time Machine and other backup mechanisms, and I tried to tolerate Final Cut Pros built-in backup system, but the damn thing runs <em>so</em> often, which I know about very well because whenever it runs Final Cut Pro becomes completely unusable for several minutes.  It&#8217;s immensely irritating when it kicks in while I&#8217;m in the middle of editing.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://wadetregaskis.com/how-to-disable-automatic-project-backups-in-final-cut-pro/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">8517</post-id>	</item>
		<item>
		<title>Never import by copy into Final Cut Pro</title>
		<link>https://wadetregaskis.com/never-import-by-copy-into-final-cut-pro/</link>
					<comments>https://wadetregaskis.com/never-import-by-copy-into-final-cut-pro/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Sat, 19 Nov 2022 00:04:30 +0000</pubDate>
				<category><![CDATA[Photography]]></category>
		<category><![CDATA[Broken by design]]></category>
		<category><![CDATA[Bugs!]]></category>
		<category><![CDATA[Final Cut Pro]]></category>
		<category><![CDATA[GoPro]]></category>
		<category><![CDATA[GPMD]]></category>
		<category><![CDATA[MOV]]></category>
		<category><![CDATA[MP4]]></category>
		<guid isPermaLink="false">https://blog.wadetregaskis.com/?p=5187</guid>

					<description><![CDATA[By default, Final Cut Pro prefers to &#8220;copy&#8221; all files on import. Indeed you&#8217;d think this is the only sensible option most of the time, since most of the time you&#8217;re importing from a memory card and you do need to make a local copy somewhere on your computer. However, Final Cut Pro has a&#8230; <a class="read-more-link" href="https://wadetregaskis.com/never-import-by-copy-into-final-cut-pro/" data-wpel-link="internal">Read more</a>]]></description>
										<content:encoded><![CDATA[
<p>By default, Final Cut Pro prefers to &#8220;copy&#8221; all files on import.  Indeed you&#8217;d think this is the <em>only</em> sensible option most of the time, since most of the time you&#8217;re importing from a memory card and you <em>do</em> need to make a local copy somewhere on your computer.</p>



<p>However, Final Cut Pro has a design flaw which causes data loss.  You see, Final Cut Pro never merely <em>copies</em> the files.  It extracts their audiovisual contents and puts it into a <em>new</em> file.  You might have noticed this already from the fact that Final Cut Pro&#8217;s copied version of the files is always a MOV container, whereas your inputs are more likely an MP4 container.</p>



<p>This would be annoying enough in itself &#8211; it means you can&#8217;t do simple bitwise comparisons of the files to e.g. ensure the imported copy is <em>actually</em> valid and not corrupt, before you erase the original from your memory card.  But it gets worse.</p>



<p><strong>Final Cut Pro doesn&#8217;t copy all the contents</strong>.  It only copies <em>some</em> types of tracks &#8211; i.e. audio, video, and timestamp tracks.  It does <em>not</em> copy tracks such as <a rel="noreferrer noopener external" href="https://github.com/gopro/gpmf-parser" data-type="URL" data-id="https://github.com/gopro/gpmf-parser" target="_blank" data-wpel-link="external">GoPro&#8217;s metadata track</a> (GPMD).  Final Cut Pro just silently discards those.</p>



<p>Those tracks can contain important information.  GPMD tracks, for example, contain a whole host of telemetry from the GoPro including its location during recording, rotation &amp; movement data, and much more.  Even if you think you don&#8217;t care about things like geotagging, consider this:  that rotation &amp; movement data can be used to enhance image stabilisation.  By losing the data at import, you&#8217;re losing the ability to ever utilise that enhanced image stabilisation.</p>



<p>So never let Final Cut Pro &#8220;copy&#8221; your files &#8211; always copy them yourself first, as needed, and then import them into Final Cut Pro by reference only (the &#8220;Leave files in place&#8221; option).  Thankfully Final Cut Pro doesn&#8217;t mangle the files when you use them that way (underlining the question: why does it force a lossy conversion to MOV to begin with, since it clearly works just fine with MP4 originals).</p>
]]></content:encoded>
					
					<wfw:commentRss>https://wadetregaskis.com/never-import-by-copy-into-final-cut-pro/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">5187</post-id>	</item>
	</channel>
</rss>
