The New Camcorder Search, Part 3

Having spent the last few weeks studying the camcorder market, I realized I had to develop a list of criteria to make the decision to buy a new camcorder. The falling Canadian dollar also became a factor—with retail prices on electronics undoubtedly to rise as a result, I had to decide sooner rather than later. So… here are the four main criteria in my decision-making:
1. Mini-DV format
2. Firewire/IEEE1394 equipped
3. Final Cut Studio compatible.
4. HD and SD capable

Compression is the main factor behind the first two items. Mini-DV and Firewire are still the best in terms of the least amount of compression applied by the camcorder or computer. Hard drive, DVD-RAM, and flash memory camcorders use higher compression than mini-DV cameras, so tape still wins (until I can afford those fancy P2 card systems). USB-2 is faster than USB, but it’s still not as good as Firewire. I’d rather not add additional compression by using a slow transfer bus.
The third criteria is dictated by the computer I’m using for post-production. I’m not upgrading from Final Cut Studio 1 as explained in an earlier post, so the camcorder has to work with it and the G5. From what I’ve read on various websites and forums, as long as you correctly tell Final Cut what kind of footage you’re uploading, it should be able to accept any SD or HDV camcorder. Mini-DV cams record video as 60i even in 30p or 24p format, but FCS can handle the various pull-down ratios. Most of the problems I’ve read about on the HV20 User and other forums are related to people not setting the right format before attempting to capture. And Adobe AfterEffects has some additional capacity for dealing with pulldown ratios if Final Cut can’t.
Finally, with HD becoming so prominent in broadcast, online, and home entertainment video, the smart choice is to buy an HD camcorder. I still need something that can play SD video for the projects already shot on SD. So it has to be a dual-format camcorder.
Other factors, although not critical, are related to the fact that I’m replacing a camcorder. I don’t think Canon has changed the form factor of their batteries, so my still-good Ultura batteries could be carried over to another Canon (this, of course, gives a boost to the HV30). An XLR mike input would be really nice having used an inline transformer with the Ultura for all this time. And if the new camcorder fits in my camcorder bag, I’ll be happy.
Next week, the decision and the purchase

The New Camcorder Search, Part 1

My needs for a new camcorder are simple: I need mini-DV so that I can recapture stuff I’ve already shot, and I want to continue to use mini-DV tapes as that format still offers less compression than consumer-grade hard drive and DVD-burning camcorders.
The leader of the camcorder pack, out of the gates, is the Canon HV30. This is the successor model to the HV20, the camcorder that brought great excitement and joy to the indie filmmaking scene when it came out in 2007. The HV20 offered, for the first time, a decent HDV camera for less than $1000 USD. The HV30 ups the ante by offering 30p as well as the two formats the HV20 offered (24p and 1080i).
I wasn’t aware of what a CMOS camcorder was prior to the HV20’s arrival, but the image quality is high enough to offer HD capability, something I haven’t worked with yet.
Naturally, the first question is whether or not the HV30 will work with my Mac. I have a 1.6 GHz G5 equipped with Mac OS 10.4 (Tiger) and Final Cut Studio 1, and I don’t anticipate upgrading to anything any time soon. My Mac had no problems capturing 24p shot from Panasonic DVX100 and DVX100A cameras we’ve used, so the next step is to see if FCS 1 can cope with whatever pull-down process the HV30 uses for 24p.
The HV30 comes with a Firewire-400 (IEEE 1394) port (as well as USB-2, HDMI, and component video, and composite video ports), so it’s not a problem getting the signal from the camcorder to the computer. The question is, of course, whether or not the computer and the camcorder speak the same language.
Next time, the other camcorders in the running.

Web Video

Over the last few weeks, Mullet and I have been spending a lot of time discussing web video, and I realized haven’t written about it here very much.

When I started buying video gear seven years ago, the 3 major players in web video were QuickTime, Real Player, and Windows Media Player. All three played a range of codecs, but there weren’t easy ways of moving between the three formats. Being a Mac user, I used QuickTime by default, but I did have the other two players on my computer.

The players were all clunky and finicky. It wasn’t uncommon to see reduced frame-rates, lowered resolution, and even minimal action to make things look better.

