<?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>GPMD &#8211; Wade Tregaskis</title>
	<atom:link href="https://wadetregaskis.com/tags/gpmd/feed/" rel="self" type="application/rss+xml" />
	<link>https://wadetregaskis.com</link>
	<description></description>
	<lastBuildDate>Sat, 18 Nov 2023 00:09:58 +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>GPMD &#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>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>
