Creative Communities of the World Forums

The peer to peer support community for media production professionals.

  • Marcus Moore

    March 28, 2013 at 6:57 pm

    Speculation.

  • Jeremy Garchow

    March 28, 2013 at 8:15 pm

    [John Heagy] “t now reads TCSource aka the original QT/FCP7 Reel/Tape entry. It’s populating the com.apple.ProAps.Reel field so it must look there first and then TCSource. I’d assume if the two were different it would use the com.Apple… entry.

    Thank You Apple!”

    Yes. Thank you, Apple.

  • Oliver Peters

    March 28, 2013 at 9:10 pm

    Agreed. Also for Alexa files, the LogC-to-REC709 processing is a very useful touch.

    – Oliver

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

  • Chris Kenny

    March 28, 2013 at 10:37 pm

    [Oliver Peters] “Agreed. Also for Alexa files, the LogC-to-REC709 processing is a very useful touch.”

    Yup, both this and the new reel name support are a big deal for indie feature film workflows.

    Between this, the R3D support, and the built-in proxy/optimized media generation features, there’s not much of a case left for externally created offline editorial dailies. That’s a pretty big change in the feature world.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Oliver Peters

    March 28, 2013 at 11:09 pm

    [Chris Kenny] “Between this, the R3D support, and the built-in proxy/optimized media generation features, there’s not much of a case left for externally created offline editorial dailies”

    While true, that’s still only specific to an FCP X workflow.

    – Oliver

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

  • Marcus Samuel-gaskin

    March 28, 2013 at 11:11 pm

    [Oliver Peters] “Agreed. Also for Alexa files, the LogC-to-REC709 processing is a very useful touch.”

    Nice!

  • Bret Williams

    March 29, 2013 at 12:23 am

    So what do you think they’ll call the new app since its against the App Store rules to have upgrades. There is no upgrade structure or path in the App Store. Steve Jobs said so himself when he introduced it. It doesn’t stop anyone from creating a new app with a different name, but it wouldn’t be upgrade pricing because then anyone could buy it for the upgrade price. And that would mean discontinuing the previous app development or continuing to update and sell multiple versions of an app. I don’t think the App Store wants you cluttering up the store with multiple apps either. So you’d have to discontinue one (and remove it from future downloads) and come out with a new app and a new name. I don’t see any if it being a good marketing move for any company.

  • Chris Kenny

    March 29, 2013 at 12:53 am

    [Oliver Peters] “While true, that’s still only specific to an FCP X workflow.”

    Well, yeah, that’s sort of my point. There are productions spending many thousands of dollars getting footage transcoded because of the NLE decisions they’re making, where with FCP X they could simply take the footage off the mags, load it onto a MacBook Pro, and start cutting, as proxy media (which they could seamlessly toggle over to) was automatically generated in the background.

    Of course as a post house providing such transcoding services, we don’t mind the standard approach too much (heh). But the next time I’m speccing the workflow for one of our occasional internal end-to-end projects, I’ll absolutely skip the traditional dailies workflow. Even despite the fact that we can do all of it without paying an outside vendor. Skipping it should save considerable time, and there’s much less that can go wrong e.g. taking a project into Resolve if the sequence coming from the NLE already contains references to your online media.

    This is the future — digital cinema workflows with high-end media formats made nearly as simple as downloading and editing together some clips from your phone.


    Digital Workflow/Colorist, Nice Dissolve.

    You should follow me on Twitter here. Or read our blog.

  • Marcus Moore

    March 29, 2013 at 3:03 am

    I’m personally not betting on this being an issue until next year. I think we’ll continue along the 10.0.X update path for a little while longer.

    That said, under the current appStore rules there’s only 2 options for a “10.1”.

    1. another free update to exiting users (basically the status quo)

    2. Released as a new app at the full price. 10.0.X disappears as a purchase option for new users. But remains for existing users who don’t upgrade as a path to updates or reinstalling the software down the road.

    I think we’ll have a clearer picture about the update based on what gets revealed at the NAB press event.

  • Chris Harlan

    March 29, 2013 at 3:28 am

    [Marcus Moore] “NAB press event”

    What NAB press event?

Page 2 of 7

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