<?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/"
	>

<channel>
	<title>Steve Covello &#187; C &#8211; Digitizing &amp; Organizing</title>
	<atom:link href="http://apescience.com/video/category/digitizing-organizing/feed" rel="self" type="application/rss+xml" />
	<link>http://apescience.com/video</link>
	<description>Best Practice and FCP Techniques for Assistant Editors</description>
	<lastBuildDate>Mon, 16 Jan 2012 05:25:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Selects: Making Choices From Your Footage</title>
		<link>http://apescience.com/video/digitizing-organizing/selects-making-choices-from-your-footage</link>
		<comments>http://apescience.com/video/digitizing-organizing/selects-making-choices-from-your-footage#comments</comments>
		<pubDate>Sun, 22 Feb 2009 03:31:14 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[C - Digitizing & Organizing]]></category>

		<guid isPermaLink="false">http://www.apescience.com/video/?p=60</guid>
		<description><![CDATA[Unless you have been given the chosen selects ahead of time, you will need to go through the material, make selects, markers and comments to use later when you begin to edit. My general rule for this process is simple: If the footage has an immediate impact on you, mark it. Allow yourself to respond [...]]]></description>
			<content:encoded><![CDATA[<p>Unless you have been given the chosen selects ahead of time, you will need to go through the material, make selects, markers and comments to use later when you begin to edit. My general rule for this process is simple: If the footage has an immediate impact on you, mark it. Allow yourself to respond to the footage as a viewer, not just as an editor. However, be open to being wrong about your instincts upon a second or third look.</p>
<p>Some additional tips on how to “look” at footage while making selects: Most projects are fairly prescribed about what shots will be used. Few editing assignments will give you the challenge of coming up with something purely creative out the footage you’ve been provided. But on those rare instances where you are looked upon to be as much of an artist as the DP or Director, you will need to look at your raw material with an eye for its potential beyond being a clip in a sequence of other clips.</p>
<ul>
<li>Look for movement and counter-movement within the composition of the screen that you can combine with other shots that “lead” your eye in a direction.</li>
<li>Look at something and ask yourself what you wish you could combine with that shot to create a flow, and you will be alert for that shot if it appears later in the footage.</li>
<li>Look for opportunities to use negative space in a shot that could be combined in layers with other shots to create depth.</li>
<li>Look for “junk” to use for character or texture over other footage, like swish, film run, scratches or light leaks.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://apescience.com/video/digitizing-organizing/selects-making-choices-from-your-footage/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ingest: Logging, Digitizing &amp; Importing</title>
		<link>http://apescience.com/video/digitizing-organizing/ingest-logging-digitizing-importing</link>
		<comments>http://apescience.com/video/digitizing-organizing/ingest-logging-digitizing-importing#comments</comments>
		<pubDate>Sun, 22 Feb 2009 03:30:35 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[C - Digitizing & Organizing]]></category>

		<guid isPermaLink="false">http://www.apescience.com/video/?p=58</guid>
		<description><![CDATA[Sometimes you will receive a data file, such as an ALE, XML, Excel, EDL or FCP logging project along with your tapes. If you are lucky, the person who did the logging work for you followed some best practice steps so that your logging, digitizing and organizing tasks will be error-free. But don&#8217;t count on [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes you will receive a data file, such as an ALE, XML, Excel, EDL or FCP logging project along with your tapes. If you are lucky, the person who did the logging work for you followed some best practice steps so that your logging, digitizing and organizing tasks will be error-free. But don&#8217;t count on it. Check for the following:</p>
<ul>
<li>Tape reel IDs should make some kind of sense. If not, change them.</li>
<li>Sort all of the clips by clip start time. Then, quickly compare the clip end time to the timecode of the next clip&#8217;s start time just to be sure that there hasn&#8217;t been a gap in the footage that was accidentally overlooked, and if so, check the tape to see why.</li>
<li>Check each clip duration to see that it makes sense. Sometimes the logger will mark an out point after a timecode break giving a clip a crazy duration like 2 hours and 20 seconds when it should only be a 20 second clip. If it looks fishy, check the tape. If you need to adjust the log outpoint, be sure to give yourself 5+ seconds of post-roll past the outpoint. The problem could also be an in-point, but that is unusual.</li>
<li>Check to be sure that the timecode format is consistent with what is actually on the tape. Sometimes the logging is done manually without the benefit of copying the timecode from the actual source. This can cause the log to have non-drop frame timecode, but the tapes are drop frame.</li>
<li>For multi-camera shoots with sync-generated timecode, you should have identical timecode on all of your ISO tapes and line feed, if any. However, if you have only been given one log sheet for the selects, you will have to do a few summersaults with your clip to use the same numbers. See the demo.</li>
</ul>
<p>Video Demo: <a href="http://www.apescience.com/video/wp-content/themes/massivenews/videodemos/Demo_clone.mov" target="_blank">Cloning clip data to other camera ISO recordings for batch capture</a></p>
<p>If you are logging from tapes for the first time, you have a few options. Some editors prefer to log each take or scene separately, others prefer to just capture whole timecode hours regardless of what scenes or takes are recorded in them. A lot depends on the kind of footage. Each way has its own arguments for and against it. If you log every scene or take, it&#8217;s a lot of work, but the end result is highly organized and quickly accessible. If you simply capture whole tapes, you will save logging time, but you will have to go through and make markers or sub-clips to navigate the material. Another reason for not doing huge clips is the greater possibility that some kind of data corruption can occur in the middle of a clip making the whole clip useless. If corruption occurs some time after the project has been ongoing, and many parts of the clip are scattered all over the sequence, you will have a lot of work to do to manually re-insert an alternately logged and captured version of that clip. I tend to front-load the logging labor unless I&#8217;m really in a time crunch.</p>
<p>Log clip names according to scenes/takes, or with reasonable name descriptors that anyone else could understand. Do not use slashes [\ or /], punctuation, or use anything but letters and numbers in the name because it could cause problems for the computer’s file directory and perhaps cause crashes.</p>
<p>Indicate “select” choices with either markers, color or bin column notations if you have time. This is especially useful if you are collaborating with other people. When you are working with clients or directors one-on-one, you will make a good impression on them by being prepared, so know where everything is and have as much reference information available to find things quickly. Your time together should be spent as efficiently as possible.</p>
<p>Remember that FCP will create a default “Unknown” filename on your media drive if you do not log the clip name before you digitize. If this occurs, you will have difficulty reconnecting the media file to the clip in your bin if you move your media to another location or change the media drive’s name.</p>
<p>If the workflow of your project will require that you perform a high resolution re-digitizing process for final completion (such as a film shoot with low quality dailies but full quality audio, then a separate color correction layoff later on), consider setting up your System Settings in FCP so that you can capture separate audio files from your video sources. This will give you a media folder of video only and another for audio only, which will serve its purpose when you delete your old low resolution video files to make way for your final color corrected footage. More on this later in the “Online Finishing” chapter.</p>
<p>For tapeless shoots, hopefully you will be given a firewire drive that has nothing but the footage you need for your edit. If this is the case, then simply drag and drop or import the folders of clips into your project. Unfortunately, however, you may be given clips with the default hexadecimal names given to each clip from the MXF extraction to process QuickTime. Check file creation dates to see if you can sort by shoot date. It will give you a broad starting point for sorting out the shoot.</p>
]]></content:encoded>
			<wfw:commentRss>http://apescience.com/video/digitizing-organizing/ingest-logging-digitizing-importing/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Starting Up: Creating a New Project</title>
		<link>http://apescience.com/video/digitizing-organizing/starting-up-creating-a-new-project</link>
		<comments>http://apescience.com/video/digitizing-organizing/starting-up-creating-a-new-project#comments</comments>
		<pubDate>Sun, 22 Feb 2009 03:29:06 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[C - Digitizing & Organizing]]></category>

		<guid isPermaLink="false">http://www.apescience.com/video/?p=56</guid>
		<description><![CDATA[My Golden Rule for building a project structure is to Keep It Simple. Make bin names obvious, keep &#8220;garbage&#8221; out of the way of working material, name sequences according to some logic of progression. Every editor has their own way of setting up a project and they will strangle you if you go in and [...]]]></description>
			<content:encoded><![CDATA[<p>My Golden Rule for building a project structure is to Keep It Simple. Make bin names obvious, keep &#8220;garbage&#8221; out of the way of working material, name sequences according to some logic of progression. Every editor has their own way of setting up a project and they will strangle you if you go in and start changing things, but if you are just starting out, now is a good time to develop good habits.</p>
<p>Video Demo: <a href="http://www.apescience.com/video/wp-content/themes/massivenews/videodemos/Demo_project.mov" target="_blank">FCP project setup</a></p>
<p>The first folder has a space before the name so that it sorts on top. The last folder is named to sort on the bottom. Everything else in between should represent only the folders you will need to access the material for your edit. My rules for bin structure are:</p>
<p>At the end of the day, the work-in-progress sequence folder, &#8220;_Edits&#8221; will ONLY have works-in-progress that are being used and in consideration for screening. Anything else goes in the &#8220;zzzNG&#8221; folder. No exceptions!</p>
<ul>
<li>NEVER use the word &#8220;Final&#8221; or &#8220;Master&#8221; if the sequence is NOT final or a master. Never, never, never.</li>
<li>If you need to make folders of &#8220;Music&#8221;, &#8220;Sound Effects&#8221;, and &#8220;Voiceover&#8221;, nest them in a master folder called &#8220;Audio&#8221; to reduce clutter.</li>
<li>Any sequences created or sound or color correction preparation should go in its own folder. Since they are a subset of Edits, I suggest putting them there.</li>
<li>Anything that you receive as a render from AfterEffects or whatever should go in the &#8220;Renders&#8221; folder. This should correspond to another Finder level folder called &#8220;Renders&#8221; that you would create as part of setting up an AfterEffects project.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://apescience.com/video/digitizing-organizing/starting-up-creating-a-new-project/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Box of Stuff: Dealing With Your Material</title>
		<link>http://apescience.com/video/digitizing-organizing/the-box-of-stuff-dealing-with-your-material</link>
		<comments>http://apescience.com/video/digitizing-organizing/the-box-of-stuff-dealing-with-your-material#comments</comments>
		<pubDate>Sun, 22 Feb 2009 03:26:23 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[C - Digitizing & Organizing]]></category>

		<guid isPermaLink="false">http://www.apescience.com/video/?p=54</guid>
		<description><![CDATA[By the time you finish reading this you will probably think I am completely nuts. This will seem like WAY too much trouble. But I assure you, if you DON&#8217;T manage your materials as if you will suddenly and unexpectedly squirt out of the universe, your name will be cursed in absentia. In other words, [...]]]></description>
			<content:encoded><![CDATA[<p>By the time you finish reading this you will probably think I am completely nuts. This will seem like WAY too much trouble. But I assure you, if you DON&#8217;T manage your materials as if you will suddenly and unexpectedly squirt out of the universe, your name will be cursed in absentia. In other words, you need to assume that, at some point, you might not be available to administer the materials or editing tasks for some reason, and how well you organize everything will determine how well other people can pickup where you left off.</p>
<p>When the box of stuff finally arrives in your edit room, the first thing you should do is take everything out and look at it. Duh! But incredibly enough, sometimes people THINK they&#8217;ve sent you what you want, but they sent something else, or they didn&#8217;t send it at all. Open all of the tape and disc cases and confirm that there&#8217;s actually a tape or disc in it. If there are concerns about what you have in your hands, call the production company immediately. There are some facilities that require that you or an assistant to put barcode stickers on everything and begin making an inventory list.</p>
<p>When you are ready to deal with your tapes, remember, the first thing you always do is to pop the record tab so that you cannot accidentally erase it. If your tapes haven’t already been labeled, name them making sure to mark both the tape and the case. Try to keep them in chronological order too. Rewind them in a VTR, not a camera. Do not store them anyplace where there is direct sunlight, high humidity, temperature extremes, or magnetic fields such as speakers, telephones, or magnetized tools. Clearly label the container box so it doesn&#8217;t get stacked away in the wrong place.</p>
<p>Discs of other things like ALE files, logos, sound, etc. should be labeled too. I like to copy off each disc that comes in onto the harddrive you will be using for the project, each disc in its own folder, named according to the disc label name. This provides you with easy, centralized access to the material, but also permits the original discs to serve as a backup. You want to handle the original discs as little as possible for risk of scratching or losing them.</p>
]]></content:encoded>
			<wfw:commentRss>http://apescience.com/video/digitizing-organizing/the-box-of-stuff-dealing-with-your-material/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: apescience.com @ 2012-05-18 21:36:07 -->
