Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Death of Aperture-FCPX Next?

  • Craig Seeman

    June 28, 2014 at 4:27 pm

    [Andy Neil] “It just seems to me that people are far more willing to eviscerate Apple for doing the same thing as every other software company.”

    Although one might understand why that happens. Keep in mind I’m generally happy with Apple’s software and especially FCPX.

    At the time FCP legacy was EOL’d, FCPX was not yet an adequate replacement for many people. Given that Apple has mentioned nothing of Photo’s feature set for the Yosemite version, people are concerned about what will come and how long it will take to regain certain features. There’s a lack of confidence in Photo.

    I understand that people at WWDC who participating in workshop(s) around Photo or have seen the video of those workshops, have some confidence. Unless one finds that info or hear’s such accounts, one is likely to have some angst. Apple isn’t doing anything to address that beyond the brief PR statement people see on the news sites.

    Hearing nothing beyond that and, based on the FCPX release, people are ready to eviscerate Apple. I’m one of those “Apple trusting” folks but I’m sympathetic with those that don’t. Apple’s PR does not instill confidence.

    Personally I think Apple might want to more publicly show off the potential that it seems some at WWDC were introduced to (and I’m talking about the Yosemite version, not iOS 8 version).

  • John Godwin

    June 28, 2014 at 4:31 pm

    I still miss Liquid, it was waaay ahead of it’s time. I still think one of the reasons I like FCP X so much is that it’s sort of Liquid-like …

    Best,
    John

  • Herb Sevush

    June 28, 2014 at 4:53 pm

    [Bill Davis] “Herb, it’s just a linguistic convention, nothing more than that.”

    No, its not a linguistic convention, it’s a distortion of a linguistic convention, used only by editors who need to feel better about their choice of NLE. Nowhere else on the COW does anyone label any timeline “destructive.” If you were interested in describing a real as opposed to imaginary difference you could call Legacy timelines “fixed track timeline” as opposed to either floating track or magnetic timelines. That actually describes the difference. Destructive is just a pejorative justified by it’s use in other situations that are not relevant to the distinction between timelines. Conventions serve a purpose when useful, this one is merely mud slinging, like calling FCPX iMovie Pro.

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

  • Oliver Peters

    June 28, 2014 at 7:18 pm

    [Herb Sevush] “No, its not a linguistic convention, it’s a distortion of a linguistic convention, used only by editors who need to feel better about their choice of NLE.”

    Non-destructive timelines are the very essence of an NLE, going all the way back to the CMX 600.

    – Oliver

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

  • Oliver Peters

    June 28, 2014 at 7:27 pm

    [Oliver Peters] “Non-destructive timelines are the very essence of an NLE, going all the way back to the CMX 600.”

    Ironically, FCP X actually is DESTRUCTIVE. You can open a clip in its own timeline and completely destroy the essence within that master clip “container”. Once you do this, the only solution is to re-import the clip.

    – Oliver

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

  • Bill Davis

    June 28, 2014 at 10:31 pm

    Ok guys,

    Then give me a nice alternative term for what happens when an editor used to drop a clip (or the horror, a group of clips) into a Legacy timeline and the underlying tracks and clips all got instantly overwritten.

    You say that’s not “destructive” then what is it. Did we need an alternate term all along? “clip obliviation”?

    or perhaps “clip transubstantiative?”

    I put the clip there. I did something. And unless I played track tetris, the clip that I’d put there was GONE.

    To me – that’s “destructive” behavior.

    That the underlying media didn’t get destroyed is a silly distinction. My arrangement of said clip was, in fact, well and truly destroyed.

    I’m sorry the term angers you, Herb.

    And I’m still sympathetic to the loss of your beloved Legacy. But I don’t feel the slightest hesitation to use “destructive” in relation to what happened on my timelines for a decade as a Legacy editor.

    And so it goes.

    Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

  • Oliver Peters

    June 28, 2014 at 10:46 pm

    [Bill Davis] “overwritten”

    I think that’s descriptive enough. Yes, you overwrite. No, it’s not destructive.

    – Oliver

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

  • Oliver Peters

    June 28, 2014 at 10:47 pm

    [Bill Davis] “Then give me a nice alternative term for what happens when an editor used to drop a clip (or the horror, a group of clips) into a Legacy timeline and the underlying tracks and clips all got instantly overwritten.”

    Actually maybe the correct term is “stupid editor”. 😉 Especially if the editing method is to drag & drop from the browser to the timeline!

    – Oliver

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

  • Herb Sevush

    June 29, 2014 at 1:13 am

    [Bill Davis] “Then give me a nice alternative term for what happens when an editor used to drop a clip (or the horror, a group of clips) into a Legacy timeline and the underlying tracks and clips all got instantly overwritten.”

    Incompetence, if the editor didn’t want the clips to be replaced. If the editor wanted the clips to be replaced, I would call it editing.

    [Bill Davis] “I put the clip there. I did something. And unless I played track tetris, the clip that I’d put there was GONE.
    To me – that’s “destructive” behavior.”

    Yes, the editor was being destructive, but the timeline was acting just fine.

    The term destructive is used, non pejoratively, to describe a function of certain types of software. To flatten the layers in Photoshop there is no other choice than to loose all the layers. It is a function of the software, so flattening in Photoshop is rightfully described as a destructive process. In an NLE the timeline doesn’t force you to overwrite clips, that’s a choice an editor makes. For 20 years the term overwrite has been sufficient to describe the act, nobody ever called the action destructive till now. What has changed — it certainly isn’t the nature of a fixed track timeline. The term “destructive timeline” is used solely by FCPX editors as a pejorative to make their chosen NLE seem superior.

    [Bill Davis] “And I’m still sympathetic to the loss of your beloved Legacy.”

    Legacy was never my beloved. *edit was my beloved, Legacy was just a case of love the one your with.

    [Bill Davis] “But I don’t feel the slightest hesitation to use “destructive” in relation to what happened on my timelines for a decade as a Legacy editor. “

    I have no problem believing you when you say that your timelines were a scene of carnage, of that I have no doubt. It’s just that I don’t blame the software.

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

  • Mitch Ives

    June 29, 2014 at 1:29 am

    [Bill Davis] “Well, there’s a LOT to like about Lightroom. But there are dificiencies as well. It excels at the basic initial tasks of importing, sorting and rating photos to pick selects from large groupings. Then it has a basic suite of touch up tools to let you quickly enhance and repair your selected raw files.

    But it’s internal semi round trip link to Photoshop (the return file shows up as a separate tiff alongside the unretouched original) is a good indication that Adobe did not try to make it anywhere near a full fledged photo editor.

    It also sports a good bit of what I think of as feature creep, with stuff like a slide show generator and “order me a photo album” crap that I just ignore.

    That said, it’s fast, great at what it does and not overly complex once you get beyond figuring out whether and when to split off sub catalogs.

    What could send me to Photos is if Apple figures out a clever way to let me not just retouch and organize my stills, but makes them accessible directly via the FCP X media browser across all my apple devices.

    Right now, Lightroom work is a separate operation and when it’s done I’m plopping photos to the desktop and importing them to X as a totally separate operation. If I miss one, it’s launch Lightroom again and go through the whole dance over.

    I suspect Apple has a big opportunity to improve that workflow.

    We’ll see.”

    All good info, thanks Bill. I also agree that Apple has a huge opportunity here if they see it?

    Mitch Ives
    Insight Productions Corp.

    “Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

Page 6 of 9

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