Tracks are Indispensable.

[David Mathis]

No tracks in X just gave me an idea for a new signature: Less clicking, more editing, that is the power of X!

[Bill Davis]

But Charlie,

They’re so organized looking, and, like, I know what they all MEAN, and they feel so, well, COMFORTING, and you know, HOW CAN I TELL WHAT THE HELL ANYTHING IS WITHOUT TRACKS! – cuz, you know.

They’re TRACKS.

for gods sake.

How can I get stuff done if you take my TRACKS away? ……….. (i’m scared)

(said way too many people over the past 4 years)

Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

[Steve Connor]

Good grief, how DID we all cope before FCPX came along!

[Charlie Austin]

[Bill Davis] “How can I get stuff done if you take my TRACKS away? ……….. (i’m scared) “

Not sure that helps Bill… And to be fair, there are plenty of workflows where tracks serve a purpose. Mine isn’t one of them.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Chuck Pelini]

This whole track or no track thing reminds me of when non-linear was introduced. Many linear editors didn’t want anything to do with that “editing on a computer stuff.” “It will never replace a room like this…”

[Shane Ross]

[Steve Connor] “Good grief, how DID we all cope before FCPX came along!”

It’s amazing we were able to get anything done…with all those tracks hampering us.

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Bret Williams]

Interesting. They are annoying. But for your process I would’ve thought it pretty much the same. Mark in, mark out, ripple delete. Or in X… Blade all, blade all, delete primary clip.

And at least in 7 you can trim all those 20 layers at once instead of 1 at a time in X. Both apps have the exact same issues with ruining sync when doing ripple deletes or primary trims. Any clip that is connected (or “begins”, in legacy) before the trim point, is knocked out of sync. Usually music or a long bit of VO would fall into this category. I even remember watching the intro of X in 2011 and they trimmed the primary and everything moved down ( 7 works the same way as long as you do a ripple delete and don’t have Any locked tracks) knocking everything out of sync with the music. You could see it happen. And they just touted that everything stayed in sync.

Working in Avid with sync locks all on is the only foolproof stay in sync method I’ve seen. Any of those long overlapping clips simply get split at the ripple point, moving the second portion down with everything else.

[Charlie Austin]

[Bret Williams] “Working in Avid with sync locks all on is the only foolproof stay in sync method I’ve seen.”

It would have been easier to do this in MC than 7. It wasn’t the rippling that was the problem, it that there were many clips that overlapped different sections so there was no way around track tetris. I mean, it was fine, but it woulda been easier in X. That’s all I was trying to say, my intent wasn’t to stir sh*t up. 🙂

edited as I see you weren’t talking about cutting all layers, but trimming…
————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Richard Herd]

[Charlie Austin] “there were many clips that overlapped different sections”

Do you mean audio clips and/or picture in picture and composites?

[Bret Williams]

I’d say it’s nice that you can trim the primary and stuff moves out of the way, but then you usually end up having to trim lots of clips. But true in legacy you get clip collisions. I don’t miss those! But I do miss extending multiple layers with the g tool.