[Charlie Austin]

[Jeremy Garchow] “For posterity:”

Thread killer… 🙂

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

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

[Charlie Austin]

[Jordan Mena] “Has anyone found a good use for this part of FCPX? Does anyone have an idea where Apple will go in future updates for the Project Library?”

Personally I really like the Project Library, I find it much easier to organize the bazillions of versions of all the cuts associated with an event without turning my events into FCP 7-like cluttered nightmares. 🙂

That aside, my guess is that the Event/Project arrangement has something to do with some sort of future shared workflow. A “master” event shared by all with separate projects for each editor. Something like that maybe?

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

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

[Charlie Austin]

[Rafael Amador] “You mean to use the BM Camera clip to show what you can do with FCPX?
As a fast camera demo is OK; as a NLE test is pitiful.”

No, the bit linked in the first post on this thread before it devolved into a camera discussion. Not pitiful at all…

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

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

[Charlie Austin]

[TImothy Auld] “I think Apple PR got that there”

I think you’re correct. 😉

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

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

[Charlie Austin]

[Steve Connor] “Apple PR should grab this one and get it on their website

Steve Connor
“

They’ve been alerted. Though I wouldn’t be surprised if they know about it already… 😉

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

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

[Charlie Austin]

[Chuck Pelini] “I went a little further into one of my timelines and noticed that I had a Custom Title in a problem area. I changed it to a basic title and now I have normal function. Not sure why that would matter.”

Are you running OS X 10.8.3?

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

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

[Charlie Austin]

Perhaps a corrupted clip in the timeline? Or reinstall Compressor?

https://discussions.apple.com/thread/1128297?threadID=1128297&tstart=0

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

Also, Are you running OS X 10.8.3?

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

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

[Charlie Austin]

[Wayne Garton] “Would it be best to crop and transform this camera first, “share” it to a new file and re-import it. (Then do the multicam)

Or is there a better workflow?”

Not a multicam wizard, but I think you can open the multicam clip in the angle editor (right click on it for the menu), apply your transform to the clip, close the angle editor and then just proceed.

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

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

[Charlie Austin]

[Paul Neumann] “I use this all the time mostly for Ultra Key/Scale/CCR scenarios where all the talent was shot on the same set on the same day sorta stuff. Big time saver and helps keep a consistent look. Literally get one shot keyed and corrected then save it off and apply it one time to a group of clips and everything is ready to go.”

FWIW, someone posted about doing this in X on a FB group. Very nice trick:

Here’s another reason I love FCP X. To quickly colour grade interview clips in a 28 minute project, I did a basic grade of the first appearance then selected Command C to copy. In the Timeline Index, I selected all instances of the interview setup (Command click), then hit Shift Command V to paste attributes. The grade is applied to all selected clips. It’s faster than looking for the clips in the timeline. Of course you could do the same for audio sweetening – EQ, compression.

The X TL index is something we don’t talk about much here. I’ve been using it more lately and it’s a real nice implementation.

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

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

[Charlie Austin]

[Marcus Moore] “On the PR side, however, Apple needs to get in the game. First off, these “In Action” stories need to be videos. You’re talking about visual storytelling- tell your story visually. Next- the return of Apple roadshows. After the next major update, Apple should be pounding the pavement touting not only NEW features, but also all the stuff that FCPX has done for some time that no one seems to know about.

As for the public roadmap, there was always going to be an end to this. As long as they were reintegrating Legacy functionality, they weren’t giving anything away by listing that past features were returning. But key features going forward are more likely to be new [or heavily rethought], and so there’s no chance Apple will be announcing them beforehand.”

Absolutely, on both points. I have a feeling that a more focused marketing push will happen. Hopefully sooner than later. I also think that sending feedback to Apple about the marketing of X is just as helpful as bug reports/feature requests. Seriously. And I also hope Apple is reading threads like this.

Hope springs eternal. 😉

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

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