Archive for the ‘Avid Wish List & Bugs’ category

Stop Competing with Yourself

October 2, 2007

To restate the obvious: editing is being democratized. The market is getting shorter and wider — less money per sale, more sales, more and more power in the box, less need for specialized hardware.

Avid has to lead in this world, not the old world of big hardware and fewer, higher-priced sales. The question is not whether they have the expertise to aggressively innovate — they do. The question is whether they can pry themselves loose from their old business model to do it.

In some ways, they don’t have to invent anything. They could make a very good start by rolling together all the goodness that now resides in the diverse and still separate applications they’ve bought over the years.

Wouldn’t you like to have some of these capabilities?

  • Background saves (never again be interrupted by a save).
  • Background rendering.
  • 5.1 mixing in the main application.
  • The ability to generate a DVD directly out of the timeline.
  • Compatibility with AJA hardware.

Where do you get all that? Not from Final Cut — from Liquid, which is now an Avid product.

Or this:

  • DPX file editing and conforming, all the way up to 4K.
  • Sample-based editing.
  • Nested sequences.

You get all that, plus all kinds of terrific effects capabilities, in DS.

And aren’t you eager to benefit from some of the sound editing and mixing capabilities that reside in Pro Tools? (Details in this post.)

Bottom line — Avid has to show it can lead in the way it empowers creative people. It once did that in spades — and it beat every competitor. It can do it again. But it has to take off the gloves and change the way it does business. Anything less than that is a formula for slow death.

Technorati Tags: , , , ,

How a Little Bug Gets Created and Killed

September 28, 2007

It used to be that if you imported a sound file into Media Composer via drag and drop from the desktop, you got a clip with the same name as the file — but the name was truncated to 27 characters. Most of the time that didn’t matter. But with sound effects it could cause problems because sound effects libraries often have long, descriptive filenames.

Unlike a filename, there isn’t any intrinsic reason for a clipname to be shortened, so the MC was recently changed to take those filenames and turn them into clipnames intact.

And therein lies a tale.

Early last Friday I imported such a clip, and then blithely worked all day in the same bin without problems.

Monday morning I booted up to discover that the bin wouldn’t open. The error message included this text:

Exception: DOMAIN_COPYOUT_FAILED
Exception: STRM_BUF_SMALL, buflen: 256

The attic only took me backwards a few hours — none of those bins would open either. I had a backup from Thursday which worked — but that meant losing a whole day’s work. Unacceptable.

Some internet research and a few frantic calls to friends turned up the idea that the bin might open in a PC system — and, indeed, our rental house was able to open it in a Nitris. We then began the laborious process of trying to figure out which sequence within the bin was the problem. Many hours of trial and error, passing bins back and forth over the net, produced an unambiguous result — it was that sound effects clip.

Avid tech support thought the problem might be with the clipname and suggested that I keep all clipnames to 27 characters. I was skeptical since I’ve had dozens and dozens of clips with names longer than that on every show I’ve ever done. Nevertheless, I did another hour or so of experimentation and learned the following:

Now that the MC doesn’t truncate your clipnames on import, you can indeed screw yourself up pretty badly using names the MC doesn’t like. There are three conditions:

  1. Files that won’t import. In this case the MC produces a generic error message telling you that the file couldn’t be imported. Just renaming the file that you’re trying to import, using a short name with pure alphanumeric characters (no punctuation), will cure this one, but you have to know the secret.
  2. Files that cause the MC to hang on import. These have clipnames with characters that don’t produce an error message — they just hang the machine.
  3. Files with clipnames that are too long. Here’s the gotcha that we faced this week. If your source file’s name is longer than 216 characters then the MC will import it just fine. And you will be able to use it without problems. But once you close any bin that contains that file, you won’t be able to open it again — on a Mac.

The good news is that I’ve reported all this to Tewksbury and a fix is in the works. The bad news is that it represents the kind of problem Avid faces when improving the MC. The system has grown so complex that even a simple change like this can produce unexpected side effects — and in this case, pretty disastrous ones.

Meanwhile, if you import files via drag and drop, double check the filenames before you bring them in. No punctuation except a single period between the name and file type, and make sure the filename is less than 216 characters long.

Technorati Tags: , , ,

DNXHD-36 Without Adrenaline

July 26, 2007

