After announcing it last week, today Avid released the next version of Media Composer, and it is a major update.  The key thing that will affect all users is that the program will now be a natively 64bit application.  This will exclude users who still have 32bit systems, but allow the software to use more RAM, and therefore effectively do larger projects, on 64bit systems, which are pretty prevalent at this point.  From what I can tell, re-coding an entire application for 64bit is also good for cleaning up the code for existing features, and streamline performance and threading.  Avid’s primary competition: Adobe Premiere Pro, saw a huge improvement in both performance and stability when the first 64bit version (CS5) was released.  This has led to a huge increase in that application’s popularity, especially for larger projects.  The level of competition presented by that change may be a key factor in why we are now seeing so many major changes from Avid.

The next most significant new feature, that will affect many users, especially new ones, is “Avid Open I/O” which is Avid’s new approach to integrating hardware with Media Composer.  Avid now supports hardware I/O via products from AJA, Blackmagic, Matrox and others.  We have seen hints of this coming, with support for the Matrox MXO2-Mini and AJA ioExpress in versions 5.0 and 5.5 respectively.  This change has two major benefits, it will allow most users access to professional hardware I/O solutions without paying for Avid’s overpriced hardware, and nearly as important, it will allow edit systems to run multiple applications on the same system and hardware.  Add this to advances in project compatibility and interchange, and users will be able move their editing projects between Avid and Premiere Pro (and FCP on the Mac side) on the same systems, using the same video output hardware.

Avid also added a myriad of new features to enhance more advanced workflows, with better support for stereoscopic content, more advanced color correction tools, and surround sound mixing options on the audio side.  They also have a 4:4:4 RGB version of the popular DNxHD codec, and natively support ProRes files.  Their Symphony finishing toolset no longer requires Nitris DX hardware, but I have yet to find the pricing structure for that option.  It looks to be a solid feature set, and I am looking forward to trying it out.

AJA released a variety of new products, most of them adding 3D related features to previously existing offerings.  The Kona3G is a revision to the existing Kona3/Xena2Ke that adds stereoscopic support through HDMI 1.4 output and dual stream SDI-3G I/O, while also dropping in price about 30%.  Their Hi5-3D replaces the Hi5-3G and adds HDMI 1.4 output as well as a variety of options for processing dual stream and muxed stereo inputs.  The Ki Pro Mini is a smaller version of the Ki Pro that can now be mounted directly to camcorders, and record ProRes files directly to CompactFlash cards from HDMI or SDI inputs.

Blackmagic Design had their own selection of new products to announce.  Their line of SDI routers must have really taken off, because they are really scaling their offerings upwards, with new models that offer up to 288 Channels of input and output, and options for coaxial or fiber based connections.  I am just now upgrading to a 16×16 3G Micro VideoHub, but maybe someday.  Their other big news comes from their DaVinci line, with previously announced Resolve 7.0 for OSX finally being released.  It will be interesting to see what effect that new option has on the marketplace and the price of existing products.  My company will definitely be looking into setting up a Resolve system, and our primary colorist is very interested in the new capabilities it would give us.

NVidia released their new line of Fermi based Quadro graphics cards at Siggraph.  The Quadro 4000, 5000, and 6000 will be the successors to the current QuadroFX 3800, 4800, and 5800, with similar form factors and interfaces.  I have not had a chance to test them myself yet, but everything I hear has been positive.  Adobe has announced that the Quadro 4000 and 5000 will be officially supported for CUDA acceleration by the Mercury engine in Premiere Pro CS5.  This support came in the form of the Premiere Pro 5.0.2 update last week, which also adds the GeForce GTX 470 as a fully supported GPU option.  More significantly from a technology standpoint, they added 10bit Displayport support for Quadro cards, and also support for RedRocket acceleration, RMD files and newer Red camera updates, as well as better support for Broadcast Wave and certain XDCam-HD files.  There is also a 6 page list of smaller fixes in the new release, many of which fill significant holes in certain workflows.  I haven’t had much time recently to test out the new features, but getting 10bit color to my Dreamcolor is at the top of my list.

