Richard Herd
Forum Replies Created
-
Richard Herd
March 20, 2012 at 5:04 pm in reply to: Thoughts on why FCP X is here to stay and the Mac Pro isn’t.[Craig Seeman] ” I’ve never lost a project”
I knocked on my wooden desk.
Once film editors get a chance to really use it. They’ll love it too. I mean folks got into this industry to cut stories and X does that very very well.
-
Did you play with it, or did you really cut and deliver something?
I’m almost done with a project (did not DL 10.0.3 thankfully); it’s a non-deadline project by the way. The actual cutting of a story is superior. I’ve also simultaneously been using Legacy and PP for other stuff, both of which “feel” like steps backward in terms of actually cutting a story, and we all know we do a lot more than just cut. I downloaded Media Composer trial, but sheesh I still dislike it, haven’t used it since 2003.
By “preview monitor,” do you mean a color grade monitor thing? Or do you mean the skimmer tool? The color correction window is pretty decent–better than PP, IMO– but I miss my curves from Color. As far as color grading goes I hear, but haven’t used, the XML to da vinci work very well.
[Andy Field] “Folks who must deliver deadline broadcast and film aren’t sitting around playing with something only to make their work more difficult”
In fact they are just “playing” with X, because they are too busy hopefully to actually learn X. And make no mistake about it: there is a learning curve. I’ve said it before, I’ll say it again. I had to read the manual so often to simply begin a project and wrap my imagination around the nomenclature that this first project has taken easily three times longer than it should have. Knowing this, I offered a discount to the producer. But now that I know the stuff I know the actual cutting is much quicker, more accurate, more flexible.
But I know there’s no way to learn something without doing it. In any case, one must blow away the notion that one can sit down in any app and then know it after playing with it once or twice. Why do that if you have a customer sitting next to you? Could you imagine: “Sorry I need to close the app and restart it.” And “sorry I need to duplicate the project every now and again and store it on a hidden .dmg in case the project gets corrupt.”
I can’t imagine anyone is still reading, but if so: I do 99% of my title in AE, anyway, but I find myself using the titler in X — better than legacy. My next real learning is audio. Whew. Wish me luck. The best part is the FX are all from Logic and they really work awesome-ly.
-
Richard Herd
March 20, 2012 at 4:11 pm in reply to: Thoughts on why FCP X is here to stay and the Mac Pro isn’t.[Walter Soyka] “If you didn’t already have Apple hardware and FCP7, would you really be buying iMacs and FCPX for all your professional work today?”
It depends. If I hoped to cut such gems as John Carter, I would need the professionally accepted software. Maybe I could recut Ishtar too.
-
[Walter Soyka] “Doesn’t that make both Tony West and Andy Field correct?”
Argh! And such is the problem with commensurablility and construal.
-
In your opinion, what computer do developers want to use to create iApps?
-
But have you actually done any cutting in X?
-
Check the compound clip that there isn’t a fade in there. We can’t see what the audio is doing in the compound clip. We can see FCP see there’s audio, we just can’t see what FCP thinks it should be doing with the audio in the CC.
Have you made sure all the audio are assigned their proper roles?
-
The actual job of cutting pic is very awesome.
-
Richard Herd
March 19, 2012 at 7:48 pm in reply to: Thoughts on why FCP X is here to stay and the Mac Pro isn’t.[Jim Giberti] “[Robert Bracken] “I’m really excited to see where FCPX will go. It will achieve great things.”
I don’t mean to nitpick Robert but this statement is in opposition to itself.”
It’s an ontological argument 😉