I got a demo yesterday of a software-only Media Composer playing DNXHD-36 media. We hooked up an 8-core Mac Pro to a big Pioneer plasma TV that served as our second monitor. In a word, it was fantastic. Seeing material with that kind of clarity at that size in an offline editing room, and being able to play it and work with it quickly, jogging back and forth and dragging through a clip, was downright breathtaking. And it was not just an aesthetic experience, although it was that, for sure. You’re getting more information — for example, you can clearly see facial expressions in wide shots.

Major caveat — all I did was look at a couple of clips a few minutes long. I didn’t try to play huge complex sequences, I didn’t run a big project, I didn’t even have much audio. All I did was use JKL to move around in the video, made a few cuts, tried making a Quicktime and a cut list. In that limited environment, the system was quite responsive.

Special thanks go to Jeremy Dela Rosa at Global Entertainment Partners (GEP) for putting the demo together for me.

The big revelation was that we could do this with a software-only Avid. You don’t need Adrenaline to do HD, and you don’t need huge amounts of storage. DNX-36 uses about 16 GB per hour at 24 fps — just a bit more than DV, and about triple what you’d need for good ol’ 14:1.

So can you really use a software-only system instead of Adrenaline? That depends on what you are trying to do. The first problem is monitoring. We ran the system with two monitors, one of which was the HD TV (the TV has to have a DVI input). That might be a viable way to work — if you had a 30″ monitor for cutting, you could put everything there, bins, composer and timeline. But if you want three monitors, you’re moving to the bleeding edge. You’d install a second graphics card in your Mac, and run your bin monitor from that. We didn’t have that second card, so we weren’t able to try it. Avid doesn’t officially sanction it, but it ought to work.

The second problem is input and output. The software system has only one way of doing this — Firewire. And that severely limits your choices: DV or DVCPRO HD. If you’re working at DNX36 that doesn’t help much.

So a realistic environment for a small show might mean an Adrenaline-based system for the assistant and a software-only system for the editor.

We tried a few other things:

Making an SD Quicktime — something you might have to do for turnover to sound. On the 8-core Mac, creating a 640×480 QT at Motion JPEG-A was very quick — a bit faster than real time.

Playing SD material in the HD project. The only way to do this is to create a separate SD project, load your video there and then drag the bin into the HD project. In the time we had, all we could do was create some color bars at DV resolution. I was not only able to play that in the HD project, I could intercut it with HD. Unfortunately, the MC insisted on treating the SD clip as though it were 16×9, so it looked anamorphically stretched. But adding a reformat effect solved that problem, and the effect played without rendering.

I also tried making a cut list. And, not surprisingly, I ran into some new bugs. FilmScribe is not nearly as stable as it used to be. Lists out of MC used to handily beat those from FCP. I don’t know if that’s true anymore.

I heard about some other problems, too:

In Adrenaline you can output to SD with a pillar-box in real time. But you can’t do it with deck control. In other words, you can’t use digital cut, you can only crash record. That makes creating an SD tape pretty dicey and not particularly useful.

Worse, I was told about a bug in Adrenaline, that puts a delay into video on the client monitor. The result is that you can be in sync on the client, or on the record monitor, but not on both. The delay is four to six frames — not trivial. I didn’t see this myself, but I sure hope Avid engineering is doing whatever they can to fix it — pronto. The good news from my demo is that the problem only occurs with Adrenaline. Software only was in perfect sync.

All in all, an eye-opening couple of hours, and a lot of food for thought.

Technorati Tags: , , ,

More Laptop Issues

June 29, 2007

Numeric Trim Displays

More and more, I see myself working from various locations on a show — anchored in an editing room, of course, but bringing stuff home or to the set to work on or to show people.

Avid could do some useful work in this area, making it easier for us to edit on the go. I mentioned some of these things yesterday. Here are a couple of additional things I’d like to see:

1. “Pack and Go” — I’d like to be able to select a bin or bins and tell the system to copy all relevant media, and the bins themselves, to another drive or to a laptop. Media should be put in the right place, bins go into the project folder on the laptop. One-click simplicity.