Avid Media Composer 5 was released three months ago, and they are now on the 5.0.3 revision.  I have had a chance to test it out at work, and while the ability to import any Quicktime via AMA can totally change the workflow for certain tasks, I wouldn’t use it as a primary way to edit large projects.  The performance and stability is not up to the same level as MXF based editing is.  You also need a very fast system for that to work.  Most of our Avids are HP XW8600s, while we have been dedicating our newer Z800 systems to CS5, but AMA playback requires more computing power than DNxHD editing, which is to be expected.  We also found Version 5 to be less stabile and less responsive on our large feature length DNxHD project, even without AMA based media.  The fact that it fully supports Windows 7 will be the factor that motivates our facility wide upgrade in the near future.

I was also able to test Media Composer 5 with my Matrox MXO2-Mini, for hardware HDMI out, and while it worked great at first, I once again saw a major hit in stability, with an escalating number of system crashes.  It is so close, but not quite there yet.  Hopefully we will see many of those issues worked out in intermediate dot releases, since most of these features are brand new.  Stay tuned, since I have a few other new toys that I will review in my next post.

FTC Disclosure: Many of the companies I refer to above have made their products available to me or my company in the past, but none of the new items discussed above were provided to me without independently purchasing them.

The other major new feature for this release of After Effects is the Rotobrush.  Based on Photoshop image processing functionality, extended to account for the information made available from multiple frames, this is the closest thing you are going to find to magic in a current generation compositing application.  It allows you to automatically separate foreground and background objects in a video image, otherwise known as rotoscoping.  Of course it is not perfect, but it is a huge advance, compared to previous tools.  Automated tools like this are usually much more impressive if you aren’t expecting a miracle going into the process, but as long as you have reasonable expectations, Rotobrush can give you usable results in a rush, or a good starting point when more precise work is required.  Much of the “magic” of the new tool is in the processing of the automatically defined edges, and this capability is available without using the Rotobrush, in the form of the “Refine Matte” effect.  This effect can be used to polish the edges of standard keys, or manually rotoscoped footage.  Most of the other major feature enhancements for this release come in the form of integrated third party plug-ins, including Color Finesse for grading, Mocha for tracking, and DigiEffects Freeform for 3D simulation.  Each of these are feature rich plug-ins that include functionality that is beyond the scope of this overview, but are well worth experimenting with if you spend a lot of time working in After Effects.

There are quite a few new features in Premiere Pro CS5 that don’t hinge on the new Mercury Playback Engine.  These relate primarily to metadata and content organization, as opposed to the media itself.  Speech detection tools were introduced in CS4, and now those can be used in conjunction with the features of Adobe Story, to link your actual footage to your original plans, including scripts, storyboards, and shot lists.  Much of this footage processing links to OnLocation CS5′s features, which besides monitoring the technical details of a captured media signal, allow ingest of metadata during the acquisition process.  Building up as much information as possible during production, on a per-shot and per-take basis, will further streamline the organization process during editorial.  All of this information is searchable, with the intent being that an editor will have a much easier time finding what they are looking for, as this metadata is passed down throughout the post production workflow, based on source timecode.  This content logging metadata is not the only way that CS5′s handling of non-media information has improved.

Adobe has also been working hard to streamline the process of exchanging existing projects with Premiere from Final Cut Pro and Avid Media Composer.  They have further refined the FCP XML import and export functionality that was first introduced in version 4.0.1, which offers some interesting options for Mac based workflows.  Working at a PC based facility, I have had more opportunity to take advantage of Premiere’s support for exchanging timelines with Avid.  My current workflow is to use EDLs to move my sequences from Avid to Premiere, but with CS5′s improved support for AAF import and export, hopefully I will soon be able to leverage the additional functionality offered by AAF exchange.  (One caveat with using EDLs to move sequences, is that occasionally Avid adds spaces to the end of every line, and CS5 will not relink to the source footage automatically, unless you manually remove those spaces)  I have yet to find the optimal settings to switch to AAF files, but I have talked with people who have it up and running.  Combining this sequences exchanging feature with CS5′s support for DNxHD in both MXF and MOV wrappers, offers some interesting possibilities, but the truly revolutionary workflow will finally arrive when Media Composer 5 is released next month, allowing Avid to link to external QuickTime files thru AMA.  Hopefully this will allow Premiere Pro CS5 and Media Composer 5 to exchange sequences that all reference the same source files, without any conversions or transcoding.  Since Canon DSLR files will be supported natively both applications, this should totally streamline my current workflow.

