[Charlie Austin]

This is sort of boilerplate advice, but before you reinstall the OS (in theory your projects should be OK as long as you don’t wipe the drive during install) Try looking in the console, it may give you a clue as to what’s happening.

Quit FCP X, then open the console. Start FCP X. When it craps out, note the time. Then, in the console, select “all messages” in the upper left. in the search field (upper right) type “final cut” (no quotes) to filter the list. find the time stamp entry from when FCP X crapped out, or just look at what it’s logging if the beachball is still spinning. What’s it say?

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

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

[Charlie Austin]

Can you tell automator to wait a certain amount of time (longer than any export time you anticipate), before moving the file?

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

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

[Charlie Austin]

[Mark Dobson] “[Charlie Austin] “I think the biggest hurdle to X adoption is really the time needed to gain proficiency in the app. In this deadline driven business it’s a problem. It can pretty much do everything you need and more, but you do need to figure out how to bend it to your will. :-)”

I think that’s right, because it does familiar tasks in a very peculiar manner, it’s quite a deceptive application to get on top of.”

Exactly. And honestly, at least in my personal experience, once you become accustomed to these “peculiar” manners, going back to a “traditional” NLE seems peculiar… and frustrating. I suppose I should have said you need to let the app bend you to it’s will. 😉 X still occasionally makes me want to tear my hair out, but I think that’s true of any NLE to some extent.

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

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

[Charlie Austin]

[Craig Seeman] “It would be interesting to see more narrative stuff. What we’re seeing might be an example of where FCPX is making the most “natural” inroads and which areas there may still be some reluctance, given the current feature set.”

Well, FWIW, I’m cutting Trailers and TV spots in X, which are kind of condensed versions of narrative features. lol

It seems to me that the Event browser organizational abilities are very well suited to features. Although, like all of X, figuring out the most efficient workflow is the key. One giant event? Multiple events organized by scenes? Reels? Shoot days? In my case that’s not an issue since I work from relatively finished features. Even if I end up with 3 or 4 different versions of a feature my events generally haven’t exceeded 500 or so source clips so I can just have one event per job.

Editorially, all I really need are replace at playhead option and beefed up Roles for better visual timeline organization. A sequence with more than about 15 “lanes” (30 stereo channels) of audio and/or multiple layers of video can get a little difficult to keep track of currently. But the more I cut in X, the more I realize that what’s in there now takes care of the majority of things I need. I look forward to more optimization and feature additions/enhancements/polish, but there are no deal killers for me anymore.

The most difficult thing in my world is to try not to do too much crazy stuff that can’t be easily reconstructed by an overworked online editor. (I’m looking at you Slice-X!) 🙂 3rd party tools for sending out elements are great now, though there is always room for improvement and or new players.

I think the biggest hurdle to X adoption is really the time needed to gain proficiency in the app. In this deadline driven business it’s a problem. It can pretty much do everything you need and more, but you do need to figure out how to bend it to your will. 🙂

If you’re coming from FCP 7, It really is “easier” to hop into Pr, and to a lesser extent MC, than to get used to living with X. For me, it’s totally been worth it, though it hasn’t been easy by any means.

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

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

[Charlie Austin]

[Lance Bachelder] “I agree – having video and audio “pre” expanded would be nice and then just collapse as necessary. It’s an extra step I don’t like taking although at least you can expand more than one clip at a time. But maybe this would be too much like every other industry-standard NLE…”

LOL… actually, have you sent feedback about this? A little bird told me that all that stuff goes into a spreadsheet of some sort. and if there are enough requests for a useful feature they’ll move it up on the list. Unless you want tracks. That ship has sailed. 😉

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

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

[Charlie Austin]

[Lance Bachelder] “Sorry I meant “expand” not detach audio. It is a pain to have to do this for every single clip though the magnetic timeline is actually nice on a long form project making it almost impossible to knock things out of sync with picture…”

Gotcha… Sorry for stating the obvious. 🙂

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

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

[Charlie Austin]

[Lance Bachelder] ” realize my current show was not built correctly in X – an Event for every sequence makes it so slow – but there’s no way to media manage the timeline into a new project to speed things up!

I haven’t done this on any large scale, maybe 2 or 3 events into 1, but you can combine (merge) events:

https://www.kenstone.net/fcp_homepage/fcp_x_merge_events_stone.html

[Lance Bachelder] Also, having to break apart video and audio every time I want an overlap is tedious…”

Highlight clip, CNTRL-S. You can overlap all you want without disconnecting audio. Really the only reason to disconnect audio is if you want to cut it up. If you just need to do J or L cuts, just expand the audio. So you get this:

Primary sync audio is still riding with the pix, and cheated/upcut/non sync dia are connected clips.

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

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

[Charlie Austin]

[alban egger] “It is official: every phone can do more than FCP7!”

Multicam for the masses! Clearly Pr and MC are much better choices though… >;-)

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

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

[Charlie Austin]

[Brandon Cordy] “Yes, I think it’s key to make sure everything for one project is one a few Events (less than three, even less than one if it can be swung) and properly logged & tagged via metadata before editing begins.”

True for any NLE… hell it’s true when cutting on film. I’ve been in some cutting rooms that looked like an episode of Hoarders. I’ve seen some FCP 7 projects that looked the same actually. 🙂

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

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

[Charlie Austin]

Or, you could add a video role or subrole, (used-1) or something, highlight them in the index, and grab what you need…

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

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