Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Creative Community Conversations FCP7 is dead. Why can’t there be a new FCP7?

  • FCP7 is dead. Why can’t there be a new FCP7?

  • Josh Cook

    September 25, 2014 at 3:31 pm

    This may seem academic, but I would love to know what others think.

    Despite being discontinued, I have been hired to edit on FCP7 continually up until now. I don’t cut on Avid, but I DO present myself as a Premiere editor as well. I’ve had maybe one Premiere job in the past five years. With the prevalence of FCP7 still in the professional space (I’m talking mostly ad agencies and yes, a few production companies), why is no one recreating it? Why isn’t there someone simply coding a new edit software from the ground up that takes advantage of current hardware that blatantly copies the design of FCP7? I suppose you might have to name a few things different to avoid copyright issues or something, but NLE’s are all kinda based on the same concept so there shouldn’t be patent issues. It seems like a crazy obvious opportunity to serve a rather large population who want this. Is there something I don’t know?

    How many forum posts have you read in the past decade about reluctantly switching to Premiere, Avid or (gasp) FCPX?

  • Mark Suszko

    September 25, 2014 at 3:44 pm

    Some say that Premiere CC IS the re-created FCP 8 and 9 that never showed up. You can map the keyboard to the shortcuts you already know. The timeline is much the same, as are the bin structures.

    You can’t make a new FCP7 because the typw of underlying code for it is no longer supported. What you’re asking for is to *emulate* the GUI of FCP7 in a 64 bit up to date platform.

  • Ronny Courtens

    September 25, 2014 at 4:08 pm

    FCP 7 is not “dead”, a lot of people are still using it. But if you are a freelance editor and you still want to be a freelancer in the future, you will need to know different NLEs and not restrict yourself to just one.

    – Ronny

  • David Mathis

    September 25, 2014 at 4:09 pm

    While part of me does miss Final Cut Pro 7 and versions prior, I have found FCP X to be fast (in most situations), responsive, more efficient and fun to work with.

    The biggest thing I miss most is the “Send To Motion” function. I doubt that we will see that feature anytime soon. On the other hand, it is fairly easy to create a custom transition, generator, effect or title in Motion 5 for later use inside of FCP X which is a huge time saver and fun to do.

    I did find myself fighting the magnetic timeline at first, granted that tracks are useful but the way FCP goes about editing makes things much faster.

    Not sure if you have been following Resolve 11 but in the latest update (still in beta with full version due at end of month) is the ability to perform a swap edit or add a default transition to multiple clips at the same time. Both of these features were in FCP 7 and some earlier versions. Resolve is not yet considered a prime time NLE because of choppy playback but maybe that will be addressed. Until then, FCP X gets the job done and I find it a pleasure to work with.

  • Richard Herd

    September 25, 2014 at 4:14 pm

    [Josh Cook] “How many forum posts have you read in the past decade about reluctantly switching to Premiere, Avid or (gasp) FCPX?

    Probably somewhere around 10,000

  • James Patterson

    September 25, 2014 at 4:27 pm

    Get over it, FCP 7 is dead and it’s not coming back, but to be honest if you just want a similar UI to 7 then the move to premiere should be straight forward. In any case I’ve always set FCP and Avid up as similarly as possible and Premiere is even more flexible with keyboard controls.

    Not sure where you’re based but in London all the agencies are switching from FCP7 to Adobe.

    Best

    Paddy

  • Charlie Austin

    September 25, 2014 at 5:11 pm

    [David Mathis] “add a default transition to multiple clips at the same time.”

    umm… like this?

    default trans

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

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

  • Andy Neil

    September 25, 2014 at 5:13 pm

    [Josh Cook] “Why isn’t there someone simply coding a new edit software from the ground up that takes advantage of current hardware that blatantly copies the design of FCP7?”

    Because writing an NLE from the ground up isn’t easy. Just ask blackmagic design. Without an existing foundation to start from, it would take years and lots of coders to get anywhere near approximation of final cut 7. By the time you finish, it would be completely obsolete comparative to the existing NLEs out there.

    Besides, people like FCP 7 for it’s editing paradigm and it’s familiarity. Any new editing software that skirts around Apples patents without violating them would require it’s own learning curve so you’d be in the same place as the other software companies.

    I recently had to edit something in FCP7 and let me tell you, that NLE feels really damn old.

    Andy

    https://plus.google.com/u/0/107277729326633563425/videos

  • Herb Sevush

    September 25, 2014 at 5:25 pm

    [Josh Cook] ” It seems like a crazy obvious opportunity to serve a rather large population who want this. Is there something I don’t know?”

    You don’t know how hard it would be. If it were easy, it would have happened, because you are correct, there is a market for FCP8. While PPro is close, since it was modeled on FCP from Premiere’s first “pro” iteration, it is not nearly the same.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • Bret Williams

    September 25, 2014 at 5:26 pm

    I was wondering when someone would set that straight. Sorry David I was getting tired of hearing you say that! 🙂

Viewing 1 - 10 of 65 posts

Log in to reply.

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