Now why would someone want to move their project between different NLE applications?  An editor’s familiarity with a specific toolset is usually important to them, so certain offline creative editors are not going to switch their primary editorial app no matter what.  To its credit, Avid has a solid reputation for handling extremely large projects with no decrease in performance.  While Premiere Pro has taken a huge step forward in that regard, it is going to take a long time for it to build a stable reputation, since trust usually develops very slowly.  On the other hand, Premiere makes a perfect interactive online conform tool, especially compared to Avid.  It can ingest most digital formats in their native form, supports SDI capture and playback over a number of different hardware solutions, and scales to 2K and 4K resolutions, in RGB color space if desired.  It is compatible with DPXs for color grading, and can playback surround sound for reviewing final mixes.  The fact that Premiere can use Dynamic Link to ingest your visual effects changes from After Effects, and to output to Encore for adding interaction becomes an added bonus for this conform solution.

Dynamic Link is now on its fourth iteration, and has matured into a functional tool, even at HD resolutions.  It is designed exchange media between apps, without having to waste time or disk space by rendering.  While it started as a method for importing AE comps into PPro, it became the backbone of PPro’s export capabilities thru Adobe Media Encoder as well.  While Media Encoder CS5 is a dramatic improvement from the previous version, Adobe also added back in the option to export files directly from within Premiere.  This is much quicker for rendering out small parts of large projects, avoiding the overhead of syncing the entire project with Media Encoder before rendering a couple of frames.  They also brought back the ability to easily export single frames from the timeline, a function that had been removed in CS4, an inexcusable oversight that has now been rectified.  Exporting a Premiere Pro sequence thru Media Encoder, while not transparent, is now a much faster and more stabile process than it was in CS4.  Media Encoder also now supports DPX sequences and AVC-Intra MXF files, for both input and output.  Still sequence support in both Premiere Pro and Media Encoder is still missing crucial options, for relinking footage in PPro and manually overriding the frame rate in AME.  Hopefully we will have more user control of these settings in future versions.

One thing that I would like to see handled differently in Media Encoder, as well as the Premiere exporter, is the default settings for each export plug-in.  Adobe is never going to be able to predict what settings every user is going to want, but it would be nice if it defaulted to whatever I selected last time I used that particular output option.  As it stands, Media Encoder defaults to the same output as the last file queued, but if I choose any other output (AVI, MOV, DPX) it returns all of the individual settings to the original default, which is usually DV based.  Now it is possible to save presets, but I hesitate to do so unless I anticipate using that exact configuration frequently, because sorting through too many presets can become harder than manually defining the individual settings.  On a relate note, be careful where you save your .prproj files, since selecting “Save As” does not default to the current project location as it should.  Instead it defaults to the folder containing the last piece of media that you imported.  I usually follow a strict project organizational pattern, but I have saved projects in the wrong folders daily since switching to CS5 thanks to this “feature.”  Hopefully this can be fixed in a minor update.

Now a subsidiary application to Premiere Pro, Encore CS5 is the next logical step in that application’s evolution as an interactive authoring tool.  The most significant new feature for larger productions would have to be support for DDP output, so that your Encore projects can now be replicated at a professional facility without any special hardware required on the authoring side.  Adobe has also continued to develop the Flash export options, allowing Encore users to output their interactive experiences directly to the web, now with most of the BluRay interactivity features, including the new multipage menus, supported as well.  Encore projects are now completely cross platform compatible, between the Mac and PC versions.  There is also better support for 23.976p and 24p source files, and an easier subtitling process.  AVCHD files can now be authored directly to BluRay discs without any transcoding, decreasing processing time, and increasing output quality.

