Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations The Open Timeline and Spatial Workflows — Another Example

  • Rafael Amador

    October 16, 2011 at 12:56 pm

    [Jeremy Garchow] “[Rafael Amador] “I’ve been working with DVCpro25, 8 years before FC release (Barcelona’92 Olympics was the big public presentation of the format).”

    That was on a laptop over FireWire?”
    No on PANASONIC VTRS.
    You said “The idea of lightweight native codec editing over firewire and laptop, in Ok (dv), better(dv50), and pretty good qualities (DVCPro HD).” belongs to Apple. Sorry but not.
    Apple got it done first (in collaboration with SONY).
    All waht you mention has been but FCP implementations.
    I agree with you that the great contribution of Apple to video (beside QT) has been: FCP.

    [Jeremy Garchow] “Rafael Amador] “but i doubt very much that you would have been very happy with an application that simply won’t allows you to take certain jobs, and I don’t mean that you can make the same product. I’m talking that you are tied to a computer and an storage system.”

    What do you mean?”

    I mis explained my self.
    I mean that you may be able to do the same product in both apps, but there are jobs and workflows I can’t undertake in FCPX for what I explain next.

    [Rafael Amador] “Why do I want more efficiency if I’ve o stay at home?”
    Why can’t you work on a laptop on FCPX? I don’t get it.”

    In fact I’m running FCPX in a laptop, no problem, but how I’ll do to move my projects when the iMac will arrive?
    I often work in the provinces and I have to do half of the job there (I make a lot of ITWs to minorities people; I need them translated on location). I work with small eSATA/FW800 drives (laCie LittleBigDisk).
    Back home I move the media to a CalDigit and keep working.
    I bring to the field the old MBP Core2Duo and finish in the “i7” (prefer to keep the new one at home).
    If I’m not wrong I can’t work this way with FCPX.

    [Jeremy Garchow] “Sequences, Compounds clips, all are the same story with different under-laying technologies.
    Compounds clips are basically QT REFERENCES FILES created inside the application.”

    So FCPX works for you in this regard then?

    Compounds are not reference movies. Far different.”
    Then, I don’t catch well the idea of the Compound clip.
    I see it as kind of “virtual clip” where you can “compact” many clips (and even other elements) together.
    Then you can manage that as a single clip.
    rafael

    http://www.nagavideo.com

  • Jeremy Garchow

    October 17, 2011 at 12:34 am

    [Rafael Amador] “If I’m not wrong I can’t work this way with FCPX.”

    Of course you can. It’s actually pretty easy:

    https://help.apple.com/finalcutpro/mac/10.0.1/#verb8e5fcf4

    Jeremy

  • David Powell

    January 9, 2012 at 10:56 pm

    From what I’ve read the keyword collections are restricted to one computer though no?

  • Jeremy Garchow

    January 9, 2012 at 10:58 pm

    [David Powell] “From what I’ve read the keyword collections are restricted to one computer though no?”

    Sorry, I’m not quite following what you’re saying.

    If you move the Event to another computer/hard drive, the keywords go with it. Is that what you mean?

    Jeremy

  • Tom Wolsky

    January 9, 2012 at 11:25 pm

    The keyword collections are part of the event. Wherever that event is see the collections will be visible. If I have a drive or an Xsan and make change to that event, and then take that drive or have someone else access the Xsan the collections will be there.

    All the best,

    Tom

    Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
    Coming in 2012 “Complete Training for FCPX” from Class on Demand
    “Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press

Page 5 of 5

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