Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Todays FCP X announcement

  • Aindreas Gallagher

    February 2, 2012 at 12:51 am

    i can’t keep track of who is pro or con anymore? aren’t you a floater??

    🙂

    ok so for the sake of a rant to reassert my rabid credentials:

    look forget everything else – bottom line – the FCPX timeline is a bombsite. its a crater. and they’re not going to try and fix that because of where they wanted to bring imovie.

    the timeline is the central intellectual conceit of an editing system. Apple’s timeline is a broken, slow to react mess of indescribable proportions.

    primary storyline, secondary storyline, connected clips, roles, its ridiculous. it represents lunatic *not invented here* avoidance of the continuing reality of the underlying track structure. Apple’s core timeline work is immensely annoying.

    people can talk about four dimensional databases and exposing data though three dimensional artificially intelligent tags all they want.

    the timeline is a gloopy ridiculous reductive metaphor mess. that, I would argue, is the central issue.

    there – a bit of the rabid froth.

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

  • Chris Harlan

    February 2, 2012 at 1:56 am

    [David Lawrence] ” Spatial position is essential in mapping a nodal pipeline. The last thing you’d want is for it to constantly reflow. “

    I was just trying to imagine that, and it made me laugh my head off.

  • Oliver Peters

    February 2, 2012 at 2:06 am

    [Aindreas Gallagher] “i can’t keep track of who is pro or con anymore? “

    You mean me? I’m trying to keep an open mind, but the application keeps fighting me on that 😉

    – Oliver

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

  • Walter Soyka

    February 2, 2012 at 2:09 am

    [Chris Harlan] “Those timelines are interesting, Walter. I’ve got to go back and read that.”

    Thanks, Chris. I’d certainly appreciate hearing your thoughts on it, especially in light of the release of 10.0.3 (which I would note on the timeline if I were building it today — it’s a much more important release than a couple of the major version FCP Classic releases).

    I’m glad to see the pro features making their way back into FCPX, but 10.0.0’s missing functionality wasn’t the main thrust of my thinking, then or now. The question has become much larger than FCP/FCPX for me.

    Walter Soyka
    Principal & Designer at Keen Live
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    RenderBreak Blog – What I’m thinking when my workstation’s thinking
    Creative Cow Forum Host: Live & Stage Events

  • Chris Harlan

    February 2, 2012 at 2:36 am

    [Walter Soyka] “I’m glad to see the pro features making their way back into FCPX, but 10.0.0’s missing functionality wasn’t the main thrust of my thinking, then or now. The question has become much larger than FCP/FCPX for me.”

    I agree completely. I’ve never had any doubt that Apple would do the things they announced they would. The bright side today–for me–are the small things they have turned their attention to. But it also demonstrates to me that the notions I’ve held of X’s trajectory are pretty much on target, and that the decisions I’ve made to expand my personal toolset beyond what Apple has to offer were correct. I guess I’m even grateful for the motivation. And, as X opens up more, I’m sure I’ll find uses for it.

    I was cutting a piece last night on FCP7, with several temporarily overlapping chunks of video, and 18 tracks of audio–some synced, some out of sync, and some not synced at all–and I became aware for a moment how much I was depending on the color-coded timecode overlay in the record monitor and all of the TC sync references on the timeline, and really, how much I regularly depend on them without even being aware that I am. And then today, as I read about the new fixes and enhancements, it just really struck me how far apart these tools are.

  • Adam Dewhirst

    February 2, 2012 at 3:25 am

    i’ve done some reading about roles and i find it hard to believe they are being talked aboutas a replacement for tracks. they are an organisational tool. tracks can serve this purpose well and still do in legacy fcp versions but their main use for me is providing a visual summation of my edit and ease of editing.

  • Bill Davis

    February 2, 2012 at 4:53 am

    [Brad Davis] “They’ll keep adding to it but it will never be like FCP 7.”

    Agree with this. And that’s a very good thing. 7 was great. But built for a different era and largely stuck in the particular needs of that era.

    [Brad Davis] “This also further my previous conclusion 8 months ago that the entire FCS was dumped because of legal and licensing of the previous software more than anything.”

    Disagree with this. If that was the only issue, they could have simply totally dumped their NLE business and the resulting revenue loss would have had an effect on Apple roughly equal to someone wielding a squirt gun during a monsoon rainstorm.

    My view is that Apple had some of the finest NLE interface programmers on the planet in-house. And the best way to keep the top talent happy is to give them projects that challenge their skills and capabilities.

    The X project was precisely that. A room full of top notch experts being given the ultimate reward for having built a program that changed the whole industry a decade plus ago. That last decade project has generated a nice return, so the FCP team was simply given marching orders something like “dream big, don’t be afraid to break with tradition if you think you can make something that will work better in the changing landscape of media in the 21st century.”

    I think they’ve done that.

    Legacy developed to meet the needs of the video/movie industry in 2000. That was a world where broadcast and motion picture production were the “marquee” outlets. – but web video, video for teaching purposes, and video produced for the kinds of iDevices that Apple produces have generated new needs that are basically “different” from the old MovieStudio/TV station model.

    So Apple is constructing a tool for this new world.

    Simple as that.

    “Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

  • Simon Ubsdell

    February 2, 2012 at 11:19 am

    [Michael Gissing] “But still vaporware”

    Absolutely – and even come the end of February I will sit back and wait for others to discover all the things XtoPro may not be able to do. (On day one it won’t be able to handle levels or transitions for a start …)

    Automatic Duck, now entirely broken by 10.0.3, had a number of alarmingly significant issues which made it very far from the robust solution that is essential if FCPX is to be taken seriously at the top end.

    Robust really is the word here. Rock solid, 100% reliable. Anything less means time wasted, missed deadlines, loss of revenue. Gimcrack solutions just won’t cut it here.

    So great, Apple delivered multicam (of a sort, because the audio side doesn’t really work yet), and yes they delivered the first tentative move towards monitoring (but it’s still “Beta” – as if the whole of the rest of the application wasn’t also still in Beta). I can’t get really excited about those things because we’ve known they were coming now for months.

    But multicam for me is a pointless bit of window dressing when it’s still missing OMF – which FCPX absolutely must have and should have had from the word go.

    99% of jobs that I do absolutely require going to ProTools to finish the audio, full stop, no negotiations. Hence no OMF, no FCPX. I can’t believe that more people are not kicking up a stink about this as to my mind it’s the single most important obstacle – not to say that there aren’t others.

    Simon Ubsdell
    Director/Editor/Writer
    http://www.tokyo-uk.com

  • Simon Ubsdell

    February 2, 2012 at 12:10 pm

    [Michael Gissing] “But still vaporware”

    Absolutely – and even come the end of February I will sit back and wait for others to discover all the things XtoPro may not be able to do. (On day one it won’t be able to handle levels or transitions for a start …)

    Automatic Duck, now entirely broken by 10.0.3, had a number of alarmingly significant issues which made it very far from the robust solution that is essential if FCPX is to be taken seriously at the top end.

    Robust really is the word here. Rock solid, 100% reliable. Anything less means time wasted, missed deadlines, loss of revenue. Scissors and paste solutions just won’t cut it here.

    So great, Apple delivered multicam (of a sort, because the audio side doesn’t really work yet), and yes they delivered the first tentative move towards monitoring. I can’t get really excited about those things because we’ve known they were coming now for months.

    But multicam for me is a pointless bit of window dressing when it’s still missing OMF – which FCPX absolutely must have and should have had from the word go.

    99% of jobs that I do absolutely require going to ProTools to finish the audio, full stop, no negotiations. Hence no OMF, no FCPX. I can’t believe that more people are not kicking up a stink about this as to my mind it’s the single most important obstacle – not to say that there aren’t others.

    Simon Ubsdell
    Director/Editor/Writer
    http://www.tokyo-uk.com

  • Craig Seeman

    February 2, 2012 at 3:28 pm

    Might it be that OMF won’t happen until Logic Pro X is out . . . unless a third party succeeds. It might be Apple wants Logic to be an equal option, not giving ProTools and advantage. I’m not saying that’s a good business decision but it wouldn’t surprise me that Apple wants to give their tools equal footing (at least in their perception).

Page 9 of 10

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