<?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 on: My DSLR Workflow (Canon 5D/7D/T2i/1Dmk4)</title>
	<atom:link href="http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/feed/" rel="self" type="application/rss+xml" />
	<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/</link>
	<description>Mario Feil Films</description>
	<lastBuildDate>Sun, 22 Apr 2012 02:08:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Kacey</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-15047</link>
		<dc:creator>Kacey</dc:creator>
		<pubDate>Fri, 18 Nov 2011 01:22:24 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-15047</guid>
		<description>I do agree with all of the ideas you&#039;ve introduced for your post. They are very convincing and can certainly work. Still, the posts are too short for newbies. Could you please extend them a little from next time? Thank you for the post.</description>
		<content:encoded><![CDATA[<p>I do agree with all of the ideas you&#8217;ve introduced for your post. They are very convincing and can certainly work. Still, the posts are too short for newbies. Could you please extend them a little from next time? Thank you for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WALLY</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-13463</link>
		<dc:creator>WALLY</dc:creator>
		<pubDate>Wed, 19 Oct 2011 10:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-13463</guid>
		<description>twitter api twitter api</description>
		<content:encoded><![CDATA[<p>twitter api twitter api</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Audio Power Amplifiers</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-2165</link>
		<dc:creator>Audio Power Amplifiers</dc:creator>
		<pubDate>Tue, 25 Jan 2011 04:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-2165</guid>
		<description>`.` I am really thankful to this topic because it really gives up to date information ,:.</description>
		<content:encoded><![CDATA[<p>`.` I am really thankful to this topic because it really gives up to date information ,:.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-1033</link>
		<dc:creator>Geoff</dc:creator>
		<pubDate>Fri, 12 Nov 2010 00:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-1033</guid>
		<description>Hi all-

I had a problem with Premiere CS4 not playing the H.264 smoothly so I simply batched out the files to a lower bandwidth of H.264 (around 1.5mp/s) still looks great on screen for editing but takes no space up at all. Then I relink. 

For some reason Adobe Media Encoder puts a .mp4 tag on these files  verses the .mov tag I get native from DSLR. That means I can keep track of which is which. 

Works like a charm. Hope that is helpful.

Next question for me is what is best to master to? Any ideas?</description>
		<content:encoded><![CDATA[<p>Hi all-</p>
<p>I had a problem with Premiere CS4 not playing the H.264 smoothly so I simply batched out the files to a lower bandwidth of H.264 (around 1.5mp/s) still looks great on screen for editing but takes no space up at all. Then I relink. </p>
<p>For some reason Adobe Media Encoder puts a .mp4 tag on these files  verses the .mov tag I get native from DSLR. That means I can keep track of which is which. </p>
<p>Works like a charm. Hope that is helpful.</p>
<p>Next question for me is what is best to master to? Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mario</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-1016</link>
		<dc:creator>mario</dc:creator>
		<pubDate>Tue, 09 Nov 2010 18:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-1016</guid>
		<description>Juan, just read the last part of my post. 
After each shoot, I&#039;m doing the ProRes conversion of all the files I shot.

Native files are saved on 2 different harddrives (=&gt;BACKUP)
Am only using the ProRes files for each edit. After that, I&#039;m deleting the ProRes files to get HDD space back.

Even without all the ProRes files on my harddrives, I&#039;ve got around 20TB of used HDD space. Imagine how many harddrives I would have to buy when keeping the HUGE ProRes files :)</description>
		<content:encoded><![CDATA[<p>Juan, just read the last part of my post.<br />
After each shoot, I&#8217;m doing the ProRes conversion of all the files I shot.</p>
<p>Native files are saved on 2 different harddrives (=>BACKUP)<br />
Am only using the ProRes files for each edit. After that, I&#8217;m deleting the ProRes files to get HDD space back.</p>
<p>Even without all the ProRes files on my harddrives, I&#8217;ve got around 20TB of used HDD space. Imagine how many harddrives I would have to buy when keeping the HUGE ProRes files <img src='http://mf-films.de/en/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mario</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-1015</link>
		<dc:creator>mario</dc:creator>
		<pubDate>Tue, 09 Nov 2010 18:28:48 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-1015</guid>
		<description>sorry, never used the EOS Plugin. Only use MPEG Streamclip for encoding ALL files</description>
		<content:encoded><![CDATA[<p>sorry, never used the EOS Plugin. Only use MPEG Streamclip for encoding ALL files</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mario</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-1014</link>
		<dc:creator>mario</dc:creator>
		<pubDate>Tue, 09 Nov 2010 18:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-1014</guid>
		<description>yup, it saves HDD space at the END not during the edit. Since FCP obviously doesn&#039;t support H.264 natively, we have to transcode each clip first. 

The main thing I want to write down is simple: don&#039;t fear to delete the ProRes files as soon as your project is finished. The DSLRs don&#039;t create Proxies for editing like the RED One, so we have to create our own editing Proxies (like huge ProRes files)</description>
		<content:encoded><![CDATA[<p>yup, it saves HDD space at the END not during the edit. Since FCP obviously doesn&#8217;t support H.264 natively, we have to transcode each clip first. </p>
<p>The main thing I want to write down is simple: don&#8217;t fear to delete the ProRes files as soon as your project is finished. The DSLRs don&#8217;t create Proxies for editing like the RED One, so we have to create our own editing Proxies (like huge ProRes files)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mario</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-1013</link>
		<dc:creator>mario</dc:creator>
		<pubDate>Tue, 09 Nov 2010 18:23:22 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-1013</guid>
		<description>totally forgot to reply. Sorry for that.
For 35mm blow up, I&#039;d recommend to create a tiff or targa sequenz. But actually never did that with DSLR footage, only with Motion Graphics out of After Effects</description>
		<content:encoded><![CDATA[<p>totally forgot to reply. Sorry for that.<br />
For 35mm blow up, I&#8217;d recommend to create a tiff or targa sequenz. But actually never did that with DSLR footage, only with Motion Graphics out of After Effects</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-1011</link>
		<dc:creator>Juan</dc:creator>
		<pubDate>Tue, 09 Nov 2010 17:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-1011</guid>
		<description>Thank you for sharing your workflow. 

I want to ask you a very basic question. 

After the conversion do yo delete the original footage ? 

I&#039;m feeling that I have to buy a new 2TB hard drive every week. 

Thank you again!
Juan</description>
		<content:encoded><![CDATA[<p>Thank you for sharing your workflow. </p>
<p>I want to ask you a very basic question. </p>
<p>After the conversion do yo delete the original footage ? </p>
<p>I&#8217;m feeling that I have to buy a new 2TB hard drive every week. </p>
<p>Thank you again!<br />
Juan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://mf-films.de/en/2010/06/english-my-personal-dslr-workflow-canon-5d7dt2i1dmk4/comment-page-1/#comment-978</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Fri, 05 Nov 2010 16:41:48 +0000</pubDate>
		<guid isPermaLink="false">http://animatola.com/wordpress/?p=207#comment-978</guid>
		<description>What about the Date/Timestamp of the Native H264 Quicktime fies when using Canon EOS Plugin for FCP (vie Log and Transfer) or the RG &quot;Grinder&quot; Software, maintaining the &quot;Timcode&quot; Information on clips.
Are there any drawbacks when reconnection to the original (Native) data that way?</description>
		<content:encoded><![CDATA[<p>What about the Date/Timestamp of the Native H264 Quicktime fies when using Canon EOS Plugin for FCP (vie Log and Transfer) or the RG &#8220;Grinder&#8221; Software, maintaining the &#8220;Timcode&#8221; Information on clips.<br />
Are there any drawbacks when reconnection to the original (Native) data that way?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

