Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects AE CS5 network issues

  • AE CS5 network issues

    Posted by Eric Santiago on September 15, 2010 at 7:11 pm

    Ive been having problems rendering over a network lately.
    We have a XServe running Leopard using AFP.
    The same render takes 41 sec using local desktop but 2 min plus over the network.
    Same test with CS4 and no problem.
    Just a CS5 issues.
    The only thing different about my set-up is that I turned on the 64bit option on the MacPro.
    I tried different network points and some crash CS5.

    Todd Kopriva replied 14 years, 4 months ago 2 Members · 7 Replies
  • 7 Replies
  • Todd Kopriva

    September 16, 2010 at 6:47 am

    > The only thing different about my set-up is that I turned on the 64bit option on the MacPro.

    Why?

    If you thought that you needed to do that for After Effects, then don’t bother.

    You didn’t say what kind of footage or output movie type you’re using. If you’re rendering over a network, I hope that you’re not rendering and exporting to QuickTime files. Are you using image sequences?

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    Technical Support for professional video software
    After Effects Help & Support
    Premiere Pro Help & Support
    ———————————————————————————————————

  • Eric Santiago

    September 17, 2010 at 3:08 pm

    I was testing the capabilities of CS5 and found a link on turning on the 64bit. If Adobe had sent me your link then I would have listened 🙂
    This is not just a network issue. The same CS5 will not render to desktop. The QT gets created but when you try to open or import into another app, it states that its not a movie file.
    Ive been rendering for the last few years to QT none compression.
    We’ve been doing the same set-up since CS2 over the network.
    Its a XServe G5 running Leopard Server.

  • Eric Santiago

    September 17, 2010 at 3:34 pm

    Just did another test.
    It looks like an issue with file size.
    Ive been testing with a 40 sec comp that renders past 2GB.
    I used the same comp but blocked it down to a file at 600mb.
    The file opened with no errors.

  • Todd Kopriva

    September 17, 2010 at 4:07 pm

    Regarding the 2GB issue: This is a known problem with After Effects CS5. Actually, it’s a known problem with the QuickTime Compression Session API that Apple asked us to use for this version. We found out (too late) that this API has a limitation when rendering over a network. The workarounds are a) render and export using a different format—anything but QuickTime— or b) render and export locally, not over the network. We have a bug report in to Apple about this and are looking into what we can do on our side. Sorry for the inconvenience.

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    Technical Support for professional video software
    After Effects Help & Support
    Premiere Pro Help & Support
    ———————————————————————————————————

  • Eric Santiago

    September 17, 2010 at 4:13 pm

    Wow that I didnt know.
    What about rendering too local drive?
    The original docs and resources are on the network, would that be the problem too?
    Should I move everything locally?
    Im going to test this on Windows 7 CS5 station too.

  • Todd Kopriva

    September 17, 2010 at 4:21 pm

    > What about rendering too local drive?
    The original docs and resources are on the network, would that be the problem too?
    Should I move everything locally?

    The cause of the problem is the export destination being across a network, so you shouldn’t have to move your input files.

    As I said before, the workaround is to render and export to the local computer or to render and export to anything other than QuickTime.

    As an aside: I would never recommend rendering and exporting to self-contained movie files over a network, anyway. I prefer working with image sequences over the network and then using QuickTime Pro or Adobe Media Encoder to assemble those into a final movie at the end as a batch process.

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    Technical Support for professional video software
    After Effects Help & Support
    Premiere Pro Help & Support
    ———————————————————————————————————

  • Todd Kopriva

    September 17, 2010 at 11:05 pm

    BTW, here is a message that shows that it’s not just After Effects that hit this new QuickTime API problem:
    https://lists.apple.com/archives/quicktime-api/2006/Aug/msg00235.html

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    Technical Support for professional video software
    After Effects Help & Support
    Premiere Pro Help & Support
    ———————————————————————————————————

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