2. The Media Composer expects you to have a dedicated numeric keypad. But laptops don’t have them, and that creates some problems. You can change a dissolve length in the timeline using the regular number keys (at the top of the keyboard). But if you want to trim numerically — or even just move around in the timeline numerically — you’ve got to hit the number lock key, use the embedded keypad (and go blind finding the keys) and then finally turn number lock off, because it locks out all the other keys. Final Cut does not have this problem. You can trim and move around with the normal number keys. And Final Cut adds another bit of finesse — when you customize your keyboard, the template is smart enough to show you the keyboard you’re really using.

Technorati Tags: , , ,

Heads Up Displays

June 28, 2007

Heads Up Displays in iPhotoMany of the new Apple applications employ what the company calls “heads up displays.” These are control panels that are translucent and appear over the image you’re working on, fading in and out as needed. You can see them in iPhoto, Aperture, Motion and Quicktime. They look cool, but more important, they’re functional, because they let you do useful work on a full-sized image. They’re particularly helpful for small (ie. laptop) displays, where screen real estate is at a premium.

As I use my laptop more and more for cutting, I’m starting to see how valuable such displays could be in a mobile editing environment.

Because, in the laptop environment, the Media Composer definitely has some rough edges. When I’m working with the laptop itself, I want one window layout. But when I plug in to a bigger monitor and use the laptop screen as a bin monitor, I want another. The MC can handle this, but it takes a lot of fiddling around. And even when you have your workspaces all set up the way you want them, the system often does the wrong thing.

In general, the MC needs some tweaking around the issue of window activation. For example, when I double-click on a sequence I want the Composer window and the Timeline to activate and move forward. But now, only the Composer window does so. I also want the ability to quickly tab from bin to bin.

And that leads me back to the subject of heads up displays. How about this? Wouldn’t it be nice to work in full screen mode (video playing full screen) — but with a translucent timeline supered over it? The timeline (and maybe the editing controls from the bottom of the composer window — what Avid calls the ‘mini–composer’) would appear when you move the mouse, and they’d disappear when video plays for a moment. That sure would make for a slick, small-screen editing environment.

Heads up displays would also be great in a redesigned full screen title tool, much as they now allow for full screen editing in iPhoto.

What else could you do with this kind of interface?

Technorati Tags: , , ,

More on the Title Tool

June 26, 2007

Grant has posted some great suggestions for a new title tool on his blog “Avid Tips.” He’s hoping you all will weigh in with your ideas, either here or on his site, and then he hopes to collect all the material from both blogs (see my previous post) and present it to his friends at Avid. I think that’s a great idea, so I hope you will add your comments here or on Avid Tips and let us know what you’d like to see.

Meanwhile, I’ll add a few additional suggestions. Though I think the title tool needs to be scraped and replaced, there are some things that Avid could do short-term that would help, too.

For example:

  1. Improve the way a title’s bounding box resizes. No matter what you do, the size of the box that contains a title adjusts every time you change the font or font size — but, like an old Detroit seatbelt, the box can get tighter, but it can never get loser. When you switch to a font with narrower letters, the box gets smaller. If you then switch back to the original font, it doesn’t get bigger again, the line breaks change. Even undo doesn’t get around this bug.
  2. Put render files for changed titles where I want them. Every time I change a title, a new master clip is created — and it automatically goes into the same bin as the sequence that contained the original title. That’s not where I want them. Please let me specify a bin for these things.
  3. Work on the typography. I have a lot of fonts installed. They look fine in every application — except in the MC, where kerning is so uneven that it’s almost comical. No matter what font I pick I can’t make a good-looking title.

And finally, make it easier to create a series of similar titles. Let’s say I’ve made a title card I like. I now want to make 10 or 12 more with the same font, size, drop shadow, alignment, length and fade length. The easiest way to do that is to copy the title, put it into the source monitor, cut it in again, and modify the text. Sounds easy, right? Well, here are the steps:

  • Mark in and out on the existing title. Select the appropriate track. Hit command-option-c (copy to source monitor).
  • Mark in on the record monitor and edit the old title to a new position.
  • Park over the title, go into effects mode, then select the little “modify” button on the effects palette.
  • The title tool opens, change your text, resize the bounding box, as needed (#1, above).
  • Close the title tool. The precompute is saved (in the wrong place — #2, above).
  • So much for the first title of 10.
  • Now make another. Woops — the title I carefully placed in the source monitor is now gone, replaced by the full master clip of the modified title. So — start over at the top of the list.

All this to copy one title and change its text.

Technorati Tags: , , ,