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 — An Example

  • Aindreas Gallagher

    October 3, 2011 at 11:31 pm

    oh right, simple really – I mean opening two bins as two separate containers to view, but there can be no two or more containers opened in FCPX, as there is only the one browser?

    you cannot open, view, scan and contrast say two keyword collections as two separate items? the basic architecture of FCPX does not allow for this operation, and I find it very useful when assessing footage: opening, and scanning multiple bins as discreet containers – FCPX’s keyword/event list populated into one single browser does not allow for this behaviour?
    it does not allow for opening and onscreen spatial arrangement of bins/keyword collections. I find that ability quite powerful.
    FCPX has only one single persistent browser as a single window view for all assets? that I do actually find rather limiting.

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    October 3, 2011 at 11:41 pm

    dude, andy is good to go.

    ..I.. get itches thinking about plowing into avid.

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • David Roth weiss

    October 3, 2011 at 11:54 pm

    [Aindreas Gallagher] “..I.. get itches thinking about plowing into avid.

    I’m plowing fields of gold in Avid these days myself… though not with clients looking on just yet.

    Simple editing in Avid is duck soup; the plow needn’t go to deep in that regard. It’s when you need to go deeper and find something you’ve never seen before that the plowing gets a bit harder. Premiere is not that much different. It can be a bit frustrating with both apps in that regard, but then good old FCP was always that way for many newbies too.

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles
    https://www.drwfilms.com

    Don’t miss my new Creative Cow Podcast: Producing Episodic TV with “24” Producer Michael Klick:
    https://library.creativecow.net/weiss_roth_david/Podcast-Series-1_Michael-Klick/1

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.

  • Aindreas Gallagher

    October 4, 2011 at 12:02 am

    i know – like everyone says – if FCPX does one thing, FCPX reminds you that you actually have to know and be able to execute on the other editing systems within about 12 to 14 months or face peril.

    premiere I’m ok with so far, its more or less a puddle jump largely, although there is some weird (by which he means new) stuff there. Am loving the keyframe editing though – proper nice old style AE inline timeline stretchable keyframe beziers! I missed you! – makes a huge difference in sultry fades to black I find.

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Jeremy Garchow

    October 4, 2011 at 12:39 am

    Got ya. I get it now, sorry it took me so long.

    Two collections can be selected, but you can’t drag them to where you want.

    I guess I find the new browser much more flexible and visual, and texty when it’s needed. That doesn’t matter as you don’t. I see your point, it’s how you work.

    So say we all.

  • Aindreas Gallagher

    October 4, 2011 at 12:44 am

    Oh BSG. Where is blood and chrome I ask?

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Jeremy Garchow

    October 4, 2011 at 1:00 am
  • David Lawrence

    October 4, 2011 at 5:49 am

    [Chris Kenny] “People keep accusing Apple of not understanding what editors do.”

    According to Larry Jordan: “Retaining In and Out points for clips in the Event Browser is undergoing a debate in Apple. So is the ability to read source timecode for clips in the Timeline.”

    If the geniuses in Cupertino really are debating persistent In and Out points and reading source timecode, I think the case of Apple of not understanding what editors do makes itself.

    [Chris Kenny] “Some critics have confused the mechanics of how these tasks are performed in current NLEs with the tasks themselves.”

    Let’s say there’s a bathtub filled with water in front of us. Our task is to empty the bathtub with the tools we’ve been given. I get to use a five-gallon bucket. You get to use a spoon. Same task, different mechanics. One of us is gonna be a lot more efficient than the other. Task and mechanics are intrinsically related when it comes to efficiency. That’s what UI design is all about.

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • David Lawrence

    October 4, 2011 at 6:22 am

    [Jeremy Garchow] “Supposedly soon.

    Or here:

    https://forums.creativecow.net/readpost/335/602

    lol! How did I miss that thread?

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • David Lawrence

    October 4, 2011 at 6:28 am

    [Steve Connor] “Yes I have and I’m still interested in exactly what constraints are making the process inefficient, is it the lack of tracks? is it connected clips?”

    Fair question, Steve. Some of the constraints have to do with issues Aindreas raised in his example regarding the fixed screen layout and wanting more flexibility with how bins and multiple sequences can be arranged. Others have to do with the nature of the timeline itself. I’ll explain in more detail when I answer Jeremy.

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

Page 8 of 12

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