Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations still driving me nuts

  • still driving me nuts

    Posted by James Ewart on June 1, 2015 at 12:12 am

    I can get over most of it but …

    We come back to this time and time again. Calling a timeline a project is so hopelessly confusing and if anything it becomes more annoying as time goes on.

    Language is language. To start calling carrots bananas just for the sake of being different is beyond ridiculous don’t you think? How many years in and it still grates.

    Call it a timeline. A timeline is not a project.

    A project is “a piece of planned work or an activity that is finished over a period of time and intended to achieve a particular aim”

    Walter Soyka replied 10 years, 10 months ago 29 Members · 288 Replies
  • 288 Replies
  • Douglas K. dempsey

    June 1, 2015 at 12:35 am

    James, I have posted about this many times and most people think it is no big deal. To me it is significant, in demonstrating Apple’s goofy consumer mentality. I have adjusted to “Library-Events-Projects” but to a client or friend I can only apologize. It should be “Projects-Clips-Timelines (Or Sequences, or Edits).

    Doug D

  • James Ewart

    June 1, 2015 at 7:51 am

    I’m sure people will think “why is he still banging on about that?”. But it’s because It is constantly something have to make sure people don’t get the wrong end of the stick about and so I have to call it a ‘project timeline’ to be certain I’ am communicating clearly.

    I can kind of get over Library (pointless but at least less confusing).

    Event (well funnily enough I had reason to be rather pleased of that the other day. Multiple day shoot each Event a different day).

    But WAY too late to change the name of a sequence or timeline to something used in every other NLE (I think) and referring to a completely different “thing”.

    I’ll get over it one day.

  • Tim Wilson

    June 1, 2015 at 9:54 am

    [Douglas K. Dempsey] “I have adjusted to “Library-Events-Projects” but to a client or friend I can only apologize.”

    and

    [James Ewart] “I’m sure people will think “why is he still banging on about that?” …. because I have to call it a ‘project timeline’ to be certain I am communicating clearly.”

    I call this kind of thing the Pebble in the Shoe Principle. As hard as it is to climb a mountain, it can be excruciating to walk a short distance on flat ground with a pebble in your shoe.

    Apple may have created a previously unimaginably efficient mountain mover, but that doesn’t mean that they haven’t also created a number of brand new pebbles that didn’t need to be created, and placed them squarely in your shoes.

    This language is still a problem. It never had to be.

    Of course, pebbles are stone age, and dinosaurs are stone age, so everyone who finds these shiny space age terms occasionally exasperating is surely a dinosaur, right? Right.

  • Eric Santiago

    June 1, 2015 at 12:30 pm

    Great now I have to stop saying…

    “This is called a project…I mean sequence….or timeline..wait maybe just call it a project…”

    during my instructions in class 😉

  • Jeremy Garchow

    June 1, 2015 at 2:48 pm

    In your Libraries, do you typically work on one Project? Like, you have one single timeline that needs to be exported from your Library? If you have another timeline that needs exporting (like a different, um, Project) do you start a new Library?

    Do you use multicam, or synchronized clips, or Auditions?

    I need to write this up, for reals, but I simply can’t find the time. There are fantastic reasons that Apple, at least in my mind, has chosen to differentiate a timeline or sequence from a Project, but part of that means that you really have to use FCPX how it was designed to be used, and not use it like other project based systems. I know, that’s shocking news I’m sure.

    Also, if you told someone, I’ll send you my timeline, or you asked them to send them their timeline, are you saying they wouldn’t know what to do?

  • James Ewart

    June 1, 2015 at 2:54 pm

    Hi Jeremy.

    I might keep two closely associated “jobs” in one library. Each of those might comprise 5 or ten timelines which I want to put into a transfer library but when I do, the Library is still quite a few gigs and I don’t want it to have have actual media in it. But it still contains media I don’t need as it’s all in the duplicated library on the external drive. I don’t ask it to copy media … it still does though. or appears to and the size of the Library would suggest this is the case.

    If I tell someone I am sending a timeline it’s not a problem. But it’s not called a timeline is it? It’s called a project now!

    And it still confuses people and I am so bored with writing project/timeline every time to make sure there is no confusion

  • Jeremy Garchow

    June 1, 2015 at 3:15 pm

    [James Ewart] “And it still confuses people and I am so bored with writing project/timeline every time to make sure there is no confusion”

    So just call it a timeline if it’s really that confusing. The FCPX manual uses the word timeline.

    No one will fault you for it.

  • Nick Toth

    June 1, 2015 at 3:15 pm

    Wouldn’t any FCP X user know exactly what you’re talking about when you say project, event, library?

    When I’m in the Midwest of the US, I know when they say “sack” they mean “bag”. When someone in the Northeast says “grinder” I know they mean “sub” and vice-versa. 🙂

  • Jeremy Garchow

    June 1, 2015 at 3:16 pm

    [Nick Toth] “When I’m in the Midwest of the US, I know when they say “sack” they mean “bag””

    It’s a pop, not a soda. Got it? 🙂

  • James Ewart

    June 1, 2015 at 3:19 pm

    [Jeremy Garchow] “The FCPX manual uses the word timeline.”

    Does it/

    Terrible confession time. I never read the manual. Just did Ripple.

Page 1 of 29

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