It is with great excitement that I am finally able to make an announcement that has been eating at me for nearly a year now. In June of 2009 when the iPhone 3GS was released I had a flash of what the future could hold for editing, and it’s that moment of inspiration that gave birth to the product I’m announcing today.

Our new groundbreaking product, Final Cut Pro Mobile, is now available on the iPhone 3GS. It will also be available on the iPad later this year. You heard me right – the full suite of FCPS apps have been ported to the iPhone 3GS, and in some cases, we’ve been able to add additional features not found in the current offerings from Apple.

Much of our inspiration at SuiteTake.com to create this mobile suite was inspired by the growing interest in editing projects outside of the office. While the edit suite has been the traditional place to get your project done, technology no longer limits us to just a single location. And it was with that vision in mind that we marched forward with the project. Here is a quick overview of what the new suite includes.

Final Cut Pro M

Starting with the current version of Final Cut Pro 7 from 2009, we included all of the same new features as well as the under the hood improvements from Apple. But we’ve also added some features that are only possible on the iPhone.

For example, with a single swipe of your finger – you can save your project, duplicate it, or permanently delete it – all with the same gesture. Swiping at different speeds determines which of the functions is selected. Now that’s efficient!

Need a quick rough cut of the footage you’ve imported? Just shake your phone up and down 3 times and the built-in accelerometer will create a rough cut using the current ins and outs of each clip. The phone will use our patented Content Detection™ algorithm to analyze dialog, body language and facial expressions. It will then systematically assemble the clips in the most pleasing and logical way.

Motion M

Complete with Open GL acceleration, 3D shadows and real-time playback, you can create graphics at uncompressed 4K or HD resolution while browsing the iTunes store, surfing the web or taking a call from your client. And all of this while you’re outside of the standard ball-and-chain edit suite. Be inspired – be Mobile!

While the standard motion templates that you’re used to are included, we’ve also added the ability to buy templates through the App Store, right inside of Motion M. Using your iTunes account and 3G networking you can download the latest templates where you want, when you want.

Soundtrack Pro M

Using your iPhone earbuds you can mix your latest soundtrack while listening to your favorite iPod playlist, checking your messages with  Google Voice and browsing SFX from the SoundTrack library.  All while walking through the busy city traffic to catch your bus to the beach.

But it’s not just about multi-tasking. SoundTrack Pro M can mix up to 256 tracks of audio in real time, has new MIDI functions available through the dock connector and now includes a cool iTunes-like screen saver to help you  see your audio as you mix. This is part of our new SeeHearMix™ technology.

Color M

Who says you need a $10K monitor to color grade your latest film? Don’t let the monitor industry make a fool out of you any longer! Using the precision color LCD touch screen on the iPhone you can grade like a pro using just your fingertips.

What’s that? You don’t have time to do the grading yourself? Again we tied into the Apple App Store and you can now purchase and download preset looks based on the type of project you’re grading. Some of the categories include Corporate Training Video, Broadcast Reality Show, Broadcast Sitcom, Over Produced Documentary, Low Budget Film, B-Movie, Direct to DVD, Flip Cam to Film Look and Barely Good Enough For YouTube. Each preset will optimize the look and feel of your video based on your target audience.

DVD Studio Pro M

Apple may not have updated DVD Studio Pro, but we sure did.

Need a DVD and need it while on the go? No problem! Plug in your favorite DVD burner and create a Standard Def or Blu-ray DVD on the spot right from your iPhone using our patented USB-BlazeBurn™ technology.

Don’t have a DVD burner? That’s OK too. Master directly to our new SuiteTake.com Print-On-Demand DVD service. Most DVDs will upload over 3G in just 2-3 weeks, and you’ll receive your DVD copies within one calendar year. Let’s face it, you didn’t really need it that fast anyway.

iChat Theater M

Using the iPhone 3GS camera,  you can now chat with your client live while watching your latest cut. You can even conference in up to three other members of the “creative team” to watch and comment on the playback of your sequence while referencing a live timecode window. Getting unwanted needless feedback has never been so easy.

And Finally, Compressor M

Compressor is more then a compression engine – it’s a publishing factory. Set up automated processes that will convert your final video to the proper format and upload it to iTunes, YouTube, Vimeo, FaceBook or just a standard FTP site.

