I’m migrating from wordpress to my hosted server, so you can find everything here at www.luminoir.com from now on. All further updates will be reflected there.
———-
If you’ve ever searched on a bittorrent search engine for a tv programme, you’ll notice their filenames are always in a certain format.
Part of the reason for this, is that programs like TvShows, ted (Torrent Episode Downloader),
and others rely upon standardized filenames to find and automatically download these torrents as soon as they’re released.
What the uploaders and programmers understand very well is that a strongly standardized filenaming convention makes
searching for these files and recognizing when they have been released significantly easier for the software.
Let’s say you are looking for the latest episode of Battlestar Galactica. The latest file is Battlestar.Galactica.S04E04.Escape.Velocity.HDTV.XviD-FQM.[VTV]
As all episodic torrents use a very similar filenaming convention to identify the exact episode of a particular series,
the software only needs to find “battlestar galactica” followed by S(number)E(number).
Once it has ascertained that this is the latest episode by checking that the Season and Episode numbers are indeed the latest available,
it recognizes it as the latest file and downloads it.
As you can see in the above filename even information such as the
Episode Name, Resolution, Compression Codec, Compression Profile and the encoding group is contained in the filename.
In turn, this can be used to our advantage as content creators to organize the vast amount of files we have to deal with in our work.
This allows us to take advantage of spotlight and FCP’s find function in the bins and timeline.
Example
This is an example of a filenaming convention I enforced on my assistants and PAs for a video game review series.
————————-
Filenames will be in this format.
Game-S[season #]E[episode #]-[Game name]-[Type of footage]-[Shot #]-[description]
Filenames should always use leading zeros. eg (EP01 NOT EP1)
For example
Game-S02E04-Rock Band-Gameplay-05-Drum Tutorial (Say it ain’t so)
Game-S02E09-MGS4-Interview-08-Matt Jones talks about engine
Game-S02E14-Halo4-B roll-13-Master Chief mascot at E3
TYPES OF FOOTAGE
Essentially the types of footage depend on the nature of the segment.
For Reviews the types of footage are
1. Gameplay
2. Music
3. SFX
4. Commentary (only for sports games)
5. VO
For Interviews, they are
1. B roll
2. Interview
3. VO
SHOT NUMBER
The numbers before the description eg(05-Drum Tutorial in the above example) are not as important for interviews captured from tape
as I can refer to timecode on the tape to see the sequence of events.
The reason I need it for gameplay or any footage we capture wild without timecode/device control is so I know the sequence of gameplay
rather than trying to guess if COD5-snow stage is before or after COD5-Helicopter stage.
If the files are
Game-S02E15-COD5-06-Snow Stage
Game-S02E15-COD5-12-Helicopter Stage
I don’t need to guess.
MULTIPLE SEGMENTS WITH SAME GAME
If we are doing multiple segments on the same game over an episode,
we will give the individual segments names and label it into the Game name.
Game-S02E21-Halo4 History-Gameplay-04-Halo3 FMV
Game-S02E21-Halo4 Technology-Interview-Jonty Barnes on new co-op features.
————————-
Rationale
We have become very used to organizing our files in context using folders.

However, when you take these files out of the directory structure,
their filenames are not useful and do not help you identify
which project they are from or indeed what types of files they are.
With organized filenames, you can use spotlight to search your media drives without having to sift through hundreds of false positives.
(instead of searching for “VO”, you can look for Game-S02E45-VO, and not have to scroll through every other VO you’ve ever ingested.)
This is most evident when you media-manage a project in FCP,
and your painstakingly created bin structure is lost as all linked media files are placed in a single bin with a flat directory structure.
Also, finding all the files in a project is significantly easier.
If I wanted to find only the B Roll footage of Rockband in for example, it’s just
Command
|
Action
|
| cmd-4 |
Browser Window |
| cmd-shift-a |
deselect, this forces the search to commence from the top,
otherwise it searches starting from the selected file |
| cmd f |
find |
| enter in search field “Rockband-B Roll” |
|
| find all |
|
This finds all Rockband B Roll but excludes the interviews, VO, etc.
This applies for any type of footage if the filenames are standardized for this in mind.
Playing Nicely with others
Why don’t I use the comments/labelling in FCP to make these distinctions in the types of files?
Files are often transferred to other departments like graphics or audio and sent back to us when the work on them is done.
So all the metadata and comments that we add in FCP to a ingested or imported file may or may not be interpreted by the software that your audio post house or graphics department uses.
In addition, naming these files makes it easy for them to find and forces them to conform to your filenaming system.
For example, you may send your audio-post house a file for a job you’re doing for a bank, let’s say ABN Amro.
They might send the file back as “ABN Amro Project FINAL AudioMix.aiff”, especially if they’ve only ever done one mix for an ABN AMRO project.
But what happens if you have more than one job for the same client?
If you send the file as “ABN Amro-TVC-CashFast Credit Banking-Final Online”, your audio-post house is more likely to use an adaptation of that filename like
“ABN Amro-TVC-CashFast Credit Banking-Final Online with AudioMixDown” and it won’t get mixed up with your ABN Amro Corporate Video.
Creating templates
Having these standardized filenames becomes very useful when you deal with an episodic series.
As each episode progresses, some creative decisions may be taken that will be maintained throughout the remainder of the series.
These then have to be updated into the template project so all future episodes follow this standard.
But it’s a pain to have to make changes to your current episode while updating a template project to reflect these changes in the future.
Take heart, there is an easier way.
Look out for more on how you can use the power of standardized filenames to easily maintain episodic templates
in my next article “Be replaceable, have a life.”
In that article, I’ll go in detail about steps you can take to hand over a job to another editor with minimal fuss
and how you can help him get up to speed as fast you can can walk out the door.
The Sudden Rise of FCP
July 6, 2008 · Leave a Comment
I was trained on the Avid Meridien platform and my first time using FCP was on my very first job which I took on part-time while I was in my final year at Film, Sound and Video in Ngee Ann Polytechnic.
My employer at that time had a G4 running FCP v1.2.
It was slow, unstable, crashed a lot, lacked realtime effects support and dissolves needed to be rendered.
Suffice to say, it failed to make much of an impression. It was an interesting mix of a NLE with some motion graphics capability but lacked many of features we have been spoiled with on the Avid.
In the interim, I worked on the Avid Meridien based systems and transitioned to the Adrenline when that line was EOLed. I became overly familiar with the Avid error messages to an embarrassing extent.I remember a producer quizzically looking at me when I started explaining to her about DRAGON Error messages, BUFFER OVERRUN and UNDERRUN codes.
Progress
During that time, under the auspices of Apple’s ProApps department, FCP improved. Enough for Walter Murch to decide that he could do Cold Mountain on it. Before that, Rules of Attraction, Full Frontal and The Ring had also been cut on it.
It was a necessary response from the company now that Avid had decided to migrate to Windows XP for the Adrenaline, Mojo series of Media Composer. Apple no longer had a video killer app solely available on the mac platform.
Apple had to get marketshare back somehow set that in motion by purchasing Keygrip from Macromedia and renaming it Final Cut Pro.
Apple’s G5 became the biggest dongle in the world for the new fastest growing NLE.
Avid’s regression
Avid still had a dominant installed userbase and felt no need to compete with Apple on the basis of their disruptive price point. DVXpress was deemed to be their equivalent product line, but the restriction of it’s maximum output resolution to DV25 without additional hardware meant that it’s usefulness would be restricted to the hobbyist/prosumer/budget/boutique production house.
Avid’s workflow for footage originating on tape is first class.
The media management tools, offline/online media reconnection all save us loads of time by storing it in the omf media database and enabling simple and mostly painless media management.
However, importing files to Avid, has always been a pain for the exact same reason.
Importing video files in particular is akin to pulling teeth. The files have to converted to omf media on import before they can be used.
If the current show I’m editing was done on the Avid, I would easily be converting up to 80% of my footage.
Also, the disruptive price point of FCP meant that a lot of boutique production houses were sprouting up. Final Cut Studio meant any one man operation with $2500 had the tools (not unnecessarily the skills) to compete with a production house with an Avid and graphics department.
This has resulted in the freelance editing market shifting from 80% Avid, 15% FCP, 5% others in 2002 to what seems to be a 70% FCP, 25% Avid, 5% others pie. (These numbers are obviously not scientifically gathered, it’s just me asking other freelancers the percentage of jobs they do on each platform.)
Apple’s complacency
Apple hasn’t really been pushing the boundaries of what FCP can achieve. The impression that Avid seems to have given up on competing with them for the budget/boutique user demographic seems to have left them free to their own devices. Both companies neglected to have a booth at NAB.
There are numerous bugs that have existed from the first version I used (v1.2) to this very day.
Particularly annoying are the edit to tape compression error, the keyframe editor redraw bug, inconsistent render file linkages and the fact that every point update breaks the project file.
I think the problem with FCP is that the Proapps team seems to find it cooler to add new features than fix existing bugs.
The Future
I hope Avid continues to try to compete with FCP.
Competition is necessary for innovation and I think the best work we’ve seen from both developers were when they were fighting for marketshare. It would be great if Quantel, Sony (Vegas/xpri), Media 100 got back into the mix. The key to FCP’s sudden increase in marketshare wasn’t Avid users throwing away their Meridien and Nitris Boxes. It was the multitude of new users investing in hardware/software that was no longer priced out of their reach.
This market is ever expanding and it would be a great pity, not to mention a missed opportunity, if other companies allowed Apple complete dominance of this space.
Categories: FCP · editing
Tagged: apple, avid, comment, FCP, hardware, software