Previous versions of Encore have used Dynamic Link to import Premiere Pro sequences as source clips, and more significantly in my opinion, to import After Effects compositions as motion menu backgrounds.  I was never really that impressed by Dynamic Link for Encore source clips, because your Premiere Pro sequence is usually finished by the time you make a DVD, and since you are going to have to transcode to MPEG2 at some point anyway, little time is saved.  Motion menu design on the other hand seems like a much better fit for the workflow benefits offered by Dynamic Link, since the menu needs to be edited in both Encore and AE during the authoring process.  Encore now also uses Dynamic Link to offload transcoding of those sequences, or any other incompatible source footage, to Adobe Media Encoder.  This will free up Encore to continue interactive authoring work, while asset transcoding proceeds in the background, and also allows third party accelerated encoding plug-ins that are compatible with Adobe Media Encoder, to be utilized for these internal transcodes.  While I am unaware of any CS5 compatible encoders, this was an issue with the Elemental Accelerator in CS4.  The files it generated at 24p were re-transcoded in Encore anyway, and Encore couldn’t utilize the accelerated plug-in directly.  Anyhow, while no CS5 version of Elemental Accelerator has been announced, Matrox’s CompressHD should be able to accelerate Encore’s BluRay H.264 encodes, once Matrox releases CS5 compatible drivers.

The one thing still missing from the Adobe package is a good intermediate format for exchanging files between other applications, systems, or facilities.  This capability is available from 3rd parties like Cineform or Matrox, but until Adobe integrates support for one directly into the suite, there will not be a single universal standard format, that can be counted on to be compatible everywhere.  It needs to be compatible with both Mac and PC, and store at least 10 bit HD footage with sufficient compression to playback smoothly on a laptop.  Apple and Avid have both recognized this need, and developed ProRes and DNxHD respectively.  AVC-Intra is Adobe’s current recommendation to meet those workflow needs, but that format has a complicated file structure, and is not a codec optimized for smooth playback.  This universal format would tie in well with OnLocation, if Adobe ever added support for HD-SDI capture capabilities.  That would allow ingest, either live or from tape playback, into a compressed format for editorial, with log notes entered in real-time similar to their current tapeless solution options.  And if a professional selection of scopes could be viewed of the SDI input signal, you would have an all-in-one onset workstation solution.  OnLocation CS5 currently offers most of these capabilities, but is limited to HDV, XDCam, and P2 acquisition for most of its features.  Oh, and if it supported my Canon DSLR, that would be pretty cool too; maybe next time.

As a whole the CS5 release is a major turning point for Adobe, especially with the problems their users experienced with CS4.  While I don’t yet fully utilize many of the new features, CS5 has already revolutionized the way I work.  Premiere Pro CS5 has replaced After Effects CS4 as central application from which I manage my projects.  I was lucky enough to be on the beta team, so most of the major issues I encountered with the software in my specific workflow, have already been resolved during the development process.  While CS5 is by no means perfect, it is a huge step forward that will begin to rebuild user confidence in Adobe products.  Once third party hardware and plug-ins have had time to be updated to be compatible with the new 64bit native applications, I see no other disadvantages or caveats to upgrading to CS5, which I highly recommend.

FTC Disclosure: I have been on Adobe’s beta team for many years, and Adobe has provided me a copy of CS5 for this review.  My only admitted personal bias is my preference of Windows over OSX, because I like full control over every aspect of my computing experience.  If for some reason that bothers anyone, there are plenty of other sources of information on the internet, but I try to provide unique insight on how each of these tools fits into the larger post-production picture.  Any relevant critique or response is welcomed.

