Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Serious X Editing for Speed

  • Jeremy Garchow

    December 1, 2015 at 9:57 pm

    [Steve Connor] “I think this is an argument that begs to be quantified, but is in fact broadly unquantifiable.

    Just don’t call it asymmetrical quantification. Then everything goes mad.

  • Oliver Peters

    December 1, 2015 at 10:06 pm

    [Nick Toth] “and the example that Oliver used can be done in FCP X as well”

    Do you mean the replace function? If so, I’d love to see how it could be done in X as well as in PPro. IMHO, replace in X is quite possibly the worst implementation of this function in any NLE.

    – Oliver

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

  • Oliver Peters

    December 1, 2015 at 10:15 pm

    [Joe Marler] “Maybe that’s understandable since historically that’s all editing software could do.”

    I don’t understand that statement. NLEs have been able to do advanced effects, audio editing/mixing and color correction for many years.

    [Joe Marler] ” I have personally seen cases where Premiere editors spent weeks viewing the material before importing, copying favorite clips into folders and making hand-written timecode notes. ….
    With FCP X you could import the whole thing and do the initial pass in skimmer marking range-based favorites, rejects, keywords and even notes.”

    That’s kind of irrelevant. It goes to personal style. Many people learn the material better this way, so Finder-level organization is quite common. In fact X actually encourages it because these folders are supported as keywords on import. same as they become bins in Premiere Pro. Creation of favorites/rejects with show/hide functions have existed in Premiere and Media Composer for quite awhile. Range-based favorite is unique to X, but not the rest. People like tangible items, like scene boards, transcripts and written notes, regardless of the software they use. It has nothing to do with speed or lack of functionality.

    – Oliver

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

  • Charlie Austin

    December 1, 2015 at 10:16 pm

    [Oliver Peters] “Do you mean the replace function? If so, I’d love to see how it could be done in X as well as in PPro. IMHO, replace in X is quite possibly the worst implementation of this function in any NLE.”

    If you mean the fact that there is no Match Frame replace function in X, I agree. It’s maddening that it hasn’t been put in at this point. However, I’d have to disagree strongly regarding the Replace functions that do exist (Replace, Replace from Start, Replace from End, Retime Replace, and Audition replace). I find them to be as good or better (meaning easier to use, obviously they mostly do the same thing) than other NLE’s.

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

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

  • Jeremy Garchow

    December 1, 2015 at 10:25 pm

    [Charlie Austin] “If you mean the fact that there is no Match Frame replace function in X, I agree. It’s maddening that it hasn’t been put in at this point. However, I’d have to disagree strongly regarding the Replace functions that do exist (Replace, Replace from Start, Replace from End, Retime Replace, and Audition replace). I find them to be as good or better (meaning easier to use, obviously they mostly do the same thing) than other NLE’s.

    +1

  • Oliver Peters

    December 1, 2015 at 10:32 pm

    [Charlie Austin] “I find them to be as good or better (meaning easier to use, obviously they mostly do the same thing) than other NLE’s.”

    So then explain how you’d achieve the same example I mentioned in the least number of keystrokes in FCPX. Premiere Pro: 20 phone number titles on a timeline. Select all. Replace with bin selection in a single step.

    – Oliver

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

  • Shawn Miller

    December 1, 2015 at 10:36 pm

    [Joe Marler] “With broader capability this evaluation becomes more complex. E.g, what if an FCP X editor needed to do spectral audio correction? If he spends lots of time tweaking with the EQ when a Premiere user can use Audition, does that make FCP X slower? Or is that just saving cost not time because the FCP X guy can buy SoundSoap or Izotope?”

    The Premiere Pro editor can also use Sound Soap or iZotope. Maybe 3D text is a better example?

    Shawn

  • Charlie Austin

    December 1, 2015 at 10:45 pm

    [Oliver Peters] “So then explain how you’d achieve the same example I mentioned in the least number of keystrokes in FCPX. Premiere Pro: 20 phone number titles on a timeline. Select all. Replace with bin selection in a single step.”

    Easy if they’re generated titles. Select Edit>Find and Replace Title text.

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

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

  • Michael Gissing

    December 1, 2015 at 10:49 pm

    [Oliver Peters] “You’d mark off certain areas of the timeline and one editor could be working on one area only, while another editor on another workstation could work on a different section of the exact same timeline.”

    We had that over 15 years ago with the dSP DAW. It was fully networked off shared SCSI RAID drives and multiple users could access and work on specific tracks and when saved the other users would get an update message. Obviously track rather than region based is not ideal but we were sound posting locked duration fine cuts so it worked well.

    I still am amazed at how slow the NLE world is to catch up with features we have taken for granted with DAWs for 20 years.

  • Michael Gissing

    December 1, 2015 at 10:58 pm

    [Nick Toth]”The anti-FCP X debate is tiresome.”

    Discussions like these also don’t help except when little gems of productive shortcuts or better workflows emerge. If the best argument for software is just who’s the fastest then it just brings out preconceptions and biases. I am more interested in hearing editors talk about what software is fun and can do all that they want in their area of work without needing an osteopath to keep them working.

Page 5 of 6

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