Prepping and Exporting for Post Audio in Final Cut Pro
Beginning the audio edit of the post production sound process requires receiving the correct files and media from the editorial facility. I’ve always had my standard “list of deliverables”, but over the past few years I’ve found that quite often the export of these files from Final Cut is not done properly. Thus, I’ve created a document (as well as explanations) outlining what a sound editor might need, why, and how to do it.
We need 3 main things in Post Audio: The media, the file which points to the media, and a video copy of the project to use as reference. The project file and media are pretty self explanatory, however, the video can complicate things. Audio needs the video file so they can:
- Match the old / original audio and new audio against the picture.
- Check sync of all dialogue, music, and effects.
- Place foley and sound effects at specific points in time.
As I’m sure you can understand, all of these go on the assumption there is “picture lock”. A more appropriate would be “picture timing lock”, as every edit and decision a sound editor and mixer makes is dependent on the timing of what is on screen. If the timing of the picture is changed during post audio, the sound will fall out of sync instantly – like dominoes. That is why it is paramount to have complete picture lock before starting audio. Unfortunately, due to timing constraints on some pieces, the audio edit has to happen while picture is still being edited. This can be the most grueling part of being an audio editor. Products like Virtual Katy help bridge the gap by comparing old edits to new edits and moving audio appropriately. However, there is no one click fix, and I cannot stress enough: if at ALL possible, only work with a cut with picture timing lock.
Next, editorial has to provide post audio with a video with a visible timecode marker on the video. This is referred to as a “Time Code Window Burn“.
Now that we have that clarified, let’s move into the specific requirements.
I. Quicktime movie with Academy Leader, 2-pop, and tail pop and embedded audio guide track. (see below for EXPORT settings)
Academy Leader is that familiar 8, 7, 6, 5, 4, 3, 2 countdown you see before some older films. Each number is on the screen for 1 second, except the “2″, which is on for 1 frame (this is where you hear a beep – also 1 frame in length). This is what’s known as a 2-pop. The Academy Leader is a carryover from mechanical film projector days. The machines had to have time to “slew” – that is, ramp up to speed so the film projector and audio system could get up to speed and be in sync. The 2 Pop was an audible indicator that things were in sync, because it lasted just as long as the visible “2″ – and at the same moment. A tail pop is analogous to the 2-pop – only at the end of the film. This is used to ensure that sync is retained through the entire piece. If the 2 Pop is in sync, but the tail pop is not – then there is a sync issue somewhere within the piece. I use this as a simple check. I also like to have the picture editors audio “mix” as a reference / guide – not only for yet another way to check sync, but because many directors & producers fall in love with audio work the picture editors do – and may want to use those in the final mix. (Ed. Note: See comments below for a correction to this explanation when dealing with film and feet)
II. OMF export that includes all audio data and NO video (see OMF export details below)
OMF (Open Media Format) is a “container” of media, along with instructions for your audio editing system as to where to place these media files in the timeline. If your audio editor is using Pro Tools – you’re in luck – Pro Tools can understand OMFs, provided they have that option purchased & enabled. Pro Tools can read OMFs with audio – but not video. Thus, the video must be generated separately.
Details for Final Cut Pro Media Export
QUICKTIME GUIDELINES:
- If for TV, divide your program into reels that span commercial break to commercial break.
- If for film, divide your program into reels, corresponding to the same length as your picture reels.
(these above two allow for smaller segments of media to be transferred from the editorial house to post audio, and is easier on the editing systems to generate and work with, plus the opportunity to not screw up the entire piece, if just one reel’s timing has to be changed) - Quicktime .mov**
- Timecode window burn (SMPTE timecode – HH:MM:SS:FF)
- Insert Academy Leader, 2-pop, and tail pop into your sequence
- If academy leader is not used, then a black slug with a one-frame visual pop 2 seconds before FFOA (first frame of action) and 2 seconds after the LFOA (last frame of action) must be added. Additionally, an audio pop (1kHz one-frame beep) must be added to match sync with the visual pop.
TIME CODE BURN:
Make a new sequence in FCP, maintaining same sequence settings as your master project. Name it same as the original locked sequence plus “_TC”. Nest your entire master project sequence into the new sequence (you can do this by dragging your master project sequence onto the time line of the new sequence). If you don’t nest the sequence, the timecode print will not print continuous timecode from HeadStart to tail sync. Be sure the PICTURE START mark is the very first frame of the timeline.
In the Browser, (important–NOT from the Effects menu) click the Effects tab. Open the Video Filters folder. Then open the Video folder. Click the Timecode Reader effect, and drag it down onto the new _TC sequence. This puts a Time Code window burn on the picture. It is imperitive that when you do this, you place the nested clip in the new _TC sequence at the exact same Timecode it resided at in the original sequence. Why? Because if you don’t, the Timecode reader effect will burn the wrong code into the exported movie, and will ruin any kind of obvious sync point. The OMF you will export for me will not match the video Time Code window burn, and there will be many sync issues.
Next, in the CENTER box click the circle with the crosshairs. The crosshairs will appear in the Canvas. If you click and drag the crosshairs in the canvas, that will adjust the placement of the timecode window. When you have placed the crosshairs where you want the window, release the mouse. Place timecode window to obscure least important pix area, usually bottom-center, within title and action safe.
QUICKTIME EXPORT:**
You can export a QuickTime movie from either the Browser or from the Timeline. Make sure you have an IN and OUT marked in your sequence so the QT movie will be limited by the marks. To export a QT, make sure the sequence with the window burn (see instructions above) is selected in whichever window you’ve clicked in (Browser or Timeline). Then go to File>Export>Using Quicktime Conversion. When the dialog box comes up, name the sequence so you recognize it as your sequence with time code burn (i.e. “your project name_TC.”) Direct it to the folder on your drive where you want to save it. Under Options (where it may say “Current Settings”) navigate to the codec of choice. Click settings and make sure both AUDIO and VIDEO are checked, and that FRAME RATE is set to CURRENT.
OMF EXPORT:
Once the QT movie is exported, go back into FCP to export an OMF. Select the MASTER sequence you made earlier (not the _TC), prior to the timecode window sequence. File>Export>Audio to OMF. Make sure your IN and OUT points are the same as your QUICKTIME export, listed above. Change the default Handle Length to AT LEAST 5 seconds (00:00:5:00 – but more is better!). Include Crossfade Transitions should be checked. Click OK and navigate for a place to save the OMF – in the same folder as the Quicktime export. Name it “your project name_OMF” and click Save. This allows the audio editor to get your audio with the same timecode (in the metadata) as the picture you just exported.
Important notes:
- Nested sequences are NOT allowed to be used in your OMF export for audio. If your project contains nested sequences (i.e. your timecode sequence) your OMF will export, but will not be completely usable – your audio files within the nested sequence will be mixed together, and therefore practically unusable in post. Therefore, you MUST un-nest all nested sequences, and place them in your master project before performing the OMF Export.
- OMF files have a 2GB limit. This is due to OMF being created back when 2GB was a huge size! Because this may cause a limitation in long form and audio heavy FCP projects, you may need to export several OMFs. A common practice is an OMF with tracks 1 & 2, an OMF with tracks 3 & 4, etc. Project length and audio density will dictate how many tracks you can export in 1 OMF – and still be under 2GB. It’s good practice to name the OMF with the track names, and what kind of audio is on them: dialogue, music, effects, etc.
**This can be any time of MOV file. The type of file will be dictated by what the sound editor’s computer(s) can playback and use. Often, this will be a DV file (for SD) or DVCProHD (for HD). If the audio facility will be projecting the image, they may require a higher quality MOV file. If a second computer is used for video playback – like Digidesign’s Video Satellite, an even high res file may be requested. Always check with the audio editor for their desired MOV file format.
*My thanks to users of the DUC (http://duc.digidesign.com) for their input on this document!
It Came From The Searches Volume 2
Matt Stratton turned me on to Clicky Stats awhile ago, and through Clicky, I’m able to see what web searches come up with my blog as a result. I also see when these searches lead them to my blog – but then they leave because they didn’t find the answer. I thought since the search engines think I already have it on my site, perhaps I should. Below is a sampling of the search queries (that I can decipher from cryptic keyword searches) that my website supposedly already has the answers for. So, I present to you:
It came from the Searches, Volume 2.
March 10th, 2010 – March 18th, 2010.
optimum use of cores on macpro using redrushes
As many as humanly possible. Unfortunately, Red Rushes is not as optimized as it could be, so there will be plenty of horsepower left over, even when red rushes is chugging away. We have to wait for Red to enable distributed transcoding, or, use another encoding solution.
FinalCutServer Slows down
What is slow? The transcoding? Check in / check out? Network traffic will slow check in / check out. Background processes and concurrent users will slow down Final Cut Server – especially if transcoding is happening in the background.
“Prores Avid Import” , “importing FCP into Avid MC” , “convert DNXhd to pro res 422” , “how to import mac prores into avid”
Right here: http://michaelkammes.com/editorial/getting-final-cut-pro-projects-andor-media-into-avid-media-composer/
P2 or DNxHD?
What flavor of P2? You can edit more tracks within Media Composer in real time with DNxHD. You also have more latitude when color grading and compositing, but files sizes are traditionally larger (assuming DNxHD 145 or greater).
unity nab rumours
Yeah, sorry. NDA.
avid dnxhd convert to prores
I assume you are on a PC. Windows cannot encode into ProRes – Apples limitations. If you’re on a Mac, you can export to ProRes from the Export menu, and change your codec / compression to ProRes.
Avid-qualified Windows-based with quad core processors
http://www.avid.com/products/Media-Composer-Software/system-requirements.asp
I will caution that if this a single quad (and not a dual quad) then only the newest Nehalem based Processors (HP z400, for example) can handle DNxHD encoding in RT.
Avid Mass Storage
Avid has several flavors of their own storage –VideoRaid SR (local) and Unity (shared) and ISIS (enterprise shared). However, Avid can use just about any storage that your OS can understand. I recommend firewire400 at the bare minimum (no USB) and esata, infiniband, or fibre if you can afford it.
“michael kammes”, “mkdc”, “micahel kammes”, “Michael Kammes Burbank”
Why yes, that’s me. Whats up? Say hi to your mother for me.
“DNxHD PE codecs IN FCP 6” , “quicktime output avid media composer for final cut hq“
Ya gotta download them.
http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=263545
FCP can export to any codec QuickTime understands…so, once you download the codec you’re golden. Keep in mind , this will export a DNxHD .mov file, NOT a DNxHD .mov in an MXF wrapper, which is what Avid needs to understand a file without transcoding or a quick import.
getting broadcast quality for fcp mov
That’s tough. ProRes is not a SMPTE standard, therefore, delivering a ProRes file will never be required for a broadcast deliverable. So, you can either A) lay it off to tape or B) transcode to a SMPTE compliant file. DNxHD, for example, is a SMPTE standard. DNxHD 145 closest in quality to ProRes 422.
“”final cut” network storage best practice” , “final cut server edit in place”
Permanent storage, like fibre. FCSvr does not like storage to go offline. Ever. Thus, get permanent storage, and set it as an “Edit in Place”, so FCSvr does not need to copy media to and from it to do conversions. EiP tells FCSvr that the storage is permanent. I recommend a RAID and several spindles, A) for speed B) for redundancy and C) faster performance for multiple users.
inexpensive final cut pro server
Buy a new, base level Xserve. Buy a 10 seat FCSvr license, buy a small RAID5 array, and buy Matt Geller’s book “Getting Started with Final Cut Server.” For anything more advanced, you’ll probably have to contract out.
the best fibre storage for final cut server
How much do you need? I’ve always been a fan of Sonnet or G-Tech.
better than final cut server
CATDV, in most cases. http://www.squarebox.co.uk/
edit in place final cut server rights share
If I understand this correctly…. Yes, you need to have Read AND Write permission to any volumes FCSvr will use. Yes – even if you don’t intend on writing to the volume, you still need that ability. It’s a limitation of FCSvr.
mxf wrap dnxhd
High(er) end encoding solutions can handle it, like most of Telestreams product line.
do stereoscopic 3d mxf files take up more storage space
Nope. Avid dumps half of the picture information to get to signals (left eye and right eye) into 1 HD Frame size. The remaining 2 halves, when combines, equal one regular frame. Thus, same file size.
“avid media” samba share
Nope, can’t do it – if you’re trying to share an OMFI or MXF folder within Avid.
Mac Pro 8 Core 2.93 Nehalem install red rocket
Red Rocket is not entirely stable on Mac, and the workflow is kluge. Wait a little bit.
difference between pro res 422 & pro res 422HQ
Higher bitrate. Both are 10bit, but HQ has the ability for higher quality because of less compression.
quality loss transcode to 220x?
What was the original source? If uncompressed, you should see no difference on the scopes.
“Ruby on rails and final cut server” , “final cut server Web-Based Review and Approval issues”
One of my favorite “wow!”s during a demo. Ruby on Rails released a “module” for FCSvr which gives basic functionality and framework for a web based review and approval process. It’s buggy and kinda unreliable, but gives people a GUI concept of what FCSvr can do.
dnx36 file format
Great Avid Offline Codec. Not broadcast quality, but looks great. DNxHD36 is for 23.976fps material, DNxHD45 is for 29.97fps material – but both belong to the DNX36 family.
optimum compressor config for final cut server
Use those virtual clusters!
http://www.kenstone.net/fcp_homepage/compressor_multi_cores_stitzer.html
http://www.fcsoutlet.com/home/Studio_Outlet/Entries/2008/9/1_Virtual_Clusters_-_Compressor.html
Hum in Avid sdi Mojo analog audio signals
Sounds like (ha!) you have unbalanced audio going into your Mojo SDI. This is common – with no ground, hums (60Hz, usually) often occur because of dirty power and/or a power cable being to close to your audio gear. Put a ground lift on your AC plugs or power-strips
encode red r3d episode engine
As long as you have the codecs on your machine, yes. However, it’s the Wavelet extraction only, at 2K.
final cut pro and avid unity bugs
Decreased performance for starters. But that’s been known. Expect a 20-30% speed drop-off when using FCP on Unity.
p2 versus xdcam HD in Avid MC 4.0.5 2010
What flavor of P2? I like how XDCAM HD 35mbit looks compared to DV100. However, I like the way AVC based P2 Media looks, but it needs transcoding (for now)
“Macbook Pro”+”dual boot”+Avid+FCP
Yes! I do it on my laptop. You need to blow your HDD and OS away, and partition the drive off into at least 2 partitions, and install an OS on each one. Then, install FCP on one partition and Avid on the other. I do this so I can independently update my OSes without hosing up the other. Hold down the Apple key on boot to select which partition to boot into.
HD AT dnx36 broadcast quality
No. DNxHD145 is the baseline for broadcast quality. Yes, you can transcode DNX36 material to DNX145, but while that may meet the deliverable spec, it won’t look good.
final cut server metadata dnxhd
If it’s DNxHD in an MXF wrapper – no. Final Cut Server cannot parse all of the metadata in an MXF wrapper –currently.
“mac mini” NLE
Yikes. Holy horsepower Batman. You’re gonna need it, and the mini doesn’t have it. I’m not even sure FCP will install.
edit dnxhd in fcp
Not natively. Downlaod the DNxHD codecs, and put the timeline in unlimited. Or, pre-render into Pro Res for an easier time editing.
It came from the Searches Volume 1
I’m on a plane from Vegas – after nerding out at the Digital Signage Expo. It’s a full circle, having been christened into Digital Signage around 2002 with Graybow. Glasfire (3M’s Vikuiti), if any of you remember. In any event, this short 50 minute jaunt from Vegas to Burbank gives me time to write a quick blog.
Matt Stratton turned me on to Clicky Stats awhile ago, and through Clicky, I’m able to see what web searches come up with my blog as a result. I also see when these searches lead them to my blog – but then they leave because they didn’t find the answer. I thought since the search engines think I already have it on my site, perhaps I should. Below is a sampling of the search queries that my website supposedly already has the answers for. So, I present to you:
It came from the Searches, Volume 1.
dnx-36 firewire 400 and bandwidth requirements DNX36
Yes, DNxHD36 (aka DNx36) can certainly work through a firewire400 pipe. DNxHD36 runs at a 36mbps, while firewire400 has a theoretical max of 400mbps. This makes firewire400 a fine choice as a transport for DNx36 offline workflows.
29.97 and dnx36
This is a source of confusion for many Avid users, and I’m in the process of authoring a blog on this. DNxHD36 is a “family” according to Avid. While the “36″ label refers to the data rate for 23.976 material, the DNxHD36 “family” codec can be applied to 29.97 material. This would be technically known as DNxHD45 (45mbps as opposed to 36mbps).
“episode engine” cpu restriction
This is kind of vague. Within Episode, you can assign priority of encodes and cpu usage. Quicktime already is pretty poor with processor usage to begin with, however.
Metafuze Lossy?
Yes. After all, you’re transcoding from one codec to another – there will always be quality loss. In addition, DNxHD is a lossy codec – so, yes.
edit room day rate
This varies wildly. Depends what gear is in the room, what the room is used for (editorial, audio, finishing, color, etc.) your experience, and geographical location – and hell, what your rent is! Normally a reputable rental rate at a good facility would be a couple hundred bucks per hour or even much more. As a side note / soap box, don’t sell out the rest of the industry by undercutting other facilities. Talent and experience are worth the money. That’s a majority of what the client is paying for – not the gear. By undercutting everyone else, the industry is forced to adopt your lower rate as a standard, then everyone has to drop their prices. And the cycle continues. You’re shooting yourself in the foot.
Does clipster support facilis
Clipster runs on Windows XP 64bit, which Facilis has a client for. Fibre is the best choice (Ethernet won’t deliver the bandwidth needed), and it should be a recent version of Facilis software to enable file locking – volume locking will cause organization issues, but can be done.
convert red footage cluster setup
I wish I could do it better than these guys have:
http://www.kenstone.net/fcp_homepage/compressor_multi_cores_stitzer.html
http://www.fcsoutlet.com/home/Studio_Outlet/Entries/2008/9/1_Virtual_Clusters_-_Compressor.html
fcserver script
Good luck. Most everything is manual at this point. Try CATDV as a more GUI based alternative.
QIO-PCIE sonnet tech
The QIO comes with either a PCIE host card or a E34 (Express slot) host card. Unveiled at NAB 2009, and finally shipping now! Mac only support for now. List Price is about $1000.
FTP, KiPro
Well, once the KiPro encodes to ProRes, you can certainly FTP the file – although it’s gonna be huge. Your best bet is to offload it to a portable drive for transport or use a transfer solution like StorageDNA.
share msm database avid
I can only assume you’d like two or more machines to access the same Avid Database at the same time, in order to share media. Nope – the functionality you are attempting to do is achieved through Avid Unity, ISIS, and Interplay.
final cut server frontend
Final Cut Server (FCSvr) clients have a front-end based in Java; it looks the same on Mac or PC – and the administrator can restrict what functions a client can have. A popular alternative is creating a web page interface which ties into the database and media of FCSvr. The functions on thew web page are usually limited and typically only used for “review and approval” functionality. Several companies out there can create a custom web based interface – although it is far from cheap.
episode pro pro res 422
Yes, If Episode is running on a Mac, you can encode and decode into any of the flavors of “ProRes” (1 word). Decoding is only available (currently) on the Windows version.
Encoding During Editorial
Last week on my POST Magazine blog, I briefly discussed Encoding in Post: The Four Hot Spots. I figured, “Why not elaborate on one of those areas?” Thus far, I’ve discussed the concept of Pre-encoding, and various facets of the final encode. Let’s talk about the most vital and often overlooked area: During Editorial.
Of course I’m (initially) referring to the almighty DVD, which all of you assistant editors need to burn daily – all, naturally, with different watermarks and circle takes or various cuts. Plus, that Blu-Ray for that Director with the fancy car – you know who you are.
However, more and more above your paygrade individuals who foot the bill for your paycheck are using non-traditional devices to view media. The web has undoubtedly become the new standard, with petaflops of media files being FTP’d daily. Flash, Windows Media, and heavily Compressed Quicktimes are all popular options – and many times, are all needed. New fangled video enabled mobile devices – like the iPhone, Blackberry, and Droid – have increasing become the way to view video while on the road between business meetings and Starbucks pit stops. Those facilities that have been wise to adopt Digital Asset Management (DAM) internally will also need a version for tracking, as well.
So, yes, dear assistant editor, you now have several DVDs, web versions, and mobile versions to create. Plus, there is always – always – that oddball version you need to create. It’s inevitable. All in time for the next edit session tomorrow.
This is when you need encoding. And a hellova lot of it.
I can only hope that all of you, dear readers, are familiar with the concept of a Quicktime (QT) Reference. No? Then Unca Michael will enlighten.
A QT Reference is simply a pointer file.
It’s a small media file that appears as a full movie file to most media players, but during playback, it points back to the initial media used in the generation of said QT reference file. Think of it like that bookmark in your web browser. That bookmark isn’t the entire website, but it pulls up the website when you click on it. It’s a link.
QT references are your best friend. Why? Most NLE’s can generate a QT Reference much faster than exporting a whole “complete” file. Thus, less time watching a progress bar. (Although, ironically, having the wait time does give you time to get coffee to stay awake and watch the progress bar longer. Interesting.) This speed boost is accomplished by having the NLE only create new (render) files for media that has some sort of effect on it in the timeline. All other media is untouched, and thus, the QT Reference can point to it. Brilliant!
So, I’ve already saved you oddles of time. Waiting.
Now, I need to earn that bonus, and you need to take this QT reference goodness and utilize the strength of it’s pointers to create the compressed files needed for your deliverables.
At this point, it may be a good time to check out this post, as I explore choosing the right encoding solution. In a nutshell, you need an encoding solution that can accommodate all of the formats you need to deliver. It’s mighty beneficial to have a solution that can encode into multiple formats at once. Again, less thumb twiddling time.
Here is where I drop the “But…” bomb. I must tell you something vital when dealing with QT references: Your encoding solution MUST sit on the same network as your edit system and media storage. Huh? The QT reference is aware of where the original media is in relation to itself when it is created. If a user were to say, I don’t know, email the file, or even move the QT reference to another folder (even on the same system), the link to the original media is lost. Yeah, big gotcha. That’s why I recommend having your encoding weapon of choice on the same SAN/NAS as your edit bay…or have a firewire drive on standby to copy the QT reference and media (retaining the same hierarchy) to move from the edit bay to the encoding solution.
Solutions like Root6’s Content Agent (see my review here) are actually built explicitly for this purpose: not only can Content Agent sit on any Windows compliant SAN, but the system can handle concurrent encodes, auto FTP files, email status updates, and automate DVD burning with watermarks. And while I’m sure burning and labeling those DVDs fulfills your life’s purpose, there is even a more efficient way to streamline that. Look into Rimage: Automated network DVD authoring and label printing, scalable from small runs to large runs.
While I am sure this will not keep you from many late nights in the edit bay, it very well may give you a few more hours to crash on that old couch in the back of the room.
A little somethin’ for the Producers….mass review and approval made simple.
I recently was posed with a relatively simple quandary from a studio:
How can I get edits which need review out to non tech savvy producers for approval so they can:
A) easily view the edit (did I mention easily?)
B) stay out of the edit room.
Of course, sometimes A) means burning a DVD or laying off a tape, which is time consuming, not secure, and let’s face it, decidedly not green. It also can eliminate FTPing a file to a server to then be downloaded and watched as a viable solution, as sometimes this walking and talking at the same time complication can cause more time in tech support than just letting them in the edit room, which violates B).
Aside from my column and proposed workflows with Final Cut Server, I have something even simpler…and in 2 flavors.
Scenario 1: Small scale.
What you need:
Your Edit Bay NLE
Generic Computer (Mac, most likely)
AppleTV with Video Monitor (HDMI)
Extras: Encoding solution, Shared storage, same LAN access.
Procedure: Editor exports a full QuickTime file in the appropriate H.264 format for AppleTV, to a shared network drive. AppleTV runs off of iTunes, so your generic computer picks up the H.264 file, which sync (or streams) to your AppleTV. Now, the producer can view the cut in the comfort of the plush couch of his 4 wall, and not in the edit room. This can be streamlined even further by having the editor export a QT Reference to a watch folder, which the encoding solution would pickup (make sure all volumes containing the referenced media can be seen by the encoder) and proceed with the H.264 encode, then sending the file to the generic computer running iTunes. Having all of the satellite AppleTVs stream from the 1 machine makes media management very easy.
Limitations?
5 AppleTVs can sync to 1 iTunes Library.
1 AppleTV can stream from up to 5 computers.
AppleTV is specific in what formats it will play.
Scenario 2: Larger Scale
What you need:
Your Edit Bay NLE
Several Mac Minis with DVI to HDMI cables (for a Plasma / LCD display), Apple Remote.
Extras: Encoding solution, Shared storage, same LAN access.
Same concept applies: Editor exports a QT or QT reference, and either the 3rd party encoding solution delivers the file to a shared network drive, or the NLE does.
Here is where the Mac Mini comes into play.
OS access is a no-no for a 2 year old. And for Producers – for the same reason. So, here is what I did:
Create an admin account on the Mac Mini. While in this account, create a new user (“Producer”), and enable Parental Controls on the account. In Parental Controls on the Producer account, activate “Use Simple Finder” and “Only allow selected applications”. In this box, select the application Front Row. Make other changes at your discretion, but these are the biggies. This will ensure that this user has limited access to OS functions and can only run Front Row.
Now, we need a way to have the Mac Mini see the shared / network drive without user intervention. Automator is an easy way to accomplish this.
Open Automator. Create a workflow that:
Gets Specified Servers and make sure to put the username and password in the URL; i.e.: afp://username:password@192.168.1.1/DRIVE_FOLDER_WITH_ENCODED_MEDIA
Add a “Connect to Servers” Action.
You can download the workflow here: producer_automount.
Save this as an Application.
Run this to test. Does it work? Great!
Now, create an Alias to this shared / network drive. Place this alias in the Movies folder on your Producer account. This allows Front Row to see movies located on the shared / network volume. You can change the name of the alias if you wish to something a bit more verbose.
Place the Automator Application you’ve created in the Login Items under the Producer account. Also, add Front Row. Set the system to auto boot into the Producer account. In System Preferences, disable any Bluetooth keyboard / mouse options – so the Mac doesn’t look for Bluetooth devices. If this is not disabled, the Mac will look for devices on bootup, potentially stalling the launching of the Automator Application and Front Row. Reboot. As the system is rebooting, disconnect your keyboard, mouse, and make sure you have your Apple Remote handy.
When the computer reboots, it will boot into the Producer account, auto mount the network volume which has the media you want them to see, then launches Front Row.
Now, using the Apple Remote, navigate through Front Row, and through the MOVIES section. Because we placed an alias to the network drive (which the computer is connected to via our Automator script), Front Row can now see that drive.
Success!
Now, you have the ability to play back ANY file format QT can play back, from an unlimited number of machines AND restrict access to what clips can be seen by mounting different network shares though Automator.
As an added bonus, if the Producer decides to think outside the proverbial box, and hit the MENU key on the remote while at the Front Row main menu – it will take them to the OS desktop. Surprise! No keyboard and no mouse make tampering very difficult, PLUS you’ve already locked out OS functions with Parental Controls. All they can do is turn the Mac Mini volume up and down…. and simply hitting the MENU button relaunches Front Row.
Success! Easy edit review with a nice Apple sheen.
The Money Room
Off and on for several years, I was involved with a post facility that had what they referred to as “The Money Room” Quite apropos, not only for the greenish hue to the walls, but what they *did* in that room. Unbeknownst to them (but now beknownst to me) the so-called castoff activities and backroom chores which took place in that space are now the new(er) ways to make money at your post facility…and even be a marketable service.
In this room, aside from the usual barrage of CD and DVD authoring, download and uploading of files, temp graphics and label creation, they did basic encoding, usually by a lesser paid assistant. Certainly not glamorous, but essential. Definitely not the first notions of what a post facility does: Offline and Online suites. Finishing. Audio rooms or dub stages. The flagship rooms.
Why?
Well, typically your talent – the editors who have named clients – command more in terms of pay than the backroom assistants, and the talents’ workspaces also have a lion’s share of the gear with which to make them shine.
Yes, I am of course referring to the almighty R.O.I.
With the current race to zero, rates for the client focused suites are continually dwindling, definitely at odds with the cost of gear and talent operating within them. Possessing a ‘Money Room’ already begins with less overhead – both financially and technologically.
So, what can you do in this money room to earn some of dat cabbage?
First and foremost: Encoding. Every website nowadays is content rich, from youtube to Facebook. Everyone has multimedia on their phones. All of these media riddled avenues necessitate a *special* and unique format. Those have to be created somewhere. Why not from you?
Utilizing your offline / online bays to chomp through 100 different formats for deliverables – when you could be billing for editorial or finishing in the room – is simply poor planning. A facility could conceivably upgrade to a new computer for the Online suite, and use the older machine as an encode station in the Money Room. This not only boosts the productivity (and marketability) of your Online suite, but also gives your Money Room a CPU to encode with.
So, I have a box with some processors. Now what?
Quicktime References. Have your offline / online bays and your encoding station see the same storage over a SAN. Whether it be via SMB re-share / Ethernet, Fibre, or simply cloned / portable firewire drives, these are a sure shot to not only increase productivity, but create a more efficient workflow. Have your editorial room export a QT Reference which links to the original media, then have the encode machine pick up that reference file, and let the number crunching commence. You’ve now significantly cut down the export time out of your edit bay (QT References are much faster to generate than a complete export) and also freed up the client bay for other activities. Hopefully more glamorous. Hopefully billable.
I recommend you create encodes for the following:
• H.264 or the like for web review and approval, or FTP uploads. Perhaps even iPod or iPhone versions.
• Flash versions for embedding in websites.
• MPEG formats for DVD or Blu-Ray dailies and/or screeners.
• Predefined proprietary formats for youtube, Facebook, myspace, Hulu, etc. Each site has its own requirements for submissions. Perhaps you can charge per location’s format?
Advanced encoding software packages allow for multiple simultaneous encodes on one machine, and some allow for distributed encoding over many machines. Others still utilize watch folders that are always looking for a QT Reference to begin encoding from, and even sets of parameters for multiple groups of encodes. What a value add it would be to tell a client that you could not only do the editorial, but give them deliverables for any destination they could desire – same day.
So, you’re not billing out your editorial room enough to justify something like this. I get it. As an example, this is where the promises of highly compressed formats (such as RED) being quicker can actually backfire and allow other revenue streams.
These abnormally large sized and compressed files are still a very, very intensive process for editorial machines. It takes a great deal to chomp through a 4K file – especially when 99%, if not more, of this material will never be viewed at 4k, or even on a playback system that would do it justice. More often than not, you will see it at less than 50% of its original quality – HD – or even less on broadcast TV or on the web. Given this truth, one can make an argument for simply downrezing the raw 4K footage to a manageable frame size and codec; like DNxHD for Avid or ProRes422 for Apple. This previously difficult to manage format in now in a much more edit machine friendly format for use in the editorial process. These formats can exceed broadcast quality standards – very appealing.
So you’re a purist – I get it. You want to have a 4Koutput. That doesn’t mean you can’t do a pre-encode (in this case, transcode) to an offline format for ease in editorial. Despite being suitable for broadcast, DNxHD and ProRes 422 – as well as DVCProHD – make create offline codecs, too. Provided the computerized tool (or the assistant!) does things right, your facility can matchback from the offline material to the 4K when onlining. Sound familiar? This is what telecine houses have been doing for years to DVCam –and charging you a ton for it.
I’m amazed at just how under-utilized this concept is: not only as a pure way to tighten ones belt, but to simply be more efficient. As an example, I happened to be at one of the studios here in Hollywood that gets the editorial output – rough cut and fine cuts – in one, and only one, format. A format that is antiquated and popular almost 10 years ago. Each department downwind of that facility spent hours encoding into a format they could use with their systems, meeting their visual and technological specifications. Imagine the amount of money spent in manhours working around this issue.
The film? Catch it this summer in theaters. Budget is $200 million.
Cheatsheet for Stereoscopic in Avid Media Composer 3.5
Summary: Avid Media Composer now has the ability to edit stereoscopic footage, by combining the 2 separate “eyes” into a single video stream.
-
Launch Metafuze on a PC. (comes with the Avid installer, or download here.)
-
Import the Left Eye & Right Eye (in that order) Folders. Avid calls this scanning. These will have unique file names, but the numeric values in each file name will match Left Eye & Right Eye files, and must have the same file format (size & resolution) and same duration.
-
Highlight a Left Eye file AND a Right Eye file. On the right window pane there are transcoding options. Select your flavor of DNxHD, and Click the Create Stereo Group button.
-
You now have Avid appropriate (OP1a) MXF wrapped video files which can be loaded into Avid (without Avid having to re-wrap the file). Utilizing the Stereoscopic settings in Avid, you can now view Left Eye or Right Eye only, over/under, or checkerboard. Remember, you can only view your 3D playout correctly via the DVI port on your computer – not via the baseband video output on your Mojo or Nitris DX. Don’t forget your IR 3D glasses and 3D capable display!