Twixtor is a plug-in from ReVision Effects that allows you to change the frame rate of your footage thru motion compensated frame blending.  While it can be used to add frames for slow motion effects, I have found that I get much better results when removing frames, such as when dropping from 30fps to 24fps.  Regardless of the specific settings, Twixtor takes a lot of time to render.  In our first tests on 8-Core Xeon systems, processing one minute of source footage required one minute of render time.  Now with Intel’s new Nehalem based CPUs, and recently their even newer Gulftown 6-core chips, we have seen that reduced by about fifty percent, to a half hour per minute of source footage, which is still a long time, but feels great compared to where we were a year ago.  Since our footage re-link process is based on frame counts, we have to process our entire source clips in order to take advantage of that level of workflow automation, even if we are only using the last ten seconds of a 14 minute take.  Obviously there are ways around this, but we currently have more render time available to us than man hours, and it gives us more flexibility later on anyway, so we just let it go.  We took advantage of every night and weekend during creative editorial to Twixtor every clip that made it into the rough cut, and now we just have to link to that bank of processed footage to conform our cuts in CS4.  The fact that all of Canons DSLRs now support 24p should alleviate most of the frame rate and Twixtor issues in future projects.

Besides frame rate issues, Canon DSLRs present another unique challenge, in regards to color space and bit depth.  Many professional video codecs store the color values in the range between 16 and 235, of the 256 possible 8bit options.  (The reasoning for this is fairly complicated, and relates primarily to legacy analog video signal issues)  This limits pixels to 220 levels for each color in most 8bit codecs, but the MOV files from the Canon DSLRs use the entire 256 possible options (0-255) for each color.  This increases the number of possible values for each three color pixel by over 50%, (220^3 vs 256^3) but also means that converting your DSLR footage into most other 8bit formats will result in one of two issues: either the extreme values will be clipped, losing detail in the highlights and the shadows, or all of the dynamic range will be squeezed into the reduced sample-space, meaning certain intermediate values are going to be merged together if you edit in an 8bit codec.

Clipping was the most likely possibility in most existing applications prior to the release of Quicktime 7.6.2 in mid 2009.  Previous to that point, Quicktime displayed Canon clips incorrectly (clipping the values beyond 16-235) but after that update was released, most applications that used Quicktime to decode DSLR footage, were able to access the entire dynamic range of the source clips.  This support is not a foregone conclusion though, since DSLR files could be imported with a more generic MPEG4 decoder without Quicktime, and still be displayed incorrectly.  Even with properly calibrated import processes, compressing the 255 possible values for each color channel into the limited 220 values that most 8bit video formats offer, will lead to a loss of precision, and a potential increase in color banding, especially if you plan to color correct the footage later.  A 10bit video format will offer four times as many possible legal color values, and will be able to store all of the original image data with precision to spare.  Once you have color corrected your footage, and any visual effects are complete, an 8bit distribution format may be sufficient for most uses, but any image processing that takes place on the original files before you apply the “look” that you want, should definitely be processed in at least 10bit color space to preserve as much of your original image information  as possible.

When editing DSLR footage in Avid, DNxHD is the recommended intermediate format.  DNxHD files can be encoded in either HD 709 (16-235) or RGB (0-255) color space, but any DNxHD files encoded in RGB are converted to HD 709 upon import into Media Composer, regardless of the original output setting.  Therefore any DNxHD MOV files generated elsewhere for ingest into Avid should be exported at 16-235 to match Avid’s target color space, for a lossless “Fast Import.”  On the other hand, when importing DSLR footage into Avid, you should select “Computer RGB (0-255)” as the SOURCE color space, in the “File Pixel to Video Mapping” options.  (Rec. 709 is always the TARGET color space for DNxHD MXFs in Avid)  While importing with the 0-255 setting retains the full dynamic range, it still squeezes the entire range into the 16-235 gamut.  That loss of precision should not be as significant as viewable dynamic range for an offline edit, but if you planning to export your Avid sequence as your master without a separate conform, you should consider using a 10bit codec in Avid, like DNxHD 175x.  That will allow you to maintain both the original dynamic range and the bit depth, at the expense of higher storage space requirements.

