FYI, the blog FCPX on-air posts will be posted in the FCPX Techniques forum

[Michael Gissing]

Thanks John for putting the series up. As someone who doesn’t use FCPX but wants to know how it can be used in a collaborative workflow I really appreciated the trouble you have gone to explain setups and workflows.

[Jeremy Garchow]

[John Godwin] “I do think “jumped the snark” is pretty funny, otherwise, though.”

Thanks, John.

I certainly don’t mind snark. In fact, I enjoy humor and I enjoy snarky humor, sometimes to a fault.

I was just hoping that I am not seen as someone on a clandestine mission to convert the nonbelievers.

I enjoy accuracy, yet I understand that I might indulge in the occasional platitude, or dream, or stretch of the imagination, or down right fantasy.

The responses here aren’t trying to persuade one to convert to FCPX, rather, some of us are here to hold up the end of the conversation that FCPX is not all that bad, and some things, are actually pretty good.

Certainly, it seems it’s not for everyone.

It does become a tit-for-tat when we get in to capabilities. My clients get in to tit-for-tats in edits. It is part of the production process in that there are significant amounts of details to account for, which is why many are here arguing these subtleties. It is sometimes hard to not get mired in the details.

[John Godwin]

With maybe one or two exceptions I don’t think anyone here has a mission to convert people to FCPX. The people who like it, generally, are of the “Hey, it’s great (or good) for me but I know it may not be the best for you” variety. Which I think is a perfectly reasonable approach.

Here, in the circles I travel, there seem to be a lot of one person shops that really love FCPX and appreciate it’s value. The larger operations I’m familiar with (not by any means all or even most) with much more hardware infrastructure seem to prefer more traditional systems. Which, again, makes sense. There’s a lot more riding on system changes.

I personally expect FCPX to grow and add capabilities and that eventually all those objections will go away. If you simply look at v1 FCPX to the current v7 the changes are pretty impressive and substantual. If that rate of improvement continues …

Best,
John

[Charlie Austin]

[John Davidson] “I should probably do a tutorial on the tutorial where I can show how much we used the magnetic to great effect on the tutorial itself

First off, nice series, thanks!. Just wanted to pipe in on the primary… As you may or may not know, i cut promos/trailers, have been using X a lot, and avoided the primary as well, for the same reasons you mention. Last couple projects though, I “forced” myself to start using it and I must say, I’m kind of digging it. 🙂 I’ll rough out bits as connected clips, then dump em in the primary and move on. I still detach the sync audio… until the expanded clips get fade handles etc it’s still easier to work with it separately. The snorkels do a good job of keeping everything in sync, ands it’s a hell of a lot easier to move chunks around. I guess chopping up gap in primary gets you the same functionality… but the primary kinda rocks once the old muscle memory (KB shortcuts etc) gets trained. lol

[John Davidson] Pre 10.0.6 we had tons and tons of projects as versions and it started getting sloppy, even with folders. Now with new the CC format it’s neat and clean.

Isn’t it just as messy using CC’s?… other than the fact that everything lives in the event? I’ve always made a “master” project folder for each event (same name), then subfolders (containing deeper subfolders) for all the different spots and versions. I’m sure that, like you, I’ll have at least 5 – usually more – versions of a spot before it even gets to V1. And then multiple versions after that. Usually around 10-15 or so projects (sequences) for each spot. And I’ll often have 5 or more spots… a lot of projects. 😉 Honestly, I like keeping that mess out of the event. It also allows me to duplicate the “master” folder, and pull out and archive folders of projects that I don’t need. I guess it’s a workflow thing? We do mostly movies, so we’re often cutting stuff for the same feature for months at a time.

In any case… thanks for taking the time to put that tutorial together!

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

~”It is a poor craftsman who blames his tools.”~

[John Davidson]

Hey Charlie, thanks! I’m going to reply/continue on Blog #5 as this thread is longer than….well…it’s pretty long. 🙂

John Davidson | President / Creative Director | Magic Feather Inc.

[Oliver Peters]

[Chris Harlan] “It looks wild, though. I was chopping up a bunch of dia when the post came in last night, which doubled my appreciation of how lovely such a thing would be. If it really works.”

I noticed tonight that I did seem to have some instability with the Waves plug-ins in X. When I quit, I sometimes have the need to force quit X. The app closes but the icon is still lit. Once I saw a crash report afterwards, which noted a Waves Shell problem. I also have some standard Focurite Scarlett filters on this machine and those appear to be OK. Apparently no problem with the Wave plug-ins in the audio apps (Audition, STP, Soundforge) on this machine.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Chris Harlan]

They still have their New Years Sale going, but sadly Vocal Rider is not or is no longer a part of it.