Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Prognostications on FCPX compared to OSX and iOS from Alex4D

  • Jeremy Garchow

    June 26, 2012 at 6:48 pm

    [Walter Soyka] “I don’t mind speculating on what FCPX might become — crystal ball gazing has become a hobby in the last year — but Franz has a point that we speculate more about FCPX than other NLEs. For example, Adobe actually demoed a concept for collaborative editing at NAB [link] with relatively little fanfare, but here we are talking about how a product that has not shown collaborative editing must surely be headed in that direction because its underpinnings may or may not allow it.”

    Well, there’s a demo, and there’s what’s actually in the application right now.

    Adobe is very serious about all of this, and I am sure something like it will come out of those efforts. The description given by Kevin sounds like a real life cloud editing solution, and it is no coincidence Creative Cloud was launched this year.

    Today, Pr needs help in sharing projects and media reconnect, FCPX doesn’t need as much help as it’s already in there to some degree. While it might not be cloud editing, it could be. With a few tweaks, the media could live in the cloud, the Event/Project (or maybe just Project) is local. The links are all there already. It’s not hard to see how this might happen because it is already happening in FCPX minus the cloud based server which is obviously a huge part of the equation, but the general infrastructure is there none-the-less. There is also a pretty kick ass Proxy creation system in case you need to *take the edit with you, and all it takes to link back to full res is a pref change. But maybe all of this is an after thought?

    I hear what you’re saying, and the non-relase of a new MacPro does not make me doubt Apple anymore than it did by actually refreshing the older MacPro model and keeping it on sale. The silence of that action speaks volumes, although I am sure that is another unpopular opinion of Apple as it relates to FCPX. So be it. I’ll roll the dice for now as I am running top of the line FCS3 hardware. 32bit has it’s merits. 🙂 As I mentioned in my first response, at some point these dreams need to become somewhat of a reality.

  • Jeremy Garchow

    June 26, 2012 at 6:55 pm

    [Franz Bieberkopf] “Jeremy,

    There is a long history of air quotes and scare quotes (uses breakdown below). None of them are the kind of caricatured arch summary that you used – though I suppose you meant something along the lines of snark?

    Franz.”

    If I only had the prefect analogy to explain why I used quotes. The quote itself was an analogy.

    To make it easy for you, I was paraphrasing. If I could go back and edit the old post, I’d use a single quotation. So here it is again for preservation:

    “[Franz Bieberkopf] “You think so? I would say it is broadly encouraged,”

    [Jeremy Snarko]
    Except when someone like Alex4d comes up with some good ideas that are based on what he actually sees inside the app and backed up by a bit of Apple development history, and someone like you says something like, ‘Hogwash, Apple’s database motives are an afterthought. How do I know? I just know. I’ve never tried to do anything with media management in FCPX, I just know it’s an afterthought.'”

  • Jeremy Garchow

    June 26, 2012 at 6:57 pm

    [Chris Harlan] “Of course there is also option 3, but I’m not certain that porn actually has titles anymore.”

    At first glance, I read “titles” as something totally different. I will let you use your imagination.

    Those are real quotes, not air quotes.

  • Jeremy Garchow

    June 26, 2012 at 6:59 pm

    [Oliver Peters] “The network should be plenty fast to have E&P folders live in the SAN volume, but for some reason the system isn’t happy when you do that. Maybe in the future.”

    Do you have a separate metadata network from other network traffic?

  • Chris Harlan

    June 26, 2012 at 7:01 pm

    [Jeremy Garchow] “[Chris Harlan] “Of course there is also option 3, but I’m not certain that porn actually has titles anymore.”

    At first glance, I read “titles” as something totally different. I will let you use your imagination.

    Those are real quotes, not air quotes.

    Oh, it definitely still has those.

  • Bill Davis

    June 26, 2012 at 7:04 pm

    [Chris Harlan] “Is this as off-topic as I can possibly get?”

    Actually, unless you use an analogy and simultaneously invoke Hitler – no.

    ; )

    “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

  • Oliver Peters

    June 26, 2012 at 7:06 pm

    “Do you have a separate metadata network from other network traffic?”

    The workstations are connected only via the Fibre Channel network to media. There is also a metadata network via Ethernet. The chassis has its own built-in controller (I presume running on Linux). In addition to the 4 MacPro edit workstations, there’s also an Xserve to run FC Server. It is the 5th station on the system.

    Oliver

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

  • Jeremy Garchow

    June 26, 2012 at 7:09 pm

    [Oliver Peters] “The workstations are connected only via the Fibre Channel network to media. “

    Got ya.

    Do they offer a File based option or would you need to add more software?

  • Walter Soyka

    June 26, 2012 at 7:12 pm

    [Jeremy Garchow] “Well, there’s a demo, and there’s what’s actually in the application right now.”

    Jeremy, I saw the demo. They were running an internal build of Premiere Pro, live on stage at NAB. To my mind, that makes the proposed feature closer to reality with Premiere than FCPX, where it has not yet been seen in a running application, but only hinted could be possible based on the architecture.

    [Jeremy Garchow] “The links are all there already. It’s not hard to see how this might happen because it is already happening in FCPX minus the cloud based server which is obviously a huge part of the equation, but the general infrastructure is there none-the-less.”

    They are totally different approaches, and Apple does not have the infrastructure in place to do what Adobe was doing in that demo. The local machine was a Premiere thin client, and the remote machine was the server actually responsible for all the media storage and realtime rendering and streaming.

    Apple’s in-place infrastructure could allow you to work on your local copy of the media; Adobe’s doesn’t require you to have the media at all. You’ve mentioned you’re going to be mobile; with Adobe’s collaborative concept, someone could ingest media for you at the office and you could start cutting it right away, with no need to even download proxies.

    All this is orthogonal to my original point, though, which was that I think a publicly demoed concept is better evidence of a company’s current development efforts than architectural hooks.

    [Jeremy Garchow] “But maybe all of this [FCPX awesomeness] is an after thought?”

    I’ve used brackets to editorialize and summarize. I’ll appeal to Chris Harlan, forum line judge, if it’s in-bounds or not. 🙂

    I don’t think the beautiful engineering in FCPX is an afterthought. I think that the FCPX architecture is its best weapon going forward.

    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

  • Bill Davis

    June 26, 2012 at 7:30 pm

    [Walter Soyka] “\ — but Franz has a point that we speculate more about FCPX than other NLEs. For example, Adobe actually demoed a concept for collaborative editing at NAB [link] with relatively little fanfare, but here we are talking about how a product that has not shown collaborative editing must surely be headed in that direction because its underpinnings may or may not allow it.”

    Like it or not, what everyone snap-characteized as the “debacle” of the X launch, may have been nothing more or less than the most painfully “necessary” of evils.

    We’re here talking about X a year later, because the ideas it represents prove over and over and over again to be worth debating.

    And NOT because Apple created them. Because they didn’t. This databasification of the world is everywhere. It’s Google, it’s smart phones, it’s the cloud, and it’s some “mechanic” plugging a bigger computer into a smaller computer in your car and reading out the database of how it’s operated over the past month.

    X is an expression of grafting content management, content assembly (and I’d increasingly argue, nascent content distribution) into a single modern tool.

    It does these things amazingly well for some classes of users – and not as well for others – but it does them in a coordinated fashion with a lot of obvious thought to how to make the entire creative/content management flow more accessible and more useful to more users.

    We all got lost (and in varying degrees, pissed) based on “how” it worked – and the real questions still being sorted out revolve around “why” it works the way it does.

    Speculation is our only tool.

    And I, for one, feel honored to be able to here to actively participate in this discussion. It stretches my thinking. And that’s good for me.

    Period.

    “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

Page 4 of 7

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