Once you have a re-linked timeline of high quality 24p footage, there are still a few more steps that can be taken to cleanup the footage.  Dead pixels should be the first thing on the list to deal with.  Dead pixels can be caused by physical debris on the sensor or lens of the camera, or by an electronic malfunction with one of the photo-receptors on the CMOS sensor.  The result is the same regardless of the cause, with one of more pixels locked at a static value throughout the shot.  The simplest way to fix this is to cover the effected pixels with information from the surrounding area.  One procedural way to fix this is to duplicate the layer of footage in an AE comp, and mask out a similar section nearby and cover it.  (If you have a horizontal row of three dead pixels, mask the three pixels above them on a second layer, and then drop the top layer down one to cover the spot)  In most cases the duplicated data will be totally invisible, but be sure to QC the result.  If you are Twixtoring your footage to a different frame rate, fix the dead pixels before applying the rate change, otherwise the motion compensation process will cause the dead pixels to move around, making them much more difficult to remove in a procedural fashion.  The next step is to look for any rolling shutter artifacts, caused by the slight difference in time between when the top and bottom of the frame are sampled.  This difference in time can manifest itself in a number of interesting ways, including distortion, with the top of the frame seeming to “lead” the bottom.  It can also cause horizontal bands of brightness with quick flashes of light only being recognized by part of the sensor.  The Foundry has a plug-in called Rolling Shutter that can help reduce the image distortion caused by motion of the camera on smoother shots.  The horizontal bands have to be removed manually in a VFX process if you want to get rid of them, borrowing data from the preceding or following frames if needed.  The Canon DSLRs also exhibit some moiré and other aliasing issues due to the way they sample the low resolution video from the high resolution sensor.  The only way to really get rid of those artifacts is to selectively mask and blur the effected sections of the frame.  Lastly, if you are using Twixtor, QC the output for corrupt frames caused by the interpretation engine being unable to guess the proper motion of the moment in the shot.  If re-rendering with different settings doesn’t help, covering the bad frame with an original frame of footage from that moment usually solves the single frame issues.  Luckily the most difficult sections of footage to calculate motion compensate for, are usually segments of where using frame dropping conversion instead is undetectable, since the extreme motion should hide any stutter caused by the missing frames. (This is coming from a guy who is processing a lot of handheld combat footage)  Once these steps, as well as the rest of your visual effects work, are finished, you are ready to export and color, which should be similar to most other workflows at this point.

Adobe announced all of the features of the new highly anticipated Creative Suite CS5, which will include native 64bit, CUDA GPU acceleration, and better support for formats like DPX and DSLR clips.  I will have many more CS5 details in future posts, delving into how that will change the landscape of many workflows.  There are lots more new developments in the post world, but those are the primary things that stick out to me right now.  We still have two more days, and I will be spending a good bit of time demonstration Cineform’s Neo3D features at their booth at the back of the Lower South Hall.  So if anyone wants to catch up with me, feel free to stop by.

Canon DSLRs name each video file “MVI_####.mov” where “####” is a constantly incrementing 4 digit number.  It is easiest to identify individual cameras if each one is shooting a totally different series of numbers. (Like CamA = 1000′s, CamB=2000′s, etc.)  While there are no options in the Canon menus for manually setting the starting file number, there is way to trick the camera into starting at any number you want.  Reset the counter to zero in the menu, and then return the setting to Continuous.  Take a picture, and then use your computer to rename the JPEG file on the card to the desired number.  (In this case: 5000)  Put the card back in the camera and take another picture.  Verify that it incremented from there. (IMG_5001)  Format the card or remove it, and your camera will continue incrementing from that point. (So my next shot, will be IMG_5002, or MVI_5002 if you switch to video mode.)  You can reset it to any four digit number you want, and it will increment from there, unless you shoot with a card from another camera, without reformatting it first.  In that case, the camera will increase the file number if necessary, above any files already on the card.  The Canon 1D MarkIV has a few more options for filename prefixes, but the objective is the same, to create a uniquely identifiable series of filenames for each camera on your shoot.