As an exclusive to the Mobile FCP Suite, you can even export directly to another iPhone no matter where they are in the world. And all of this over 3G. Take that AT&T!

Need more speed while compressing? Using iPhone QMaster integration you can cluster up to 50 iPhone 3GSs together to cut compression times by up to 8.9%. (Estimated, actual savings can vary. In some cases render times can actually increase up to 75% due to some unknown reason that we’re still baffled by. Due to the increased radiation output of the phones during the render process, women who are pregnant or are hoping to ever become pregnant should limit their exposure to FCPm Qmaster. Do not taunt Qmaster under any circumstances.)

And with our new Social Media plugin architecture, you can send custom notifications to Twitter, FaceBook, MySpace and even the Creative Cow Forums. Now all of your fellow editors will know just how frustrated you are by that request to make “one more small change”. Partner deals with Gowalla, FourSquare and DropBox are in the works for late 2010.

I am proud to say that I think we’ve really hit this one out of the park. And we’re just getting started. Since I started using FCP Mobile I’ve realized that having a full size computer is a thing of the past. I used to say I would never give up my Mac Pro. Now I’m starting to ask myself if it even makes sense to have an office. Since I started using FCPm I have barely bothered to show up to work at all.

Still not convinced?

Check out the cover story in the next issue of MacWorld magazine for a full hands on review or read our Press Release.

Can’t wait?

Head over to the App Store and download it now. We hope you’re as excited about it as we are.

This week I have the good fortune of getting out of the cold Chicago weather and editing in sunny California. I’m was brought out to do some on-site editing for Fender at the NAMM convention in Anaheim.

Like every travel job that I do, there are unique needs that needed to be addressed. No two jobs are exactly the same.  The needs of this job resulted in me having the most sophicated travel setup I’ve had to date. Here are the details of the job.

NAMM is a convention that showcases manufactures of musical instruments and gear. It’s kind of the NAB of the music industry. Fender has one whole floor of the convention center, and my job is specific to what they’re doing here. There are 3 main areas of their venue. The Stage, where there will be live performances, both planned and as people walk up and just want to jam. There is the exhibit area where booths are setup for all of the separate companies that are under the Fender umbrella. And then there’s the “floor”, where people are just socializing and moving from one place to the other. All of these are being covered by video, and as quickly as possible edited down and posted to the web on the Fender website as well as many social media sites.

The stage area is being covered by another editor who is recording the line feed and 3 iso cameras to AJA KI recorders.

He then takes specific performances (just single songs), cuts them down, adds bumpers on both sides and compresses it for the web. He then hands it off to one of the 3 web guys that take care of the online distribution.

As for my job, I’m handling the show floor and the booths, which is being covered by 2 roaming cameras shooting DVCPro50 widescreen on P2 cards. There is an assistant that will be running cards to and from the cameras whenever they think they got something special to post. That might be a good interview, a really kick ass performance by somebody jamming out, or an unexpected moment with a real rock star. It’s rumored that Eddie Van Halen may be showing up at some point.

So, my job started out sounding pretty simple, but the more we talked it through in the pre-production meeting we realized that the big issue is going to be time. Time to get the cards, time to download and wipe them, time to edit, and especially, time to compress the final video to flash so it can be uploaded. While this can easily all be done on a single machine, it didn’t seem like the best idea. So what we ended up with was a multiple station setup, all being run by a single operator (me).

So from left to right, here’s what I have setup.

P2 Ingest Station

This machine is a MacBookPro laptop with Final Cut Pro doing nothing other then logging and importing p2 footage. The client provided the p2 reader, which is way overkill for what we’re doing. But it does hold multiple cards and connects via USB. It’s really designed to do a lot more then just read cards, but hey… it looks pretty awesome as part of my setup.

