[Charlie Austin]

[Tim Wilson] “Wow, I think that’s way off. Apple dropped “Computer” from its company name in January 2007. Was that guy not around for that? And by then, Apple had already long outgrown the computer industry. ” … “I’m really stupefied by his statement. It makes no sense to me at all.”

I dunno.. First, to be fair, the quote does seem a little random taken out of context. He wasn’t talking about the the corporate description at all, I made that connection. So I guess I should be the object of your stupefaction. 🙂 It’s from a footnote to a larger opinion piece which is pretty interesting. As I said, in terms of Pro Apps, computers etc, I don’t think it means anything.

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

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

[Charlie Austin]

[Andrew Kimery] “This week they dropped the words ‘professional applications’ from their definition:””

As I pointed out, they kept iMovie in the blurb. And honestly, after spending the last week or so working in FCP 7 and/or Pr CC, I think I’d rather work in iMovie. :-/

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

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

[Charlie Austin]

[Andrew Kimery] “This week they dropped the words ‘professional applications’ from their definition:””

Fortunately they kept iMovie in there. 😉

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

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

[Charlie Austin]

[Daniel Waldron] “Maybe I’m paranoid, but I haven’t even upgraded to Mavericks yet…”

You’re paranoid. 🙂 Pr and 10.9.4 work fine together. 🙂

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

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

[Charlie Austin]

[TImothy Auld] “It is possible to do almost anything in FCPX with workarounds. And the first word there is “work.” And in EVERY OTHER NLE I don’t have to worry about primary or connected story lines.”

There are about 3 things in X I can think of that require workarounds. Shall I list them?

-no match frame replace (annoying)
-no true batch export
-no clip targeting/simultaneous selection of multiple edit points

Most everything else, particularly stuff being discussed here, just works differently. It ain’t rocket science. Just different. And before anyone gets their panties in a bunch, let me just say that I’ve been working mostly in Pr the last couple weeks. It’s fine. It’d be just as easy for me to list all the “workarounds” I need to do in Pr to accomplish what is dead simple in X. But I won’t because I work with Pr the way it works, and I work with X the way it works.

Like Franken-dialog. Just as easy (easier IMO) in x as anything else. The Bonus in X is that once I get all my phonemes cut, or find the perfect dialog cheat to pix, I can hit a keystroke and lock it up in a single clip. Always in sync, and accessible in my browser. Simple, powerful. To do that in Pr requires a workaround. 🙂

Pr is great. For FCP 7 folks it’s an easy transition, particularly if you cheat and use the FCP 7 KB shortcuts. I don’t because I like to use software the way it was designed to be used, but maybe that’s only me. 😉 I just prefer X. Simpler UI resulting in way less desktop clutter. Really easy to work in the timeline, I can just cut. Every other NLE requires at least some pre-edit thought about where things will go. No tracks to mess with, and I can just toss unused bits at the end of the timeline to store them. Literally just throw them there. 😉 Skimming in general and Clip skimming in particular, that is huge. And, it’s so much easier to find stuff (a huge part of my job) it’s not even worth comparing it with anything else.

I made an FCP X library with all the same media as my Pr project because it’s faster to find something in X, and then just enter the name in the Pr search field to get to it. I’m talking about wading through thousands of SFX and dozens of MX cues (in dozens of bins in Pr). A pleasure in X, a chore in 7, Pr, MC.

Also I never ever need to remember to save. Yesterday, I was working on X and Pr jobs at the same time. I was in X working, Pr in the BG. The computer froze. Not an app crash, just everything locked up requiring a force reboot. Opened X, the edit I had just made was still there. Had to hunt in Pr for a backup, rename it, resave it, and a couple edits were missing. Not really a problem, but little things like that make a big difference. To me anyway.

In any case, the newly announced features in Pr sound nice. Having smart folders will be useful. Good times. 🙂

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

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

[Charlie Austin]

[Vince Becquiot] “Isn’t that a feature that started with CC 2014?”

Nevermind… operator error. :-/
————————————————————-

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

[Charlie Austin]

Click the “show Angles Viewer” button in the pop up menu in the upper right corner of the viewer. You need to cut the multi cam clip into a timeline and you can then switch between angles…

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

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

[Charlie Austin]

You’ve still got this import pref checked right?

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

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

[Charlie Austin]

[Bret Williams] “Did you look at the video? Nice smooth grads. I didn’t see any problems either.”

I did, the blob edge gradient looks fine at 720 on YT, but I think I see what he’s talking about if you look at the non-colored area. (kind of moving graininess?) That’s why I suggested a slight blur. Honestly I don’t know where in the chain it’s coming from, it may well look like that in the generator source and just not show up in the X UI.

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

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

[Charlie Austin]

[Andrei Popa] ” which gets rendered with wave like artefacts”

I’ve seen this on stuff rendered out of many apps, after effects, FCP, Pr etc. I forget exactly what causes it, but try dropping a gaussian blur on the BG and play with the strength (to shouldn’t need too much) and see if that helps.

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

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