[Charlie Austin]

[Chris Harlan] ” I know you are trying to be nice, but it gets really insulting every time you pull out that “old school dudes just want to be old school” meme to explain why everyone does not embrace X to the degree you do.”

I’m with you. Just like there were/are things that MC does that FCP “classic” couldn’t, there are things that X can’t do that other NLE’s can. And visa versa of course. The “just don’t want to learn new things” refrain is a little tiresome, and in many cases, incorrect.

Bill, when you say: “It’s a philosophy that rewards anyone who gets excited to learn new things. And kinda penalizes anyone who is honestly just trying to leverage everything they already know about how NLEs already work and preserve that knowledge while operating a new one.”

it comes across as kind of condescending. Also, it’s sort of wrong. X isn’t reinventing the wheel here, it’s just maybe uh, like when bias ply tires were replaced by radials? lol I dunno.

Anyway, as someone said the other day, the war is pretty much over and people are adopting X, now that it actually works. 🙂 I’m getting quite a few inquiries about my workflow from people in my niche. People who, a year ago, thought X was a toy. There’s still resistance, but less than in the past.

I dig X, and am using it more and more on things I would have been nervous to use it on 6 months ago. Anyone who still says it’s not a “pro” app is demonstrably wrong. But there are some things, as Chris points out, it can’t really do yet. If you need those things, (and I’m not talking about tracks here, that ship has sailed, thank god), then you use the app that does ’em. If X doesn’t do something that an editor needs, it doesn’t mean they are luddites stuck in some sort of time warp. (cue rocky horror soundtrack) 🙂

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

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

[Charlie Austin]

[Gabriel Spaulding] “What trim tools does Premiere Pro CS6 have that Final Cut Pro X does not?”

He’s talking about JKL live trimming, which MC has had for some time, and Pr just got. Having used it in both those apps, I don’t miss it at all in X, but that’s just me of course… 🙂

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

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

[Charlie Austin]

[Richard Herd] “You are unable to open the compound clip and peer inside, and because their is no physical media as far as FCPX is concerned, you cannot relink it to an event that DOES have all the media.””

And this is why I won’t use CC’s for versioning either. There’s a bunch of people who, in trying to make X more like 7, are shouting far and wide to cut everything in CC’s. In this way they can mimic other NLE’s where sequences live in your “project” with all your media. I like having a separate Project Library, and this is another reason to use X like X. 🙂

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

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

[Charlie Austin]

[adam chesbrough] “Are there editing systems out there that allow for sub 1 frame cuts”

Nope, at least not for video. For audio, yes. In fact, X is way more flexible than 7 and other NLE’s when cutting audio only. Video, on the other hand, must be cut on a frame boundary. X will allow you to put an audio marker at a subframe location, FCP 7 will not. That’s probably what you’re noticing…

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

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

[Charlie Austin]

[Marcus Hardy] “2013-05-20 10:53:55.591 PM Final Cut Pro[8230]: CoreData: error: (1) I/O error for database at /Volumes/RAID/Final Cut Events/Cold Lights/CurrentVersion.fcpevent. SQLite error code:1, ‘too many SQL variables’

Now I have no idea how to read this, but my guess is that my project has too many compound clips for FCPX to measure and as a result it freaks out and doesn’t load.

Any ideas on what I can do?”

No idea, but I’d paste that info into the FCP X feedback form right away, and leave contact info. Also, I believe digital rebellion makes an app that will attempt to repair an FCP X database (which is what an event or project is). However, I wouldn’t mess with the original at all. Try the feedback form, and tell ’em your situation, they do read that stuff. 🙂

Here’s an old discussion at apple about the same issue…

https://discussions.apple.com/thread/4034983?start=0&tstart=0

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

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

[Charlie Austin]

[Neil Goodman] “between magnetic timelines and creative cloud activation nightmares”

Those 2 things are not the same. One you just don’t like, the other prevents you from opening your project. 🙂

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

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

[Charlie Austin]

[Marcus Hardy] “its literally this singular event that causes the problem.”

FWIW, Quit FCP… wait a minute or so, note the time, and then try and open your problem event. After it hangs/crashes/whatever, open the Console app, select “all messages” in the upper left, and type Final Cut Pro into the search field. what is it saying has occurred at the time it just blew up?

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

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

[Charlie Austin]

[Ricardo Marty] ” I need at leat 3 displays. (it wont have thunderbolt)”

Well, as long as you have enough display card/GPU monitor outs, it should work. Anyone with a hackintosh want to chime in?

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

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

[Charlie Austin]

[Ricardo Marty] “Can i have 3 monitors with fcpx. 2 for extended display (monitir 1 for timeline nd program monitor 2 for bin ) monitor 3 for a program window only.”

Yes, with caveat. What Mac are you coming out of? Normal or thunderbolt displays? I’m doing this with a new iMac, second monitor (non t-bolt) and a blackmagic ultra studio mini monitor box feeding a HDTV. Works fine. With t-bolt monitors you could probably have a 3 monitor extended desktop, though there’s some voodoo involved in telling X (or any other apps for that matter) which display is which.

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

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

[Charlie Austin]

[Chris Harlan] “I edited on a Montage3 for years, as well as a D/Vision, which later became Edit. I think I got my first demo of Lightworks back in ’93 or ’94. The first “broadcast” cards were Perception’s PVR and then the Media 100 Vincent card, so Avid was actually kind of late to the table on that, too.”

Yeah, I guess you’re right. I suppose that “the only game in town” was my impression when I started editing picture in ’98 or so. Previous to that I was in the audio world. Actually, I think the reason I was able to pick up MC relatively quickly is that I had been cutting sound on an AudioVision system for a couple years before that. I liked that program. Then they had to go and buy Digidesign and kill it off. Evil Corporations! Killing off perfectly good apps! 😉

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

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