Forum Replies Created

Page 11 of 26
  • Douglas K. dempsey

    July 18, 2014 at 9:40 am in reply to: Oh dear, we will switch to fcpx!

    Good luck, Mark. Many of us are using it successfully and enjoying the process. “We Love X!”

    However, I feel your uneasiness. A lot of people here don’t mind or fret over the garbled language — Libraries, Projects, Events — which work fine but perversely scramble the logic of editing. But it bothers me. Years of making movies tells me that I have a Project in which I try out different Sequences using clips from my Bins (or Reels, or Clip Collections).

    It IS of concern because it possibly expresses Apple’s overall intent to keep X skewed consumer and not so much pro. “Events” is a concept shared with the Instamatic-like iPhoto app, and makes you feel that Apple sees everyone as a Mom & Pop Home Movie Maker, who in turn see the stuff that comes out of their camera as an important “Event” in their lives: Baby’s first step, Grandma’s birthday, Vacation at the Shore etc.

    Couple that with Tim Cook’s scary pronouncement the other day, speaking about the new IBM enterprise partnership, and the fact that Tim personally does 80% of his work on an iPad: “There’s no reason why everyone shouldn’t be like that. Imagine enterprise apps being as simple as the consumer apps that we’ve all gotten used to. That’s the way it should be” …

    Maybe there will be an enterprise version of FCPX that uses “Campaigns, Strategies and Resources.”

    Doug D

  • Douglas K. dempsey

    July 10, 2014 at 4:09 pm in reply to: Destructive edits

    Sorry, wrong, thought I was looking at an overlap, not a complete clip overwrite. Yes, that’s always a pain which is why, even in track NLE like Legacy, tend to leave upper/connected or secondaries in place until picture lock (and maybe a Snapshot of edit) before cleaning up via overwrites.

    Doug D

  • Douglas K. dempsey

    July 10, 2014 at 4:05 pm in reply to: Destructive edits

    I agree Overwrite is by nature destructive within a work session, but unlike word processors or image editors, you are not limited only to the Undo or Step Backward remedies. In your example, a simple trim back to the original configuration makes it feel a lot less “destructive.”

    Doug D

  • Douglas K. dempsey

    June 30, 2014 at 7:25 pm in reply to: OT: Photos.app = Aperture X

    iAgree

    Doug D

  • Douglas K. dempsey

    June 30, 2014 at 6:35 pm in reply to: FCP X or not?

    I froze my FCS 3 MacBook Pro 17″ on Snow Leopard. Also has CS3 and other stuff that is stable on that OS.

    It seems to be a sweet spot for older versions and EOL apps. Even a creaky app like CS6 Dreamweaver, which modern web builders scoff at, but Adobe still includes in CC suites … works perfectly in Snow Leopard, but is broken in Mavericks.

    I picked Snow Leopard because as far as I can tell, that was the last OS that issued ProApp updates (e.g. Frameworks and other files/folders) for FCP 7.0.3

    Now my costs are in replacing hardware! $310 Apple flat rate for new motherboard and RAM to fix display issues encountered while — get this — making DVDs in StudioPro for an old-school client!

    Doug D

  • Scott, point taken. The iMovie Pro relationship, as Andy notes, is better revised to iMovie as a kind of FCPX Lite. When I say “turns out to be true” I just mean that Alex’s observations show there is more than a surface UI relationship between the apps. I love X and never use “iMovie Pro” as a disparaging comment … which is why I will now drop it altogether in favor of Andy’s variation!

    Doug D

  • Marcus, I agree I don’t want to see any of the stuff we love about X watered down or pushed back toward conventional track-based apps.

    Doug D

  • Andy, good point. This Fall I will change my comment to be, “Well, if you’ve been using iMovie, then you’ve kinda been working in FCPX-Lite already … so the transition will be easy!” It really helps the less technically-minded students to hear that it will be pretty easy to get going in the software … while understanding it is a real Pro app that will handle anything they can throw at it.

    Doug D

  • The denigrating appellation “FCPX is iMovie Pro” a couple years back … turns out to be true.

    When I introduce it to students who proclaim they have no NLE experience, and are a bit wary of apps like Premiere Pro … I ask them, “Have you used iMovie, the free app on your Mac?” When they say yes, I tell them “Don’t worry, you’re ready to start FCPX, which looks very similar. It’s kinda like ‘iMovie Pro’.”

    It does point, though, to the scenario where FCPX never really breaks its bonds into a super-featured app … in the way many had hoped when it came out, e.g. comparing it to the arc taken from FCP 1 to FCP 7.

    Already you are seeing posts by people like David Lawrence, who noted that FCPX is a great meta-data-wrangling organizational app for eventual cutting on other NLEs. And some of use who enjoyed the teasing/promise of Resolve 11, imagined cutting in FCPX and finishing in Resolve.

    We may have to accept that FCPX will always be its own module, a quick-on-its-feet app that some of us will use for entire productions, and others will use along with a bundle of third-party products … just another tool in the box.

    Doug D

  • Douglas K. dempsey

    June 17, 2014 at 8:31 pm in reply to: FCP X and MBA

    Yes, I did small tests with late 2013 MBA, 512 SSD, maxed RAM and processor … and media on an external USB3.0 pocket drive, seemed to work just fine.

    Doug D

Page 11 of 26

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy