At which point it would top out at about seven miles an hour, since a Tesla weighs just slightly less than a black hole of the same size.

And it's made of wood!

I will concede the point, though, that a Veyron is not the sort of car one really wants to see from the outside. In my defense, you can't see the outside if you're driving it.

Therefore I present to you the 1961 E-type Jaguar roadster. Look on it, ye mighty, and despair.

Free no-cost-to-you bonus? It is literally impossible to say the name of that car aloud without pronouncing it "Jegg-you-uh."

Can we say the whole Star Wars prequel trilogy? Is that allowed?

Agreed. I find myself wishing Twitter had some kind of visible reminder that the person you're looking at is set to private.

Damn, I'm sorry. I forgot his twits are private. My bad.

Here's the link, Eddie: https://twitter.com/markraudonis/status … 4821435392 I see now that I look at it that I paraphrased pretty … um … aggressively.

The fact that you got to work under him knocks me out, man. I got a really, really nice email from him last week about something I'd made, and I nearbouts peed myself in excitement.

Okay, I did pee myself. But only a little bit. I covered it up my dumping my nalgene in my lap … which in retrospect was kind of a bad move.

I think Paulou's absolutely right. It's too easy to become complacent. We all know the vendors will fuck you, but in the past it's been like not returning your emergency call at nine o'clock on Christmas Eve, or charging you ten grand a year for support. Taking a successful, widely used product and just dropping it is something I haven't had to experience before. It's a bit of a shock.

Can I be Tank this time? I'm sick of always getting killed before the end of the second act.

Actually no, since you mention it. Let's go through it point by point.

The "trackless timeline" excuse is weak sauce. Setting aside whether FCP X should ever have had a trackless timeline in the first place — it shouldn't — the program still needed a way to import FCP 7 timelines on day one. It doesn't matter if it's imperfect; imperfect we can live with happily. The fact that there isn't even a fifty-percent solution is just insulting. It says Apple doesn't think old project files are important, which says they don't get commercial post.

The "you can import video directly just like before" thing is downright misleading. You can't, because there's no SDI input. You can import some things in a similar way to what you did in FCP 7, but not all, and not just-like-before.

"Final Cut Pro X does support FireWire import for DV, DVCPRO, DVCPRO 50, DVCPRO HD, and HDV." No, it doesn't, unless you mean crash-recording. There's no way to batch input. Which drops their "Yes, we do tape workflows in a limited way" thing down to "No, we really don't do tape workflows at all, lol."

"Does Final Cut Pro X support multicam editing?" No. It doesn't. "But it will," they say. Don't care. If it doesn't, it doesn't, which means you need a tool that does.

"Does Final Cut Pro X support external monitors?" Apple says yes, but that's a flat-out lie, frankly. It doesn't. Yes, Apple interpreted the question as, "Can you have multiple computer monitors hooked up?" and "Can you show an 8-bit RGB preview on a $20,000 10-bit NTSC broadcast monitor?" and said yes to both, but that's not what the question means. It means can you pipe real-time full-resolution full-depth full-quality program feed out an SDI spigot, and the answer to that is a shameless "no."

"Final Cut Pro X automatically saves your project during the editing process, so you never lose your work." Except when it doesn't, and you do, as a great many people trying out the software have discovered. Lol jk.

"Are keyboard shortcuts in Final Cut Pro X different from those in Final Cut Pro 7?" I don't even know why that's a FAQ. Nobody cares.

"You’ll be able to use [third-party plugins] as soon as they are updated." And they'll be updated as soon as Apple ships an SDK, which they didn't do before the software was released and still haven't done now. Stu Maschwitz said it best: "None of our new stuff works with FCP X … because after all, neither do you."

"Can I specify a scratch disk location?" Admittedly, a lot of early testers got this wrong. In their defense, Apple has gone out of their way to obscure how media and cached renders are stored on disk.

"Can I share projects with other editors?" Apple says yes, but the answer is really no … unless they happen to be using FCP X. There's absolutely no way to collaborate with other NLEs or finishing systems.

"Can I store media in locations other than my system drive?" Same as above: A lot of people got this wrong because the software seems deliberately designed to make it unclear.

"Can I hide Events that I am not working on?" Now this one just pisses me the fuck off. Apple says, "You can hide Events in Final Cut Pro X by moving them out of the Final Cut Events folder." Well whoopty shit. Here's this awesome media management infrastructure we've been working on for two years! All you need to do to take advantage of it is drop into the Finder and move shit around every hour or two, which means extra work for you and an increased chance of screwing something up! Yay!

"We will release a set of APIs in the next few weeks so that third-party developers can access the next-generation XML in Final Cut Pro X." No excuse — no excuse — for not shipping that months before FCP X was released to the public.

"Does Final Cut Pro X support OMF, AAF, and EDLs?" Yes, but it'll cost you nearly twice as much as your NLE did, because we just don't give a shit.

"Can I send my project to a sound editing application such as Pro Tools?" Yes. Except really no, because we just don't give a shit. See above.

"An update this summer will allow you to use metadata tags to categorize your audio clips by type and export them directly from Final Cut Pro X." Great! That's completely unrelated to what people actually need to be able to do! Metadata is an unacceptable solution, Apple, when the same bit of audio can show up on the dialogue track here, and later on the ambience track.

"Can I customize my export settings?" Nobody. Gives. A shit. The only thing anybody ever "exports" from FCP is a timeline-format master Quicktime that goes somewhere else for encoding. Every second you spent on this shit, Apple, is a second you didn't spend making the program useful for commercial post.

And finally: "Can I purchase a volume license?" Yes, if you are a crazy person. Or you can just install that copy of Adobe Premiere you already got when you bought the bundle because it was cheaper than buying After Effects and Photoshop separately.

This FAQ is nothing short of insulting. It's just a giant fuck-you to the post industry, brushing off legitimate and catastrophic design flaws in the app with PR-speak spin-language.

Pissed me off, is what it did.

Dude. You think your day was weird? I woke up yesterday to find a hundred unread emails and ten new ones a minute, and before the day was over I had a conference call scheduled with Adobe's project managers to talk about why Premiere annoyed me.

Yesterday was just fucking bizarre on every level.

I was talking to my best friend last night. He runs a medium-sized boutique post house that does mostly TVCs. His Avids, and he's got seven of them, are all four years old, four Mojos, an Adrenaline and two softs. FCP was never an option for him, because his editors are Avid guys and that's just fine for everybody. But right now he's faced with the prospect of having to upgrade those machines soon. Clients are making noise like they want to see HD in their offline sessions, the machines are underpowered, it's just time for something new.

Trouble is, now feels like — I said "feels like," I'm just speculating here — a rotten time to invest in Avid hardware. The software no; Media Composer's great and getting steadily better. But the hardware options still suck. If you don't want Nitris, your choices are either Mojo DX or the Matrox box, and both of those are these shitty little non-rack-mountable things with flimsy connectors on them.

If Media Composer were compatible with the Kona board, my friend said he'd upgrade today. Immediately. No hesitation.

Meanwhile, I'm about ready to download the MC demo for my Macbook Pro. I managed to completely skip my Avid education over the years, and it's high time I fixed that.