The footage is all ingested over the network to the edit station, where I continue editing as the footage comes in (everything is networked via Gigabit Ethernet and a small 5 port switch. This also keeps me from having to copy footage from one machine to the other. All of the machines are using the same drive. It’s local to one machine, and remote to the other 2.

Edit Station

The edit station is another MacBookPro running FCP. On this machine I have a small Raid 0 strip of 2 G-Raid drives, giving me 1 TB of raided space and connected via FW800. I also have a 2TB Western Digital “My Book” drive that I’m using to mirror all of my work and captured footage on-site. I’m a big believer of having a duplicate or triplicate of everything when editing on the road.

As I bring in the footage I’m first sorting it into different sequences (as opposed to bins), one for each of the companies. At some point the producer will come in and quickly tell me what footage goes up and what does not.  I will then edit down the clips with clean ins and outs, add the company logo bumper on the in and out and export it into a compression watch folder.

Compression Station

The final stage is a MacPro Tower running Episode Pro. I customized it just for this job, and it is also using the same raid drive that both the P2 ingest machine and edit machine are using. So as soon as a file shows up in the watch folder, it starts compressing it using the preset that was already created and tested with the client. The output folder is a shared folder that the web crew has access to on their end of the network (upstream of my 5-port switch).

Pulling It All Together

While it would not be too difficult to slide my chair from machine to machine, I had an idea as I was testing the system. Why not use Apple Remote Desktop to control all 3 machines from the one 23″ monitor!

So, that’s what I’m doing. From the edit station, which has a large LCD hooked up, I have access to both of the other stations, and switching is very fast and easy since it’s all the same mouse and keyboard. What an awesome way to work!

Ready to Rock n’ Roll

So at this point, I’m pretty much playing the waiting game. I’m set up, I’ve tested, retested and tested again and everything is working as expected. It all gets put to the test tomorrow.

Video compression has come a long way from the days of using Cinepak on a Quadra 950 tower and the old NuBus slots. For the most part, the wars between online formats has been settled with Flash leading the way. But behind that Flash Player is often H.264 encoded video, ever since it was introduced with Flash 9 in December of 2007. Even video powerhouse YouTube is pushing out H.264 video wrapped in a flash player. If that’s not enough, one of the officially supported video formats for Blu-ray is H.264.

So from on-line video (SD or HD) to high end Blu-ray DVD’s, h.264 is a huge player. It’s all good, right? Well, mostly. Have you ever compressed an h.264 video file? It can be unbearably long. We first started running into this bottleneck when we switched from doing mpeg-1 client web approvals (something that was very fast to compress and widely compatible) to h.264. We switched mainly because we wanted to post high resolution web approvals for our clients at higher quality, and MPEG-1 just wasn’t cutting it. H.264 really filled that need. But even a shorter video, say 10-15 minutes could take 60-90 minutes to compress on a Quad Intel MacPro, and some of our videos are more in the 30 minute range. If you have the time, leaving it running overnight is no big deal, but most of the time we’re doing these web approvals close to 5 or 6pm and they needed to be posted and sent to the client that same day. Waiting around just to finish a web post feels like a waste of time (although we did minimize this to some degree using LogMeIn as covered in my previous post).

After hearing others brag about how great it was, we finally decided to try the “to good to be true” Turbo.264 USB key from Elgato (the non-HD version). I really fought it because I had a hard time believing that a little USB key could do what my huge expensive multi-processor MacPro could not. But also because it did not integrate with Compressor, which is part of our workflow. For the price though, we decided to give it a try.

For what you end up paying, the Turbo.264 does a pretty good job. It is FAST for sure, and the output is not too bad, but it’s not perfect either. It gave us the speed that we wanted, but not the quality. One of the main reasons it’s able to do what it does so fast is that the very first thing that’s done is resize the video frame, and then pass it off to the USB key for processing. This is key, because the rest of the processing is done on a lower resolution frame instead of working with the original uncompressed frame. Great for speed, but not optimal for quality. But for many people, this might just do the trick depending on your needs and budget. You end up seeing compression artifacts in places that you wouldn’t when using compressor with similar settings, typically areas of fast movement, effects or dissolves. But it did take care of the time bottleneck that we were having. So we decided to sacrifice some quality for the sake of actually getting home on time but continued to look for other options.

Then I read a press release about a new product from Matrox called CompressHD, and I had a warm and fuzzy feeling all over. I contacted Matrox and asked them if it was possible to get a review unit and they were nice enough to send it out a week later. While it’s 4-5x the cost of the Turbo.264 USB key, (depending on which one you compare it to, the first SD key or the more recent HD version) it has some great benefits that make the cost worthwhile.  I’ve been using it for nearly 2 months now and it has taken the pain out of h.264 encoding.

Installation

Installation is easy, but for most editors the biggest problem may be finding an open card slot on your MacPro. We decided to sacrifice a SATA card to make way for the CompressHD card. All it needs is a PCIe slot. Once installed I started the computer and installed the software, and after a quick reboot it was good to go.

Integration with Compressor

The biggest selling point (aside from the speed)  is the seamless integration with compressor. Inside of compressor there is a new preset folder called “Matrox MAX H.264 Settings”. If you take a look at what’s inside, you’ll find that the presets are very similar to what you’re used to seeing in the Apple Settings.

If you’re used to using compressor, not much changes in your workflow for creating h.264 files. You pick one of the Matrox presets that fits your needs, apply it and submit just as you did in the past. However, much of the processing is now handed off to the CompressHD card. The only thing handled by compressor now is the decoding of the video frame, everything else is handled by the CompressHD card. The card has 2 processors that are optimized for different functions. One chip handles resizing/scaling, and the other handles the color space, compression and output. So what you end up with is this nice little video assembly line and each frame is passed from chip to chip to perform it’s designated function.

But what if you don’t want to use one of the presets included? What if you have specific needs of your own? No problem! You can create your own settings and still take advantage of that nice processing power. As an example, here is a setting that we created to use for web approvals.

What is the difference between the Apple h.264 presets and the Matrox ones? Nothing really. The Matrox folder was created for convenience and to streamline your experience. You can choose any of the Apple h.264 presets and they too will access the card.

If you want to compare performance with and without the card, there’s no need to pull the card out and then put it back in. Open up the control panel and you can turn the card on and off. This is what we did for the comparison tests. We’ve been running version 1.6 of the software, but the current version is 1.8 and is now Snow Leopard compatible. However, we’re still using Leopard and do not plan to upgrade until sometime late next summer.

Performance

Once we got this card in the machine, we just couldn’t wait to start compressing something… ANYTHING, just to try it out. It’s not that compression is all that interesting, but I really wanted to see how this baby performed. It was like dropping a new engine into a used car, we just wanted to hear the engine fire up. Here are the details on how we tested the card.

All tests were performed on a 3.o ghz Quad Core Intel MacPro with 12 gigs of RAM. We ran each compression twice. Once with the CompressHD card enabled, and once without. During these tests there were no other operations being performed on the machine, but only for the sake of making sure we were comparing apples to apples when we got the final numbers. One of the main reasons to use this card is that it handles so much of the work load, you can continue to work and even do processor intensive functions on the computer while having little or no effect on the compression times that the card puts out.

We used version 3.05 of compressor, that is part of Final Cut Studio 2. If you’re running the latest version of Final Cut Studio (we call it 3 because Apple forgot to give it a number) you will already have the ability to create Blu-ray movies within compressor. In our case, the card actually adds that ability to compressor, since this version of compressor does not directly support Blu-ray (only the now dead HD-DVD standard).

Our test video is 14:12 long and in 720p format using the ProRes 422 codec. The original file is 7.85 gigs in size, and we compressed it to 6 different formats as part of a single batch for each of the tests. We chose some of the most common presets that we might use, as well as one custom one that we use in house.

Here are the results.

As you can see, there is a significant difference with the card enabled.  There’s something very satisfying about watching it crank through the data so fast. It does however cut down on the coffee breaks and long walks on the beach.

One thing that I noticed is that the biggest benefit comes when you are changing resolution. This is where having the dedicated hardware really pays off. When you’re simply just converting from one format to another (say ProRes to h.264 with no other changes) the speed bump is less noticeable, but still there.

As an example, look at the Apple TV bar compared to the iPhone bar. Because the frame size for Apple TV does not need to be changed, the card just passes the frames through at the same resolution. But for the iPhone version it has to be scaled down a lot, something that the card does much faster and with better results then just using compressor.

*NOTE:  You might have noticed that the Blu-ray bar is the same on both passes. Because I was running Compressor 3 instead of the newer 3.5, Blu-ray is not supported natively. So on both passes, the CompressHD card was used. So kind of pointless for our purposes, but I left it in anyway.

Image Quality

The image quality is as good as anything coming out of compressor natively, but at a fraction of the time. In all of the tests that we did I couldn’t see a quality difference between using the card or not. Compared to video run through the Turbo.264 key, there was a noticeable difference. Again, I’m not totally knocking the Turbo.264 product, it does have its place. I use it all the time to convert movies/tv shows from the TiVo format to iPhone so that I can watch them while at the gym. But for trying to exceed the expectations of my clients the Turbo.264 key falls short. We’ve also had problems with it dealing with anamorphic footage properly without having weird scaling and cropping issues.

One thing to be aware of is that the CompressHD card will only do CBR compression, not VBR. Not a huge deal, but something to be aware of. This is also a limitation of the Turbo.264 usb key. VBR adds a much better quality to file size ratio then CBR, but in my experience this is not much of an issue. Disk space is abundant, the internet is fast and both SD DVD and Blu-ray can hold plenty of data. Not a huge deal.

Just to give you an idea, here are some file size differences based on the same source video.

Compatibility

One of my original concerns was that the card might interfere or conflict with other capture cards from AJA or BlackMagic, but it plays nicely. The codec’s that Matrox wrote are based on the Quicktime Component architecture built into QT, so any hardware or software that supports the implementation of QuickTime Component will work just fine.

Matrox Product Integration

It’s worth noting that you can get the CompressHD hardware (called the “MAX“) as part of some of the other Matrox products. For example, you can purchase a MXO2 and get it outfitted with the MAX card for just $400 more, saving you a $100 over buying the card separately. One of the great benefits of this is the ability to run this type of hardware on a laptop that has a Express34 slot, instead of just a tower. One of the down sides is that you can’t use both the MXO2 Max for editing/monitoring while the hardware is compressing. It’s an either/or situation. But for many that will be a small trade off for the ability to take this mobile.

The SuiteTake

At a street price of $499 the CompressHD is not exactly cheap, especially if you only occasionally need to compress to h.264, and time is not an issue for you. But if you encode as much as we do and don’t’ want to spend your whole week watching a progress bar, I would whole heartedly recommend getting the Matrox CompressHD. It’s a solid piece of hardware that integrates nicely with the FCP workflow so seamlessly you will forget it’s even there. That is, unless somebody takes it away from you.

Late last year we added a new camera package to our offerings at Edit Creations. In part because we wanted to diversify the services we had to offer, and also because it played into a spinoff company we’ve been working on. That new company would be a lot more production based then Edit Creations currently is.

We looked at all the options out there in the sub 10K price range, and after weeks of research ended up with a Sony EX-1. That really surprised me because when we started the search I was pretty much set on the Panasonic P2 format and the AG-HVX200A model. Not only do I have experience with that camera, but almost everything else we do is shot in the DVCPro HD format, so we have a nice workflow in place. More then that though, I can’t stand editing in the MPEG-2 format. It’s fine for shooting and can capture great images, but once you get it into the edit system you can be assured you will rendering more then ever before. But in the end, the Sony EX-1 won hands down in image quality, built in features, and price. There was just no denying it.

So, what to do with the workflow?

On the first several projects we tried multiple different ways of attacking the projects. Everything from working in the MPEG-2 format natively to converting everything to ProRes and editing with the converted files instead. We also have extensive experience working with the Sony software, which includes XDCam EX Clip Browser and XDCam Transfer.

In addition to all of this trial and error, I was training a client on how to handle the workflow for his own project (he was renting our camera). But it seemed every time I met with him I was saying “OK, I know I said do it like this, but now there’s a whole new way to do it”. Nothing like learning on the job to keep everybody on edge!

So here we are now, about 6 months later, with what I believe is a solid workflow. So if you’re using EX-1 (or XDCam footage of any kind) you can learn from our mistakes and start off on the right foot.

In The Field

If you’re new to using a tapeless format, it can be very unnerving to spend an entire day shooting and have no tape to show for. To avoid disaster, redundancy is the key.

A simple but important note – label your media cards!!! Use a sharpie or a nice printed label, but make sure each card has a unique name/number. This will avoid confusion in the field when you drop your cards into a pile of other cards and don’t know which ones have footage to download and which are empty. Seriously, this one little step can save you in the field.

Assuming you don’t have enough SxS cards to make it through an entire day of shooting, you’re going to have to offload the cards and erase them in the field so that they can be reused (see, you’re already freaking out). Here’s how we handle that task.

In addition to the producer, camera person and possible audio guy, it’s ideal to have a AP or junior tech person with you. The handling of the media cards is very important, and getting it wrong can be disastrous. Don’t underestimate how important this is, just because it’s easy. We call this person the Media Assistant (MA from here forward).

The MA has the job of offloading all cards in the field, checking to be sure files were successfully transferred, and then erasing the clips from the card so the card can be reused. The equipment used for this is a MacBook Pro and two portable FireWire or USB drives. You can do the same thing using the PC but we’re all Mac here so I’m unable to provide any details on that side of things.

As each card is filled by the cameraperson, it’s passed off to the MA. The MA will then load it into the Express 34 slot on the MBP and it will mount on the desktop as an external drive (make sure you have the proper drive installed on this machine so that the card will mount on the desktop properly). Then, using a program called Shotput EXPress, the media is copied, simultaneously, to two different external drives (you can do up to 3 different locations. While you can do this manually in the finder as well, Shotput EXPress makes it more automated and does a nice data verification as it copies everything over. It just adds another layer of security.

Once the media has been copied, Sony’s XDCam EX Clip Browser software is used to view the clips on the drives and verify that everything looks and sounds as it should. At this point we’re just spot checking a random sampling of clips. Once the MA is satisfied, the inserted SxS card is erased by selecting all clips and hitting the delete key (this is also done using the Clip Browser software). The card is then given back to the producer or camera person for use again.

Once the shoot is over and the producer is back at the office, the footage is all copied to 2 different full size (and less expensive) drives. One is used during the production of the project by the producers and editors, and the other is a backup, and is stored with the client. It’s essentially equivalent to the box of beta tapes the client would have received in the past. After the media is successfully copied to the larger drives, the mini-drives are erased and ready for the next shoot.

As a side note, don’t cheap out on your hard drives, especially the big ones that are the final destination for your camera originals. A good drive does not cost that much more then a cheap one. Just ask yourself how much your shot day is worth, and if you would be willing to pay to reshoot everything. I highly recommend buying drives from G-Technology. While they’re not the cheapest, they are backed up with the best warranty in the business, they run quite and most of all, cool. On the flip side, STAY AWAY FROM LACIE DRIVES! I can’t tell you the number of editors and clients who have horror stories about drive failures, myself included. We used to have a ton of them but sold them all on eBay just to avoid any additional disaster.

Preparing for the Edit

While the free Sony tools can be used to screen and prep for editing, we have opted to go the route of having a FCP work station for the producer. After doing it both ways, we feel this is the most efficient for both the producer and the editor. (We’re currently looking into setting up a FCP Server workstation to streamline this process even more).

At this point loading, logging and transferring footage is the same is using P2 footage. Using the Sony FCP Logging plugin outlined in a previous SuiteTake post, the footage is loaded into the Log & Transfer window and clips are marked and labeled. As each clip is identified, it’s added to the import cue and converted to QT movies that FCP can edit with. The files you end up are basically MPEG-2 files wrapped into a .mov file. (For faster logging, check out our post on log and capture shortcuts.)

While going through this process, the producer can import multiple clips from a single recorded clip, add clip names and log notes, and organize footage into multiple bins as desired. This is all typically done to a drive designated as the “project drive”, so what you end up with is a single drive that has the FCP logging project with all of the bins and clips, and all of the transferred and transcoded media. This is what is handed off to the editor at the start of the edit.

Once the editor receives the drive, the project file that the producer created is opened, and all bins/clips are copied and pasted into the current working project (or the template project if we’re starting one from scratch). The project the producer creates is treated as a log project only, we do not edit inside that project.

With the new bins/clips pasted into the working project, we then use media manager to move all of the logged footage to our local edit drives and re-link them. We never work off of client drives, and instead opt to always have the footage on our own system. Since we have dedicated raid systems on each edit system, it’s a lot faster and it’s easier to keep things organized on our end. Once everything is copied over and re-linked we eject the drive and give it back to the producer.

Editing

So the main drawback to editing with the XDCam/EX-1 footage is that it’s saved in the MPEG-2 format. Because it’s a long GOP format, there’s not actually a full frame of video for each recorded frame of video. So when editing, FCP has to recreate those missing frames. While on the fly editing it’s usually seamless, the moment you add a transition or anything else that requires editing FCP has to create these new frames (FCP Calls this “Conforming MPEG-2 Video”), and THEN render. It adds a whole new layer of processing and even on a fast machine it’s a slow process.

So, what to do? There are three basic options.

Transcode to ProRes
While logging and importing footage inside of the FCP Log & Transfer window, you don’t have the option to transcode the footage into any other format. However, once that the footage has been imported and wrapped into QT files, you do have the option to convert everything to ProRes using compressor. What you’ll end up with are iFrame based video files that look as good as the original, but are more “edit friendly”. You’ll be able to edit quickly in a ProRes sequence with minimal rendering, and be able to do compositing without watching the image degrade right in front of your eyes. The drawback is you’re adding another step to your process, and depending on the amount of footage you have and the speed of your machine, it can be a very timely step.

Edit Natively in the XDCam EX MPEG-2 Format
For some very simple and short projects, this is actually a good option. Just drag your first shot into the timeline and let FCP match the timeline to your raw footage, and everything will play and edit in real time and you’ll be pretty happy with how it all comes together. But there’s one trick to make it go smoothly.

After you’ve let FCP match the sequence settings to you footage, open up the settings for your sequence and go to the “Render Control” tab. Make sure all rendering is done to ProRes instead of Same as Sequence. This way whenever you do need to render it will take less time and you won’t be compressing back into the MPEG-2 format. This essentially removes the conforming step that FCP would otherwise need to perform, at least while editing.

Exporting your final sequence will go slower then you might be used to, but it’s usually tolerable unless your project is very complex with lots of effects/render files. Because you’re exporting back into the XDCam EX format, it has to convert everything back into the Long GOP MPEG-2 format, which is very slow even on a fast machine.

Edit in a ProRes Timeline
You can also setup your timeline as a ProRes timeline for whatever frame size/frame rate matches your source footage. Once you do this, you can edit with your footage and for the most part play it back in real time (except for some effects) with FCP’s RT timeline. The advantage to working in this way is that since you’re working in the ProRes codec, your footage will continue to look great even if you throw lots of layers, graphics and effects at your project.

The huge down side to this is everything, and I mean EVERY-THING must be rendered at one point or another. Even if you’re able to play things back in real time while you’re editing using the RT features of FCP, when it comes time to print to tape or export a master QT file, you will have to render everything and it can take a very long time, even on shorter projects. You will end up with a very nice, high quality ProRes master file, but if you’re on a tight deadline this might not the way to go.

The Best Way?
After trying all of the above approaches on multiple projects, I don’t think this is a single solution that fits every project. I think before starting each project the best thing to do is look at the details of that project and decide. For simple projects that are short, mostly cuts and dissolves, few graphics and no real layers, staying in the MPEG-2 format is by far the fastest way to go. But if you have a more complicated project with layers, keys, graphics and so on, I would work in the ProRes world so that the image quality holds up though all of the processing.

At least for the majority of projects we do, transcoding everything to ProRes before we start is not really efficient. It takes too long and just adds an extra step that we just don’t have the time for. So in my opinion the it’s just not worth the time penalty.

The SuiteTake Take?
The EX-1/EX-3 and the higher end XDCam cameras have all proven that you can create some great images and record them to the MPEG-2 format. MPEG-2 cameras have really matured over the years, and they’re far superior to the baby brother HDV format cameras.

But understand that if you go this route there are tradeoffs when you get to the postproduction stage. The tradeoffs are not nearly as bad as they used to be and there are now multiple ways to handle the challenges – but they are still tradeoffs.

When starting any project, you should always consider the entire work flow start to end before shooting your first frame of video. If after doing this the EX-1/EX-3 fit your production needs, I say go for it.

Believe it or not the built-in tools in iTunes can be useful in a Final Cut Pro working environment. In this quick video tutorial I’ll show you some hidden features in iTunes that can help you maximize your efficiency and better your organization when importing music tracks into FCP projects.

When Compressor (part of FCP Studio) works, it works well. And when it doesn’t, it can be a really pain and waste of time trying to get things working again. For me it’s a true love/hate relationship.

Have you ever went to submit your batch compression only to find that you don’t have the option to submit it to anything?

When you try to click on the cluster as shown above, you don’t have the option to select the default “This Computer”, or anything else for that matter. If you just try to submit it anyway, you’ll get an error telling you to re-install Compressor. But don’t (at least not yet).

There is a simple Terminal command you can run that will, at least for the moment, fix the problem. Try the following.

Open your terminal program and enter the following command. You will need to enter the administrator or root password when prompted.

sudo SystemStarter start Qmaster

Then for good measure, run this command as well.

sudo qmasterprefs -reset

The first command restarts Qmaster, and the second deletes the pref file.

If you have compressor open, close it and reopen. With just a little bit of luck, when you try to submit again you’ll see everything back to normal.

In my experience, this fix is temporary. It may work or the rest of the day or even several days, but the problem eventually comes back. If you know of a more perminant fix that doesn’t involve reformatting the drive and reinstalling everything, let me know.

It’s been a few years now since the battle over which video format would dominate the web. It’s hard to argue that over the last few years Flash is by far the clear winner. From entertainment sites like YouTube to news organizations like CNN, when you watch video changes are it’s Flash encoded.

I would argue that as far as quality, bit rates and file sizes go, Flash is not the best choice out there. But its cross platform ubiquity is unquestionable.

This post is not going to get into all of the ins and outs of Flash, but I want to discuss one point. VBR (variable bit rate) and CBR (constant bit rate) encoding.

For those who don’t already know, a CBR encode simply applies the same number of bits to each frame of video, regardless of the material being encoded. The data rate is setup at the start and is applied throughout the encode. What you end up with is a very predictable file size and a very steady, predictable stream of data when playing back the file.

With VBR you also set a data rate at the beginning of the encode, but instead of applying that amount to each frame of video, frames are analyzed to determine how many bits are really needed to recreate the image. The bitrate is actually averaged over the frames, sometimes going lower and sometimes higher then the number you have set.

For example, a talking head over a static background would require less compression then a busy city street full of traffic and people. In the first example, much of the screen from frame to frame stays the same, while in the second example virtually every pixel on the frame will change. What VBR does is apply more data to the frames that need it, and less to frames that can get by with less. As a result, you end up with a very good picture, and with a smaller file size. Sometimes, a significantly smaller file, depending on the material. I recently encoded an 80 minute video in both VBR and CBR for a client. THe CBR file was 267 megs, and the VBR was 169. This is a huge deal when you’re paying for server bandwidth!

I should mention at this point that not every compression program will offer both CBR and VBR, and on some programs it actually costs extra. For example, Sorenson Squeeze includes CBR compression for encoding into the On2 VP6 Codec, but if you want VBR it’s an extra $100.

So you might be wondering why you would ever want to use CBR if VBR creates a better image and smaller file size. Well for one, CBR is a much faster way to encode. Because each frame  does not need to be analyzed, it can take half as long. So if time is an issue, CBR might be the answer. Especially if you’re talking about doing on-line approvals for a job and quality is not as important as having it to the client on time.

There is another reason to consider CBR. Streaming.

If you are encoding files that will be handed off to a client to be used elsewhere (as opposed to creating the files for your own use or site) one question you should always ask is how the files will be used. If they are for the web, they can be streamed using a Flash streaming server, or hosted as a progressive download over a typical http server. Which one is being used affects how you should encode the file.

When a file is being hosted by a streaming server, there is a set bandwidth for the streaming pipe. For example, a service may guarantee that a 500 mbit stream will play without any pausing because they dedicate 500 mbits to each client accessing the file. So with a CBR file, things work well. The server provides the proper bandwidth, and the file stays within that limit. But with VBR, the rate is not constant. And not only does the rate drop when fewer bits can be used, but it can spike to higher then what the dedicated pipe was expecting. The end result is very jerky playback that’s nearly impossible to watch, especially in busy areas of the video.

So the most important thing to take away here is to always ask what the file is being used for. Never make an assumption that even your client knows, often they are just relaying what they were told. Whenever I’m asked for any type of compressed file (Flash or anything else), I always ask how they will be using it, not what technical specs they want. The answer might be PowerPoint, web, CD, laptop playback, or anything in-between. I have found that nearly half the time asking this question (and sometimes several follow up questions) changes what I deliver, and in most cases avoids having to do it over a second time.

Asking pertinent questions is the most important thing you can do for yourself, as well as your client.