Forum Replies Created

Page 1 of 87
  • Steven Gonzales

    May 17, 2012 at 7:26 pm in reply to: Anyone on here cut a feature in FCP X?

    I’m curious about audio on the feature. Did you use camera audio, or did you sync separate audio?

    Every feature I’ve done had post sync due to dual system sound, even when it was a video shoot and there was also a dummy camera audio track.

  • Steven Gonzales

    January 28, 2012 at 7:47 pm in reply to: Which FCP version for newbie?

    Thanks for the clarification. Thanks for putting that interview out there.

  • Steven Gonzales

    January 26, 2012 at 6:52 pm in reply to: Which FCP version for newbie?

    Thelma Schoonmaker still uses Lightworks. Hugo was edited in parallel with Avid and Lightworks.

    https://dv.com/article/113960

    “Thelma cuts on [EditShare] Lightworks, but by mirroring her edits on Media Composer, I had the information in a form ready to disperse to the visual effects designers.”

  • Steven Gonzales

    January 4, 2012 at 11:41 pm in reply to: Bunim/Murray chooses Avid

    A lot of the emotion on this board is because many folks that post here were the ones that argued FCP into usage.

    With that in mind, it’s not surprising that these folks are at the FCP houses.

    The cost / benefit of FCP was great compared to Avid, but only if the shared network investment got through its usable life.

  • Steven Gonzales

    August 20, 2011 at 4:51 pm in reply to: Some thoughts on the FCPX Forum

    So post a hint or discovery.

    Remember when the FCPX Techniques forum was created?

  • Steven Gonzales

    August 2, 2011 at 11:37 pm in reply to: What Do we Do now? How Do you Feel?

    Avid’s really not that hard to learn. Remember, you have the experience of knowing one NLE, and they all basically do the same thing.

    I think the key to understanding Avid is thinking that they have two large needs: the interface needs to appear essentially the same in the Windows OS and the Mac OS, which means they don’t utilize either OS to the best potential.

    The other is that there is a legacy base, which means they can’t drastically change the interface. There is a lot of early 90’s quirks about the program.

    But they have some tutorials online, and it is the big elephant for feature films and a lot of TV.

    It’s clumsy, but you can get used to it.

  • Steven Gonzales

    July 29, 2011 at 10:30 pm in reply to: Ask yourself this question

    Apple doesn’t want the graphics card market because it’s too risky, they don’t want the education market because it can’t pay their margins, and they don’t want the professional video market because it’s not big enough.

  • We all must admit that there are many editors alienated from the new FCP. While Crumplepop really had no choice but to embrace the new version, their enthusiastic support (coupled with other companies in the near future) is absolutely necessary to restart the FCP momentum.

  • Steven Gonzales

    July 15, 2011 at 7:53 pm in reply to: All the DRAMA!

    Not to nitpic, but OS9 shipped with OSX early releases, and ran in the classic environment.

    FCP7 is not shipping, and is not available to a new purchases with legacy needs.

    OSX allowed for OS9 workflows.

    FCP X does not allow for FXP 7 workflows.

  • Steven Gonzales

    July 15, 2011 at 6:04 pm in reply to: All the DRAMA!

    OS9 to OSX included the “classic mode” to keep compatibility during the transition. I don’t believe this analogy is appropriate.

Page 1 of 87

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