Back then, I didn’t have a website or even an internet connection. The main means of delivering video was by running the signal from my capture card to my VCR. VHS was king—everyone, amateur or professional, used tape.

When I upgraded and got my G4, I suddenly had a DVD-R burner, and that led me to supplement Final Cut Pro with DVD Studio Pro (a couple months later, the Final Cut Studio bundle came out at a lower price than what it cost me to buy FCP and DVD-SP separately—thanks, Apple!).

Thus equipped, in 2003 I made history at the late, great Second Ciné video show by being the first to submit a video on DVD. But it was still a VHS world, and I backed up that DVD by exporting my clips to my VCR.

When I traded in my G4 for my G5, the new PCI expansion slot arrangement rendered my capture card useless, so I dropped the VHS option completely. By then, DVD burners were cheap enough that the indie world had shifted away from VHS.

DVD seemed to be the new king, unbeatable with its portability and flexibility. You could play it on your TV with a regular DVD player, or you could put it in a DVD-equipped computer. DVD sprouted in rental stores and retailers, offering special features and all the things impossible on VHS (subtitles and audio tracks in different languages, commentary tracks, alternate endings, etc, etc). The disks didn’t wear out like all tape-based technologies do—with care and handling, you would see the same image quality on the 1000th play as you would on the first play.

For an indie producer, you could easily crank out a DVD (maybe not the DVD-9 dual-layer format, but something that worked in most players and nearly all computers) that looked and played the same as the big boys’ disks.

I bought the 3rd edition of Chris Gore’s excellent film festival book in 2005, and we started to base our video efforts on the advice given. Film festivals were still king, and most of the ones that encouraged indie contributions readily accepted all the digital formats.

I bought Gore’s follow-up book on producing indie DVDs and used it as the main guide for our first appearance at the San Diego Comicon in 2006.

But it was at San Diego that I saw the future, and its name was not DVD but web video.

The big 3 players were still in the game, but Apple had introduced a new wrinkle—the iPod and iTunes. With incredible ease, you could download podcasts and listen to them on your Mac or iPod. The arrival of video-capable iPods sparked video podcasting. Flash video had arrived in force, with the help of some serious web video sites like YouTube. The big three media players changed membership, with Real player becoming a distant fourth. In fact, by 2006, I didn’t even have Real installed on my G5 as nobody was putting out video that QuickTime or WMP wouldn’t handle.

Gore and Mark Bell from Film Threat hosted a couple of panels at the con’s film festival (where my costumed appearance got some nasty looks from the black-clad filmistas—clearly a line is drawn in some people’s minds between the film fest and the convention itself!), and I attended a couple of them.

In one panel, Gore and Bell introduced the two guys behind Ask a Ninja as well as a couple of people from Hope is Emo, two of the most popular podcasts. I was still sans-internet at home, so I wasn’t aware of how big podcasting and web video had become. More people were watching these online videos than hundreds of film festivals put together.

But the indie aspect of these productions—Ninja was shot in the star’s apartment (painted up for green-screen production)—made it clear that you didn’t need a lot of money, just enough technology and, of course, a good idea well executed, to build an audience.

DVD suddenly looked less essential, just like VHS. Apple introduced its TV interface, and with flatscreen TVs and computer monitors becoming essentially the same, the average consumer realized they didn’t need a disk or tape to watch movies, TV shows, and indie video. The messy blue laser fight didn’t help, with the traditional market split into 3 different camps—DVD loyalists, Blu-Ray, and HD-DVD. Even with HD-DVD losing the fight, most people I know aren’t rushing into the blue laser world. After seeing CDs largely replaced by web music, most people are expecting the same of video.

So… in the 9 years I have been dabbling with indie video, I have seen it change completely. A physical product is no longer the primary goal since you can find a larger audience thorugh the magic of internet pixels.

Mullet and I are prepping our old feature, Babysitters, for web in small chapters. Our long-in-development DVD project is now a web video project with a DVD version also available. We’ll follow the footsteps of successful web video people like Rob Schrab or the guys behind Chad Vader and put the videos online and make a full-quality DVD available for sale.

More on web video to come. After all, it’s Tuesday. There’ll probably be some new development on Wednesday….

Upgrade Update and Why DVD Studio Pro is Teh Suck

First, an update on my upgrade plans. I’ve eliminated one option from my ongoing post-production software. Way, way back in an earlier entry, I wrote about upgrading from Final Cut Studio 1 on my G5. I played with Red Giant’s Magic Bullet suite and came away impressed. I also played with Adobe AfterEffect’s demo (which I haven’t blogged about yet). Last week, I started to research my third option, Final Cut Studio 2. That’s when I discovered a problem with FCS 2: my G5.

I have a 1.6 GHz G5, the low-end model of the first release, the slowest G5 ever made. I have a stock model, with an extra gigabyte of RAM. The original graphics card is the stock GeForce FX5200 Ultra, a card that isn’t certified to power Color or Motion 3. The card I would need is the Radeon X1900 G5 Mac Edition, which is no longer available new (Amazon and eBay prices range from $250 to $350 for used and "new" cards. Apple carries an X1900, but it's the version for the Mac Pros).

My G5 turns five in August, so I have to ask, “Is it worth spending $300 to upgrade an old computer so I can spend another $600 to get Color and Motion 3?

I’m not convinced my colour-correcting or motion-graphics skills are worth $1000. And there’s no guarantee my G5 will run the apps efficiently. Therefore, I’m taking Final Cut Studio 2 out of the equation. And then there were two….

And now our second topic. Last week, we got the Ed & Red appearances dubbed from VHS to mini-DV. I was able to capture the footage, edit everything in Final Cut, use Compressor to convert the footage for DVD, and then set up a project in DVD Studio Pro.

I’ve always found DVD Studio Pro to be the problem child of Final Cut Studio. It works great up until I start a build or format a DVD. I don’t recall any projects where I didn’t have to trash all the build files and start over. Sometimes, each disk I burned required me to trash and start over again. Clearly, Apple doesn’t care about the DVD—it’s the interwebs, stupid!

The Sock DVD is just for friends and family who missed our appearances, so I did a barebones project, with four options: both complete shows, the excerpts of us, a main menu, a menu for each show, and a disclaimer video to make sure nobody plays it around kids or at work. Nothing fancy, or so I thought.

So as I started to burn a test disk, the app crashed. One moment, it was on screen, the next, I was staring at the Finder. This happened every time. I trashed all the build files and folders, rechecked the project—everything I’d done in the past that had worked I did. But nothing worked, even after rebooting, checking Software Update for anything related to Final Cut Studio 1, sacrificing a goat to the gods, etc., etc.

So I trashed the video and audio files and re-rendered everything through Compressor again. I started from scratch and reprogrammed the DVD. But as I started to drop the video from one of the shows into its track, DVD Studio Pro again vanished. This happened each of the four times I tried it.

A third trip through Compressor seemed unavoidable, so I went back into Final Cut and removed the chapter markers from the troublesome track. Compressor churned out new files, and I went back into DVD Studio Pro muttering things about Steve Jobs. I put together the entire project from scratch, for the third frigging time. Then, sure I was ready to toss the G5 off the balcony, I clicked on Build/Format again, but opted to build a disk image instead of burning directly to disk. Then I went into the next room and watched TV to bring my blood pressure down.

To my shock and horror, DVD SP actually worked. I had a working disk image on my hard drive. Using OS X’s Disk Utility, I burned the image to a blank DVD and, lo and behold, I had a working DVD. So… hopefully… this is a workaround that continues to work going forward.

DVD SP allows you great control over every aspect of your DVD, so I am frustrated by Apple’s inability to prevent it from blowing up real good….

Earth Hour, YouTube, and Web 2.0

We had a big media blitz for Earth Hour here in Canada this year, and I decided to do my part and shut off all lights and appliances for an hour on March 29th. This I did.

But I did run one electrical device: my camcorder. I put my trusty ol’ Canon Ultura on my tripod and parked it in front of my balcony window to capture the beginning and end of Earth Hour. I used my Canon wide-angle adaptor (similar to this but not the same model) on the Ultura to make sure I got as much of the landscape as possible, so the balcony railing and the ceiling above it are both curved—but I caught a much wider angle than I would have otherwise.

I captured it the next morning to my hard drive, used Final Cut to edit it, and sent it through Compressor to prepare it for YouTube. I sped the footage up to 1000%, so each minute of video became 1.7982 seconds. I must admit I was impressed with Final Cut’s abilities to do so—with frame blending, it became seamless. Watching the headlights of cars showed how smooth Final Cut can be.

Here’s the video:



You’ll see someone slide the screen door open and then the balcony door several times—if I do this again, I’m putting a moratorium on going out on the balcony until after the camera’s shut off!

After I’d rendered and exported the video to QuickTime, I used a Compressor preset I’d obtained from Ken Stone’s website. The tutorial you’ll find there (by Brian Gary) is quite thorough, and I’ve been really impressed with the quality after YouTube finishes rendering. One thing to remember—you can ignore title-safe and action-safe as your entire video ends up on YouTube.

As I was waiting for Compressor to finish rendering, I wondered what the world in front of my balcony looked like on video on any other night—would it be a noticeable difference? So 24 hours after Earth Hour, I shot more video, with the camcorder in approximately the same spot.

I captured the subsequent night footage, sped it up and exported it to QuickTime as before. Then I brought both clips into Motion, where I planted them side-by-side with a background and text to try to make things clearer. I considered doing a wipe back and forth between the two clips, but side-by-side made the most sense for quick ‘n’ dirty video. I sent it through Compressor and then uploaded it.



As of tonight (April 1), the first video has 137 views and the second has 98. Some people have added comments, the “honors” link shows that the videos were in the top videos for their category, and I feel I’ve made a small contribution to the Web 2.0 phenomenon. Interestingly, the first video I put up, Hotdog, has gone from my 3 test viewings to 22 views since the other videos first appeared. I have no idea how anyone wathcing environmental videos would respond to Hotdog’s somewhat scatological bent….

I have had some time to think about the impact of these videos given the comments people have made—there was a 2-person mini-debate about global warming in the 2nd one—and I think I should have made clearer that I was shooting a great swath of residential space, where streetlights from a few major roads as well as row upon row of residential streets, dominate the landscape. The busiest stretch of highway in North American, the 401, crosses just below the horizon as well, so a lot of those lights were not part of Earth Hour. If I’d been able to shoot the skyline from my tiny bathroom window, I would have cpatured the CN Tower and the bank towers downtown going dark, as well as parts of Riverdale and the Beaches. So, in hindsight, I would have put in captions or title cards to put things in context—I didn’t intend the comparison video to present Earth Hour in a negative light (no pun intended).

If I’m still in this apartment a year from now, I’m definitely repeating the experiment and I’ll post all 4 videos for comparison.

To Upgrade or Not to Upgrade—that is the question.

…Whether 'tis nobler to stand pat with what I’ve got….

As next spring’s post on our DVD draws nearer, I’ve been contemplating the post-production aspect of it: do I have the tools to do a really good job by current standards?

I could produce a functioning DVD with basic tools, even freeware apps, but the goal with this project is to produce a demo reel to put into the hands of the mighty. If we sell a few of them, all the better, but I wouldn’t want to sell anyone something that wasn’t the result of Mullet and I playing at the top of our game. Mullet takes the same approach with the comic, as does our artist, Kameron Gates.

At the moment, I have a G5 (single 1.6 GHz processor, the original low-end G5 model) and Final Cut Studio 1 as my software. I have a pair of 250 GB external hard drives for video capture, and I listen to the whole thing via a 10-watt Radio Shack amp and $30 Radio Shack speakers. This is probably as no-budget as you can get! I won’t be replacing the G5, so my focus will be on the software.

I’m running OS X Tiger, and I haven’t decided whether I’ll upgrade to the new Mac OS, Leopard, yet. I usually wait some time before upgrading, but I’m happy with how fast and stable Tiger is—Leopard’s new features haven’t prompted me to run down to Riverdale Mac just yet. I’ll revisit the OS after the DVD’s done, but I don’t anticipate, at this point, upgrading based on some of the negative experiences people have had. If the consensus on the various forums that focus on all things Final Cut and Mac come back with reports of speed increases or can’t-work-without features, I might take the plunge.

I am, however, evaluating 4 options for upgrading my current apps:

• Stand pat with what I’ve got ($0)
• Upgrade to Final Cut Studio 2 ($545 CAD),
• Buy Magic Bullet Suite ($799 USD) or just one of the Magic Bullet apps
• Buy Adobe AfterEffects ($1149 CAD for CS3, $1969 CAD for the Production Premium version, which adds PhotoShop, Illustrator, etc.).
  
  Taking Magic Bullet for a ride is step one in my evaluation. Magic Bullet was created by Stu Maschwitz of The Orphanage, and it’s been a well-known plug-in and stand-alone app for years. Last spring, I bought Stu’s book, The DV Rebel's Guide: An All-Digital Approach to Making Killer Action Movies on the Cheap, which I’d recommend to anyone making no-budget movies (even if you’re not shooting action flicks, there’s plenty of good information there), and found his blog and forum there quite interesting.
  
  Magic Bullet Suite is priced at $799 USD, and you get Magic Bullet Looks (applies preset or user-created “looks” to video), Magic Bullet Frames (converts 60i to 24p, also deinterlaces video), Magic Bullet Colorista (3-way colour correction), and Instant HD (converts SD video to HD video). These programs are either stand-alone or plug-ins for FCP and Motion, but the demos seem to be plug-ins only. I’ve read a few reviews for Colorista, plus various forum comments, and all have been positive. I can’t recall any negative comments, actually. I downloaded the demos for Magic Bullet Looks and Colorista, and in a future post I’ll let you know how they’ve worked out.
  
  Upgrading to Final Cut Studio 2 would give me the latest versions of that bundle: Final Cut Pro 6, DVD Studio Pro 4, Motion 3, Compressor 3, and Soundtrack Pro 2, plus the new app, Color. At the moment, this would be a $545 CAD investment. The learning curve is the lowest here given that I’m familiar with the previous versions of all these apps, with the exception of Color. There are no demos available for FCS 2, so I’ll have to rely upon reviews and the Apple website for evaluation. The reviews of FCS 2 have been positive overall, although some people don’t like Color.
  
  Whether I upgrade or not, I’ll be using FCP, Soundtrack Pro, Compressor, and DVD SP for the DVD. These are good, stable programs that meet most of my needs for no-budget post-production. The only needs I find wanting are in the areas of mastering and onlining.
  
  Stu’s book goes into onlining quite a bit—getting the video from your non-linear editing program to the final version enjoyed by millions. Colour correction and mastering are the two main areas. In the book, Stu has reservations about using FCP for onlining and recommends using AfterEffects since FCP renders at 8-bits and AE can render 8-, 16-, or 24-bits. The higher the bit rate, the better the filters and transitions look. With Stu’s workflow, you don’t do any rendering at all in FCP—you export everything sans transitions and filters, and apply them inside AfterEffects instead.
  
  In FCP 5, you’re limited to 8-bit rendering, but Apple promises that FCP 6 does 16- and 24-bit rendering, as does Color, but I haven’t seen anyone come out with a clear statement on whether it works as well as AE does, even on Stu’s blog and forum.
  
  I’ll download the AfterEffects CS3 demo and try it out once I’ve played with Magic Bullet. I had AfterEffects 3 way back when OS9 ruled the Mac world, so I’m somewhat familiar with the program, but I suspect that CS3 is probably a lot more sophisticated than 3 is!
  
  To evaluate the 2 demos, I’ll take the same sequence from a Final Cut project, export it as a DV QuickTime file, and import it into each program (bearing in mind that the Magic Bullet demo is plug-in only, I’ll presumably be using FCP’s rendering engine when I test Magic Bullet, so I’m testing the interface more than I am the output).
  
  I’ll come up with 3 or 4 different things I want to test, and use Magic Bullet, AfterEffects, and Final Cut Studio 1 to independently come up with 3 different versions. Once I’ve done all 9 or 12 tests, I’ll export them as QuickTime files and bring them into Compressor to convert into H.264 and DVD files. I’ll run the DVD files through DVD Studio Pro to create DVDs to look at on various TVs, and I’ll test the H.264 files on a mix of computers, mostly Windows.
  
  I’ll post results for these evaluations in the coming weeks.