[Chris Kenny]

[Aindreas Gallagher] “I’ve made my thoughts clear above, my thoughts are my own.”

You’ve said the way FCP X handles gaps interferes with the way you edit, but you haven’t explained how, given that insert/overwrite operations on top of sequence gaps in FCP X work the same way in FCP X as they do in FCP 7.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[David Roth Weiss] “As I’ve already mentioned elsewhere, David Pogue never quotes a single human being, alive or dead, from Apple by name, and there’s been no official documented word yet released from Apple. So, the certainty with which you counter the arguments of others here by quoting what can best be characterized as “hearsay,” is now beginning to have a cumulative effect that is starting to raise my hackles and the needle on my truth meter.”

We have now heard essentially these same things from three different sources: Studio Daily, David Pogue, and Philip Hodgetts. You can choose to believe Apple is lying, or that all three of these sources (who all claim to have had direct independent contact with Apple) are lying about or consistently misinterpreting what Apple said. But these things seem quite unlikely. It is simply not reasonable at this point to continue to believe that Apple has no intent to add these features.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[Aindreas Gallagher] “Oh no – I’m not going down to crazy town with you again Chris – we’re doing enough of that below. I’ve stated my thoughts above, they are my own.”

You claim the new gap behavior makes it harder for you to edit. But as far as I can see, it’s easier to insert gaps, easier to delete them, and easier to change their lengths. And insert/overwrite operations work the same with gaps in FCP X as they did with gaps in FCP 7.

And now you’re not willing to explain what you were talking about.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[Aindreas Gallagher] “moronically, if you move a clip using the position tool, the gap will not be allowed to exist – a slug will appear. That is stupid. if I need to perceive what is going to, or should happen in a space, i cannot simply slide the next three or four clips down the track, leave a breather, and begin to place clips into the black, trying to consider in my mind the number and type of shots I feel should be there.”

How does the slug that appears in a gap prevent you from doing this? IMO this ‘gap slug’ behavior is a very nice feature, because it allows gaps to be treated like normal clips. Want to delete one? You don’t have to just a special ‘close gap’ command; just delete it like any other clip. Want to extend one? You don’t have to switch tools, select every clip that follows it on the timeline, and drag them all further back. Just drag it out to be longer like any other clip, and everything else ripples.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

You’re not even trying to have an actual discussion at this point.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[Aindreas Gallagher] “FCP7 wasn’t a multitrack editor, editing is a multitrack operation”

I disagree with this statement. Editing is the process of arranging a series of shots to tell a story. Sometimes for organizational reasons it’s useful to be able to have two shots that overlap on the timeline (so that, for instance, you can keep cutting away to one of them, with the main shot showing through gaps between the cutaways), and it’s also necessary to be able to layer shots in order to create certain effects.

Tracks are merely one way of doing this. They are, perhaps, the most obvious way, but the most obvious way to do something is frequently not the best way.

[Aindreas Gallagher]
Yeah and you know what, that is all dumb as crazy town dumb. How in the hell am I supposed to work with a single track of video sliding around itself and a secondary track that attaches to the clip below it the minute I lay it down?

This is what I mean when I say you’re not really making an argument here. All you’re doing is asking a question. You think the answer is self-evidently “You can’t be expected to work like that; the FCP team was full of idiots who designed a timeline that’s impossible to edit with”. But this is not actually self-evident.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[Tom Daigon] “There are no facts at this point, there are just words. Facts exist when there is physical evidence available. Its not what is said, it is what is done…”

This entire discussion is about Apple’s intent. Words can convey facts about intent. Do you believe Apple is lying about its intent to add these features?

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[Aindreas Gallagher] “Oh give me a break. Chris, in reference to V1 and V2 I am never Chris, never do you hear me, never going to refer to them as primary and secondary storyline. If I did, I would have to walk up to a mirror and punch myself in the face. What’s V4 anyway? Postscript? What’s A4? Whispers off stage?”

Now you’re simply writing as if “storyline” is the new word Apple is using for “track”, tracks and storylines are equivalent, and I’m giving you a hard time merely just for using the wrong synonym. But this is not true. The area above the primary storyline (what you’re calling V2) is not the secondary storyline; it’s an area for things that are linked to clips on the primary storyline. Those things can be secondary storylines (which are basically nested sequences that can be edited inline), compound clips (nested sequences that aren’t edited inline), normal clips, text generators, etc.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[David Roth Weiss] “Having now read very many of your posts I can’t help but notice that you consistently speak with a POV that implies that your conjecture is “fact.” Do you have an inside track, or is your ability to read minds better than the 50/50 of those Creative Cows whose own theories you consistently correct?

I’m not suggesting you’re right or wrong about the things you postulate, just that the voice you give to your take on the inner workings of the minds at Apple is said with such great certaint”

Honestly, WTF? I am repeating things here that Final Cut Pro product managers have told to (among other people) a New York Times columnist, and people are trying to pretend these things are simply speculation on my part.

Seriously, it’s all right here.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

[Chris Kenny]

[Aindreas Gallagher] “The hubris and pomposity of the “solutions” proposed by Randy in this ludicrous piece of software just about take my breath away.”

You haven’t actually advanced a substantive argument here. All you’ve done is point out that it’s different, and claim that it’s worse without explaining why.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.