[Charlie Austin]

[David Lawrence] “I’d add one more – “Pin to timeline”.”

I know we’ve had a back and forth on this but, yeah, you should be able to do that without a workaround. Maybe an unassigned (I could see this screwing people up if done by mistake) KB command to “float” a clip (i.e pin to project time wherever you put it). 🙂 I’ll add it to my prayers.

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

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

[Charlie Austin]

[Bret Williams] “I registered finalcutproclassic.com when X came out, but damned if everyone didn’t call it legacy in the end.”

heh… yeah, I still have macmates.com. I was convince the MacMate was gonna be a big hit! Oh well, maybe I can start an online dating service for Mac users? lol

EDIT… autocorrect changed macmates to machetes in the original reply. I don’t own that. lol
————————————————————-

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

[Charlie Austin]

[David Cherniack] “From the Premiere sidelines, Go X and Halelujah. Really. The better X becomes the better other NLEs will become.”

And vice-versa. Strong competition is good no matter what tool you wield. If R12 is any good it’s gonna light some fires under everyone. 🙂

[David Cherniack] “BTW I trademarked “Church of X” and now you’ll have to pay. Big time. heh heh.”

lol… I was gonna run off and register the churchofx.com domain, but I have too many already from knee-jerk reactions like that, so it’s all yours. 🙂 Some are kind of cool. Others, not so much. For instance, I have no idea what I’ll do with wombsforrent.com. lol

EDIT: Bummer, someone’s already squatting on the churchofx domain… Sue them! 😉

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

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

[Charlie Austin]

[Steve Connor] “You covered all mine quite nicely there Charlie”

Maybe the Creator, being everywhere and all-knowing, will read this post and our prayers will be answered. Hallelujah!

lol

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

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

[Charlie Austin]

[David Lawrence] “Um guys, I thought this was going to be a thread about history? We could be discussing much more interesting stuff if you want. Just sayin’ ;)”

History?!? I remember scraping fades on mag tracks with a razor blade! And manually punching in video edits on tape! It worked fine! You kids inventing your newfangled computer thingies just piss me off!

Sorry. 🙂 I really did punch video and scrape fades on occasion, though we did have a DAW available… I wish I could remember the name.. before ProTools, it chased TC… very fancy…

EDIT: Otari Prodisc. ProTools had been out for a year, but didn’t chase TC reliably, This baby was geared for broadcast rathe than music…
————————————————————-

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

[Charlie Austin]

[Bill Davis] “I’m just a bit tired of those who seem to argue that everything necessary or useful about audio in an NLE was TOTALLY covered by track based systems, and that because X is trackless somehow that means it’s also hobbled. “

Totally agree. I think there’s also a perception that how X handles audio now is how it will always handle audio. I don’t think that’s correct, and i think the way Roles work, and how X in general works, offers some very interesting possibilities relative to track based audio handling.

[Bill Davis] “But to listen to some who have virtually no experience in trackless X style editing- argue that it’s somehow deficient? – nope. Not buying it. That’s misinformation that requires addressing. “

Also agree. There’s also a tendency, as has been pointed out a zillion times, for people to extrapolate their own workflow and preferences (with X, Or tracks, or whatever) onto “everyone”. When that happens, nice threads like this one umm… devolve… 😉

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

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

[Charlie Austin]

[Bill Davis] “And smart guys in HUGE shops are reporting huge productivity gains via roles export over manual stem creation. That’s a fact. Since Apple didn’t decide that all audio MUST remain stuck in the paradigm of 1971 – we have some nice alternatives now. “

Bill, your music video timeline illustrates your point, but that type of cut isn’t the only thing people are doing in X. As you know, I’m a strong proponent of X, I think it kicks ass. But there are absolutely some things it could do better. (New thread coming up on that!) I’ll keep it short as the “debate” has once again hijacked a great thread that has nothing to do with it but… When you’ve got a project like the one below, there are absolutely some “track-like” functions that would be very useful to have in FCP X. Not tracks, but vertical position settings (Z-order?), Roles as groups that can be effected without comping, things of that nature. I could have cut this in a tracked NLE, but to me the benefits of X outweigh the drawbacks by a long shot

FCP X is “not” the same as other NLE’s in many ways, and like you, I think that’s a good thing. It’s also not perfect, and there are valid reasons not to use it in some workflows. Personally I think those shortcomings will be addressed going forward, and there will be less of them, but for now, it’s true. (it’s true of *every* NLE as well) There are also a lot of stupid, invalid reasons for not using X, and I’m not above the occasional, veiled, “luddite!” jabs when I hear them. 😉 I want X to keep improving, to get to the point where any “X can’t do that” comment can be countered with “yeah it does” without offering a workaround. Adding effects to an entire Role, or an entire mix is one example. Yes, you can do it, but not without comps within comps etc. Everyone who uses X, including you, should want Apple to “fix” things like this. And in a way that blows the existing methods away. 😉

That whole “keep it short” thing didn’t work out huh? lol

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

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

[Charlie Austin]

[Glenn Payne] “Hmm. I’ll give that a try if i end up getting the new Mac. I guess I’d just link them via a FireWire cable/usb or would I copy files somehow on a jump drive/disc? Sorry, I’m inexperienced in transferring programs from one machine to another.”

When you get a new Mac, there’s a Migration assistant to transfer settings etc from your previous Mac.

https://support.apple.com/en-us/HT204350

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

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

[Charlie Austin]

[Glenn Payne] “Good deal! I believe the version I bought was studio 2.”

I don’t think that’ll work unfortunately. IF you can transfer it from another machine I’d do that. or, the internet can help you locate installers for discontinued software such as FCS 3…

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

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

[Charlie Austin]

[Glenn Payne] “Thanks Charlie!
Thanks for the thought on referbs. For some reason that hadn’t even crossed my mind. So it sounds like maxing out the graphics card is the way to go. “

Yep, GPU is the most important, at least for FCP X, though 7 likes more GPU as well. Also, can’t vouch for refurbs from anyone but Apple. I’ve had no problems with the ones I’ve gotten from them.

[Glenn Payne] “Have you personally ever used final cut 7 on a newer machine running Yosemite? I was a bit worried about the older program running on it.”

Yep, quite often (sadly… lol) It works fine. you need to install from a FCS 3 disc set though, as earlier versions have PPC code in the installer and it won’t run. If you restore the new machine from a system that has it installed it’ll work too, but I’d do a fresh install if possible…

One caveat… Older versions of Compressor and Motion will not work, so your “send to” stuff will be broken except for STP which still runs…
————————————————————-

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