[Charlie Austin]

[Aindreas Gallagher] “but you’re skirting around the fact that there are four guys in total working on advancing and bug fixing core data full stop nevermind the syncing issue. That was one of the specific points the developers made – that they view it as a resource/does apple really care/ issue, given that there are just four guys representing the entire company effort on core data. “

It seems to me, in the context of that statement that those 4 guys referenced anecdotally by an unnamed developer are working on Core Data synching, not Core Data itself. In any case Core Data (not synching) has been around for quite some time and is a solid, well regarded framework. You’re grasping at straws.

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

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

[Charlie Austin]

[Aindreas Gallagher] “hey Charlie – you know what they say – you’re never a troll once you remember to put a smiley face at the end of every sentence. :)”

😀 lol

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

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

[Charlie Austin]

[Chris Harlan] “Yes, they look more alike, but they really function quite differently. For instance, if you spend a lot of time expecting Filler to act like FCP’s black (and, I don’t mean slug), you will go insane.”

I guess that’s what i meant…Pr is the closest to Classic, but it’s not the same. At all really. The timeline behaves in a similar fashion, but, even if you use the FCP KB they put in there, it’s a different beast. As far as MC, i totally agree. It’s a whole other kettle of fish. 😉 I’ve said before that I feel like the X timeline behaves more like MC than Classic, though you can just cut everything into X as connected clips, which I started out doing. But really, that’s kind of like your analogy of trying to use Classic in an Avid like way. You miss out on the best stuff I think. No matter which way you go, it’s a tough road for folks who learned to cut on classic and haven’t really got any other NLE experience. I understand why they’re upset…

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

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

[Charlie Austin]

[Chris Harlan] “LOL. Actually, in both cases it was hyper X enthusiasts who were beating on folks that didn’t quite have the presence of mind to see it Apple’s way.

Funny.. I’m against hyper-anything enthusiasts. 🙂

[Chris Harlan] “Hey, I love Motion! It’d be great if they could ever get it round-tripping again.”

Yeah… i really wish I knew it better, I just bumble around in there. But even just doing that I can do some cool stuff. Practice practice… 🙂

[Chris Harlan] [Charlie Austin] “Either way it’s gonna take some re-learning for half the folks here at work who’ve never cut on anything but FCP Classic. Oh well…”

That’s for sure.”

I think the relearning thing is what frightens people most about X. Yes, there are some post workflow issues that need addressing/improvement and features that need implementation and improvement and/or require workarounds. No question. But the biggie I think is that Classic and MC and Pr etc all kinda work like one another. They look the same: Source-Record-Tracks. They all handle things quite differently, but they work sort of the same. X works like other NLE’s too, but it looks and acts very different. Weird. Scaarryyy… 😉

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

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

[Charlie Austin]

[Chris Harlan] “I don’t know. It always ends up bitting me somehow, so I almost never do it. I was fondly reminiscing the other day about work I did in the middle of the last decade, and I suddenly find myself in water where someone wants to argue about one of my current clients as if they are the evil empire. I don’t post my reel here, either. Tempers can run high, and some line crossing does go on; I’ve seem members of this very forum try to discredit individuals with their employers because of their positions on FCP X. Sad, huh?”

I hear ya. As i said, this stuff is all on the web already, and is well past it’s air date. Nothing amazing or anything, just things cut in X that lots of people have seen. Not like it’s some big secret who the clients are either, we all work for the same people right? 😉 And anyone who wants to discredit me with my employer because of my position on X is too late. They already think I’m crazy. 🙂 Though that’s changing.

Watching their reactions as I make revisions and pop in and out of full screen without stopping playback is priceless. And that’s just basic modern NLE tricks. Now that i’ve gotten more dialed in with X muscle memory and KB shortcuts I hear “wait, what just happened?!, how’d you do that?” regularly. lol Throwing together temp titles and transitions that look as good or better than what we make in AE, making slates and other reusable GFX into generators in Motion, exporting multiple spots with multiple presets while continuing to cut etc., is fun too. As long as I can get stuff out to finish, nobody cares. If multiple people are on the same job I’ll still cut in creaky old Classic for now. Eventually I’ll get the Luddites up to speed.

Or… we’ll switch to Pr or MC and plod along like we have for the last 20 years, and I’ll continue to use X when i can because I like it. I’m feeling that’s less and less likely though, no matter what the trolls believe. Either way it’s gonna take some re-learning for half the folks here at work who’ve never cut on anything but FCP Classic. Oh well…

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

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

[Charlie Austin]

[Chris Harlan] “You are a braver man than I. I would never put my clients up here.
“

Meh… it’s all stuff that’s done and out there, no different than a reel on a website. Not posting anything that isn’t already out in the wild. *That* would be suicidal. 😉

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

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

[Charlie Austin]

[Walter Soyka] “Does any of this mean anything?”

Yes. It means you have way too much spare time. 😉

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

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

[Charlie Austin]

[Mark LeGrand] “Can I now send them a FCP7 XML export and have them opening the project in FCPx using 7toX without resending all the media?”

I am not an expert but… assuming all the media is the same… I can’t see why that wouldn’t work.

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

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

[Charlie Austin]

[Neil Goodman] “…Aindreas isnt completely mad, and while i think its still too early to mke that sort of call, it definitely isnt gaining any traction out here even 2 years later.”

Leaving aside the fact that it’s “different”, which is a big deal in itself for folks who have deadlines – I think X is suffering from the effects of, for lack of a better term, editorial elitism. At least here in LA. When you say “Truth be told there aren’t alot of FCP legacy fans either but everyone was hoping FCP 8 would be the one to get them off of Avid”… that’s what I’m talking about. X is making inroads, but it’s on the edges of the “high end” post world. Davidson is using it quite effectively for his promo biz, but on some level that’s seen as “lesser than” say, theatrical trailers etc.

Really, it wasn’t until the “cold mountain” moment that people in LA took Legacy seriously. This despite the fact that I and others had been finishing theatrical trailers and TV spots with it for at least 2-3 years previous to that.

I think the same thing is playing out with X. It’s complicated by the fact that there is a bit steeper learning curve to X due to the magnetic timeline. And Apple knew that folks in LA and NY wouldn’t adopt it right away. But I’ll tell ya, once you get dialed in to X, it is really a pleasure to work with. Yeah, yeah, it needs work in many ways, but I’ve gone from trying make it work like the timelines I’m “used to”, to using the primary, audio components, and all the other new features available. It’s fun, that sounds ridiculous, but it is. I still cut at work in 7 as well, and have been polishing my rusty MC and new Pr chops on my own time, but X is what I prefer.

I’m gonna start posting things here in my Cow profile that I’ve cut in X and finished. Just for laughs. Mostly just TV spots for now… sadly the Elysium trailer we just did came out of an FCP 7 suite, but eventually I’ll finish something that will appeal to the LA elite. (which I suppose I’m a part of, but F all that…) 😉

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

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

[Charlie Austin]

[Chris Harlan] “And, FYI, I have no idea whether it is at all normal for Seattle’s Fremont Troll to use FCP 7 or not.”

I heard he switched to CS6.

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

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