Doing this will make it much easier to sort through your files, since you will be left with a separate numbered sequence of files from each camera.  I was recently on a two week shoot with twenty Canon cameras, and by setting their initial numbers 500 apart, (Since four digits gives you 10K possibilities, divided by 20) it was easy to sort the resulting files, even though due to logistics, I got some of the files many days after they were shot, and out of order.  If you set the clocks on the cameras accurately, the timestamps on the files will make it easier figure out which files are different angles of the same take.  Even with all that, I still had duplicate file names on that project, with 5600 files for that shoot, so renaming to a better convention will be important on most large projects.

Having a good naming convention for your media files can save a lot of time and trouble.  The info that needs to be contained within the file name will vary depending on the nature of the project.  For the Navy Seal movie I setup a convention that included Scene, Setup, Take, and Camera.  The next project I worked on was more of a documentary type shoot, with no script or scene numbers, so the file name was composed of Date, Camera, and an incrementing shot number.  The important things to keep in mind are: order the info intelligently for searching, keep place values consistent for sorting, (Use leading zeros) and make it unique within the first 8 characters for EDLs.  For the movie, 005A_02b.mov is: scene 5, first setup, second take, camera B.  If I want to see the other camera angles for this take, they should be nearby if the footage is sorted alphabetically.  And if I want to find other takes from that setup, I shouldn’t have to scroll too far. If during onlining I am looking for a specific clip based on the name, I go to the proper scene folder, and scroll down to the right setup, and start looking from there.  Now if you want to include descriptions in your filenames, put them after the unique identifiers up front.  This is because sorting descriptions alphabetically is relatively useless, but you can still search through them with regular OS tools, as long as the description is somewhere in the filename. (10_E_026_BigExplosion.mov)  And if your software at some point in the process truncates the name, there should still be enough info in the first 8 characters to identify the exact source file.

During the process of renaming, it is a good idea to keep a log of what you have done in case you make a mistake, and it forms a basis for content logging as well.  I do this with a simple Excel spreadsheet that records: Original Name (MVI_####), New Asset Name, Description, Comments, as well as CameraName, Date, FrameRate, or any other data that might be relevant depending on the project.  I also sort out the bad takes and delete the .THM thumbnail files during this stage. (The THM files are actually JPEGs that can be opened if you rename them, but I have never found any practical use for them)  Once I have this list of what I want the files to be renamed to, to fit the filename convention for the project, I convert the log into a renaming batch file.

To do this, save a copy of your log sheet as a “Text (Tab Delimited)” file from Excel. Then delete every column except the original name and the new asset name, and insert blank columns before, in between, and after those two columns. Fill each of those three columns with a unique character, like #, $, and %. Save your file and close Excel. Open the file in Notepad, and press CTRL+H to bring up the replace window. Replace “#([TAB]” with a command and the path to your media files. (“REN D:\ProjectName\Footage\”) Replace “[TAB]$[TAB]” with “.MOV[SPACE]” unless your log included file extensions, in which case just replace that with [SPACE]. Replace “[TAB]%” with “.MOV” unless your log included that, in which case replace it with nothing. (In WinXP the only way to insert a [TAB] into the Replace dialog box is to cut and paste one from the document, with CTRL+V.)  You should be left with a text file with a series of commands that each look something  like this:
REN D:\ProjectName\Footage\MVI_0001.MOV 057_T12A_NewClipName.MOV
Save this document and rename the file extention to .bat, and double click on it to run the batch.  This should assign new names that match your log to each of your files, and make it much easier to sort through your footage, if you designed your naming convention well.

The other thing you can do with you footage log is generate an ALE, so that if you are editing in Avid, your log notes can be linked to your clips within the program.  I will go into those details, and other tips for editing DSLR files in Avid, in my next post.