Forum Replies Created

Page 86 of 124
  • Shawn Miller

    January 24, 2013 at 3:43 am in reply to: scrutinising FCPX and john davidson’s timelapse.

    [Jeremy Garchow] “[Walter Soyka] “The poor fellow needs procedural editorial.”

    It reminds me of this EOL software: https://creativemac.digitalmedianet.com/articles/viewarticle.jsp?id=35021

    Jeremy”

    Holy crap, that is just fantastic! I need that for PPro today. 🙂

    Shawn

  • Shawn Miller

    January 24, 2013 at 3:38 am in reply to: scrutinising FCPX and john davidson’s timelapse.

    [Walter Soyka] “See this recent post on the Avid forum:

    Advice for the most monotonous workflow ever… [link]

    The poor fellow needs procedural editorial.”

    Wow, talk about a great use case! 🙂

    Shawn

  • Shawn Miller

    January 24, 2013 at 3:05 am in reply to: scrutinising FCPX and john davidson’s timelapse.

    [Walter Soyka] “Shawn, I’m suggesting there could be a lot more to it than that, too.

    Think about how proceduralism works in a tool like Houdini or XSI. You can make structural alterations to a scene based on data that you import into the scene.”

    [Walter Soyka] “This is a bit off-the-cuff, so I’m sure there are better examples, but procedural editorial could guide a good number of routine or simple decision-tree-oriented tasks.”

    Absolutely, and I’m completely agreeing with you Walter. My example was a lot simpler, but I think we’re getting at the same point. Procedural workflows are extremely powerful and flexible, it’s just a shame that none of the NLEs allow you to extend their functionality in that way.

    Shawn

  • Shawn Miller

    January 24, 2013 at 12:51 am in reply to: scrutinising FCPX and john davidson’s timelapse.

    [Aindreas Gallagher] “but I fail to understand even the most basic causal linkages from those system work cases to picture and video editing.”

    I don’t know Aindreas, it seems like that kind of functionality could be very useful in an NLE. I would love to be able to change the font color or scale of 50 or 60 lower thirds titles with a few simple lines of text.
    Then again, I’m a heavy user of Cinema 4D and AE, so I do find myself missing the power and flexibility of expressions when I’m editing. That said, I also recognize that scripting, even light or node based scripting isn’t everyone’s cup of tea… but I still think it would be cool.

    Shawn

  • Shawn Miller

    January 15, 2013 at 7:34 am in reply to: Version 6.5 a big step forward for Edius

    [Lance Bachelder] ” This is a FCPX forum and that means Apple hardware so…”

    Considering the number of platform discussions around here lately, this post still seems in-bounds. Maybe the name of this forum really should be changed…

    Shawn

  • Shawn Miller

    January 15, 2013 at 4:02 am in reply to: Version 6.5 a big step forward for Edius

    [Marcus Moore] “How does this belong in an FCPX forum again…?”

    Seems as appropriate as any of the Smoke 2013 or Avid posts. Isn’t that part of the reason for this forum… to discuss alternatives to FCP Legacy – X and otherwise?

    Shawn

  • Shawn Miller

    January 15, 2013 at 12:37 am in reply to: Version 6.5 a big step forward for Edius

    You’re a brave man, Dominic! I’m happy that all turned out for the best though. It sounds like Edius 6.5 really deserves a serious look from Windows users.

    Shawn

  • Nice, I’m glad to see they’re still putting work in on Conduit. I’m bummed that the latest release doesn’t include a Windows version… but I’m glad to see it progressing nonetheless.

    Shawn

  • Shawn Miller

    January 8, 2013 at 6:24 am in reply to: Understanding FCPX under the hood.

    [Bernard Newnham] “I always wonder why people bother with that stuff – I it think might be “gear porn” stuff that gives them a thrill.

    Getting the very fastest machine at any point in time might be good hobby, but it isn’t good business. Those processors they were talking about cost more even than an iMac, and give a few percentage points of speed gain.”

    I agree with most of what you’re saying here, Bernie. A fast(ish) single proc machine with a fast HDD sub system and beefy(ish) GPU is more than enough for many creative pros. For users needing as many CPU threads as they can get, an i7 based system isn’t going to cut it though. For tasks like fluid/physics simulations or muti-threaded rendering, more cores = faster output. Why not just send out to the render farm you might ask? Because you need to do full quality test renders before farming out whole sequences, and assuming you do a lot of test renders before final output (as I do), saving a few minutes per frame can add up to hours of valuable project time saved (over the life of the project).

    Shawn

  • Shawn Miller

    January 5, 2013 at 6:39 am in reply to: Understanding FCPX under the hood.

    [Jeremy Garchow]
    I’d really like to know how much cheaper that’d be.”

    It’s not too difficult to suss out. Components are pretty easy to price… might be fun to visit newegg.com, frys.com or your local PC hardware shop to price out a new system.

    Shawn

Page 86 of 124

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